Changes between Version 4 and Version 5 of InsertAnalysisStep

Timestamp:

Apr 29, 2014, 4:51:18 PM (11 years ago)

Author:

lnerger

Comment:

--

InsertAnalysisStep

@@ -82 +82 @@
 To indicate user-supplied routines we use the prefix `U_`. In the template directory `templates/` as well as in the example implementation in `testsuite/src/dummymodel_1D` these routines exist without the prefix, but with the extension `_pdaf.F90`. In the section titles below we provide the name of the template file in parentheses.
 
+The user-supplied routines are in general identical for the 'fully parallel' and 'flexible' implementation variants. The only difference is in `U_next_observation` as is described below. 
+
 === `U_next_observation` (next_observation_pdaf.F90) ===
 
@@ -96 +98 @@
 The routine is called once at the beginning of each forecast phase. It is executed by all processes that participate in the model integrations.
 
-Based on the information of the current time step, the routine has to define the number of time steps `nsteps` for the next forecast phase. For the 'fully parallel' data assimialtion variant the flag `doexit` is not used. `timenow` is the current model time. However, for the 'fully parallel' data assimilation variant, this value is not relevant.
+Based on the information of the current time step, the routine has to define the number of time steps `nsteps` for the next forecast phase. For the 'fully parallel' data assimilation variant the flag `doexit` is not used and does not need to be set. `timenow` is the current model time. However, for the 'fully parallel' data assimilation variant, this value is not relevant.
 
 Some hints: