-
Notifications
You must be signed in to change notification settings - Fork 168
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
JCB-based obs+bias staging, Jedi class updates, and marine B-matrix refactoring #2992
base: develop
Are you sure you want to change the base?
JCB-based obs+bias staging, Jedi class updates, and marine B-matrix refactoring #2992
Conversation
…e bias correction files from tarball (NOAA-EMC#2862)
…on files using jedi class (NOAA-EMC#2862)
…ns analysis scripts (NOAA-EMC#2862)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks ok to me.
Experiment C96C48_ufs_hybatmDA FAILED on Hera in Build# 1 with error logs:
Follow link here to view the contents of the above file(s): (link) |
Experiment C96C48_ufs_hybatmDA FAILED on Hera in Build# 1 in |
Experiment C96C48_hybatmaerosnowDA FAILED on Hera in Build# 1 with error logs:
Follow link here to view the contents of the above file(s): (link) |
Experiment C96C48_hybatmaerosnowDA FAILED on Hera in Build# 1 in |
CI Failed on Hera in Build# 1
|
@WalterKolczynski-NOAA The issue with the CI failures is the update of the GDASApp hash, since the old hash points to some patches for its submodules. We should hold off on CI until #1362 is resolved. @RussTreadon-NOAA is using this branch as his baseline and is making rapid progress. Sorry, I should have let you known ealier. |
@DavidNew-NOAA , any reason why we need to have the new variable name as part of this pr? If not I'd suggest to revert to a working gdas.cd # so we can move the other pr's through the pipeline. |
@guillaumevernieres This PR depends on a more recent GDASApp hash due to GDASApp PR #1312 (merged), but I think we could throw together a quick GDASApp PR that would at least fix these CI failures. The The failure in The failure in |
Ha ... yes ... Thanks for the reminders. I also just remembered that @RussTreadon-NOAA had to cook a saber/vader # in a fork ... Never mind my comment above! |
Description
This PR is a companion to GDASApp PR #1312 (merged) and JCB-GDAS PR #31 (merged).
This PR does three things:
Jedi
constructor now takes as input a dictionary that is essentially subset of thetask_config
dictionary. This makes the code clearer and less opaque and makes debugging easier. Each dictionary is constructed from a YAML file with configuration parameters for each JEDI application that is run.AtmAnalysis
andAtmEnsAnalysis
. Before, in theatmensanl*
jobs for example, the LETKF solver was initialized in theatmensanlinit
cjob, but the LETKF solver and FV3 increment converter were both initialized and executed in theatmensanlobs
andatmensanlfv3inc
jobs respectively. This makes more sense in terms of resource allocation.Addendum:
I'm now rolling in the refactoring of the marine B-matrix task into this PR. That makes it also a companion of GDASApp PR #1346 and JCB-GDAS PR #36.
These new changes introduce the
Jedi
class and JCB into the marine B-matrix job.Partially resolves GDASApp issue #1296
Type of change
Change characteristics
How has this been tested?
C96C48_ufs_hybatmDA CI runs successfully
GDASApp jjob tests pass successfully
Checklist