Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apples collapses some branches of the backbone tree to polytomies in the jplace file #14

Open
computations opened this issue Oct 6, 2023 · 1 comment

Comments

@computations
Copy link

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).

tanglegram

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.

example-files.tar.gz

@balabanmetin
Copy link
Owner

Thanks for using APPLES-2. APPLES-2 calls FastTree internally to reestimate backbone tree branch lengths. The command is

FastTreeMP -nosupport -nt -nome -noml -log tree.log -intree backbone.nwk < ref.fa > minimum_evo_backbone.nwk

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants