From: P.-L. Chau (pc104_at_pasteur.fr)
Date: Wed May 25 2011 - 12:56:41 CDT
Thank you for your prompt reply.
> The coordinates used for the constraints are being overwritten by the
> bincoordinates file. You can see this because the BOUNDARY energy where
> constraints are reported is zero at restart. This only happens if the
> coordinates and consref filenames are the same, so you can work around
> the issue by giving the files different names (or make one a symlink to
> the other). I just checked in a fix that moves the bincoordinates read
> to after constraints reference coordinates have been copied.
I am new to NAMD so could I follow up with two questions, please? If you
do not mind, could I possibly start from the beginning?
If I run a simulation sim1 of a protein using files protein.pdb and
protein.psf, then sim1.conf should have two lines like these:
so that the coordinates used for starting the run is protein.pdb.
If I would like to restart from the end of sim1 to run sim2, then in the
sim2.conf file, I usually have a few lines like these:
Could I ask you if the line "coordinates protein.pdb" is necessary? If the
starting coordinates is already defined to be sim1.restart.coor, then why
do we need protein.pdb, please?
The second question pertains to the constraints. I put constraints on
using the following lines:
You wrote that I should NOT have "consref protein.pdb" and "coordinates
protein.pdb", is that right? So if I copy protein.pdb to protein_ref.pdb
and use the latter as the consref file, then would this "jump" disappear?
I am sorry if these questions sound idiotic, but I am a new user so I beg
you to bear with me. Thank you for your kind help and advice.
CNRS URA 2185
This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:57:11 CST