atmospheric_fieldAppendBaseData

Workspace.atmospheric_fieldAppendBaseData(self, atmospheric_field: pyarts.arts.AtmField | None = None, basename: pyarts.arts.String | None = None, extrapolation: pyarts.arts.String | None = None, deal_with_field_component: pyarts.arts.String | None = None, replace_existing: pyarts.arts.Index | None = None, allow_missing_pressure: pyarts.arts.Index | None = None, allow_missing_temperature: pyarts.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 valid extrapolation.

See MissingFieldComponentError for valid deal_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 and allow_missing_temperature are used to determine if the method should throw if the pressure or temperature is missing.

Author(s): Richard Larsson

Parameters:

  • atmospheric_field (AtmField, optional) – An atmospheric field in ARTS. See atmospheric_field, defaults to self.atmospheric_field [INOUT]

  • basename (String) – The base name of the files. [IN]

  • extrapolation (String, optional) – , optionalThe extrapolation to use. [IN]

  • deal_with_field_component (String, optional) – , optionalHow to deal with the field component. [IN]

  • replace_existing (Index, optional) – , optionalWhether or not to replace existing data. [IN]

  • allow_missing_pressure (Index, optional) – , optionalWhether or not to allow missing pressure data. [IN]

  • allow_missing_temperature (Index, optional) – , optionalWhether or not to allow missing temperature data. [IN]