Changes between Version 2 and Version 3 of ImplementAnalysisseek

Timestamp:

May 17, 2011, 4:30:47 PM (14 years ago)

Author:

lnerger

Comment:

--

ImplementAnalysisseek

@@ -28 +28 @@
 For the analysis step of the SEEK filter different operations related to the observations are needed. These operations are requested by PDAF by calling user-supplied routines. Intentionally, the operations are split into separate routines in order to keep the operations rather elementary. This procedure should simplify the implementation. The names of the required routines are specified in the call to the routine `PDAF_put_state_seek`. With regard to the parallelization, all these routines are executed by the filter processes (`filterpe=1`) only.
 
-For completeness we discuss here all user-supplied routines that are specified in the interface to PDAF_put_state_seek. Thus, some of the user-supplied that are explained on the page explaining the modification of the model code for the ensemble integration for the SEIK filter are repeated here, but specified for the SEEK filter.
+For completeness we discuss here all user-supplied routines that are specified in the interface to PDAF_put_state_seek. Thus, some of the user-supplied routines that are explained on the page explaining the modification of the model code for the ensemble integration for the SEIK filter are repeated here, but specified for the SEEK filter.
 
 The SEEK filter is very similar to the SEIK filter. In fact, the SEIK filter has been introduced as an interpolated (Pham et al., 1998) version of the SEEK filter. Due to the similarity of both filters, the interface to the user-supplied routines is almost identical. Several of the user-suppplied routines can be identical for SEEK and SEIK. Differences are marked in the text below. The implementation of the SEEK filter follows its original description by Pham et al. (1998) as reviewed by Nerger et al. (Tellus, 2005).