ESCOMP
out-of-the-box functionality for dyamond configuration
What is the feature/what would you like to discuss?
We would like to implement out-of-the-box functionality for our dyamond configurations, which are AMIP experiments using global 3.75 km CAM-MPAS. The 3.75 km grid is already implemented in CESM, and so the work consists of developing compsets FDYAMOND1 & FDYAMOND2, implementing datasets in namelist_defaults, and use_cases setting namelists as well as xml variables controlling the pe layout, PIO settings, etc... that we've found necessary to run this large-configuration on derecho. We also would like an error check to ensure that the correct grid alias is set by the user when these compsets are invoked, or if users try to override certain xml settings.
Getting this running oob will also require a CLM issue & PR, which I will link here when opened. If we want these compsets to invoke the official dyamond SST/sea-ice datasets, it will require a separate CDEPS PR.
Is there anyone in particular you want to be part of this conversation?
@briandobbins @PeterHjortLauritzen @JulioTBacmeister @marybarthbrock
Will this change (regression test) answers?
Yes
Will you be implementing this enhancement yourself?
Yes
PR for MPAS physics-dynamics coupling used in DYAMOND simulation is in progress: https://github.com/ESCOMP/CAM/pull/1304
@cacraigucar re-opening this as #1304 does not resolve this issue, but just a piece of it. We've yet to open a PR to resolve all the other stuff.