-
Notifications
You must be signed in to change notification settings - Fork 4
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
OMPS/OMI Validation #57
Comments
omi_aura test YAML added to parm/atm/obs/testing in GDASApp to reproduce the GSI HofX, QC and final obs error. |
Sent pull request (PR438) |
Re-evaluation for OMI AURA(No data thinning for input data)
The last plot does not look right. Some observations have QC difference = 14, meaning GsiEffectiveQC= 0, but JEDI EffectiveQC =14. |
The GDASApp test results based on the updated GSI obs file for OMI AURA
Here is how to interpret the plot: QC diff = 13 --- GsiEffectiveQC = 1, and JEDI EffectiveQC = 14 (RejectList)--- observation are screened from both GSI and UFO QC diff = 0 --- GsiEffectiveQC (GSI) and EffectiveQC (JEDI)) are zeros The plot tells us that the QC results between GSI and JEDI are identical. |
@ADCollard @azadeh-gh Please check the last three new comments. They are updated results for omi, ompstc, and ompsnp. |
Review current use of OMPS and add a test YAML to
parm/atm/obs/testing
inGDASApp
to reproduce the GSI (HofX, QC and final obs error)The text was updated successfully, but these errors were encountered: