[dev/gfs.v17] Update the UFSWM and UFS_UTILS hash

[dpsarmie]

Description

This PR will update the dev/gfs.v17 branch in Global Workflow that updates the UFS_UTILS and UFSWM production hashes.

The UFSWM updates include an update to CCPP to reduce warnings (ufs-community/ccpp-physics#360) and a atmos-cubed update to relax the warning range on TA_dyn (NOAA-GFDL/GFDL_atmos_cubed_sphere#405).

The UFS_UTILS update just updates the CCPP hash to match the hash in UFSWM.

Type of change

• Bug fix (fixes something broken)
• New feature (adds functionality)
• Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

• Is this change expected to change outputs (e.g. value changes to existing outputs, new files stored in COM, files removed from COM, filename changes, additions/subtractions to archives)? NO
  • GFS
  • GEFS
  • SFS
  • GCAFS
• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO
• Does this change require an update to any of the following submodules? YES/NO (If YES, please add a link to any PRs that are pending.)
  • EMC verif-global
  • GDAS
  • GFS-utils
  • GSI
  • GSI-monitor
  • GSI-utils
  • UFS-utils [production/GFS.v17.0.0] Update to latest CCPP_Phys production/GFS.v17 hash ufs-community/UFS_UTILS#1137
  • UFS-weather-model [production/GFS.v17] Modify FV3 warning range trigger and fix some CCPP warnings ufs-community/ufs-weather-model#3128
  • wxflow

How has this been tested?

Tested on WCOSS2 and Gaea with UFSWM regression tests.

Checklist

• Any dependent changes have been merged and published
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have documented my code, including function, input, and output descriptions
• My changes generate no new warnings
• New and existing tests pass with my changes
• This change is covered by an existing CI test or a new one has been added
• Any new scripts have been added to the .github/CODEOWNERS file with owners
• I have made corresponding changes to the system documentation if necessary

[dpsarmie]

The plan for this PR is that it won't be merged until there is a recompile needed for the GFSv17 retros.

[JessicaMeixner-NOAA]

What is the desired name for log files in COM for MOM6 log files? Do we need both the output and restart log files in COM?

atm log file name is: model/atmos/history/gfs.t00z.log.f016.txt

ocean output files are: model/ocean/history/gfs.t00z.6hr_avg.f006.nc

Log file name thoughts: gfs.t00z.6hr_avg.log.f006.txt or gfs.t00z.log.f006.txt

If we add restart logs, maybe:
20211221.030000.MOM.res.log.txt (corresponds with 20211221.030000.MOM.res.nc)

@TravisElless-NOAA @DavidHuber-NOAA

I'm working on translating the MOM6 logs to the appropriate COM directories.

For reference I reran a forecast
/lfs/h2/emc/stmp/jessica.meixner/RUNDIRS/C96C48mx500_S2SW_cyc_gfs_mom602/gfs.2021122100/gfsfcst.2021122100/fcst.453353 (it's still running, should be done soon)

But we have log files:
20211221.060000.mom6.06h 20211221.120000.mom6.06h 20211221.120000.mom6.res 20211221.180000.mom6.06h 20211222.000000.mom6.res

Output is:
MOM6_OUTPUT
available_diags.000000 ocean.stats ocn_2021_12_21_21_00.nc ocn_2021_12_23_03_00.nc ocn_2021_12_24_09_00.nc ocn_2021_12_25_15_00.nc
MOM_parameter_doc.all ocean.stats.nc ocn_2021_12_22_03_00.nc ocn_2021_12_23_09_00.nc ocn_2021_12_24_15_00.nc ocn_2021_12_25_21_00.nc
MOM_parameter_doc.debugging ocn_2021_12_21_03_00.nc ocn_2021_12_22_09_00.nc ocn_2021_12_23_15_00.nc ocn_2021_12_24_21_00.nc Vertical_coordinate.nc
MOM_parameter_doc.layout ocn_2021_12_21_09_00.nc ocn_2021_12_22_15_00.nc ocn_2021_12_23_21_00.nc ocn_2021_12_25_03_00.nc
MOM_parameter_doc.short ocn_2021_12_21_15_00.nc ocn_2021_12_22_21_00.nc ocn_2021_12_24_03_00.nc ocn_2021_12_25_09_00.nc

Restarts are:
MOM6_RESTART
20211221.120000.MOM.res.nc 20211222.000000.MOM.res.nc

Matching restarts is straightforward. as they have same dates.

Output, is less straightforward, b/c the file name is the mid-point, where as the output appears to be the YMDH of the end of the interval.

[JessicaMeixner-NOAA]

Currently testing with: gfs.t00z.6hr_avg.log.f006.txt

This can be changed.