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

SMIRNOFF: "No cutoff" vdW interactions not allowed #7

Closed
mattwthompson opened this issue Jun 16, 2021 · 3 comments
Closed

SMIRNOFF: "No cutoff" vdW interactions not allowed #7

mattwthompson opened this issue Jun 16, 2021 · 3 comments
Assignees
Labels

Comments

@mattwthompson
Copy link
Member

It would be useful for testing purposes (and possibly some gas-phase small molecule studies, I'm not sure) to allow for vdW interactions to not be truncated at all. This is dubious for most applications that people care about, since an "all-all" neighbor list is not tractable for anything but small configurations.

I don't know what other engines this is implemented in; I don't think GROMACS supports it. OpenMM implements openmm.NonbondedForce.NoCutoff.

@davidlmobley
Copy link

In GROMACS you would presumably just need to make the cutoff larger than the size of the molecule, so it's indirectly supported. And I agree with you that this would be useful.

@mrshirts
Copy link

In GROMACS you would presumably just need to make the cutoff larger than the size of the molecule, so it's indirectly supported. And I agree with you that this would be useful.

Yes, though you should also turn off periodic boundary conditions, or make them quite large just to be sure.

@mattwthompson
Copy link
Member Author

With OFF-EP 0008 #53 there is now a "no-cutoff" option that does what I believe it intended here in version 0.4 of the vdW section.

Note that the toolkit doesn't support it yet, but there should be an upcoming change to vdWHandler that does.

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.

3 participants