Hi Mark.<br><br><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> I think those three can become yes in a really easy way: some kind of
<br>> "state machine" would easily do the trick and "count" them properly.<br>Yes, but now you have to infer molecule changes from residue name<br>changes, which is doable, but messy.</blockquote><div>
<br>Forgot about this slice of the problem. You are right now, so, or a .ndx file, or .tpr files. ;) Or read both residue counting and molecule cou8nting from the .pdb file. ;)<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Only modifying editconf to print those in a adapted .pdb file, throw a<br>> file conversion and much disk space "wasted". Or I can learn exactly<br>> from editconf how to read it from .tpr or .top (I guess it takes from
<br>> these files the atomic charges when needed) and adapt into my codes.<br><br>The point of editconf is to feed your system *one* pdb structure with<br>atom names, charges and/or whatever - it would be easy to modify
<br>editconf to write masses in one column and charges in another. You rely<br>on the user to then supply a .xtc file that corresponds to that .pdb, in<br>the same way that most of the GROMACS analysis tools accept an .xtc and
<br>various subsets of the possible structure files. You don't convert your<br>.xtc to a .pdb trajectory, because that would be immensely wasteful, and<br>the static information of the names, masses and charges doesn't vary
<br>with time under the MD approximation.</blockquote><div><br>Ops, now I've got your idea! I was thinking too much about trjconv way of working instead of editconf one! Sorry!<br><br>On this way, yes, editconf becomes a really good idea, side-by-side with reading the .tpr one. But, of course, and easier to implement one.
<br><br>Thanks a lot for all information and for all your time. I'll start to look into the sources you mentioned before and try to properly find out how to deal with those problems properly. ;)<br><br>Thanks a lot again for all your time,
<br><br>Sincerally yours,<br><br>Jones <br></div></div><br>