source_id add EC-Earth3-ESM-1

[treerink]

The EC-Earth consortium (institution_id is EC-Earth-Consortium) kindly asks for the following changes in the CMIP6_CV.json:

Please add a new configuration, i.e. a new source_id: EC-Earth3-ESM-1 as follows:

        "EC-Earth3-ESM-1":{
            "activity_participation":[
                "C4MIP",
                "CDRMIP",
                "CMIP",
                "DCPP",
                "LUMIP",
                "OMIP",
                "ScenarioMIP"
            ],
            "cohort":[
                "Published"
            ],
            "institution_id":[
                "EC-Earth-Consortium"
            ],
            "label":"EC-Earth3-ESM-1",
            "label_extended":"EC-Earth3-ESM-1",
            "license_info":{
                "exceptions_contact":"@ec-earth.org <- cmip6-data",
                "history":"2024-03-15: initially published under CC BY 4.0",
                "id":"CC BY 4.0",
                "license":"Creative Commons Attribution 4.0 International (CC BY 4.0; https://creativecommons.org/licenses/by/4.0/)",
                "source_specific_info":"",
                "url":"https://creativecommons.org/licenses/by/4.0/"
            },
            "model_component":{
                "aerosol":{
                    "description":"none",
                    "native_nominal_resolution":"none"
                },
                "atmos":{
                    "description":"IFS cy36r4 (TL255, linearly reduced Gaussian grid equivalent to 512 x 256 longitude/latitude; 91 levels; top level 0.01 hPa) and co2box v1.0 (CO2 box model; global grid)",
                    "native_nominal_resolution":"100 km"
                },
                "atmosChem":{
                    "description":"none",
                    "native_nominal_resolution":"none"
                },
                "land":{
                    "description":"HTESSEL (land surface scheme built in IFS) and LPJ-GUESS v4.1.2",
                    "native_nominal_resolution":"100 km"
                },
                "landIce":{
                    "description":"PISM v1.2 (5 km x 5 km for Greenland, 31 levels)",
                    "native_nominal_resolution":"5 km"
                },
                "ocean":{
                    "description":"NEMO3.6 (ORCA1 tripolar primarily 1 degree with meridional refinement down to 1/3 degree in the tropics; 362 x 292 longitude/latitude; 75 levels; top grid cell 0-1 m) and MWE v1.0 (Melt Water Emulator; same grid as ocean for the Antarctic surroundings) ",
                    "native_nominal_resolution":"100 km"
                },
                "ocnBgchem":{
                    "description":"PISCES v2 (same grid as ocean)",
                    "native_nominal_resolution":"100 km"
                },
                "seaIce":{
                    "description":"LIM3 (same grid as ocean)",
                    "native_nominal_resolution":"100 km"
                }
            },
            "release_year":"2024",
            "source_id":"EC-Earth3-ESM-1"
        },

Additional context: In the first place this EC-Earth3-ESM-1 configuration will be used for another project than the CMIP6 project, but that project will use the CMIP6 cmor tables as base (and the fork will be updated for the upstream updates). However, this EC-Earth3-ESM-1 might be later on also used for CMIP6 activities, therefore registration here is considered as the best option.

Thanks a lot,
Thomas

[treerink]

Hi, we are eagerly waiting for the registration of this new configuration ;)
Regards, Thomas

[durack1]

@treerink apologies for the delay, EC-Earth3-ESM-1 is now registered. Take a peek at CMIP6_source_id.html and let me know of any issues.

As you do not plan to publish data to ESGF, I'll leave this issue closed for now. If, in the future you want to publish to the project, we can always reopen this issue and amend the information.

[treerink]

@treerink apologies for the delay, EC-Earth3-ESM-1 is now registered. Take a peek at CMIP6_source_id.html and let me know of any issues.

Great, thanks a lot, looks perfect fine to me!

As you do not plan to publish data to ESGF, I'll leave this issue closed for now. If, in the future you want to publish to the project, we can always reopen this issue and amend the information.

Actually we will publish at the ESGF nodes with this configuration soon for the OptimESM project. However, this won't be as part of the CMIP6 framework, but as part of a new framework which has to cover OptimESM/TipESM/TipMIP maybe established as part of the CMIP6plus project, but this is currently heavily under discussion.

[durack1]

@treerink as we have EC-Earth3-ESM-1 registered here with no intention of publishing to the project, I wonder whether migrating the registration across to the WCRP-CMIP/CMIP6Plus_CVs repo might be a good idea?

If registration here is intended to enable the CMOR-required code to be useable by the project, this would be achieved by migrating the registration

ping @wolfiex @matthew-mizielinski @taylor13 - reopening as there may be actions required

[durack1]

@treerink just circling on the query above - about migrating this registration out of the CMIP6_CVs, project that you have no intention of publishing data to

[treerink]

Hi @durack1, as long as the CMP6+ has not adopted our and the related projects (OptimESM, TIPMIP etc.) we actually need to have it here. It's a little difficult story, but in order to avoid delay of delivery of products in our projects we will use the current CMIP6 CV and MIP tables so we can cmorise all the data (which is quite a lot) so results can be shared and analysed across partners. In a late stage when all is set with either an overarching CMIP6+ project or separate projects, we will fix the metadata with a fixer to make it ESGF publishable.

[durack1]

Hi @durack1, as long as the CMP6+ has not adopted our and the related projects (OptimESM, TIPMIP etc.) we actually need to have it here.

The statement above wasn't completely obvious to me. There are ongoing discussions with TIPMIP etc about registering their experiments into the CMIP6Plus_CVs for exactly the reason you outline - making it easier to CMORize and potentially publish these data on ESGF

@matthew-mizielinski ping

[matthew-mizielinski]

I've started on the steps towards registering TIPMIP in CMIP6Plus (more tomorrow). Once that is done lets look at clearing this out as it would be preferable to ensure that the CVs match the archive contents once we close CMIP6 to new submissions (timescales to be discussed at the next WIP meeting)