Changes between Version 36 and Version 37 of ImplementationofAnalysisStep


Ignore:
Timestamp:
May 24, 2025, 3:22:42 PM (8 days ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ImplementationofAnalysisStep

    v36 v37  
    11= Implementing the analysis step =
     2
     3[[PageOutline(2-3,Contents of this page)]]
    24
    35{{{
     
    4951}}}
    5052
    51 The implementation of the analysis step requires that the user-supplied routines whose names are given in the call to the filter-specific put-state routine are implemented with full functionality.
     53The implementation of the analysis step requires that the user-supplied routines that are arguments in the call to the routine for the analysis step are implemented with full functionality.
    5254
    53 With PDAF-OMI many of the routines are general and hence usable for all filter algorithms. There are some differences between the local and global filters and the LEnKF.  The general routines will be repeated, but they are marked as general.
     55While different routines are used for the online and offline modes of PDAF, the implementation of the analysis is generally generic. As such we combine this here for both the online and offline modes.
    5456
    5557
     58== Ensemble filter methods ==
    5659
    57 There is a universal routine that calls the filter analysis step for all filter methods.
    58  * [ImplementFilterAnalysisOverview General overview] of routines required to implement the analysis step for ensemble filters.
    59  1. [ImplementAnalysisUniversal Implementation of the analysis]
     60To get an overview of the required routines for the analysis step see:
     61 * [ImplementFilterAnalysisOverview General overview of routines required to implement the analysis step for ensemble filters].
     62
     63
     64There are universal routines that call the filter analysis step for all ensemble filter methods.
     65 * [ImplementAnalysisUniversal Implementation of the analysis using the universal routines.]
     66
     67For more specific cases, there are further routines
     68 * [wiki:ImplementAnalysisUniversalLocal Implementation with user-provided routines for transfer between global and local state vectors (g2l_state_pdaf/l2g_state_pdaf) in local filters]
     69 * [wiki:ImplementanalysisGlobalPDAF3 Implemenation exclusively for global filters and LEnKF]
    6070
    6171
     
    6474 1. [ImplementAnalysislenkfOmi Implementation of the analysis for the LEnKF using covariance localization]
    6575
    66 For the application of the 3D-Var methods there are separate routines (added with PDAF 2.0):
    67  * [wiki:Implement3DVarAnalysisOverview General overview] of routines required to implement the analysis step for 3D-Var.
     76
     77== 3D-Var methods ==
     78
     79To get an overview of the required routines for the analysis step of 3D-Var methods see:
     80 * [wiki:Implement3DVarAnalysisOverview General overview of routines required to implement the analysis step for 3D-Var].
     81
     82For the application of the 3D-Var methods there are universal routines for all methods:
     83 * [wiki:Implement3DVarAnalysisUniversal Implementation of the analysis using the universal routines.]
     84
     85For more specific cases, there are further routines
     86
    6887 1. [wiki:ImplementAnalysis_3DVar Implementation of the analysis for 3D-Var with parameterized background covariance matrix]
    6988 1. [wiki:ImplementAnalysis_3DEnVar Implementation of the analysis for 3D Ensemble Var ]
     
    7190
    7291
    73 == Implementation of the analysis step without OMI ==
     92== Implementation Variants before PDAF3 ==
    7493
    75 PDAF-OMI was introduced with version 1.16 of PDAF. While we recommend using OMI, the [wiki:OfflineImplementationofAnalysisStep_noOMI implementation of the analysis step without OMI] is still possible.
     94=== Implementation of the analysis step using PDAF-OMI without PDAFlocal ===
    7695
     96Before 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. 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.
     97
     98|| For reference we provide the documentation on the  **[wiki:ImplementAnalysisLocal_untilPDAF221 implementation of the analysis step with PDAF-OMI not using PDAFlocal].** ||
     99
     100=== Implementation of the analysis step using PDAF's full interface ===
     101
     102The 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.
     103
     104|| For reference we provide the documentation on the  **[wiki:OfflineImplementationofAnalysisStep_noOMI implementation of the analysis step without OMI]**, which is still possible. ||
    77105
    78106== Testing the full implementation ==