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

Non-comprehensive constraint tree issue #114

Closed
zcalamari opened this issue Feb 10, 2021 · 6 comments
Closed

Non-comprehensive constraint tree issue #114

zcalamari opened this issue Feb 10, 2021 · 6 comments

Comments

@zcalamari
Copy link

Hello,

I am trying to run RAxML-ng with a non-comprehensive constraint tree, but I keep getting this error:

[00:00:00] Loaded non-comprehensive constraint tree with 15 taxa
Assertion failed: (bin_tree->inner_count == old_inner_count + degree-3), function pllmod_utree_resolve_multi, file /Users/sco/alexey/raxml-ng/libs/pll-modules/src/tree/pll_tree.c, line 356.
zsh: abort /Applications/raxml-ng_v0.9.0_macos_x86_64/raxml-ng --all --tree-constraint

I have also tried running this on the CIPRES implementation and it also quits after the "[00:00:00] Loaded non-comprehensive constraint tree with 15 taxa" line. My constraint tree is a fully bifurcating newick tree that doesn't have all the species in it.

Any help would be appreciated!

@amkozlov
Copy link
Owner

could you please post your constraint tree file and full raxml-ng log here?

@zcalamari
Copy link
Author

I have attached both, thanks!

RAxML.output.txt

NewickExtantCollapsedBackboneTree.txt

@amkozlov
Copy link
Owner

For some reason, your tree had an extra pair of parenthesis around of the clades. Please find fixed tree attached.

Also, I strongly recommend to upgrade raxml-ng to the most recent version.

tree3.txt

@zcalamari
Copy link
Author

Thanks for the support! I was planning to run this on CIPRES and was using my local install to troubleshoot when the CIPRES version wasn't working. Will update regardless.

@amkozlov
Copy link
Owner

OK from now on, raxml-ng will print a meaningful error message in such cases.

So I guess this issue is resolved?

@zcalamari
Copy link
Author

Yes, thank you!

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