Changes between Version 9 and Version 10 of PDAF_OMI_Overview


Ignore:
Timestamp:
Nov 18, 2020, 1:08:13 PM (7 days ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PDAF_OMI_Overview

    v9 v10  
    2121PDAF-OMI (Observation Module Infrastructure) is an extension to PDAF for a structured modular implementation of the call-back routines handling observations for PDAF. It was introduced with PDAF V1.16.
    2222
    23 OMI is designed to reduce the coding effort for implementing the support for an observation type, its corresponding observation operator, and localization. In particular, only the three routines
     23OMI is designed to reduce the coding effort for implementing the support for an observation type, its corresponding observation operator, and localization. In particular, only four routines need to be implemented for an observation type:
    2424 - init_dim_obs
    2525 - obs_op
    26  - init_dim_obs_l (for domain-localized filters like LETKF and LESTKF)
    27 need to be implemented for an observation type. All other routines base on variables that are initialized by these routines and are provided by PDAF-OMI.
     26 - init_dim_obs_l (only for domain-localized filters like LETKF and LESTKF)
     27 - localize_covar (only needed for the localized EnKF)
     28All other routines base on variables that are initialized by these routines and are provided by PDAF-OMI.
    2829
    29 With OMI one implements one module for each observation type (like sea surface temperature data from some satellite sensor, or altimetry data). This guarantees that each observation type is handled indenpendently from the others. Thus different developers can implement observation types without interfering with the implemnetations by others.
     30With OMI one implements one module for each observation type (like sea surface temperature data from some satellite sensor, or altimetry data). This guarantees that each observation type is handled indenpendently from the others. Thus different developers can implement observation types without interfering with the implementations by others.
    3031
    3132