Changes between Version 12 and Version 13 of PDAF_OMI_Overview

Timestamp:

Nov 22, 2020, 9:52:06 AM (4 years ago)

Author:

lnerger

Comment:

--

PDAF_OMI_Overview

@@ -21 +21 @@
 PDAF-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.
 
-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:
+Compared 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:
  - init_dim_obs
  - obs_op
  - init_dim_obs_l (only for domain-localized filters like LETKF and LESTKF)
  - localize_covar (only needed for the localized EnKF)
-All other routines base on variables that are initialized by these routines and are provided by PDAF-OMI.
+Here, 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.
+Other functionality needed during the analyis step bases on variables that are initialized by these routines and is provided by PDAF-OMI.
 
 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 implementations by others.