Changes between Version 3 and Version 4 of ImplementAnalysisPDAF3UniversalLocal

Timestamp:

May 24, 2025, 6:19:12 PM (8 days ago)

Author:

lnerger

Comment:

--

ImplementAnalysisPDAF3UniversalLocal

@@ -52 +52 @@
 Here, we list the full interface of the routine. Subsequently, the user-supplied routines specified in the call are explained. 
 
-The interface when using one of the local filters is the following:
-{{{
-  SUBROUTINE PDAF3_assimilate(collect_state_pdaf, distribute_state_pdaf, &
+The universal interface is the following:
+{{{
+  SUBROUTINE PDAF3_assimilate_local(collect_state_pdaf, distribute_state_pdaf, &
                 init_dim_obs_pdafomi, obs_op_pdafomi, &
                 init_n_domains_pdaf, init_dim_l_pdaf, init_dim_obs_l_pdafomi, &
@@ -122 +122 @@
 In the subroutine interfaces some variables appear with the suffix `_p` (short for 'process'). This suffix indicates that the variable is particular to a model sub-domain, if a domain decomposed model is used. In addition, there will be variables with suffix `_l` (indicating 'local').
 
+Call-back routines that end on `_pdaf` are regular call-back routines from the core part of PDAF, while call-back routines that end on `_pdafomi` handle observations within PDAF-OMI.
+
+
 
 === `collect_state_pdaf` (collect_state_pdaf.F90) ===