Add errtable comparison tool and align selected wind obs errors with GSI#571
Conversation
|
Just curious, where is use_error_inflation set? And regarding 247, should this be consistent with the superYAML used in rrfs-workflow? The errors suggest that GSI did not assimilate 247 at all. |
|
FAILED on hera started build_and_test on hera at UTC time: Mon May 11 21:09:24 UTC 2026 workdir: /scratch3/NCEPDEV/fv3-cam/rrfsbot/PRs_RDASApp/571 |
|
FAILED on wcoss2 started build_and_test on wcoss2 at UTC time: Mon May 11 21:08:17 UTC 2026 workdir: /lfs/h2/emc/da/noscrub/samuel.degelia/rrfsbot/PRs_RDASApp/571 |
The use_error_inflation is set in the jcb-configuration file. This is the jcb-config for this ctest Could you be more specific with 247 being consistent with the superYAML in [rrfs-mpas-jedi] rrfs-workflow? It is all basically the same already. Mostly organizational and jinja templating differences. But if you mean the ob errors for 247, then for these JCB templates, I am reverting them to that filler value of 1e10 used by GSI. This is simply so that GSI and JEDI are doing the same thing. Yes, this means they will have essentially zero impact. Science changes such as changes to ob errors will come later. I would think you are fine to use the errors you have set for mpas-jedi purposes. |
|
PASSED on hera started build_and_test on hera at UTC time: Tue May 12 00:20:18 UTC 2026 workdir: /scratch3/NCEPDEV/fv3-cam/rrfsbot/PRs_RDASApp/571 |
|
PASSED on wcoss2 started build_and_test on wcoss2 at UTC time: Tue May 12 00:14:37 UTC 2026 workdir: /lfs/h2/emc/da/noscrub/samuel.degelia/rrfsbot/PRs_RDASApp/571 |
Description
The main changes are:
check_j2_errtable.pyutility for comparing JEDI YAMLObsErrorModelStepwiseLinearpressure-dependent error tables againsterrtable.rrfs.use_error_inflationJinja guards around the SATWND error inflation blocks so error inflation can be toggled consistently for diagnostic experiments.0.5observation-error scaling earlier in the filter sequence, alongside the other error inflation steps, rather than applying it later after additional QC filters.[-130, 130]to[-200, 200].150-400 mbto150-300 mb.errtable.rrfs.sfcshp_winds_284.yaml.j2initial wind errors from1.079to1.5874.Motivation
While comparing JEDI conventional observation YAMLs against GSI configuration tables, several inconsistencies were identified in the pressure-dependent initial observation errors and SATWND QC setup. These differences can affect observation usage, effective errors, and count comparisons between GSI and JEDI.
The new
check_j2_errtable.pytool provides a quick way to compare the JEDI YAML error tables againsterrtable.rrfs, including the needed unit conversions for pressure levels and error values. This helps catch incorrect or stale YAML error tables during future updates.Testing
check_j2_errtable.pytool to compare JEDI YAML error tables againsterrtable.rrfs.rrfs-test/testoutput/rrfs-fv3jedi-3dvar-conv-surface.refrrfs-test/testoutput/rrfs-fv3jedi-3dvar-remote.refNotes
The errtable comparison utility accounts for known unit conventions, including pressure levels in hPa in
errtable.rrfsversus Pa in the JEDI YAMLs, as well as variable-specific error scaling for moisture and station pressure.Checklist