-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update feature/coupled-crow for consistency w/model regtests #172
Comments
First step of pointing to new ufs-weather-model instead of ufs-s2s-model has been completed in my fork/branch here: |
After ufs-community/ufs-weather-model#270 Also, after NCAR/ccpp-physics#514 namelist options iovrsw and iovrlw will be replaced by a single iovr option |
All updates for this are in: https://github.com/JessicaMeixner-NOAA/global-workflow/tree/coupled/consistencyupdates (or already in feature/coupled-crow). Making a test run on orion and then will create PR. |
* add the SUBMODELNAME='RTMA' logic to update 10m wind for 3DRTMA * use 'submodelname' from the ctlblk_mod module
Top level CMakeLists.txt and CMakeLists.txt file in FV3 have been changed (and cleaned up) to use imported targets (mostly for NCEPLIBS). Remove *.appBuilder compsets and log. Remove outdated doc directory
Making these updates will help when adding new features from model upgrades to the workflow as most updates to the workflow can be mimicked by following a regression test of the model. The following are a few major recent items that should be updated:
Updating the name of the nems.configure for consistent naming of coupler restarts from CMEPS (See: https://github.com/ufs-community/ufs-weather-model/blob/develop/tests/parm/nems.configure.medcmeps_atm_ocn_ice_wav.IN#L110) will also need to update forecast scripts
Use only 1 MOM_input per resolution and have use_waves true/false see https://github.com/ufs-community/ufs-weather-model/blob/develop/tests/parm/MOM_input_template_025 or the other resolution MOM_inputs
update to point to ufs-weather-model instead of ufs-s2s-model (This could even be a chance to unify and just have one build of the model for standalone atm and coupled, but first step just point to ufs-weather-model.)
FYI @DeniseWorthen I think this covers the list we talked about if there are others I missed please add
The text was updated successfully, but these errors were encountered: