List of trajectory converters

ASE

Converts a trajectory to MDT format using ASE.

Attempts to convert a trajectory file to MDANSE .mdt format (HDF5). The conversion is done using the ase.io module. It works both for the ASE’s own .traj format, and for other formats supported by ASE. Please help the ASE format detection mechanism by using standard input file names.

Inputs:

CASTEP

Converts a Castep Trajectory into an MDT trajectory file.

Inputs:

CHARMM

Converts a CHARMM trajectory to an MDT trajectory.

Inputs:

CP2K

Converts a CP2K trajectory to an MDT trajectory.

Inputs:

DCD

Converts a DCD trajectory to an MDT trajectory.

Inputs:

DFTB

Converts a DFTB trajectory to an MDT trajectory.

Inputs:

DL_POLY

Converts a DL_POLY trajectory to an MDT trajectory.

Inputs:

Forcite

Converts a Forcite trajectory to an MDT trajectory.

Inputs:

Gromacs

Converts a Gromacs trajectory to an MDT trajectory.

Inputs:

LAMMPS

Converts a LAMMPS trajectory to an MDT trajectory.

Inputs:

MDAnalysis

Converts a trajectory to the MDT format using MDAnalysis.

MDAnalysis reads MD trajectories by specifying topology and coordinate files. Multiple files can be used for the coordinate files so that trajectories will be stitched together. For supported file formats, the continuous option ensures that duplicated time-frames will not be added, see <a href=”https://userguide.mdanalysis.org/stable/reading_and_writing.html”>reading and writing</a>. For topology and coordinate files supported by MDAnalysis see <a href=”https://userguide.mdanalysis.org/stable/formats/index.html#formats”>formats</a>.

Inputs:

MDTraj

Converts a trajectory to the MDT format using MDTraj.

MDTraj reads MD trajectories by specifying trajectory files and optionally a topology file. Multiple files can be used for the trajectory files so that trajectories will be stitched together.

Inputs:

NAMD

Converts a NAMD trajectory to an MDT trajectory.

Inputs:

VASP

Converts a VASP XDATCAR file to an MDT trajectory.

This converter works for XDATCAR files which contain a header specifying the unit cell size and atom types.

If your XDATCAR file does not have a header, you can add it manually to the beginning of the file. The header can be copied from the CONTCAR file.

A valid header should look like this:

unknown system
1
9.050041    0.000000    0.000000
0.000000    8.236754    0.000000
0.000000    0.000000   11.000452
Cu   Rb   Cl    S
9   4   7   12

where the last two lines specify the atomic types and the number of the atoms of each type in the same order as they appear in the atom coordinates below.

Inputs:

XPLOR

Converts an Xplor trajectory to an MDT trajectory.

Inputs: