Thanks so much, Chris. I will check wiki. <br>-Xianghong Qi<br><br><div class="gmail_quote">On Fri, Nov 7, 2008 at 10:44 AM, <span dir="ltr"><<a href="mailto:chris.neale@utoronto.ca">chris.neale@utoronto.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We have experienced this with NFS delay problems if you try to access the fie before it is completely written. On our most frustrating server, it can take up to an hour for the .xtc to be written in rare cases. For us, the biggest problem is when the .trr and .edr are completely written but the .xtc is not. Therefore one may not notice for many days and end up unable to make a nice movie to show your colleagues. To combat this, I developed an automated checkpointing script that you can find in the beginners->checkpointing jobs section of the gromacs wiki.<br>
<br>
Chris.<div class="Ih2E3d"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
xianghong qi wrote:<br>
<br>
Hello, everyone:<br>
<br>
when I run simulation, I got incomplete .xtc file, incomplete<br>
.trr file, but I have a complete log file. Then I use this<br>
incomplete to create input file for mdrun, I got the reasonable<br>
size of .tpr file.<br>
<br>
<br>
I wouldn't trust that .tpr file to contain what you think it does<br>
(size doesn't matter), at least in terms of the starting time. It<br>
will take the last frame as input, whatever it may be in the .trr file.<br>
<br>
<br>
I am confused what happed there. Does anyone has some idea about<br>
this?<br>
<br>
<br>
Probably a hardware blip caused the last frame(s) to not be written.<br>
I've had that happen before.<br>
<br>
<br>
actually, when I rerun my simulation, I got the complete .xtc<br>
file . I don't know why.<br>
<br>
<br>
Probably because the blip didn't happen again :)<br>
<br>
-Justin<br>
</blockquote>
<br></div><div class="Ih2E3d">
_______________________________________________<br>
gmx-users mailing list <a href="mailto:gmx-users@gromacs.org" target="_blank">gmx-users@gromacs.org</a><br>
</div><div class="Ih2E3d"><a href="http://www.gromacs.org/mailman/listinfo/gmx-users" target="_blank">http://www.gromacs.org/mailman/listinfo/gmx-users</a><br>
Please search the archive at <a href="http://www.gromacs.org/search" target="_blank">http://www.gromacs.org/search</a> before posting!<br></div>
Please don't post (un)subscribe requests to the list. Use thewww interface or send it to <a href="mailto:gmx-users-request@gromacs.org" target="_blank">gmx-users-request@gromacs.org</a>.<div><div></div><div class="Wj3C7c">
<br>
Can't post? Read <a href="http://www.gromacs.org/mailing_lists/users.php" target="_blank">http://www.gromacs.org/mailing_lists/users.php</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Some people make the world more special just by being in it.<br>