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 trying to run a stepping-stone analysis in MrBayes to get accurate marginal likelihood estimates for two different constrained trees. I am using the following MrBayes command block in my nexus file:
This analysis starts off fine and runs for about 9M generations of the 20M I have it set to run for, and I get the following error:
DEBUG ERROR: Log likelihood nan after move 'Slider(Ratemultiplier{all})'
After that all of the output from MrBayes stops, but the processors continue to run at 100% as if the analysis is still running. From what I can gather my Ratemultiplier has become so small that it can't be expressed with computer precision anymore, but I am completely at a loss for how to fix this. I ran this analysis and its pair (the only difference is in the 'muusoctopus' constraint) simultaneously using the MPI version of MrBayes, with each analysis spread across 10 processors. Both analyses get the same error somewhere between 9M and 10M generations.
Any ideas how to fix this problem? Thanks in advance!
The text was updated successfully, but these errors were encountered:
I am trying to run a stepping-stone analysis in MrBayes to get accurate marginal likelihood estimates for two different constrained trees. I am using the following MrBayes command block in my nexus file:
This analysis starts off fine and runs for about 9M generations of the 20M I have it set to run for, and I get the following error:
After that all of the output from MrBayes stops, but the processors continue to run at 100% as if the analysis is still running. From what I can gather my Ratemultiplier has become so small that it can't be expressed with computer precision anymore, but I am completely at a loss for how to fix this. I ran this analysis and its pair (the only difference is in the 'muusoctopus' constraint) simultaneously using the MPI version of MrBayes, with each analysis spread across 10 processors. Both analyses get the same error somewhere between 9M and 10M generations.
Any ideas how to fix this problem? Thanks in advance!
The text was updated successfully, but these errors were encountered: