This lesson is still being designed and assembled (Pre-Alpha version)

Supplemental: Diagnosing Unstable Systems

Overview

Teaching: 0 min
Exercises: 0 min
Questions
  • FIXME

Objectives
  • This episode is still work-in-progress.

  • FIXME

It is not uncommon for Molecular Dynamics simulation to become unstable for various reasons, resulting certain numerical algorithms to break and the simulation to crash. This is often referred to as the simulation is “blowing up” and especially inexperienced users often have difficulties with dealing with this.

This section provides some tips about what can be checked and how one can proceed.

When does the crash occur?

flowchart LR subgraph minimization["Energy Minimization and Relaxation"] direction TB B1["Energy Minimization"] B1 --> B2["short NVT (possibly w/ position restraints)"] B2 --> B3["short NPT"] end subgraph equilibration["Equilibration"] direction TB C1["Equilibration MD"] end subgraph production["Production"] direction TB D1["Production MD and data collection"] end minimization ---> equilibration equilibration ---> production

During Energy Minimization

If the crash happens during energy minimization, then it is quite likely that there are atomic clashes that are so severe that the minimization cannot resolve. Note down the atom-number that has the largest force and use it as a start for your investigation.

Other possibilities are that there is an error in the topology or a severe error in the MD-parameters (e.g. are the cut-offs specified in the correct unit – Å vs nm).

When using GROMACS

When the GROMACS energy minimization is executed with the -v option, it will print information about which atom has the larges force (Fmax) acting on it. e.g.:

Steepest Descents:
   Tolerance (Fmax)   =  1.00000e+03
   Number of steps    =        50000
Step=    0, Dmax= 1.0e-02 nm, Epot= -4.52720e+05 Fmax= 2.48664e+05, atom= 710
Step=    1, Dmax= 1.0e-02 nm, Epot= -4.63759e+05 Fmax= 8.99042e+04, atom= 710
Step=    2, Dmax= 1.2e-02 nm, Epot= -4.79680e+05 Fmax= 2.77594e+04, atom= 1046
Step=    3, Dmax= 1.4e-02 nm, Epot= -5.00649e+05 Fmax= 9.51331e+03, atom= 24272
Step=    4, Dmax= 1.7e-02 nm, Epot= -5.21439e+05 Fmax= 9.13588e+03, atom= 710
Step=    5, Dmax= 2.1e-02 nm, Epot= -5.32010e+05 Fmax= 1.79030e+04, atom= 710

When using AMBER

FIXME

When using NAMD

FIXME

During initial NVT Simulation

FIXME: Is the Langevin thermostat also prone to fail during relaxation phase?

During initial NPT Simulation

FIXME

Using VMD to Inspect Atomic Clashes

If you have identified some atoms as “suspects” (e.g. atoms mentioned in LINCS, SHAKE or SETTLE warnings, or having very large forces during energy minimization), it can be helpful to visualize the vicinity around those “suspects” with a molecular viewer like VMD. The same strategy can also be applied with other molecular viewers.

  1. Open the initial coordinate file (starting structure) and the trajectory in VMD and advance to the timesteps closet to the crash.
    If your MD-package has saved coordinate files for the time-steps leading up to the crash, you can load these instead.

  2. Open the “Grahical Representations” window (Graphics > Representations…) and create a new representation: Create Rep..

  3. Select the “suspect” atom (e.g. serial = 710) and set it to style VDW so that it stands out.

  4. Create another representation (Create Rep.) in which you you select residues within a certain distance (e.g. between 5 and 10 Å). around the central atom and set a style (e.g. Lines or CPK). The selection command for selecting all residues that have atoms within 7 Å around atom number 710 is: same resid as (within 7 of serial = 710).

  5. Toggle off the original representation (selection “all”) by double-clicking on that line in the list. The result should look like this: select residues around central atom with VMD

  6. Set Mouse to “Pick” and open the “Graphics > Labels…” window, so that you can identify the atom/residue number of the offending atoms/molecules.

  7. If you are looking at a trajectory, you can also step one-by-one through a few adjacent frames to get a sense how the system has been evolving leading up to the crash. Is there an atom moving very fast and hitting a series of other atoms that were flagged by warnings?

  8. You may need to repeat this with several atoms that you have on your list of suspects.

Additional Resources

Key Points

  • FIXME