refactoring ERA5 data mode#396
Conversation
|
@billsacks I am still working on it. Once tests are passed I'll let you know. |
|
Hi @uturuncoglu @billsacks . May I ask if this is still planned? I'm interested so I ran some tests in UFS. There is also interest in using ERA5 for datm-ocn-ice work, like for RTOFS development. fyi, AI came back with some review notes (NickSzapiro-NOAA#11 (review)). |
|
@uturuncoglu I got a link to this (draft) PR from @NickSzapiro-NOAA in the context of UFS DATM with the "data" atmosphere coming from ERA-5. 2 questions for either/both of you:
|
Description of changes
This PR aims to restructure ERA5 data mode to support:
(1) Using ERA5 as a replacement of JRA55 under CESM framework. This work does not include any necessary change needs to be done in CIME interface.
(2) Adding new data component configuration option for data atmosphere (DATM) as
skip_field_check. The default value is.false.and does not change the exiting behavior. By setting it.true.the field check part is skipped and user is able to provide just set of fields supported by the data mode.(3) The changes related to support UFS WM RTs with help of (2) and also some other changes.
Specific notes
Contributors other than yourself, if any:
CDEPS Issues Fixed (include github issue #):
Are there dependencies on other component PRs (if so list):
No
Are changes expected to change answers (bfb, different to roundoff, more substantial):
No
Any User Interface Changes (namelist or namelist defaults changes):
New optional
skip_field_checkoption for datmTesting performed (e.g. aux_cdeps, CESM prealpha, etc):
UFS WM RTs:
UFS Coastal:
Hashes used for testing: