Changes between Version 3 and Version 4 of Implement3DVarAnalysisPDAF3Universal

Timestamp:

May 26, 2025, 5:46:01 PM (6 days ago)

Author:

lnerger

Comment:

--

Implement3DVarAnalysisPDAF3Universal

@@ -55 +55 @@
 === `PDAF3_assimilate_3dvar_all` ===
 
-This routine is used both in the ''fully-parallel'' and the ''flexible'' implementation variants of the data assimilation system. (See the page [ModifyModelforEnsembleIntegration Modification of the model code for the ensemble integration] for these variants)
+This routine is used both in the ''fully-parallel'' and the ''flexible'' implementation variants of the data assimilation system. (See the page [OnlineModifyModelforEnsembleIntegration_PDAF3 Modification of the model code for the ensemble integration] for these variants)
 
 The interface is:
@@ -87 +87 @@
 === `PDAF3_assim_offline_3dvar_all` ===
 
-For the offline mode of PDAF, the routine `PDAF3_assim_offline_3dvar_all` is used to perform the analysis step.
+This routine is used to perform the analysi step for the offline mode of PDAF.
 The interface of the routine is identical with that of `PDAF3_assimilate_3dvar_all`, except that the user-supplied routines `U_distribute_state`, `U_collect_state` and `U_next_observation` are missing. 
 
-The interface when using one of the global filters is the following:
+The interface is:
 {{{
   SUBROUTINE PDAF3_assim_offline_3dvar_all(&
@@ -105 +105 @@
 
 This routine exists for backward-compatibility. In implementations that were done before the release of PDAF V3.0, a 'put_state' routine was used for the `flexible` parallelization variant and for the offline mode. 
-When the 'flexible' implementation variant is chosen for the assimilation system, the routine. The routine `PDAF3_put_state_3dvar_all` allows to port such implemnetations to the PDAF3 interface with minimal changes.
+When the 'flexible' implementation variant is chosen for the assimilation system, the routine. The routine `PDAF3_put_state_3dvar_all` allows to port such implementations to the PDAF3 interface with minimal changes.
 The interface of the routine is identical with that of `PDAF3_assimilate_3dvar_all`, except that the user-supplied routines `U_distribute_state` and `U_next_observation` are missing. 
 
-The interface when using one of the global filters is the following:
+The interface is:
 {{{
   SUBROUTINE PDAF3_put_state_3dvar_all(U_collect_state, &