-
Notifications
You must be signed in to change notification settings - Fork 31
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
Enable run_jedi_exe.py to run 3dvar #278
Conversation
Automated Global-Workflow GDASApp Testing Results:
|
Automated Global-Workflow GDASApp Testing Results:
|
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.
👍
I haven't tested the application, but I assume it's all good!
@CoryMartin-NOAA and @guillaumevernieres , I don't think one of the changes in this PR is the best way to do things. I cut-n-pasted functions I modified the Is there a way to reference the external |
@RussTreadon-NOAA the easiest thing to do is probably move those two functions into a file in |
Thank you @CoryMartin-NOAA . Let me try this. |
Automated execution of
Executing ctests from Orion command line results in 100% pass. In particular,
Not sure what's going on. |
@CoryMartin-NOAA and @guillaumevernieres , is there a way to manually run the |
@RussTreadon-NOAA this failure is because there is a dependence on IODA in that routine that @guillaumevernieres put in... Not immediately sure what the best solution here is though. And manually running it on Github actions? You can re-run on the same commit manually from the actions page. |
Automated Global-Workflow GDASApp Testing Results:
|
Automated Global-Workflow GDASApp Testing Results:
|
@RussTreadon-NOAA I didn't clearly read the comments above earlier... do I need to checkout that specific branch of global workflow to run the CI or are we going to assume that it worked as you tested it manually? I'm happy to do it I just wanted to check that this is the correct thing to do. |
We need to use the updated Once this PR, #278, is approved & merged into GDASApp |
Yeah I see it is a bit of a chicken and egg problem. The danger of having it use your forked branch is that I have to remember to change it back to develop :-). Do we think I should do that or run it manually and trust it will work? |
I really like to cross all the t's and dot all the i's, but doing so is probably overkill in this case. You, @CoryMartin-NOAA , have more important things to do than keep changing the g-w branch used by GW-RT. |
I agree, while it's important to be thorough, we are still in active development, and the danger of this breaking something seems low. We can always revert if that is not the case. |
As an aside, do we know if Do we want to maintain the 3dhofx and 4dhofx capability with |
We will need this capability for JEDI evaluation when we are ready to use FV3 cube sphere backgrounds and not GSI provided interpolated values. However, I don't know if we will want it as part of run_jedi_exe or part of the j-job approach. I'm inclined to say the former, but depending on how the EnKF is structured, perhaps we will need to run H(x) as stand alone in the workflow? |
At present Given this we should ensure |
Complete the following:
and Orion
and Orion
Given the above change this PR from draft to active. |
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.
Everything here looks good to me, thanks @RussTreadon-NOAA !
@guillaumevernieres , would you like to take another look at this PR or are you OK with your previous approval? I'd like to merge this PR into GDASApp |
All good @RussTreadon-NOAA ! Sorry for holding up the merge. |
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.
👍
Thank you @guillaumevernieres! |
…pdate (#1265) Updates the GDAS App version to incorporate the changes of NOAA-EMC/GDASApp#278, which restores the ability of `run_jedi_exe.py` to execute UFS-DA applications, specifically `fv3jedi_var.x`. Included in NOAA-EMC/GDASApp#278 is the removal of entry `ufsda.stage` from `ush/ufsda/__init__.py`. Scripts which simply `import ufsda` must now specify the functions to from `ufsda.stage`. g-w issue #1262 documents the addition of the `ufsda.stage` line to `scripts/exgdas_global_atmos_analysis_prep.py`. This change is required for g-w to successfully stage files used by the var and ensemble UFS-DA applications. Fixes #1262
ush/run_jedi_exe.py
no longer successfully executesfv3jedi_var.x
using the 3dvar yamls inush/examples/run_jedi_exe
. This functionality is restored in branchfeature/runjedi
. This PR is opened to get the required changes intodevelop