Simulation & physics

Physical simulation that says which engine actually ran

Molecular dynamics, machine-learned potentials, docking and free energies, quantum estimators and phonons — wired to the same projects, runs and evidence ledger as the rest of the platform.

3
MD engines: GROMACS, OpenMM, LAMMPS
deck builders + live probes
9
ML potentials in the registry
8 ASE-drivable; availability probed live
5
GROMACS .mdp presets
minim · em · NVT · NPT · prod
6
evidence classes, E0–E5
no unlabelled numbers
Evidence contract

Every number names the engine that produced it

The provenance registry behind /physics treats a result as a claim: which engine, what kind of computation, what it cannot do, and how far to trust it. Real engine runs are COMPUTED; analytic fallbacks are DEMO with null values; machine-learned potentials are PREDICTED.

Six evidence classes form a ladder. Each class sets a ceiling on trust, and a card may claim a level below its ceiling but never above it — inconsistent labels are caught at card construction and clamped at response time, not printed.

  • COMPUTED · E4 — A deterministic solver or exact computation ran — real DFT/MD, closed-form math, or deterministic deck templating whose text is exact.
  • PREDICTED · E3 — A statistical or machine-learned model produced the number; accuracy is bounded by its training domain.
  • MEASURED · E5 — A certified experimental measurement — the top of the ladder, where lab results live.
  • EXTRACTED · E2 — Automated extraction from a vendor file or document, with its source attached.
  • HYPOTHESIS · E1 — A generative screening candidate proposed for testing.
  • DEMO · E0 — A synthetic or analytic placeholder. Numeric fields are null and the response says why.
Server-side, not browser-side.Decks, protocols and inputs are rendered on the server. Nothing integrates a trajectory in your browser; whether a real engine runs depends on the deployment — an installed binary or module, an engine container, or a configured cluster.
Fallbacks are announced.When an engine is absent, the response carries value: null plus an install or container next step. Deck text may still be generated — deck templating is deterministic, so it is labelled template text, not a simulation result.
One ledger.Every response carries an engine card and an evidence block, so simulation output can be traced the same way as an experiment or a prediction: by what produced it.
Molecular dynamics

GROMACS, OpenMM and LAMMPS from one deck workflow

Build real MD inputs and analysis on the server, with the engine card naming whether gmx, OpenMM or lmp actually ran. Availability is probed live, so an absent engine degrades to a labelled DEMO envelope rather than a quiet substitution.

GROMACS
Decks, topology and trajectory analysis

Five .mdp presets — steepest-descent minimisation, conjugate-gradient polish, NVT, NPT and production — plus a full setup script (pdb2gmx → editconf → solvate → genion → grompp → mdrun) and a force-field/water matrix spanning AMBER, CHARMM, OPLS and GROMOS with TIP3P/TIP4P/SPC/SPCE. Analysis ports Kabsch RMSD, per-atom RMSF, radius of gyration and H-bond counting run over your frame arrays even when the gmx binary is not installed.

OpenMM
Force fields, ensembles, reporters, replicates

AMBER ff14SB/ff19SB, CHARMM36 and OpenFF SMIRNOFF; Langevin-middle and Brownian integrators; NVT or NPT with a Monte-Carlo barostat; StateDataReporter, DCD and checkpoint artifacts. Seeded replicates (up to eight) aggregate mean and standard deviation instead of dressing up one short trajectory, and the platform probe reports which of CPU/CUDA/OpenCL is available.

LAMMPS
Metals, alloys, defects and MLIAP

EAM/alloy and MEAM pair blocks, or ML potentials through pair_style mliap unified (MACE, SevenNet, ORB). A four-stage NPT deck — minimise, NVT equilibrate, NPT equilibrate, NPT production — includes dump and restart blocks, and the vacancy workflow ships paired bulk and defect decks with the E_vac = E_defect − (N−1)/N · E_bulk formula written into the payload so the arithmetic is auditable.

Cluster templates
Slurm scripts for every engine

CPU, GPU and MPI batch scripts are returned as copy-paste text for gmx mdrun, long OpenMM runs and MPI LAMMPS defect sweeps. Decks and submission scripts are rendered server-side; the browser never executes a simulation.

Machine-learned potentials

Nine potentials, one driver, zero invented numbers

The unified MLIP driver resolves a structure, builds the right ASE calculator lazily, and reports availability before anything runs. Relaxation, MD, equation-of-state fits and benchmarks all reuse the same engine cards.

Live registry
A registry that admits what is missing

GET /api/mlip/registry probes every entry on this deployment: MACE, CHGNet, MatterSim, SevenNet, ORB, FAIR-Chem OMat24, M3GNet, ALIGNN and ASE EMT. Unavailable potentials are shown as unavailable, and ALIGNN states openly that it ships no ASE calculator and is property-prediction only. Probing is import-only — no weights are downloaded to answer the question.

Relax & MD
Single points, geometry relaxation and MLIP MD

Energy, forces and stress from a CIF, POSCAR, pymatgen structure or ASE atoms object; relaxation with BFGS, FIRE, LBFGS or GPMin and a downsampled energy/fmax trajectory; NVT (Langevin) or NPT molecular dynamics through ASE. Every field is machine-learned prediction, labelled PREDICTED/E3 — never COMPUTED as if it were DFT.

EOS & uncertainty
Bulk modulus scans and cross-model spread

An isotropic strain scan single-points each volume and fits a quadratic E(V) around the minimum to report V0 and B0. The uncertainty endpoint runs the same structure across every available potential and returns mean and standard deviation of the per-atom energy as a disagreement proxy — and returns no spread when fewer than two potentials exist, rather than inventing an error bar.

Benchmarks & phonons
Score potentials on your entries, then compute phonons

Benchmark runs report energy/force/stress MAE against your reference entries, plus hull-distance and phonon-span errors and a cross-instance leaderboard. The embedded Phonopy workflow then turns MLIP or caller-supplied DFT forces into phonon bands, DOS and thermal properties.

A surrogate of DFT is still a surrogate.MLIP energies, forces and stresses are machine-learned predictions at PBE-level accuracy; they are labelled PREDICTED/E3 and never presented as first-principles results. Cross-model spread is a disagreement heuristic, not a calibrated error bar.
Docking & free energies

From receptor prep to a ligand network

Vina and Smina score real poses when the binaries are present; preparation steps that are deterministic (boxes, PDBQT text, atom maps) always run. Every scoring path states its engine, and a missing binary returns DEMO with value null.

Receptor prep
PDB to PDBQT, rigidify, flexible residues

Receptor preparation writes PDBQT with Open Babel when it is present (hydrogens optional), rigidifies the result for Vina, and can split named flexible residues (chain:RESnum) into a real flex file that matches ATOM records — with a warning when the names match nothing rather than pretending the split worked.

Search box
Vina-style boxes with pocket presets

Define a centre and size in the 5–60 Å sanity range, use the auto-centroid blind box, or start from pocket presets (kinase ATP, GPCR orthosteric, protease active, blind) and supply an explicit centre for a real target. The generated vina argv is returned alongside the box.

Dock · array · ensemble
Ranked poses, library screens, receptor conformers

Single docking returns affinities in kcal/mol plus PDBQT poses and greedy RMSD pose clusters. Array runs screen up to 200 ligands on a worker pool with an optional GPU queue hand-off. Ensemble docking docks one ligand across up to twelve receptor conformations and rolls the scores into a Boltzmann-weighted affinity at a stated temperature.

FEP & chemical space
Atom maps, networks and diversity

Build atom maps with sanity filters, plan a relative free-energy network (minimum-spanning-tree strategy), generate lambda schedules and run an MBAR-lite estimator. Chemical-space projection and diversity picking place a ligand set in context. OpenFE alchemical free energy runs behind component validation and atom/step caps: when OpenFE and OpenMM are both present it builds the RBFE network descriptor and a short CPU vacuum/minimisation sanity — explicitly labelled not a production ΔΔG — and otherwise reports a validation-only DEMO rather than a fabricated number.

Scores rank, they do not bind.A Vina/Smina affinity is an approximate ranking score in kcal/mol, not a binding free energy, and the receptor is rigid unless flexible residues are declared. The OpenFE-backed path runs a network descriptor and a short CPU vacuum/minimisation sanity when OpenFE and OpenMM are both importable — explicitly labelled not a production alchemical ΔΔG.
Quantum & HPC

Fast estimators now, real DFT where a cluster exists

The composition path is a fast physics heuristic; it is honest about being one. Real ab-initio work is dispatched by compute tier, and periodic plane-wave DFT is only ever sent to a configured remote Slurm cluster.

Fast estimators
Composition and structure in, properties out

From a formula or POSCAR/CIF: formation energy, d-band centre and adsorption energetics for metallic compositions, with band gaps taken only from a live Materials Project lookup — otherwise null with a note. Three tiers are reported explicitly: GPAW planewave DFT when installed (COMPUTED), a real M3GNet/MatPES GNN relaxation (PREDICTED/E3), or the labelled composition heuristic (DEMO).

ASE & MLIP relaxation
Real relaxations, labelled by engine

A real ASE EMT relaxation runs for the metals EMT is parameterised for, and optional MLIP bridges upgrade the formation-energy path to a genuine interatomic-potential prediction when a checkpoint is configured. The engine name in the response says exactly which path produced the number.

HPC dispatch
Local tiers, cluster tiers, honest refusals

Local execution routes by tier: classical EMT (Al, Ag, Au, Cu, Ni, Pd, Pt), semi-empirical GFN2-xTB on finite clusters up to 60 atoms, and ab-initio Psi4 HF/def2-SVP for formula units up to 12 atoms. Periodic plane-wave DFT (PBE, PBEsol, LDA, RPBE, revPBE, SCAN, HSE06) requires a configured remote Slurm cluster and is dispatched over SSH sbatch; on localhost it fails with an explanation instead of silently substituting EMT.

Inputs
Quantum ESPRESSO and VASP input decks

Generate INCAR, KPOINTS and POSCAR with POTCAR specifications plus a Quantum ESPRESSO deck from a parsed structure or generated prototype cell, with optional Hubbard-U and D3 dispersion settings. This path writes inputs only — it never claims to have run a solver.

No cluster, no fake DFT.Set periodic plane-wave DFT to run on localhost and the job fails with a message explaining that it needs a real Slurm/Quantum ESPRESSO cluster — it is never silently downgraded to the classical EMT potential. Host-key verification is on by default for remote dispatch.
Phonons

Lattice dynamics over MLIP or DFT forces

The Phonopy depth service turns displacements and forces into force constants, then into band structures, density of states and thermal properties — reporting imaginary modes instead of hiding them.

FAQ

Questions the engine cards already answer

Does Matflow simulate in my browser?
No. The MD studio builds and renders inputs on the server; nothing integrates a trajectory client-side. Real runs happen when the engine binary or module is installed on the deployment, in an engine container, or on a configured cluster.
What is the difference between COMPUTED and DEMO here?
COMPUTED/E4 means a deterministic solver or exact computation produced the number — including exact deck-templating text. DEMO/E0 means an analytic fallback ran, numeric fields are null, and the response includes the reason plus a next step. The engine card on the response names the path.
Are MLIP energies DFT results?
No. They are machine-learned predictions of DFT-level properties and are labelled PREDICTED/E3. Accuracy is bounded by the potential’s training data; electronic structure such as band gaps is out of scope for these potentials.
Can I submit jobs to my own cluster?
Yes. Slurm templates ship for every engine, and the HPC dispatcher targets a configured remote host over SSH with host-key verification on by default. Periodic plane-wave DFT is refused on localhost rather than substituted with EMT.
What happens if Vina, GROMACS or Phonopy is missing?
Deterministic preparation still runs (boxes, decks, displacement datasets, atom maps), but scoring, trajectories and spectra come back as DEMO with value null and an install hint. No fabricated numbers are emitted.
Can I use DFT forces in the phonon workflow?
Yes — pass force sets in eV/Å, one array per displaced supercell. The service validates their shape against the generated supercells and returns a clear error on mismatch instead of guessing.
How do I see what actually ran?
Open /physics for the engine cards, or read the engine card and evidence block on any individual response. Both name the engine, its kind (real, analytic or surrogate), its limitations and its evidence class.

Add physics to your campaign

Screen candidates, relax structures and run real engines where installed — then feed the results into the same projects, evidence ledger and reports as the rest of your work.