CMIP data located at the National Computational Infrastructure (NCI) covers a broad range of datasets, including CMIP5 and CMIP6 era replicated and published data as well as key observational and reanalysis datasets. For further information on the different climate datasets and available variables see the Datasets and Available Variables page. On this page we describe the methods in which the CMIP data hosted at NCI may be accessed. Sections in this page are broken into the following topics:
Column | ||||
---|---|---|---|---|
| ||||
|
Column | ||
---|---|---|
| ||
Image Source: https://www.earthsystemcog.org/projects/cmip/ |
Section | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Access to the CMIP and related data available is available via three key methods:
Primary access to the CMIP data, from both raijin and the VDI, is achieved via requesting to join the relevant project space (see below) and accessing the data from /g/data/<project code> (see table below).
Request to Access a Data CollectionYou may request to join a data collection through my.nci.org.au/mancini. Your request will be sent to the data collection manager for approval and you must agree to the same Terms and Conditions that govern CMIP access data access as stipulated by the Earth Systems Grid Federation: CleFThe volume and complexity of CMIP makes manual searching for data on the filesystem a time consuming process. To efficiently find the CMIP data that you wish to access we recommend using the Climate Finder tool CleF developed by ARCCSS and CLEX. CleF is a python module designed for ease of searching and accessing data at NCI through a command line interface. Documentation on using CleF is available here and membership of any of the NCI CMIP projects oi10, al33, rr3 or ua6 is required for use (if you are a new member it may take up to 1 day for access to the NCI database used by CleF to be granted). |
Section | |||||||||
---|---|---|---|---|---|---|---|---|---|
To permit ease of use and interdisciplinary research, CMIP uses a standard naming convention for files, directories, metadata and URLs. These conventions are described in detail in the CMIP6 Controlled Vocabularies and CMIP5 Controlled Vocabulary CMIP6 Published and Official Replica DataUnder the CMIP6 DRS, data may be found with the following directory format: CMIP6/CMIP/<institution_id>/<source_id>/<experiment_id>/<member_id>/<table_id>/<variable>/<grid_label>/<version> CMIP5 Australian Publishedand Official ReplicaDataThe CMIP5 published data can be found with the following directory structure: /g/data/rr3/publications/CMIP5/output1/<institute>/<model>/<experiment>/<frequency>/<realm>/<table>/<ensemble>/<version><variable> CMIP5 Official Replica DataThe CMIP5 official replica data (project code = rr3) and official replica data (project code = al33) can be found with the following directory structure: /g/data/<project>al33/publicationsreplicas/CMIP5/output1combined/<institute>/<model>/<experiment>/<frequency>/<realm>/<table>/<ensemble>/<version><variable> Note some of the key difference in the facets between CMIP5 and CMIP6, in particular "model" in CMIP5 has become "source_id" and "ensemble" has become "member_id". Other facets have similar names, though in CMIP6 the convention often includes an "_id". Definitions for directory format terms:
|
Section | |||||||||
---|---|---|---|---|---|---|---|---|---|
The following guidance material for CMIP6 data users is provided through PCMDI. It includes information on experiment design, model output, terms of use and citation, model documentation, error reporting, registering publications which use CMIP6 data, and CMIP6 governance. |