real_time_data¶
Description of the data bus circulating on the real time data network of the machine. This is typically used (but not only) as an interface to the Plasma Control System (PCS)
Maximum occurrences (MDS+ backend only): 3
New in version 3.34.0: lifecycle status alpha
Changed in version 3.40.0.
ids_propertiesstructure¶
See common IDS structure reference: ids_properties.
topic(i1)AoS¶List of topics. […]
List of topics. Signals are grouped by topic
Maximum occurrences (MDS+ backend only): 20
1 |
|
topic(i1)/signal(i2)AoS¶List of signals that are allocated to the PCS interface
List of signals that are allocated to the PCS interface
Maximum occurrences (MDS+ backend only): 100
1 |
|
topic(i1)/signal(i2)/allocated_position(:)INT_1D¶Allocation of signal to a position in the SDN (1..N), or several […]
Allocation of signal to a position in the SDN (1..N), or several positions in case of signal reshaping; this will be implementation specific
1 |
|
topic(i1)/signal(i2)/data_str(:)STR_1D¶Signal data (e.g. […]
Signal data (e.g. diagnostic signal or PCS command), serialized as a string
1 |
New in version >3.39.0.
topic(i1)/signal(i2)/quality(:)INT_1D¶Indicator of the quality of the signal. […]
Indicator of the quality of the signal. Following ITER PCS documentation (https://user.iter.org/?uid=354SJ3&action=get_document), possible values are: 1 - GOOD (the nominal state); 2 - INVALID (data no usable); 3 - DATA INTEGRITY ERROR (e.g. out of bounds with respect to expectations, calibration error,…)
1 |
New in version >3.39.0.
topic(i1)/time_stamp(:) ⇹sFLT_1D¶Time of creation for all signals belonging to this topic. […]
Time of creation for all signals belonging to this topic. A set of time stamps can be recorded if needed
1 |
|
New in version >3.39.0.