ITER Physics Data Model Documentation for refractometer
Density profile refractometer 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.31.0
Last change occured on version: 3.33.0
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/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 | ||||||||||
type | Type of refractometer (differential, impulse, ...) {static} | STR_0D | ||||||||||
channel(i1) | Set of channels, e.g. different reception antennas of the refractometer | struct_array [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 | Description of the line of sight. The first point corresponds to the probing wave emission point. The second point corresponds to the probing wave detection point | 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/z | Height {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/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/z | Height {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)/bandwidth(i2) | Set of frequency bandwidths | struct_array [max_size=10 (limited in MDS+ backend only)] |
1- 1...N |
|||||||||
channel(i1)/bandwidth(i2)/frequency_main | Main frequency used to probe the plasma (before upshifting and modulating) {static} [Hz] | FLT_0D | ||||||||||
channel(i1)/bandwidth(i2)/phase(:) | Phase of the envelope of the probing signal, relative to the phase at launch {dynamic} [rad]. Introduced after DD version 3.32.1 | FLT_1D |
1- channel(i1)/bandwidth(i2)/time |
|||||||||
channel(i1)/bandwidth(i2)/i_component(:,:) | I component of the IQ detector used to retrieve the phase of signal's envelope, sampled on a high resolution time_detector grid just before each measurement time slice represented by the ../time vector {dynamic} [V]. Introduced after DD version 3.32.1 | FLT_2D |
1- 1...N 2- channel(i1)/bandwidth(i2)/time |
|||||||||
channel(i1)/bandwidth(i2)/q_component(:,:) | Q component of the IQ detector used to retrieve the phase of signal's envelope, sampled on a high resolution time_detector grid just before each measurement time slice represented by the ../time vector {dynamic} [V]. Introduced after DD version 3.32.1 | FLT_2D |
1- 1...N 2- channel(i1)/bandwidth(i2)/time |
|||||||||
channel(i1)/bandwidth(i2)/n_e_line | Integral of the electron density along the line of sight, deduced from the envelope phase measurements [m^-2] | structure |
1- channel(i1)/bandwidth(i2)/n_e_line/time |
|||||||||
channel(i1)/bandwidth(i2)/n_e_line/data(:) | Data {dynamic} [as_parent] | FLT_1D |
1- channel(i1)/bandwidth(i2)/n_e_line/time |
|||||||||
channel(i1)/bandwidth(i2)/n_e_line/time(:) | Time {dynamic} [s] | FLT_1D |
1- 1...N |
|||||||||
channel(i1)/bandwidth(i2)/phase_quadrature | In-phase and Quadrature components of the analysed signal. They are returned by an IQ-detector, that takes carrying and reference signals as the input and yields I and Q components. These are respectively stored as the first and the second index of the first dimension of the data child. [V] | structure |
1- 1...2 2- channel(i1)/bandwidth(i2)/phase_quadrature/time |
|||||||||
channel(i1)/bandwidth(i2)/phase_quadrature/data(:,:) | Data {dynamic} [as_parent] | FLT_2D |
1- 1...N 2- channel(i1)/bandwidth(i2)/phase_quadrature/time |
|||||||||
channel(i1)/bandwidth(i2)/phase_quadrature/time(:) | Time {dynamic} [s] | FLT_1D |
1- 1...N |
|||||||||
channel(i1)/bandwidth(i2)/time_detector(:,:) | High sampling timebase of the IQ-detector signal measurements {dynamic} [s]. Introduced after DD version 3.32.1 | FLT_2D |
1- 1...N 2- channel(i1)/bandwidth(i2)/time |
|||||||||
channel(i1)/bandwidth(i2)/time(:) | Timebase for this bandwidth {dynamic} [s]. Introduced after DD version 3.32.1 | FLT_1D |
1- 1...N |
|||||||||
channel(i1)/n_e_line | Integral of the electron density along the line of sight, deduced from the envelope phase measurements [m^-2] | structure |
1- channel(i1)/n_e_line/time |
|||||||||
channel(i1)/n_e_line/data(:) | Data {dynamic} [as_parent] | FLT_1D |
1- channel(i1)/n_e_line/time |
|||||||||
channel(i1)/n_e_line/time(:) | Time {dynamic} [s] | FLT_1D |
1- 1...N |
|||||||||
channel(i1)/n_e_profile_approximation | Approximation of the radial electron density profile with an array of parameters and an approximation formula, used by post-processing programs for the identification of the electron density profile. | structure | ||||||||||
channel(i1)/n_e_profile_approximation/formula | Analytical formula representing the electron density profile as a function of a radial
coordinate and adjustable parameters f(rho_tor_norm, alpha1, ... alphaN). Available options (refer to the children of this identifier structure) :
|
structure | ||||||||||
channel(i1)/n_e_profile_approximation/formula/name | Short string identifier {constant} | STR_0D | ||||||||||
channel(i1)/n_e_profile_approximation/formula/index | Integer identifier (enumeration index within a list). Private identifier values must be indicated by a negative index. {constant} | INT_0D | ||||||||||
channel(i1)/n_e_profile_approximation/formula/description | Verbose description {constant} | STR_0D | ||||||||||
channel(i1)/n_e_profile_approximation/parameters(:,:) | Values of the formula's parameters alpha1, ..., alphaN {dynamic} [mixed] | FLT_2D |
1- 1...N 2- channel(i1)/n_e_line/time |
|||||||||
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 | 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 |