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

Document how nonbonded methods get resolved #380

Closed
j-wags opened this issue Jul 12, 2019 · 0 comments · Fixed by #916
Closed

Document how nonbonded methods get resolved #380

j-wags opened this issue Jul 12, 2019 · 0 comments · Fixed by #916

Comments

@j-wags
Copy link
Member

j-wags commented Jul 12, 2019

Is your feature request related to a problem? Please describe.
@SimonBoothroyd asked how openMM nonbonded methods get selected based on user input. We had discussed this for a long time, and come up with a decision table, but it never made it into the documentation. The current decision table is recorded in the tests here:

nonbonded_resolution_matrix = [

Describe the solution you'd like
That table should be in the ReadTheDocs. The best place for it is probably the ForceField docstring.

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

Successfully merging a pull request may close this issue.

2 participants