-
Notifications
You must be signed in to change notification settings - Fork 180
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
GFSv16.3.21 - Remove WAFS from GFS #2591
Comments
Timeline update from @aerorahul :
|
|
Also update gfs_ver=v16.3.19 Refs NOAA-EMC#2591
Update the release notes for the WAFS removal from the GFS. Files and settings that are removed are noted. Also update `gfs_ver=v16.3.19`. Refs #2591
Just renamed the release branch to |
Thank you @KateFriedman-NOAA for your quick action. DA team members are meeting this afternoon to make a final decision as to what course of action to take. Submitting an ARFC to place PlanetiQ data in monitor mode is one option. Another option is to let the PlanetiQ data flow into and be assimilated by the GFS. This later option requires no EIB action. This issue is opened as a "heads up" to EIB in case the DA team goes with the first option. |
Synced the |
Merge remote-tracking branch 'origin/release/gfs.v16.3.20' into release/gfs.v16.3.21 Refs #2591 * origin/release/gfs.v16.3.20: Update GSI tag to gfsda.v16.3.20 for saildrone data (#2986) Update WAFS tag in release notes Set WAFS tag back to new gfs_wafs.v6.3.3 Revert "Remove WAFS from ops (#2889)" Update for obsproc/v1.3 and new AFWA global snow filename (#2957)
Sync merged the recently-handed-off changes for GFSv16.3.20 into the |
CDF submitted to NCO. |
WAFS CDF was also just submitted to NCO. EVS will also be submitting a companion CDF soon. |
@YaliMao-NOAA NCO has requested that we increase the walltime of the wafs 0p25 blending job to 40mins in the new WAFSv7.0.0 package. NCO made the change locally in the GFSv16.3.20 install:
Please make the same increase in the WAFSv7.0.0 package and recut the WAFS hand-off tag. Thanks! |
@KateFriedman-NOAA Thank you for the notification. |
Updates for the `enkfgdas_update` job from testing by NCO/GDIT and EMC. They produce a more stable runtime and bitwise identical outputs to ops. Add `export OMP_PROC_BIND=true` and update `APRUN_ENKF` to use `--cpu-bind core` instead of `--cpu-bind depth` in WCOSS2.env. Also, adjust npe (280) and thread (16) values. NCO requests that we include these updates in the GFSv16.3.21 package. Refs #2591
Merge synced the release/gfs.v16.3.20 changes into the release/gfs.v16.3.21 branch and recut the EMC-v16.3.21 tag. |
This is now v16.3.22. The new ops change documented in issue #3082 will go in before this and pushes this to v16.3.22. |
Update the version for the "WAFS removal from GFS" release branch to v16.3.22. Refs #2591
- updated release notes - remove all WAFS scripts and settings - include resource update for enkfgdas_update job Refs NOAA-EMC#2591
Remake the release branch for the WAFS removal from the GFS due to implementation order change. It includes changes previously made in the original release branch: - updated release notes - remove all WAFS scripts and settings - include resource update for enkfgdas_update job Refs #2591
The gfs_atmos_tropcy_qc_reloc did not properly parse the vitals info from a raw bulletin with a tab in the storm name field for storm "SIX". The code sorc/syndat_getjtbul.fd/getjtbul.d converting a tab to a space worked well for storms that have at least 4 characters in their names, but does not work as well for storms with 3-character names. This code change will fix the parsing problem for 3-character storms. Refs NOAA-EMC#2591
…3.21) (#3200) Update the `sorc/syndat_getjtbul.fd/getjtbul.f` code to resolve a problem parsing 3-character storm names. This update is being included in the GFSv16.3.21 package (with approval by NCO). From the developer @Qingfu-Liu: > The `gfs_atmos_tropcy_qc_reloc` job did not properly parse the vitals info from a raw bulletin with a tab in the storm name field for storm "SIX". The code sorc/syndat_getjtbul.fd/getjtbul.f converting a tab to a space worked well for storms that have at least 4 characters in their names, but does not work as well for storms with 3-character names. This code change will fix the parsing problem for 3-character storms. Refs #2591
Update from NCO/Xiaoxue:
|
From the January 24th 2025 RFC memo:
|
The WAFS is now a separate package in operations and is no longer a part of the GFS. Also included in this package are the following unrelated updates: 1. improvements to the enkfgdas_update job resource and environment settings 2. a fix for the syndat_getjtbul code when parsing 3-character storm names Refs #2591
Tagged and released: https://github.com/NOAA-EMC/global-workflow/releases/tag/gfs.v16.3.21 Announced to users. Closing this issue as complete. Thanks all! |
Description
Remove the WAFS (formerly EMC_gfs_wafs) from the GFS, it will now be a standalone system in operations.
WAFS issue: NOAA-EMC/WAFS#23
Target version
v16.3.21 (previously v16.3.22 (previously v16.3.23))
Expected workflow changes
Remove WAFS pieces:
WAFSF="NO"
-o
flag for checkout (?)The text was updated successfully, but these errors were encountered: