-
Notifications
You must be signed in to change notification settings - Fork 110
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
Updates for new 20231027 orog fix file set #867
Comments
any update on this? Are the older versions of the fix files affected by this too or just the latest version? @andytangborn is having some issues generating cold start ICs and I don't know if it's related or not to this. |
For this issue, I'm still waiting for the fix files for NOAA-EMC/global-workflow#1981 to be ready and then we'll be wrapping up that issue and NOAA-EMC/global-workflow#1984 together and can do this. These updates are all new so I wouldn't suspect they'd impact current functionality. Just need to move to a new hash of UFS_UTILS in global-workflow when we also move to the new |
Thanks @KateFriedman-NOAA, just as an FYI, it seems that while building UFS_UTILS standalone this works fine, but building it as part of the workflow (which uses this https://github.com/NOAA-EMC/global-workflow/blob/1fc8b5bf55581de18e786611c65bc3f84bb0c082/versions/fix.ver#L17) it does not work |
I'm going to guess it's because UFS_UTILS is pointing to |
@KateFriedman-NOAA thanks yes that is what I guess too. Ok, well since it seems to still work using the old orog, I think @andytangborn and I can get by with the old orog until the new files are supported. |
@KateFriedman-NOAA and @CoryMartin-NOAA - I will fix the |
orog directory. Fixes ufs-community#867.
climo fixed files - i.e., C96 or C96.mx050. Fixes ufs-community#867.
name. Update chgres_cube regression tests accordingly. Fixes ufs-community#867.
@AlexanderRichert-NOAA - any idea why my workflows are failing? The spack-based installs are failing. |
Can you point me to a failed run? |
https://github.com/GeorgeGayno-NOAA/UFS_UTILS/actions/runs/7133553716/job/19426490024 |
When the 'precision' variant is set for ip, it expects the 'precision' variant from sp to be set, but it's only available with sp@2.4.0 onward. Would you be able to use a more recent sp? |
Let's try 2.4.0. |
name holding the surface climo data. Fixes ufs-community#867.
complete. Fixing will require a separate PR. Fixes ufs-community#867.
uncoupled orography data. Fixes ufs-community#867.
coupled or uncoupled model. Fixes ufs-community#867.
combinations of model and ocean resolutions. Fixes ufs-community#867.
to the regression test directory. Fixes ufs-community#867.
the 'orog' and 'sfc' files. Fixes ufs-community#867.
Update "./fix/link_fixdirs.sh" to point to the new 20231027 "orog" directory. Update "global_cycle" regression tests to point to a local copy of the required "orog" files. Update "global_cycle" scripts to use either form of the 'orog' files - i.e., C96 or C96mx100. Update "chgres_cube" to read either form of the surface climatological files, i.e., C96 or C96.mx100. Update the "gdas_init" scripts to use the 20231027 'orog' files. Update "./ush/chgres_cube.sh" and "./reg_tests/update_baseline.sh" for the new fixed surface directory name (is now ./sfc. previously ./fix_sfc). Update chgres_cube regression tests accordingly. Fixes #867.
A new
orog
fix file timestamp is being created for the GFS fix file developmental set. Some updates are needed in UFS_UTILS to accommodate changes in this new timestamp set.orog_ver=20231027
for the newGlobalLake*
fix files that previously lived in the unversionedraw/orog
subset. Any other related updates for this. Discussed in Update global lake data NOAA-EMC/global-workflow#1984.Files in new orog set:
oro_data
filenames used by gdas_init utility and anything else in UFS_UTILS (no longer using symlink in fix set). Change fromoro_C###.mx###.tile#.nc
toC###.mx###_oro_data.tile#.nc
. Discussed in Update fix files for HR3/EP5 NOAA-EMC/global-workflow#1981. Example in C384:Full list of affected files:
The text was updated successfully, but these errors were encountered: