separation of grids in config_grids.xml - Githubissues

ESMCI / ccs_config_cesm

CESM CIME Case Control System configuration files

3 stars 46 forks source link

separation of grids in config_grids.xml #2

Closed mvertens closed 2 years ago

mvertens commented 2 years ago

The current config_grids.xml that has just been migrated to this repository is confusing.

some new grids are only supported for nuopc and older grids are only supported for mct.
nuopc also no longer needs domain files other than for land.
so the situation was getting progressively more confusing. I propose splitting up the files into the following new files?

config_grids_mct.xml 
   component_grids_mct.xml
   modelgrid_aliases_mct.xml
   maps_mct.xml

config_grids_nuopc.xml
   component_grids_nuopc.xml
   modelgrid_aliases_nuopc.xml
   maps_nuopc.xml

component_grids_xxx.xml- specifies the component grids that are available.
- for nuopc - if a user wants to add a new grid - the ONLY entry they normally need is just here (assuming that the long name will be used when calling create_newcase). Since mapping files are normally not needed for nuopc, this will normally just entail creating a new mesh file.
modelgrid_aliases_xxx.xml- specifies the aliases that are used when calling create_newcase. This is really only needed when new model grids are supported and used in testing. For just experimentation with a new grid, this will will not need to be changed.
maps_xxx.xml - specifies the mapping files between components that are needed. For nuopc this includes rof->ocn, glc->ocn and glc->ice mapping files - and also new mizuroute mapping files between the lnd->rof that are needed for performance reasons.

Since the grid is specified created at create_newcase time - introducing new grids cannot be put in the SourceMods. But it seems fairly lightweight now to just add one entry to component_grids_nuopc.xml.

mvertens commented 2 years ago

Resolved by PR #1