Changes between Version 11 and Version 12 of OMI_debugging


Ignore:
Timestamp:
Mar 14, 2023, 5:25:37 PM (13 months ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OMI_debugging

    v11 v12  
    4747   INTEGER :: dbg_id  ! Debugging flag: >0 for debug output; =0 for no debug output
    4848
    49    CALLOMI PDAFomi_set debug_flag(dbg_id)
     49   CALLOMI PDAFomi_set_debug_flag(dbg_id)
    5050}}}
    5151In particular this call can be inserted in any routines contained in `callback_obs_pdafomi.F90`. Setting the single argument of `PDAFomi_set_debug_flag` to a value larger 0 will active the output, while =0 will deactivate it. For the debugging it is useful to keep the number of observations low since for a large number of observations, the output will be very lengthy. This can particularly be the case when using the debugging output in `init_dim_obs_pdafomi` or `obs_op_pdafomi`. To this end, it can be useful to intentionally reduce the number of observations for the debugging. For the localized filters (LESTKF, LETKF, LNETF, LSEIK) it is recommended to only activate the debugging for a single local analysis domain as shown below. The particular domain index can be chosen e.g. based on the coordinates of the domain, which are usually determined in `init_dim_l_pdaf`.