Update WAFS package #2018
Update WAFS package #2018
Conversation
… 2023 ICAO milestone 2. Update GCIP config file for NESDIS satellite upgrade
There was a problem hiding this comment.
Updates look as discussed. Left comments to make a couple small changes to release notes. Will approve for merge into release branch when addressed. Thanks @YaliMao-NOAA !
docs/Release_Notes.gfs.v16.3.11.md
Outdated
| Finally, NESDIS informed EMC that they will implement new global satellite composite data in Jan 2024. | ||
| This data set is used by one of WAFS packages. NESDIS provided a sample data set which Yali used to | ||
| develop an updated config file that works with current ops and to-be-implemented satellite data. | ||
| This updated config file will be implemented too. |
There was a problem hiding this comment.
Following the meeting discussion on Nov 3, the NESDIS changes are not going to be included in this release.
docs/Release_Notes.gfs.v16.3.11.md
Outdated
| Additionally, EMC is updating WAFS ecf definition file to 1)trigger WAFS blending job 5 min later | ||
| from 4:25 to 4:30 to compensate for 5-10 min delay in receiving UKMO high resolution data; | ||
| 2)stop producing blended 1.25 deg WAFS file per ICAO milestone. | ||
| Both sides agreed that we sill stop waiting for data from the other side at T+4:45. |
There was a problem hiding this comment.
| Additionally, EMC is updating WAFS ecf definition file to 1)trigger WAFS blending job 5 min later | |
| from 4:25 to 4:30 to compensate for 5-10 min delay in receiving UKMO high resolution data; | |
| 2)stop producing blended 1.25 deg WAFS file per ICAO milestone. | |
| Both sides agreed that we sill stop waiting for data from the other side at T+4:45. | |
| Additionally, EMC is updating WAFS ecf definition file to: | |
| 1. trigger WAFS blending job 5 min later from 4:25 to 4:30 to compensate for 5-10 min delay in receiving UKMO high resolution data | |
| 2. stop producing blended 1.25 deg WAFS file per ICAO milestone. | |
| Both sides agreed that we sill stop waiting for data from the other side at T+4:45. |
|
Steven didn't approve combining WAFS blending update and GCIP parm update this morning. I am going to make the change to switch back to gfs_wafs.v6.3.1 |
2. Modify release note
|
The current UK data at DCOM is /lfs/h1/ops/prod/dcom/20231103/wgrbbul/ukmet_wafs My question is how the parallel run will point to the para DCOM, not the prod DCOM. In global ecflow, which variable is controlling this? |
| @@ -1584,12 +1584,9 @@ suite gfs_v16_3 | |||
| trigger ../../post/jgfs_atmos_post_f000 == complete | |||
| task jgfs_atmos_wafs_grib2_0p25 | |||
| trigger ../../post/jgfs_atmos_post_f036 == complete | |||
| task jgfs_atmos_wafs_blending | |||
There was a problem hiding this comment.
@KateFriedman-NOAA 1.25 deg WAFS blending needs to be added back for #2100
There was a problem hiding this comment.
Ignore my prior reply, I see it's missing now but thankfully the ops version has it in /lfs/h1/ops/prod/packages/gfs.v16.3.11/ecf/defs/gfs_v16_3.def:
task jgfs_atmos_wafs_blending
trigger ./jgfs_atmos_wafs_grib2 == complete
time 04:33
There was a problem hiding this comment.
@KateFriedman-NOAA That's good. Cactus hasn't synchronized gfs.v16.3.11 yet so I can't compare the file.
There was a problem hiding this comment.
@YaliMao-NOAA You can compare the para install of that version on Cactus: /lfs/h1/ops/para/packages/gfs.v16.3.11/ecf/defs/gfs_v16_3.def
That's the package that was moved to prod on Dogwood.
There was a problem hiding this comment.
@KateFriedman-NOAA Good. The para version on Cactus includes 1.25 deg WAFS blending. Should I withdraw PR #2113?
There was a problem hiding this comment.
Should I withdraw PR #2113?
@YaliMao-NOAA Nope, all good! We were missing that change on our end so I've already merged that PR and we're good now. Thanks for catching that in our branch!
Update WAFS package to produce high resolution WAFS output to meet 2023 ICAO milestone
Refs #2013
Description
Type of change
Change characteristics
How has this been tested?
Checklist