Opened 16 years ago
Closed 15 years ago
#166 closed enhancement (fixed)
Valid observation range cutoff in 1dVar
| Reported by: | Huw Lewis | Owned by: | Huw Lewis |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.0 |
| Component: | ropp_1dvar | Version: | 2.0 |
| Keywords: | Cc: |
Description
Investigate options and sensitivity of results to defining cutoff heights for usable data in 1dVar (e.g. only consider observations valid between 10 and 30 km).
Cutoff limits could be defined as configuration options. What impact does this have on 1dVar results?
Note:
See TracTickets
for help on using tickets.
New configuration parameters config%max_1dvar_height and config%min_1dvar_height have been added to the set of user-definable parameters. These specify the height range within which data should be used for the 1dVar analysis. Outside this height range, the data weighting is set to zero (not contributing to the cost function). The weights adjustment is performed in the new routine ropp_1dvar/qc/ropp_1dvar_cutoff().
The updated code has been committed to trunk code (revisions [2379], [2380]) and suc-cessfully tested by re-running test folder IT-1DVAR-OP.
The User Guide document (Part II) has been updated to provide details of the new con-figuration options, and an explanation is included in the Change Log html document pro-vided to users as part of the release.
Ticket closed as fixed.