How Long Should Molecular Dynamics Simulations Run? A Practical Guide

Jan 9, 2023·
Yassir Boulaamane
Yassir Boulaamane
· 5 min read

A protein–ligand simulation is long enough when the motion you care about has had time to happen, and the traces you are willing to trust have stopped drifting.

There is no single correct length. The ranges below are the ones that have proved useful for common questions. They are starting points. The trajectory, not the number you typed into the input file, tells you whether to stop.

Match the length to the event

Several windows have become usual for protein–ligand work, from published practice and from running these systems:

  • 50–100 nanoseconds. Often enough to judge initial binding stability, particularly with a small, rigid ligand and a relatively stable protein.
  • 100–200 nanoseconds. Room for ligand flexibility, side-chain reorganization, or early conformational change inside the pocket.
  • 200–500 nanoseconds. Slower events: partial unbinding, induced fit, or a shift at the domain level.
  • 500 nanoseconds to 1 microsecond, or longer. Long-timescale processes: allosteric communication, full ligand unbinding, or a global rearrangement of the protein.
Simulation length matched to the eventFour practical windows: 50 to 100 nanoseconds for pose stability, 100 to 200 for flexibility in the pocket, 200 to 500 for induced fit and partial unbinding, and 500 nanoseconds to 1 microsecond for allostery, full unbinding, and global rearrangement.Pick the window for the motion, not for the habit50–100 nsIs the pose still there?Rigid ligand, stable pocket100–200 nsLigand flex, side chainsEarly change inside the pocket200–500 nsInduced fit, domain shiftPartial unbinding500 ns–1 µsAllostery, full unbindingGlobal rearrangement. Or longer.
Figure 1. The four windows used in this note. A rigid ligand in a quiet pocket can be readable in the first. Unbinding and allostery sit in the last, and sometimes beyond it. The cards are the same size so they can be compared. The times are not.

These are guidelines. The required time moves with the system and with the question. A short run can be the right experiment when the question is whether a docked pose survives relaxation. It is the wrong experiment when the question is how the ligand leaves.

Convergence is the stopping rule

Convergence here means that the structural and energetic quantities you intend to interpret have settled. A long simulation that is still drifting does not become trustworthy because it is long. A short one that has plateaued on the observables you care about can be enough for that question.

Five checks cover the usual protein–ligand case.

  1. Root-mean-square deviation (RMSD). Deviation of the chosen atoms, often the protein backbone, from a reference over time. A plateau suggests that this part of the structure has stopped walking away from the reference. An RMSD that is still climbing means the rearrangement is not finished.
  2. Root-mean-square fluctuation (RMSF). Flexibility per residue across the run. Once the trajectory is stable, RMSF profiles from successive windows look alike. A window that redraws the profile is a sign you have not settled.
  3. Energy. Total, potential, and kinetic energy. A system at equilibrium should not show a long drift. Sharp, persistent swings are a sign the equilibration was not long enough, or that something in the setup is wrong.
  4. Secondary structure. For a folded protein, helices and sheets that keep their assignment are a useful stability check. Assignments that keep flipping after the start of the production run are a reason to extend it.
  5. Interaction fingerprints. Hydrogen bonds, salt bridges, stacking, and the other contacts you claim as the binding pose. A pose is hard to defend when those contacts appear and vanish from one slice of the trajectory to the next.
Five convergence checksBefore stopping a protein-ligand simulation, look at RMSD, RMSF, energy, secondary structure, and the persistence of protein-ligand contacts.Stop when these settle, not when the clock doesA climbing trace is a reason to continueRMSDplateauRMSFstablewindowsEnergyno longdriftSecondarystructureholdsContactspersist
Figure 2. Five traces that have to be read together. A flat RMSD with contacts that keep rearranging is not a stable pose. A quiet energy with a protein that is still unfolding its secondary structure is not a finished run.

An illustrative scenario

Imagine a complex whose RMSD rises over the first 50 nanoseconds while the pose settles, then levels off near 100 nanoseconds. Over that same later window the interaction fingerprint stops changing and the total energy no longer drifts. For a question about pose stability, extending the run may add little.

The opposite pattern is also common. The ligand keeps sliding in the pocket, or a domain keeps moving in one direction. That trajectory is asking for more time, or for an enhanced-sampling method aimed at the slow coordinate. Adding nanoseconds at random is a weaker response than naming the motion that has not converged.

What pushes the length up or down

  • Size and flexibility. A larger or more flexible protein has more conformational space to cross.
  • The ligand. Many rotatable bonds mean many poses. The dominant one may not be the pose you started from, and it may take longer to identify.
  • The question. Pose checking and a mechanism of unbinding are different experiments.
  • Replicates. Several independent runs often say more than one very long trajectory. A single run can look converged and still be stuck in the basin where it started.
  • The checks above. Decide in advance which observables would make you stop, and compute them before you interpret the pose.

Bottom line

For many protein–ligand questions about pose stability and interaction patterns, 50 to 200 nanoseconds is the window where those traces become readable. Unbinding, allosteric modulation, and large conformational change often need longer, sometimes past a microsecond.

Length is not a badge. A conclusion about a binding mode needs the traces that support it to have settled. If they have not, the honest result is that the simulation has not answered the question yet.