ITER Physics Data Model Documentation for bolometer

Bolometer 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.7.4

Last change occured on version: 3.40.0

Back to top IDS list

By convention, only the upper error node should be filled in case of symmetrical error bars. The upper and lower errors are absolute and defined positive, and represent one standard deviation of the data. The effective values of the data (within one standard deviation) will be within the interval [data-data_error_lower, data+data_error_upper]. Thus whatever the sign of data, data_error_lower relates to the lower bound and data_error_upper to the upper bound of the error bar interval.

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/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
channel(i1) Set of channels (detector or pixel of a camera) array of structures [max_size=500 (limited in MDS+ backend only)] 1- 1...N
channel(i1)/name Short string identifier (unique for a given device) {static} STR_0D
channel(i1)/description Description, e.g. “channel viewing the upper divertor” {static}. Introduced after DD version 3 STR_0D
channel(i1)/detector Detector description structure
channel(i1)/detector/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)/detector/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)/detector/centre/r Major radius {static} [m] FLT_0D
channel(i1)/detector/centre/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/detector/centre/z Height {static} [m] FLT_0D
channel(i1)/detector/radius Radius of the circle, used only if geometry_type = 2 {static} [m] FLT_0D
channel(i1)/detector/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)/detector/x1_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/detector/x1_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/detector/x1_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/detector/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)/detector/x2_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/detector/x2_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/detector/x2_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/detector/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)/detector/x3_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/detector/x3_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/detector/x3_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/detector/x1_width Full width of the aperture in the X1 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/detector/x2_width Full width of the aperture in the X2 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/detector/outline Irregular outline of the detector/aperture in the (X1, X2) coordinate system. Repeat the first point since this is a closed contour structure
channel(i1)/detector/outline/x1(:) Positions along x1 axis {static} [m] FLT_1D 1- 1...N
channel(i1)/detector/outline/x2(:) Positions along x2 axis {static} [m] FLT_1D 1- channel(i1)/detector/outline/x1
channel(i1)/detector/surface Surface of the detector/aperture, derived from the above geometric data {static} [m^2] FLT_0D
channel(i1)/aperture(i2) Description of a set of collimating apertures array of structures [max_size=5 (limited in MDS+ backend only)] 1- 1...N
channel(i1)/aperture(i2)/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)/aperture(i2)/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)/aperture(i2)/centre/r Major radius {static} [m] FLT_0D
channel(i1)/aperture(i2)/centre/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/aperture(i2)/centre/z Height {static} [m] FLT_0D
channel(i1)/aperture(i2)/radius Radius of the circle, used only if geometry_type = 2 {static} [m] FLT_0D
channel(i1)/aperture(i2)/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)/aperture(i2)/x1_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x1_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x1_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/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)/aperture(i2)/x2_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x2_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x2_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/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)/aperture(i2)/x3_unit_vector/x Component along X axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x3_unit_vector/y Component along Y axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x3_unit_vector/z Component along Z axis {static} [m] FLT_0D
channel(i1)/aperture(i2)/x1_width Full width of the aperture in the X1 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/aperture(i2)/x2_width Full width of the aperture in the X2 direction, used only if geometry_type = 3 {static} [m] FLT_0D
channel(i1)/aperture(i2)/outline Irregular outline of the detector/aperture in the (X1, X2) coordinate system. Repeat the first point since this is a closed contour structure
channel(i1)/aperture(i2)/outline/x1(:) Positions along x1 axis {static} [m] FLT_1D 1- 1...N
channel(i1)/aperture(i2)/outline/x2(:) Positions along x2 axis {static} [m] FLT_1D 1- channel(i1)/aperture(i2)/outline/x1
channel(i1)/aperture(i2)/surface Surface of the detector/aperture, derived from the above geometric data {static} [m^2] FLT_0D
channel(i1)/etendue Etendue (geometric extent) of the channel's optical system {static} [m^2.sr] FLT_0D
channel(i1)/etendue_method Method used to calculate the etendue. Index = 0 : exact calculation with a 4D integral; 1 : approximation with first order formula (detector surface times solid angle subtended by the apertures); 2 : other methods structure
channel(i1)/etendue_method/name Short string identifier {static} STR_0D
channel(i1)/etendue_method/index Integer identifier (enumeration index within a list). Private identifier values must be indicated by a negative index. {static} INT_0D
channel(i1)/etendue_method/description Verbose description {static} STR_0D
channel(i1)/line_of_sight Description of the reference line of sight of the channel, defined by two points when the beam is not reflected, a third point is added to define the reflected beam path structure
channel(i1)/line_of_sight/first_point Position of the first point structure
channel(i1)/line_of_sight/first_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight/first_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight/first_point/z Height {static} [m] FLT_0D
channel(i1)/line_of_sight/second_point Position of the second point structure
channel(i1)/line_of_sight/second_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight/second_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight/second_point/z Height {static} [m] FLT_0D
channel(i1)/line_of_sight/third_point Position of the third point structure
channel(i1)/line_of_sight/third_point/r Major radius {static} [m] FLT_0D
channel(i1)/line_of_sight/third_point/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
channel(i1)/line_of_sight/third_point/z Height {static} [m] FLT_0D
channel(i1)/power Power received on the detector [W] structure
channel(i1)/power/data(:) Data {dynamic} [as_parent] FLT_1D 1- channel(i1)/power/time
channel(i1)/power/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
channel(i1)/validity_timed Indicator of the validity of the channel as a function of time (0 means valid, negative values mean non-valid) structure
channel(i1)/validity_timed/data(:) Data {dynamic} INT_1D 1- channel(i1)/validity_timed/time
channel(i1)/validity_timed/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
channel(i1)/validity Indicator of the validity of the channel for the whole acquisition period (0 means valid, negative values mean non-valid) {static} INT_0D
power_radiated_total(:) Total radiated power reconstructed from bolometry data {dynamic} [W] FLT_1D 1- time
power_radiated_inside_lcfs(:) Radiated power from the plasma inside the Last Closed Flux Surface, reconstructed from bolometry data {dynamic} [W] FLT_1D 1- time
power_radiated_validity(:) Validity flag related to the radiated power reconstructions {dynamic} INT_1D 1- time
grid_type Selection of one of a set of grid types for the 2D power density map. Introduced after DD version 3.39.0. Available options (refer to the children of this identifier structure) :
Name Index Description
rectangular 1 Cylindrical R,Z ala eqdsk (R=dim1, Z=dim2). In this case the position arrays should not be filled since they are redundant with grid/dim1 and dim2.
inverse 2 Rhopolar_polar 2D polar coordinates (rho=dim1, theta=dim2) with magnetic axis as centre of grid; the polar angle is theta= -atan2(z-zaxis,r-raxis).
inverse_psi_straight_field_line 11 Flux surface type with psi as radial label (dim1) and the straight-field line poloidal angle (mod(index,10)=1) (dim2); could be non-equidistant; magnetic axis as centre of grid
inverse_psi_equal_arc 12 Flux surface type with psi as radial label (dim1) and the equal arc poloidal angle (mod(index,10)=2) (dim2)
inverse_psi_polar 13 Flux surface type with psi as radial label (dim1) and the polar poloidal angle (mod(index,10)=3) (dim2); could be non-equidistant
inverse_psi_straight_field_line_fourier 14 Flux surface type with psi as radial label (dim1) and Fourier modes in the straight-field line poloidal angle (mod(index,10)=4) (dim2), could be non-equidistant; magnetic axis as centre of grid
inverse_psi_equal_arc_fourier 15 Flux surface type with psi as radial label (dim1) and Fourier modes in the equal arc poloidal angle (mod(index,10)=5) (dim2)
inverse_psi_polar_fourier 16 Flux surface type with psi as radial label (dim1) and Fourier modes in the polar poloidal angle (mod(index,10)=6) (dim2); could be non-equidistant
inverse_rhopolnorm_straight_field_line 21 Flux surface type with radial label sqrt[(psi-psi_axis)/(psi_edge-psi_axis)] (dim1) and the straight-field line poloidal angle (dim2)
inverse_rhopolnorm_equal_arc 22 Flux surface type with radial label sqrt[(psi-psi_axis)/(psi_edge-psi_axis)] (dim1) and the equal arc poloidal angle (dim2)
inverse_rhopolnorm_polar 23 Flux surface type with radial label sqrt[(psi-psi_axis)/(psi_edge-psi_axis)] (dim1) and the polar poloidal angle (dim2)
inverse_rhopolnorm_straight_field_line_fourier 24 Flux surface type with radial label sqrt[(psi-psi_axis)/(psi_edge-psi_axis)] (dim1) and Fourier modes in the straight-field line poloidal angle (dim2)
inverse_rhopolnorm_equal_arc_fourier 25 Flux surface type with radial label sqrt[(psi-psi_axis)/(psi_edge-psi_axis)] (dim1) and Fourier modes in the equal arc poloidal angle (dim2)
inverse_rhopolnorm_polar_fourier 26 Flux surface type with radial label sqrt[(psi-psi_axis)/(psi_edge-psi_axis)] (dim1) and Fourier modes in the polar poloidal angle (dim2)
inverse_rhotornorm_straight_field_line 31 Flux surface type with radial label sqrt[Phi/Phi_edge] (dim1) and the straight-field line poloidal angle (dim2)
inverse_rhotornorm_equal_arc 32 Flux surface type with radial label sqrt[Phi/Phi_edge] (dim1) and the equal arc poloidal angle (dim2)
inverse_rhotornorm_polar 33 Flux surface type with radial label sqrt[Phi/Phi_edge] (dim1) and the polar poloidal angle (dim2)
inverse_rhotornorm_straight_field_line_fourier 34 Flux surface type with radial label sqrt[Phi/Phi_edge] (dim1) and Fourier modes in the straight-field line poloidal angle (dim2)
inverse_rhotornorm_equal_arc_fourier 35 Flux surface type with radial label sqrt[Phi/Phi_edge] (dim1) and Fourier modes in the equal arc poloidal angle (dim2)
inverse_rhotornorm_polar_fourier 36 Flux surface type with radial label sqrt[Phi/Phi_edge] (dim1) and Fourier modes in the polar poloidal angle (dim2)
inverse_rhopol_straight_field_line 41 Flux surface type with radial label sqrt[psi-psi_axis] (dim1) and the straight-field line poloidal angle (dim2)
inverse_rhopol_equal_arc 42 Flux surface type with radial label sqrt[psi-psi_axis] (dim1) and the equal arc poloidal angle (dim2)
inverse_rhopol_polar 43 Flux surface type with radial label sqrt[psi-psi_axis] (dim1) and the polar poloidal angle (dim2)
inverse_rhopol_straight_field_line_fourier 44 Flux surface type with radial label sqrt[psi-psi_axis] (dim1) and Fourier modes in the straight-field line poloidal angle (dim2)
inverse_rhopol_equal_arc_fourier 45 Flux surface type with radial label sqrt[psi-psi_axis] (dim1) and Fourier modes in the equal arc poloidal angle (dim2)
inverse_rhopol_polar_fourier 46 Flux surface type with radial label sqrt[psi-psi_axis] (dim1) and Fourier modes in the polar poloidal angle (dim2)
inverse_rhotor_straight_field_line 51 Flux surface type with radial label sqrt[Phi/pi/B0] (dim1), Phi being toroidal flux, and the straight-field line poloidal angle (dim2)
inverse_rhotor_equal_arc 52 Flux surface type with radial label sqrt[Phi/pi/B0] (dim1), Phi being toroidal flux, and the equal arc poloidal angle (dim2)
inverse_rhotor_polar 53 Flux surface type with radial label sqrt[Phi/pi/B0] (dim1), Phi being toroidal flux, and the polar poloidal angle (dim2)
inverse_rhotor_straight_field_line_fourier 54 Flux surface type with radial label sqrt[Phi/pi/B0] (dim1), Phi being toroidal flux, and Fourier modes in the straight-field line poloidal angle (dim2)
inverse_rhotor_equal_arc_fourier 55 Flux surface type with radial label sqrt[Phi/pi/B0] (dim1), Phi being toroidal flux, and Fourier modes in the equal arc poloidal angle (dim2)
inverse_rhotor_polar_fourier 56 Flux surface type with radial label sqrt[Phi/pi/B0] (dim1), Phi being toroidal flux, and Fourier modes in the polar poloidal angle (dim2)
irregular_rz_na 91 Irregular grid, thus give list of vertices in dim1(1:ndim1), dim2(1:ndim1) and then all fields are on values(1:ndim1,1)
structure
grid_type/name Short string identifier {constant} STR_0D
grid_type/index Integer identifier (enumeration index within a list). Private identifier values must be indicated by a negative index. {constant} INT_0D
grid_type/description Verbose description {constant} STR_0D
grid Definition of the 2D grid (the content of dim1 and dim2 is defined by the selected grid_type). Introduced after DD version 3.39.0 structure
grid/dim1(:) First dimension values {constant} [mixed] FLT_1D 1- 1...N
grid/dim2(:) Second dimension values {constant} [mixed] FLT_1D 1- 1...N
grid/volume_element(:,:) Volume of plasma enclosed in the cell formed by the nodes [dim1(i) dim2(j)], [dim1(i+1) dim2(j)], [dim1(i) dim2(j+1)] and [dim1(i+1) dim2(j+1)] {constant} [m^3] FLT_2D 1- grid/dim1
2- grid/dim2
power_density Power density map in the poloidal cross-section, obtained from tomographic inversion of the bolometer data [W.m^-3]. Introduced after DD version 3.39.0 structure 1- grid/dim1
2- grid/dim2
power_density/data(:,:,:) Data {dynamic} [as_parent] FLT_3D 1- grid/dim1
2- grid/dim2
3- power_density/time
power_density/time(:) Time {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