Changes between Version 16 and Version 17 of ImplementationConceptOffline
- Timestamp:
- May 17, 2025, 12:50:55 PM (22 hours ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ImplementationConceptOffline
v16 v17 35 35 36 36 * With the offline mode of PDAF, no direct coupling between PDAF and the model code is required. The exchange of information between the model and the assimilation program is performed solely through the output and restart files of the model. It requires that the user implements routines to read the model fields from the forecast files. In addition, routines are necessary that write the analysis state ensemble into restart files of the model. 37 * Model-specific operations like the initialization of the array of ensemble states in `PDAF_init` are performed by user-supplied subroutines, which are executed by PDAF as call-back routines. These routines are called through the standard interface of PDAF. They can be implemented in the users programming style and just have to be consistent with the interface. Details on the interface and the required routines are given on the pages describing the implementation steps. The concept of the call-back routines is depicted in Fig. 2.37 * PDAF uses the concept to 'pull' information at the time when it is needed. Model-specific operations like the initialization of the array of ensemble states in `PDAF_init` are performed by user-supplied subroutines, which are executed by PDAF as call-back routines. These routines are called through the standard interface of PDAF. They can be implemented in the users programming style and just have to be consistent with the interface. Details on the interface and the required routines are given on the pages describing the implementation steps. The concept of the call-back routines is depicted in Fig. 2. 38 38 [[Image(//pics/PDAF_callback_offline_v3.png)]] 39 39 [[BR]]'''Figure 2:''' The assimilation program consist of the driver program, the PDAF core, and user-supplied call-back routines.
