-
Notifications
You must be signed in to change notification settings - Fork 28
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
JEDI ATM gfs and gdas prepatmiodaobs breaks with GDASapp hash 33b4cb9 #1006
Comments
As a test, make the following changes in a working copy of GDASApp
A similar check is found in other bufr2ioda converters. Rerun gfs and gdas prepatmiodaobs. Both jobs ran to completion for 20240224 00Z. The bufrfile check caught several instances of non-existent dump files.
That these dump files do not exist is not surprising. These dump files are not routinely stored in the GDA. |
My fault @RussTreadon-NOAA , I'm going to move the marine converters somewhere else. |
The gfs and gdas prepatmioda jobs fail for 20240224 00Z in g-w C96C48_ufs_hybatmDA testing.
Examination of the log files found that the job was trying to access a non-existent file
File
/work2/noaa/da/rtreadon/git/global-workflow/test/parm/gdas/ioda/bufr2ioda/bufr2ioda_insitu_profiles_argo.json
does not exist. The actual name of the file isbufr2ioda_insitu_profile_argo.json
. There is no s in profile.Script
ush/ioda/bufr2ioda/run_bufr2ioda.py
constructs observation specific filenames using the name of the bufr2ioda python script inush/ioda/bufr2ioda
. Given this, we need to ensure consistency between the names of the converter scripts inush/ioda/bufr2ioda
and json files inparm/ioda/bufr2ioda
.The text was updated successfully, but these errors were encountered: