10 Common Molecular Dynamics Simulation Mistakes (And How to Avoid Every One)
Most failed MD simulations don’t fail with an obvious error message. They run to completion, produce a plausible-looking trajectory, and return results you might trust — until someone more experienced looks at your methods. These are the ten mistakes that appear most often in troubleshooting requests, reviewer comments, and retracted computational papers.
Periodic boundary conditions require the simulation box to be large enough that the protein never comes within interaction distance of its own periodic image. When the minimum distance between the protein and the box edge is smaller than the non-bonded cutoff (typically 1.0–1.2 nm), the protein effectively interacts with itself — an unphysical artifact that corrupts electrostatics, introduces false forces, and produces meaningless dynamics.
This is especially problematic for elongated proteins, flexible proteins that sample extended conformations during the simulation, and any system that undergoes significant conformational change. A box that was large enough at the start may become too small after 100 ns if the protein extends.
gmx editconf -d 1.0. For flexible proteins or long simulations, use 1.2 nm. Monitor the minimum image distance throughout the simulation with gmx mindist -pi — if it drops below your non-bonded cutoff at any point, the simulation is compromised.
The most common source of non-reproducible MD results. A system that hasn’t equilibrated is not representative of physiological conditions — temperature, pressure, and density are still drifting, and the protein may be in a metastable state far from its true equilibrium structure. Running production MD from a poorly equilibrated system means collecting data from an artifact rather than a real simulation.
The telltale sign: RMSD that rises steadily throughout what you’re calling the “production” phase. If RMSD hasn’t plateaued, the system hasn’t equilibrated — regardless of how long the equilibration phases nominally ran.
Particle Mesh Ewald (PME) — the standard long-range electrostatics method — requires the simulation box to be charge-neutral. A system with a non-zero net charge generates a divergent electrostatic energy under PBC that is handled by adding a uniform background charge, introducing a systematic error in the electrostatic calculation. The simulation runs and produces no error message, but all electrostatic energies are shifted by an unquantified constant.
This affects binding free energies, protein-ligand electrostatic interactions, and ion binding. It is especially problematic when the charged species is the ligand — a charged ligand in an uncorrected system will have spurious electrostatic interactions with the background charge.
gmx genion -neutral to add counterions and neutralize the system before simulation. Verify with grep "qtot" topol.top | tail -1 — the total charge must be zero. For ligands with a net charge, confirm the formal charge is correctly assigned in the ligand parameterization step and that the corresponding counterion is added.
Every biomolecular force field is parameterized against a specific water model. The protein parameters and water parameters are interdependent — they were fitted together to reproduce experimental observables including protein-water interactions, hydration free energies, and structural properties. Using a mismatched combination (CHARMM36 protein with TIP4P water, for example) introduces systematic errors in protein-water interactions that propagate into every property you measure.
pdb2gmx prompt when you choose your force field.
Protein force fields cover the 20 amino acids. They say nothing about arbitrary drug molecules. Using protein-derived atom types for a ligand, mixing GAFF2 ligand parameters with CHARMM36 protein parameters, or using poorly validated ACPYPE output without checking the atom type assignments all produce physically wrong interactions between the ligand and protein. The simulation runs, but the binding affinity, ligand dynamics, and protein-ligand contacts are all artifacts.
The standard 2 femtosecond timestep is safe when X-H bonds are constrained with LINCS or SHAKE. Without these constraints, the fastest atomic motions (X-H bond vibrations, ~10 fs period) require a timestep of 1 fs or smaller. Using 2 fs without hydrogen constraints can cause numerical instability that either crashes the simulation with a Stepsize too small error or, more insidiously, produces a trajectory that looks normal but has accumulated integration errors.
The opposite problem also exists: some researchers use very long timesteps (4–5 fs with virtual sites) without properly validating that structural properties are preserved. A timestep that’s too long for the system’s fastest degrees of freedom produces systematic errors that don’t announce themselves.
constraints = h-bonds in your MDP file when running at 2 fs. If you want to use a 4 fs timestep for performance, also constrain heavy-atom bonds (constraints = all-bonds) and consider using virtual sites for aromatic rings. After any change to timestep, run a short NVT simulation and check that total energy is conserved and temperature is stable.
The Berendsen thermostat and barostat equilibrate temperature and pressure quickly and stably — which is why they’re appropriate for equilibration. But they do not produce a correct thermodynamic ensemble: they suppress the natural fluctuations that define the canonical (NVT) or isothermal-isobaric (NPT) ensemble. Using Berendsen for production MD gives the wrong heat capacity, wrong compressibility, wrong free energies, and potentially wrong conformational populations. The simulation looks fine; the thermodynamics are wrong.
tcoupl = Nose-Hoover and pcoupl = Parrinello-Rahman. This is one of the most common errors in published MD papers and increasingly flagged by reviewers.
Periodic boundary conditions cause atoms to appear to teleport across the box boundary in the raw trajectory. This is not a physical artifact — it’s a coordinate wrapping convention. But it causes real problems when you run analysis on the raw trajectory: RMSD calculations give wrong values when atoms jump across boundaries, hydrogen bond distances appear impossibly large, and visualization shows a fragmented protein. The simulation is fine; the analysis is wrong.
gmx trjconv -pbc whole followed by gmx trjconv -center -pbc mol -ur compact before any analysis or visualization. Make this the first step after every simulation — before RMSD, before RMSF, before hydrogen bond analysis, before loading into VMD or PyMOL.
In NVT simulations with no thermostat coupling (or very weak coupling), total energy should be approximately conserved over time. Systematic energy drift — the total energy rising or falling steadily throughout the simulation — indicates a problem with the integrator, timestep, or force field parameters. It’s a diagnostic signal that most researchers never check, leaving subtle simulation problems undetected.
Energy drift is measured in kJ/mol/atom/ns. A drift rate below 0.01 kJ/mol/atom/ns is excellent. Above 0.1 suggests a problem worth investigating.
tcoupl = no (no thermostat) and check total energy conservation with echo "Total-Energy" | gmx energy -f nve.edr -o nve_energy.xvg. If energy is not conserved, reduce the timestep, increase the LINCS order, or check for poorly parameterized atoms in your system.
A 100 ns simulation that samples a local energy minimum looks identical to a 100 ns simulation that has genuinely explored the relevant conformational space — unless you check convergence. Conclusions drawn from unconverged simulations are simply observations of where the system happened to be, not statements about equilibrium properties. This is the most common way MD studies overstate their confidence in results.
Common convergence checks include: comparing RMSF profiles from the first and second halves of the trajectory (they should be similar), checking whether RMSD has genuinely plateaued or is still slowly rising, and running multiple independent replicas with different initial velocities to confirm key observations are reproducible.
Quick reference: all 10 mistakes at a glance
| Mistake | Severity | Core fix |
|---|---|---|
| Box too small | Critical | ≥ 1.0 nm edge distance; monitor with gmx mindist -pi |
| Insufficient equilibration | Critical | Check RMSD plateau; discard non-equilibrated frames |
| Non-zero system charge | Critical | gmx genion -neutral; verify qtot = 0 in topology |
| Mismatched FF + water model | Critical | Use recommended pairs: AMBER+TIP3P, CHARMM36+TIP3P |
| Wrong ligand parameters | Critical | Match GAFF2 to AMBER or CGenFF to CHARMM36 |
| Timestep too large | High | Use constraints = h-bonds with 2 fs timestep |
| Berendsen in production | High | Switch to Nosé-Hoover + Parrinello-Rahman for production |
| Raw trajectory analysis | High | Always run gmx trjconv -pbc whole then -center first |
| No energy conservation check | Medium | Run short NVE test; drift < 0.01 kJ/mol/atom/ns |
| No convergence check | Medium | Compare first and second half RMSF; run 2+ replicas |
The one-paragraph version
MD simulation mistakes are dangerous precisely because most of them are silent — the simulation runs, produces numbers, and returns results that look reasonable. The five critical mistakes (box size, equilibration, system charge, force field mismatch, ligand parameters) can each independently invalidate an entire study. Build a preparation checklist, run convergence checks on every trajectory, and verify the basics before trusting any result. The researchers who catch these mistakes in their own work before publication are the ones whose reviewers don’t catch them afterwards.