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

adapt FEP tests to not trigger GROMACS exclusion/rlist limitation #175

Closed
orbeckst opened this issue Jul 31, 2021 · 0 comments · Fixed by #249
Closed

adapt FEP tests to not trigger GROMACS exclusion/rlist limitation #175

orbeckst opened this issue Jul 31, 2021 · 0 comments · Fixed by #249
Labels

Comments

@orbeckst
Copy link
Member

As seen in PR #173 (#173 (comment)) we can occasionally fail a FEP MD test with GROMACS 2021 because the solute may extend beyond rlist. Tests should be written (larger rlist) to always pass.

orbeckst added a commit that referenced this issue Jun 29, 2023
- close #175
- use better error handling in runMD_or_exit to check if we triggered the
  non-bonded interactions beyond cutoff issue and if so, pass with xfail
orbeckst added a commit that referenced this issue Jun 29, 2023
- add new kwarg exit_on_error=True|False to run runMD_or_exit() to only raise
  exceptions instead of calling sys.exit(); default is old behavior (True)
- added tests for runMD_or_exit() failure modes
- use better error handling in runMD_or_exit to check if we triggered the
  non-bonded interactions beyond cutoff issue and if so, pass with xfail
- close #175
orbeckst added a commit that referenced this issue Jun 30, 2023
- add new kwarg exit_on_error=True|False to run runMD_or_exit() to only raise
  exceptions instead of calling sys.exit(); default is old behavior (True)
- added tests for runMD_or_exit() failure modes
- use better error handling in runMD_or_exit to check if we triggered the
  non-bonded interactions beyond cutoff issue and if so, pass with xfail
- close #175
orbeckst added a commit that referenced this issue Jun 30, 2023
- add new kwarg exit_on_error=True|False to run runMD_or_exit() to only raise
  exceptions instead of calling sys.exit(); default is old behavior (True)
- added tests for runMD_or_exit() failure modes
- use better error handling in runMD_or_exit to check if we triggered the
  non-bonded interactions beyond cutoff issue and if so, pass with xfail
- close #175
@orbeckst orbeckst linked a pull request Jun 30, 2023 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant