...
For pressure level data the model output is available on the pressure levels according to the table below. Note that since the model output is standardised all models produce the data on the same pressure levels. I SAW WE WILL HAVE ALSO 3-HOURLY DATA, THEY ALL WILL BE SINGLE LEVEL FIELDS?
Frequency | Number of Levels | Pressure Levels (hPa) |
Daily | 8 | 1000., 850., 700., 500., 250., 100., 50., 10. |
Monthly | 19 | 1000., 925., 850., 700., 600., 500., 400., 300., 250., 200., 150., 100., 70., 50., 30., 20., 10., 5., 1. |
Ensembles
IN THE FIRST BATCH WE WILL HAVE ONLY THE CONTROL MEMBER. I HOPE (WE ARE DISCUSSING THIS ISSUE WITH RUTH AND MARTIN) WE WILL HAVE ALSO ENSEMBLE MEMBERS. THEREFORE I GUESS THE TEXT BELOW WILL NOT BE NEEDED AT THE FIRST PUBLICATION.
Each modelling centre typically run the same experiment using the same model with slightly different settings several times to confirm the robustness of results and inform sensitivity studies through the generation of statistical information. A model and its collection of runs is referred to as an ensemble. Within these ensembles, four different categories of sensitivity studies are done, and the resulting individual model runs are labelled by four integers indexing the experiments in each category
...
- Global metadata: these fields can describe many different aspects of the file such as
- when the file was created
- the name of the institution and model used to generate the file
- Information on the horizontal grid and regridding procedure
- links to peer-reviewed papers and technical documentation describing the climate model,
- links to supporting documentation on the climate model used to generate the file,
- software used in post-processing.
- variable dimensions: such as time, latitude, longitude and height
- variable data: the gridded data
- variable metadata: e.g. the variable units, averaging period (if relevant) and additional descriptive data
File naming conventions
THIS WILL CHANGE, SINCE WE WILL NOT ANY MORE OFFER FULL FILES USING THE WPS SERVICES. THE OUTPUT FILE NAMES WILL BE PROPOSED BY THE WPS TEAM OR THE CDS TEAM, TO BE CHECKED WITH THEM!
When you download a CMIP6 file from the CDS it will have a naming convention that is as follows:
...
CDS users will now be able to apply subsetting operations to CMIP6 datasets. This mechanism (the "roocs" WPS framework) that runs at each of the partner sites: CEDA, DKRZ and IPSL. The WPS can receive requests for processing based on dataset identifiers, a temporal range, a bounding box and a range of vertical levels. Each request is converted to a job that is run asynchronously on the processing servers at the partner sites. NetCDF files are generated and the response contains download links to each of the files. Users of the CDS will be able to make subsetting selections using the web forms provided by the CDS catalogue web-interface. More advanced users will be able to define their own API requests in the CDS Toolbox that will call the WPS. Output files will be automatically retrieved so that users can access them directly within the CDS.WE WILL HAVE TO UPDATE THIS PART ABOVE ONCE NEW PROCESSES (LIKE AVERAGING OR RE-GRIDDING WILL BE AVAILABLE)
References
Durack, P J. (2020) CMIP6_CVs. v6.2.53.5. Available at: https://github.com/WCRP-CMIP/CMIP6_CVs (Accessed: 26 October 2020).
...