Changes between Version 33 and Version 34 of ImplementationGuide


Ignore:
Timestamp:
Sep 20, 2024, 11:34:53 AM (2 weeks ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ImplementationGuide

    v33 v34  
    2828== The implementation of PDAF with an existing model ==
    2929
    30 For the online-mode of data assimilation, the numerical model has to be combined with PDAF into a single program to generate the assimilation system.
     30For the online-mode of data assimilation, the numerical model has to be combined with PDAF into a single program to generate the assimilation system. This is done by adding several function calls into the model code.
    3131The implementation of PDAF with an existing model can be performed in a few steps. A possible sequence is the following:
    3232
     
    3838
    3939In Steps 1 to 3, PDAF is attached to the numerical model to allow it to perform ensemble integrations. Step 4 completes the data assimilation program with the analysis step. Finally, step 5 is optional to obtain information on the computing time and required memory.
    40 The implementation steps are described on the pages linked above. An example of the implementation is given in tutorial cose provided with PDAF  in `tutorial/online_2D_serialmodel/` and `tutorial/online_2D_serialmodel/`. (The [PdafTutorial tutorial] also provides detail explanations of the implementation steps).
     40The implementation steps are described on the pages linked above. Examples of the implementation are given in tutorial code provided with PDAF in `tutorial/online_2D_serialmodel/` and `tutorial/online_2D_parallelmodel/`. (The [PdafTutorial tutorial] also provides detail explanations of the implementation steps).
    4141
    42 Several subroutines that contain model and observation specific operations are called as call-back routines by PDAF. For this, PDAF defines interfaces for all routines. These routines need to be implemented by the user. The operations in all these routines are rather elementary like the initialization of the model's physical fields from a state vector provided by PDAF and the initialization of the vector of observations. The examples mentioned above also include example implementations for these routines. In addition, the directory `templates/` contains template implementations of the routines that can be used as a basis for new implementations.
     42Several subroutines that contain specific operations for the model and observations are called as call-back routines by PDAF. For this, PDAF defines interfaces for all routines. These routines need to be implemented by the user. The operations in all these routines are rather elementary like the initialization of the model's physical fields from a state vector provided by PDAF and the initialization of the vector of observations. The examples mentioned above also include example implementations for these routines. In addition, the directory `templates/` contains template implementations of the routines that can be used as a basis for new implementations.
    4343
    4444An 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].