-
Notifications
You must be signed in to change notification settings - Fork 63
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
terminate called after throwing an instance of 'std::runtime_error' #71
Comments
this looks very similar to the issue recently reported on the raxml google group here: https://groups.google.com/forum/#!topic/raxml/gluJCb9PGvA Could you please try to reproduce with the latest dev and/or |
Thanks for the suggestion. I've tried the following:
However, the issue persists in all of these cases. |
Just an update, the issue seems to be limited to the |
Thanks for checking! Can I get your alignment to reproduce the error? |
Sure, here is a trimmed down version of the original that gives the same error: |
thanks, I'll have a look! just a side note: if you do have the full MSA, it is preferable to use it instead of |
I wasn't aware of that. Can you briefly outline what the advantage of using the full MSA is over using ascertainment bias correction? Would a similar result be achieved by including variant sites as trinucleotides instead? Thanks you. |
The main shortcoming of ascertainment bias correction is that it ignores the missing data/indels in the original MSA. Please see detailed discussion here: |
Issue description:
raxml-ng fails on certain input for an unknown reason. The time until failure seems to depend on the random seed used. Jobs have been run on an HPC with 8 cpus and 32 GB ram requested.
stdout:
stderr:
The text was updated successfully, but these errors were encountered: