ITER Physics Data Model Documentation for reflectometer_profile

Profile reflectometer diagnostic. Multiple reflectometers are considered as independent diagnostics to be handled with different occurrence numbers

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.11.0

Last change occured on version: 3.39.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
type Type of reflectometer (frequency_swept, radar, ...) {static} STR_0D
channel(i1) Set of channels, e.g. different reception antennas or frequency bandwidths of the reflectometer array of structures [max_size=5 (limited in MDS+ backend only)] 1- 1...N
channel(i1)/name Name of the channel {static} STR_0D
channel(i1)/identifier ID of the channel {static} STR_0D
channel(i1)/mode Detection mode "X" or "O" {static} STR_0D
channel(i1)/line_of_sight_emission Description of the line of sight of the emission antenna. The first point corresponds to the centre of the antenna mouth. The second point correspond to the interception of the line of sight with the reflection surface on the inner wall. structure
channel(i1)/line_of_sight_emission/first_point Position of the first point structure
channel(i1)/line_of_sight_emission/first_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight_emission/first_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight_emission/first_point/z Height {static} [m] FLT_0D
channel(i1)/line_of_sight_emission/second_point Position of the second point structure
channel(i1)/line_of_sight_emission/second_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight_emission/second_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight_emission/second_point/z Height {static} [m] FLT_0D
channel(i1)/line_of_sight_detection Description of the line of sight of the detection antenna, to be filled only if its position is distinct from the emission antenna. The first point corresponds to the centre of the antenna mouth. The second point correspond to the interception of the line of sight with the reflection surface on the inner wall. structure
channel(i1)/line_of_sight_detection/first_point Position of the first point structure
channel(i1)/line_of_sight_detection/first_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight_detection/first_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight_detection/first_point/z Height {static} [m] FLT_0D
channel(i1)/line_of_sight_detection/second_point Position of the second point structure
channel(i1)/line_of_sight_detection/second_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight_detection/second_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight_detection/second_point/z Height {static} [m] FLT_0D
channel(i1)/antenna_emission Geometry of the emission antenna. Introduced after DD version 3.38.1 structure
channel(i1)/antenna_emission/geometry_type Type of geometry used to describe the surface of the detector or aperture (1:'outline', 2:'circular', 3:'rectangle'). In case of 'outline', the surface is described by an outline of point in a local coordinate system defined by a centre and three unit vectors X1, X2, X3. Note that there is some flexibility here and the data provider should choose the most convenient coordinate system for the object, respecting the definitions of (X1,X2,X3) indicated below. In case of 'circular', the surface is a circle defined by its centre, radius, and normal vector oriented towards the plasma X3. In case of 'rectangle', the surface is a rectangle defined by its centre, widths in the X1 and X2 directions, and normal vector oriented towards the plasma X3. {static} INT_0D
channel(i1)/antenna_emission/centre If geometry_type=2, coordinates of the centre of the circle. If geometry_type=1 or 3, coordinates of the origin of the local coordinate system (X1,X2,X3) describing the plane detector/aperture. This origin is located within the detector/aperture area. structure
channel(i1)/antenna_emission/centre/r Major radius {static} [m] FLT_0D
channel(i1)/antenna_emission/centre/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/antenna_emission/centre/z Height {static} [m] FLT_0D
channel(i1)/antenna_emission/radius Radius of the circle, used only if geometry_type = 2 {static} [m] FLT_0D
channel(i1)/antenna_emission/x1_unit_vector Components of the X1 direction unit vector in the (X,Y,Z) coordinate system, where X is the major radius axis for phi = 0, Y is the major radius axis for phi = pi/2, and Z is the height axis. The X1 vector is more horizontal than X2 (has a smaller abs(Z) component) and oriented in the positive phi direction (counter-clockwise when viewing from above). Click here for further documentation. structure
channel(i1)/antenna_emission/x1_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x1_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x1_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x2_unit_vector Components of the X2 direction unit vector in the (X,Y,Z) coordinate system, where X is the major radius axis for phi = 0, Y is the major radius axis for phi = pi/2, and Z is the height axis. The X2 axis is orthonormal so that uX2 = uX3 x uX1. Click here for further documentation. structure
channel(i1)/antenna_emission/x2_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x2_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x2_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x3_unit_vector Components of the X3 direction unit vector in the (X,Y,Z) coordinate system, where X is the major radius axis for phi = 0, Y is the major radius axis for phi = pi/2, and Z is the height axis. The X3 axis is normal to the detector/aperture plane and oriented towards the plasma. Click here for further documentation. structure
channel(i1)/antenna_emission/x3_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x3_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x3_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/antenna_emission/x1_width Full width of the aperture in the X1 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/antenna_emission/x2_width Full width of the aperture in the X2 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/antenna_emission/outline Irregular outline of the detector/aperture in the (X1, X2) coordinate system. Do NOT repeat the first point. structure
channel(i1)/antenna_emission/outline/x1(:) Positions along x1 axis {static} [m] FLT_1D 1- 1...N
channel(i1)/antenna_emission/outline/x2(:) Positions along x2 axis {static} [m] FLT_1D 1- channel(i1)/antenna_emission/outline/x1
channel(i1)/antenna_emission/surface Surface of the detector/aperture, derived from the above geometric data {static} [m^2] FLT_0D
channel(i1)/antenna_detection Geometry of the detection antenna, to be filled only if it is distinct from the emission antenna.. Introduced after DD version 3.38.1 structure
channel(i1)/antenna_detection/geometry_type Type of geometry used to describe the surface of the detector or aperture (1:'outline', 2:'circular', 3:'rectangle'). In case of 'outline', the surface is described by an outline of point in a local coordinate system defined by a centre and three unit vectors X1, X2, X3. Note that there is some flexibility here and the data provider should choose the most convenient coordinate system for the object, respecting the definitions of (X1,X2,X3) indicated below. In case of 'circular', the surface is a circle defined by its centre, radius, and normal vector oriented towards the plasma X3. In case of 'rectangle', the surface is a rectangle defined by its centre, widths in the X1 and X2 directions, and normal vector oriented towards the plasma X3. {static} INT_0D
channel(i1)/antenna_detection/centre If geometry_type=2, coordinates of the centre of the circle. If geometry_type=1 or 3, coordinates of the origin of the local coordinate system (X1,X2,X3) describing the plane detector/aperture. This origin is located within the detector/aperture area. structure
channel(i1)/antenna_detection/centre/r Major radius {static} [m] FLT_0D
channel(i1)/antenna_detection/centre/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/antenna_detection/centre/z Height {static} [m] FLT_0D
channel(i1)/antenna_detection/radius Radius of the circle, used only if geometry_type = 2 {static} [m] FLT_0D
channel(i1)/antenna_detection/x1_unit_vector Components of the X1 direction unit vector in the (X,Y,Z) coordinate system, where X is the major radius axis for phi = 0, Y is the major radius axis for phi = pi/2, and Z is the height axis. The X1 vector is more horizontal than X2 (has a smaller abs(Z) component) and oriented in the positive phi direction (counter-clockwise when viewing from above). Click here for further documentation. structure
channel(i1)/antenna_detection/x1_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x1_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x1_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x2_unit_vector Components of the X2 direction unit vector in the (X,Y,Z) coordinate system, where X is the major radius axis for phi = 0, Y is the major radius axis for phi = pi/2, and Z is the height axis. The X2 axis is orthonormal so that uX2 = uX3 x uX1. Click here for further documentation. structure
channel(i1)/antenna_detection/x2_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x2_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x2_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x3_unit_vector Components of the X3 direction unit vector in the (X,Y,Z) coordinate system, where X is the major radius axis for phi = 0, Y is the major radius axis for phi = pi/2, and Z is the height axis. The X3 axis is normal to the detector/aperture plane and oriented towards the plasma. Click here for further documentation. structure
channel(i1)/antenna_detection/x3_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x3_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x3_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/antenna_detection/x1_width Full width of the aperture in the X1 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/antenna_detection/x2_width Full width of the aperture in the X2 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/antenna_detection/outline Irregular outline of the detector/aperture in the (X1, X2) coordinate system. Do NOT repeat the first point. structure
channel(i1)/antenna_detection/outline/x1(:) Positions along x1 axis {static} [m] FLT_1D 1- 1...N
channel(i1)/antenna_detection/outline/x2(:) Positions along x2 axis {static} [m] FLT_1D 1- channel(i1)/antenna_detection/outline/x1
channel(i1)/antenna_detection/surface Surface of the detector/aperture, derived from the above geometric data {static} [m^2] FLT_0D
channel(i1)/sweep_time Duration of a sweep {static} [s] FLT_0D
channel(i1)/frequencies(:) Array of frequencies scanned during a sweep {static} [Hz] FLT_1D 1- 1...N
channel(i1)/phase Measured phase of the probing wave for each frequency and time slice (corresponding to the begin time of a sweep), relative to the phase at launch [rad] structure 1- channel(i1)/frequencies
2- channel(i1)/phase/time
channel(i1)/phase/data(:,:) Data {dynamic} [as_parent] FLT_2D 1- channel(i1)/frequencies
2- channel(i1)/phase/time
channel(i1)/phase/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
channel(i1)/amplitude Measured amplitude of the detected probing wave for each frequency and time slice (corresponding to the begin time of a sweep) [V]. Introduced after DD version 3.38.1 structure 1- channel(i1)/frequencies
2- channel(i1)/amplitude/time
channel(i1)/amplitude/data(:,:) Data {dynamic} [as_parent] FLT_2D 1- channel(i1)/frequencies
2- channel(i1)/amplitude/time
channel(i1)/amplitude/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
channel(i1)/position Position of the density measurements structure
channel(i1)/position/r(:,:) Major radius {dynamic} [m] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/position/phi(:,:) Toroidal angle (oriented counter-clockwise when viewing from above) {dynamic} [rad] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/position/z(:,:) Height {dynamic} [m] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/position/psi(:,:) Poloidal flux {dynamic} [W] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/position/rho_tor_norm(:,:) Normalised toroidal flux coordinate {dynamic} [-] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/position/rho_pol_norm(:,:) Normalised poloidal flux coordinate = sqrt((psi(rho)-psi(magnetic_axis)) / (psi(LCFS)-psi(magnetic_axis))) {dynamic} [-] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/position/theta(:,:) Poloidal angle (oriented clockwise when viewing the poloidal cross section on the right hand side of the tokamak axis of symmetry, with the origin placed on the plasma magnetic axis) {dynamic} [rad] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/n_e Electron density [m^-3] structure 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/n_e/data(:,:) Data {dynamic} [as_parent] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
channel(i1)/n_e/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
channel(i1)/cut_off_frequency(:,:) Cut-off frequency as a function of measurement position and time {dynamic} [Hz] FLT_2D 1- 1...N
2- channel(i1)/n_e/time
position Position associated to the density reconstruction from multiple channels structure
position/r(:,:) Major radius {dynamic} [m] FLT_2D 1- 1...N
2- n_e/time
position/phi(:,:) Toroidal angle (oriented counter-clockwise when viewing from above) {dynamic} [rad] FLT_2D 1- 1...N
2- n_e/time
position/z(:,:) Height {dynamic} [m] FLT_2D 1- 1...N
2- n_e/time
position/psi(:,:) Poloidal flux {dynamic} [W] FLT_2D 1- 1...N
2- n_e/time
position/rho_tor_norm(:,:) Normalised toroidal flux coordinate {dynamic} [-] FLT_2D 1- 1...N
2- n_e/time
position/rho_pol_norm(:,:) Normalised poloidal flux coordinate = sqrt((psi(rho)-psi(magnetic_axis)) / (psi(LCFS)-psi(magnetic_axis))) {dynamic} [-] FLT_2D 1- 1...N
2- n_e/time
position/theta(:,:) Poloidal angle (oriented clockwise when viewing the poloidal cross section on the right hand side of the tokamak axis of symmetry, with the origin placed on the plasma magnetic axis) {dynamic} [rad] FLT_2D 1- 1...N
2- n_e/time
n_e Electron density reconstructed from multiple channels [m^-3] structure 1- 1...N
2- n_e/time
n_e/data(:,:) Data {dynamic} [as_parent] FLT_2D 1- 1...N
2- n_e/time
n_e/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
psi_normalization Quantities to use to normalize psi, as a function of time structure
psi_normalization/psi_magnetic_axis(:) Value of the poloidal magnetic flux at the magnetic axis {dynamic} [Wb] FLT_1D 1- psi_normalization/time
psi_normalization/psi_boundary(:) Value of the poloidal magnetic flux at the plasma boundary {dynamic} [Wb] FLT_1D 1- psi_normalization/time
psi_normalization/time(:) Time for the R,Z,phi coordinates {dynamic} [s] FLT_1D 1- 1...N
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