Changes between Version 2 and Version 3 of ImplementAnalysisPDAF3UniversalLocal

Timestamp:

May 24, 2025, 6:13:59 PM (8 days ago)

Author:

lnerger

Comment:

--

ImplementAnalysisPDAF3UniversalLocal

@@ -277 +277 @@
 == Execution order of user-supplied routines ==
 
-The user-supplied routines are executed in the order listed below. The order can be important as some routines can perform preparatory work for routines executed later on during the analysis. For example, in `U_init_dim_l` we can prepare the index array that provides the information how to localize a global state vector. 
-
-Before the analysis step is called the following is executed:
- 1. [#U_collect_statecollect_state_pdaf.F90 U_collect_state] (called once for each ensemble member)
- 1. [#U_prepoststepprepoststep_ens_pdaf.F90 U_prepoststep] (Call to act on the forecast ensemble, called with negative value of the time step)
+The user-supplied routines are executed in the order listed below. The order can be important as some routines can perform preparatory work for routines executed later on during the analysis. For example, in `init_dim_l_pdaf` we can prepare the index array that provides the information how to localize a global state vector. 
+
+Before the analysis step is called the following is executed by `PDAF3_assimilate_local` and `PDAF3_put_state_local`:
+ 1. [#collect_state_pdafcollect_state_pdaf.F90 collect_state_pdaf] (called once for each ensemble member)
+ 1. [#prepoststep_pdafprepoststep_ens_pdaf.F90 prepoststep_pdaf] (Call to act on the forecast ensemble, called with negative value of the time step)
 
 At the analysis time, the observations are initialized by the routines:
- 1. [#U_init_dim_obs_pdafomicallback_obs_pdafomi.F90 U_init_dim_obs_pdafomi]
- 1. [#U_obs_op_pdadfomicallback_obs_pdafomi.F90 U_obs_op_pdafomi] (Called `dim_ens` times; once for each ensemble member)
+ 1. [#init_dim_obs_pdafomicallback_obs_pdafomi.F90 init_dim_obs_pdafomi]
+ 1. [#obs_op_pdadfomicallback_obs_pdafomi.F90 obs_op_pdafomi] (Called `dim_ens` times; once for each ensemble member)
 
 Now the analysis step is entered and the number of local analysis domain is initialized by calling:
- 1. [#U_init_n_domainsinit_n_domains_pdaf.F90 U_init_n_domains]
+ 1. [#init_n_domains_pdafinit_n_domains_pdaf.F90 init_n_domains_pdaf]
 
 In the loop over all local analysis domains, it is executed for each local analysis domain:
- 1. [#U_init_dim_linit_dim_l_pdaf.F90 U_init_dim_l]
- 1. [#U_init_dim_obs_l_pdafomiinit_dim_obs_l_pdaf.F90 U_init_dim_obs_l_pdafomi]
+ 1. [#init_dim_l_pdafinit_dim_l_pdaf.F90 init_dim_l_pdaf]
+ 1. [#g2l_state_pdafg2lstate_pdaf.F90 g2l_state_pdaf]
+ 1. [#init_dim_obs_l_pdafomiinit_dim_obs_l_pdaf.F90 U_init_dim_obs_l_pdafomi]
+ 1. [#l2g_state_pdafl2gstate_pdaf.F90 l2g_state_pdaf]
 
 After the loop over all local analysis domains, it is executed:
- 1. [#U_prepoststepprepoststep_ens_pdaf.F90 U_prepoststep] (Call to act on the analysis ensemble, called with (positive) value of the time step)
-
-In case of the routine `PDAF3_assimilate`, the following routines are executed after the analysis step:
- 1. [#U_distribute_statedistribute_state_pdaf.F90 U_distribute_state]
- 1. [#U_next_observationnext_observation_pdaf.F90 U_next_observation]
+ 1. [#prepoststep_pdafprepoststep_ens_pdaf.F90 prepoststep_pdaf] (Call to act on the analysis ensemble, called with (positive) value of the time step)
+
+In case of the routine `PDAF3_assimilate_local`, the following routines are executed after the analysis step:
+ 1. [#distribute_state_pdafdistribute_state_pdaf.F90 distribute_state_pdaf]
+ 1. [#next_observation_pdafnext_observation_pdaf.F90 next_observation_pdaf]