Combining various ready-made inputs for CHIMERE#
Here we combine emissions and boundary conditions from multiple ready-made files for CHIMERE.
These instructions assume that you already have a YAML for a first simulation with ready-made files, and focus on the datavect components that provide CHIMERE with its standard inputs.
How to test the choices made#
Have a YAML for a first forward simulation.
Modify the YAML for the targeted inputs, as shown below.
Run the system with the modified YAML (see Run the simulation).
Check the generated inputs, as explained in Checking the input files:.
Combining ready-made files for emissions#
Different input sources can be specified for the various emitted species that do not require sub-hourly interpolation.
These species must be listed as parameters of flux,
with names matching those in ANTHROPIC.
Each parameter inherits the component plugin settings by default,
but all settings, including the plugin itself, can be overridden individually, as shown in the examples below.
Combining a general file with particular files for a few species#
A common pattern is to use a general set of files for all species in the chemical scheme, except for a few that use a different source. In the following example, all species come from the AEMISSIONS files in directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files, except S1 which comes from directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S1:
datavect: plugin: name: standard version: std components: meteo: dir: directory_containing_METEO.YYYYMMDDHH.*.nc_files file: METEO.%Y%m%d%H.X.nc plugin: name: CHIMERE version: std type: meteo file_freq: XH flux: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files file: AEMISSIONS.%Y%m%d%H.X.nc plugin: name: CHIMERE version: AEMISSIONS type: flux file_freq: XH parameters: S1: plugin: name: CHIMERE version: AEMISSIONS type: flux dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S1
Specifying a file for each species#
When there are only a few emitted species, each one can be specified individually with no general fallback file. If any species from the ANTHROPIC list is missing from parameters, the CIF will raise an error when attempting to create a symlink to a non-existent inventory file.
datavect: plugin: name: standard version: std components: meteo: dir: directory_containing_METEO.YYYYMMDDHH.*.nc_files file: METEO.%Y%m%d%H.X.nc plugin: name: CHIMERE version: std type: meteo file_freq: XH flux: parameters: S1: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S1 file: AEMISSIONS.%Y%m%d%H.X.nc file_freq: XH plugin: name: CHIMERE version: AEMISSIONS type: flux S2: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S2 file: AEMISSIONS.%Y%m%d%H.Y.nc file_freq: YH plugin: name: CHIMERE version: AEMISSIONS type: flux
Interpolate one AEMISSIONS from another domain into the chosen one#
When AEMISSIONS files are available for a different domain, you can instruct the CIF to interpolate them onto the current domain by specifying the original domain’s characteristics in the relevant parameter(s). The CIF does not infer this information automatically.
domain: plugin: name: CHIMERE version: std type: domain domid: THISSTUDY emissublayer: 0 nlev: NL p1: P1 pmax: PMAX repgrid: directory_containing_domains_definitions/domains datavect: plugin: name: standard version: std components: meteo: dir: directory_containing_METEO.YYYYMMDDHH.*.nc_files file: METEO.%Y%m%d%H.X.nc plugin: name: CHIMERE version: std type: meteo file_freq: XH flux: parameters: S1: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S1 file: AEMISSIONS.%Y%m%d%H.X.nc file_freq: XH plugin: name: CHIMERE version: AEMISSIONS type: flux S2: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S2_on_domain_ORIGIN domain: domid: ORIGIN emissublayer: 0 nlev: NLORIG p1: P1ORIG pmax: PMAXORIG file: AEMISSIONS.%Y%m%d%H.Y.nc file_freq: YH plugin: name: CHIMERE version: AEMISSIONS type: flux
Both the horizontal and vertical grids can differ. If the original domain covers a smaller area than the target domain, emissions outside the original domain are set to zero.
BEMISSIONS#
The bioflux specifications follow the same principles as flux.
All the examples provided for AEMISSIONS apply to BEMISSIONS, with the addition of emis_type.
Combining ready-made files for boundary conditions#
The inicond, latcond, and topcond components are distinguished by their comp_type;
otherwise their specifications follow the same principles as flux.
To use different pre-computed files for different species, specify parameters whose names match those in ACTIVE_SPECIES.
The example below shows a case where a general file is used for initial and lateral conditions except for one species in each case, and a general file is used for all top conditions.
datavect: plugin: name: standard version: std components: meteo: dir: directory_containing_METEO.YYYYMMDDHH.*.nc_files file: METEO.%Y%m%d%H.X.nc plugin: name: CHIMERE version: std type: meteo file_freq: XH flux: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files file: AEMISSIONS.%Y%m%d%H.X.nc plugin: name: CHIMERE version: AEMISSIONS type: flux file_freq: XH inicond: dir: directory_containing_IC.YYYYMMDDHH.*.nc_files file: INI_CONCS.0.nc plugin: name: CHIMERE version: icbc type: field comp_type: inicond parameters: S1: dir: directory_containing_IC.YYYYMMDDHH.*.nc_files_forS1 file: INI_CONCS.0.nc plugin: name: CHIMERE version: icbc type: field latcond: dir: directory_containing_BC.YYYYMMDDHH.*.nc_files file: BOUN_CONCS.%Y%m%d%H.X.nc plugin: name: CHIMERE version: icbc type: field comp_type: latcond file_freq: XH parameters: S3: dir: directory_containing_BC.YYYYMMDDHH.*.nc_files_forS3 file: BOUN_CONCS.%Y%m%d%H.Y.nc file_freq: YH plugin: name: CHIMERE version: icbc type: field topcond: dir: directory_containing_BC.YYYYMMDDHH.*.nc_files file: BOUN_CONCS.%Y%m%d%H.X.nc plugin: name: CHIMERE version: icbc type: field comp_type: topcond file_freq: XH