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

Beauti clock model cloning problem (STACEY, StarBeast v1) #701

Closed
Graham853 opened this issue May 9, 2017 · 1 comment
Closed

Beauti clock model cloning problem (STACEY, StarBeast v1) #701

Graham853 opened this issue May 9, 2017 · 1 comment

Comments

@Graham853
Copy link

@Graham853 Graham853 commented May 9, 2017

Start Beauti 2.4.6 (also 2.4.5)
Choose STACEY or StarBeast template
Load 26.nex, 29.nex, 47.nex
Clock Model, change 26 to relaxed log normal
Select all, clone from 26
Save.
The XML won't run in BEAST.

Error 110 parsing the xml input file

validate and intialize error: Operator updown.all.Species.29 has a statenode clockRate.c:29 in its inputs that is missing from the state.

@rbouckaert
Copy link
Member

@rbouckaert rbouckaert commented May 9, 2017

The up-down operator is cloned from the catch-all generic up-down operator, but that should not happen. This can be prevented somewhat inelegantly by adding in a connector rule to disconnect any accidentally cloned up-down operator.

@rbouckaert rbouckaert closed this in fdf4645 May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.