-
Notifications
You must be signed in to change notification settings - Fork 7
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
UFS-dev PR#22 #82
UFS-dev PR#22 #82
Conversation
… indices. (ufs-community#1497) * fv3 surface restart io: turn some calls into loops * turn many loops into subroutine calls, and remove nt_save * Refactor surface restart logic in FV3GFS_io.F90 to not use hard-coded indices Co-authored-by: Brian Curtis <[email protected]> Co-authored-by: jkbk2004 <[email protected]>
* Enhanced stability of drag_suite module and added diagnostics * Added new UGWP diagnostic variables to parm/diag_table/diag_table_rap * Bug fixes to rap, hrrr and rrfs test description files and tests/parm/rap.nml.IN * Updated standard_names for do_gsl_drag_ls_bl, do_gsl_drag_ss, do_gsl_drag_tofd and ugwp_seq_update * Incorporated dustinswales suggestions in ccpp-physics PR#22 * Assumed-shape in gwdps.f * Added logical flag 'ugwp_seq_update' to gfs_physics_nml namelist * Modified calculation of dtfac in drag_suite.F90 and revised various long_name's of diagnostic variables * Removed passage of variables 'ak' and 'bk' to drag_suite -- these are no longer used * Removed unused variables from GFS_typedefs.F90 and added clarifying comments in ccpp-physics Co-authored-by: JONG KIM <[email protected]>
Includes ufs-community#1497 |
Requires baseline change for tests using unified_ugwp |
Automated RT Failure Notification |
Automated RT Failure Notification |
Automated RT Failure Notification |
Automated RT Failure Notification |
Automated RT Failure Notification |
Automated RT Failure Notification |
on-behalf-of @NCAR <[email protected]>
Automated RT Failure Notification |
on-behalf-of @NCAR <[email protected]>
Automated RT Failure Notification |
@dustinswales Looks like the cheyenne storage quota is full. Can you make some space when you get a chance and delete the 20220109 baseline dirs on cheyenne? |
on-behalf-of @NCAR <[email protected]>
Automated RT Failure Notification |
on-behalf-of @NCAR <[email protected]>
Automated RT Failure Notification |
Identical to ufs-community#1488