|
Reducing Trajectory Storage VolumeTable of contentsNo headersThis advice also pertains to cases where analysis tools crash (or are too slow) because you are running out of (real) memory. First, consider whether you are producing more output than you need to store. Look at the .mdp file options for output frequency of positions ( You don't want data every frame, because the frames are strongly correlated with their neighbours. If you're never going to do analysis on the solvent coordinates, there's no need to save them - and normally they greatly outnumber your solute of interest. So, if you only want position data for your solute for your later analysis, then outputting only that group to an .xtc file ( With GROMACS 3.x you normally only want a full frame of positions and velocities in your .trr file with frequency with which you might ever want to do an exact restart (and make sure your energy output frequency ( With GROMACS 4.x the need for planning for positions, velocities and energies for restarts mentioned above is superseded by the checkpointing mechanism. Note that you can also use trjconv and eneconv to reduce your output frequency, change file format and select groups after doing the simulation too, but most of these decisions are best made (correctly!) before the simulation. |