-
Notifications
You must be signed in to change notification settings - Fork 15
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
remove no-longer-needed diagnostics.departures
and rename jedi diagnostic files as jdiag*
#241
Conversation
…stic files as jdiag*
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.
Good changes, thanks for doing this @guoqing-noaa. Also glad to see more verification that the ombg
and oman
diagnostics are working correctly now.
0ec6eef
@ShunLiu-NOAA @SamuelDegelia-NOAA @delippi I have merged the latest develop branch, resolved the conflicts, and updated the newly-added fv3jedi yaml files accordingly. |
On a sort of unrelated note, do we know if anyone is using the yamls contained in |
That is a good point @SamuelDegelia-NOAA. We need to open an issue to start cleaning out and cleaning up older yamls. |
@SamuelDegelia-NOAA The |
@guoqing-noaa It is worth keeping that directory since it contains the single obs test as you mention. Maybe it would be be better to rename |
As discussed in issue #240 , we no longer need to specify
diagnostics.departures
in YAML files and JEDI will always outputombg, oman, innov1
for two outer loop minimizationAlso, the JEDI diagnostic file contains much more information than
hofx
. It is better to rename the JEDI diagnostic files asjdiag*
, for examplejdiag_adpupa.nc4
to be consistent with the reality (the wordjdiag
has been used for a long time in the python plotting scripts).