You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a test run of GFS HR4 performed by @RuiyuSun, execution of the post processing package is included, and the following log files indicated the following errors:
gfsarch.log: FATAL ERROR: Required file, directory, or glob gfs.20201030/00/products/atmos/wmo/gfs_collective1.postsnd_00 not found!
gfsawips_20km_1p0deg_f###-f###.log: End exgfs_atmos_awips_20km_1p0deg.sh ... with error code 30
gfswaveawipsbulls.log: FATAL ERROR: Job waveawipsbulls.95602 failed RETURN CODE 4
gfswaveawipsgridded.log: End exgfs_wave_prdgen_gridded.sh ... with error code 1
What should have happened?
The post processing scripts should all have run to completion without error or interruption.
Clone and build the workflow code from the indicated hash on WCOSS, then execute a single cycle (2020103000) that points to datasets available from the HR4 test case. Please consult @RuiyuSun for more specifications.
Additional information
Errors from gfswaveawipsbulls and gfswaveawipsgridded appear to result from a misread of Alaska buoy station information, and these scripts within the workflow may require reference to an updated table that links stations to expected data bulletins. @AminIlia-NOAA is added here for reference to the issue and the attached log files. gfswaveawipsbulls.log gfswaveawipsgridded.log
Errors resulting from gfsfbwind and gfsgempakncdcupagif are being assessed for potential inclusion with this issue.
Do you have a proposed solution?
The GETGB2P errors generated from gfsawips_20km_1p0deg - as seen in OUTPUT70005.txt - result from the absence of GRIB variable 5WAVH from the GFS control file, and appear related to those resolved through #2652; the relevant parameter tables will be modified in a similar manner. Resolution of errors from gfsawips_20km_1p0deg may subsequently resolve the absence of files causing the gfsarch error.
Once developed, the modifications resolving all errors described here will be bundled into one or two pull requests.
The text was updated successfully, but these errors were encountered:
What is wrong?
From a test run of GFS HR4 performed by @RuiyuSun, execution of the post processing package is included, and the following log files indicated the following errors:
What should have happened?
The post processing scripts should all have run to completion without error or interruption.
What machines are impacted?
WCOSS2
What global-workflow hash are you using?
4ad9695
Steps to reproduce
Clone and build the workflow code from the indicated hash on WCOSS, then execute a single cycle (2020103000) that points to datasets available from the HR4 test case. Please consult @RuiyuSun for more specifications.
Additional information
Errors from gfswaveawipsbulls and gfswaveawipsgridded appear to result from a misread of Alaska buoy station information, and these scripts within the workflow may require reference to an updated table that links stations to expected data bulletins. @AminIlia-NOAA is added here for reference to the issue and the attached log files.
gfswaveawipsbulls.log
gfswaveawipsgridded.log
Errors resulting from gfsfbwind and gfsgempakncdcupagif are being assessed for potential inclusion with this issue.
Do you have a proposed solution?
The GETGB2P errors generated from gfsawips_20km_1p0deg - as seen in OUTPUT70005.txt - result from the absence of GRIB variable 5WAVH from the GFS control file, and appear related to those resolved through #2652; the relevant parameter tables will be modified in a similar manner. Resolution of errors from gfsawips_20km_1p0deg may subsequently resolve the absence of files causing the gfsarch error.
Once developed, the modifications resolving all errors described here will be bundled into one or two pull requests.
The text was updated successfully, but these errors were encountered: