...
- 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: Occurences
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, …).
By default, the IDS name without specification of the occurrence number (e.g. “equilibrium”) corresponds to occurrence “0”. IDS occurrences above the default value (occurrence “0”) are accessed by concatenating the name of the IDS with the occurrence number, with a “/” in between. For example “equilibrium/2” is the name of the occurrence number 2 of the equilibrium IDS. Note that “equilibrium/0” is not valid (temporary limitation).
In the present implementation, there is a pre-set maximum number of occurrences of a given IDS usable in a Database entry or in a workflow. This number is indicated in the documentation in the “Max. occurrence number” column of the list of IDS table. This limitation should be removed in the future
Data Model documentation
Dynamically generated
Open the documentation by typing: dd_doc
...