OpenMM

Run energy minimization and molecular dynamics (MD) from an input protein structure using nonperiodic conditions.

API/CLI tool ID: openmm

Understanding inputs and outputs

Molecular dynamics (MD) follows atomic motion over time by calculating forces. This OpenMM input handles protein-only systems under nonperiodic conditions: it does not assume that the same box repeats through space. Its environment therefore differs from the current GROMACS setup, which prepares water and ions.

simTimeNs specifies the duration of molecular motion to simulate, in ns, not the time spent waiting for the server. The default 0.002 ns equals 2 ps, or 1,000 steps of 2 fs. Energy minimization is a preparation step that reduces issues such as atomic overlaps in the starting structure; it is separate from this MD time.

potential_energy_kj_mol is the potential energy calculated for the atomic configuration, in kJ/mol. It depends on atom count, water and ion composition, and the force model, so comparing numbers from different systems alone cannot identify a more stable protein. This short calculation does not establish long-term stability or equilibration.

temperature_k reports the simulation temperature in kelvin (K), not degrees Celsius. A higher or lower temperature alone does not indicate result quality.

Input settings

SettingFormatRequiredDefaultDescription and constraints
pdbFilepdbRequired—Protein structure with standard amino-acid ATOM records only (no HETATM, ligands or water), at most 2,000 non-hydrogen atoms — Extensions pdb · cif
simTimeNsnumberOptional0.002Simulation time (ns): an integer multiple of 2 fs, at most 0.02 ns (10,000 steps). Not the wall-clock wait — Minimum 0.000002, Maximum 0.02

Output metrics

ColumnDisplay nameRangeUnitDescription
potential_energy_kj_molPotential energy—kJ/mol—
temperature_kTemperature—K—

See Reading results for metric definitions and interpretation. A range shows possible values; whether higher or lower is better depends on the metric.

Execution availability

Open an execution plan in your project to see available tool versions and costs. Review and approve the inputs, settings, and terms before running.

License

Code, model weights, and accompanying data have their own terms. The table summarizes terms from official sources; check your execution plan for the configuration you will use. License texts are available in Third-party notices.

ComponentLicenseCommercial useSourceNotes
CodeMIT AND LGPL-3.0-onlyConditional; see notesLicense textAPI and CPU components are MIT; CUDA and OpenCL components are LGPL 3. Bundled third-party terms such as BSD, zlib and CC BY 3.0 follow the same file. Supplying binaries or containers to customers requires review of LGPL distribution obligations even if unmodified

A computational program without trained weights

Checked on 2026-10-06.

References

On this page