Changes between Version 4 and Version 5 of OMI_Callback_obs_pdafomi

Timestamp:

Nov 17, 2020, 1:46:08 PM (3 years ago)

Author:

lnerger

Comment:

--

OMI_Callback_obs_pdafomi

@@ -27 +27 @@
 == obs_op_pdafomi ==
 
- In this routine one has to use the offset variable `offset_obs`. It is initialized to zero and then used as an argument in each call to the observation-specific obs_op_TYPE routine. This offset defines the order in which the observations are treated in the full observation vector. 
+In this routine one just calls `obs_op_TYPE` for each observation type.
 
 The implementation steps are:
 1. Include the observation-specific routine `obs_op_TYPE` from the observation-module with 'use'
-1. Ensure that the integer variable `offset_obs` is declared and initialized to 0
 1. Add a call to the observation-specific routine obs_op_TYPE
 
 Notes:
- - The order of the calls to `obs_op_TYPE` determine how the different observations are ordered in the full observation vector containing all observation types.
+ - The order of the calls to `obs_op_TYPE` is not relevant because the setup of the overall full observation vector is defined by the order of the calls in init_dim_obs_pdafomi. Anyway, it's good practive to keep the order of the calls consistent.
 
 
 == init_dim_obs_l_pdafomi ==
 
-  In this routine two offset variables `offset_obs_f` and `offset_obs_l` are used to ensure a consistent order of the calls. 
+In this routine one just calls `init_dim_obs_l_TYPE` for each observation type. 
 
 The implementation steps are: