Changes between Version 14 and Version 15 of PDAF_OMI_Overview_PDAF3

Timestamp:

Jun 3, 2025, 2:17:27 PM (3 days ago)

Author:

lnerger

Comment:

--

PDAF_OMI_Overview_PDAF3

@@ -50 +50 @@
 [[BR]]'''Figure 1:''' Call-structure of PDAF with 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.
 
-With OMI, the functionality to handle observations is included in generic routines in `callback_obs_pdafomi.F90` and observation-specific modules (purple `obs_*_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. 
+With 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. 
 
 For each observation type, one needs to implement the follwing routines in the respective obs-module. For ensemble-based filters one needs:
@@ -59 +59 @@
  - '''init_dim_obs_l''' [[br]]
   Calls a generic routine to initialize local observations (only for domain-localizated filters)
-Only in the case of '''3D-Var'''methods, two more routines are required:
+Only in the case of '''3D-Var''' methods, two more routines are required:
  - '''obs_op_lin'''[[br]]
   Calls a routine for the linearized observation operator (equal to `obs_op` if this is linear)