Changes between Version 13 and Version 14 of ImplementAnalysisGlobal

Timestamp:

Nov 24, 2020, 10:45:15 AM (4 years ago)

Author:

lnerger

Comment:

--

ImplementAnalysisGlobal

@@ -9 +9 @@
 <li><a href="InitPdaf">Initialization of PDAF</a></li>
 <li><a href="ModifyModelforEnsembleIntegration">Modifications for ensemble integration</a></li>
-<li><a href="ImplementationofAnalysisStep">Implementation of the analysis step</a></li>
+<li><a href="OMI_ImplementationofAnalysisStep">Implementation of the analysis step with OMI</a></li>
 <ol>
 <li>Implementation for Global Filters</li>
@@ -26 +26 @@
 == Overview ==
 
-With Version 1.16 of PDAF we introduced PDAF-OMI (observation module infrastructure). With OMI we provide generic routines for the analysis step, which only distinguish global and local filters. This page describes the implementation of the analysis step for global filters (ESTKF, ETKF, EnKF, NETF, PF).
+With Version 1.16 of PDAF we introduced PDAF-OMI (Observation Module Infrastructure). With OMI we provide generic routines for the analysis step, which only distinguish global and local filters, and the LEnKF. This page describes the implementation of the analysis step for global filters (ESTKF, ETKF, EnKF, NETF, PF).
 
-For the analysis step of the global filters different operations related to the observations are needed. These operations are requested by PDAF by call-back routines supplied by the user and provided in the OMI structure. The names of the routines that are provided by the user are specified in the call to the routine `PDAFomi_assimilate_global` in the fully-parallel implementation (or `PDAFomi_put_state_global` for the 'flexible' implementation) that was discussed before. With regard to the parallelization, all these routines (except `U_collect_state`, `U_distribute_state`, and `U_next_observation`) are executed by the filter processes (`filterpe=.true.`) only.
+For the analysis step of the global filters we need different operations related to the observations. These operations are requested by PDAF by call-back routines supplied by the user and provided in the OMI structure. The names of the routines that are provided by the user are specified in the call to the routine `PDAFomi_assimilate_global` in the fully-parallel implementation (or `PDAFomi_put_state_global` for the 'flexible' implementation) that was discussed before. With regard to the parallelization, all these routines (except `U_collect_state`, `U_distribute_state`, and `U_next_observation`) are executed by the filter processes (`filterpe=.true.`) only.
 
 For completeness we discuss here all user-supplied routines that are specified in the interface to `PDAFomi_assimilate_global`. Thus, some of the user-supplied routines that are explained on the page describing the modification of the model code for the ensemble integration are repeated here.
@@ -37 +37 @@
 The general aspects of the filter specific routines `PDAF_assimilate_*` have been described on the page [ModifyModelforEnsembleIntegration Modification of the model code for the ensemble integration] and its sub-page on [InsertAnalysisStep inserting the analysis step]. The routine is used in the fully-parallel implementation variant of the data assimilation system. When the 'flexible' implementation variant is used, the routines `PDAF_put_state_*` is used as described further below. Here, we list the full interface of the routine. Subsequently, the user-supplied routines specified in the call is explained.
 
-The interface when using one of the global filters is the following:
+The interface for using the global filters is:
 {{{
   SUBROUTINE PDAFomi_assimilate_global(U_collect_state, U_distribute_state, &