ARTS built-in documentation server

Workspace Method AtmWithNLTERawRead


Reads atmospheric data from a scenario.

An atmospheric scenario includes the following data for each
position (pressure, latitude, longitude) in the atmosphere:
   1. temperature field
   2. the corresponding altitude field
   3. vmr fields for the gaseous species
   4. Non-LTE temperature fields and matching identifiers
The data is stored in different files. This method reads all
files and creates the variables t_field_raw, z_field_raw,
vmr_field_raw, nlte_field_raw, and nlte_level_identifiers.

Files in a scenarios should be named matching the pattern of:

The files can be anywhere, but they must be all in the same
directory, selected by 'basename'. The files are chosen by the
species name. If you have more than one tag group for the same
species, the same profile will be used.

Authors: Claudia Emde, Richard Larsson


AtmWithNLTERawRead( t_field_raw, z_field_raw, vmr_field_raw, nlte_field_raw, nlte_level_identifiers, nlte_vibrational_energies, abs_species, basename, expect_vibrational_energies )


OUTt_field_raw(GriddedField3)Raw data for atmospheric temperatures.
OUTz_field_raw(GriddedField3)Raw data for geometrical altitudes.
OUTvmr_field_raw(ArrayOfGriddedField3)VMR data for the chosen gaseous species.
OUTnlte_field_raw(ArrayOfGriddedField3)Raw data for NLTE temperatures and/or ratios.
OUTnlte_level_identifiers(ArrayOfQuantumIdentifier)An array of non-lte quantum identifiers for levels matching nlte_field_raw and on request nlte_vibrational_energies.
OUTnlte_vibrational_energies(Vector)An list of vibrational energies matching nlte_level_identifiers and nlte_field_raw or being 0.
INabs_species(ArrayOfArrayOfSpeciesTag)Tag groups for gas absorption.
GINbasename(String)Name of scenario, probably including the full path. For example: "/smiles_local/arts-data/atmosphere/fascod/tropical"
GINexpect_vibrational_energies(Index, Default: 0)Should ev.xml be read?