Hi,
As with another answer I gave earlier today, many tools don't have good
handling of time steps and particularly their differences, once there are a
lot of significant digits in the times recorded. You could try using gmx
tools from a double-precision build, but that might not help. The step
Hello
I fudged a restart on gromacs 2018 and am missing 195 femtoseconds from my
trajectory. This shouldn't matter because I only need a 10 picosecond
resolution trajectory. However, when I try to correct the timestep with
trjconv and -timestep it doesnt seem to have done anything.
*gmx trjconv
Hello
I fudged a restart on gromacs 2018 and am missing 195 femtoseconds from my
trajectory. This shouldn't matter because I only need a 10 picosecond
resolution trajectory. However, when I try to correct the timestep with
trjconv and -timestep it doesnt seem to have done anything.
*gmx trjconv
