GMX-CHECK(1)

πŸ’– GMX-CHECK(1) β€” the gmx check page, bestie edition πŸ’–

okay so this is GMX-CHECK(1), one of the GROMACS manual pages, and she is literally the friend who looks at your files and tells you the truth. sit down, grab a matcha, we're doing this. πŸ“


✨ NAME ✨

gmx-check β€” check and compare files 🫢


🌈 SYNOPSIS 🌈

gmx check [-f [<.xtc/.trr/...>]] [-f2 [<.xtc/.trr/...>]] [-s1 [<.tpr>]]
          [-s2 [<.tpr>]] [-c [<.tpr/.gro/...>]] [-e [<.edr>]]
          [-e2 [<.edr>]] [-n [<.ndx>]] [-m [<.tex>]] [-vdwfac <real>]
          [-bonlo <real>] [-bonhi <real>] [-[no]rmsd] [-tol <real>]
          [-abstol <real>] [-[no]ab] [-lastener <string>]

πŸ’… DESCRIPTION πŸ’…

ngl, gmx check is the girl who reads your files and spills all the tea. she reads a trajectory (.tng, .trr or .xtc), an energy file (.edr), or an index file (.ndx), and prints out genuinely useful info about them. periodt. ✨

the -c option is doing the most (affectionate) β€” she checks whether coordinates, velocities and box are present in the file, checks for close contacts (smaller than -vdwfac and not bonded, i.e. not between -bonlo and -bonhi, all relative to the sum of both Van der Waals radii), and checks for atoms outside the box (these may occur often and are no problem, so don't panic bestie 😭). and if velocities are present, she'll calculate an estimated temperature from them. it's giving physics.

if an index file is given, its contents will be summarized. cute.

if you hand her both a trajectory and a .tpr file (with -s1), she will check whether the bond lengths defined in the tpr file are indeed correct in the trajectory. if they're not, you may have non-matching files due to e.g. deshuffling or due to problems with virtual sites. with these flags, gmx check provides a quick check for such problems. so like, a vibe check for your topology. πŸ‘‘

the program can compare two run input (.tpr) files when both -s1 and -s2 are supplied. when comparing run input files this way, the default relative tolerance is reduced to 0.000001 and the absolute tolerance set to zero, to find any differences not due to minor compiler optimization differences β€” although you can of course still set any other tolerances through the options. similarly a pair of trajectory files can be compared (using the -f2 option), or a pair of energy files (using the -e2 option). twin energy files? compared. iconic.

for free energy simulations, the A and B state topology from one run input file can be compared with options -s1 and -ab. slay. πŸ’–


πŸŽ€ OPTIONS πŸŽ€

🌸 options to specify input files 🌸

  • -f [<.xtc/.trr/...>] (traj.xtc) (Optional) β€” Trajectory: xtc trr cpt gro g96 pdb tng h5md
  • -f2 [<.xtc/.trr/...>] (traj.xtc) (Optional) β€” Trajectory: xtc trr cpt gro g96 pdb tng h5md
  • -s1 [<.tpr>] (top1.tpr) (Optional) β€” Portable xdr run input file
  • -s2 [<.tpr>] (top2.tpr) (Optional) β€” Portable xdr run input file
  • -c [<.tpr/.gro/...>] (topol.tpr) (Optional) β€” Structure+mass(db): tpr gro g96 pdb brk ent
  • -e [<.edr>] (ener.edr) (Optional) β€” Energy file
  • -e2 [<.edr>] (ener2.edr) (Optional) β€” Energy file
  • -n [<.ndx>] (index.ndx) (Optional) β€” Index file

🌼 options to specify output files 🌼

  • -m [<.tex>] (doc.tex) (Optional) β€” LaTeX file

⭐ other options ⭐

  • -vdwfac <real> (0.8) β€” Fraction of sum of VdW radii used as warning cutoff
  • -bonlo <real> (0.4) β€” Min. fract. of sum of VdW radii for bonded atoms
  • -bonhi <real> (0.7) β€” Max. fract. of sum of VdW radii for bonded atoms
  • -[no]rmsd (no) β€” Print RMSD for x, v and f
  • -tol <real> (0.001) β€” Relative tolerance for comparing real values, defined as 2*(a-b)/(|a|+|b|)
  • -abstol <real> (0.001) β€” Absolute tolerance, useful when sums are close to zero
  • -[no]ab (no) β€” Compare the A and B topology from one file
  • -lastener <string> β€” Last energy term to compare (if not given all are tested). It makes sense to go up until the Pressure.

πŸ‘€ SEE ALSO πŸ‘€

the original has a lil line-break hyphen thing in that URL (<‐ at the end of the line) because man pages do that whole hyphenation vibe β€” the link itself is the gromacs website, ok bestie? πŸ’œ

2026, GROMACS development team


and that's the whole page, no notes. this is version 2026.4, dated Oct 02, 2026, from the GROMACS crew β€” GMX-CHECK(1) and she ate, fr fr. go check ur files, ily, bye πŸ¦‹βœ¨πŸ’–

πŸ“¦ where this page comes from