Changes between Version 1 and Version 2 of ImplementationofAnalysisStep_PDAF3


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

--

Legend:

Unmodified
Added
Removed
Modified

  • ImplementationofAnalysisStep_PDAF3

    v1 v2  
    8787=== Implementing the analysis step using PDAF-OMI without PDAFlocal ===
    8888
    89 Before 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-procided routines `g2l_state_pdaf` and `l2g_state_pdaf`.
     89This variant refers to the `PDAFomi_` routines to call the analysis step.
     90
     91Before 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
    9193|| For reference we provide the documentation on the  **[wiki:ImplementAnalysisLocal_untilPDAF221 implementation of the analysis step with PDAF-OMI not using PDAFlocal].** ||
    9294
     95=== Implementing the analysis step using PDAF-OMI and PDAFlocal ===
     96
     97This variant refers to the `PDAFlocalomi_` routines to call the analysis step.
     98
     99PDAFlocal 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.
     100without PDAFlocal. This mean they call user-procided routines `g2l_state_pdaf` and `l2g_state_pdaf`. Even so, the period between the introduction of PDAFlocal and the PDAF3 interface was short, there are possible implementations using PDAFlocal. The PDAF3 interface bases on both PDAF-OMI and PDAFlocal, so that it should be very easy to port a code to using the universal PDAF3 interface described above. See the [wiki:PortingToPDAF3 explanation for porting von PDAF2 to PDAF3].
     101
     102|| For reference we provide the documentation on the  **[wiki:ImplementAnalysisLocal implementation of the analysis step with PDAF-OMI and PDAFlocal].** ||
     103
     104
    93105=== Implementing the analysis step using PDAF's full interface ===
     106
     107This variant refers to the `PDAF_` routines to call the analysis step.
    94108
    95109The 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.
    96110
    97 || For reference we provide the documentation on the  **[wiki:OfflineImplementationofAnalysisStep_noOMI implementation of the analysis step without PDAF-OMI]**, which is still possible. ||
     111|| For reference we provide the documentation on the  **[wiki:ImplementationofAnalysisStep_noOMI implementation of the analysis step without PDAF-OMI]**, which is still possible. ||
     112
    98113
    99114== Testing the full implementation ==