You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running some benchmarks with several placement programs, and apples will (rarely) modify the backbone tree by collapsing some branches into polytomies (see the following image for an example).
This makes it difficult to compute a common node distance between all the placement tools.
I looked at the options as well as the code, and I didn't an obvious way to stop this from happening. Is there some way to stop this from happening?
I've attached the some files. 5.tree is the backbone tree for the rest of the programs in the benchmark, apples.tree is the tree extracted from the jplace file, and apples.jplace is the original jplace file.
Since I don't have your alignment, can you call this and see whether minimum_evo_backbone.nwk has any collapsed branches. If that's the case, you can remove multifunctions in minimum_evo_backbone.nwk and provide that tree to APPLES-2 with "-D" option so that FastTree is not called internally. That will ensure the output tree will have no multifurcations.
I am running some benchmarks with several placement programs, and apples will (rarely) modify the backbone tree by collapsing some branches into polytomies (see the following image for an example).
This makes it difficult to compute a common node distance between all the placement tools.
I looked at the options as well as the code, and I didn't an obvious way to stop this from happening. Is there some way to stop this from happening?
I've attached the some files.
5.tree
is the backbone tree for the rest of the programs in the benchmark,apples.tree
is the tree extracted from the jplace file, andapples.jplace
is the original jplace file.example-files.tar.gz
The text was updated successfully, but these errors were encountered: