Your trajectory file is only half the story: choosing formats in SAMSON

A molecular trajectory can contain thousands of coordinate snapshots, but opening one is not always as simple as choosing a file. A common source of frustration is discovering that a format can be read but not written, or that a trajectory needs a separate topology file to make sense of its coordinates.

SAMSON supports several molecular trajectory formats. The useful first step is to check the format’s role in your workflow: are you importing a simulation result, exporting coordinates for another tool, or moving between both? The supported-formats reference distinguishes reading from writing, which helps avoid assuming that support works in both directions.

Choose by the task, not just the extension

For a quick overview, these are some of the options listed in the documentation:

  • DCD: listed for both reading and writing. The documentation describes it as a CHARMM, NAMD, or LAMMPS binary trajectory.
  • AMBER NetCDF (NC): listed for reading and writing. The read aliases include NCDF and NCTRAJ.
  • TRR and XTC: GROMACS trajectory formats listed for both reading and writing.
  • PDB: listed for both reading and writing as a standard PDB file. It also appears in the molecular-structures section, so the same extension can represent structural data or a trajectory, depending on the file.
  • XYZ: listed for reading as a simple coordinate trajectory format, but not for writing in the trajectory table.
  • ARC, LAMMPSTRJ, TNG, and TRJ: listed for reading, with no write support indicated in that table.

That last distinction matters when planning a round trip. If your workflow ends with exporting a trajectory, start by checking the write column—not just whether SAMSON can open the input file. An empty write cell means the page does not list that format as writable.

For AMBER NetCDF, keep the topology nearby

The documentation specifically notes that AMBER NetCDF trajectories are loaded using an AMBER topology file, with PARM7 and PRMTOP listed as topology formats. In practical terms, treat the trajectory and its topology as a pair when organizing simulation results. Keeping them together makes it easier to identify the context needed when you return to the data later.

This is a useful habit even before you open SAMSON: give related files clear names, and record which topology belongs with which trajectory. A filename such as production.nc is much more informative when its corresponding topology is easy to identify in the same project folder.

Check the format before converting

Conversion can be tempting when a file does not fit the next step in your workflow. Before converting, verify three things: whether SAMSON reads the source format, whether it writes the intended destination format, and whether the destination will preserve the data your next tool needs. The supported-formats page is a compatibility reference; it does not promise that every format stores identical information.

SAMSON uses the chemfiles library to read and write some trajectory formats. The documentation does not identify which listed formats use it, so check the relevant format details rather than assuming that all trajectory support follows the same route.

A small pre-import checklist

  1. Identify the file type and any aliases listed for it.
  2. Confirm that the format is supported for reading.
  3. If you need to export later, confirm write support separately.
  4. For AMBER NetCDF, keep the associated topology file available.
  5. When a format is not listed, check whether an extension adds support. SAMSON Extensions may support additional formats beyond those in the reference.

These checks can save time by turning an ambiguous “why won’t this trajectory work?” problem into a more specific question about format, direction of use, or associated files. For the complete list and details, see the SAMSON supported formats reference.

Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.

Comments are closed.