Opened 18 years ago
Closed 15 years ago
#95 closed enhancement (fixed)
1dvar information on error
| Reported by: | frae | Owned by: | Huw Lewis |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.1 |
| Component: | ropp_1dvar | Version: | 0.9 |
| Keywords: | Cc: |
Description
a test of the 1dvar module with errroneous input data just gives out some warnings on the screen. an additional retrieval flag indicating errors or warnings in the output netcdf file would be helpful, something akin to the bad flag of cosmic data.
Change history (8)
comment:1 by , 17 years ago
| Milestone: | 1.1 → 1.2 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:2 by , 16 years ago
| Milestone: | 1.2 → 3.0 |
|---|
Updated obs2roprof and state2roprof routines in v1.2 to make use of state_ok and obs_ok flags. See [1564]. This only gives 'error warnings' of quality = 0 in output file. Note output file will contain all -999s (or no data if using rangecheck) if errors occurred during processing.
Keeping ticket open (and moving to milestone 3.0) as more can be done on this and QC in general.
comment:4 by , 16 years ago
| Milestone: | → 3.0 |
|---|
comment:5 by , 16 years ago
| Priority: | minor → normal |
|---|
comment:6 by , 15 years ago
| Milestone: | 3.0 → 4.0 |
|---|
Keep ticket open (and move to milestone v4.0) to remind us that more can/should be done on using 1dVar output in QC in general. Perhaps DMI experience of using ROPP 1dVar can be incorporated in the ROPP release here.
Ticket remains open
comment:7 by , 15 years ago
| Milestone: | 4.0 → 4.1 |
|---|
Insufficient time for implementation at ROPP-4 (and not blocking action for delivery). Ticket moved (again!) to ROPP-4.1.
comment:8 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
A number of new output diagnostics have been added to the ROPP-4.1 code. See [2453].
A discussion of these output diagnostics is now provided in GSR 11 https://trac.grassaf.org/ropp/browser/ropp_doc/trunk/grassaf_report/gsr/gsr_11.pdf
In the ropp_1dvar_diagnostics.f90 code, a couple of simple quality control checks have been implemented based on n_iter > 25 and j_scaled > 5. If these are triggered, a warning message can be output to screen (in diagnostic message mode) and the diag%ok flag is set to false. If diag%ok is false, the PCD_met flag in the output file is set as 'meteorological data non-nominal'.
The ROPP-v4.1 candidate code (branch) has been tested successfully using the full test folder.
Ticket closed as fixed.
Will investigate this for v1.2.