ITER Physics Data Model Documentation for ec_launchers

Launchers for heating and current drive in the electron cyclotron (EC) frequencies.

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

Last change occured on version: 3.37.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/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/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} struct_array [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)/sources(:) List of sources used to import or calculate this node, identified as explained below. In case the node is the result of of a calculation / data processing, the source is an input to the process described in the "code" structure at the root of the IDS. The source 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 source, or the persistent identifier of the data source). 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 sources. Click here for further documentation. {constant} STR_1D 1- 1...N
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} struct_array [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) struct_array [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) struct_array [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. struct_array [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
beam(i1) Set of Electron Cyclotron beams. Introduced after DD version 3.36.0 struct_array [max_size=100 (limited in MDS+ backend only)] 1- 1...N
beam(i1)/name Beam name {static} STR_0D
beam(i1)/identifier Beam identifier {static} STR_0D
beam(i1)/frequency Frequency [Hz] structure
beam(i1)/frequency/data(:) Data {dynamic} [as_parent] FLT_1D 1- beam(i1)/frequency/time
beam(i1)/frequency/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
beam(i1)/power_launched Beam power launched into the vacuum vessel [W] structure
beam(i1)/power_launched/data(:) Data {dynamic} [as_parent] FLT_1D 1- beam(i1)/power_launched/time
beam(i1)/power_launched/time(:) Time {dynamic} [s] FLT_1D 1- 1...N
beam(i1)/mode Identifier for the main plasma wave mode excited by the EC beam. For the ordinary mode (O-mode), mode=1. For the extraordinary mode (X-mode), mode=-1 {constant} INT_0D
beam(i1)/launching_position Launching position of the beam structure
beam(i1)/launching_position/r(:) Major radius {dynamic} [m] FLT_1D 1- beam(i1)/time
beam(i1)/launching_position/r_limit_min Major radius lower limit for the system {static} [m]. Introduced after DD version 3.32.1 FLT_0D
beam(i1)/launching_position/r_limit_max Major radius upper limit for the system {static} [m]. Introduced after DD version 3.32.1 FLT_0D
beam(i1)/launching_position/z(:) Height {dynamic} [m] FLT_1D 1- beam(i1)/time
beam(i1)/launching_position/phi(:) Toroidal angle {dynamic} [rad] FLT_1D 1- beam(i1)/time
beam(i1)/steering_angle_pol(:) Steering angle of the EC beam in the R,Z plane (from the -R axis towards the -Z axis), angle_pol=atan2(-k_Z,-k_R), where k_Z and k_R are the Z and R components of the mean wave vector in the EC beam {dynamic} [rad] FLT_1D 1- beam(i1)/time
beam(i1)/steering_angle_tor(:) Steering angle of the EC beam away from the poloidal plane that is increasing towards the positive phi axis, angle_tor=arcsin(k_phi/k), where k_phi is the component of the wave vector in the phi direction and k is the length of the wave vector. Here the term wave vector refers to the mean wave vector in the EC beam {dynamic} [rad]. This quantity is COCOS-dependent, with the following transformation :
Label Expression
tor_angle_like .sigma_rphiz_eff
FLT_1D 1- beam(i1)/time
beam(i1)/spot Spot ellipse characteristics at launch structure
beam(i1)/spot/size(:,:) Size of the spot ellipse: distance between the central ray and the peripheral rays in the horizontal (first index of the first coordinate) and vertical direction (second index of the first coordinate) {dynamic} [m] FLT_2D 1- 1...2
2- beam(i1)/time
beam(i1)/spot/angle(:) Rotation angle for the spot ellipse {dynamic} [rad] FLT_1D 1- beam(i1)/time
beam(i1)/phase Phase ellipse characteristics at launch structure
beam(i1)/phase/curvature(:,:) Inverse curvature radii for the phase ellipse, positive/negative for divergent/convergent beams, in the horizontal direction (first index of the first coordinate) and in the vertical direction (second index of the first coordinate) {dynamic} [m^-1] FLT_2D 1- 1...2
2- beam(i1)/time
beam(i1)/phase/angle(:) Rotation angle for the phase ellipse {dynamic} [rad] FLT_1D 1- beam(i1)/time
beam(i1)/time(:) Time base used for position, angle, spot and phase quantities {dynamic} [s] FLT_1D 1- 1...N
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 struct_array [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