Open JosieReinhardt opened 9 years ago
Thanks for this report. We should be able to help fix this. We'll try reproducing with one of our data sets, first. Otherwise, if there's any public dataset that gives the same error that would be a great starting point.
Thanks,
I ended up pre-pruning my dataset using another tool (tree_doctor) and then everything worked fine. But, I figured you'd want to know anyway. I'm not sure about a public dataset but if you do want mine to reproduce the error, I'd be happy to share an anonymized version.
Josie
On Thu, Aug 6, 2015 at 1:17 PM, Ryan Newton notifications@github.com wrote:
Thanks for this report. We should be able to help fix this. We'll try reproducing with one of our data sets, first. Otherwise, if there's any public dataset that gives the same error that would be a great starting point.
— Reply to this email directly or view it on GitHub https://github.com/rrnewton/PhyBin/issues/10#issuecomment-128448764.
The prune option does not appear to be working properly - on my 22 taxa dataset, binning works successfully when I run the full dataset, but fails for one of two reasons when I use --prune.
First, the program errors out and produces no output trees/clusters if I specify > 5 taxa with --prune, and this seems to be in any combination.
Second, if I specify 5 or fewer taxa, the program completes, but the output doesn't make sense. A single cluster is produced, regardless of the edit distance I specify, and the consensus tree output file includes taxa that were not specified with --prune, whereas the alltrees file includes only taxa specified with prune.
The output from two examples demonstrating these is pasted below:
First issue (crash when > 5 taxa are specified with --prune)
Second issue (weird output when <= 5 taxa are specified with --prune)