-
Notifications
You must be signed in to change notification settings - Fork 34
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
Refactor ATM mode to work with python-based g-w structure #357
Comments
g-w specific work for this issue is documented in g-w issue #1313. |
Work for this issue will be done in |
I encountered a problem with
The above is related to the following line found twice in
If
I replaced
May we safely revert |
… with geopoential height in sondes.yaml (NOAA-EMC#357)
@CoryMartin-NOAA , g-w PR #1354 has been opened with the refactored UFS DA ATM var and ens components. The UFS DA ATM var and ens jobs work from g-w. I am now updating the GDASApp ctests. Eventually we can add a bufr-to-ioda step to convert the GDA amsua to a format |
sorry @RussTreadon-NOAA for missing the geopotential/geometric comment. I think it's safe for now and we can revisit later. Ideally FV3-JEDI should handle either and compute which it needs from the other. The approach I was taking for the prototype aerosol cycling was to, as you suggested, create a GDA directory that has already converted IODA format files. Presumably this would most closely mimic a future implementation because either the 'obsproc' side would be handling the conversion, or we would read BUFR as-is into IODA. |
Status Update The g-w work for this issue was completed in Instead of merging g-w PR #1354 into g-w
One challenge in doing this was that some of the files modified in PR #1354 contain changes for more than one UFS-DA component. An attempt was made to untangle these changes along with other component specific changes into the following forked branches:
The above three branches correspond to g-w PRs #1370 , #1372, and #1373, respectively. GDASApp ctests run from g-w PR #1354 found that 6 tests fail
This is expected given the changes in g-w #1354. These GDASApp tests will be in various states of |
While the following g-w PRs remain open
a g-w parallel The
have been replaced by
The ctests were updated to run with the changes in the g-w PRs. The atm var and ens ctests now run to completion. The changes required for this to happen were committed to |
Changes to GDASAPP_TESTDATA To get the atm var and ens ctests to work with the pending g-w PRs, it is necessary to modify the
The restructured @CoryMartin-NOAA , we will need to update |
@RussTreadon-NOAA are you ready for me to do that now or should I wait until this PR is approved by others? |
@CoryMartin-NOAA , I would like to move forward but I don't think we can. If we change Let me open a GDASApp PR for this issue and note it's dependency on the three g-w PRs. We can update |
* add sondes to test_gdasapp_atm_jjob_var_run, replace geometric height with geopoential height in sondes.yaml (#357) * update atm_jjob var and ens ctests to work with python UFS-DA ATM g-w (#357) * correct yaml syntax error in config.yaml (#357) * correct name of ens final j-job on Orion (#357) * lgetkf updates: specify analysis variables, turn off posterior observer (#357) * update yamls used in UFS-DA ATM prototype cycling to be consistent with g-w python (#357) * remove RESTART from bkg path * Update UFS DA ATM yaml and scripts to use g-w pygw (#357) * remove 10-digit datetime string from radiance bias correction filenames (#357) * replace JEDIVAREXE with JEDIEXE in config.atmanl (#357) * remove extraneous yaml import (#357) * add g-w pygw to PYTHONPATH in run_jedi_exe scripts (#357) * move atm run_jedi_exe ctests into global-workflow (#357)
Addition of the GDASApp Aerosol mode to the global-workflow was done using a python based approach (see g-w PR #1106). This issue is opened to refactor the GDASApp ATM mode to use the same python-based g-w approach.
The text was updated successfully, but these errors were encountered: