Changes between Version 104 and Version 105 of doc/app/initialization_parameters

Timestamp:

Sep 15, 2010 1:40:19 PM (14 years ago)

Author:

kanani

Comment:

--

doc/app/initialization_parameters

@@ -630 +630 @@
 By default, data for all grid points along z are output. The parameter '''nz_do3d''' can be used to limit the output up to a certain vertical grid point (e.g. in order to reduce the amount of output data). It affects all output of volume data ("normal" output to file, see [../d3par#data_output data_output], as well as output for '''dvrp'''-software, see [../d3par#mode_dvrp mode_dvrp]).
 }}}
-|----------------
-{{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
-}}}
-{{{#!td style="vertical-align:top"
-<insert type>
-}}}
-{{{#!td style="vertical-align:top"
-<insert value>
-}}}
-{{{#!td
-<insert explanation>
-}}}
-|----------------
-{{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
-}}}
-{{{#!td style="vertical-align:top"
-<insert type>
-}}}
-{{{#!td style="vertical-align:top"
-<insert value>
-}}}
-{{{#!td
-<insert explanation>
-}}}
+
 [[BR]]
 
@@ -1007 +982 @@
 |----------------
 {{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
-}}}
-{{{#!td style="vertical-align:top"
-<insert type>
-}}}
-{{{#!td style="vertical-align:top"
-<insert value>
-}}}
-{{{#!td
-<insert explanation>
-}}}
-|----------------
-{{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
-}}}
-{{{#!td style="vertical-align:top"
-<insert type>
-}}}
-{{{#!td style="vertical-align:top"
-<insert value>
-}}}
-{{{#!td
-<insert explanation>
-}}}
-|----------------
-{{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
-}}}
-{{{#!td style="vertical-align:top"
-<insert type>
-}}}
-{{{#!td style="vertical-align:top"
-<insert value>
-}}}
-{{{#!td
-<insert explanation>
-}}}
-|----------------
-{{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
-}}}
-{{{#!td style="vertical-align:top"
-<insert type>
-}}}
-{{{#!td style="vertical-align:top"
-<insert value>
-}}}
-{{{#!td
-<insert explanation>
-}}}
+[=#timestep_scheme '''timestep_scheme''']
+}}}
+{{{#!td style="vertical-align:top"
+C*20
+}}}
+{{{#!td style="vertical-align:top"
+'runge\\
+kutta-3'
+}}}
+{{{#!td
+Time step scheme to be used for the integration of the prognostic variables.\\\\
+The user can choose between the following schemes:\\\\
+'' 'runge-kutta-3' ''\\\
+      Third order Runge-Kutta scheme.\\
+      This scheme requires the use of [#momentum_advec momentum_advec] = [#scalar_advec scalar_advec] = '' 'pw-scheme'.'' Please refer to the documentation on PALM's time integration schemes (28p., in German) for further details.\\\\
+'' 'runge-kutta-2' ''\\\
+      Second order Runge-Kutta scheme.\\
+      For special features see '''timestep_scheme''' = '' 'runge-kutta-3'.''\\\\
+'' 'leapfrog' ''\\\
+      Second order leapfrog scheme.\\
+      Although this scheme requires a constant timestep (because it is centered in time), it is even applied in case of changes in timestep. Therefore, only small changes of the timestep are allowed (see [#dt dt]). However, an Euler timestep is always used as the first timestep of an initial run. When using the Bott-Chlond scheme for scalar advection (see [#scalar_advec scalar_advec]), the prognostic equation for potential temperature will be calculated with the Euler scheme, although the leapfrog scheme is switched on.\\ 
+      The leapfrog scheme must not be used together with the upstream-spline scheme for calculating the advection (see [#scalar_advec scalar_advec] = '' 'ups-scheme' '' and [#momentum_advec momentum_advec] = '' 'ups-scheme' '').\\\\
+'' 'leapfrog+euler' ''\\\
+      The leapfrog scheme is used, but after each change of a timestep an Euler timestep is carried out. Although this method is theoretically correct (because the pure leapfrog method does not allow timestep changes), the divergence of the velocity field (after applying the pressure solver) may be significantly larger than with '' 'leapfrog'.''\\\\
+'' 'euler' ''\\\
+      First order Euler scheme.\\ 
+      The Euler scheme must be used when treating the advection terms with the upstream-spline scheme (see [#scalar_advec scalar_advec] = '' 'ups-scheme' '' and momentum_advec = 'ups-scheme').
+
+
+A differing timestep scheme can be choosed for the subgrid-scale TKE using parameter use_upstream_for_tke.
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+[=#use_upstream_for_tke '''use_upstream_for_tke''']
+}}}
+{{{#!td style="vertical-align:top"
+L
+}}}
+{{{#!td style="vertical-align:top"
+.F.
+}}}
+{{{#!td
+Parameter to choose the advection/timestep scheme to be used for the subgrid-scale TKE.
+
+By default, the advection scheme and the timestep scheme to be used for the subgrid-scale TKE are set by the initialization parameters scalar_advec and timestep_scheme, respectively. use_upstream_for_tke = .T. forces the Euler-scheme and the upstream-scheme to be used as timestep scheme and advection scheme, respectively. By these methods, the strong (artificial) near-surface vertical gradients of the subgrid-scale TKE are significantly reduced. This is required when subgrid-scale velocities are used for advection of particles (see particle package parameter use_sgs_for_particles).
+}}}
+
 [[BR]]