Changes between Version 23 and Version 24 of PDAF_OMI_Overview_PDAF3


Ignore:
Timestamp:
May 31, 2026, 9:36:48 AM (5 hours ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PDAF_OMI_Overview_PDAF3

    v23 v24  
    4848
    4949[[Image(//pics/PDAFstructure_PDAF-OMI_PDAF3.png)]]
    50 [[BR]]'''Figure 1:''' Call-structure of PDAF with PDAF-OMI: (green) PDAF library with core and omi; (blue) call-back routines; (red) OMI call-back routines; (purple) observation-specific modules. The cyan color marks call-back functions for localization. If [wiki:PDAFlocal_overview PDAFlocal] is not used, there will be two additional routines `g2l_state` and `l2g_state` relating to localization.
     50[[BR]]'''Figure 1:''' Call-structure of PDAF with PDAF-OMI: (green) PDAF library with core and omi; (red) PDAF-OMI call-back routines; (purple) observation modules with one module per observation type. (cyan) marks call-back routines for localization. In implementations before PDAF3, [wiki:PDAFlocal_overview PDAFlocal] might not be used. In this case there will be two additional routines `g2l_state` and `l2g_state` relating to localization.
    5151
    5252With OMI, the functionality to handle observations is included in generic routines in `callback_obs_pdafomi.F90` and observation-specific modules (purple `obs_OBSTYPE_pdafomi` in the third column in Fig. 1, denoted obs-module below). Based on the information initialized in the call-back routines, PDAF will perform further observation handling internally. There is one obs-module per observation type with contains these routines. For example, one can have one obs-module for the satellite sea surface temperature from one data provider and another one for sea level anomaly data. Important is that each of these obs-modules, which are further described below, is independent from the others. This allows us to switch between different combinations of observations ensuring that their implementations don’t interfere.