The file opens—but is it the right kind of molecular data?

A common molecular-modeling frustration is choosing a file that looks relevant by its extension, only to discover that it contains a trajectory rather than a structure—or that the application can read it but cannot export it. Checking the format before building a workflow can save time and help avoid confusing missing or incomplete data with a modeling problem.

In SAMSON, it helps to start with one question: what kind of data are you trying to move? A molecular structure describes a system’s atoms and their coordinates. A molecular trajectory contains coordinate frames that describe how a system changes over time. A topology or parameter file may provide information needed to interpret a simulation or trajectory. These categories overlap in some workflows, but they are not interchangeable.

First, identify the file’s role

For molecular structures, SAMSON lists formats including PDB, mmCIF/CIF, MOL2, SDF, GRO, XYZ, and LAMMPS data files. Many of these are both readable and writable, but not all are. For example, MMTF, Molden, PSF, and AMBER topology files are listed as readable without a corresponding write capability in this reference. The table is therefore useful not just for checking whether a format is supported, but for checking the direction of support.

For trajectories, the list includes DCD, AMBER NetCDF (NC), TRR, XTC, TNG, and XYZ, among others. Some can be read and written; others are listed as read-only. If you need to send results to another tool, check the “Write” column before choosing an export path. A format being readable does not imply that it can be exported.

Pay attention to companion files

Some simulation data is meant to be used with another file. The documentation specifically notes that AMBER topology files such as PARM7 or PRMTOP are used when loading AMBER NetCDF trajectories. In practice, when preparing a trajectory for review or sharing, keep the associated topology information together and confirm that you are selecting the intended files.

There are also format-specific details worth knowing. SAMSON can read PDB files and common aliases such as ENT, and it supports PDBx/mmCIF as an import format; the documented CIF export is specifically PDBx/mmCIF. SDF supports both V2000 and V3000, with MOL and SD listed as read aliases. SMILES can be read and generated with the SMILES Manager extension, while PDBQT support is associated with AutoDock Vina Extended. GROMACS project files can be generated with GROMACS Wizard.

A quick pre-flight check

  1. Classify the data: structure, trajectory, 3D geometry, image, or another kind of file.
  2. Check Read and Write separately: confirm the direction you need, rather than relying on the format name alone.
  3. Look for aliases and conditions: a familiar extension may be listed as a read alias, or a format may require a SAMSON Extension.
  4. Keep related files together: especially when working with trajectories and their associated topology information.
  5. Choose an exchange format deliberately: if another application is involved, verify that it supports the same format and the data you need to preserve.

If a needed format is not listed, the reference notes that extensions may add support for additional formats. You can also develop importers and exporters, or contact the SAMSON team through the forum to request a format.

For the full format tables and extension notes, see the SAMSON supported formats reference.

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

Comments are closed.