You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice that since commit 73c5c8f (which is in 2.1.0 but not in 2.0.x) masses are taken into account by PLUMED only at the first step. I suspect that the masses passed after the first step are correct. This could mean that:
In PLUMED 2.0 masses were wrong only at the first step
Since PLUMED 2.1 masses are wrong during the whole simulation.
Perhaps that's why we did not notice the problem.
The text was updated successfully, but these errors were encountered:
As discussed here it is possible to avoid re-patching and re-compiling namd just by adding in the input file something like
DUMPATOMS ATOMS=1-10000 STRIDE=5000000 FILE=test.xyz
Here 10000 is the number of atoms of the system and 500000 is larger than the number of simulation steps.
This however does not fix the problem on charges.
This is related to the closed issue #162
I think that with standard usage of PLUMED all the actions should be
active at step zero, and so all the masses and charges should be requested
to codes like NAMD or OPENMM. Anyway,this fix will double check for it
adding an overhead only at the first simulation step.
See this thread:
https://groups.google.com/d/msgid/plumed-users/07f2a653-af03-42f6-905a-04c66da0679e%40googlegroups.com
Notice that since commit 73c5c8f (which is in 2.1.0 but not in 2.0.x) masses are taken into account by PLUMED only at the first step. I suspect that the masses passed after the first step are correct. This could mean that:
Perhaps that's why we did not notice the problem.
The text was updated successfully, but these errors were encountered: