-
Notifications
You must be signed in to change notification settings - Fork 0
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
gsd/develop: add capability to call radiation on physics timestep for first N time steps #3
Conversation
…physics timestep for first nhfrad timesteps
@grantfirl should this change be made for SCM as well, or does radiation run on the physics time step anyway? |
Calls to radiation for the SCM are controlled identically to FV3, by the namelist values of fhswr and fhlwr converted to nsswr and nslwr in control_initialize, then used in GFS_time_vary_pre.scm to set the logicals. So, if it is deemed necessary for FV3, we'll probably want to have it in SCM too. |
This has been replaced by NOAA-GSL#1. |
Suggested changes to rucice PR
Constant branch update from Dom 2021/08/02
Update to mraerosol branch from Dom
Update cloud_cover_xr with latest change from NCAR ccpp-physics main
Fix the rest of the Cheyenne/GNU tests
Revert combination, update to ufs/dev, and update CODEOWNERS
Merge PR NCAR#121 and resolve conflicts
Random fixes for HR4 GWD update
This PR adds the capability to allow for radiation being called on physics timestep for first nhfrad timesteps (coldstarts only, for spinup) to physics/GFS_time_vary_pre.fv3.*
The new functionality is activated by setting nhfrad in the gfs physics namelist section to a value larger than one (default is zero).
Associated PR: climbfuji/fv3atm#1
This PR has been tested to work on macOS/GNU and needs to be tested for b4b identical results when nhfrad is not set (default value is zero) on hera/intel.