Fix 06z gfs_sfcanl jobs failing due to a bug in CCPP#4389
Fix 06z gfs_sfcanl jobs failing due to a bug in CCPP#4389DavidHuber-NOAA merged 18 commits intoNOAA-EMC:developfrom
Conversation
ush/parsing_ufs_configure.sh
Outdated
| local MOM6_OUTPUT_DIR="${MOM6_OUTPUT_DIR:-./MOM6_OUTPUT}" | ||
| local MOM6_RESTART_DIR="${MOM6_RESTART_DIR:-./MOM6_RESTART}" |
There was a problem hiding this comment.
| local MOM6_OUTPUT_DIR="${MOM6_OUTPUT_DIR:-./MOM6_OUTPUT}" | |
| local MOM6_RESTART_DIR="${MOM6_RESTART_DIR:-./MOM6_RESTART}" | |
| local MOM6_OUTPUT_DIR="./MOM6_OUTPUT" | |
| local MOM6_RESTART_DIR="./MOM6_RESTART" |
This isn't an option. The workflow will always write to this space. The other instances where this variable is set in this manner is ush/parsing_namelists_FV3.sh
There was a problem hiding this comment.
I agree, I don't think this should be configurable. This is assumed other places.
I also see that ufs-community/ufs-weather-model@6f22f57...f8b0802 we have a MOM6_OUTPUT_FH defined, which is defined in forecast_predet.
I'm assuming those are consistent definitions?
aerorahul
left a comment
There was a problem hiding this comment.
just one suggestion, looks good.
JessicaMeixner-NOAA
left a comment
There was a problem hiding this comment.
We should run a S2S test of some sort to make sure ocean output looks okay given the changes. I didn't follow exactly when those changes went in. @jiandewang or @dpsarmie might know more about that the MOM6_OUTPUT_FH to make sure that is as expected here now.
ush/parsing_ufs_configure.sh
Outdated
| local MOM6_OUTPUT_DIR="${MOM6_OUTPUT_DIR:-./MOM6_OUTPUT}" | ||
| local MOM6_RESTART_DIR="${MOM6_RESTART_DIR:-./MOM6_RESTART}" |
There was a problem hiding this comment.
I agree, I don't think this should be configurable. This is assumed other places.
I also see that ufs-community/ufs-weather-model@6f22f57...f8b0802 we have a MOM6_OUTPUT_FH defined, which is defined in forecast_predet.
I'm assuming those are consistent definitions?
|
|
Yes. And looking a bit further, this variable should be "FHOUT_OCN" and not MOM6_OUTPUT_FH. |
ClaraDraper-NOAA
left a comment
There was a problem hiding this comment.
I haven't tested it, but can confirm that this PR brings the needed update to CCPP/physics into UFS_UTILS to fix the gfs_sfcanl issue. It also updates the CCPP/physics used by the model to the same hash.
Note that updating the ufs_model and ufs_utils brings in many additional changes in addition to the gfs_sfcnl issue.
446b134
|
All tests passed on Ursa. I will run a develop C96C48mx500 case to verify the MOM6 output, then launch CI on all platforms. |
|
I verified the 6-hour MOM6 forecast for the >cmp /scratch3/NCEPDEV/stmp/David.Huber/rt_4389/COMROOT/C96C48mx500_S2SW_cyc_gfs_4389/gfs.20211220/18/model/ocean/history/gfs.t18z.6hr_avg.f120.nc /scratch3/NCEPDEV/global/role.glopara/GFS_CI_CD/URSA/BUILDS/GITLAB/nightly_6ada5183_010726/RUNTESTS/COMROOT/C96C48mx500_S2SW_cyc_gfs_6ada5183-6840/gfs.20211220/18/model/ocean/history/gfs.t18z.6hr_avg.f120.nc
> echo $?
0Proceeding with CI testing. |
|
The gaea c6 failure was caused by a build stalling on a known-bad head node. I will relaunch tests there now that CI is running there again smoothly. The SFS test failure on Ursa is known and that test has since been removed from the CI matrix. The Hera failure is the only concerning issue. The |
|
@JessicaMeixner-NOAA @dpsarmie is there a required WW3 update needed with this update? It appears that the wave grid changed unexpectedly from 0p50 to 0p16. |
|
@JessicaMeixner-NOAA @dpsarmie actually, this does not seem to be related to the model update. Last night's nightly also ran WW3 at 0p16 and archived correctly. I will continue investigating. |
|
I see now what happened. The |
|
I am still wrong. The Going to the end of the MPMD job at line 9891: It appears that |
7d7fe51
|
All tests passed on all platforms. Requesting final approvals to merge. |
| dep_dict = {'type': 'task', 'name': f'{self.run}_fbwind'} | ||
| deps.append(rocoto.add_dependency(dep_dict)) | ||
|
|
||
| if self.options['do_wave']: |
There was a problem hiding this comment.
This is okay to add but we don't actually archive any of the awips files for waves to my knowledge, so I don't think this is actually needed.
There was a problem hiding this comment.
Good to know! I'll open an issue to remove this tarball/job.
There was a problem hiding this comment.
Opened issues #4454 to retire AWIPS waves archiving.
Description
This fixes a bug in CCPP that prevented the 06Z
gfs_sfcanljob from running global_cycle on the 03Z IAU time. The code change now allows the input hour to be any integer between 0 and 23.Resolves #4364
Refs #4408 (partially resolves but a full investigation is needed)
Type of change
Change characteristics
How has this been tested?
Checklist