<html>
<head>
</head>
<body>
Hi, David.<br>
<br>
I am not sure what you mean. On our cluster, my home directory with gmx data
and the trr > 2.2 GB is already NFS mounted on all nodes. What would I
do next?<br>
<br>
As I mentioned earlier, the command:<br>
<br>
<pre wrap="">tpbconv -s full.tpr -f full.trr -o full_extend_1.tpr -extend 10000</pre>
<br>
does not work, because the full.trr "cannot be found". Peter Zoon suggested
compressing trr into xtc format, but that will not work, because you need
velocity information to continue or extend a run. <br>
<br>
Would it be terribly wrong if I simply started a new 10-ns simulation with
the final coordinates from the first trr:<br>
<br>
<pre wrap="">grompp -f full.mdp -c MT1_popc_postfull.gro -n index.ndx -p MT1_popc.top -o full_extend.tpr</pre>
i.e., if I disregarded the velocities?<br>
<br>
What I am trying to do is collect the full MD data for my receptor in the
POPC bilayer. <br>
<br>
Thank you for your clarifications.<br>
Martina<br>
<br>
<br>
David wrote:<br>
<blockquote type="cite" cite="mid:1080376011.10068.9.camel@h15n2fls34o1123.telia.com">
<pre wrap="">On Sat, 2004-03-27 at 10:10, Martina Bertsch, PhD wrote:<br></pre>
<blockquote type="cite">
<pre wrap="">If I understand correctly, trjconv converts the trr file to xtc format, <br>which does *not* contain velocities or forces and thus saves space. <br>Manuals specifically instruct us not to remove the trr file if a run has <br>to be restarted.<br><br></pre>
</blockquote>
<pre wrap=""><!----><br>You need the trr file. This is a linux problem that has been discussed<br>many times on the list. Apparently we need a FAQ entry. A possible<br>solution is to NFS mount the disk your trajectory is on and do it over<br>NFS. With a decently modern Linux it should not be a problem (we run<br>Redhat 8 and higher):<br><br>[rembrandt:octanol/XTC] % ls -l simE2.xtc<br>-rw-r--r-- 1 spoel xray 16029520596 Nov 15 21:15 simE2.xtc<br><br><br><br></pre>
<blockquote type="cite">
<pre wrap="">I don't think I would get a true continuation run without velocities. Am <br>I correct?<br><br>Martina <br><br>Peter Zoon wrote:<br><br></pre>
<blockquote type="cite">
<pre wrap="">Hi!<br>with trjconv you can make full.trr smaller and thus overcome the <br>problem of file> 2GB<br>Then you can use this newly made file to restart, with tpbconv.<br><br>Cheers<br>Peter<br><br>At 09:18 3/27/2004, you wrote:<br><br></pre>
<blockquote type="cite">
<pre wrap="">Greetings.<br><br>Our administrator had to install upgrades on the cluster, so I had to <br>stop my mdrun of a protein in a POPC bilayer, which was running <br>smoothly up until now (for 10 ns). To stop the run, I used the kill <br>-USR1 signal. The signal produced a gro file, named <br>"MT1_popc_postfull.gro", and the megaflops accounting report at the <br>end of the log file, as if it were the end of the run. However, the <br>run would have been continued for another 10 ns, if there had not <br>been any interruption.<br><br>When the upgrades were completed, I attempted to restart the run with <br>the following command:<br><br>tpbconv -s full.tpr -f full.trr -o full_extend_1.tpr -extend 10000<br><br>I also tried the following:<br><br>grompp -f full.mdp -t full.trr -c MT1_popc_postfull.gro -n index.ndx <br>-p MT1_popc.top -o full_extend.tpr<br><br>But in both cases, I received an error message:<br><br>File full.trr not found.<br><br>Of course, the file
is actually present and larger than 2.2 GB.<br><br>How do I continue/extend my mdrun? I could start a new 10 ns <br>simulation with the final coordinates from MT1_popc_postfull.gro, but <br>it would not be a true continuation run without the velocities from <br>the first part of the run, since I could not read the trr file.<br><br>Also, will I be able to analyze the trr trajectory that is larger <br>than 2 GB with g_rms, g_hbond etc, or will I have to convert it to <br>the xtc format?<br><br>Thank you.<br><br>Martina<br><br>_______________________________________________<br>gmx-users mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:gmx-users@gromacs.org">gmx-users@gromacs.org</a><br><a class="moz-txt-link-freetext" href="http://www.gromacs.org/mailman/listinfo/gmx-users">http://www.gromacs.org/mailman/listinfo/gmx-users</a><br>Please don't post (un)subscribe requests to the list. Use the www <br>interface or send it to <a class="moz-txt-link-abbreviated" href
="mailto:gmx-users-request@gromacs.org">gmx-users-request@gromacs.org</a>.<br></pre>
</blockquote>
<pre wrap=""><br><br>_______________________________________________<br>gmx-users mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:gmx-users@gromacs.org">gmx-users@gromacs.org</a><br><a class="moz-txt-link-freetext" href="http://www.gromacs.org/mailman/listinfo/gmx-users">http://www.gromacs.org/mailman/listinfo/gmx-users</a><br>Please don't post (un)subscribe requests to the list. Use the www <br>interface or send it to <a class="moz-txt-link-abbreviated" href="mailto:gmx-users-request@gromacs.org">gmx-users-request@gromacs.org</a>.<br><br><br></pre>
</blockquote>
<pre wrap=""><br>_______________________________________________<br>gmx-users mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:gmx-users@gromacs.org">gmx-users@gromacs.org</a><br><a class="moz-txt-link-freetext" href="http://www.gromacs.org/mailman/listinfo/gmx-users">http://www.gromacs.org/mailman/listinfo/gmx-users</a><br>Please don't post (un)subscribe requests to the list. Use the <br>www interface or send it to <a class="moz-txt-link-abbreviated" href="mailto:gmx-users-request@gromacs.org">gmx-users-request@gromacs.org</a>.<br></pre>
</blockquote>
</blockquote>
<br>
</body>
</html>