Fix GIST order calculation for water models with more than 3 points#788
Merged
drroe merged 6 commits intoAmber-MD:masterfrom Jan 9, 2020
Merged
Fix GIST order calculation for water models with more than 3 points#788drroe merged 6 commits intoAmber-MD:masterfrom
drroe merged 6 commits intoAmber-MD:masterfrom
Conversation
added 6 commits
January 9, 2020 10:48
Contributor
Author
|
The Jenkins failure is for the CUDA build but is framework=related, not code: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A simple but necessary fix. Adds tests for order calculations with tip4p and tip5p water models to catch any issues like this in the future. Should be merged before #787. Not incrementing the version number since #787 (which should be merged right after) already increments the minor version. #787 should be fully compatible with this PR.
@jokr91 I'll merge this before #787 just so the tests get in the tree, but I already checked that your new GPU code gives the right answers (which is awesome!). It's just the CPU code that had the issue.