atmospheric_fieldAppendBaseData
- Workspace.atmospheric_fieldAppendBaseData(self, atmospheric_field: pyarts3.arts.AtmField | None = None, basename: pyarts3.arts.String | None = None, extrapolation: pyarts3.arts.String | None = None, deal_with_field_component: pyarts3.arts.String | None = None, replace_existing: pyarts3.arts.Index | None = None, allow_missing_pressure: pyarts3.arts.Index | None = None, allow_missing_temperature: pyarts3.arts.Index | None = None) None
Append base data to the atmospheric field
This will look at the valid
basename
for files matching base data. The base data file names are of the form“<…>t.xml”
“<…>p.xml”
“<…>wind_u.xml”
“<…>wind_v.xml”
“<…>wind_w.xml”
“<…>mag_u.xml”
“<…>mag_v.xml”
“<…>mag_w.xml”
If any of these files are found, they are appended to the atmospheric field.
See
InterpolationExtrapolation
for validextrapolation
.See
MissingFieldComponentError
for validdeal_with_field_component
.The
replace_existing
is used to determine if the data should be replaced if it already exists in the atmospheric field.The
allow_missing_pressure
andallow_missing_temperature
are used to determine if the method should throw if the pressure or temperature is missing.Author: Richard Larsson
Used by wrapper method
- Parameters:
atmospheric_field (AtmField, optional) – An atmospheric field in ARTS. See
atmospheric_field
, defaults toself.atmospheric_field
[INOUT]basename (String) – The base name of the files. [IN]
extrapolation (String, optional) – The extrapolation to use. Defaults to
"Linear"
[IN]deal_with_field_component (String, optional) – How to deal with the field component. Defaults to
"Throw"
[IN]replace_existing (Index, optional) – Whether or not to replace existing data. Defaults to
1
[IN]allow_missing_pressure (Index, optional) – Whether or not to allow missing pressure data. Defaults to
0
[IN]allow_missing_temperature (Index, optional) – Whether or not to allow missing temperature data. Defaults to
0
[IN]