Combining various ready-made inputs for CHIMERE¶
Here we combine various inputs of emissions and boundary conditions from various ready-made files for CHIMERE.
The instructions provided here assume that you already have a yaml for a first simulation with ready-made files and deal with the components of datavect which provide CHIMERE with its usual 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 system).
Check the generated inputs, as explained in Checking the input files:.
Combining ready-made files for emissions¶
It is possible to specify different input sources for the various emitted species which do not require a sub-hourly interpolation.
These species must be listed as parameters of flux
and their names must match the names in ANTHROPIC.
For each parameter, the specifications of the component plugin are inherited by default
but it is possible to individualize everything, including the plugin to use, as shown in the following examples.
Combining a general file with particular files for a few species¶
Very often, a general set of files is used for all species required by the chemical scheme but a few, for which another set is indicated: in the following example, all species are taken from the AEMISSIONS files available in directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files, only S1 is taken from the AEMISSIONS files in 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: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S1 XXX CHECK IF name/version/type must be repeated here XXX
Specifying a file for each species¶
For chemical species with one or only a few species, all species can be detailed, with no use of a general set of files; if one species of the ANTHROPIC list is forgotten among the parameters, an error will be raised (the CIF will stop on an error trying to make a link to a non-existing inventory file for it).
##################################################################### ##################################################################### 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 S2: dir: directory_containing_AEMISSIONS.YYYYMMDDHH.*.nc_files_for_S2 file: AEMISSIONS.%Y%m%d%H.Y.nc file_freq: YH XXX CHECK THAT IT WORKS WITH X different from Y, if yes direct to explanations about time interpolation XXXX plugin: name: CHIMERE version: AEMISSIONS type: flux
XXXXXX ajouter exemple avec AEMISSIONS d’un autre domaine a interpoler XXXX
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 characterized by their comp_type; otherwise, their specifications follow the same principles as flux.
To use various pre-computed files, according to the species, parameters with names matching the names in ACTIVE_SPECIES have to be specified.
The example shows a case of general files used for initial conditions and lateral conditions but for one species in each case, and a general file 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 is_lbc: true XXX CHECK WHY THIS: for the plugin or the compenent?? + for the others? XXXXX 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 XX OK X different de Y??XXX 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
