search

WCRP-CORDEX / cordex-cmip6-cmor-tables

JSON Tables for CMOR3 to create CORDEX-CMIP6 datasets
https://wcrp-cordex.github.io/cordex-cmip6-cmor-tables
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

table Header #1

Closed larsbuntemeyer closed 3 months ago

larsbuntemeyer commented 2 years ago

I am not sure how to fill the table header and what consequences it will have, e.g., this is the current "CMIP6_fx.json" table header:

"Header": {
        "data_specs_version": "XX.XX.XX", 
        "cmor_version": "3.5", 
        "table_id": "Table fx", 
        "realm": "land", 
        "table_date": "18 November 2020", 
        "missing_value": "1e20", 
        "int_missing_value": "-999", 
        "product": "model-output", 
        "approx_interval": "0.00000", 
        "generic_levels": "alevel", 
        "mip_era": "CMIP6", 
        "Conventions": "CF-1.7 CMIP-6.2"

I'll have to find out what the other attributes mean, .e.g., generic_levels, approx_interval, etc...

data_specs_version : version of data request, e.g., dreqPy

larsbuntemeyer commented 2 years ago

here is some useful information (found in https://github.com/PCMDI/cmor/issues/442):

http://goo.gl/v1drZl

and here:

https://cmip6dr.github.io/Data_Request_Home/ https://pypi.org/project/dreqPy/

larsbuntemeyer commented 2 years ago

maybe the table header is not really relevant for CORDEX. I will keep it for now, we can still dump it later on.

larsbuntemeyer commented 3 months ago

my latest insight is:

the header is required for CMOR tools to run. However, i stripped it down to the minimum for now (removed generic_levels, realm, data_specs_version, cmor_version)...