ITER Physics Data Model Documentation for nbi

Neutral Beam Injection systems and description of the fast neutrals that arrive into the torus

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: active since version 4.0.0

Last change occured on version: 3.33.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
unit(i1) The NBI system is described as a set of units of which the power can be controlled individually. array of structures [max_size=32 (limited in MDS+ backend only)] 1- 1...N
unit(i1)/name Short string identifier (unique for a given device) {static} STR_0D
unit(i1)/description Description, e.g. “channel viewing the upper divertor” {static}. Introduced after DD version 3 STR_0D
unit(i1)/species Injected species structure
unit(i1)/species/a Mass of atom {constant} [Atomic Mass Unit] FLT_0D
unit(i1)/species/z_n Nuclear charge {constant} [Elementary Charge Unit] INT_0D
unit(i1)/species/name String identifying the species (e.g. H, D, T, ...) {constant} STR_0D
unit(i1)/power_launched Power launched from this unit into the vacuum vessel [W] structure
unit(i1)/power_launched/data(:) Data {dynamic} [as_parent] FLT_1D 1- unit(i1)/power_launched/time
unit(i1)/power_launched/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
unit(i1)/energy Full energy of the injected species (acceleration of a single atom) [eV] structure
unit(i1)/energy/data(:) Data {dynamic} [as_parent] FLT_1D 1- unit(i1)/energy/time
unit(i1)/energy/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
unit(i1)/beam_current_fraction Fractions of beam current distributed among the different energies, the first index corresponds to the fast neutrals energy (1:full, 2: half, 3: one third) [-] structure 1- 1...3
2- unit(i1)/beam_current_fraction/time
unit(i1)/beam_current_fraction/data(:,:) Data {dynamic} [as_parent] FLT_2D 1- 1...3
2- unit(i1)/beam_current_fraction/time
unit(i1)/beam_current_fraction/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
unit(i1)/beam_power_fraction Fractions of beam power distributed among the different energies, the first index corresponds to the fast neutrals energy (1:full, 2: half, 3: one third) [-] structure 1- 1...3
2- unit(i1)/beam_power_fraction/time
unit(i1)/beam_power_fraction/data(:,:) Data {dynamic} [as_parent] FLT_2D 1- 1...3
2- unit(i1)/beam_power_fraction/time
unit(i1)/beam_power_fraction/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
unit(i1)/beamlets_group(i2) Group of beamlets with common vertical and horizontal focal point. If there are no common focal points, then select small groups of beamlets such that a focal point description of the beamlets group provides a fair description. Beamlet groups are assumed to be Gaussian. array of structures [max_size=16 (limited in MDS+ backend only)] 1- 1...N
unit(i1)/beamlets_group(i2)/position R, Z, Phi position of the beamlet group centre structure
unit(i1)/beamlets_group(i2)/position/r Major radius {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/position/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
unit(i1)/beamlets_group(i2)/position/z Height {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/tangency_radius Tangency radius (major radius where the central line of a NBI unit is tangent to a circle around the torus) {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/angle Angle of inclination between a beamlet at the centre of the injection unit surface and the horiontal plane {static} [rad] FLT_0D
unit(i1)/beamlets_group(i2)/tilting(itime) In case of dynamic beam tilting (i.e. during the pulse), e.g. for some Beam Emission Spectroscopy use cases, variations of position, tangency radius and angle with respect to their static value, for various time slices {dynamic} array of structures 1- unit(i1)/beamlets_group(i2)/tilting(itime)/time
unit(i1)/beamlets_group(i2)/tilting(itime)/delta_position Variation of the position of the beamlet group centre structure
unit(i1)/beamlets_group(i2)/tilting(itime)/delta_position/r Major radius {dynamic} [m] FLT_0D
unit(i1)/beamlets_group(i2)/tilting(itime)/delta_position/phi Toroidal angle (oriented counter-clockwise when viewing from above) {dynamic} [rad] FLT_0D
unit(i1)/beamlets_group(i2)/tilting(itime)/delta_position/z Height {dynamic} [m] FLT_0D
unit(i1)/beamlets_group(i2)/tilting(itime)/delta_tangency_radius Variation of the tangency radius (major radius where the central line of a NBI unit is tangent to a circle around the torus) {dynamic} [m] FLT_0D
unit(i1)/beamlets_group(i2)/tilting(itime)/delta_angle Variation of the angle of inclination between a beamlet at the centre of the injection unit surface and the horiontal plane {dynamic} [rad] FLT_0D
unit(i1)/beamlets_group(i2)/tilting(itime)/time Time {dynamic} [s] FLT_0D
unit(i1)/beamlets_group(i2)/direction Direction of the beam seen from above the torus: -1 = clockwise; 1 = counter clockwise {static} INT_0D
unit(i1)/beamlets_group(i2)/width_horizontal Horizontal width (dimensions of the smallest rectangle that surrounds the outer dimensions of the beamlets) of the beamlet group at the injection unit surface (or grounded grid) {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/width_vertical Vertical width (dimensions of the smallest rectangle that surrounds the outer dimensions of the beamlets) of the beamlet group at the injection unit surface (or grounded grid) {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/focus Describes how the beamlet group is focused. Calculations of width_min_horizontal and width_min_vertical are on a plane defined by the average normal vector of the two constituent accelerator nbi target planes. structure
unit(i1)/beamlets_group(i2)/focus/focal_length_horizontal Horizontal focal length along the beam line, i.e. the point along the centre of the beamlet-group where the beamlet-group has its minimum horizontal width {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/focus/focal_length_vertical Vertical focal length along the beam line, i.e. the point along the centre of the beamlet-group where the beamlet-group has its minimum vertical width {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/focus/width_min_horizontal The horizontal width (Full Width at Half Maximum) of the beamlets group at the horizontal focal point {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/focus/width_min_vertical The vertical width (Full Width at Half Maximum) of the beamlets group at the vertical focal point {static} [m] FLT_0D
unit(i1)/beamlets_group(i2)/divergence_component(i3) Detailed information on beamlet divergence. Divergence is described as a superposition of Gaussian components with amplitide "particles_fraction" and vertical/horizontal divergence. Note that for positive ion NBI the divergence is well described by a single Gaussian array of structures [max_size=3 (limited in MDS+ backend only)] 1- 1...N
unit(i1)/beamlets_group(i2)/divergence_component(i3)/particles_fraction Fraction of injected particles in the component {static} [-] FLT_0D
unit(i1)/beamlets_group(i2)/divergence_component(i3)/vertical The vertical beamlet divergence of the component. Here the divergence is defined for Gaussian beams as the angel where the beam density is reduced by a factor 1/e compared to the maximum density. For non-Gaussian beams the divergence is sqrt(2)*mean((x-mean(x))**2), where x is the angle and the mean should be performed over the beam density, P(x): mean(y)=int(y*P(x)*dx). {static} [rad] FLT_0D
unit(i1)/beamlets_group(i2)/divergence_component(i3)/horizontal The horiztonal beamlet divergence of the component. Here the divergence is defined for Gaussian beams as the angel where the beam density is reduced by a factor 1/e compared to the maximum density. For non-Gaussian beams the divergence is sqrt(2)*mean((x-mean(x))**2), where x is the angle and the mean should be performed over the beam density, P(x): mean(y)=int(y*P(x)*dx). {static} [rad] FLT_0D
unit(i1)/beamlets_group(i2)/beamlets Detailed information on beamlets structure
unit(i1)/beamlets_group(i2)/beamlets/positions Position of each beamlet structure
unit(i1)/beamlets_group(i2)/beamlets/positions/r(:) Major radius {static} [m] FLT_1D 1- 1...N
unit(i1)/beamlets_group(i2)/beamlets/positions/phi(:) Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_1D 1- unit(i1)/beamlets_group(i2)/beamlets/positions/r
unit(i1)/beamlets_group(i2)/beamlets/positions/z(:) Height {static} [m] FLT_1D 1- unit(i1)/beamlets_group(i2)/beamlets/positions/r
unit(i1)/beamlets_group(i2)/beamlets/tangency_radii(:) Tangency radius (major radius where the central line of a beamlet is tangent to a circle around the torus), for each beamlet {static} [m] FLT_1D 1- unit(i1)/beamlets_group(i2)/beamlets/positions/r
unit(i1)/beamlets_group(i2)/beamlets/angles(:) Angle of inclination between a line at the centre of a beamlet and the horizontal plane, for each beamlet {static} [rad] FLT_1D 1- unit(i1)/beamlets_group(i2)/beamlets/positions/r
unit(i1)/beamlets_group(i2)/beamlets/power_fractions(:) Fraction of power of a unit injected by each beamlet {static} [-] FLT_1D 1- unit(i1)/beamlets_group(i2)/beamlets/positions/r
unit(i1)/source Description of the surface of the ion source from which the beam is extracted structure
unit(i1)/source/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
unit(i1)/source/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
unit(i1)/source/centre/r Major radius {static} [m] FLT_0D
unit(i1)/source/centre/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
unit(i1)/source/centre/z Height {static} [m] FLT_0D
unit(i1)/source/radius Radius of the circle, used only if geometry_type = 2 {static} [m] FLT_0D
unit(i1)/source/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
unit(i1)/source/x1_unit_vector/x Component along X axis {static} [m] FLT_0D
unit(i1)/source/x1_unit_vector/y Component along Y axis {static} [m] FLT_0D
unit(i1)/source/x1_unit_vector/z Component along Z axis {static} [m] FLT_0D
unit(i1)/source/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
unit(i1)/source/x2_unit_vector/x Component along X axis {static} [m] FLT_0D
unit(i1)/source/x2_unit_vector/y Component along Y axis {static} [m] FLT_0D
unit(i1)/source/x2_unit_vector/z Component along Z axis {static} [m] FLT_0D
unit(i1)/source/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
unit(i1)/source/x3_unit_vector/x Component along X axis {static} [m] FLT_0D
unit(i1)/source/x3_unit_vector/y Component along Y axis {static} [m] FLT_0D
unit(i1)/source/x3_unit_vector/z Component along Z axis {static} [m] FLT_0D
unit(i1)/source/x1_width Full width of the aperture in the X1 direction, used only if geometry_type = 3 {static} [m] FLT_0D
unit(i1)/source/x2_width Full width of the aperture in the X2 direction, used only if geometry_type = 3 {static} [m] FLT_0D
unit(i1)/source/outline Irregular outline of the detector/aperture in the (X1, X2) coordinate system. Repeat the first point since this is a closed contour structure
unit(i1)/source/outline/x1(:) Positions along x1 axis {static} [m] FLT_1D 1- 1...N
unit(i1)/source/outline/x2(:) Positions along x2 axis {static} [m] FLT_1D 1- unit(i1)/source/outline/x1
unit(i1)/source/surface Surface of the detector/aperture, derived from the above geometric data {static} [m^2] FLT_0D
unit(i1)/aperture(i2) Description of a set of collimating apertures through which the beam is launched array of structures [max_size=5 (limited in MDS+ backend only)] 1- 1...N
unit(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
unit(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
unit(i1)/aperture(i2)/centre/r Major radius {static} [m] FLT_0D
unit(i1)/aperture(i2)/centre/phi Toroidal angle (oriented counter-clockwise when viewing from above) {static} [rad] FLT_0D
unit(i1)/aperture(i2)/centre/z Height {static} [m] FLT_0D
unit(i1)/aperture(i2)/radius Radius of the circle, used only if geometry_type = 2 {static} [m] FLT_0D
unit(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
unit(i1)/aperture(i2)/x1_unit_vector/x Component along X axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x1_unit_vector/y Component along Y axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x1_unit_vector/z Component along Z axis {static} [m] FLT_0D
unit(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
unit(i1)/aperture(i2)/x2_unit_vector/x Component along X axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x2_unit_vector/y Component along Y axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x2_unit_vector/z Component along Z axis {static} [m] FLT_0D
unit(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
unit(i1)/aperture(i2)/x3_unit_vector/x Component along X axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x3_unit_vector/y Component along Y axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x3_unit_vector/z Component along Z axis {static} [m] FLT_0D
unit(i1)/aperture(i2)/x1_width Full width of the aperture in the X1 direction, used only if geometry_type = 3 {static} [m] FLT_0D
unit(i1)/aperture(i2)/x2_width Full width of the aperture in the X2 direction, used only if geometry_type = 3 {static} [m] FLT_0D
unit(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
unit(i1)/aperture(i2)/outline/x1(:) Positions along x1 axis {static} [m] FLT_1D 1- 1...N
unit(i1)/aperture(i2)/outline/x2(:) Positions along x2 axis {static} [m] FLT_1D 1- unit(i1)/aperture(i2)/outline/x1
unit(i1)/aperture(i2)/surface Surface of the detector/aperture, derived from the above geometric data {static} [m^2] FLT_0D
latency Upper bound of the delay between input command received from the RT network and actuator starting to react. Applies globally to the system described by this IDS unless specific latencies (e.g. channel-specific or antenna-specific) are provided at a deeper level in the IDS structure. {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