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

Fix feptasks.minimize()'s minimisation_steps argument #1086

Open
zhang-ivy opened this issue Aug 18, 2022 · 1 comment · May be fixed by #1141
Open

Fix feptasks.minimize()'s minimisation_steps argument #1086

zhang-ivy opened this issue Aug 18, 2022 · 1 comment · May be fixed by #1141
Assignees

Comments

@zhang-ivy
Copy link
Contributor

zhang-ivy commented Aug 18, 2022

minimisation_steps, an argument to feptasks.minimize() , currently matches the openmm LocalEnergyMinimizer.minimize() argument maxIterations in that when its equal to 0, it will run as many steps of minimization as needed, not zero steps.

minimisation_steps should work like this instead:

  • None should be interpreted to run until tolerance is reached
  • 0 should be interpreted to run 0 steps

See thread: #1065 (comment)

related: #1083

@ijpulidos
Copy link
Contributor

Even if this is a minor change, this is an API breaking one. I think we should leave it to the next milestone release, where many API breaking changes will happen. We also need a docstring for the HybridCompatibilityMixin.setup method, I'll open a new issue for that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants