Changes between Version 5 and Version 6 of OMI_observation_modules


Ignore:
Timestamp:
Nov 23, 2020, 11:27:09 AM (3 months ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OMI_observation_modules

    v5 v6  
    22
    33[[PageOutline(2-3,Contents of this page)]]
     4
     5== Overview ==
    46
    57The implementation of the observations with OMI is done in observation modules (obs-modules). For each observation type a separate module should be created.
     
    1618In the obs-module the subroutines are named according to the observation type. The template file uses generic names which can be replaced by the user. Having distinct names for each observation type is relevant to include the subroutine from the module in the call-back routine with ‘use’. In the header of each obs-module, the user can declare further variables, e.g. assim_TYPE as a flag to control whether the observation type should be assimilated.
    1719
    18 == obs_f data type ==
     20== Data type obs_f ==
    1921
    2022To ensure the functionality within each obs-module, we rely on a derived data type called `obs_f` that contains all information about the observation. One instance of this data type is allocated in each obs-module with the generic variable name `thisobs`. A few of the elements of `obs_f` are initialized by the user when the observation information is initialized on `init_dim_obs_f`. Further variables is set in a call to the routine `PDAFomi_gather_obs`. This information is then used by all other routines in the obs-module. The template file obs_TYPE_pdafomi_TEMPLATE.F90 shows the different steps needed to initialize thisobs.