-
Notifications
You must be signed in to change notification settings - Fork 168
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.22 - 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. |
@YaliMao-NOAA Good point, sounds good, thanks! |
- Add OMP_PROC_BIND=true and update APRUN_ENKF to use "--cpu-bind core" instead of "--cpu-bind depth" in WCOSS2.env. - Adjust npe (280) and thread (16) values. Updates come from testing by NCO/GDIT and produce a more stable runtime and bitwise identical outputs to ops. NCO requests that we include these updates in the GFSv16.3.21 package. Refs NOAA-EMC#2591
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
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.22
Expected workflow changes
Remove WAFS pieces:
WAFSF="NO"
-o
flag for checkout (?)The text was updated successfully, but these errors were encountered: