CMOR MIP tables for use with CMOR v3.13 in preparation for CMIP7.

Note that versions of CMOR after v3.10 will be able to use these MIP tables, but version 3.13 is required to correctly output the realization, initialization, physics and forcing indices.

With the introduction of branded variable names (work in progress) and an updated set of global attributes the tables here look a little different to those for CMIP6.

• Variables are arranged in MIP tables by realm and indexed by branded variable name.
• Frequency is no longer defined for a specific variable and any valid frequency can be set via the input JSON file.

Notable changes to the input JSON file used by CMOR

• drs_specs should be set to "MIP-DRS7"
• region is required (usually "GLB" for global variables)
• archive_id is "WCRP"
• frequency must be specified
• *_index fields are now strings and must have the appropriate prefix, e.g. realization_index should be "r1" rather than 1
• tracking_prefix has been updated with the value required for CMIP7

The CV json files in this repository are for TESTING only. In the near future we are planning for the CMIP7_CV.json file to be constructed and supplied via the CMIP7-CVs repository. Updates will be posted here when progress has been made

The tables and examples presented here are derived directly from Data Request version v1.2.2.2 with the following changes;

• long_name and modeling_realm fields have been "homogenised"; there are a number Data Request variables with the same branded variable name, e.g. tas_tavg-h2m-hxy-u, at different frequencies , but with different long name or modeling realm. This will be corrected in the Data Request in version v1.2.2.3.
• comment fields have been left blank as we have not yet "homogenised" this data.
• cell_measures are currently blank, with a separate JSON file containing them indexed by the CMIP7 Compound name from the Data Request -- the examples show how to re-introduce this metadata, and updated guidance will be added here.

• There are some branded variable names that appear in both atmos and landIce MIP tables. We are expecting to change this in the next version of the Data Request to avoid duplication.

Each of these use the tables and the testing CVs JSON file

• Simple CMOR demo notebook (python script equivalent)
• Example of "re-cmorising" CMIP6 data

Note in particular the lines used to add cell_measures metadata to variables.

Testing of these tables has been limited, so please report problems / suggestions via the issues.

The construction script uses the Data Request API and a set of reference files (adapted from CMIP6Plus) to construct the MIP tables and associated files.