Changes between Version 2 and Version 3 of Implement3DVarAnalysisPDAF3_3DEnVar

Timestamp:

May 26, 2025, 5:45:57 PM (6 days ago)

Author:

lnerger

Comment:

--

Implement3DVarAnalysisPDAF3_3DEnVar

@@ -55 +55 @@
 This routine can be used to run both variants of the 3D ensemble Var, i.e., using the local LESTKF or the global ESTKF for the transformation of the ensemble perturbations.
 
-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:
@@ -84 +84 @@
 === `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. 
 
@@ -100 +100 @@
 
 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.
-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. 
+When the 'flexible' implementation variant is chosen for the assimilation system, the routine. This routine allows to port such implemnetations to the PDAF3 interface with minimal changes.
+The interface of the routine is identical with that of `PDAF3_assimilate_en3dvar`, 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:
@@ -120 +120 @@
 This routine is particular for the ESTKF. One can use it if one exclusively uses the global filter. In the argument list of this routine, the call-back routine for localization are not present and hence the argument list is shorter than that of `PDAF3_assimilate_en3dvar`.
  
-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:
@@ -134 +134 @@
 
 
-=== `PDAF3_assim_offline_hyb3dvar_estkf` ===
+=== `PDAF3_assim_offline_en3dvar_estkf` ===
 
 This routine is particular for the ESTKF. One can use it if one exclusively uses the global filter. In the argument list of this routine, the call-back routine for localization are not present and hence the argument list is shorter than that of `PDAF3_assim_offline_en3dvar`.
@@ -163 +163 @@
 The interface is:
 {{{
-SUBROUTINE PDAF3_assimilate_hyb3dvar_estkf(collect_state_pdaf, &
+SUBROUTINE PDAF3_assimilate_en3dvar_estkf(collect_state_pdaf, &
                                  init_dim_obs_pdafomi, obs_op_pdafomi, &
                                  cvt_ens_pdaf, cvt_adj_ens_pdaf,  &