CAMS_TNO_REG emissions in EMEP

[AlexanderdeMeij]

Dear EMEP model community, @gitpeterwind @avaldebe I am writing to you regarding a question on the implementation of the new CAMS-REG emissions in the EMEP model (CAMS-REG-AP_TNO_0.05x0.1_anthro_allspecies_v2.2.zip, which can be downloaded from https://eccad.aeris-data.fr/2019/06/05/cams-inventories).

Currently I am running the EMEP model (rv4.15.OpenSource) with the 0.1x0.1 EMEP emissions over Europe for 2015. I would like to use the newly released CAMS emissions (at 0.1 x 0.05: CAMS_REG -AP_TNO_0.05x0.1.nc datasets). I've downloaded the CAMS_REG-AP_TNO files, concatenated the variables into one single NetCDF file, redistributed the file on 0.1x01 degrees and transformed to tonnes/year, renamed the variables, attributes and the changed the dimensions, but the EMEP model doesn't seem to like the new emissions.

I know that EMEP is part of CAMS, so perhaps you run in-house EMEP with the CAMS_REG-AP_TNO files? Do you have a methodology on how to process the CAMS_REG-AP_TNO_0.05x0.1.nc emissions for the EMEP model or is the modified CAMS emission inventory for the model available?

Best regards, Alexander

[avaldebe]

I know that EMEP is part of CAMS, so perhaps you run in-house EMEP with the CAMS_REG-AP_TNO files? Do you have a methodology on how to process the CAMS_REG-AP_TNO_0.05x0.1.nc emissions for the EMEP model or is the modified CAMS emission inventory for the model available?

On our daily CAMS50 forecasts and analysis we use the CAMS_REG_v2.2.1 emission dataset. From your description seems it is the same dataset you downloaded, but I'm not sure we can redistribute the processed file as part of our open source release.

There are different ways to describe emission files, specially on our latest model version (rv4.32 from April 2019). BTW, we are about to release a model update (rv4.33), which changes the configuration namelists. I hope to release the source code later today, and the input and benchmark output next week.

In any case, in order to use our processed emission file you would need rv4.32 or the soon to be released rv4.33.

I do not know what would take to use the our processed emission file on rv4.15. I do have a patch for rv4.17, but if you can update your model version I would strongly recommend to update the the latest version.

@michaelgau Do you know if we can redistribute the processed CAMS_REG_v2.2.1 emission file?

@agnesny and @gitpeterwind Is it possible to use the raw emission files using the new emission description?

[gitpeterwind]

Hi Alexander, I haven't checked in details, but with the new format scheme from the latest version, it should be possible to read the raw emission file with only minor changes. Best wishes, Peter

[agnesny]

Hi Alexander, I am not familiar with the file format which is available from the ECCAD website, so I can not answer whether the emission files can be used in the EMEP model as they are, and if so, how to do it. I know that in previous versions the country codes were not included, therefore we preferred to obtain the data directly from TNO instead of using the ECCAD website. It might be different now, but we have not downloaded our latest CAMS emissions from there, so I do not know. We downloaded the CAMS_REG_v2.2.1 dataset through TNO's ftp in a different format (as csv files) and converted them ourselves into EMEP model friendly netCDF files. I am not sure whether we can redistribute the processed CAMS_REG_v2.2.1 emission files though. If @michaelgau confirms, we could make those available for you. Best wishes, Agnes

[michaelgau]

Hi All, we cannot redistribute the CAMS-REG-AP_v2.2.1 emissions as part of our Open Source release, neither as raw data nor processed. But in this case, since Alexander downloaded the raw files from ECCAD and has agreed to acknowledge the providers of the emission data, there is no problem. We can share our processed CAMS-REG-AP_v2.2.1 emission files with him (I also confirmed this with Hilde). Of course he should not distribute the emission data further to third parties. Best wishes, Michael

[AlexanderdeMeij]

Dear Michael, Agnes, Peter and Álvaro, @michaelgau @agnesny @gitpeterwind @avaldebe

Thank you for your prompt replies and that you will share your processed CAMS emission inventory. Many thanks for that! As agreed, I will not share/redistribute the emissions.

Do you have an ftp from which I can transfer the inventory? In case you want to send me the credentials, you can use my email address EDIT: EMAIL ADDRESS REMOVED

Best regards, Alexander

[avaldebe]

@AlexanderdeMeij

Please email me so we can arrange the transference of the file. Note that you need to update the version of the model to use this file.

[avaldebe]

@AlexanderdeMeij

Please close this issue when you get the file, and open a new issue if you need help with the new model version.