Skip to content

Need to revise commercial RO assigned error level #148

@rtodling

Description

@rtodling

This is put the discussion on a possible revision of the weighting factor used for commercial RO into a single place.

I will start by presenting how the thinking for the factor used in GSI for handling SPIRE first come about.

The first actual x-experiments to incorporate commercial RO was x0045a (x45 was deemed invalid). Evaluation of DFS for that experiment indicated to me (RTodling) that things were off in comparison to how we typically draw to COSMIC-2. The figure below shows DFS (by obs count) in this case (data for 2020/12/15 to 2021/01/14).

Recall that a problem w/ 45a was that SPIRE was available from the latter half of Dec to mid Jan - the fig (replotted) now includes the period when SPIRE is fully available as well as C2.

x45a_com_ro_dfs_tro

After some offline testing, the next run introduced a weighting factor to make the assimilation of SPIRE and COSMIC-2 more like each other (with more even weighting of data between the two instruments). The results of setting the weighting factor to two is shown below for x0046c (data for 2021/12).

x46c_com_ro_dfs_tro

Notice:

  1. The figures about include data only in the Tropics (20S,20N) to make a fair comparison.
  2. The version of SPIRE used in these cases was the so-called NASA version (high-resolution and density - nearly full observing system)
  3. This "NASA-version" is apparently known to be a smoothed our version of the data - which some say not to be a full quality because of the smoothing.
  4. The "NASA-version" is not suitable for real-time applications - it's made available in delayed mode - but it is suitable for reanalysis.

Given (4) above, when SPIRE was set to run in an FPP experiment, the input dataset that would be plausible for a real time application was a set coming from NOAA (NCEP). Unlike the NASA-version, this NOAA set had no smoothing applied to it and it was densely distributed more like COSMIC-2 than the NASA-set.

More recently (2023/07), in GEOS-FP, the NOAA-version of SPIRE has suffered yet another thinning of sorts and DFS results (2023/08) for SPIRE continue to show (as in FPP) difference for how COSMIC-2 is used. Perhaps the FPP and FP results are indication that we could consider retuning of the error assignment for SPIRE.

f5295_fp_com_ro_dfs_tro

Caveat

True DFS (calculated directly from the DA operators) much be a positive quantity. When calculated on the basis of residuals - which the results above are - there is no guarantee that DFS is actually positive. Negative values of DFS are typically interpreted as something not being quite adequately tuned (like obs-errors; or trouble quality control).

The way I look at residual-based DFS is that it is a diagnostic to check the relative contribution of the data to the analysis.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions