Changes between Version 13 and Version 14 of ImplementationConceptOffline
- Timestamp:
- Oct 8, 2013, 8:44:42 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ImplementationConceptOffline
v13 v14 22 22 In the forecast phase the user has to run the numerical model as many times as there are ensemble members. Each model forecast has to be initialized by the state fields of the ensemble member. At the end of each single forecast integration the forecast fields are written into regular output files of the model. Within the offline mode of PDAF, we leave it to the user to control the integrations. As these are regular model integrations, it should be easiest to use the regular scripts used also to perform a free model integration without data assimilation. However, the user has to take care that the output files from each ensemble member are stored separately. 23 23 24 The assimilation program is a simplified implementation of what is required when PDAF is used in its online mode. In particular, no explicit linkage to the model code and no forecast phase are required. Essentially, one just needs t odriver program that calls the PDAF routines. The general structure of the program for the offline assimilation program is depicted in figure 1.24 The assimilation program is a simplified implementation of what is required when PDAF is used in its online mode. In particular, no explicit linkage to the model code and no forecast phase are required. Essentially, one just needs the driver program that calls the PDAF routines. The general structure of the program for the offline assimilation program is depicted in figure 1. 25 25 26 26 [[Image(//pics/PDAF_offline.png)]]