################################################################## Combining various ready-made inputs for CHIMERE ################################################################## .. role:: bash(code) :language: bash Here we combine various inputs of emissions and boundary conditions from various ready-made files for :doc:`CHIMERE`. The instructions provided here assume that you already have a yaml for a :doc:`first simulation with ready-made files` and deal with the components of :bash:`datavect` which provide CHIMERE with its usual inputs. How to test the choices made ============================= 1. Have a yaml for a first forward simulation. 2. Modify the yaml for the targeted inputs, as shown below. 3. Run the system with the modified yaml (see :ref:`chimere_run_readymade`). 4. Check the generated inputs, as explained in :ref:`chimere_check_inputs_readymade`. 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 :bash:`parameters` of :bash:`flux` and their names must match the names in :doc:`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: .. code-block:: yaml 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 ----------------------------------- 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 :doc:`ANTHROPIC` list is forgotten among the :bash:`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). .. code-block:: yaml 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 given domain, it is easy to indicate to the CIF how interpolate them onto the (different) current domain: the characteristics of the original domain simply have to be specified in the relevant parameter(s). (To avoid any mistakes, the CIF does not recover this information automatically.) .. code-block:: yaml 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 The horizontal grid as well as the vertical one can be different. If the original domain covers a smaller area than the targetted one, the emissions outside the original domain are set to zero. BEMISSIONS ---------- The :bash:`bioflux` specifications follow the same principles as :bash:`flux`. All the examples provided for AEMISSIONS apply to BEMISSIONS, with the addition of :bash:`emis_type`. Combining ready-made files for boundary conditions =================================================== The :bash:`inicond`, :bash:`latcond` and :bash:`topcond` components are characterized by their :bash:`comp_type`; otherwise, their specifications follow the same principles as :bash:`flux`. To use various pre-computed files, according to the species, parameters with names matching the names in :doc:`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. .. code-block:: yaml 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