LMDZ mass fluxes LMDZ/mass-fluxes

LMDZ mass fluxes LMDZ/mass-fluxes#

Description#

Meteorology plugin for LMDZ’s monthly mass-flux NetCDF files (fluxstoke, phystoke/phystoke_csr, and, for the regular grid, fluxstokev), used with the LMDZ reg-ico regridded/icosahedral model.

This plugin only fetches/links the source files needed by the model at the dates listed in tracer.model.meteo_input_dates; it does not read their content itself (there is no read.py). The file input argument is not supported (this plugin decides file names on its own) and file_freq is forced to monthly ("1MS").

YAML arguments#

The following arguments are used to configure the plugin. pyCIF will return an exception at the initialization if mandatory arguments are not specified, or if any argument does not fit accepted values or type:

Optional arguments#

dir : str, optional, default “”

Path to the corresponding component. This value is used if not provided in parameters

file : str, optional, default “”

File format in the given directory. This value is used if not provided in parameters

varname : str, optional, default “”

Variable name to use to read data filesinstead of the parameter name if different to the parameter name

file_freq : str, optional, default “”

Temporal frequency to fetch files

split_freq : str, optional

Re-bucket this tracer’s fetched dates/files onto a fixed pandas-frequency grid (e.g. '1D', '1MS', '1YS'), independently of the native frequency the files were found at (file_freq). This fixes the sub-simulation boundaries that fromcontrol inherits for this tracer. For minimal memory usage, match it to the consuming model’s own periodicity: a finer value costs an extra time_interpolation bridge for no memory benefit, while a coarser value keeps the tracer’s data resident in memory across every one of the model’s sub-simulations it spans. See the ‘Splitting the temporal grid’ section on the observation operator page for the full mechanism and worked examples.

Requirements#

The current plugin requires the present plugins to run properly:

Requirement name

Requirement type

Explicit definition

Any valid

Default name

Default version

model

Model

False

False

LMDZ

reg-ico

YAML template#

Please find below a template for a YAML configuration:

 1meteo:
 2  plugin:
 3    name: LMDZ
 4    version: mass-fluxes
 5    type: meteo
 6
 7  # Optional arguments
 8  dir: XXXXX  # str
 9  file: XXXXX  # str
10  varname: XXXXX  # str
11  file_freq: XXXXX  # str
12  split_freq: XXXXX  # str

See also

API reference (functions & code)