Changes between Version 40 and Version 41 of ImplementationGuide


Ignore:
Timestamp:
May 21, 2025, 9:57:37 AM (11 days ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ImplementationGuide

    v40 v41  
    4343
    4444The code structure is as follows from left to right
    45 * **column 1 'User code'**: The model code calls the four routines shown in this column. These are interface routines, which define variables for PDAF and then call core-subroutines of PDAF. An exception is `init_parallel_pdaf` which does not call PDAF.
     45* **column 1 'User code'**: The model code calls the four routines shown in this column. These are interface routines, which define variables for PDAF and then call core-subroutines of PDAF. An exception is `init_parallel_pdaf` which does not call PDAF. The calls to these routines are added to the model source code.
    4646* **column 2 'PDAF'**: These are the PDAF core routines which are called by the routines in column 1 to the left.
    4747* **column 3 'Call-back routines'**: This column shows the call-back routines, which are called by the PDAF routines in column 2 to the left. The routines in the purple box `callback_obs_pdafomi.F90` are the subroutines that handle observations. The 3 routines in red are used only for localized ensemble filters.
    … …  
    5757 5. **finalize_pdaf**: [AddingMemoryandTimingInformation Adding memory and timing information]
    5858
    59 The name of PDAF core routines always starts with `PDAF`. The subroutines with name ending `_pdaf` are generally user-supplied routines in the tutorial codes.
     59The names of PDAF core routines always start with `PDAF`. The subroutines with name ending `_pdaf` are generally user-supplied routines in the tutorial codes.
    6060An overview of the available options for each filter that can be specified when PDAF is initialized is given on the [wiki:AvailableOptionsforInitPDAF overview page on options].
    6161