Changes between Version 4 and Version 5 of OMI_Callback_obs_pdafomi


Ignore:
Timestamp:
Nov 17, 2020, 1:46:08 PM (8 days ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OMI_Callback_obs_pdafomi

    v4 v5  
    2727== obs_op_pdafomi ==
    2828
    29  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.
     29In this routine one just calls `obs_op_TYPE` for each observation type.
    3030
    3131The implementation steps are:
    32321. Include the observation-specific routine `obs_op_TYPE` from the observation-module with 'use'
    33 1. Ensure that the integer variable `offset_obs` is declared and initialized to 0
    34331. Add a call to the observation-specific routine obs_op_TYPE
    3534
    3635Notes:
    37  - 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.
     36 - 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.
    3837
    3938
    4039== init_dim_obs_l_pdafomi ==
    4140
    42   In this routine two offset variables `offset_obs_f` and `offset_obs_l` are used to ensure a consistent order of the calls.
     41In this routine one just calls `init_dim_obs_l_TYPE` for each observation type.
    4342
    4443The implementation steps are: