-
Notifications
You must be signed in to change notification settings - Fork 189
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
core: thermostat: Removed heat_up/cool_down mechanism for Langevin ty… #3341
Conversation
Codecov Report
@@ Coverage Diff @@
## python #3341 +/- ##
=======================================
+ Coverage 86% 86% +<1%
=======================================
Files 525 538 +13
Lines 25005 25312 +307
=======================================
+ Hits 21507 21784 +277
- Misses 3498 3528 +30
Continue to review full report at Codecov.
|
why hast that been caught by any testcase? |
Because it was not tested. |
Shouldn't the DPD test for the velocity distribution fail if the noise magnitude is wrong? |
You have to trigger the heat_up/cool_down by forcing a recalculation of the initial foces, e.g., via
System.part[0].pos=system.part[0].pos
|
bors r+ |
3341: core: thermostat: Removed heat_up/cool_down mechanism for Langevin ty… r=KaiSzuttor a=fweik …pe thermostats The Langevin-type thermostats (excluding LB), had broken initial forces. They did still employ the heat_up/cool_down mechanism which is no longer correct with the philox rng. This is potentially a serious bug, because it makes the thermostat silently act with a different temperature than set for at least parts of the time steps. Co-authored-by: Florian Weik <fweik@icp.uni-stuttgart.de>
Build succeeded |
…pe thermostats
The Langevin-type thermostats (excluding LB), had broken initial forces.
They did still employ the heat_up/cool_down mechanism which is no longer
correct with the philox rng. This is potentially a serious bug, because it makes
the thermostat silently act with a different temperature than set for at least
parts of the time steps.