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

[openforcefields] 1.2.0 #1037

Merged
merged 1 commit into from
Jun 1, 2020
Merged

[openforcefields] 1.2.0 #1037

merged 1 commit into from
Jun 1, 2020

Conversation

j-wags
Copy link
Contributor

@j-wags j-wags commented Jun 1, 2020

No description provided.

@jchodera
Copy link
Member

jchodera commented Jun 1, 2020

@j-wags: Any chance this has a mechanism for programmatically identifying which force fields are installed by this repo? I'd love to not have to manually update https://github.com/openmm/openmmforcefields every time

@j-wags
Copy link
Contributor Author

j-wags commented Jun 1, 2020

Not yet -- This is tracked in openforcefield/openff-toolkit#477

If you need a short-term workaround, the following test function should be able to help: https://github.com/openforcefield/openforcefields/blob/master/openforcefields/tests/test_openforcefields.py#L19-L26

@j-wags j-wags merged commit 3035237 into master Jun 1, 2020
@j-wags j-wags deleted the openffs-120 branch June 1, 2020 21:52
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 this pull request may close these issues.

2 participants