Changes between Version 25 and Version 26 of PDAF_OMI_Overview


Ignore:
Timestamp:
Nov 27, 2020, 11:57:52 AM (3 years ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PDAF_OMI_Overview

    v25 v26  
    2626PDAF-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.
    2727
    28 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:
     28Compared to the classical variant to implement observations with PDAF, OMI is designed with two main aims
     29 1. reduce the coding effort for implementing the support for an observation type, its corresponding observation operator, and localization.
     30 2. simplify the implementation of complex cases in which several different observation types are assimilated by clearly separating each observation type
     31
     32With OMI one implements one Fortran 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.
     33
     34To reduce the coding effort only four routines need to be implemented for an observation type:
    2935 - '''init_dim_obs'''[[br]]
    3036  Reads observations from a file and initialize the information describing the observations
     
    3844All functionality needed during the analyis step bases on variables that are initialized by these routines and is provided by PDAF-OMI.
    3945
    40 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.
     46
    4147
    4248