Getting started

As emiprep is still in development, this document tries to give an introduction to using emiprep.

emiprep configuration

emiprep reads all runtime parameters from a configuration file in YAML format. An example file is available in the code tree at emiprep/config/tno_crimech.yaml.

emiprep input files

emiprep needs a lot of input data in order to run:

  1. The emission inventories to be used themselves
  2. Data about temporal (i.e., diurnal, weekly, seasonal) cycles. Currently, using data from EMEP is the only option (see Sect. 6.1.2 in [SBB+12]).
  3. Data about the vertical distribution of emissions. Currently, using data from EMEP is the only option (see Sect. 6.1.1 and Tab. S3 in [SBB+12]).
  4. Information about how to split emission species into model species
  5. Information about the model domain. This is currently read from wrfinput and met_em files.

Running emiprep

After activating the conda environment (see Development of emiprep for details), emiprep can be executed (from the repository’s root directory) with the command

$ python -m emiprep.run.runner -c emiprep/config/tno_crimech.yaml

More information

More information can currently be found in some Jupyter Notebooks in the Background section.

References

[SBB+12](1, 2) D. Simpson, A. Benedictow, H. Berge, R. Bergström, L. D. Emberson, H. Fagerli, C. R. Flechard, G. D. Hayman, M. Gauss, J. E. Jonson, M. E. Jenkin, A. Ny’ıri, C. Richter, V. S. Semeena, S. Tsyro, J.-P. Tuovinen, Á. Valdebenito, and P. Wind. The EMEP MSC-W chemical transport model — technical description. Atmospheric Chemistry and Physics, 12(16):7825–7865, 2012. URL: https://www.atmos-chem-phys.net/12/7825/2012/, doi:10.5194/acp-12-7825-2012.