Changes between Version 7 and Version 8 of PDAFlocal_overview


Ignore:
Timestamp:
Jun 10, 2025, 2:37:13 PM (7 days ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PDAFlocal_overview

    v7 v8  
    77
    88PDAFlocal is optional functionality and was introduced with PDAF V2.3.
     9It is now standard in the interface for PDAF3.
    910
    1011PDAFlocal provides an improved handling of the localization of state vectors as used in the loca filters LESTKF, LETKF, LNETF, LSEIK, and LKNETF. A leading motivation to implement PDAFlocal was that it leads to much better performance when the Python interface pyPDAF is used. However, it is also useful for native implementations in e.g. Fortran because it also provides additional functionality for e.g. vertical localization or weakly coupled assimilation.
    … …  
    7374 * After calling this routine, the local increment weights are one until one calls `PDAFlocal_set_increment_weights` with prescribed weights again.
    7475
     76== Routines to perform the analysis step with PDAF3  ==
     77
     78The PDAF3 interface introduced with PDAF V3.0 uses PDAFlocal by default. This is the recommended implementation approach for PDAF3. See the [wiki:ImplementationofAnalysisStep_PDAF3 Page on the implementing the analysis step for PDAF2] for the current implementation recommendations, and [wiki:PDAF3_interface Page on the PDAF3 interface] for an overview of the assimilation routines of the PDAF3 interface.
     79
     80
    7581== Routines to perform the analysis step with OMI ==
     82
     83|| Below, we describe the routines for PDAF2. We recommend to use the PDAF3 interface routines, that were introduced with PDAF V3.0. See the [wiki:ImplementationofAnalysisStep_PDAF3 Page on the implementing the analysis step for PDAF2] for the current implementation recommendations. ||
    7684
    7785Generally the routines to be called for the analysis step are analogous to those when not used PDAFlocal (e.g. in implementations before the release of PDAF V2.3). The difference is in the name and in the fact that the routines `g2l_state_pdaf` and `l2g_state_pdaf` are not present in the interface of the PDAFlocal routines.