-
Notifications
You must be signed in to change notification settings - Fork 50
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
test_openmm_dihedral
failing
#879
Comments
Looks like it is passing fine on master https://github.com/choderalab/perses/actions/runs/1356975445 It isn't failing on all the tests so I will re-run it as well |
Yes, I agree with @mikemhenry , it might just be some weird behavior from the CI environment or something like that. Because I cannot reproduce it locally after running it several times. I get the exact same behavior for tests before and after the changes. |
That run was from much earlier in the day. You can see that the test is failing on master now too: Could one of you dig into what might be wrong with the CI environment? |
@zhang-ivy This is very strange, that number being used in the failed assertion is exactly 2𝝅 🤔 |
Okay, so clearly we are getting positve values for the |
Something weird is going on, looking at the last 2 nights of CI runs: https://github.com/choderalab/perses/actions/runs/1365813609 We are getting this error, but not consistently across python versions or openmm versions. So we need to dig into these tests and see if there is a source of randomness somewhere. I'm going to tag this into our current milestone so we can talk about it at our meeting today. |
The test is sensitive to tiny numerical errors, and should be changed from assert np.linalg.norm(openmm_phi - phi) < TORSION_TOLERANCE, msg to # Compute absolute error across periodic boundary
delta = abs(openmm_phi - phi)
error = min(delta, 2*np.pi-delta)
assert error < TORSION_TOLERANCE, msg |
It seems like this test is failing all of a sudden, but I'm not sure why.
@mikemhenry @ijpulidos : could you investigate why?
I'm not sure if this is only happening in #860 or not, but the tests were passing fine for commit 4b72d38.
https://github.com/choderalab/perses/pull/860/checks?check_run_id=3942799861
The text was updated successfully, but these errors were encountered: