Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A set of 25 core variables from the CORDEX archive were identified for the CDS. These are the most used of the CORDEX data. These variables are provided from 5 CORDEX experiment types (evaluation, historical and 3 RCP scenarios)  that are derived (downscaled) from the CMIP5 experiments.

ANDRAS: I think, we have to indicate here, that for the non-European domain we provide lass variables and maybe in the table below indicate, which ones are only for the EURO-CORDEX or meMed-CORDEX domains.

GL: That's difficult and also depends on the RCMs. I propose to at least indicate into the table of variable the one we "try" to provide for each domain (basically one additional column per domain).

The CDS subset of CORDEX data have been through a metadata quality control procedure which ensures a high standard of reliability of the data. It may be for example that similar data can be found in the main CORDEX archive at the ESGF (Earth System Grid Federation) however these data come with no quality assurance and may have metadata errors or omissions. The quality-control process means that the CDS subset of CORDEX data is further reduced to exclude data that have metadata errors or inconsistencies. It is important to note that passing of the quality control should not be confused with validity: for example, it will be possible for a file to have fully compliant metadata but contain gross errors in the data that have not been noted. In other words, it means that the quality control is purely technical and does not contain any scientific evaluation (for instance consistency check).

ANDRAS: I think, here we have to mention that we also publish data, which had not been available so far in the ESGF. GL : Is there any dataset in this case? Euro-CORDEX comes from the ESGF, even the new simulations from PRINCIPLES that are published on the ESGF first. Med-CORDEX will be published on the ESGF in a second step after the 34b Lot 1. And for 34d data, non-ESGF data will be published on the ESGF and ESGF data have been just Qc-ed for CDS. So I don't see any dataset that exist on the CDS which is/will be not on the ESGF.

that we also publish data, which had not been available so far in the ESGF. We can mention the additional effort (of 34d) to find the additional data for non-European domains. Maybe the link to the IPCC Atlas should be also mentioned. GL: I agree.

In addition, CORDEX data for CDS includes Persistent IDentifiers (PID) in their metadata which allows CDS users to report any error during the scientific analysis. The error will be at least documented on the ESGF Errata Service (http://errata.es-doc.org) 

ANDRAS: would you check this link to the ERRATA, please, it does not work for me!  GL: Bug with the web-service, solved now.

but also planned to be documented in the CDS. The CDS aims to publish only the latest versions of the datasets.

...

ANDRAS: we will need an additional paragraph here for the non-European domains and of course similar tables for the other domains below the EURO-CORDEX oneCORDEX one. 

GL: I let Manuel for the additional paragraph. I will update the table of simulations once we agreed on the different decisions to take (cf. our mail thread about this).



Driving Global Coupled Models


HadGEM2-ESEC-EARTHCNRM-CM5NorESM1-MMPI-ESM-LRIPSL-CM5A-MRCanESM2MIROC5

Regional Climate Models

RCA4 (SMHI)111113
11111113
11





CCLM-8-17 (ETH)
11111
11



11





1

crCLIM-v1-1-1 (ETH)




1




1

2








REMO2009 (GERICS)











222







1
REMO2015 (GERICS)11
11



111

11




1
1
RACMO22E (KNMI)1111231111
11
1

1





HIRHAM5 (DMI)
12224

1
22

1








WRF361H (UHOH)













1








WRF381P (IPSL)

1

1

1

1



11





ALADIN53 (CNRM)





111














ALADIN63 (CNRM)

1


111




1








RegCM4.6.1 (ICTP)























HadGEM3-GA7-05 (MOHC)

1

1












































RCP26RCP45RCP85
[0-9] = Number of simulations

...

ANDRAS: I think, this can be a bit confusing, since above we mention that we publish only the latest version. So somehow we have to explain clearly what is the difference between model version and dataset number.

GL: As said in my email, this could be delegate to the Errata Service and we can remove this paragraph. What do you think? I will create an issue on the Errata test instance to show how it looks like.

On a general level in the CDS form for the RCM simulations “v” enumerates runs and NOT model versions. For the DMI, KNMI and SMHI runs numbers different from “v1” means new simulations relative to the first “v1” one. It might not mean a new version. Hereafter we describe the meaning of the different dataset numbers for those models, which have some.

...

For CORDEX data, the ensemble member is equivalent to the ensemble member of the CMIP5 simulation used to extract boundary conditions.

List of published parameters ANDRAS: maybe here we can indicate with bold face those variables, which are available only for the EURO-CORDEX domain GL : see my above comment on this.

NameShort nameUnitsDescription
2m temperaturetasKThe temperature of the air near the surface (or ambient temperature). The data represents the mean over the aggregation period at 2m above the surface.
200hPa temperatureta200KThe temperature of the air at 200hPa. The data represents the mean over the aggregation period at 200hPa pressure level.
Minimum 2m temperature in the last 24 hourstasminKThe minimum temperature of the air near the surface. The data represents the daily minimum over the aggregation period at 2m above the surface. ANDRAS: I guess this variable is available only for daily data, is that correct?
Maximum 2m temperature in the last 24 hourstasmaxKThe maximum temperature of the air near the surface. The data represents the daily maximum over the aggregation period at 2m above the surface. ANDRAS: I guess this variable is available only for daily data, is that correct?
Mean precipitation fluxprkg.m-2.s-1The deposition of water to the Earth's surface in the form of rain, snow, ice or hail. The precipitation flux is the mass of water per unit area and time. The data represents the mean over the aggregation period.
2m surface relative humidityhurs%

The relative humidity is the percentage ratio of the water vapour mass to the water vapour mass at the saturation point given the temperature at that location. The data represents the mean over the aggregation period at 2m above the surface.

2m surface specific humidityhussDimensionlessThe amount of moisture in the air at 2m above the surface divided by the amount of air plus moisture at that location. The data represents the mean over the aggregation period at 2m above the surface.
Surface pressurepsPa

The air pressure at the lower boundary of the atmosphere. The data represents the mean over the aggregation period.

Mean sea level pressurepslPaThe air pressure at sea level. In regions where the Earth's surface is above sea level the surface pressure is used to compute the air pressure that would exist at sea level directly below given a constant air temperature from the surface to the sea level point. The data represents the mean over the aggregation period.
10m Wind SpeedsfcWindm.s-1The magnitude of the two-dimensional horizontal air velocity. The data represents the mean over the aggregation period at 10m above the surface.
Surface solar radiation downwardsrsdsW.m-2The downward shortwave radiative flux of energy per unit area. The data represents the mean over the aggregation period at the surface.
Surface thermal radiation downwardrldsW.m-2

The downward longwave radiative flux of energy inciding on the surface from the above per unit area. The data represents the mean over the aggregation period.

Surface upwelling shortwave radiationrsusW.m-2

The upward shortwave radiative flux of energy from the surface per unit area. The data represents the mean over the aggregation period at the surface.

Total cloud covercltDimensionlessTotal refers to the whole atmosphere column, as seen from the surface or the top of the atmosphere. Cloud cover refers to fraction of horizontal area occupied by clouds. The data represents the mean over the aggregation period.
500hPa geopotentialzg500mThe gravitational potential energy per unit mass normalized by the standard gravity at 500hPa at the same latitude. The data represents the mean over the aggregation period at 500hPa pressure level.
10m u-component of winduasm.s-1The magnitude of the eastward component of the wind. The data represents the mean over the aggregation period at 10m above the surface.
10m v-component of windvasm.s-1The magnitude of the northward component of the wind. The data represents the mean over the aggregation period at 10m above the surface.
200hPa u-component of the windua200m.s-1

The magnitude of the eastward component of the wind. The data represents the mean over the aggregation period at 200hPa above the surface.

200hPa v-component of the windva200m.s-1The magnitude of the northward component of the wind. The data represents the mean over the aggregation period at 200hPa pressure level.
850hPa U-component of the windua850m.s-1The magnitude of the eastward component of the wind. The data represents the mean over the aggregation period at 850hPa pressure level.
850hPa V-component of the windva850m.s-1The magnitude of the northward component of the wind. The data represents the mean over the aggregation period at 850hPa pressure level.
Total run-off fluxmrrokg.m-2.s-1

The mass of surface and sub-surface liquid water per unit area and time, which drains from land. The data represents the mean over the aggregation period.

Mean evaporation fluxevspsblkg.m-2.s-1

The mass of surface and sub-surface liquid water per unit area ant time, which evaporates from land. The data includes conversion to vapour phase from both the liquid and solid phase, i.e., includes sublimation, and represents the mean over the aggregation period.

Land area fractionsftlf%The percentage of the surface occupied by land, aka land/sea mask. The data  is time-independent.
OrographyorogmThe surface altitude in the model. The data is time-independent.

...

  • <variable> is a short variable name, e.g. “tas” for ”temperature at the surface”
  • <driving-model> is the name of the model that produced the boundary conditions
  • <experiment> is the name of the experiment used to extract the boundary conditions
  • <ensemble-member> is the ensemble identifier in the form “r<X>i<Y>p<Z>”, X, Y and Z are integers
  • <rcm-model> is the name of the model that produced the data
  • <rcm-run> is the version run of the model in the form of "vX" where X is integer
  • <time-frequency> is the time series frequency (e.g., monthly, daily, seasonal) 
  • 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-CORDEX subset ANDRAS: any additional information for QC of the non-European domains, particularly those, who were not in the ESGF? GL: 34d has a beautiful diagram on the differnet QC steps that could be interesting to copy-paste here.

The CDS subset of the CORDEX 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-CORDEX subset or if possible the error is corrected and a note made in the history attribute of the file. The quality control of the CDS-CORDEX subset checks for metadata errors or inconsistencies against the Climate and Forecast (CF) Conventions and a set of CORDEX specific file naming and file global metadata conventions. 

...