In my case nstfout = nstvout = 5000 (otherwise the file would be huge). I am only interested in the velocities, not in the veloc.pdb. It is possible to get it without the coordinates?
No, that’s what I tried before and got the error (see the first post). In my case nstxout=5000. I tried the -ov option and works, but the file is huge and messy, since it reports the velocity for each particle at each frame.
I found some time to have a closer look at the source code - it was written overlooking the possiblity that one might have only velocities and forces on hand, but not the coordinates. I was trying to re-write the tool, but could not do a quick-fix and it’s part of future refactoring efforts to provide tools that don’t have that type of issue (the code of gmx traj is at least 17 years old).
Does using gmx trajectory -seltype res_com help to get averaged numbers per residue? I did not try myself, but it might be an easier way forward…
Good - I did not think of gmx msd. I’m tagging @pbauer as this is closely related to the work he had planned (as far as I know) on converting and extracting information from trajectories.