-
Notifications
You must be signed in to change notification settings - Fork 3
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
NullPointerException during initialization for UCRelaxedCladeClockModel #2
Comments
Can you send me your xml files so I can debug it? |
Ah, sorry, I thought that I added it to the github post, but it does not accept XML files. Here: I went through example XML and those old example XMLs that are downloaded with BEAST, but are no longer on github, but couldn't find why it isn't working. Clock, priors, operators and logs are all set up as in example files. |
Sorry for the delay. I just had a look and it works for me with BEAST2.5. What is your BEAST version? |
2.5.2. Thanks, I would like to leave this open for a while until I figure out why it doesn't work or someone else can chip in with a similar problem. |
Strange, what's the version of FLC in the package manager? |
1.1.0, what appears to be latest. |
OK, I didn't realize that the XML you sent me actually worked because of the order of the taxa as you mentioned at the end of your first comment. If I select another set of taxa I get the same errors you described. The problem comes from SimpleRandomTree, it appears to be initialized differently from RandomTree. As a quick fix you can replace this line
|
The difference (from what I understand) seems to be in setUpMap between UCRelaxedCladeClockModel and UCRelaxedMultiCladeClockModel.
In Clade model, the SetUpMap first goes into the leaf nodes and then increments BranchCladeCount. In MultiClade model, it does this in opposite way, which while it makes a little less sense to me, it works.
Well, kind of. With MultiCladeModel I get:
Strangely, code runs when the created monophyletic taxon includes taxa in the same order as they are included in the alignment, starting from first taxa. Which might point to something, however the example file runs fine and doesn't have this pattern.
Did I misspecified something?
The text was updated successfully, but these errors were encountered: