I have met similar problem before. The distance calculated by g_dist is
different from that calculated by grommp, especially when the actual
distance between the two groups is very small. As the actual distance
becomes larger, the difference of the distance from the two commands becomes
smaller. In addition, in my case,
when using larger box size, the difference gets smaller. I don't know why, but
you may try to use
larger box size to minimize the difference. I am also curious of what
is the reason.
-- Jianguo
- Original Message -
From: Steinbrecher, Thomas (IPC) thomas.steinbrec...@kit.edu
To: gmx-users@gromacs.org gmx-users@gromacs.org
Cc:
Sent: Friday, 31 August 2012, 19:45
Subject: [gmx-users] Umbrella Sampling Pull code Problem
Dear Gromacs users,
I have encountered a strange problem when trying to set up umbrella sampling
simulations using gromacs 4.5.3.
My system contains two groups with a COM distance of 1.95 nm (all distances
measured by g_dist).
Trying to set up the first US window, I use the following pull code, together
with typical mdp parameters from the Gromacs US tutorial:
; pull options
pull = umbrella
pull_geometry = distance
pull_dim = Y Y Y
pull_start = yes
pull_init1 = 0.00
pull_nstxout = 1
pull_nstfout = 0
pull_group0 = Protein
pull_group1 = OHM
pull_rate1 = 0.0
pull_k1 = 1
this results in a simulation in which the group distance remains close to
1.95nm, as expected.
However, when I make the following two changes in my input file:
pull_start = no
pull_init1 = 1.95
which should (?) amount to an equivalent setup, a very different trajectory
results in which the COM distance quickly increases to 2.7 nm and then appears
to be restrained there. (Visualization confirms, in the first case, the groups
remain in their starting conformation, in the second one, they are pushed
appart)
Interestingly, the grompp output contains the following lines:
Pull group natoms pbc atom distance at start reference at t=0
0 994 497
1 2 46347 1.224 1.950
in this case. Apparently, grompp (and mdrun thereafter) calculates the group
COM distance differently from g_dist! I think this is not a PBC issue, every
atomic distance within both groups is smaller than half the box size and the
pbcatoms are close together. However, when I set pbcatom0 to various atom
numbers, different 'distance at start' values are obtained, but never the
correct COM distance. The two groups do not have overlapping atoms. I am sure I
used the same group indexes for pulling and distance measurements.
This behaviour is so visibly wrong that I cannot believe this is a bug and
rather think I am doing something incorrect. A search of the list revealed a
somewhat similar report by Gavin Melaugh in 2011 which did not resolve the
issue.
Any ideas on what might be the problem here?
I am willing to send around files to reproduce the problem of course.
Thomas
Dr. Thomas Steinbrecher
Institut für Physikalische Chemie, KIT
Kaiserstr. 12, 76131 Karlsruhe--
gmx-users mailing list gmx-users@gromacs.org
http://lists.gromacs.org/mailman/listinfo/gmx-users
* Please search the archive at
http://www.gromacs.org/Support/Mailing_Lists/Search before posting!
* Please don't post (un)subscribe requests to the list. Use the
www interface or send it to gmx-users-requ...@gromacs.org.
* Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
--
gmx-users mailing listgmx-users@gromacs.org
http://lists.gromacs.org/mailman/listinfo/gmx-users
* Please search the archive at
http://www.gromacs.org/Support/Mailing_Lists/Search before posting!
* Please don't post (un)subscribe requests to the list. Use the
www interface or send it to gmx-users-requ...@gromacs.org.
* Can't post? Read http://www.gromacs.org/Support/Mailing_Lists