UFS-dev PR#57#95
Conversation
…pplication; utilize custom restart names for WW3 (was ufs-community#1684) (ufs-community#1692) * set configuration variable true to use non-default restart file names in WW3 * change name of WW3 used for restart tests * change name of WW3 in hafs wav tests * update CMEPS
…KMPI (ufs-community#1681) * Remove DEBUG_LINKMPI logic
…astic perturbations) needed for GFS/GEFS prototypes (ufs-community#1677) * Bugfix for convection (prog closure) and gravity wave drag (for stochastic perturbations) needed for GFS/GEFS prototypes Co-authored-by: Michael Toy <michael.toy@noaa.gov>
|
From ufs-community#1692, expected failures are: Cheyenne/GNU Cheyenne/INTEL |
|
cpld_control_gfsv17 is expected to fail from ufs-community#1677 changes alone |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
on-behalf-of @NCAR <dswales@ucar.edu>
|
Automated RT Failure Notification |
|
Out of space on Cheyenne, and I still don't have permissions for clearing enough space for the auto RTs, so I ran a creation of new baselines for Cheyenne/intel manually and verified against them. The new baselines are in: /glade/scratch/grantf/FV3_RT/REGRESSION_TEST_INTEL |
Identical to ufs-community#1677
needs
EP4tag after mergeContains changes from ufs-community#1692 (BL change) and ufs-community#1681 (no BL change)