ITER Physics Data Model Documentation for spectrometer_mass

Mass spectrometer diagnostic

Notation of array of structure indices: itime indicates a time index; i1, i2, i3, ... indicate other indices with their depth in the IDS. This notation clarifies the path of a given node, but should not be used to compare indices of different nodes (they may have different meanings).

Lifecycle status: alpha since version 3.29.0

Last change occured on version: 3.42.0

Back to top IDS list

You are now in flat display mode, note that errorbars are not visible in this mode

Full path name Description Data Type Coordinates
ids_properties Interface Data Structure properties. This element identifies the node above as an IDS structure
ids_properties/comment Any comment describing the content of this IDS {constant} STR_0D
ids_properties/name User-defined name for this IDS occurrence {constant}. Introduced after DD version 3.39.0 STR_0D
ids_properties/homogeneous_time This node must be filled (with 0, 1, or 2) for the IDS to be valid. If 1, the time of this IDS is homogeneous, i.e. the time values for this IDS are stored in the time node just below the root of this IDS. If 0, the time values are stored in the various time fields at lower levels in the tree. In the case only constant or static nodes are filled within the IDS, homogeneous_time must be set to 2 {constant} INT_0D
ids_properties/occurrence_type Type of data contained in this occurrence. Introduced after DD version 3.39.0. Available options (refer to the children of this identifier structure) :
Name Index Description
reconstruction 1 Equilibrium reconstruction
prediction_fixed 2 Equilibrium prediction, fixed boundary
prediction_free 3 Equilibrium prediction, free boundary
mapping 4 Used for mapping equilibrium results from one grid type / resolution to another, or for including variables not present in the first set such as the calculation of magnetic field of other derived parameters
structure
ids_properties/occurrence_type/name Short string identifier {constant} STR_0D
ids_properties/occurrence_type/index Integer identifier (enumeration index within a list). Private identifier values must be indicated by a negative index. {constant} INT_0D
ids_properties/occurrence_type/description Verbose description {constant} STR_0D
ids_properties/source
Lifecycle status: obsolescent since version 3.34.0
Source of the data (any comment describing the origin of the data : code, path to diagnostic signals, processing method, ...). Superseeded by the new provenance structure. {constant} STR_0D
ids_properties/provider Name of the person in charge of producing this data {constant} STR_0D
ids_properties/creation_date Date at which this data has been produced {constant} STR_0D
ids_properties/version_put Version of the access layer package used to PUT this IDS structure
ids_properties/version_put/data_dictionary Version of Data Dictionary used to PUT this IDS {constant} STR_0D
ids_properties/version_put/access_layer Version of Access Layer used to PUT this IDS {constant} STR_0D
ids_properties/version_put/access_layer_language Programming language of the Access Layer high level API used to PUT this IDS {constant} STR_0D
ids_properties/provenance
Lifecycle status: alpha since version 3.34.0
Provenance information about this IDS structure
ids_properties/provenance/node(i1) Set of IDS nodes for which the provenance is given. The provenance information applies to the whole structure below the IDS node. For documenting provenance information for the whole IDS, set the size of this array of structure to 1 and leave the child "path" node empty {constant} array of structures [max_size=20 (limited in MDS+ backend only)] 1- 1...N
ids_properties/provenance/node(i1)/path Path of the node within the IDS, following the syntax given in the link below. If empty, means the provenance information applies to the whole IDS. Click here for further documentation. {constant} STR_0D
ids_properties/provenance/node(i1)/reference(i2) List of references used to populate or calculate this node, identified as explained below. In case the node is the result of of a calculation / data processing, the reference is an input to the process described in the "code" structure at the root of the IDS. The reference can be an IDS (identified by a URI or a persitent identifier, see syntax in the link below) or non-IDS data imported directly from an non-IMAS database (identified by the command used to import the reference, or the persistent identifier of the data reference). Often data are obtained by a chain of processes, however only the last process input are recorded here. The full chain of provenance has then to be reconstructed recursively from the provenance information contained in the data references. Click here for further documentation.. Introduced after DD version 3.41.0 array of structures [max_size=10 (limited in MDS+ backend only)] 1- 1...N
ids_properties/provenance/node(i1)/reference(i2)/name Reference name {constant} STR_0D
ids_properties/provenance/node(i1)/reference(i2)/timestamp Date and time (UTC) at which the reference was created, expressed in a human readable form (ISO 8601) : the format of the string shall be : YYYY-MM-DDTHH:MM:SSZ. Example : 2020-07-24T14:19:00Z {constant} STR_0D
ids_properties/plugins
Lifecycle status: alpha since version 3.39.0
Information about the plugins used to write/read this IDS. This structure is filled automatically by the Access Layer at GET/PUT time, no need to fill it via a user program.. Introduced after DD version 3.38.1 structure
ids_properties/plugins/node(i1) Set of IDS nodes for which a plugin has been applied {constant} array of structures [max_size=20 (limited in MDS+ backend only)] 1- 1...N
ids_properties/plugins/node(i1)/path Path of the node within the IDS, following the syntax given in the link below. If empty, means the plugin applies to the whole IDS. Click here for further documentation. {constant} STR_0D
ids_properties/plugins/node(i1)/put_operation(i2) Plugins used to PUT a node (potentially, multiple plugins can be applied, if so they are listed by order of application) array of structures [max_size=10 (limited in MDS+ backend only)] 1- 1...N
ids_properties/plugins/node(i1)/put_operation(i2)/name Name of software used {constant} STR_0D
ids_properties/plugins/node(i1)/put_operation(i2)/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
ids_properties/plugins/node(i1)/put_operation(i2)/commit Unique commit reference of software {constant} STR_0D
ids_properties/plugins/node(i1)/put_operation(i2)/version Unique version (tag) of software {constant} STR_0D
ids_properties/plugins/node(i1)/put_operation(i2)/repository URL of software repository {constant} STR_0D
ids_properties/plugins/node(i1)/put_operation(i2)/parameters List of the code specific parameters in XML format {constant} STR_0D
ids_properties/plugins/node(i1)/readback(i2) Plugins to be used to read back a node (potentially, multiple plugins can be applied, listed in reverse order of application) array of structures [max_size=10 (limited in MDS+ backend only)] 1- 1...N
ids_properties/plugins/node(i1)/readback(i2)/name Name of software used {constant} STR_0D
ids_properties/plugins/node(i1)/readback(i2)/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
ids_properties/plugins/node(i1)/readback(i2)/commit Unique commit reference of software {constant} STR_0D
ids_properties/plugins/node(i1)/readback(i2)/version Unique version (tag) of software {constant} STR_0D
ids_properties/plugins/node(i1)/readback(i2)/repository URL of software repository {constant} STR_0D
ids_properties/plugins/node(i1)/readback(i2)/parameters List of the code specific parameters in XML format {constant} STR_0D
ids_properties/plugins/node(i1)/get_operation(i2) Plugins actually used to read back a node (potentially, multiple plugins can be applied, listed in reverse order of application). This information is filled by the plugin infrastructure during the GET operation. array of structures [max_size=10 (limited in MDS+ backend only)] 1- 1...N
ids_properties/plugins/node(i1)/get_operation(i2)/name Name of software used {constant} STR_0D
ids_properties/plugins/node(i1)/get_operation(i2)/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
ids_properties/plugins/node(i1)/get_operation(i2)/commit Unique commit reference of software {constant} STR_0D
ids_properties/plugins/node(i1)/get_operation(i2)/version Unique version (tag) of software {constant} STR_0D
ids_properties/plugins/node(i1)/get_operation(i2)/repository URL of software repository {constant} STR_0D
ids_properties/plugins/node(i1)/get_operation(i2)/parameters List of the code specific parameters in XML format {constant} STR_0D
ids_properties/plugins/infrastructure_put Plugin infrastructure used to PUT the data structure
ids_properties/plugins/infrastructure_put/name Name of software used {constant} STR_0D
ids_properties/plugins/infrastructure_put/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
ids_properties/plugins/infrastructure_put/commit Unique commit reference of software {constant} STR_0D
ids_properties/plugins/infrastructure_put/version Unique version (tag) of software {constant} STR_0D
ids_properties/plugins/infrastructure_put/repository URL of software repository {constant} STR_0D
ids_properties/plugins/infrastructure_get Plugin infrastructure used to GET the data structure
ids_properties/plugins/infrastructure_get/name Name of software used {constant} STR_0D
ids_properties/plugins/infrastructure_get/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
ids_properties/plugins/infrastructure_get/commit Unique commit reference of software {constant} STR_0D
ids_properties/plugins/infrastructure_get/version Unique version (tag) of software {constant} STR_0D
ids_properties/plugins/infrastructure_get/repository URL of software repository {constant} STR_0D
name Name of the spectrometer {static} STR_0D
identifier ID of the spectrometer {static} STR_0D
channel(i1) Set of mass channels, each corresponding to a given atomic mass measured continuously by the spectrometer. Introduced after DD version 3.38.1 array of structures [max_size=100 (limited in MDS+ backend only)] 1- 1...N
channel(i1)/a Atomic mass measured by this channel {constant} [Atomic Mass Unit] FLT_0D
channel(i1)/current(:) Collected current {dynamic} [A] FLT_1D 1- channel(i1)/time
channel(i1)/pressure_partial(:) Partial pressure (calibrated data) {dynamic} [Pa] FLT_1D 1- channel(i1)/time
channel(i1)/photomultiplier_voltage(:) Voltage applied to the photomultiplier {dynamic} [V] FLT_1D 1- channel(i1)/time
channel(i1)/validity Indicator of the validity of the data. 0: Valid from automated processing; 1: Valid and certified by the diagnostic RO; -1: Problem identified in the data processing (request verification by the diagnostic RO); -2: Invalid data, should not be used. (Values less than -2 have a code-specific meaning) {constant} INT_0D
channel(i1)/validity_timed(:) Indicator of the validity of the data for each time slice. 0: Valid from automated processing; 1: Valid and certified by the diagnostic RO; -1: Means problem identified in the data processing (request verification by the diagnostic RO); -2: Invalid data, should not be used. (Values less than -2 have a code-specific meaning.) {dynamic} INT_1D 1- channel(i1)/time
channel(i1)/time(:) Timebase for the dynamic nodes of this channel {dynamic} [s] FLT_1D 1- 1...N
residual_spectrum(itime) Set of entire mass spectra recorded at various time slices {dynamic}. Introduced after DD version 3.38.1 array of structures 1- residual_spectrum(itime)/time
residual_spectrum(itime)/a(:) Array of atomic masses {dynamic} [Atomic Mass Unit] FLT_1D 1- 1...N
residual_spectrum(itime)/current(:) Collected current {dynamic} [A] FLT_1D 1- residual_spectrum(itime)/a
residual_spectrum(itime)/time Time {dynamic} [s] FLT_0D
emission_current Emission current in the spectrometer filament {static} [A]. Introduced after DD version 3.41.0 FLT_0D
detector_voltage Voltage applied on the microchannel plate detector {static} [V]. Introduced after DD version 3.41.0 FLT_0D
latency Upper bound of the delay between physical information received by the detector and data available on the real-time (RT) network. {static} [s]. Introduced after DD version 3.32.1 FLT_0D
code Generic decription of the code-specific parameters for the code that has produced this IDS structure
code/name Name of software generating IDS {constant} STR_0D
code/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
code/commit Unique commit reference of software {constant} STR_0D
code/version Unique version (tag) of software {constant} STR_0D
code/repository URL of software repository {constant} STR_0D
code/parameters List of the code specific parameters in XML format {constant} STR_0D
code/output_flag(:) Output flag : 0 means the run is successful, other values mean some difficulty has been encountered, the exact meaning is then code specific. Negative values mean the result shall not be used. {dynamic} INT_1D 1- time
code/library(i1) List of external libraries used by the code that has produced this IDS array of structures [max_size=10 (limited in MDS+ backend only)] 1- 1...N
code/library(i1)/name Name of software {constant} STR_0D
code/library(i1)/description Short description of the software (type, purpose) {constant}. Introduced after DD version 3.38.1 STR_0D
code/library(i1)/commit Unique commit reference of software {constant} STR_0D
code/library(i1)/version Unique version (tag) of software {constant} STR_0D
code/library(i1)/repository URL of software repository {constant} STR_0D
code/library(i1)/parameters List of the code specific parameters in XML format {constant} STR_0D
time(:) Generic time {dynamic} [s] FLT_1D 1- 1...N

Back to top IDS list