Changes between Version 130 and Version 131 of doc/app/runtime_parameters

Timestamp:

Sep 15, 2010 12:25:00 PM (15 years ago)

Author:

weinreis

Comment:

--

doc/app/runtime_parameters

@@ -376 +376 @@
 }}}
 {{{#!td
-Temporal interval at which data of vertical profiles shall be output (output for printouts, local file [[../iofiles#LIST_PROFIL|LIST_PROFIL)]] (in s).\\\\
+Temporal interval at which data of vertical profiles shall be output (output for printouts, local file [[../iofiles#LIST_PROFIL|LIST_PROFIL]]) (in s).\\\\
 This parameter can be used to assign the temporal interval at which profile data shall be output. Reference time is the beginning of the simulation, thus t = 0. For example if '''dt_dopr_listing''' = ''1800.0'', then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since profiles can not be calculated for times lying within a time step interval, the output times can deviate from these theoretical values. If a time step ranges from t = 1799.8 to t = 1800.2, then in the example above the output would take place at t = 1800.2. In general, the output always lie between t = 1800.0 and t = 1800.0 + [#dt dt] (numbers are related to the example above). If the model uses a variable time step, these deviations from the theoretical output times will of course be different for each output time.\\\\
 In order to guarantee an output of profile data at the end of a simulation (see [#end_time end_time]) in any way, end_time should be a little bit larger than the respective theoretical output time. For example, if '''dt_dopr_listing''' = ''900.0'' and ''3600.0'' seconds are to be simulated, then it should be at least '''end_time''' > ''3600.0 + [#dt dt]''. If variable time steps are used (which is the default), '''dt''' should be properly estimated.\\\\