You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current land perturbation scheme (lndp=2) needs to be updated to the Noah-MP land model for use in GFSv17.
Solution
Update the routine applying land perturbations to also work with Noah-MP.
At the same time, revise the namelist options for applying land perturbations to the regional system (HRRR), since these are currently confusing and sometimes use the land model as a proxy for a regional / global run.
Alternatives
None.
Testing:
NA. Raising an issue at the moment.
Have you tested the code changes? On what platforms?
Have you run regression test in ufs-weather-model or ufs-s2s-model with code changes?
Will the baseline results change?
If yes, please give brief explanation of your code updates on the regression test.
…add export of openwater_frac_in_atm from fv3ATM when coupled (NOAA-EMC#475)
* update CICE in ufs-weather for the latest emc/develop
* fix ice_in_template; sw_redist has been moved to shortwave_nml and removed two unused settings
* update fv3ATM to use esmf-bs47 and add the export of open-water fraction from fv3ATM
* update module files to use bs47 (PR NOAA-EMC#493)
* fix wcoss-cray for alt-compare functionality
* update CMEPS and NEMS for added export field
* update Dockerfile
Description
The current land perturbation scheme (lndp=2) needs to be updated to the Noah-MP land model for use in GFSv17.
Solution
Update the routine applying land perturbations to also work with Noah-MP.
At the same time, revise the namelist options for applying land perturbations to the regional system (HRRR), since these are currently confusing and sometimes use the land model as a proxy for a regional / global run.
Alternatives
None.
Testing:
NA. Raising an issue at the moment.
Dependent PRs:
Issues:
ufs-weather-model #1076
stochastic_physics #55
fv3atm #493
The text was updated successfully, but these errors were encountered: