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

XML is incorrect if data clamping not in the sink of graphical model #164

Open
zjzxiaohei opened this issue Oct 22, 2024 · 1 comment
Open
Labels
critical change the bug fix or new feature will significant change the code enhancement New feature or request

Comments

@zjzxiaohei
Copy link
Collaborator

If data clamping is not in the sink of the graphical model, a new data which is not clamped will be generated in the xml file. And the new one will be used in the xml file.

walterxie added a commit that referenced this issue Oct 22, 2024
@walterxie walterxie added enhancement New feature or request critical change the bug fix or new feature will significant change the code labels Oct 22, 2024
@walterxie
Copy link
Collaborator

If data clamping, the simulated alignment LPhy value will not be processed by ValueToBeast. So, there is no beast object created for the simulated alignment. Then, use getBEASTObject(alignmentValue.getId()), because

BEASTInterface alignmentParam = context.getBEASTObject(alignmentValue);

alignmentParam will be null.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical change the bug fix or new feature will significant change the code enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants