amns_data¶
Atomic, molecular, nuclear and surface physics data. Each occurrence contains the data for a given element (nuclear charge), describing various physical processes. For each process, data tables are organized by charge states. The coordinate system used by the data tables is described under the coordinate_system node.
Maximum occurrences (MDS+ backend only): 2
New in version 3.0.0: lifecycle status alpha
Changed in version 3.42.0.
ids_propertiesstructure¶
See common IDS structure reference: ids_properties.
process(i1)AoS¶Description and data for a set of physical processes.
Description and data for a set of physical processes.
Maximum occurrences (MDS+ backend only): 20
1 |
|
process(i1)/sourceSTR_0D¶Filename or subroutine name used to provide this data
Filename or subroutine name used to provide this data
process(i1)/providerSTR_0D¶Name of the person in charge of producing this data
Name of the person in charge of producing this data
process(i1)/nameSTR_0D¶String identifying the process (e.g. […]
String identifying the process (e.g. EI, RC, …)
Changed in version 3.42.0: Renamed from label
process(i1)/reactants(i2)AoS¶Set of reactants involved in this process
Set of reactants involved in this process
Maximum occurrences (MDS+ backend only): 5
1 |
|
process(i1)/reactants(i2)/nameSTR_0D¶String identifying reaction participant (e.g. […]
String identifying reaction participant (e.g. “D”, “e”, “W”, “CD4”, “photon”, “n”)
Changed in version 3.42.0: Renamed from label
process(i1)/reactants(i2)/element(i3)AoS¶List of elements forming the atom (in such case, this array should […]
List of elements forming the atom (in such case, this array should be of size 1) or molecule. Mass of atom and nuclear charge should be set to 0 for photons and electrons. The mass of atom shouldn’t be set for an atomic process that is not isotope dependent.
Maximum occurrences (MDS+ backend only): 5
1 |
|
process(i1)/reactants(i2)/rolestructure¶Identifier for the role of this paricipant in the reaction. […]
Identifier for the role of this paricipant in the reaction. For surface reactions distinguish between projectile and wall.
process(i1)/reactants(i2)/charge ⇹1FLT_0D¶Charge number of the participant
Charge number of the participant
process(i1)/reactants(i2)/relative_chargeINT_0D¶This is a flag indicating that charges are absolute (if set to […]
This is a flag indicating that charges are absolute (if set to 0), relative (if 1) or irrelevant (-1); relative would be used to categorize the ionization reactions from i to i+1 for all charge states; in the case of bundles, the +1 relative indicates the next bundle
process(i1)/reactants(i2)/multiplicity ⇹1FLT_0D¶Multiplicity in the reaction
Multiplicity in the reaction
process(i1)/reactants(i2)/metastable(:)INT_1D¶An array identifying the metastable; if zero-length, then not […]
An array identifying the metastable; if zero-length, then not a metastable; if of length 1, then the value indicates the electronic level for the metastable (mostly used for atoms/ions); if of length 2, then the 1st would indicate the electronic level and the second the vibrational level for the metastable (mostly used for molecules and molecular ions); if of length 3, then the 1st would indicate the electronic level, the second the vibrational level and the third the rotational level for the metastable (mostly used for molecules and molecular ions)
1 |
|
process(i1)/products(i2)AoS¶Set of products resulting of this process
Set of products resulting of this process
Maximum occurrences (MDS+ backend only): 5
1 |
|
process(i1)/products(i2)/nameSTR_0D¶String identifying reaction participant (e.g. […]
String identifying reaction participant (e.g. “D”, “e”, “W”, “CD4”, “photon”, “n”)
Changed in version 3.42.0: Renamed from label
process(i1)/products(i2)/element(i3)AoS¶List of elements forming the atom (in such case, this array should […]
List of elements forming the atom (in such case, this array should be of size 1) or molecule. Mass of atom and nuclear charge should be set to 0 for photons and electrons. The mass of atom shouldn’t be set for an atomic process that is not isotope dependent.
Maximum occurrences (MDS+ backend only): 5
1 |
|
process(i1)/products(i2)/rolestructure¶Identifier for the role of this paricipant in the reaction. […]
Identifier for the role of this paricipant in the reaction. For surface reactions distinguish between projectile and wall.
process(i1)/products(i2)/charge ⇹1FLT_0D¶Charge number of the participant
Charge number of the participant
process(i1)/products(i2)/relative_chargeINT_0D¶This is a flag indicating that charges are absolute (if set to […]
This is a flag indicating that charges are absolute (if set to 0), relative (if 1) or irrelevant (-1); relative would be used to categorize the ionization reactions from i to i+1 for all charge states; in the case of bundles, the +1 relative indicates the next bundle
process(i1)/products(i2)/multiplicity ⇹1FLT_0D¶Multiplicity in the reaction
Multiplicity in the reaction
process(i1)/products(i2)/metastable(:)INT_1D¶An array identifying the metastable; if zero-length, then not […]
An array identifying the metastable; if zero-length, then not a metastable; if of length 1, then the value indicates the electronic level for the metastable (mostly used for atoms/ions); if of length 2, then the 1st would indicate the electronic level and the second the vibrational level for the metastable (mostly used for molecules and molecular ions); if of length 3, then the 1st would indicate the electronic level, the second the vibrational level and the third the rotational level for the metastable (mostly used for molecules and molecular ions)
1 |
|
process(i1)/table_dimensionINT_0D¶Table dimensionality of the process (1 to 6), valid for all charge […]
Table dimensionality of the process (1 to 6), valid for all charge states. Indicates which of the tables is filled (below the charge_state node)
process(i1)/coordinate_indexINT_0D¶Index in tables_coord, specifying what coordinate systems to […]
Index in tables_coord, specifying what coordinate systems to use for this process (valid for all tables)
process(i1)/result_labelSTR_0D¶Description of the process result (rate, cross section, sputtering […]
Description of the process result (rate, cross section, sputtering yield, …)
process(i1)/result_transformationINT_0D¶Transformation of the process result. […]
Transformation of the process result. Integer flag: 0=no transformation; 1=10^; 2=exp()
process(i1)/charge_state(i2)AoS¶Process tables for a set of charge states. […]
Process tables for a set of charge states. Only one table is used for that process, defined by process(:)/table_dimension. If the data in the table_Nd array are used as parameters for a function, then no coordinates are needed, and coordinate_index should be set to -1, and result_transformation should contain the integer identifier to the internally provided functions. If the results will come from an interpolation in the table_Nd data, then coordinates must be provided in coordinate_system(process(i1)/coordinate_index), and the shape of the table should match the cartesian product of the coordinates
Maximum occurrences (MDS+ backend only): 75
1 |
|
process(i1)/charge_state(i2)/nameSTR_0D¶String identifying charge state (e.g. […]
String identifying charge state (e.g. C+, C+2 , C+3, C+4, C+5, C+6, …)
Changed in version 3.42.0: Renamed from label
process(i1)/charge_state(i2)/z_min ⇹eFLT_0D¶Minimum Z of the charge state bundle
Minimum Z of the charge state bundle
process(i1)/charge_state(i2)/z_max ⇹eFLT_0D¶Maximum Z of the charge state bundle (equal to z_min if no bundle)
Maximum Z of the charge state bundle (equal to z_min if no bundle)
process(i1)/charge_state(i2)/table_0d ⇹units given by process(:)/results_unitsFLT_0D¶0D table describing the process data
0D table describing the process data
process(i1)/charge_state(i2)/table_1d(:) ⇹units given by process(i1)/results_unitsFLT_1D¶1D table describing the process data
1D table describing the process data
1 |
|
process(i1)/charge_state(i2)/table_2d(:,:) ⇹units given by process(i1)/results_unitsFLT_2D¶2D table describing the process data
2D table describing the process data
1 |
|
2 |
|
process(i1)/charge_state(i2)/table_3d(:,:,:) ⇹units given by process(:)/results_unitsFLT_3D¶3D table describing the process data
3D table describing the process data
1 |
|
2 |
|
3 |
|
process(i1)/charge_state(i2)/table_4d(:,:,:,:) ⇹units given by process(i1)/results_unitsFLT_4D¶4D table describing the process data
4D table describing the process data
1 |
|
2 |
|
3 |
|
4 |
|
process(i1)/charge_state(i2)/table_5d(:,:,:,:,:) ⇹units given by process(i1)/results_unitsFLT_5D¶5D table describing the process data
5D table describing the process data
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
coordinate_system(i1)AoS¶Array of possible coordinate systems for process tables
Array of possible coordinate systems for process tables
Maximum occurrences (MDS+ backend only): 20
1 |
|
coordinate_system(i1)/coordinate(i2)AoS¶Set of coordinates for that coordinate system. […]
Set of coordinates for that coordinate system. A coordinate an be either a range of real values or a set of discrete values (if interpolation_type=0)
Maximum occurrences (MDS+ backend only): 6
1 |
|
coordinate_system(i1)/coordinate(i2)/nameSTR_0D¶Name of coordinate (e.g. […]
Name of coordinate (e.g. “Electron temperature”)
Changed in version 3.42.0: Renamed from label
coordinate_system(i1)/coordinate(i2)/values(:) ⇹units given by coordinate_system(:)/coordinate(:)/unitsFLT_1D¶Coordinate values
Coordinate values
1 |
|
coordinate_system(i1)/coordinate(i2)/interpolation_typeINT_0D¶Interpolation strategy in this coordinate direction. […]
Interpolation strategy in this coordinate direction. Integer flag: 0=discrete (no interpolation); 1=linear; …
coordinate_system(i1)/coordinate(i2)/extrapolation_type(:)INT_1D¶Extrapolation strategy when leaving the domain. […]
Extrapolation strategy when leaving the domain. The first value of the vector describes the behaviour at lower bound, the second describes the at upper bound. Possible values: 0=none, report error; 1=boundary value; 2=linear extrapolation
1 |
|
coordinate_system(i1)/coordinate(i2)/value_labels(:)STR_1D¶String description of discrete coordinate values (if interpolation_type=0). […]
String description of discrete coordinate values (if interpolation_type=0). E.g., for spectroscopic lines, the spectroscopic description of the transition.
1 |
coordinate_system(i1)/coordinate(i2)/unitsSTR_0D¶Units of coordinate (e.g. […]
Units of coordinate (e.g. eV)
release(i1)AoS¶List of available releases of the AMNS data; each element contains […]
List of available releases of the AMNS data; each element contains information about the AMNS data that is included in the release. This part of the IDS is filled and stored only into shot/run=0/1, playing the role of a catalogue.
Maximum occurrences (MDS+ backend only): 100
1 |
|
release(i1)/data_entry(i2)AoS¶For this release, list of each data item (i.e. […]
For this release, list of each data item (i.e. shot/run pair containing the actual data) included in this release
Maximum occurrences (MDS+ backend only): 30
1 |
|
release(i1)/data_entry(i2)/descriptionSTR_0D¶Description of this data entry
Description of this data entry
codestructure¶Generic decription of the code-specific parameters for the code […]
Generic decription of the code-specific parameters for the code that has produced this IDS
code/descriptionSTR_0D¶Short description of the software (type, purpose)
Short description of the software (type, purpose)
New in version >3.38.1.
code/parametersSTR_0D¶List of the code specific parameters in XML format
List of the code specific parameters in XML format
code/library(i1)AoS¶List of external libraries used by the code that has produced […]
List of external libraries used by the code that has produced this IDS
Maximum occurrences (MDS+ backend only): 10
1 |
|
code/library(i1)/descriptionSTR_0D¶Short description of the software (type, purpose)
Short description of the software (type, purpose)
New in version >3.38.1.