Can we load ICON dust AOD with ESMValTool?

[nchawang]

Hi ESMValTool community!

I had a question regarding loading of ICON-ART dust AOD to carry out some predecessors and diagnostics to it,

Going through here and going through the config-developer.yml file, i saw that ICON takes in CMIP 6 Tables I think from here?

Can we load the ICON variables using the varaible names mentioned in the table (for example, load dust AOD into od550dust mentioned in CMIP6_AERmon?) (I dont see aerosol variables in ICON_mappings.yml file)

Also, for example, od550dust variable is not mentioned in CMIP6_AERday, can I edit the file to include od550dust and it'll work for daily output files?

Any help in this regard is highly appreciated!

[schlunma]

Hi @nchawang, the entry "CMIP6" for ICON in the config-developer file just means that its output is supposed to be checked against the CMIP6 tables. The only variables "fully" supported for ICON data (i.e., tested by us) are the ones listed in the mapping file.

Other variables might be supported if you specify the correct var_type in your recipe (e.g., at the place where you define things like mip: AERmon. To fully support them, we would need to add them to our mapping table (see example pull request ESMValGroup/ESMValCore#2700). Alternatively, you can also use a custom mapping by using the configuration option extra_facets_dir, see here for details.

If a variable is in another table but with a wrong table, you can simply do ..., mip: AERmon, frequency: day, ... in the recipe.

[nchawang]

Ah, okay! thanks a lot @schlunma I shall try this!

[nchawang]

Hi @schlunma, I just wanted to follow up with another query, setting the mip:AERmon for ICON-ART variables work!

I was wondering if there were variables (or var_types) that aren't mentioned in the MIP tables for AER but would like to load it with the ESMValCore and carry out some preprocessor and diagnostics on it, how should I go about it? (for example if i would like to load the accumulated emission of dust "acc_emiss_dusta")

[schlunma]

Yes! You need to define a custom table for each variable that you want to read. In this case, the mip entry in the recipe can be anything, but cannot be omitted. For example, if your variable is a monthly atmospheric variable, I recommend setting it to Amon.

[nchawang]

Ah okay, wonderful! I shall explore this more, thanks @schlunma