Changes between Version 5 and Version 6 of Implement3DVarAnalysisPDAF3_3DEnVar

Timestamp:

May 27, 2025, 2:06:28 PM (5 days ago)

Author:

lnerger

Comment:

--

Implement3DVarAnalysisPDAF3_3DEnVar

@@ -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. This routine allows to port such implementations to the PDAF3 interface with minimal changes.
+When the ''flexible'' implementation variant is chosen for the assimilation system, this routine allows to port such implementations 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 `distribute_state_pdaf` and `next_observation_pdaf` are missing. 
 
@@ -156 +156 @@
 
 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_en3dvar_estkf` 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 `PDAF3_put_state_en3dvar_estkf` 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_estkf`, except that the user-supplied routines `U_distribute_state` and `U_next_observation` are missing. 
 
@@ -272 +272 @@
 === `init_n_domains_pdaf` (init_n_domains_pdaf.F90) ===
 
-This routine is only used for localization. It is called during the analysis step before the loop over the local analysis domains is entered. It has to provide the number of local analysis domains. In case of a domain-decomposed model, the number of local analysis domain for the model sub-domain of the calling process has to be initialized.
+This routine is used in the LESTKF.
+
+The routine is called during the analysis step of the LESTKF before the loop over the local analysis domains is entered. It has to provide the number of local analysis domains. In case of a domain-decomposed model, the number of local analysis domain for the model sub-domain of the calling process has to be initialized.
 
 The interface for this routine is:
@@ -287 +289 @@
 
 === `init_dim_l_pdaf` (init_dim_l_pdaf.F90) ===
+
+This routine is used in the LESTKF.
 
 This routine is only used for localization. 
@@ -333 +337 @@
 === `init_dim_obs_l_pdafomi` (callback_obs_pdafomi.F90) ===
 
-This routine is only used for localization. It is a call-back routine for PDAF-OMI that initializes the local observation vector. The routine calls a routine from the observation module for each observation type.
+This routine is used in the LESTKF.
+
+It is a call-back routine for PDAF-OMI that initializes the local observation vector. The routine calls a routine from the observation module for each observation type.
 
 See the [wiki:OMI_Callback_obs_pdafomi documentation on callback_obs_pdafomi.F90] for more information.