-
Notifications
You must be signed in to change notification settings - Fork 180
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
gdasfcst task failure with warnings during canopy conductance step, abnormal 2MT, HDF errors #652
Comments
@BrettHoover-NOAA The abnormal 2MT warnings are not too uncommon the Antarctic winter. The HDF error usually signifies an error in creating the |
Thanks @DavidHuber-NOAA, I'm running a test with this change to config.fcst right now. |
@BrettHoover-NOAA FYI, when you run serially ( |
Note the incoming PR #602 will change this, as the OUTPUT_FILETYPES is being split into two variables until being combined when writing the namelist. That PR also forces serial write for the EnKF on Hera because of this type of issue. I didn't encounter issues with non-ensemble data. Or, at least, none that I noticed. |
@BrettHoover-NOAA Is this still a problem when running develop, or can we close this issue? |
Hi @WalterKolczynski-NOAA, I think it's safe to close this issue, thank you! |
Description
gdasfcst task cannot complete, with the log-file citing an HDF error after a series of "ABNORMAL 2MT" warnings during a canopy conductance step.
Requirements
I am using a v16x global workflow (fca3433) modified with updated obsproc packages in the config.base file:
experiment setup:
setup_expt.py --pslot v16x_sept_g17 --configdir /scratch1/NCEPDEV/da/Brett.Hoover/mit_g16_g17/global-workflow/develop.20201222.AMVQ/parm/config --idate 2020082200 --edate 2020110100 --comrot /scratch1/NCEPDEV/stmp2/Brett.Hoover/ROTDIRS/ --expdir /scratch1/NCEPDEV/da/Brett.Hoover/para --resdet 384 --resens 192 --nens 80 --gfs_cyc 1
workflow setup:
setup_workflow.py --expdir /scratch1/NCEPDEV/da/Brett.Hoover/para/v16x_sept_g17
Using cold-start C384/C192 ICs that were provided to me. The bug appears on the gfsfcst task initialized on 202008230000.
Acceptance Criteria (Definition of Done)
Successful completion of gdasfcst task, continuation of gdas cycling
@KateFriedman-NOAA, let me know if you have any suggestions
The text was updated successfully, but these errors were encountered: