...
- variable_id: variable is a short variable name, e.g. “tas” for “temperature at the surface”.
- table_id: this refers to the MIP table being used. The MIP tables are used to organise the variables. For example, Amon refers to monthly atmospheric variables and Oday contains daily ocean data.
- source_id: this refers to the model used that produced the data.
- experiment_id: refers to the set of experiments being run for CMIP6. For example, PiControl, historical and 1pctCO2 (1 percent per year increase in CO2).
- variant_label: is a label constructed from 5 indices (ensemble identifiers) s<yyyy>-r<W>i<X>p<Y>f<Z>, where yyyy is the start year and W, K, Y and Z are positive integers.
- grid_label: this describes the model grid used. For example, global mean data (gm), data reported on a model's native grid (gn) or regridded data reported on a grid other than the native grid and other than the preferred target grid (gr1).
- time_range: the temporal range is in the form YYYYMM[DDHH]-YYYY[MMDDHH], where Y is year, M is the month, D is day and H is hour. Note that day and hour are optional (indicated by the square brackets) and are only used if needed by the frequency of the data. For example, daily data from the 1st of January 1980 to the 31st of December 2010 would be written 19800101-20101231.
Quality control of the CDS-CMIP6-DCPP subset
The CDS subset of the DCPP data have been through a set of quality control checks before being made available through the CDS. The objective of the quality control process is to ensure that all files in the CDS meet a minimum standard. Data files were required to pass all stages of the quality control process before being made available through the CDS. Data files that fail the quality control process are excluded from the CDS-CMIP6 subset, data providers are contacted and if they are able to release a new version of the data with the error corrected then providing this data passes all remaining QC steps may be available for inclusion in the next CMIP6 data release.
...