Changes between Version 42 and Version 43 of ImplementationofAnalysisStep
- Timestamp:
- May 25, 2025, 1:31:26 PM (7 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ImplementationofAnalysisStep
v42 v43 99 99 == Implementation variants before PDAF3 == 100 100 101 === Implement ation ofthe analysis step using PDAF-OMI without PDAFlocal ===101 === Implementing the analysis step using PDAF-OMI without PDAFlocal === 102 102 103 103 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`. … … 105 105 || For reference we provide the documentation on the **[wiki:ImplementAnalysisLocal_untilPDAF221 implementation of the analysis step with PDAF-OMI not using PDAFlocal].** || 106 106 107 === Implement ation ofthe analysis step using PDAF's full interface ===107 === Implementing the analysis step using PDAF's full interface === 108 108 109 109 The 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.