CMIP5 Coupled Model Intercomparison Project
WCRP    World Climate Research Programme

CMIP5 - Data Description



The List of Requested Model Output document describes the variables that are being requested to be saved and submitted to the CMIP5 archives. The data output is required to adhere to the common standard output that is specified in the document. The viariables names, their description, their dimensions and dimension's names, as well as standard name, long name, units and other requirements are defined in the List of Requested Model Output that each model output needs to follow.



The List of Requested Model Output

See the standard output document: standard_output.pdf . It contains the List of Requested Variables, also available as standard_output.xls .

 

Go to Output Requirements page to see the previous versions and changes.



CMIP5 Data Characteristics:


  Each file contains a single output variable (along with coordinate/grid variables, attributes and other metadata) from a single model and a single simulation (i.e., from a single ensemble member of a single climate experiment). This method of structuring model output best serves the needs of most researchers who are typically interested in only a few of the many variables in the Model Intercomparison Project (MIP) databases. Data requests can be satisfied by simply sending the appropriate file(s) without first extracting the individual field(s) of interest.


There is flexibility in specifying how many time slices (samples) are stored in a single file. A single file can contain all the time-samples for a given variable and climate experiment, or the samples can be distributed in a sequence of files.


Much of the metadata written to the output files is defined in MIP-specific tables of information, which in this document are referred to simply as "MIP tables" in ASCII files.


The metadata is constrained by the CF convention (NetCDF Climate and Forecast (CF) Metadata Convention) and as specified in the CMIP5 tables.


The output files are written through the NetCDF API following the NETCDF_CLASSIC model and without compression of any kind.

Note: It is recommended that the CMOR software be used to write the model output, which will ensure compliance with the CMIP5 specifications. See the Output Requirements page for further information and see CMIP5 Model Output Format and Metadata Requirements for full specifications for writing CMIP5 output.