Fix several bugs in GFSv16 forecast-only cold-start mode #1177
Assignees
Labels
bug
Something isn't working
Comments
KateFriedman-NOAA
added a commit
to KateFriedman-NOAA/global-workflow
that referenced
this issue
Dec 13, 2022
- Change "free" to "forecast-only" for MODE setting in setup_expt_fcstonly.py. Refs NOAA-EMC#1177
KateFriedman-NOAA
added a commit
to KateFriedman-NOAA/global-workflow
that referenced
this issue
Dec 13, 2022
In config.base.emc.dyn (only developer version): - add MODE setting (set from setup scripts) - update IAU if-block to also check for forecast-only and cold-start modes to turn off IAU (corrects bug with f000) Refs NOAA-EMC#1177
|
Testing of GFSv16 forecast-only mode on WCOSS2 with UFS-UTILS-generated C192 cold-start ICs and bug fix now produces f000 outputs for cycles after the initial one: Next cycle: |
KateFriedman-NOAA
changed the title
KateFriedman-NOAA
added a commit
to KateFriedman-NOAA/global-workflow
that referenced
this issue
Jan 4, 2023
- In hpssarch_gen.sh add an if-block to check if cycled MODE for the pgb*anl files. Refs NOAA-EMC#1177
KateFriedman-NOAA
changed the title
9 tasks
KateFriedman-NOAA
added a commit
to KateFriedman-NOAA/global-workflow
that referenced
this issue
Jan 4, 2023
- Replaced tabs with spaces. Refs NOAA-EMC#1177
9 tasks
|
Resolved by #1208. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User reported bug in GFSv16 forecast-only cold-start mode.
Expected behavior
The f000 output from the forecast job should be produced in forecast-only mode when running with cold-start ICs (a.k.a. lower resolution).
Current behavior
When running forecast-only mode with cold-start ICs the f000 files are not produced by the forecast model in cycles after the initial cycle.
Machines affected
All.
To Reproduce
Run lower resolution / cold-start forecast-only mode for more than one cycle.
Detailed Description
Upon investigation it is an issue with the
IAU_OFFSETvariable being mismatched with theDOIAUsetting. TheDOIAUvariable will be set to no in the forecast job when the forecast script does not see prior cycle warm-start inputs but theIAU_OFFSETvariable does not get set to 0 to match. WithIAU_OFFSET=3the forecast model doesn't start producing output until 3hr (or 6hr if using 6hr frequency). This causes a ripple effect in the post, postsnd, and archive jobs. The post f000 files aren't produced and thus the postsnd and archive jobs fail.Possible Implementation
Need to check for forecast-only mode and cold-start earlier in the job so
IAU_OFFSET=0can be set and passed for the forecast model. The following if-block inconfig.base[.emc.dyn]can be expanded to handle this for now:...should be changed to:
Looking at the system, the
MODEvariable was added to the setup scripts but didn't make it into the config.Add
export MODE="@MODE@"intoconfig.base.emc.dynfor use by updated if-block conditions (shown above). Also change "free" to "forecast-only" insetup_expt_fcstonly.pyto be consistent withdevelopbranch implementation. Thedevelopbranch does not have this issue since it has the expanded check inconfig.base.Will correct, test, and commit into the
dev/gfs.v16branch.The text was updated successfully, but these errors were encountered: