Glossary¶

Alias¶

A human-readable, URL-safe, unique name for a simulation, used instead of its UUID. See Alias.

Access Layer (AL)¶

The IMAS data access layer. SimDB reads data written with Access Layer 5 (AL5) or later. Older Access Layer 4 (AL4) MDSplus data must be migrated first. See Migrate AL4 MDSplus data.

Backend¶

The storage format used for an IMAS data entry, for example hdf5 or mdsplus. Specified in an IMAS URI.

Cerberus¶

The Python library SimDB uses to validate simulation metadata against a server’s schema. See Validation.

Checksum¶

A hash recorded for each data file (SHA-1 for ordinary files, a content hash for IMAS data) used to detect changes. See Validation.

HDF5¶

A file-based storage format, usable as an IMAS backend (imas:hdf5?...).

IDS¶

Interface Data Structure. The standardized data structure used by IMAS to represent physics quantities.

IMAS¶

Integrated Modelling and Analysis Suite. The data framework used by ITER and the wider fusion community. SimDB reads IMAS data through imas-python.

Manifest¶

A YAML file describing a simulation and the data it is associated with, used to ingest the simulation. See the manifest format.

MDSplus¶

A data system usable as an IMAS backend (imas:mdsplus?...).

Metadata¶

Searchable key/value information attached to a simulation. See Concepts.

Remote¶

A configured SimDB server that the client can push to and query. See Configure remotes.

Simulation¶

The central SimDB entity: one run or analysis, with a UUID, optional alias, status, files, and metadata. See Concepts.

Summary IDS¶

An IDS holding condensed summary information about a simulation, a common source of metadata.

UDA¶

Universal Data Access. A server protocol for reaching remote IMAS data, used in remote IMAS URIs.

UUID¶

The permanent unique identifier assigned to every simulation.

Watcher¶

A user subscribed to notifications about a simulation. See Concepts.