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

Plumed 2.8.0 fails metadynamics unit test #83

Closed
danielhollas opened this issue Mar 4, 2022 · 1 comment · Fixed by #102
Closed

Plumed 2.8.0 fails metadynamics unit test #83

danielhollas opened this issue Mar 4, 2022 · 1 comment · Fixed by #102
Assignees

Comments

@danielhollas
Copy link
Contributor

https://github.com/PHOTOX/ABIN/runs/5409736811?check_suite_focus=true

Metadynamics forces produce non-negligible numerical difference in the unit test. We need to investigate if this is a possible bug in Plumed, or some change in interface or something else. There were apparently some changes in the Fortran interface in 2.8.0, perhaps some of them were not backwards compatible.

ERROR STOP *** Encountered 1 or more failures/errors during testing. ***

Error termination. Backtrace:
Time:         0.032 seconds
  
Failure
 in: 
test_plumed_suite.test_force_metad
  Location: 
[test_plumed.pf:320]
fx(1) changed
AssertEqual failure:
      Expected: <0.99991611203271580>
        Actual: <0.99991594977761633>
    Difference: <-0.16225509946732330E-006> (greater than tolerance of 0.0000000000000000)
@danielhollas
Copy link
Contributor Author

This is because Plumed started using stretched gaussians, which leads to numerical differences.

See this issue and the implementation. As a quick fix for our test suite, we can set env variable PLUMED_DP2CUTOFF_NOSTRETCH before the linking step.

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 a pull request may close this issue.

1 participant