Changes between Version 8 and Version 9 of ImplementationConceptOnline

Timestamp:

May 3, 2013, 9:06:34 PM (12 years ago)

Author:

lnerger

Comment:

--

ImplementationConceptOnline

@@ -46 +46 @@
  * Model-specific operations like the initialization of the array of ensemble states in `PDAF_init` are actually performed by user-supplied routines. These routines are called through the standard interface of `PDAF`. Details on the interface and the required routines are given on the pages describing the implementation steps.
  * The assimilation system is controlled by the user-supplied routines that are called through PDAF.  With this strategy, the assimilation program is essentially driven by the model part of the program. Thus, logically the model is not a sub-component of the assimilation system, but the implementation with PDAF results in a model extended for data assimilation.
+[[Image(//pics/PDAF_callback.png)]]
+[[BR]]'''Figure 2:''' Use of user-supplied call-back functions in PDAF
+
  * The user-supplied routines can be implemented analogously to the model code. For example, if the model is implemented using Fortran common blocks or modules of the model code, these can be used to implement the user-supplied routines, too. This simplifies the implementation of the user-supplied routines knowing about the particularities of their model. 
 
@@ -54 +57 @@
 
 [[Image(//pics/parallelization.png)]]
-[[BR]]'''Figure 2:''' Two-level parallelization of PDAF: During the forecast phase several model tasks can be concurrently performed, while each model can be parallelized by itself. In the analysis step one the parallelized filter included in PDAF is applied. 
+[[BR]]'''Figure 3:''' Two-level parallelization of PDAF: During the forecast phase several model tasks can be concurrently performed, while each model can be parallelized by itself. In the analysis step one the parallelized filter included in PDAF is applied.