Changes between Version 12 and Version 13 of PDAF_OMI_Overview


Ignore:
Timestamp:
Nov 22, 2020, 9:52:06 AM (6 months ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PDAF_OMI_Overview

    v12 v13  
    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 four routines need to be implemented for an observation type:
     23Compared to the classical variant to implement observations with PDAF, 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 four routines need to be implemented for an observation type:
    2424 - init_dim_obs
    2525 - obs_op
    2626 - init_dim_obs_l (only for domain-localized filters like LETKF and LESTKF)
    2727 - localize_covar (only needed for the localized EnKF)
    28 All other routines base on variables that are initialized by these routines and are provided by PDAF-OMI.
     28Here, the first routine reads the observation from file and initializes the information describing the observations. The latter three routines merely call a generi routine provided by PDAF-OMI.
     29Other functionality needed during the analyis step bases on variables that are initialized by these routines and is provided by PDAF-OMI.
    2930
    3031With 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.