<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 15/07/2011 7:31 PM, Martin Kamp Jensen wrote:
<blockquote
cite="mid:CAFVEjokCXM=HjUWeVTAkpzwz6F02P-1hu2Jox=eoyiYTYwkkqw@mail.gmail.com"
type="cite"><span class="Apple-style-span" style="border-collapse:
collapse; font-family: arial,sans-serif; font-size: 13px;">Hello,
<div><br>
</div>
<div>I am trying to evaluate energy values of several
conformations using a (pseudo)trajectory. Currently, I am
concatenating GROMOS-96 files (.g96) and using that as a
trajectory. For some reason the second conformation in a
trajectory is ignored. So e.g. if I have three conformations
(1.g96, 2.g96, and 3.g96), then concatenate them into
1+2+3.g96, and then use the latter file as a trajectory, the
conformation of 2.g96 is ignored when using mdrun -rerun with
a suitable binary run file.</div>
<div><br>
</div>
<div>I have created an archive [1] with files demonstrating the
problem. Use the "run" script for a stepwise demonstration of
the problem: The output of mdrun shows that the last frame
processed is one less then expected for concatenated files.
Further, it is the second frame that is missing which can be
determined by looking at the energy values in the energy file
generated by mdrun.</div>
<div><br>
</div>
</span><span class="Apple-style-span" style="border-collapse:
collapse; font-family: arial,sans-serif; font-size: 13px;">I
have no clue what is going on here. I hope someone can provide
some insights. </span><span class="Apple-style-span"
style="border-collapse: collapse; font-family: arial,sans-serif;
font-size: 13px;">(The same approach seems to work fine with PDB
files instead of GROMOS-96 files, but there is less precision in
PDB files and because of some irrelevant details it is easier
for me to work with GROMOS-96 files at the moment.)</span><span
class="Apple-style-span" style="border-collapse: collapse;
font-family: arial,sans-serif; font-size: 13px;">
<div>
<br>
</div>
</span><span class="Apple-style-span" style="border-collapse:
collapse; font-family: arial,sans-serif; font-size: 13px;">[1] <a
moz-do-not-send="true"
href="http://dl.dropbox.com/u/2666968/GROMACS/missingframe.tar">http://dl.dropbox.com/u/2666968/GROMACS/missingframe.tar</a></span>
<div>
<font class="Apple-style-span" face="arial, sans-serif"><span
class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font><span class="Apple-style-span"
style="border-collapse: collapse; font-family:
arial,sans-serif; font-size: 13px;">
<div>
Thanks,</div>
<div>Martin.</div>
</span></div>
</blockquote>
<br>
That's a bug. Reading the .g96 file format as a trajectory uses some
dirty dirty non-thread-safe code, and the cleanup a few years ago to
make things thread-safe did that without preserving correct
functionality. I suggest you concatenate separate .g96 files using
trjcat into .trr format, and use rerun on that.<br>
<br>
Mark<br>
</body>
</html>