WCRP-CORDEX / cordex-cmip6-cv

Controlled Vocabulary (CV) for use in CORDEX
BSD 3-Clause "New" or "Revised" License
1 stars 7 forks source link

values in CORDEX-CMIP6_activity_id.json #33

Closed gnikulin closed 9 months ago

gnikulin commented 12 months ago

We need to edit https://github.com/WCRP-CORDEX/cordex-cmip6-cv/blob/main/CORDEX-CMIP6_activity_id.json be deleting "FPS" and "Adjust" and changing "RCM" to "DD". Can be simply ?

{
  "activity_id": {
    "DD": "Dynamical Downsacling",
    "ESD": "Empirical Statistical Downscaling"
   }
 }
larsbuntemeyer commented 12 months ago

Ok, i'll try to close some issues including this during this week!

jesusff commented 12 months ago

OK, I updated this, but kept the original list format, since this impacts the way CMOR validates entries https://github.com/WCRP-CORDEX/cordex-cmip6-cv/blob/b57012e00e28b54d148507b05605110220fe0085/CORDEX-CMIP6_activity_id.json#L1-L6 Also, there is currently no activity attribute, so the explanation would not be used in the DRS. This attribute would be helpful to clarify the meaning of the activity_ids, though (see #20). It could be more explicit, such as

{
  "activity_id": {
    "DD": "Dynamical downscaling on standard CORDEX continental domains",
    "ESD": "Empirical-statistical downscaling on standard CORDEX continental domains"
   }
 }
gnikulin commented 12 months ago

In CMIP6 activityis defined in CMIP6_activity_id.json but not used as an attribute. By the way, this CV in CMIP6 has format

{
    "activity_id":{
        "AerChemMIP":"Aerosols and Chemistry Model Intercomparison Project",
        "C4MIP":"Coupled Climate Carbon Cycle Model Intercomparison Project",
gnikulin commented 12 months ago

I'm not sure about adding that these 2 activities are for the standard continental-scale CORDEX domains and would use "Dynamical downscaling" and "Empirical-statistical downscaling" as general definitions. Currently, there is no common framework for sub-domains, only within different FPS, another challenge.

jesusff commented 12 months ago

Yes, I agree that for the moment we can keep it general, but we need to provide some anchorage for future activities. Since we are restricting the domain_ids, this CV can hardly cover other activities not focused on continental domains. And if another initiative, such as an FPS, considers other domains, it will need to define them in its own CV as a separate activity, in order not to mix the results in the search. I continue with some examples in #20 to avoid lengthening this issue, which can be closed easily.

gnikulin commented 12 months ago

Yes, I agree that this case is only for the 14 continental-scale domains and in general we need to consider possible sub-domain activities. So currently we can use:

{
  "activity_id": {
    "DD": "Dynamical downscaling",
    "ESD": "Empirical-statistical downscaling"
   }
 }

ML-based downscaling methods can be another activity in this CV.

larsbuntemeyer commented 11 months ago

closed by b57012

gnikulin commented 9 months ago

My understanding is that we agreed on:

{
  "activity_id": {
    "DD": "Dynamical downscaling",
    "ESD": "Empirical-statistical downscaling"
   }
 }

while the current CMIP6_activity_id.json is still

{ 
     "activity_id": [ 
         "DD", 
         "ESD" 
     ] 
 } 

or any CMOR-related issues ??