What this category is
Simulations, labelled as such
Every record carries the source publication or dataset, the simulated
system, the model family and force field, the pulling protocol and geometry, and the
reported results. They have their own record type (SIM-######), their own
pages and downloads, and they never stand in for an experiment.
Units are part of the data
Coarse-grained models often report reduced units. Each value keeps the
unit the source wrote plus a unit_system field, and a reduced value is only
converted when the paper states the conversion — the conversion is stored with it.
Matched to experiments
Simulations are matched to SMASH-BIO and MechanoProDB experiments by shared resolver-checked identifiers and the same pulling geometry. Each link carries a match level, so a loose match is never presented as a like-for-like one.
By molecule type
By model family
How a simulation is compared with an experiment
The API and the downloads keep both sides of every link, and the disagreement is the interesting part.
1 · Same construct, same geometry
A shared resolver-checked identifier, the same pulling geometry in the experimental vocabulary, and constructs that overlap. This is the level at which a force can be compared directly.
2 · Same molecule, other geometry
The molecule matches, but the construct or the geometry differs or is not stated. Comparable with care, and never plotted on a shared physical axis without a stated conversion.
3 · Homolog
No shared identifier: the link rests on a distinctive molecule-name token. Weakest level, shown as such, and useful only as a pointer.
Recently indexed simulations
The simulation schema
SMASH-SIM v1.0.0 reuses the published SMFS definitions for quantities, identifiers, evidence and results, and adds the model, protocol and unit-system blocks.
Read the schemaSubmit a simulation record
Authors can submit a JSON record that validates against the schema; every extracted value in an automatic record shows its evidence snippet.
Submit a record