...
- The Data Model has a tree structure, for the sake of clarity
- At the top level, a collection of modular structures representing
- Abstract physical quantities (e.g. distribution functions)
- Tokamak subsystems (e.g. PF systems)
- These modular structures have the appropriate granularity for exchange in an IM workflow → they also represent standardised interfaces for communication between codes, named Interface Data Structure (IDS)
- Each has an “ids_properties” substructure (metadata + comments + timebase usage)
- Each has a “code” substructure (trace the code-specific parameters of the code that has generated this IDS)
- Each has a generic timebase (“time”)
Data Model:
...
Occurrences
There can be multiple instances, or “occurrences” of a given IDS in a Database Entry (see 5.2) or used in an IMAS workflow. These occurrences can correspond to different methods for computing the physical quantities of the IDS, or to different functionalities in a workflow (e.g. store initial values, prescribed values, values at next time step, …).
...