<p dir="ltr"><br>
On Jan 31, 2014 4:22 AM, "sryckbos" <<a href="mailto:sryckbos@stanford.edu">sryckbos@stanford.edu</a>> wrote:<br>
><br>
> trjconv doesn't seem to check whether the .ndx file you specify corresponds<br>
> at all with the .tpr and .xtc files you input. </p>
<p dir="ltr">Hi, </p>
<p dir="ltr">Thanks for the report. As Tsjerk said, the only metadata in .xtc is the number of atoms, so only if an index group references out of those bounds is there a clear error that can be caught. We are aware of these and other deficiencies in the file formats; one advantage of the TNG trajectory format available in the upcoming GROMACS 5.0 is that it has embedded molecule information, which broadens the scope for such sanity checks. These kinds of checks are not implemented yet, because the scope and historical implementation of trajectory-file handling in GROMACS is mind-boggling.</p>
<p dir="ltr">> I wrote a script that was<br>
> using trjconv to remove the waters from many of my trajectories on several<br>
> different systems. I made an .ndx file for each of them, system1.ndx and<br>
> system2.ndx, and planned to do something like this:<br>
><br>
> echo Protein_ligand1|trjconv -s system1.tpr -f system1.xtc -o<br>
> system1_dehyd.xtc -n system1.ndx<br>
><br>
> and, separately, do<br>
><br>
> echo Protein_ligand2|trjconv -s system2.tpr -f system2.xtc -o<br>
> system2_dehyd.xtc -n system2.ndx<br>
><br>
> Inadvertently, I forgot to change stuff in my second script, giving me a<br>
> command like this<br>
><br>
> echo Protein_ligand1|trjconv -s system2.tpr -f system2.xtc -o<br>
> system2_dehyd.xtc -n system1.ndx<br>
><br>
> Rather than flipping out and telling me that there isn't anything that<br>
> corresponds to Protein_ligand1 in system2.tpr or system2.xtc, however, it<br>
> gave me system2_dehyd.xtc as if nothing went wrong. When I pulled<br>
> coordinates from that xtc file, it just used the numbers that corresponded<br>
> to Protein_ligand1 in the system2 files without looking at what it was<br>
> actually pulling.</p>
<p dir="ltr">Indeed, but as the tool cannot parse the name of the index group, only if a group with that name was used in the .tpr could there be a basis for a warning. The best solution is to implement a command-line selection like</p>
<p dir="ltr">trjconv -s -f -o -select "Protein and Ligand1"</p>
<p dir="ltr">This kind of thing is available for a few tools in GROMACS 5.0, but more hands are needed to port the machinery to more tools. Contributions welcome!</p>
<p dir="ltr">That still won't prevent you from writing the wrong selection for the name of your -o file, though...</p>
<p dir="ltr">> Next I tried to break it. system1 has slightly more atoms than system2, and<br>
> so I figured if trjconv just ran out of atoms, it'd throw an error. Not<br>
> really. If I did this:<br>
><br>
> echo System|trjconv -s system2.tpr -f system2.xtc -o system2_dehyd.xtc -n<br>
> system1.ndx<br>
><br>
> All I got was:<br>
><br>
> Select a group: Selected 0: 'System'<br>
> Segmentation fault</p>
<p dir="ltr">Thanks, that is bad - enough information exists to give a sensible error message.</p>
<p dir="ltr">> Finally, I figured if there was no ndx file, I wouldn't get this problem.<br>
> Not so. If I did<br>
><br>
> echo System|trjconv -s system2.tpr -f system1.xtc -o test.xtc<br>
><br>
> This time, I did get the following error:<br>
><br>
> -------------------------------------------------------<br>
> Program trjconv, VERSION 4.6<br>
> Source code file:<br>
> /home/sryckbos/Downloads/gromacs-4.6/src/tools/gmx_trjconv.c, line: 1312<br>
><br>
> Fatal error:<br>
> Index[33820] 33821 is larger than the number of atoms in the<br>
> trajectory file (33820). There is a mismatch in the contents<br>
> of your -f, -s and/or -n files.<br>
> For more information and tips for troubleshooting, please check the GROMACS<br>
> website at <a href="http://www.gromacs.org/Documentation/Errors">http://www.gromacs.org/Documentation/Errors</a><br>
> -------------------------------------------------------</p>
<p dir="ltr">Good</p>
<p dir="ltr">> BUT, if I reversed it,<br>
><br>
> echo System|trjconv -s system1.tpr -f system2.xtc -o test2.xtc<br>
><br>
> There was no error, and I got test2.xtc out without any problems.</p>
<p dir="ltr">This "supports" the standard usage of .xtc to contain a subset of the .tpr atoms, as written from mdrun. But since it is a null operation, it should give an error. It doesn't do so because trjconv has too much functionality, which I am working on.</p>
<p dir="ltr">> This seems like a pretty major bug to me, and presumably this isn't<br>
> occurring because I'm not up to date (didn't see anything about it in any of<br>
> the release notes for the 4.6.x series, or on any of the mailing lists).<br>
> Has anyone else experienced or noticed this issue?</p>
<p dir="ltr">Yes you're sufficiently up to date. Whether a problem gets fixed basically depends on whether it annoys a developer enough to provoke them to fix it. Unfortunately experience mitigates making this kind of mistake, and this particular group of problems is too large for a new developer to fix!</p>
<p dir="ltr">Mark</p>
<p dir="ltr">> --<br>
> View this message in context: <a href="http://gromacs.5086.x6.nabble.com/trjconv-doesn-t-check-if-the-tpr-xtc-and-ndx-files-provided-match-tp5014178.html">http://gromacs.5086.x6.nabble.com/trjconv-doesn-t-check-if-the-tpr-xtc-and-ndx-files-provided-match-tp5014178.html</a><br>
> Sent from the GROMACS Developers Forum mailing list archive at Nabble.com.<br>
> --<br>
> Gromacs Developers mailing list<br>
><br>
> * Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
><br>
> * Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists">http://www.gromacs.org/Support/Mailing_Lists</a><br>
><br>
> * For (un)subscribe requests visit<br>
> <a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br>
</p>