cordex-cmip6-cmor-tables

JSON Tables for CMOR3 to create CORDEX-CMIP6 datasets.

Table update

These tables are created from the CORDEX-CMIP6 data request table using:

pip install git+https://github.com/WCRP-CORDEX/data-request-tools.git

and

python scripts/create-tables.py https://raw.githubusercontent.com/WCRP-CORDEX/data-request-table/main/CORDEX-CMIP6/data-request.csv

Current Issues

Note that there might be some issues if your are using the cmor library with these tables, for example:

• In your input dataset json file, make sure the _cmip6_option is removed so that more flexible CV's are possible. See also this discussion. You can also check the example input file.
• Make sure to use cmor>=3.8.0 since CORDEX-CMIP6 does not require the further_info_url, see also PCMDI/cmor#727. Otherwise, a default further_info_url will be added by cmor that is created from related attributes but will probably point to an invalid URL.
• With the current cmor release (3.8.0), a default realm attribute is written, although not required by the CV. This is fixed in an upcoming cmor release.
• Finally, if you use these tables together with the cmor library and successfully create cmorized files, it is still not guaranteed that you used the CV correctly. This is unfortunately but reasonably due to the close relation between cmor and the original CMIP6 requirements for AR6. This means, e.g., that CV entries other than the basic insitution_id or source_id are not as rigorously checked but mainly only for their presence if they are part of the required global attributes. For example, only attributes in the CV that are defined as lists are checked for consistency but not if they are defined as subsections. For some more details on this issue, please follow PCMDI/cmor#679 (comment).

Feedback

If you have any issues regarding the cmor tables, please open an issue. If you have an issue regarding the data request, e.g., variable metadata, please check here. For issues regarding the controlled vocabulary, please check here.