Changes between Version 46 and Version 47 of ImplementationofAnalysisStep


Ignore:
Timestamp:
May 25, 2025, 6:01:20 PM (7 days ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ImplementationofAnalysisStep

    v46 v47  
    8787=== Implementing the analysis step using PDAF-OMI without PDAFlocal ===
    8888
     89This variant refers to the `PDAFomi_` routines to call the analysis step.
     90
    8991Before releasing PDAF V3.0 with its now PDAF3-interface routines for the analysis step, using the PDAF Observation Module Interface (PDAF-OMI) was recommended. PDAFlocal was introduced with PDAF V2.3 in September 2024 as an add-on to PDAF-OMI for local filters. With PDAFlocal we simplified the localization of the state vector. Implementations done before the release of PDAF V2.3 likely use PDAF-OMI without PDAFlocal. This mean they call user-provided routines `g2l_state_pdaf` and `l2g_state_pdaf`.
    9092
    … …  
    9294
    9395=== Implementing the analysis step using PDAF-OMI and PDAFlocal ===
     96
     97This variant refers to the `PDAFlocalomi_` routines to call the analysis step.
    9498
    9599PDAFlocal was introduced with PDAF V2.3 in September 2024 as an add-on to PDAF-OMI for local filters. With PDAFlocal we simplified the implementation of localization of the state vector.
    … …  
    100104
    101105=== Implementing the analysis step using PDAF's full interface ===
     106
     107This variant refers to the `PDAF_` routines to call the analysis step.
    102108
    103109The full interface omits the use of PDAF-OMI for the observation handling, and PDAFlocal for the simplified handling of localization. Using the full interface is an 'expert mode' because it requires to implement a larger number of call-back routines. Nonetheless, assimilation systems implemented before the introduction of PDAF-OMI with Version 1.16 in November 2020 might still use this approach.