Index: palm/trunk/DOC/app/chapter_4.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.1.html	(revision 57)
+++ palm/trunk/DOC/app/chapter_4.1.html	(revision 61)
@@ -1,898 +1,98 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html><head>
-
-
-
-
-
-
-
-
-
-
-  
-  
-  
-  
-  
-  
-  
-  
-  
-  
-  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>PALM chapter 4.1</title></head>
-<body>
-
-
-
-
-
-
-
-
-
-
-<h3><a name="chapter4.1"></a>4.1 Initialization parameters</h3>
-
-
-
-
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-
-
-
-
-<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
-
-
-
-
-
-
-
-
-
-
-  <tbody>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><font size="4"><b>Parameter name</b></font></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><b><font size="4">Default</font></b> <br>
-
-
-
-
-
-
-
-
-
-
-      <b><font size="4">value</font></b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="adjust_mixing_length"></a><b>adjust_mixing_length</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Near-surface adjustment of the
-mixing length to the Prandtl-layer law.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Usually the mixing length in LES models l<sub>LES</sub>
+<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>PALM
+chapter 4.1</title></head>
+<body><h3><a name="chapter4.1"></a>4.1
+Initialization parameters</h3>
+<br><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody>
+<tr> <td style="vertical-align: top;"><font size="4"><b>Parameter name</b></font></td>
+<td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
+<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
+<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="adjust_mixing_length"></a><b>adjust_mixing_length</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td> <td style="vertical-align: top;"> <p style="font-style: normal;">Near-surface adjustment of the
+mixing length to the Prandtl-layer law.&nbsp; </p> <p>Usually
+the mixing length in LES models l<sub>LES</sub>
 depends (as in PALM) on the grid size and is possibly restricted
 further in case of stable stratification and near the lower wall (see
 parameter <a href="#wall_adjustment">wall_adjustment</a>).
 With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span>
-the Prandtl' mixing length l<sub>PR</sub> = kappa * z/phi is calculated
+the Prandtl' mixing length l<sub>PR</sub> = kappa * z/phi
+is calculated
 and the mixing length actually used in the model is set l = MIN (l<sub>LES</sub>,
-l<sub>PR</sub>). This usually gives a decrease of the mixing length at
+l<sub>PR</sub>). This usually gives a decrease of the
+mixing length at
 the bottom boundary and considers the fact that eddy sizes
-decrease in the vicinity of the wall.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;"><b>Warning:</b> So far, there is
+decrease in the vicinity of the wall.&nbsp; </p> <p style="font-style: normal;"><b>Warning:</b> So
+far, there is
 no good experience with <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> !&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> and the Prandtl-layer being
-switched on (see <a href="#prandtl_layer">prandtl_layer</a>) <span style="font-style: italic;">'(u*)** 2+neumann'</span>
+<p>With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> and the
+Prandtl-layer being
+switched on (see <a href="#prandtl_layer">prandtl_layer</a>)
+<span style="font-style: italic;">'(u*)** 2+neumann'</span>
 should always be set as the lower boundary condition for the TKE (see <a href="#bc_e_b">bc_e_b</a>),
 otherwise the near-surface value of the TKE is not in agreement with
 the Prandtl-layer law (Prandtl-layer law and Prandtl-Kolmogorov-Ansatz
-should provide the same value for K<sub>m</sub>). A warning is given,
-if this is not the case.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="alpha_surface"></a><b>alpha_surface</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Inclination of the model domain
-with respect to the horizontal (in degrees).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">By means of <b>alpha_surface</b>
+should provide the same value for K<sub>m</sub>). A warning
+is given,
+if this is not the case.</p> </td> </tr> <tr>
+<td style="vertical-align: top;"> <p><a name="alpha_surface"></a><b>alpha_surface</b></p>
+</td> <td style="vertical-align: top;">R<br> </td>
+<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Inclination of the model domain
+with respect to the horizontal (in degrees).&nbsp; </p> <p style="font-style: normal;">By means of <b>alpha_surface</b>
 the model domain can be inclined in x-direction with respect to the
 horizontal. In this way flows over inclined surfaces (e.g. drainage
-flows, gravity flows) can be simulated. In case of <b>alpha_surface </b>/=
-      <span style="font-style: italic;">0</span> the buoyancy term
+flows, gravity flows) can be simulated. In case of <b>alpha_surface
+</b>/= <span style="font-style: italic;">0</span>
+the buoyancy term
 appears both in
 the equation of motion of the u-component and of the w-component.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">An inclination is only possible in
+</p> <p style="font-style: normal;">An inclination
+is only possible in
 case of cyclic horizontal boundary conditions along x AND y (see <a href="#bc_lr">bc_lr</a>
 and <a href="#bc_ns">bc_ns</a>) and <a href="#topography">topography</a> = <span style="font-style: italic;">'flat'</span>. </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Runs with inclined surface still require additional
+<p>Runs with inclined surface still require additional
 user-defined code as well as modifications to the default code. Please
 ask the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">PALM
-developer&nbsp; group</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_e_b"></a><b>bc_e_b</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-TKE.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><b>bc_e_b</b> may be set to&nbsp;<span style="font-style: italic;">'neumann'</span> or <span style="font-style: italic;">'(u*) ** 2+neumann'</span>. <b>bc_e_b</b>
-= <span style="font-style: italic;">'neumann'</span> yields to
+developer&nbsp; group</a>.</p> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="bc_e_b"></a><b>bc_e_b</b></p> </td>
+<td style="vertical-align: top;">C * 20</td> <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Bottom boundary condition of the
+TKE.&nbsp; </p> <p><b>bc_e_b</b> may be
+set to&nbsp;<span style="font-style: italic;">'neumann'</span>
+or <span style="font-style: italic;">'(u*) ** 2+neumann'</span>.
+<b>bc_e_b</b>
+= <span style="font-style: italic;">'neumann'</span>
+yields to
 e(k=0)=e(k=1) (Neumann boundary condition), where e(k=1) is calculated
-via the prognostic TKE equation. Choice of <span style="font-style: italic;">'(u*)**2+neumann'</span> also yields to
+via the prognostic TKE equation. Choice of <span style="font-style: italic;">'(u*)**2+neumann'</span>
+also yields to
 e(k=0)=e(k=1), but the TKE at the Prandtl-layer top (k=1) is calculated
 diagnostically by e(k=1)=(us/0.1)**2. However, this is only allowed if
 a Prandtl-layer is used (<a href="#prandtl_layer">prandtl_layer</a>).
-If this is not the case, a warning is given and <b>bc_e_b</b> is reset
-to <span style="font-style: italic;">'neumann'</span>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">At the top boundary a Neumann
-boundary condition is generally used: (e(nz+1) = e(nz)).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_lr"></a><b>bc_lr</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Boundary
-condition along x (for all quantities).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-By default, a cyclic boundary condition is used along x.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">bc_lr</span> may also be
+If this is not the case, a warning is given and <b>bc_e_b</b>
+is reset
+to <span style="font-style: italic;">'neumann'</span>.&nbsp;
+</p> <p style="font-style: normal;">At the top
+boundary a Neumann
+boundary condition is generally used: (e(nz+1) = e(nz)).</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="bc_lr"></a><b>bc_lr</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
+<td style="vertical-align: top;">Boundary
+condition along x (for all quantities).<br> <br>
+By default, a cyclic boundary condition is used along x.<br> <br>
+<span style="font-weight: bold;">bc_lr</span> may
+also be
 assigned the values <span style="font-style: italic;">'dirichlet/neumann'</span>
-(inflow from left, outflow to the right) or <span style="font-style: italic;">'neumann/dirichlet'</span> (inflow from
+(inflow from left, outflow to the right) or <span style="font-style: italic;">'neumann/dirichlet'</span>
+(inflow from
 right, outflow to the left). This requires the multi-grid method to be
 used for solving the Poisson equation for perturbation pressure (see <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</a>)
-and it also requires cyclic boundary conditions along y (see<br>
-
-
-
-
-
-
-
-
-
-
-      <a href="#bc_ns">bc_ns</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+and it also requires cyclic boundary conditions along y (see<br> <a href="#bc_ns">bc_ns</a>).<br> <br>
 In case of these non-cyclic lateral boundaries, a Dirichlet condition
 is used at the inflow for all quantities (initial vertical profiles -
@@ -906,51 +106,10 @@
 free of divergence at the inflow and at the outflow. For perturbation
 pressure Neumann (zero gradient) conditions are assumed both at the
-inflow and at the outflow.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+inflow and at the outflow.<br> <br>
 When using non-cyclic lateral boundaries, a filter is applied to the
 velocity field in the vicinity of the outflow in order to suppress any
 reflections of outgoing disturbances (see <a href="#km_damp_max">km_damp_max</a>
 and <a href="#outflow_damping_width">outflow_damping_width</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<br>
 In order to maintain a turbulent state of the flow, it may be
 neccessary to continuously impose perturbations on the horizontal
@@ -961,200 +120,22 @@
 and <a href="#inflow_disturbance_end">inflow_disturbance_end</a>.
 The vertical range and the perturbation amplitude are given by <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_b</a>,
-      <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_t</a>,
+<a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_t</a>,
 and <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_amplitude</a>.
 The time interval at which perturbations are to be imposed is set by <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#dt_disturb">dt_disturb</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<br>
 In case of non-cyclic horizontal boundaries <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#call_psolver_at_all_substeps">call_psolver
-at_all_substeps</a> = .T. should be used.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">Note:</span><br>
-
-
-
-
-
-
-
-
-
-
+at_all_substeps</a> = .T. should be used.<br> <br> <span style="font-weight: bold;">Note:</span><br>
 Using non-cyclic lateral boundaries requires very sensitive adjustments
 of the inflow (vertical profiles) and the bottom boundary conditions,
 e.g. a surface heating should not be applied near the inflow boundary
 because this may significantly disturb the inflow. Please check the
-model results very carefully.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_ns"></a><b>bc_ns</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Boundary
-condition along y (for all quantities).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-By default, a cyclic boundary condition is used along y.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">bc_ns</span> may also be
+model results very carefully.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="bc_ns"></a><b>bc_ns</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
+<td style="vertical-align: top;">Boundary
+condition along y (for all quantities).<br> <br>
+By default, a cyclic boundary condition is used along y.<br> <br>
+<span style="font-weight: bold;">bc_ns</span> may
+also be
 assigned the values <span style="font-style: italic;">'dirichlet/neumann'</span>
 (inflow from rear ("north"), outflow to the front ("south")) or <span style="font-style: italic;">'neumann/dirichlet'</span>
@@ -1163,37 +144,5 @@
 method to be used for solving the Poisson equation for perturbation
 pressure (see <a href="chapter_4.2.html#psolver">psolver</a>)
-and it also requires cyclic boundary conditions along x (see<br>
-
-
-
-
-
-
-
-
-
-
-      <a href="#bc_lr">bc_lr</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+and it also requires cyclic boundary conditions along x (see<br> <a href="#bc_lr">bc_lr</a>).<br> <br>
 In case of these non-cyclic lateral boundaries, a Dirichlet condition
 is used at the inflow for all quantities (initial vertical profiles -
@@ -1207,478 +156,54 @@
 free of divergence at the inflow and at the outflow. For perturbation
 pressure Neumann (zero gradient) conditions are assumed both at the
-inflow and at the outflow.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+inflow and at the outflow.<br> <br>
 For further details regarding non-cyclic lateral boundary conditions
-see <a href="#bc_lr">bc_lr</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_p_b"></a><b>bc_p_b</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-perturbation pressure.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>,
-      <span style="font-style: italic;">'neumann'</span> and <span style="font-style: italic;">'neumann+inhomo'</span>.&nbsp; <span style="font-style: italic;">'dirichlet'</span> sets
+see <a href="#bc_lr">bc_lr</a>.</td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="bc_p_b"></a><b>bc_p_b</b></p> </td>
+<td style="vertical-align: top;">C * 20</td> <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Bottom boundary condition of the
+perturbation pressure.&nbsp; </p> <p>Allowed values
+are <span style="font-style: italic;">'dirichlet'</span>,
+<span style="font-style: italic;">'neumann'</span>
+and <span style="font-style: italic;">'neumann+inhomo'</span>.&nbsp;
+<span style="font-style: italic;">'dirichlet'</span>
+sets
 p(k=0)=0.0,&nbsp; <span style="font-style: italic;">'neumann'</span>
 sets p(k=0)=p(k=1). <span style="font-style: italic;">'neumann+inhomo'</span>
 corresponds to an extended Neumann boundary condition where heat flux
 or temperature inhomogeneities near the
-surface (pt(k=1))&nbsp; are additionally regarded (see Shen and LeClerc
+surface (pt(k=1))&nbsp; are additionally regarded (see Shen and
+LeClerc
 (1995, Q.J.R. Meteorol. Soc.,
 1209)). This condition is only permitted with the Prandtl-layer
 switched on (<a href="#prandtl_layer">prandtl_layer</a>),
-otherwise the run is terminated.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Since at the bottom boundary of the model the vertical
+otherwise the run is terminated.&nbsp; </p> <p>Since
+at the bottom boundary of the model the vertical
 velocity
-disappears (w(k=0) = 0.0), the consistent Neumann condition (<span style="font-style: italic;">'neumann'</span> or <span style="font-style: italic;">'neumann+inhomo'</span>) dp/dz = 0 should
+disappears (w(k=0) = 0.0), the consistent Neumann condition (<span style="font-style: italic;">'neumann'</span> or <span style="font-style: italic;">'neumann+inhomo'</span>)
+dp/dz = 0 should
 be used, which leaves the vertical component w unchanged when the
 pressure solver is applied. Simultaneous use of the Neumann boundary
 conditions both at the bottom and at the top boundary (<a href="#bc_p_t">bc_p_t</a>)
 usually yields no consistent solution for the perturbation pressure and
-should be avoided.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_p_t"></a><b>bc_p_t</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-perturbation pressure.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Allowed values are <span style="font-style: italic;">'dirichlet'</span> (p(k=nz+1)= 0.0) or <span style="font-style: italic;">'neumann'</span>
-(p(k=nz+1)=p(k=nz)).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Simultaneous use of Neumann boundary conditions both at the
+should be avoided.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="bc_p_t"></a><b>bc_p_t</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Top boundary condition of the
+perturbation pressure.&nbsp; </p> <p style="font-style: normal;">Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+(p(k=nz+1)= 0.0) or <span style="font-style: italic;">'neumann'</span>
+(p(k=nz+1)=p(k=nz)).&nbsp; </p> <p>Simultaneous use
+of Neumann boundary conditions both at the
 top and bottom boundary (<a href="#bc_p_b">bc_p_b</a>)
 usually yields no consistent solution for the perturbation pressure and
 should be avoided. Since at the bottom boundary the Neumann
 condition&nbsp; is a good choice (see <a href="#bc_p_b">bc_p_b</a>),
-a Dirichlet condition should be set at the top boundary.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_pt_b"></a><b>bc_pt_b</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C*20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-potential temperature.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+a Dirichlet condition should be set at the top boundary.</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="bc_pt_b"></a><b>bc_pt_b</b></p>
+</td> <td style="vertical-align: top;">C*20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Bottom boundary condition of the
+potential temperature.&nbsp; </p> <p>Allowed values
+are <span style="font-style: italic;">'dirichlet'</span>
 (pt(k=0) = const. = <a href="#pt_surface">pt_surface</a>
 + <a href="#pt_surface_initial_change">pt_surface_initial_change</a>;
@@ -1686,441 +211,40 @@
 and <span style="font-style: italic;">'neumann'</span>
 (pt(k=0)=pt(k=1)).&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
-When a constant surface sensible heat flux is used (<a href="#surface_heatflux">surface_heatflux</a>), <b>bc_pt_b</b> = <span style="font-style: italic;">'neumann'</span>
+When a constant surface sensible heat flux is used (<a href="#surface_heatflux">surface_heatflux</a>), <b>bc_pt_b</b>
+= <span style="font-style: italic;">'neumann'</span>
 must be used, because otherwise the resolved scale may contribute to
 the surface flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="pc_pt_t"></a><b>bc_pt_t</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'initial gradient'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-potential temperature.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed are the values <span style="font-style: italic;">'dirichlet'
-      </span>(pt(k=nz+1)
-does not change during the run), <span style="font-style: italic;">'neumann'</span> (pt(k=nz+1)=pt(k=nz)), and <span style="font-style: italic;">'initial_gradient'</span>.
-With the 'initial_gradient'-condition the value of the temperature gradient at the top is
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pc_pt_t"></a><b>bc_pt_t</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'initial gradient'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Top boundary condition of the
+potential temperature.&nbsp; </p> <p>Allowed are the
+values <span style="font-style: italic;">'dirichlet' </span>(pt(k=nz+1)
+does not change during the run), <span style="font-style: italic;">'neumann'</span>
+(pt(k=nz+1)=pt(k=nz)), and <span style="font-style: italic;">'initial_gradient'</span>.
+With the 'initial_gradient'-condition the value of the temperature
+gradient at the top is
 calculated from the initial
-temperature profile (see <a href="#pt_surface">pt_surface</a>, <a href="#pt_vertical_gradient">pt_vertical_gradient</a>)
+temperature profile (see <a href="#pt_surface">pt_surface</a>,
+<a href="#pt_vertical_gradient">pt_vertical_gradient</a>)
 by bc_pt_t_val = (pt_init(k=nz+1) -
 pt_init(k=nz)) / dzu(nz+1).<br>
-
-
-
-
-
-
-
-
-
-
 Using this value (assumed constant during the
 run) the temperature boundary values are calculated as&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">pt(k=nz+1) = pt(k=nz) +
-bc_pt_t_val * dzu(nz+1)</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">(up to k=nz the prognostic
+<ul> <p style="font-style: normal;">pt(k=nz+1) =
+pt(k=nz) +
+bc_pt_t_val * dzu(nz+1)</p> </ul> <p style="font-style: normal;">(up to k=nz the prognostic
 equation for the temperature is solved).<br>
-
-
-
-
-
-
-
-
-
-
-When a constant sensible heat flux is used at the top boundary (<a href="chapter_4.1.html#top_heatflux">top_heatflux</a>), <b>bc_pt_t</b> = <span style="font-style: italic;">'neumann'</span>
+When a constant sensible heat flux is used at the top boundary (<a href="chapter_4.1.html#top_heatflux">top_heatflux</a>),
+<b>bc_pt_t</b> = <span style="font-style: italic;">'neumann'</span>
 must be used, because otherwise the resolved scale may contribute to
-the top flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_q_b"></a><b>bc_q_b</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-specific humidity / total water content.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+the top flux so that a constant value cannot be guaranteed.</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="bc_q_b"></a><b>bc_q_b</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Bottom boundary condition of the
+specific humidity / total water content.&nbsp; </p> <p>Allowed
+values are <span style="font-style: italic;">'dirichlet'</span>
 (q(k=0) = const. = <a href="#q_surface">q_surface</a>
 + <a href="#q_surface_initial_change">q_surface_initial_change</a>;
@@ -2128,150 +252,14 @@
 and <span style="font-style: italic;">'neumann'</span>
 (q(k=0)=q(k=1)).&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
-When a constant surface latent heat flux is used (<a href="#surface_waterflux">surface_waterflux</a>), <b>bc_q_b</b> = <span style="font-style: italic;">'neumann'</span>
+When a constant surface latent heat flux is used (<a href="#surface_waterflux">surface_waterflux</a>), <b>bc_q_b</b>
+= <span style="font-style: italic;">'neumann'</span>
 must be used, because otherwise the resolved scale may contribute to
 the surface flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_q_t"></a><b>bc_q_t</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">C
-* 20</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-specific humidity / total water content.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed are the values <span style="font-style: italic;">'dirichlet'</span>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="bc_q_t"></a><b>bc_q_t</b></p>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">C
+* 20</span></td> <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Top boundary condition of the
+specific humidity / total water content.&nbsp; </p> <p>Allowed
+are the values <span style="font-style: italic;">'dirichlet'</span>
 (q(k=nz) and q(k=nz+1) do
 not change during the run) and <span style="font-style: italic;">'neumann'</span>.
@@ -2279,429 +267,33 @@
 condition the value of the humidity gradient at the top is calculated
 from the
-initial humidity profile (see <a href="#q_surface">q_surface</a>, <a href="#q_vertical_gradient">q_vertical_gradient</a>)
+initial humidity profile (see <a href="#q_surface">q_surface</a>,
+<a href="#q_vertical_gradient">q_vertical_gradient</a>)
 by: bc_q_t_val = ( q_init(k=nz) - q_init(k=nz-1)) / dzu(nz).<br>
-
-
-
-
-
-
-
-
-
-
 Using this value (assumed constant during the run) the humidity
 boundary values
-are calculated as&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">q(k=nz+1) =q(k=nz) +
-bc_q_t_val * dzu(nz+1)</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">(up tp k=nz the prognostic
-equation for q is solved). </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_s_b"></a><b>bc_s_b</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-scalar concentration.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+are calculated as&nbsp; </p> <ul> <p style="font-style: normal;">q(k=nz+1) =q(k=nz) +
+bc_q_t_val * dzu(nz+1)</p> </ul> <p style="font-style: normal;">(up tp k=nz the prognostic
+equation for q is solved). </p> </td> </tr> <tr>
+<td style="vertical-align: top;"> <p><a name="bc_s_b"></a><b>bc_s_b</b></p> </td>
+<td style="vertical-align: top;">C * 20</td> <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Bottom boundary condition of the
+scalar concentration.&nbsp; </p> <p>Allowed values
+are <span style="font-style: italic;">'dirichlet'</span>
 (s(k=0) = const. = <a href="#s_surface">s_surface</a>
 + <a href="#s_surface_initial_change">s_surface_initial_change</a>;
 the user may change this value during the run using user-defined code)
-and <span style="font-style: italic;">'neumann'</span> (s(k=0) =
+and <span style="font-style: italic;">'neumann'</span>
+(s(k=0) =
 s(k=1)).&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
-When a constant surface concentration flux is used (<a href="#surface_scalarflux">surface_scalarflux</a>), <b>bc_s_b</b> = <span style="font-style: italic;">'neumann'</span>
+When a constant surface concentration flux is used (<a href="#surface_scalarflux">surface_scalarflux</a>), <b>bc_s_b</b>
+= <span style="font-style: italic;">'neumann'</span>
 must be used, because otherwise the resolved scale may contribute to
 the surface flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_s_t"></a><b>bc_s_t</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-scalar concentration.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed are the values <span style="font-style: italic;">'dirichlet'</span>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="bc_s_t"></a><b>bc_s_t</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Top boundary condition of the
+scalar concentration.&nbsp; </p> <p>Allowed are the
+values <span style="font-style: italic;">'dirichlet'</span>
 (s(k=nz) and s(k=nz+1) do
 not change during the run) and <span style="font-style: italic;">'neumann'</span>.
@@ -2709,955 +301,104 @@
 condition the value of the scalar concentration gradient at the top is
 calculated
-from the initial scalar concentration profile (see <a href="#s_surface">s_surface</a>,
-      <a href="#s_vertical_gradient">s_vertical_gradient</a>)
+from the initial scalar concentration profile (see <a href="#s_surface">s_surface</a>, <a href="#s_vertical_gradient">s_vertical_gradient</a>)
 by: bc_s_t_val = (s_init(k=nz) - s_init(k=nz-1)) / dzu(nz).<br>
-
-
-
-
-
-
-
-
-
-
 Using this value (assumed constant during the run) the concentration
 boundary values
-are calculated as </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">s(k=nz+1) = s(k=nz) +
-bc_s_t_val * dzu(nz+1)</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">(up to k=nz the prognostic
+are calculated as </p> <ul> <p style="font-style: normal;">s(k=nz+1) = s(k=nz) +
+bc_s_t_val * dzu(nz+1)</p> </ul> <p style="font-style: normal;">(up to k=nz the prognostic
 equation for the scalar concentration is
-solved).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_uv_b"></a><b>bc_uv_b</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-horizontal velocity components u and v.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed values are <span style="font-style: italic;">'dirichlet'
-      </span>and <span style="font-style: italic;">'neumann'</span>. <b>bc_uv_b</b>
-= <span style="font-style: italic;">'dirichlet'</span> yields the
+solved).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="bc_uv_b"></a><b>bc_uv_b</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Bottom boundary condition of the
+horizontal velocity components u and v.&nbsp; </p> <p>Allowed
+values are <span style="font-style: italic;">'dirichlet' </span>and
+<span style="font-style: italic;">'neumann'</span>. <b>bc_uv_b</b>
+= <span style="font-style: italic;">'dirichlet'</span>
+yields the
 no-slip condition with u=v=0 at the bottom. Due to the staggered grid
 u(k=0) and v(k=0) are located at z = - 0,5 * <a href="#dz">dz</a>
 (below the bottom), while u(k=1) and v(k=1) are located at z = +0,5 *
 dz. u=v=0 at the bottom is guaranteed using mirror boundary
-condition:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">u(k=0) = - u(k=1) and v(k=0) = -
-v(k=1)</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">The Neumann boundary condition
+condition:&nbsp; </p> <ul> <p style="font-style: normal;">u(k=0) = - u(k=1) and v(k=0) = -
+v(k=1)</p> </ul> <p style="font-style: normal;">The
+Neumann boundary condition
 yields the free-slip condition with u(k=0) = u(k=1) and v(k=0) =
 v(k=1).
 With Prandtl - layer switched on, the free-slip condition is not
 allowed (otherwise the run will be terminated)<font color="#000000">.</font></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_uv_t"></a><b>bc_uv_t</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-horizontal velocity components u and v.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
-and <span style="font-style: italic;">'neumann'</span>. The
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="bc_uv_t"></a><b>bc_uv_t</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+<td style="vertical-align: top;"> <p style="font-style: normal;">Top boundary condition of the
+horizontal velocity components u and v.&nbsp; </p> <p>Allowed
+values are <span style="font-style: italic;">'dirichlet'</span>
+and <span style="font-style: italic;">'neumann'</span>.
+The
 Dirichlet condition yields u(k=nz+1) = ug(nz+1) and v(k=nz+1) =
 vg(nz+1),
 Neumann condition yields the free-slip condition with u(k=nz+1) =
 u(k=nz) and v(k=nz+1) = v(k=nz) (up to k=nz the prognostic equations
-for the velocities are solved).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_height"></a>building_height</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
-
-
-
-
-
-
-      <td>Height of a single building in m.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">building_height</span> must be less than the height of the model domain. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_x"></a>building_length_x</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
-
-
-
-
-
-
-      <td><span style="font-style: italic;"></span>Width of a single building in m.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_length_x</span> must be at least <span style="font-style: italic;">3 *&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#nx">nx</a><span style="font-style: italic;"> - 1 ) </span><span style="font-style: italic;"> * <a href="#dx">dx</a> </span><span style="font-style: italic;">- <a href="#building_wall_left">building_wall_left</a><a href="#dx"></a><a href="#dx"></a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_y"></a>building_length_y</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
-
-
-
-
-
-
-      <td>Depth of a single building in m.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_length_y</span> must be at least <span style="font-style: italic;">3 *&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#ny">ny</a><span style="font-style: italic;"> - 1 )&nbsp;</span><span style="font-style: italic;"> * <a href="#dy">dy</a></span><span style="font-style: italic;"> - <a href="#building_wall_south">building_wall_south</a><a href="#dy"></a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_left"></a>building_wall_left</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">building centered in x-direction</span></td>
-
-
-
-
-
-
-      <td>x-coordinate of the left building wall (distance between the left building wall and the left border of the model domain) in m.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_wall_left</span> must be at least <span style="font-style: italic;">1 *&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and less than <span style="font-style: italic;">( <a href="#nx">nx</a>&nbsp; - 1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-The default value&nbsp;<span style="font-weight: bold;">building_wall_left</span> = <span style="font-style: italic;">( ( <a href="#nx">nx</a>&nbsp;+ 1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a> ) / 2</span> centers the building in x-direction. </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_south"></a>building_wall_south</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;"></span><span style="font-style: italic;">building centered in y-direction</span></td>
-
-
-
-
-
-
-      <td>y-coordinate of the South building wall (distance between the
+for the velocities are solved).</p> </td> </tr> <tr>
+<td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_height"></a>building_height</span></td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td> <td>Height
+of a single building in m.<br> <br> <span style="font-weight: bold;">building_height</span> must
+be less than the height of the model domain. This parameter requires
+the use of&nbsp;<a href="#topography">topography</a>
+= <span style="font-style: italic;">'single_building'</span>.</td>
+</tr> <tr> <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_x"></a>building_length_x</span></td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td> <td><span style="font-style: italic;"></span>Width of a single
+building in m.<br> <br>
+Currently, <span style="font-weight: bold;">building_length_x</span>
+must be at least <span style="font-style: italic;">3
+*&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#nx">nx</a><span style="font-style: italic;"> - 1 ) </span><span style="font-style: italic;"> * <a href="#dx">dx</a>
+</span><span style="font-style: italic;">- <a href="#building_wall_left">building_wall_left</a></span>.
+This parameter requires the use of&nbsp;<a href="#topography">topography</a>
+= <span style="font-style: italic;">'single_building'</span>.</td>
+</tr> <tr> <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_y"></a>building_length_y</span></td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td> <td>Depth
+of a single building in m.<br> <br>
+Currently, <span style="font-weight: bold;">building_length_y</span>
+must be at least <span style="font-style: italic;">3
+*&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#ny">ny</a><span style="font-style: italic;"> - 1 )&nbsp;</span><span style="font-style: italic;"> * <a href="#dy">dy</a></span><span style="font-style: italic;"> - <a href="#building_wall_south">building_wall_south</a></span>. This parameter requires
+the use of&nbsp;<a href="#topography">topography</a>
+= <span style="font-style: italic;">'single_building'</span>.</td>
+</tr> <tr> <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_left"></a>building_wall_left</span></td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">building centered in x-direction</span></td>
+<td>x-coordinate of the left building wall (distance between the
+left building wall and the left border of the model domain) in m.<br>
+<br>
+Currently, <span style="font-weight: bold;">building_wall_left</span>
+must be at least <span style="font-style: italic;">1
+*&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and less than <span style="font-style: italic;">( <a href="#nx">nx</a>&nbsp;
+- 1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a></span>.
+This parameter requires the use of&nbsp;<a href="#topography">topography</a>
+= <span style="font-style: italic;">'single_building'</span>.<br>
+<br>
+The default value&nbsp;<span style="font-weight: bold;">building_wall_left</span>
+= <span style="font-style: italic;">( ( <a href="#nx">nx</a>&nbsp;+
+1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a> ) / 2</span>
+centers the building in x-direction. </td> </tr> <tr>
+<td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_south"></a>building_wall_south</span></td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;"></span><span style="font-style: italic;">building centered in y-direction</span></td>
+<td>y-coordinate of the South building wall (distance between the
 South building wall and the South border of the model domain) in m.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_wall_south</span> must be at least <span style="font-style: italic;">1 *&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and less than <span style="font-style: italic;">( <a href="#ny">ny</a>&nbsp; - 1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-The default value&nbsp;<span style="font-weight: bold;">building_wall_south</span> = <span style="font-style: italic;">( ( <a href="#ny">ny</a>&nbsp;+ 1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a> ) / 2</span> centers the building in y-direction. </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="cloud_droplets"></a>cloud_droplets</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Parameter to switch on usage of cloud droplets.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<br>
+Currently, <span style="font-weight: bold;">building_wall_south</span>
+must be at least <span style="font-style: italic;">1
+*&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and less than <span style="font-style: italic;">( <a href="#ny">ny</a>&nbsp;
+- 1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a></span>.
+This parameter requires the use of&nbsp;<a href="#topography">topography</a>
+= <span style="font-style: italic;">'single_building'</span>.<br>
+<br>
+The default value&nbsp;<span style="font-weight: bold;">building_wall_south</span>
+= <span style="font-style: italic;">( ( <a href="#ny">ny</a>&nbsp;+
+1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a> ) / 2</span>
+centers the building in y-direction. </td> </tr> <tr>
+<td style="vertical-align: top;"><span style="font-weight: bold;"><a name="cloud_droplets"></a>cloud_droplets</span><br>
+</td> <td style="vertical-align: top;">L<br> </td>
+<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td>
+<td style="vertical-align: top;">Parameter to switch on
+usage of cloud droplets.<br> <br>
 Cloud droplets require to use the particle package (<span style="font-weight: bold;">mrun</span>-option <span style="font-family: monospace;">-p particles</span>),
 so in this case a particle corresponds to a droplet. The droplet
@@ -3666,159 +407,17 @@
 The real number of initial droplets in a grid cell is equal to the
 initial number of droplets (defined by the particle source parameters <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
-      <span lang="en-GB"><font face="Thorndale, serif">and </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>) times the <a href="#initial_weighting_factor">initial_weighting_factor</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-In case of using cloud droplets, the default condensation scheme in PALM cannot be used, i.e. <a href="#cloud_physics">cloud_physics</a> must be set <span style="font-style: italic;">.F.</span>.<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="cloud_physics"></a><b>cloud_physics</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch on the condensation scheme.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-For <b>cloud_physics =</b> <span style="font-style: italic;">.TRUE.</span>, equations for the
+<span lang="en-GB"><font face="Thorndale, serif">and
+</font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>)
+times the <a href="#initial_weighting_factor">initial_weighting_factor</a>.<br>
+<br>
+In case of using cloud droplets, the default condensation scheme in
+PALM cannot be used, i.e. <a href="#cloud_physics">cloud_physics</a>
+must be set <span style="font-style: italic;">.F.</span>.<br>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cloud_physics"></a><b>cloud_physics</b></p>
+</td> <td style="vertical-align: top;">L<br> </td>
+<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td> <td style="vertical-align: top;"> <p>Parameter to switch
+on the condensation scheme.&nbsp; </p>
+For <b>cloud_physics =</b> <span style="font-style: italic;">.TRUE.</span>, equations
+for the
 liquid water&nbsp;
 content and the liquid water potential temperature are solved instead
@@ -3828,794 +427,98 @@
 unsaturated (0%-or-100%-scheme). A simple precipitation scheme can
 additionally be switched on with parameter <a href="#precipitation">precipitation</a>.
-Also cloud-top cooling by longwave radiation can be utilized (see <a href="#radiation">radiation</a>)<br>
-
-
-
-
-
-
-
-
-
-
-      <b><br>
-
-
-
-
-
-
-
-
-
-
-cloud_physics =</b> <span style="font-style: italic;">.TRUE. </span>requires <a href="#moisture">moisture</a> =<span style="font-style: italic;"> .TRUE.</span> .<br>
-
-
-
-
-
-
-
-
-
-
+Also cloud-top cooling by longwave radiation can be utilized (see <a href="#radiation">radiation</a>)<br> <b><br>
+cloud_physics =</b> <span style="font-style: italic;">.TRUE.
+</span>requires <a href="#moisture">moisture</a>
+=<span style="font-style: italic;"> .TRUE.</span> .<br>
 Detailed information about the condensation scheme is given in the
 description of the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM-1/Dokumentationen/Cloud_physics/wolken.pdf">cloud
-physics module</a> (pdf-file, only in German).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-This condensation scheme is not allowed if cloud droplets are simulated explicitly (see <a href="#cloud_droplets">cloud_droplets</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="conserve_volume_flow"></a>conserve_volume_flow</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-
-      <td>Conservation of volume flow in x- and y-direction.<br>
-      <br>
-      <span style="font-weight: bold;">conserve_volume_flow</span> = <span style="font-style: italic;">.TRUE.</span>
+physics module</a> (pdf-file, only in German).<br> <br>
+This condensation scheme is not allowed if cloud droplets are simulated
+explicitly (see <a href="#cloud_droplets">cloud_droplets</a>).<br>
+</td> </tr> <tr> <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="conserve_volume_flow"></a>conserve_volume_flow</span></td>
+<td style="vertical-align: top;">L</td> <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td> <td>Conservation
+of volume flow in x- and y-direction.<br> <br> <span style="font-weight: bold;">conserve_volume_flow</span>
+= <span style="font-style: italic;">.TRUE.</span>
 guarantees that the volume flow through the xz- or yz-cross-section of
 the total model domain remains constant (equal to the initial value at
 t=0) throughout the run.<br>
-</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="cut_spline_overshoot"></a><b>cut_spline_overshoot</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Cuts off of so-called overshoots, which can occur with the
-upstream-spline scheme.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><font color="#000000">The cubic splines tend to overshoot in
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cut_spline_overshoot"></a><b>cut_spline_overshoot</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">.T.</span></td> <td style="vertical-align: top;"> <p>Cuts off of
+so-called overshoots, which can occur with the
+upstream-spline scheme.&nbsp; </p> <p><font color="#000000">The cubic splines tend to overshoot in
 case of discontinuous changes of variables between neighbouring grid
 points.</font><font color="#ff0000"> </font><font color="#000000">This
-may lead to errors in calculating the advection tendency.</font> Choice
-of <b>cut_spline_overshoot</b> = <i>.TRUE.</i> (switched on by
+may lead to errors in calculating the advection tendency.</font>
+Choice
+of <b>cut_spline_overshoot</b> = <i>.TRUE.</i>
+(switched on by
 default)
 allows variable values not to exceed an interval defined by the
 respective adjacent grid points. This interval can be adjusted
 seperately for every prognostic variable (see initialization parameters
-      <a href="#overshoot_limit_e">overshoot_limit_e</a>, <a href="#overshoot_limit_pt">overshoot_limit_pt</a>, <a href="#overshoot_limit_u">overshoot_limit_u</a>,
+<a href="#overshoot_limit_e">overshoot_limit_e</a>, <a href="#overshoot_limit_pt">overshoot_limit_pt</a>, <a href="#overshoot_limit_u">overshoot_limit_u</a>,
 etc.). This might be necessary in case that the
 default interval has a non-tolerable effect on the model
-results.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Overshoots may also be removed using the parameters <a href="#ups_limit_e">ups_limit_e</a>, <a href="#ups_limit_pt">ups_limit_pt</a>,
+results.&nbsp; </p> <p>Overshoots may also be removed
+using the parameters <a href="#ups_limit_e">ups_limit_e</a>,
+<a href="#ups_limit_pt">ups_limit_pt</a>,
 etc. as well as by applying a long-filter (see <a href="#long_filter_factor">long_filter_factor</a>).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="damp_level_1d"></a><b>damp_level_1d</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz+1)</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Height where the damping layer begins in the 1d-model
-(in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This parameter is used to switch on a damping layer for the
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="damp_level_1d"></a><b>damp_level_1d</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">zu(nz+1)</span></td>
+<td style="vertical-align: top;"> <p>Height where
+the damping layer begins in the 1d-model
+(in m).&nbsp; </p> <p>This parameter is used to
+switch on a damping layer for the
 1d-model, which is generally needed for the damping of inertia
 oscillations. Damping is done by gradually increasing the value
 of the eddy diffusivities about 10% per vertical grid level
 (starting with the value at the height given by <b>damp_level_1d</b>,
-or possibly from the next grid pint above), i.e. K<sub>m</sub>(k+1) =
+or possibly from the next grid pint above), i.e. K<sub>m</sub>(k+1)
+=
 1.1 * K<sub>m</sub>(k).
-The values of K<sub>m</sub> are limited to 10 m**2/s at maximum.&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
+The values of K<sub>m</sub> are limited to 10 m**2/s at
+maximum.&nbsp; <br>
 This parameter only comes into effect if the 1d-model is switched on
 for
 the initialization of the 3d-model using <a href="#initializing_actions">initializing_actions</a>
-= <span style="font-style: italic;">'set_1d-model_profiles'</span>. <br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-      <td style="vertical-align: top;"><a name="dissipation_1d"></a><span style="font-weight: bold;">dissipation_1d</span><br>
-      </td>
-      <td style="vertical-align: top;">C*20<br>
-      </td>
-      <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;">
-      <span style="font-style: italic;">model'</span><br>
-      </td>
-      <td style="vertical-align: top;">Calculation method for the energy dissipation term in the TKE equation of the 1d-model.<br>
-      <br>
-By default the dissipation is calculated as in the 3d-model using diss = (0.19 + 0.74 * l / l_grid) * e**1.5 / l.<br>
-      <br>
-Setting <span style="font-weight: bold;">dissipation_1d</span> = <span style="font-style: italic;">'detering'</span> forces the dissipation to be calculated as diss = 0.064 * e**1.5 / l.<br>
-      </td>
-    </tr>
-<tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dt"></a><b>dt</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">variable</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Time step for the 3d-model (in s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By default, (i.e. if a Runge-Kutta scheme is used, see <a href="#timestep_scheme">timestep_scheme</a>)
+= <span style="font-style: italic;">'set_1d-model_profiles'</span>.
+<br> </p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dissipation_1d"></a><span style="font-weight: bold;">dissipation_1d</span><br>
+</td> <td style="vertical-align: top;">C*20<br>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;"> <span style="font-style: italic;">model'</span><br> </td>
+<td style="vertical-align: top;">Calculation method for
+the energy dissipation term in the TKE equation of the 1d-model.<br>
+<br>
+By default the dissipation is calculated as in the 3d-model using diss
+= (0.19 + 0.74 * l / l_grid) * e**1.5 / l.<br> <br>
+Setting <span style="font-weight: bold;">dissipation_1d</span>
+= <span style="font-style: italic;">'detering'</span>
+forces the dissipation to be calculated as diss = 0.064 * e**1.5 / l.<br>
+</td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="dt"></a><b>dt</b></p> </td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">variable</span></td>
+<td style="vertical-align: top;"> <p>Time step for
+the 3d-model (in s).&nbsp; </p> <p>By default, (i.e.
+if a Runge-Kutta scheme is used, see <a href="#timestep_scheme">timestep_scheme</a>)
 the value of the time step is calculating after each time step
 (following the time step criteria) and
-used for the next step.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If the user assigns <b>dt</b> a value, then the time step is
+used for the next step.</p> <p>If the user assigns <b>dt</b>
+a value, then the time step is
 fixed to this value throughout the whole run (whether it fulfills the
 time step
 criteria or not). However, changes are allowed for restart runs,
 because <b>dt</b> can also be used as a <a href="chapter_4.2.html#dt_laufparameter">run
-parameter</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>In case that the calculated time step meets the condition<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p><b>dt</b> &lt; 0.00001 * dt_max (with dt_max = 20.0)</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>the simulation will be aborted. Such situations usually arise
+parameter</a>.&nbsp; </p> <p>In case that the
+calculated time step meets the condition<br> </p> <ul>
+<p><b>dt</b> &lt; 0.00001 * <a href="chapter_4.2.html#dt_max">dt_max</a> (with dt_max
+= 20.0)</p> </ul> <p>the simulation will be
+aborted. Such situations usually arise
 in case of any numerical problem / instability which causes a
-non-realistic increase of the wind speed.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>A small time step due to a large mean horizontal windspeed
+non-realistic increase of the wind speed.&nbsp; </p> <p>A
+small time step due to a large mean horizontal windspeed
 speed may be enlarged by using a coordinate transformation (see <a href="#galilei_transformation">galilei_transformation</a>),
-in order to spare CPU time.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If the leapfrog timestep scheme is used (see <a href="#timestep_scheme">timestep_scheme</a>)
+in order to spare CPU time.<br> </p> <p>If the
+leapfrog timestep scheme is used (see <a href="#timestep_scheme">timestep_scheme</a>)
 a temporary time step value dt_new is calculated first, with dt_new = <a href="chapter_4.2.html#fcl_factor">cfl_factor</a>
 * dt_crit where dt_crit is the maximum timestep allowed by the CFL and
@@ -4625,5 +528,6 @@
 least +5 % / -2%. If it is smaller, <span style="font-weight: bold;">dt</span>
 = dt_new is immediately used for the next timestep. If it is larger,
-then <span style="font-weight: bold;">dt </span>= 1.02 * dt_prev
+then <span style="font-weight: bold;">dt </span>=
+1.02 * dt_prev
 (previous timestep) is used as the new timestep, however the time
 step is only increased if the last change of the time step is dated
@@ -4633,1533 +537,94 @@
 does not change at all. By doing so, permanent time step changes as
 well as large
-sudden changes (increases) in the time step are avoided.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dt_pr_1d"></a><b>dt_pr_1d</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Temporal interval of vertical profile output of the 1D-model
-(in s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Data are written in ASCII format to file <a href="chapter_3.4.html#LIST_PROFIL_1D">LIST_PROFIL_1D</a>.
+sudden changes (increases) in the time step are avoided.</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="dt_pr_1d"></a><b>dt_pr_1d</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
+<td style="vertical-align: top;"> <p>Temporal
+interval of vertical profile output of the 1D-model
+(in s).&nbsp; </p> <p>Data are written in ASCII
+format to file <a href="chapter_3.4.html#LIST_PROFIL_1D">LIST_PROFIL_1D</a>.
 This parameter is only in effect if the 1d-model has been switched on
 for the
 initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
 = <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dt_run_control_1d"></a><b>dt_run_control_1d</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">60.0</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Temporal interval of runtime control output of the 1d-model
-(in s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Data are written in ASCII format to file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_run_control_1d"></a><b>dt_run_control_1d</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">60.0</span></td> <td style="vertical-align: top;"> <p>Temporal interval of
+runtime control output of the 1d-model
+(in s).&nbsp; </p> <p>Data are written in ASCII
+format to file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
 This parameter is only in effect if the 1d-model is switched on for the
 initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
 = <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dx"></a><b>dx</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Horizontal grid spacing along the x-direction (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Along x-direction only a constant grid spacing is allowed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dy"></a><b>dy</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Horizontal grid spacing along the x-direction (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Along x-direction only a constant grid spacing is allowed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dz"></a><b>dz</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Vertical grid spacing (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This parameter must be assigned by the user, because no
-default value is given.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By default, the
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dx"></a><b>dx</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td> <td style="vertical-align: top;"> <p>Horizontal grid
+spacing along the x-direction (in m).&nbsp; </p> <p>Along
+x-direction only a constant grid spacing is allowed.</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="dy"></a><b>dy</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td> <td style="vertical-align: top;"> <p>Horizontal grid
+spacing along the x-direction (in m).&nbsp; </p> <p>Along
+x-direction only a constant grid spacing is allowed.</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="dz"></a><b>dz</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>Vertical grid
+spacing (in m).&nbsp; </p> <p>This parameter must be
+assigned by the user, because no
+default value is given.<br> </p> <p>By default, the
 model uses constant grid spacing along z-direction, but it can be
 stretched using the parameters <a href="#dz_stretch_level">dz_stretch_level</a>
-and <a href="#dz_stretch_factor">dz_stretch_factor</a>. In case of stretching, a maximum allowed grid spacing can be given by <a href="#dz_max">dz_max</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Assuming a constant <span style="font-weight: bold;">dz</span>,
+and <a href="#dz_stretch_factor">dz_stretch_factor</a>.
+In case of stretching, a maximum allowed grid spacing can be given by <a href="#dz_max">dz_max</a>.<br> </p> <p>Assuming
+a constant <span style="font-weight: bold;">dz</span>,
 the scalar levels (zu) are calculated directly by:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>zu(0) = - dz * 0.5&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
-zu(1) = dz * 0.5</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The w-levels lie
-half between them:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>zw(k) = ( zu(k) + zu(k+1) ) * 0.5</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><a name="dz_max"></a><span style="font-weight: bold;">dz_max</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td><td style="vertical-align: top;">Allowed maximum vertical grid spacing (in m).<br><br>If the vertical grid is stretched (see <a href="#dz_stretch_factor">dz_stretch_factor</a> and <a href="#dz_stretch_level">dz_stretch_level</a>), <span style="font-weight: bold;">dz_max</span> can be used to limit the vertical grid spacing.</td></tr><tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dz_stretch_factor"></a><b>dz_stretch_factor</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">1.08</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Stretch factor for a vertically stretched grid (see <a href="#dz_stretch_level">dz_stretch_level</a>).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The stretch factor should not exceed a value of approx. 1.10 -
+<ul> <p>zu(0) = - dz * 0.5&nbsp; <br>
+zu(1) = dz * 0.5</p> </ul> <p>The w-levels lie
+half between them:&nbsp; </p> <ul> <p>zw(k) =
+( zu(k) + zu(k+1) ) * 0.5</p> </ul> </td> </tr>
+<tr><td style="vertical-align: top;"><a name="dz_max"></a><span style="font-weight: bold;">dz_max</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td><td style="vertical-align: top;">Allowed maximum vertical grid
+spacing (in m).<br><br>If the vertical grid is stretched
+(see <a href="#dz_stretch_factor">dz_stretch_factor</a>
+and <a href="#dz_stretch_level">dz_stretch_level</a>),
+<span style="font-weight: bold;">dz_max</span> can
+be used to limit the vertical grid spacing.</td></tr><tr>
+<td style="vertical-align: top;"> <p><a name="dz_stretch_factor"></a><b>dz_stretch_factor</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">1.08</span></td> <td style="vertical-align: top;"> <p>Stretch factor for a
+vertically stretched grid (see <a href="#dz_stretch_level">dz_stretch_level</a>).&nbsp;
+</p> <p>The stretch factor should not exceed a value of
+approx. 1.10 -
 1.12, otherwise the discretization errors due to the stretched grid not
-negligible any more. (refer Kalnay de Rivas)</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="dz_stretch_level"></a><b>dz_stretch_level</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">100000.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Height level above which the grid is to be stretched
-vertically (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The vertical grid spacings <a href="#dz">dz</a>
-above this level are calculated as&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p><b>dz</b>(k+1) = <b>dz</b>(k) * <a href="#dz_stretch_factor">dz_stretch_factor</a></p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>and used as spacings for the scalar levels (zu). The
-w-levels are then defined as:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>zw(k) = ( zu(k) + zu(k+1) ) * 0.5</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="e_min"></a>e_min</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-
-
-
-
-
-
-      <td>Minimum subgrid-scale TKE in m<sup>2</sup>s<sup>-2</sup>.<br>
-
-
-
-
-
-
-
-      <br>This
-option&nbsp;adds artificial viscosity to the flow by ensuring that the
-subgrid-scale TKE does not fall below the minimum threshold <span style="font-weight: bold;">e_min</span>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="end_time_1d"></a><b>end_time_1d</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">864000.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Time to be simulated for the 1d-model (in s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The default value corresponds to a simulated time of 10 days.
+negligible any more. (refer Kalnay de Rivas)</p> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="dz_stretch_level"></a><b>dz_stretch_level</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">100000.0</span><br> </td>
+<td style="vertical-align: top;"> <p>Height level
+above which the grid is to be stretched
+vertically (in m).&nbsp; </p> <p>The vertical grid
+spacings <a href="#dz">dz</a>
+above this level are calculated as&nbsp; </p> <ul> <p><b>dz</b>(k+1)
+= <b>dz</b>(k) * <a href="#dz_stretch_factor">dz_stretch_factor</a></p>
+</ul> <p>and used as spacings for the scalar levels (zu).
+The
+w-levels are then defined as:&nbsp; </p> <ul> <p>zw(k)
+= ( zu(k) + zu(k+1) ) * 0.5</p> </ul> </td> </tr>
+<tr> <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="e_min"></a>e_min</span></td>
+<td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td> <td>Minimum
+subgrid-scale TKE in m<sup>2</sup>s<sup>-2</sup>.<br>
+<br>This
+option&nbsp;adds artificial viscosity to the flow by ensuring that
+the
+subgrid-scale TKE does not fall below the minimum threshold <span style="font-weight: bold;">e_min</span>.</td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="end_time_1d"></a><b>end_time_1d</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">864000.0</span><br> </td>
+<td style="vertical-align: top;"> <p>Time to be
+simulated for the 1d-model (in s).&nbsp; </p> <p>The
+default value corresponds to a simulated time of 10 days.
 Usually, after such a period the inertia oscillations have completely
 decayed and the solution of the 1d-model can be regarded as stationary
@@ -6168,378 +633,37 @@
 initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
 = <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="fft_method"></a><b>fft_method</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'system-</span><br style="font-style: italic;">
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">specific'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>FFT-method to be used.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><br>
-
-
-
-
-
-
-
-
-
-
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="fft_method"></a><b>fft_method</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'system-</span><br style="font-style: italic;"> <span style="font-style: italic;">specific'</span></td>
+<td style="vertical-align: top;"> <p>FFT-method to
+be used.<br> </p> <p><br>
 The fast fourier transformation (FFT) is used for solving the
 perturbation pressure equation with a direct method (see <a href="chapter_4.2.html#psolver">psolver</a>)
 and for calculating power spectra (see optional software packages,
 section <a href="chapter_4.2.html#spectra_package">4.2</a>).</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><br>
-
-
-
-
-
-
-
-
-
-
+<p><br>
 By default, system-specific, optimized routines from external
 vendor libraries are used. However, these are available only on certain
 computers and there are more or less severe restrictions concerning the
-number of gridpoints to be used with them.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>There are two other PALM internal methods available on every
+number of gridpoints to be used with them.<br> </p> <p>There
+are two other PALM internal methods available on every
 machine (their respective source code is part of the PALM source code):</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>1.: The <span style="font-weight: bold;">Temperton</span>-method
+<p>1.: The <span style="font-weight: bold;">Temperton</span>-method
 from Clive Temperton (ECWMF) which is computationally very fast and
 switched on with <b>fft_method</b> = <span style="font-style: italic;">'temperton-algorithm'</span>.
 The number of horizontal gridpoints (nx+1, ny+1) to be used with this
-method must be composed of prime factors 2, 3 and 5.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
+method must be composed of prime factors 2, 3 and 5.<br> </p>
 2.: The <span style="font-weight: bold;">Singleton</span>-method
 which is very slow but has no restrictions concerning the number of
-gridpoints to be used with, switched on with <b>fft_method</b> = <span style="font-style: italic;">'singleton-algorithm'</span>. </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="galilei_transformation"></a><b>galilei_transformation</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Application of a Galilei-transformation to the
+gridpoints to be used with, switched on with <b>fft_method</b>
+= <span style="font-style: italic;">'singleton-algorithm'</span>.
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="galilei_transformation"></a><b>galilei_transformation</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.F.</i></td>
+<td style="vertical-align: top;">Application of a
+Galilei-transformation to the
 coordinate
-system of the model.<br><p>With <b>galilei_transformation</b> = <i>.T.,</i> a so-called
+system of the model.<br><p>With <b>galilei_transformation</b>
+= <i>.T.,</i> a so-called
 Galilei-transformation is switched on which ensures that the coordinate
 system of the model is moved along with the geostrophical wind.
@@ -6556,151 +680,15 @@
 each case, the distance the coordinate system has been moved is written
 to the file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>), the specification of a gestrophic
+</p> <p>Non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
+and <a href="#bc_ns">bc_ns</a>), the specification
+of a gestrophic
 wind that is not constant with height
 as well as e.g. stationary inhomogeneities at the bottom boundary do
-not allow the use of this transformation.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="grid_matching"></a><b>grid_matching</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 6</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'match'</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Variable to adjust the subdomain
-sizes in parallel runs.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+not allow the use of this transformation.</p> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="grid_matching"></a><b>grid_matching</b></p>
+</td> <td style="vertical-align: top;">C * 6</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">'match'</span></td> <td style="vertical-align: top;">Variable to adjust the
+subdomain
+sizes in parallel runs.<br> <br>
 For <b>grid_matching</b> = <span style="font-style: italic;">'strict'</span>,
 the subdomains are forced to have an identical
@@ -6708,30 +696,8 @@
 respective directions of the virtual processor net must fulfill certain
 divisor conditions concerning the grid point numbers in the three
-directions (see <a href="#nx">nx</a>,
-      <a href="#ny">ny</a>
+directions (see <a href="#nx">nx</a>, <a href="#ny">ny</a>
 and <a href="#nz">nz</a>).
 Advantage of this method is that all PEs bear the same computational
-load.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+load.<br> <br>
 There is no such restriction by default, because then smaller
 subdomains are allowed on those processors which
@@ -6741,174 +707,17 @@
 the grid point numbers used. Information about the respective settings
 are given in file <a href="file:///home/raasch/public_html/PALM_group/home/raasch/public_html/PALM_group/doc/app/chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<br>
 When using a multi-grid method for solving the Poisson equation (see <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</a>)
 only <b>grid_matching</b> = <span style="font-style: italic;">'strict'</span>
-is allowed.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>Note:</b><br>
-
-
-
-
-
-
-
-
-
-
+is allowed.<br> <br> <b>Note:</b><br>
 In some cases for small processor numbers there may be a very bad load
 balancing among the
-processors which may reduce the performance of the code.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="inflow_disturbance_begin"></a><b>inflow_disturbance_<br>
-
-
-
-
-
-
-
-
-
-
-begin</b></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(10,</span><br style="font-style: italic;">
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">nx/2 or ny/2)</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Lower
+processors which may reduce the performance of the code.</td> </tr>
+<tr> <td style="vertical-align: top;"><a name="inflow_disturbance_begin"></a><b>inflow_disturbance_<br>
+begin</b></td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">MIN(10,</span><br style="font-style: italic;"> <span style="font-style: italic;">nx/2 or ny/2)</span></td>
+<td style="vertical-align: top;">Lower
 limit of the horizontal range for which random perturbations are to be
-imposed on the horizontal velocity field (gridpoints).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+imposed on the horizontal velocity field (gridpoints).<br> <br>
 If non-cyclic lateral boundary conditions are used (see <a href="#bc_lr">bc_lr</a>
 or <a href="#bc_ns">bc_ns</a>),
@@ -6917,126 +726,9 @@
 horizontal velocity field. Perturbations must be switched on with
 parameter <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="inflow_disturbance_end"></a><b>inflow_disturbance_<br>
-
-
-
-
-
-
-
-
-
-
-end</b></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(100,</span><br style="font-style: italic;">
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">3/4*nx or</span><br style="font-style: italic;">
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">3/4*ny)</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Upper
+</tr> <tr> <td style="vertical-align: top;"><a name="inflow_disturbance_end"></a><b>inflow_disturbance_<br>
+end</b></td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">MIN(100,</span><br style="font-style: italic;"> <span style="font-style: italic;">3/4*nx or</span><br style="font-style: italic;"> <span style="font-style: italic;">3/4*ny)</span></td> <td style="vertical-align: top;">Upper
 limit of the horizontal range for which random perturbations are
-to be imposed on the horizontal velocity field (gridpoints).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+to be imposed on the horizontal velocity field (gridpoints).<br> <br>
 If non-cyclic lateral boundary conditions are used (see <a href="#bc_lr">bc_lr</a>
 or <a href="#bc_ns">bc_ns</a>),
@@ -7045,297 +737,31 @@
 horizontal
 velocity field. Perturbations must be switched on with parameter <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="initializing_actions"></a><b>initializing_actions</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 100</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Initialization actions
-to be carried out.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">This parameter does not have a
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="initializing_actions"></a><b>initializing_actions</b></p>
+</td> <td style="vertical-align: top;">C * 100</td>
+<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p style="font-style: normal;">Initialization actions
+to be carried out.&nbsp; </p> <p style="font-style: normal;">This parameter does not have a
 default value and therefore must be assigned with each model run. For
 restart runs <b>initializing_actions</b> = <span style="font-style: italic;">'read_restart_data'</span>
 must be set. For the initial run of a job chain the following values
-are allowed:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;"><span style="font-style: italic;">'set_constant_profiles'</span>
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>A horizontal wind profile consisting of linear sections (see
-        <a href="#ug_surface">ug_surface</a>, <a href="#ug_vertical_gradient">ug_vertical_gradient</a>, <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a> and <a href="#vg_surface">vg_surface</a>, <a href="#vg_vertical_gradient">vg_vertical_gradient</a>,
-        <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
+are allowed:&nbsp; </p> <p style="font-style: normal;"><span style="font-style: italic;">'set_constant_profiles'</span>
+</p> <ul> <p>A horizontal wind profile consisting
+of linear sections (see <a href="#ug_surface">ug_surface</a>,
+<a href="#ug_vertical_gradient">ug_vertical_gradient</a>,
+<a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>
+and <a href="#vg_surface">vg_surface</a>, <a href="#vg_vertical_gradient">vg_vertical_gradient</a>,
+<a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
 respectively) as well as a vertical temperature (humidity) profile
 consisting of
-linear sections (see <a href="#pt_surface">pt_surface</a>, <a href="#pt_vertical_gradient">pt_vertical_gradient</a>, <a href="#q_surface">q_surface</a>
+linear sections (see <a href="#pt_surface">pt_surface</a>,
+<a href="#pt_vertical_gradient">pt_vertical_gradient</a>,
+<a href="#q_surface">q_surface</a>
 and <a href="#q_vertical_gradient">q_vertical_gradient</a>)
 are assumed as initial profiles. The subgrid-scale TKE is set to 0 but K<sub>m</sub>
-and K<sub>h</sub> are set to very small values because otherwise no TKE
-would be generated.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: italic;">'set_1d-model_profiles' </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>The arrays of the 3d-model are initialized with the
+and K<sub>h</sub> are set to very small values because
+otherwise no TKE
+would be generated.</p> </ul> <p style="font-style: italic;">'set_1d-model_profiles' </p>
+<ul> <p>The arrays of the 3d-model are initialized with
+the
 (stationary) solution of the 1d-model. These are the variables e, kh,
 km, u, v and with Prandtl layer switched on rif, us, usws, vsws. The
@@ -7343,69 +769,12 @@
 for 'set_constant_profiles' and assumed as constant in time within the
 1d-model. For steering of the 1d-model a set of parameters with suffix
-"_1d" (e.g. <a href="#end_time_1d">end_time_1d</a>, <a href="#damp_level_1d">damp_level_1d</a>)
-is available.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'by_user'</span></p><p style="margin-left: 40px;">The initialization of the arrays of the 3d-model is under complete control of the user and has to be done in routine <a href="chapter_3.5.1.html#user_init_3d_model">user_init_3d_model</a> of the user-interface.<span style="font-style: italic;"></span></p><p><span style="font-style: italic;">'initialize_vortex'</span> </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The initial velocity field of the
+"_1d" (e.g. <a href="#end_time_1d">end_time_1d</a>,
+<a href="#damp_level_1d">damp_level_1d</a>)
+is available.</p> </ul> <p><span style="font-style: italic;">'by_user'</span></p><p style="margin-left: 40px;">The initialization of the arrays
+of the 3d-model is under complete control of the user and has to be
+done in routine <a href="chapter_3.5.1.html#user_init_3d_model">user_init_3d_model</a>
+of the user-interface.<span style="font-style: italic;"></span></p><p><span style="font-style: italic;">'initialize_vortex'</span>
+</p> <div style="margin-left: 40px;">The initial
+velocity field of the
 3d-model corresponds to a
 Rankine-vortex with vertical axis. This setting may be used to test
@@ -7421,68 +790,7 @@
 extends from k = 0 to k = nz+1. Its radius is 8 * <a href="#dx">dx</a>
 and the exponentially decaying part ranges to 32 * <a href="#dx">dx</a>
-(see init_rankine.f90). </div>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'initialize_ptanom'</span> </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>A 2d-Gauss-like shape disturbance (x,y) is added to the
+(see init_rankine.f90). </div> <p><span style="font-style: italic;">'initialize_ptanom'</span>
+</p> <ul> <p>A 2d-Gauss-like shape disturbance
+(x,y) is added to the
 initial temperature field with radius 10.0 * <a href="#dx">dx</a>
 and center at jc = (nx+1)/2. This may be used for tests of scalar
@@ -7494,225 +802,19 @@
 Additionally, the buoyancy term
 must be switched of in the equation of motion&nbsp; for w (this
-requires the user to comment out the call of <span style="font-family: monospace;">buoyancy</span> in the source code of <span style="font-family: monospace;">prognostic_equations.f90</span>).</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Values may be
+requires the user to comment out the call of <span style="font-family: monospace;">buoyancy</span> in the
+source code of <span style="font-family: monospace;">prognostic_equations.f90</span>).</p>
+</ul> <p style="font-style: normal;">Values may be
 combined, e.g. <b>initializing_actions</b> = <span style="font-style: italic;">'set_constant_profiles
-initialize_vortex'</span>, but the values of <span style="font-style: italic;">'set_constant_profiles'</span>, <span style="font-style: italic;">'set_1d-model_profiles'</span>
-, and <span style="font-style: italic;">'by_user'</span> must not be given at the same time.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="font-style: italic;"> </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="km_constant"></a><b>km_constant</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>variable<br>
-
-
-
-
-
-
-
-
-
-
-(computed from TKE)</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Constant eddy diffusivities are used (laminar
-simulations).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If this parameter is specified, both in the 1d and in the
+initialize_vortex'</span>, but the values of <span style="font-style: italic;">'set_constant_profiles'</span>,
+<span style="font-style: italic;">'set_1d-model_profiles'</span>
+, and <span style="font-style: italic;">'by_user'</span>
+must not be given at the same time.</p> <p style="font-style: italic;"> </p> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="km_constant"></a><b>km_constant</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>variable<br>
+(computed from TKE)</i></td> <td style="vertical-align: top;"> <p>Constant eddy
+diffusivities are used (laminar
+simulations).&nbsp; </p> <p>If this parameter is
+specified, both in the 1d and in the
 3d-model constant values for the eddy diffusivities are used in
 space and time with K<sub>m</sub> = <b>km_constant</b>
@@ -7720,128 +822,10 @@
 The prognostic equation for the subgrid-scale TKE is switched off.
 Constant eddy diffusivities are only allowed with the Prandtl layer (<a href="#prandtl_layer">prandtl_layer</a>)
-switched off.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="km_damp_max"></a><b>km_damp_max</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.5*(dx
-or dy)</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Maximum
+switched off.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="km_damp_max"></a><b>km_damp_max</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">0.5*(dx
+or dy)</span></td> <td style="vertical-align: top;">Maximum
 diffusivity used for filtering the velocity field in the vicinity of
-the outflow (in m<sup>2</sup>/s).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+the outflow (in m<sup>2</sup>/s).<br> <br>
 When using non-cyclic lateral boundaries (see <a href="#bc_lr">bc_lr</a>
 or <a href="#bc_ns">bc_ns</a>),
@@ -7853,26 +837,5 @@
 parallel to the outflow boundary are filtered (e.g. v and w, if the
 outflow is along x). Damping is applied from the bottom to the top of
-the domain.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+the domain.<br> <br>
 The horizontal range of the smoothing is controlled by <a href="#outflow_damping_width">outflow_damping_width</a>
 which defines the number of gridpoints (counted from the outflow
@@ -7883,208 +846,21 @@
 up to the outflow boundary. If at a certain grid point the eddy
 diffusivity calculated from the flow field is larger than as described
-above, it is used instead.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+above, it is used instead.<br> <br>
 The default value of <span style="font-weight: bold;">km_damp_max</span>
-has been empirically proven to be sufficient.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="long_filter_factor"></a><b>long_filter_factor</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Filter factor for the so-called Long-filter.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><br>
-
-
-
-
-
-
-
-
-
-
+has been empirically proven to be sufficient.</td> </tr> <tr>
+<td style="vertical-align: top;"> <p><a name="long_filter_factor"></a><b>long_filter_factor</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Filter factor
+for the so-called Long-filter.<br> </p> <p><br>
 This filter very efficiently
 eliminates 2-delta-waves sometimes cauesed by the upstream-spline
 scheme (see Mahrer and
 Pielke, 1978: Mon. Wea. Rev., 106, 818-830). It works in all three
-directions in space. A value of <b>long_filter_factor</b> = <i>0.01</i>
+directions in space. A value of <b>long_filter_factor</b>
+= <i>0.01</i>
 sufficiently removes the small-scale waves without affecting the
-longer waves.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By default, the filter is switched off (= <i>0.0</i>).
+longer waves.<br> </p> <p>By default, the filter is
+switched off (= <i>0.0</i>).
 It is exclusively applied to the tendencies calculated by the
 upstream-spline scheme (see <a href="#momentum_advec">momentum_advec</a>
@@ -8094,405 +870,52 @@
 2-delta-waves is reduced. There, the amplitude of these waves is only
 reduced by approx. 50%, otherwise by nearly 100%.&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
-Filter factors with values &gt; <i>0.01</i> also reduce the amplitudes
+Filter factors with values &gt; <i>0.01</i> also
+reduce the amplitudes
 of waves with wavelengths longer than 2-delta (see the paper by Mahrer
 and
-Pielke, quoted above). </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-      <td style="vertical-align: top;"><a name="mixing_length_1d"></a><span style="font-weight: bold;">mixing_length_1d</span><br>
-      </td>
-      <td style="vertical-align: top;">C*20<br>
-      </td>
-      <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;">
-      <span style="font-style: italic;">model'</span><br>
-      </td>
-      <td style="vertical-align: top;">Mixing length used in the 1d-model.<br>
-      <br>
-By default the mixing length is calculated as in the 3d-model (i.e. it depends on the grid spacing).<br>
-      <br>
-By setting <span style="font-weight: bold;">mixing_length_1d</span> = <span style="font-style: italic;">'blackadar'</span>,
+Pielke, quoted above). </p> </td> </tr> <tr>
+<td style="vertical-align: top;"><a name="mixing_length_1d"></a><span style="font-weight: bold;">mixing_length_1d</span><br>
+</td> <td style="vertical-align: top;">C*20<br>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;"> <span style="font-style: italic;">model'</span><br> </td>
+<td style="vertical-align: top;">Mixing length used in the
+1d-model.<br> <br>
+By default the mixing length is calculated as in the 3d-model (i.e. it
+depends on the grid spacing).<br> <br>
+By setting <span style="font-weight: bold;">mixing_length_1d</span>
+= <span style="font-style: italic;">'blackadar'</span>,
 the so-called Blackadar mixing length is used (l = kappa * z / ( 1 +
 kappa * z / lambda ) with the limiting value lambda = 2.7E-4 * u_g / f).<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">
-      <p><a name="moisture"></a><b>moisture</b></p>
-      </td>
-      <td style="vertical-align: top;">L</td>
-      <td style="vertical-align: top;"><i>.F.</i></td>
-      <td style="vertical-align: top;">
-      <p>Parameter to switch on the prognostic equation for specific
-humidity q.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The initial vertical profile of q can be set via parameters <a href="chapter_4.1.html#q_surface">q_surface</a>, <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="moisture"></a><b>moisture</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.F.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+switch on the prognostic equation for specific
+humidity q.<br> </p> <p>The initial vertical
+profile of q can be set via parameters <a href="chapter_4.1.html#q_surface">q_surface</a>, <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
 and <a href="chapter_4.1.html#q_vertical_gradient_level">q_vertical_gradient_level</a>.&nbsp;
 Boundary conditions can be set via <a href="chapter_4.1.html#q_surface_initial_change">q_surface_initial_change</a>
 and <a href="chapter_4.1.html#surface_waterflux">surface_waterflux</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-
+</p>
 If the condensation scheme is switched on (<a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
 = .TRUE.), q becomes the total liquid water content (sum of specific
-humidity and liquid water content).</td>
-    </tr>
-<tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="momentum_advec"></a><b>momentum_advec</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 10</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>'pw-scheme'</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Advection scheme to be used for the momentum equations.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+humidity and liquid water content).</td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="momentum_advec"></a><b>momentum_advec</b></p>
+</td> <td style="vertical-align: top;">C * 10</td>
+<td style="vertical-align: top;"><i>'pw-scheme'</i></td>
+<td style="vertical-align: top;"> <p>Advection
+scheme to be used for the momentum equations.<br> <br>
 The user can choose between the following schemes:<br>
-
-
-
-
-
-
-
-
-
-
-&nbsp;<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">'pw-scheme'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The scheme of Piascek and
+&nbsp;<br> <br> <span style="font-style: italic;">'pw-scheme'</span><br>
+</p> <div style="margin-left: 40px;">The scheme of
+Piascek and
 Williams (1970, J. Comp. Phys., 6,
 392-405) with central differences in the form C3 is used.<br>
-
-
-
-
-
-
-
-
-
-
 If intermediate Euler-timesteps are carried out in case of <a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'leapfrog+euler'</span> the
+= <span style="font-style: italic;">'leapfrog+euler'</span>
+the
 advection scheme is - for the Euler-timestep - automatically switched
-to an upstream-scheme.<br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p> </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'ups-scheme'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The upstream-spline scheme is
+to an upstream-scheme.<br> </div> <p> </p> <p><span style="font-style: italic;">'ups-scheme'</span><br>
+</p> <div style="margin-left: 40px;">The
+upstream-spline scheme is
 used
 (see Mahrer and Pielke,
@@ -8503,5 +926,6 @@
 expensive. In
 addition, the use of the Euler-timestep scheme is mandatory (<a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'</span><i>euler'</i>), i.e. the
+= <span style="font-style: italic;">'</span><i>euler'</i>),
+i.e. the
 timestep accuracy is only of first order.
 For this reason the advection of scalar variables (see <a href="#scalar_advec">scalar_advec</a>)
@@ -8509,90 +933,19 @@
 because otherwise the scalar variables would
 be subject to large numerical diffusion due to the upstream
-scheme.&nbsp; </div>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">Since the cubic splines used tend
+scheme.&nbsp; </div> <p style="margin-left: 40px;">Since
+the cubic splines used tend
 to overshoot under
 certain circumstances, this effect must be adjusted by suitable
 filtering and smoothing (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>,
-      <a href="#long_filter_factor">long_filter_factor</a>, <a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>,
-      <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
+<a href="#long_filter_factor">long_filter_factor</a>,
+<a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>, <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
 This is always neccessary for runs with stable stratification,
 even if this stratification appears only in parts of the model domain.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">With stable stratification the
+</p> <div style="margin-left: 40px;">With stable
+stratification the
 upstream-spline scheme also
 produces gravity waves with large amplitude, which must be
 suitably damped (see <a href="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">Important: </span>The&nbsp;
+<br> <span style="font-weight: bold;">Important: </span>The&nbsp;
 upstream-spline scheme is not implemented for humidity and passive
 scalars (see <a href="#moisture">moisture</a>
@@ -8602,257 +955,63 @@
 very long execution times! The scheme is also not allowed for
 non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>).</div>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    
-
-
-
-
-
-
-
-
-
-
-    <tr>
-      <td style="vertical-align: top;"><a name="netcdf_precision"></a><span style="font-weight: bold;">netcdf_precision</span><br>
-      </td>
-      <td style="vertical-align: top;">C*20<br>
-(10)<br>
-      </td>
-      <td style="vertical-align: top;"><span style="font-style: italic;">single preci-</span><br style="font-style: italic;">
-      <span style="font-style: italic;">sion for all</span><br style="font-style: italic;">
-      <span style="font-style: italic;">output quan-</span><br style="font-style: italic;">
-      <span style="font-style: italic;">tities</span><br>
-      </td>
-      <td style="vertical-align: top;">Defines the accuracy of the NetCDF output.<br>
-      <br>
-By default, all NetCDF output data (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>) have single precision&nbsp; (4 byte) accuracy. Double precision (8 byte) can be choosen alternatively.<br>
-Accuracy for the different output data (cross sections, 3d-volume data, spectra, etc.) can be set independently.<br>
-      <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL4'</span> (single precision) or <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL8'</span> (double precision) are the two principally allowed values for <span style="font-weight: bold;">netcdf_precision</span>, where the string <span style="font-style: italic;">'&lt;out&gt;' </span>can be chosen out of the following list:<br>
-      <br>
-      <table style="text-align: left; width: 284px; height: 234px;" border="1" cellpadding="2" cellspacing="2">
-        <tbody>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'xy'</span><br>
-            </td>
-            <td style="vertical-align: top;">horizontal cross section<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'xz'</span><br>
-            </td>
-            <td style="vertical-align: top;">vertical (xz) cross section<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'yz'</span><br>
-            </td>
-            <td style="vertical-align: top;">vertical (yz) cross section<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'2d'</span><br>
-            </td>
-            <td style="vertical-align: top;">all cross sections<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'3d'</span><br>
-            </td>
-            <td style="vertical-align: top;">volume data<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'pr'</span><br>
-            </td>
-            <td style="vertical-align: top;">vertical profiles<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'ts'</span><br>
-            </td>
-            <td style="vertical-align: top;">time series, particle time series<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'sp'</span><br>
-            </td>
-            <td style="vertical-align: top;">spectra<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'prt'</span><br>
-            </td>
-            <td style="vertical-align: top;">particles<br>
-            </td>
-          </tr>
-          <tr>
-            <td style="vertical-align: top;"><span style="font-style: italic;">'all'</span><br>
-            </td>
-            <td style="vertical-align: top;">all output quantities<br>
-            </td>
-          </tr>
-        </tbody>
-      </table>
-      <br>
-      <span style="font-weight: bold;">Example:</span><br>
+and <a href="#bc_ns">bc_ns</a>).</div> </td>
+</tr> <tr> <td style="vertical-align: top;"><a name="netcdf_precision"></a><span style="font-weight: bold;">netcdf_precision</span><br>
+</td> <td style="vertical-align: top;">C*20<br>
+(10)<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">single preci-</span><br style="font-style: italic;"> <span style="font-style: italic;">sion for all</span><br style="font-style: italic;"> <span style="font-style: italic;">output quan-</span><br style="font-style: italic;"> <span style="font-style: italic;">tities</span><br> </td>
+<td style="vertical-align: top;">Defines the accuracy of
+the NetCDF output.<br> <br>
+By default, all NetCDF output data (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
+have single precision&nbsp; (4 byte) accuracy. Double precision (8
+byte) can be choosen alternatively.<br>
+Accuracy for the different output data (cross sections, 3d-volume data,
+spectra, etc.) can be set independently.<br> <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL4'</span>
+(single precision) or <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL8'</span>
+(double precision) are the two principally allowed values for <span style="font-weight: bold;">netcdf_precision</span>,
+where the string <span style="font-style: italic;">'&lt;out&gt;'
+</span>can be chosen out of the following list:<br> <br>
+<table style="text-align: left; width: 284px; height: 234px;" border="1" cellpadding="2" cellspacing="2"> <tbody>
+<tr> <td style="vertical-align: top;"><span style="font-style: italic;">'xy'</span><br> </td>
+<td style="vertical-align: top;">horizontal cross section<br>
+</td> </tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'xz'</span><br> </td>
+<td style="vertical-align: top;">vertical (xz) cross
+section<br> </td> </tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'yz'</span><br> </td>
+<td style="vertical-align: top;">vertical (yz) cross
+section<br> </td> </tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'2d'</span><br> </td>
+<td style="vertical-align: top;">all cross sections<br>
+</td> </tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'3d'</span><br> </td>
+<td style="vertical-align: top;">volume data<br> </td>
+</tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'pr'</span><br> </td>
+<td style="vertical-align: top;">vertical profiles<br>
+</td> </tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'ts'</span><br> </td>
+<td style="vertical-align: top;">time series, particle
+time series<br> </td> </tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'sp'</span><br> </td>
+<td style="vertical-align: top;">spectra<br> </td>
+</tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'prt'</span><br> </td>
+<td style="vertical-align: top;">particles<br> </td>
+</tr> <tr> <td style="vertical-align: top;"><span style="font-style: italic;">'all'</span><br> </td>
+<td style="vertical-align: top;">all output quantities<br>
+</td> </tr> </tbody> </table> <br> <span style="font-weight: bold;">Example:</span><br>
 If all cross section data and the particle data shall be output in
-double precision and all other quantities in single precision, then <span style="font-weight: bold;">netcdf_precision</span> = <span style="font-style: italic;">'2d_NF90_REAL8'</span>, <span style="font-style: italic;">'prt_NF90_REAL8'</span> has to be assigned.<br>
-      </td>
-    </tr>
-<tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="npex"></a><b>npex</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Number of processors along x-direction of the virtual
+double precision and all other quantities in single precision, then <span style="font-weight: bold;">netcdf_precision</span> = <span style="font-style: italic;">'2d_NF90_REAL8'</span>, <span style="font-style: italic;">'prt_NF90_REAL8'</span>
+has to be assigned.<br> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="npex"></a><b>npex</b></p> </td>
+<td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>Number of processors
+along x-direction of the virtual
 processor
-net.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For parallel runs, the total number of processors to be used
+net.&nbsp; </p> <p>For parallel runs, the total
+number of processors to be used
 is given by
-the <span style="font-weight: bold;">mrun</span> option <a href="http://www.muk.uni-hannover.de/software/mrun_beschreibung.html#Opt-X">-X</a>.
+the <span style="font-weight: bold;">mrun</span>
+option <a href="http://www.muk.uni-hannover.de/software/mrun_beschreibung.html#Opt-X">-X</a>.
 By default, depending on the type of the parallel computer, PALM
 generates a 1d processor
 net (domain decomposition along x, <span style="font-weight: bold;">npey</span>
-= <span style="font-style: italic;">1</span>) or a 2d-net (this is
+= <span style="font-style: italic;">1</span>) or a
+2d-net (this is
 favored on machines with fast communication network). In case of a
 2d-net, it is tried to make it more or less square-shaped. If, for
 example, 16 processors are assigned (-X 16), a 4 * 4 processor net is
-generated (<span style="font-weight: bold;">npex</span> = <span style="font-style: italic;">4</span>, <span style="font-weight: bold;">npey</span>
+generated (<span style="font-weight: bold;">npex</span>
+= <span style="font-style: italic;">4</span>, <span style="font-weight: bold;">npey</span>
 = <span style="font-style: italic;">4</span>).
 This choice is optimal for square total domains (<a href="#nx">nx</a>
@@ -8860,1125 +1019,119 @@
 since then the number of ghost points at the lateral boundarys of
 the subdomains is minimal. If <span style="font-weight: bold;">nx</span>
-nd <span style="font-weight: bold;">ny</span> differ extremely, the
+nd <span style="font-weight: bold;">ny</span>
+differ extremely, the
 processor net should be manually adjusted using adequate values for <span style="font-weight: bold;">npex</span> and <span style="font-weight: bold;">npey</span>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><b>Important:</b> The value of <span style="font-weight: bold;">npex</span> * <span style="font-weight: bold;">npey</span> must exactly correspond to the
+<p><b>Important:</b> The value of <span style="font-weight: bold;">npex</span> * <span style="font-weight: bold;">npey</span> must exactly
+correspond to the
 value assigned by the <span style="font-weight: bold;">mrun</span>-option
-      <tt>-X</tt>.
+<tt>-X</tt>.
 Otherwise the model run will abort with a corresponding error
 message.&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
 Additionally, the specification of <span style="font-weight: bold;">npex</span>
-and <span style="font-weight: bold;">npey</span> may of course
+and <span style="font-weight: bold;">npey</span>
+may of course
 override the default setting for the domain decomposition (1d or 2d)
 which may have a significant (negative) effect on the code performance.
-      </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="npey"></a><b>npey</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Number of processors along y-direction of the virtual
+</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="npey"></a><b>npey</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>Number of processors
+along y-direction of the virtual
 processor
-net.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#npex">npex</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="nsor_ini"></a><b>nsor_ini</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>100</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Initial number of iterations with the SOR algorithm.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This parameter is only effective if the SOR algorithm was
+net.&nbsp; </p> <p>For further information see <a href="#npex">npex</a>.</p> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="nsor_ini"></a><b>nsor_ini</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><i>100</i></td>
+<td style="vertical-align: top;"> <p>Initial number
+of iterations with the SOR algorithm.&nbsp; </p> <p>This
+parameter is only effective if the SOR algorithm was
 selected as the pressure solver scheme (<a href="chapter_4.2.html#psolver">psolver</a>
-= <span style="font-style: italic;">'sor'</span>) and specifies the
+= <span style="font-style: italic;">'sor'</span>)
+and specifies the
 number of initial iterations of the SOR
 scheme (at t = 0). The number of subsequent iterations at the following
 timesteps is determined
 with the parameter <a href="#nsor">nsor</a>.
-Usually <b>nsor</b> &lt; <b>nsor_ini</b>, since in each case
+Usually <b>nsor</b> &lt; <b>nsor_ini</b>,
+since in each case
 subsequent calls to <a href="chapter_4.2.html#psolver">psolver</a>
 use the solution of the previous call as initial value. Suitable
 test runs should determine whether sufficient convergence of the
 solution is obtained with the default value and if necessary the value
-of <b>nsor_ini</b> should be changed.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="nx"></a><b>nx</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Number of grid points in x-direction.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>A value for this parameter must be assigned. Since the lower
+of <b>nsor_ini</b> should be changed.</p> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="nx"></a><b>nx</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>Number of grid
+points in x-direction.&nbsp; </p> <p>A value for this
+parameter must be assigned. Since the lower
 array bound in PALM
 starts with i = 0, the actual number of grid points is equal to <b>nx+1</b>.
 In case of cyclic boundary conditions along x, the domain size is (<b>nx+1</b>)*
-      <a href="#dx">dx</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For parallel runs, in case of <a href="#grid_matching">grid_matching</a>
-= <span style="font-style: italic;">'strict'</span>, <b>nx+1</b> must
+<a href="#dx">dx</a>.</p> <p>For
+parallel runs, in case of <a href="#grid_matching">grid_matching</a>
+= <span style="font-style: italic;">'strict'</span>,
+<b>nx+1</b> must
 be an integral multiple
 of the processor numbers (see <a href="#npex">npex</a>
 and <a href="#npey">npey</a>)
 along x- as well as along y-direction (due to data
-transposition restrictions).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ny"></a><b>ny</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Number of grid points in y-direction.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>A value for this parameter must be assigned. Since the lower
+transposition restrictions).</p> </td> </tr> <tr>
+<td style="vertical-align: top;"> <p><a name="ny"></a><b>ny</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>Number of grid
+points in y-direction.&nbsp; </p> <p>A value for this
+parameter must be assigned. Since the lower
 array bound in PALM starts with i = 0, the actual number of grid points
-is equal to <b>ny+1</b>. In case of cyclic boundary conditions along
+is equal to <b>ny+1</b>. In case of cyclic boundary
+conditions along
 y, the domain size is (<b>ny+1</b>) * <a href="#dy">dy</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For parallel runs, in case of <a href="#grid_matching">grid_matching</a>
-= <span style="font-style: italic;">'strict'</span>, <b>ny+1</b> must
+<p>For parallel runs, in case of <a href="#grid_matching">grid_matching</a>
+= <span style="font-style: italic;">'strict'</span>,
+<b>ny+1</b> must
 be an integral multiple
 of the processor numbers (see <a href="#npex">npex</a>
 and <a href="#npey">npey</a>)&nbsp;
 along y- as well as along x-direction (due to data
-transposition restrictions).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="nz"></a><b>nz</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Number of grid points in z-direction.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>A value for this parameter must be assigned. Since the lower
+transposition restrictions).</p> </td> </tr> <tr>
+<td style="vertical-align: top;"> <p><a name="nz"></a><b>nz</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>Number of grid
+points in z-direction.&nbsp; </p> <p>A value for this
+parameter must be assigned. Since the lower
 array bound in PALM
 starts with k = 0 and since one additional grid point is added at the
-top boundary (k = <b>nz+1</b>), the actual number of grid points is <b>nz+2</b>.
-However, the prognostic equations are only solved up to <b>nz</b> (u,
+top boundary (k = <b>nz+1</b>), the actual number of grid
+points is <b>nz+2</b>.
+However, the prognostic equations are only solved up to <b>nz</b>
+(u,
 v)
-or up to <b>nz-1</b> (w, scalar quantities). The top boundary for u
-and v is at k = <b>nz+1</b> (u, v) while at k = <b>nz</b> for all
-other quantities.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For parallel runs,&nbsp; in case of <a href="#grid_matching">grid_matching</a>
-= <span style="font-style: italic;">'strict'</span>, <b>nz</b> must
+or up to <b>nz-1</b> (w, scalar quantities). The top
+boundary for u
+and v is at k = <b>nz+1</b> (u, v) while at k = <b>nz</b>
+for all
+other quantities.&nbsp; </p> <p>For parallel
+runs,&nbsp; in case of <a href="#grid_matching">grid_matching</a>
+= <span style="font-style: italic;">'strict'</span>,
+<b>nz</b> must
 be an integral multiple of
 the number of processors in x-direction (due to data transposition
-restrictions).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="omega"></a><b>omega</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>7.29212E-5</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Angular velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The angular velocity of the earth is set by default. The
+restrictions).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="omega"></a><b>omega</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>7.29212E-5</i></td>
+<td style="vertical-align: top;"> <p>Angular
+velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;
+</p> <p>The angular velocity of the earth is set by
+default. The
 values
-of the Coriolis parameters are calculated as:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p>f = 2.0 * <b>omega</b> * sin(<a href="#phi">phi</a>)&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
-f* = 2.0 * <b>omega</b> * cos(<a href="#phi">phi</a>)</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-      <td style="vertical-align: top;">
-      <p><a name="outflow_damping_width"></a><b>outflow_damping_width</b></p>
-      </td>
-      <td style="vertical-align: top;">I</td>
-      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(20,
+of the Coriolis parameters are calculated as:&nbsp; </p> <ul>
+<p>f = 2.0 * <b>omega</b> * sin(<a href="#phi">phi</a>)&nbsp;
+<br>f* = 2.0 * <b>omega</b> * cos(<a href="#phi">phi</a>)</p>
+</ul> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="outflow_damping_width"></a><b>outflow_damping_width</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">MIN(20,
 nx/2</span> or <span style="font-style: italic;">ny/2)</span></td>
-      <td style="vertical-align: top;">Width of
+<td style="vertical-align: top;">Width of
 the damping range in the vicinity of the outflow (gridpoints).<br>
-
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-
+<br>
 When using non-cyclic lateral boundaries (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
 or <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
@@ -9989,1186 +1142,78 @@
 in gridpoints counted from the respective outflow boundary. For further
 details about the smoothing see parameter <a href="chapter_4.1.html#km_damp_max">km_damp_max</a>,
-which defines the magnitude of the damping.</td>
-    </tr>
-<tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_e"></a><b>overshoot_limit_e</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit for the overshooting of subgrid-scale TKE in
+which defines the magnitude of the damping.</td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="overshoot_limit_e"></a><b>overshoot_limit_e</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Allowed limit
+for the overshooting of subgrid-scale TKE in
 case that the upstream-spline scheme is switched on (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By deafult, if cut-off of overshoots is switched on for the
+</p> <p>By deafult, if cut-off of overshoots is switched
+on for the
 upstream-spline scheme (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>),
 no overshoots are permitted at all. If <b>overshoot_limit_e</b>
 is given a non-zero value, overshoots with the respective
 amplitude (both upward and downward) are allowed.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_e</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_pt"></a><b>overshoot_limit_pt</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit for the overshooting of potential temperature in
+<p>Only positive values are allowed for <b>overshoot_limit_e</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="overshoot_limit_pt"></a><b>overshoot_limit_pt</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Allowed limit
+for the overshooting of potential temperature in
 case that the upstream-spline scheme is switched on (in K).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_pt</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_u"></a><b>overshoot_limit_u</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Allowed limit for the
+<p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+</p> <p>Only positive values are allowed for <b>overshoot_limit_pt</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="overshoot_limit_u"></a><b>overshoot_limit_u</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;">Allowed limit for the
 overshooting of
 the u-component of velocity in case that the upstream-spline scheme is
-switched on (in m/s).
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_u</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_v"></a><b>overshoot_limit_v</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit for the overshooting of the v-component of
+switched on (in m/s). <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+</p> <p>Only positive values are allowed for <b>overshoot_limit_u</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="overshoot_limit_v"></a><b>overshoot_limit_v</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Allowed limit
+for the overshooting of the v-component of
 velocity in case that the upstream-spline scheme is switched on
-(in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_v</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_w"></a><b>overshoot_limit_w</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit for the overshooting of the w-component of
+(in m/s).&nbsp; </p> <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+</p> <p>Only positive values are allowed for <b>overshoot_limit_v</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="overshoot_limit_w"></a><b>overshoot_limit_w</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Allowed limit
+for the overshooting of the w-component of
 velocity in case that the upstream-spline scheme is switched on
-(in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>overshoot_limit_w</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="passive_scalar"></a><b>passive_scalar</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch on the prognostic equation for a passive
-scalar. <br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The initial vertical profile of s can be set via parameters <a href="#s_surface">s_surface</a>, <a href="#s_vertical_gradient">s_vertical_gradient</a>
+(in m/s).&nbsp; </p> <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+</p> <p>Only positive values are permitted for <b>overshoot_limit_w</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="passive_scalar"></a><b>passive_scalar</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.F.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+switch on the prognostic equation for a passive
+scalar. <br> </p> <p>The initial vertical profile
+of s can be set via parameters <a href="#s_surface">s_surface</a>,
+<a href="#s_vertical_gradient">s_vertical_gradient</a>
 and&nbsp; <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.
 Boundary conditions can be set via <a href="#s_surface_initial_change">s_surface_initial_change</a>
-and <a href="#surface_scalarflux">surface_scalarflux</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><b>Note:</b> <br>
-
-
-
-
-
-
-
-
-
-
-With <span style="font-weight: bold;">passive_scalar</span> switched
+and <a href="#surface_scalarflux">surface_scalarflux</a>.&nbsp;
+</p> <p><b>Note:</b> <br>
+With <span style="font-weight: bold;">passive_scalar</span>
+switched
 on, the simultaneous use of humidity (see <a href="#moisture">moisture</a>)
-is impossible.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="phi"></a><b>phi</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>55.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Geographical latitude (in degrees).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The value of this parameter determines the value of the
+is impossible.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="phi"></a><b>phi</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>55.0</i></td>
+<td style="vertical-align: top;"> <p>Geographical
+latitude (in degrees).&nbsp; </p> <p>The value of
+this parameter determines the value of the
 Coriolis parameters f and f*, provided that the angular velocity (see <a href="#omega">omega</a>)
-is non-zero.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="prandtl_layer"></a><b>prandtl_layer</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.T.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch on a Prandtl layer.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By default, a Prandtl layer is switched on at the bottom
+is non-zero.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="prandtl_layer"></a><b>prandtl_layer</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.T.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+switch on a Prandtl layer.&nbsp; </p> <p>By default,
+a Prandtl layer is switched on at the bottom
 boundary between z = 0 and z = 0.5 * <a href="#dz">dz</a>
 (the first computational grid point above ground for u, v and the
@@ -11178,624 +1223,56 @@
 are not allowed. Likewise, laminar
 simulations with constant eddy diffusivities (<a href="#km_constant">km_constant</a>)
-are forbidden.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>With Prandtl-layer switched off, the TKE boundary condition <a href="#bc_e_b">bc_e_b</a>
-= '<i>(u*)**2+neumann'</i> must not be used and is automatically
-changed to <i>'neumann'</i> if necessary.&nbsp; Also, the pressure
+are forbidden.&nbsp; </p> <p>With Prandtl-layer
+switched off, the TKE boundary condition <a href="#bc_e_b">bc_e_b</a>
+= '<i>(u*)**2+neumann'</i> must not be used and is
+automatically
+changed to <i>'neumann'</i> if necessary.&nbsp; Also,
+the pressure
 boundary condition <a href="#bc_p_b">bc_p_b</a>
 = <i>'neumann+inhomo'</i>&nbsp; is not allowed. </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The roughness length is declared via the parameter <a href="#roughness_length">roughness_length</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="precipitation"></a><b>precipitation</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch on the precipitation scheme.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For precipitation processes PALM uses a simplified Kessler
+<p>The roughness length is declared via the parameter <a href="#roughness_length">roughness_length</a>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="precipitation"></a><b>precipitation</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td> <td style="vertical-align: top;"> <p>Parameter to switch
+on the precipitation scheme.<br> </p> <p>For
+precipitation processes PALM uses a simplified Kessler
 scheme. This scheme only considers the
 so-called autoconversion, that means the generation of rain water by
 coagulation of cloud drops among themselves. Precipitation begins and
 is immediately removed from the flow as soon as the liquid water
-content exceeds the critical value of 0.5 g/kg.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><a name="pt_reference"></a><span style="font-weight: bold;">pt_reference</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">use horizontal average as refrence</span></td><td style="vertical-align: top;">Reference temperature to be used in all buoyancy terms (in K).<br><br>By default, the instantaneous horizontal average over the total model domain is used.</td></tr><tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_surface"></a><b>pt_surface</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>300.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Surface potential temperature (in K).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This parameter assigns the value of the potential temperature
-pt at the surface (k=0)<b>.</b> Starting from this value, the
+content exceeds the critical value of 0.5 g/kg.</p> </td> </tr>
+<tr><td style="vertical-align: top;"><a name="pt_reference"></a><span style="font-weight: bold;">pt_reference</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">use horizontal average as
+refrence</span></td><td style="vertical-align: top;">Reference
+temperature to be used in all buoyancy terms (in K).<br><br>By
+default, the instantaneous horizontal average over the total model
+domain is used.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="pt_surface"></a><b>pt_surface</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>300.0</i></td>
+<td style="vertical-align: top;"> <p>Surface
+potential temperature (in K).&nbsp; </p> <p>This
+parameter assigns the value of the potential temperature
+pt at the surface (k=0)<b>.</b> Starting from this value,
+the
 initial vertical temperature profile is constructed with <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
-and <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level </a>.
+and <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level
+</a>.
 This profile is also used for the 1d-model as a stationary profile.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_surface_initial_change"></a><b>pt_surface_initial</b>
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>_change</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Change in surface temperature to be made at the beginning of
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pt_surface_initial_change"></a><b>pt_surface_initial</b>
+<br> <b>_change</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
+<td style="vertical-align: top;"> <p>Change in
+surface temperature to be made at the beginning of
 the 3d run
-(in K).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If <b>pt_surface_initial_change</b> is set to a non-zero
+(in K).&nbsp; </p> <p>If <b>pt_surface_initial_change</b>
+is set to a non-zero
 value, the near surface sensible heat flux is not allowed to be given
 simultaneously (see <a href="#surface_heatflux">surface_heatflux</a>).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_vertical_gradient"></a><b>pt_vertical_gradient</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>10 * 0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Temperature gradient(s) of the initial temperature profile (in
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pt_vertical_gradient"></a><b>pt_vertical_gradient</b></p>
+</td> <td style="vertical-align: top;">R (10)</td>
+<td style="vertical-align: top;"><i>10 * 0.0</i></td>
+<td style="vertical-align: top;"> <p>Temperature
+gradient(s) of the initial temperature profile (in
 K
-/ 100 m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This temperature gradient holds starting from the height&nbsp;
+/ 100 m).&nbsp; </p> <p>This temperature gradient
+holds starting from the height&nbsp;
 level defined by <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>
 (precisely: for all uv levels k where zu(k) &gt;
@@ -11806,738 +1283,57 @@
 A total of 10 different gradients for 11 height intervals (10 intervals
 if <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be assigned. The surface temperature is assigned via
-      <a href="#pt_surface">pt_surface</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p><b>pt_vertical_gradient</b> = <i>1.0</i>, <i>0.5</i>,&nbsp;
-        <br>
-
-
-
-
-
-
-
-
-
-
-        <b>pt_vertical_gradient_level</b> = <i>500.0</i>, <i>1000.0</i>,</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>That defines the temperature profile to be neutrally
+= <i>0.0</i>) can be assigned. The surface temperature is
+assigned via <a href="#pt_surface">pt_surface</a>.&nbsp;
+</p> <p>Example:&nbsp; </p> <ul> <p><b>pt_vertical_gradient</b>
+= <i>1.0</i>, <i>0.5</i>,&nbsp; <br>
+<b>pt_vertical_gradient_level</b> = <i>500.0</i>,
+<i>1000.0</i>,</p> </ul> <p>That
+defines the temperature profile to be neutrally
 stratified
 up to z = 500.0 m with a temperature given by <a href="#pt_surface">pt_surface</a>.
-For 500.0 m &lt; z &lt;= 1000.0 m the temperature gradient is 1.0 K /
+For 500.0 m &lt; z &lt;= 1000.0 m the temperature gradient is
+1.0 K /
 100 m and for z &gt; 1000.0 m up to the top boundary it is
 0.5 K / 100 m (it is assumed that the assigned height levels correspond
-with uv levels). </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_vertical_gradient_level"></a><b>pt_vertical_gradient</b>
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>_level</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><i>10 *</i>&nbsp; <span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Height level from which on the temperature gradient defined by
-      <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The height levels are to be assigned in ascending order. The
+with uv levels). </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pt_vertical_gradient_level"></a><b>pt_vertical_gradient</b>
+<br> <b>_level</b></p> </td> <td style="vertical-align: top;">R (10)</td> <td style="vertical-align: top;"> <p><i>10 *</i>&nbsp;
+<span style="font-style: italic;">0.0</span><br>
+</p> </td> <td style="vertical-align: top;">
+<p>Height level from which on the temperature gradient defined by
+<a href="#pt_vertical_gradient">pt_vertical_gradient</a>
+is effective (in m).&nbsp; </p> <p>The height levels
+are to be assigned in ascending order. The
 default values result in a neutral stratification regardless of the
 values of <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
 (unless the top boundary of the model is higher than 100000.0 m).
 For the piecewise construction of temperature profiles see <a href="#pt_vertical_gradient">pt_vertical_gradient</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="q_surface"></a><b>q_surface</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Surface specific humidity / total water content (kg/kg).&nbsp;
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This parameter assigns the value of the specific humidity q at
-the surface (k=0).&nbsp; Starting from this value, the initial humidity
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="q_surface"></a><b>q_surface</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Surface
+specific humidity / total water content (kg/kg).&nbsp; </p> <p>This
+parameter assigns the value of the specific humidity q at
+the surface (k=0).&nbsp; Starting from this value, the initial
+humidity
 profile is constructed with&nbsp; <a href="#q_vertical_gradient">q_vertical_gradient</a>
 and <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>.
 This profile is also used for the 1d-model as a stationary profile.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="q_surface_initial_change"></a><b>q_surface_initial</b>
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>_change</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Change in surface specific humidity / total water content to
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="q_surface_initial_change"></a><b>q_surface_initial</b>
+<br> <b>_change</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Change in
+surface specific humidity / total water content to
 be made at the beginning
-of the 3d run (kg/kg).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If <b>q_surface_initial_change</b><i> </i>is set to a
+of the 3d run (kg/kg).&nbsp; </p> <p>If <b>q_surface_initial_change</b><i>
+</i>is set to a
 non-zero value the
 near surface latent heat flux (water flux) is not allowed to be given
 simultaneously (see <a href="#surface_waterflux">surface_waterflux</a>).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="q_vertical_gradient"></a><b>q_vertical_gradient</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>10 * 0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Humidity gradient(s) of the initial humidity profile
-(in 1/100 m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This humidity gradient holds starting from the height
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="q_vertical_gradient"></a><b>q_vertical_gradient</b></p>
+</td> <td style="vertical-align: top;">R (10)</td>
+<td style="vertical-align: top;"><i>10 * 0.0</i></td>
+<td style="vertical-align: top;"> <p>Humidity
+gradient(s) of the initial humidity profile
+(in 1/100 m).&nbsp; </p> <p>This humidity gradient
+holds starting from the height
 level&nbsp; defined by <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>
 (precisely: for all uv levels k, where zu(k) &gt;
@@ -12548,592 +1344,47 @@
 A total of 10 different gradients for 11 height intervals (10 intervals
 if <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be asigned. The surface humidity is assigned
+= <i>0.0</i>) can be asigned. The surface humidity is
+assigned
 via <a href="#q_surface">q_surface</a>. </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p><b>q_vertical_gradient</b> = <i>0.001</i>, <i>0.0005</i>,&nbsp;
-        <br>
-
-
-
-
-
-
-
-
-
-
-        <b>q_vertical_gradient_level</b> = <i>500.0</i>, <i>1000.0</i>,</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
+<p>Example:&nbsp; </p> <ul> <p><b>q_vertical_gradient</b>
+= <i>0.001</i>, <i>0.0005</i>,&nbsp; <br>
+<b>q_vertical_gradient_level</b> = <i>500.0</i>,
+<i>1000.0</i>,</p> </ul>
 That defines the humidity to be constant with height up to z =
 500.0
 m with a
 value given by <a href="#q_surface">q_surface</a>.
-For 500.0 m &lt; z &lt;= 1000.0 m the humidity gradient is 0.001 / 100
+For 500.0 m &lt; z &lt;= 1000.0 m the humidity gradient is
+0.001 / 100
 m and for z &gt; 1000.0 m up to the top boundary it is
 0.0005 / 100 m (it is assumed that the assigned height levels
 correspond with uv
-levels). </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="q_vertical_gradient_level"></a><b>q_vertical_gradient</b>
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>_level</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Height level from which on the moisture gradient defined by <a href="#q_vertical_gradient">q_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The height levels are to be assigned in ascending order. The
+levels). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="q_vertical_gradient_level"></a><b>q_vertical_gradient</b>
+<br> <b>_level</b></p> </td> <td style="vertical-align: top;">R (10)</td> <td style="vertical-align: top;"> <p><i>10 *</i>&nbsp;
+<i>0.0</i></p> </td> <td style="vertical-align: top;"> <p>Height level from
+which on the moisture gradient defined by <a href="#q_vertical_gradient">q_vertical_gradient</a>
+is effective (in m).&nbsp; </p> <p>The height levels
+are to be assigned in ascending order. The
 default values result in a humidity constant with height regardless of
 the values of <a href="#q_vertical_gradient">q_vertical_gradient</a>
 (unless the top boundary of the model is higher than 100000.0 m). For
 the piecewise construction of humidity profiles see <a href="#q_vertical_gradient">q_vertical_gradient</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="radiation"></a><b>radiation</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch on longwave radiation cooling at
-cloud-tops.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Long-wave radiation processes are parameterized by the
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="radiation"></a><b>radiation</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.F.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+switch on longwave radiation cooling at
+cloud-tops.&nbsp; </p> <p>Long-wave radiation
+processes are parameterized by the
 effective emissivity, which considers only the absorption and emission
 of long-wave radiation at cloud droplets. The radiation scheme can be
 used only with <a href="#cloud_physics">cloud_physics</a>
-= .TRUE. .</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="random_generator"></a><b>random_generator</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><i>'numerical</i><br>
-
-
-
-
-
-
-
-
-
-
-      <i>recipes'</i></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Random number generator to be used for creating uniformly
-distributed random numbers. <br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>It is used if random perturbations are to be imposed on the
+= .TRUE. .</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="random_generator"></a><b>random_generator</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"> <p><i>'numerical</i><br>
+<i>recipes'</i></p> </td> <td style="vertical-align: top;"> <p>Random number
+generator to be used for creating uniformly
+distributed random numbers. <br> </p> <p>It is
+used if random perturbations are to be imposed on the
 velocity field or on the surface heat flux field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>
 and <a href="chapter_4.2.html#random_heatflux">random_heatflux</a>).
@@ -13141,327 +1392,46 @@
 This one provides exactly the same order of random numbers on all
 different machines and should be used in particular for comparison runs.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<br>
 Besides, a system-specific generator is available ( <b>random_generator</b>
-= <i>'system-specific')</i> which should particularly be used for runs
+= <i>'system-specific')</i> which should particularly be
+used for runs
 on vector parallel computers (NEC), because the default generator
 cannot be vectorized and therefore significantly drops down the code
-performance on these machines.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">Note:</span><br>
-
-
-
-
-
-
-
-
-
-
+performance on these machines.<br> </p> <span style="font-weight: bold;">Note:</span><br>
 Results from two otherwise identical model runs will not be comparable
-one-to-one if they used different random number generators.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="random_heatflux"></a><b>random_heatflux</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to impose random perturbations on the internal two-dimensional near surface heat flux field <span style="font-style: italic;">shf</span>. <br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-If a near surface heat flux is used as bottom boundary
+one-to-one if they used different random number generators.</td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="random_heatflux"></a><b>random_heatflux</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.F.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+impose random perturbations on the internal two-dimensional near
+surface heat flux field <span style="font-style: italic;">shf</span>.
+<br> </p>If a near surface heat flux is used as bottom
+boundary
 condition (see <a href="#surface_heatflux">surface_heatflux</a>),
 it is by default assumed to be horizontally homogeneous. Random
-perturbations can be imposed on the internal two-dimensional&nbsp;heat flux field <span style="font-style: italic;">shf</span> by assigning <b>random_heatflux</b>
-= <i>.T.</i>. The disturbed heat flux field is calculated by
+perturbations can be imposed on the internal
+two-dimensional&nbsp;heat flux field <span style="font-style: italic;">shf</span> by assigning <b>random_heatflux</b>
+= <i>.T.</i>. The disturbed heat flux field is calculated
+by
 multiplying the
 values at each mesh point with a normally distributed random number
 with a mean value and standard deviation of 1. This is repeated after
-every timestep.<br>
-
-
-
-      <br>
-
-
-
-
-
-
-In case of a non-flat <a href="#topography">topography</a>,&nbsp;assigning <b>random_heatflux</b>
-= <i>.T.</i> imposes random perturbations on the combined&nbsp;heat
-flux field <span style="font-style: italic;">shf</span> composed of <a href="#surface_heatflux">surface_heatflux</a> at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a> at the topography top face.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="rif_max"></a><b>rif_max</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>1.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Upper limit of the flux-Richardson number.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>With the Prandtl layer switched on (see <a href="#prandtl_layer">prandtl_layer</a>),
-flux-Richardson numbers (rif) are calculated for z=z<sub>p</sub> (k=1)
+every timestep.<br> <br>
+In case of a non-flat <a href="#topography">topography</a>,&nbsp;assigning
+<b>random_heatflux</b>
+= <i>.T.</i> imposes random perturbations on the
+combined&nbsp;heat
+flux field <span style="font-style: italic;">shf</span>
+composed of <a href="#surface_heatflux">surface_heatflux</a>
+at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a>
+at the topography top face.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="rif_max"></a><b>rif_max</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>1.0</i></td>
+<td style="vertical-align: top;"> <p>Upper limit of
+the flux-Richardson number.&nbsp; </p> <p>With the
+Prandtl layer switched on (see <a href="#prandtl_layer">prandtl_layer</a>),
+flux-Richardson numbers (rif) are calculated for z=z<sub>p</sub>
+(k=1)
 in the 3d-model (in the 1d model for all heights). Their values in
 particular determine the
@@ -13469,558 +1439,40 @@
 the eddy diffusivity (1d-model). With small wind velocities at the
 Prandtl layer top or small vertical wind shears in the 1d-model, rif
-can take up unrealistic large values. They are limited by an upper (<span style="font-weight: bold;">rif_max</span>) and lower limit (see <a href="#rif_min">rif_min</a>)
-for the flux-Richardson number. The condition <b>rif_max</b> &gt; <b>rif_min</b>
-must be met.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="rif_min"></a><b>rif_min</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>- 5.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Lower limit of the flux-Richardson number.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>For further explanations see <a href="#rif_max">rif_max</a>.
-The condition <b>rif_max</b> &gt; <b>rif_min </b>must be met.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="roughness_length"></a><b>roughness_length</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.1</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Roughness length (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This parameter is effective only in case that a Prandtl layer
+can take up unrealistic large values. They are limited by an upper (<span style="font-weight: bold;">rif_max</span>) and lower
+limit (see <a href="#rif_min">rif_min</a>)
+for the flux-Richardson number. The condition <b>rif_max</b>
+&gt; <b>rif_min</b>
+must be met.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="rif_min"></a><b>rif_min</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>- 5.0</i></td>
+<td style="vertical-align: top;"> <p>Lower limit of
+the flux-Richardson number.&nbsp; </p> <p>For further
+explanations see <a href="#rif_max">rif_max</a>.
+The condition <b>rif_max</b> &gt; <b>rif_min </b>must
+be met.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="roughness_length"></a><b>roughness_length</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.1</i></td>
+<td style="vertical-align: top;"> <p>Roughness
+length (in m).&nbsp; </p> <p>This parameter is
+effective only in case that a Prandtl layer
 is switched
 on (see <a href="#prandtl_layer">prandtl_layer</a>).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="scalar_advec"></a><b>scalar_advec</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 10</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>'pw-scheme'</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Advection scheme to be used for the scalar quantities.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The user can choose between the following schemes:<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'pw-scheme'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The scheme of Piascek and
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="scalar_advec"></a><b>scalar_advec</b></p>
+</td> <td style="vertical-align: top;">C * 10</td>
+<td style="vertical-align: top;"><i>'pw-scheme'</i></td>
+<td style="vertical-align: top;"> <p>Advection
+scheme to be used for the scalar quantities.&nbsp; </p> <p>The
+user can choose between the following schemes:<br> </p> <p><span style="font-style: italic;">'pw-scheme'</span><br>
+</p> <div style="margin-left: 40px;">The scheme of
+Piascek and
 Williams (1970, J. Comp. Phys., 6,
 392-405) with central differences in the form C3 is used.<br>
-
-
-
-
-
-
-
-
-
-
 If intermediate Euler-timesteps are carried out in case of <a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'leapfrog+euler'</span> the
+= <span style="font-style: italic;">'leapfrog+euler'</span>
+the
 advection scheme is - for the Euler-timestep - automatically switched
-to an upstream-scheme. <br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'bc-scheme'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The Bott scheme modified by
+to an upstream-scheme. <br> </div> <br> <p><span style="font-style: italic;">'bc-scheme'</span><br>
+</p> <div style="margin-left: 40px;">The Bott
+scheme modified by
 Chlond (1994, Mon.
 Wea. Rev., 122, 111-125). This is a conservative monotonous scheme with
@@ -14033,88 +1485,18 @@
 quantities. For output of horizontally averaged
 profiles of the resolved / total heat flux, <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
-= <i>'w*pt*BC'</i> / <i>'wptBC' </i>should be used, instead of the
+= <i>'w*pt*BC'</i> / <i>'wptBC' </i>should
+be used, instead of the
 standard profiles (<span style="font-style: italic;">'w*pt*'</span>
-and <span style="font-style: italic;">'wpt'</span>) because these are
+and <span style="font-style: italic;">'wpt'</span>)
+because these are
 too inaccurate with this scheme. However, for subdomain analysis (see <a href="#statistic_regions">statistic_regions</a>)
 exactly the reverse holds: here <i>'w*pt*BC'</i> and <i>'wptBC'</i>
-show very large errors and should not be used.<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+show very large errors and should not be used.<br> <br>
 This scheme is not allowed for non-cyclic lateral boundary conditions
 (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">'ups-scheme'</span><br>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">The upstream-spline-scheme is used
+and <a href="#bc_ns">bc_ns</a>).<br> <br>
+</div> <span style="font-style: italic;">'ups-scheme'</span><br>
+<p style="margin-left: 40px;">The upstream-spline-scheme
+is used
 (see Mahrer and Pielke,
 1978: Mon. Wea. Rev., 106, 818-830). In opposite to the Piascek
@@ -14124,5 +1506,6 @@
 expensive. In
 addition, the use of the Euler-timestep scheme is mandatory (<a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'</span><i>euler'</i>), i.e. the
+= <span style="font-style: italic;">'</span><i>euler'</i>),
+i.e. the
 timestep accuracy is only first order. For this reason the advection of
 momentum (see <a href="#momentum_advec">momentum_advec</a>)
@@ -14130,91 +1513,19 @@
 because otherwise the momentum would
 be subject to large numerical diffusion due to the upstream
-scheme.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">Since the cubic splines used tend
+scheme.&nbsp; </p> <p style="margin-left: 40px;">Since
+the cubic splines used tend
 to overshoot under
 certain circumstances, this effect must be adjusted by suitable
 filtering and smoothing (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>,
-      <a href="#long_filter_factor">long_filter_factor</a>, <a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>,
-      <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
+<a href="#long_filter_factor">long_filter_factor</a>,
+<a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>, <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
 This is always neccesssary for runs with stable stratification,
 even if this stratification appears only in parts of the model
-domain.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">With stable stratification the
+domain.&nbsp; </p> <p style="margin-left: 40px;">With
+stable stratification the
 upstream-upline scheme also produces gravity waves with large
 amplitude, which must be
 suitably damped (see <a href="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;"><span style="font-weight: bold;">Important:
-      </span>The&nbsp;
+</p> <p style="margin-left: 40px;"><span style="font-weight: bold;">Important: </span>The&nbsp;
 upstream-spline scheme is not implemented for humidity and passive
 scalars (see <a href="#moisture">moisture</a>
@@ -14224,300 +1535,59 @@
 very long execution times! This scheme is also not allowed for
 non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>).</p><br>A differing advection scheme can be choosed for the subgrid-scale TKE using parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="statistic_regions"></a><b>statistic_regions</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Number of additional user-defined subdomains for which
+and <a href="#bc_ns">bc_ns</a>).</p><br>A
+differing advection scheme can be choosed for the subgrid-scale TKE
+using parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>.</td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="statistic_regions"></a><b>statistic_regions</b></p>
+</td> <td style="vertical-align: top;">I</td>
+<td style="vertical-align: top;"><i>0</i></td>
+<td style="vertical-align: top;"> <p>Number of
+additional user-defined subdomains for which
 statistical analysis
-and corresponding output (profiles, time series) shall be made.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By default, vertical profiles and other statistical quantities
+and corresponding output (profiles, time series) shall be
+made.&nbsp; </p> <p>By default, vertical profiles and
+other statistical quantities
 are calculated as horizontal and/or volume average of the total model
 domain. Beyond that, these calculations can also be carried out for
-subdomains which can be defined using the field <a href="chapter_3.5.3.html">rmask </a>within the user-defined software
+subdomains which can be defined using the field <a href="chapter_3.5.3.html">rmask </a>within the
+user-defined software
 (see <a href="chapter_3.5.3.html">chapter
 3.5.3</a>). The number of these subdomains is determined with the
-parameter <b>statistic_regions</b>. Maximum 9 additional subdomains
+parameter <b>statistic_regions</b>. Maximum 9 additional
+subdomains
 are allowed. The parameter <a href="chapter_4.3.html#region">region</a>
 can be used to assigned names (identifier) to these subdomains which
 are then used in the headers
-of the output files and plots.</p><p>If the default NetCDF output format is selected (see parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>), data for the total domain and all defined subdomains are output to the same file(s) (<a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>, <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>). In case of <span style="font-weight: bold;">statistic_regions</span> &gt; <span style="font-style: italic;">0</span>,
+of the output files and plots.</p><p>If the default NetCDF
+output format is selected (see parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>),
+data for the total domain and all defined subdomains are output to the
+same file(s) (<a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>,
+<a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>).
+In case of <span style="font-weight: bold;">statistic_regions</span>
+&gt; <span style="font-style: italic;">0</span>,
 data on the file for the different domains can be distinguished by a
 suffix which is appended to the quantity names. Suffix 0 means data for
-the total domain, suffix 1 means data for subdomain 1, etc.</p><p>In case of <span style="font-weight: bold;">data_output_format</span> = <span style="font-style: italic;">'profil'</span>, individual local files for profiles (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)&nbsp;are created for each subdomain. The individual subdomain files differ by their name (the
+the total domain, suffix 1 means data for subdomain 1, etc.</p><p>In
+case of <span style="font-weight: bold;">data_output_format</span>
+= <span style="font-style: italic;">'profil'</span>,
+individual local files for profiles (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)&nbsp;are
+created for each subdomain. The individual subdomain files differ by
+their name (the
 number of the respective subdomain is attached, e.g.
 PLOT1D_DATA_1). In this case the name of the file with the data of
 the total domain is PLOT1D_DATA_0. If no subdomains
-are declared (<b>statistic_regions</b> = <i>0</i>), the name
+are declared (<b>statistic_regions</b> = <i>0</i>),
+the name
 PLOT1D_DATA is used (this must be considered in the
-respective file connection statements of the <span style="font-weight: bold;">mrun</span> configuration file).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_heatflux"></a><b>surface_heatflux</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
-heatflux<br>
-      </span></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Kinematic sensible heat flux at the bottom surface (in K m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If a value is assigned to this parameter, the internal two-dimensional surface heat flux field <span style="font-style: italic;">shf</span> is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span>&nbsp;as bottom (horizontally homogeneous) boundary condition for the
+respective file connection statements of the <span style="font-weight: bold;">mrun</span> configuration
+file).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="surface_heatflux"></a><b>surface_heatflux</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
+heatflux<br> </span></td> <td style="vertical-align: top;"> <p>Kinematic sensible
+heat flux at the bottom surface (in K m/s).&nbsp; </p> <p>If
+a value is assigned to this parameter, the internal two-dimensional
+surface heat flux field <span style="font-style: italic;">shf</span>
+is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span>&nbsp;as
+bottom (horizontally homogeneous) boundary condition for the
 temperature equation. This additionally requires that a Neumann
 condition must be used for the potential temperature (see <a href="#bc_pt_b">bc_pt_b</a>),
@@ -14527,165 +1597,32 @@
 surface temperature (see <a href="#pt_surface_initial_change">pt_surface_initial_change</a>)
 are not allowed. The parameter <a href="#random_heatflux">random_heatflux</a>
-can be used to impose random perturbations on the (homogeneous) surface heat
+can be used to impose random perturbations on the (homogeneous) surface
+heat
 flux field <span style="font-style: italic;">shf</span>.&nbsp;</p>
-
-
-
-      
-      
-      
-      <p>
-
-
-In case of a non-flat <a href="#topography">topography</a>,&nbsp;the internal two-dimensional&nbsp;surface heat
-flux field <span style="font-style: italic;">shf</span> is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span> at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a> at the topography top face.&nbsp;The parameter<a href="#random_heatflux"> random_heatflux</a>
-can be used to impose random perturbations on this combined surface heat
-flux field <span style="font-style: italic;">shf</span>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If no surface heat flux is assigned, <span style="font-style: italic;">shf</span> is calculated at each timestep by u<sub>*</sub> * theta<sub>*</sub>
-(of course only with <a href="#prandtl_layer">prandtl_layer</a> switched on). Here, u<sub>*</sub>
-and theta<sub>*</sub> are calculated from the Prandtl law assuming
+<p>
+In case of a non-flat <a href="#topography">topography</a>,&nbsp;the
+internal two-dimensional&nbsp;surface heat
+flux field <span style="font-style: italic;">shf</span>
+is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span>
+at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a>
+at the topography top face.&nbsp;The parameter<a href="#random_heatflux"> random_heatflux</a>
+can be used to impose random perturbations on this combined surface
+heat
+flux field <span style="font-style: italic;">shf</span>.&nbsp;
+</p> <p>If no surface heat flux is assigned, <span style="font-style: italic;">shf</span> is calculated
+at each timestep by u<sub>*</sub> * theta<sub>*</sub>
+(of course only with <a href="#prandtl_layer">prandtl_layer</a>
+switched on). Here, u<sub>*</sub>
+and theta<sub>*</sub> are calculated from the Prandtl law
+assuming
 logarithmic wind and temperature
 profiles between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_pt_b">bc_pt_b</a>)
-must be used as bottom boundary condition for the potential temperature.</p><p>See also <a href="#top_heatflux">top_heatflux</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_pressure"></a><b>surface_pressure</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>1013.25</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Atmospheric pressure at the surface (in hPa).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
+must be used as bottom boundary condition for the potential temperature.</p><p>See
+also <a href="#top_heatflux">top_heatflux</a>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="surface_pressure"></a><b>surface_pressure</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>1013.25</i></td>
+<td style="vertical-align: top;"> <p>Atmospheric
+pressure at the surface (in hPa).&nbsp; </p>
 Starting from this surface value, the vertical pressure
 profile is calculated once at the beginning of the run assuming a
@@ -14694,127 +1631,15 @@
 converting between the liquid water potential temperature and the
 potential temperature (see <a href="#cloud_physics">cloud_physics</a><span style="text-decoration: underline;"></span>).</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_scalarflux"></a><b>surface_scalarflux</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Scalar flux at the surface (in kg/(m<sup>2</sup> s)).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If a non-zero value is assigned to this parameter, the
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="surface_scalarflux"></a><b>surface_scalarflux</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Scalar flux at
+the surface (in kg/(m<sup>2</sup> s)).&nbsp; </p>
+<p>If a non-zero value is assigned to this parameter, the
 respective scalar flux value is used
 as bottom (horizontally homogeneous) boundary condition for the scalar
-concentration equation.&nbsp;This additionally requires that a Neumann
+concentration equation.&nbsp;This additionally requires that a
+Neumann
 condition must be used for the scalar concentration&nbsp;(see <a href="#bc_s_b">bc_s_b</a>),
 because otherwise the resolved scale may contribute to
@@ -14822,37 +1647,6 @@
 changes of the
 surface scalar concentration (see <a href="#s_surface_initial_change">s_surface_initial_change</a>)
-are not allowed. <br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If no surface scalar flux is assigned (<b>surface_scalarflux</b>
+are not allowed. <br> </p> <p>If no surface scalar
+flux is assigned (<b>surface_scalarflux</b>
 = <i>0.0</i>),
 it is calculated at each timestep by u<sub>*</sub> * s<sub>*</sub>
@@ -14862,135 +1656,10 @@
 profile between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_s_b">bc_s_b</a>)
 must be used as bottom boundary condition for the scalar concentration.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_waterflux"></a><b>surface_waterflux</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Kinematic water flux near the surface (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If a non-zero value is assigned to this parameter, the
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="surface_waterflux"></a><b>surface_waterflux</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Kinematic
+water flux near the surface (in m/s).&nbsp; </p> <p>If
+a non-zero value is assigned to this parameter, the
 respective water flux value is used
 as bottom (horizontally homogeneous) boundary condition for the
@@ -15002,37 +1671,6 @@
 changes of the
 surface humidity (see <a href="#q_surface_initial_change">q_surface_initial_change</a>)
-are not allowed.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If no surface water flux is assigned (<b>surface_waterflux</b>
+are not allowed.<br> </p> <p>If no surface water
+flux is assigned (<b>surface_waterflux</b>
 = <i>0.0</i>),
 it is calculated at each timestep by u<sub>*</sub> * q<sub>*</sub>
@@ -15041,718 +1679,63 @@
 profile between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_q_b">bc_q_b</a>)
 must be used as the bottom boundary condition for the humidity.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="s_surface"></a><b>s_surface</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Surface value of the passive scalar (in kg/m<sup>3</sup>).&nbsp;<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="s_surface"></a><b>s_surface</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Surface value
+of the passive scalar (in kg/m<sup>3</sup>).&nbsp;<br>
+</p>
 This parameter assigns the value of the passive scalar s at
 the surface (k=0)<b>.</b> Starting from this value, the
 initial vertical scalar concentration profile is constructed with<a href="#s_vertical_gradient">
 s_vertical_gradient</a> and <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="s_surface_initial_change"></a><b>s_surface_initial</b>
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>_change</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Change in surface scalar concentration to be made at the
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="s_surface_initial_change"></a><b>s_surface_initial</b>
+<br> <b>_change</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Change in
+surface scalar concentration to be made at the
 beginning of the 3d run (in kg/m<sup>3</sup>).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If <b>s_surface_initial_change</b><i>&nbsp;</i>is set to a
+<p>If <b>s_surface_initial_change</b><i>&nbsp;</i>is
+set to a
 non-zero
 value, the near surface scalar flux is not allowed to be given
 simultaneously (see <a href="#surface_scalarflux">surface_scalarflux</a>).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="s_vertical_gradient"></a><b>s_vertical_gradient</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>10 * 0</i><i>.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Scalar concentration gradient(s) of the initial scalar
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="s_vertical_gradient"></a><b>s_vertical_gradient</b></p>
+</td> <td style="vertical-align: top;">R (10)</td>
+<td style="vertical-align: top;"><i>10 * 0</i><i>.0</i></td>
+<td style="vertical-align: top;"> <p>Scalar
+concentration gradient(s) of the initial scalar
 concentration profile (in kg/m<sup>3 </sup>/
-100 m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The scalar gradient holds starting from the height level
+100 m).&nbsp; </p> <p>The scalar gradient holds
+starting from the height level
 defined by <a href="#s_vertical_gradient_level">s_vertical_gradient_level
-      </a>(precisely: for all uv levels k, where zu(k) &gt;
+</a>(precisely: for all uv levels k, where zu(k) &gt;
 s_vertical_gradient_level, s_init(k) is set: s_init(k) = s_init(k-1) +
-dzu(k) * <b>s_vertical_gradient</b>) up to the top boundary or up to
+dzu(k) * <b>s_vertical_gradient</b>) up to the top
+boundary or up to
 the next height level defined by <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.
 A total of 10 different gradients for 11 height intervals (10 intervals
 if <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be assigned. The surface scalar value is assigned
-via <a href="#s_surface">s_surface</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        
-        <p><b>s_vertical_gradient</b> = <i>0.1</i>, <i>0.05</i>,&nbsp;
-        <br>
-
-
-
-
-
-
-
-
-
-
-        <b>s_vertical_gradient_level</b> = <i>500.0</i>, <i>1000.0</i>,</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>That defines the scalar concentration to be constant with
+= <i>0.0</i>) can be assigned. The surface scalar value is
+assigned
+via <a href="#s_surface">s_surface</a>.<br> </p>
+<p>Example:&nbsp; </p> <ul> <p><b>s_vertical_gradient</b>
+= <i>0.1</i>, <i>0.05</i>,&nbsp; <br>
+<b>s_vertical_gradient_level</b> = <i>500.0</i>,
+<i>1000.0</i>,</p> </ul> <p>That
+defines the scalar concentration to be constant with
 height up to z = 500.0 m with a value given by <a href="#s_surface">s_surface</a>.
 For 500.0 m &lt; z &lt;= 1000.0 m the scalar gradient is 0.1
-kg/m<sup>3 </sup>/ 100 m and for z &gt; 1000.0 m up to the top
-boundary it is 0.05 kg/m<sup>3 </sup>/ 100 m (it is assumed that the
+kg/m<sup>3 </sup>/ 100 m and for z &gt; 1000.0 m up to
+the top
+boundary it is 0.05 kg/m<sup>3 </sup>/ 100 m (it is
+assumed that the
 assigned height levels
 correspond with uv
-levels).</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="s_vertical_gradient_level"></a><b>s_vertical_gradient_</b>
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <b>level</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><i>10 *</i> <i>0.0</i></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Height level from which on the scalar gradient defined by <a href="#s_vertical_gradient">s_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The height levels are to be assigned in ascending order. The
+levels).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="s_vertical_gradient_level"></a><b>s_vertical_gradient_</b>
+<br> <b>level</b></p> </td> <td style="vertical-align: top;">R (10)</td> <td style="vertical-align: top;"> <p><i>10 *</i>
+<i>0.0</i></p> </td> <td style="vertical-align: top;"> <p>Height level from
+which on the scalar gradient defined by <a href="#s_vertical_gradient">s_vertical_gradient</a>
+is effective (in m).&nbsp; </p> <p>The height levels
+are to be assigned in ascending order. The
 default values result in a scalar concentration constant with height
 regardless of the values of <a href="#s_vertical_gradient">s_vertical_gradient</a>
@@ -15760,397 +1743,24 @@
 the
 piecewise construction of scalar concentration profiles see <a href="#s_vertical_gradient">s_vertical_gradient</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="timestep_scheme"></a><b>timestep_scheme</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><i>'runge</i><br>
-
-
-
-
-
-
-
-
-
-
-      <i>kutta-3'</i></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Time step scheme to be used for the integration of the prognostic
-variables.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The user can choose between the following schemes:<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'runge-kutta-3'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Third order Runge-Kutta scheme.<br>
-
-
-
-
-
-
-
-
-
-
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="timestep_scheme"></a><b>timestep_scheme</b></p>
+</td> <td style="vertical-align: top;">C * 20</td>
+<td style="vertical-align: top;"> <p><i>'runge</i><br>
+<i>kutta-3'</i></p> </td> <td style="vertical-align: top;"> <p>Time step scheme to
+be used for the integration of the prognostic
+variables.&nbsp; </p> <p>The user can choose between
+the following schemes:<br> </p> <p><span style="font-style: italic;">'runge-kutta-3'</span><br>
+</p> <div style="margin-left: 40px;">Third order
+Runge-Kutta scheme.<br>
 This scheme requires the use of <a href="#momentum_advec">momentum_advec</a>
 = <a href="#scalar_advec">scalar_advec</a>
-= '<i>pw-scheme'</i>. Please refer to the&nbsp;<a href="../tec/numerik.heiko/zeitschrittverfahren.pdf">documentation on PALM's time integration schemes&nbsp;(28p., in German)</a> fur further details.<br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'runge-kutta-2'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Second order Runge-Kutta scheme.<br>
-
-
-
-
-
-
-
-
-
-
+= '<i>pw-scheme'</i>. Please refer to the&nbsp;<a href="../tec/numerik.heiko/zeitschrittverfahren.pdf">documentation
+on PALM's time integration schemes&nbsp;(28p., in German)</a>
+fur further details.<br> </div> <p><span style="font-style: italic;">'runge-kutta-2'</span><br>
+</p> <div style="margin-left: 40px;">Second order
+Runge-Kutta scheme.<br>
 For special features see <b>timestep_scheme</b> = '<i>runge-kutta-3'</i>.<br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;"><span style="font-style: italic;">'leapfrog'</span><br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      </span>
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Second order leapfrog scheme.<br>
-
-
-
-
-
-
-
-
-
-
+</div> <br> <span style="font-style: italic;"><span style="font-style: italic;">'leapfrog'</span><br>
+<br> </span> <div style="margin-left: 40px;">Second
+order leapfrog scheme.<br>
 Although this scheme requires a constant timestep (because it is
 centered in time),&nbsp; is even applied in case of changes in
@@ -16163,84 +1773,11 @@
 with the Euler scheme, although the leapfrog scheme is switched
 on.&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
 The leapfrog scheme must not be used together with the upstream-spline
 scheme for calculating the advection (see <a href="#scalar_advec">scalar_advec</a>
 = '<i>ups-scheme'</i> and <a href="#momentum_advec">momentum_advec</a>
-= '<i>ups-scheme'</i>).<br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">'</span><span style="font-style: italic;"><span style="font-style: italic;">leapfrog+euler'</span><br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      </span>
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The leapfrog scheme is used, but
+= '<i>ups-scheme'</i>).<br> </div> <br>
+<span style="font-style: italic;">'</span><span style="font-style: italic;"><span style="font-style: italic;">leapfrog+euler'</span><br>
+<br> </span> <div style="margin-left: 40px;">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
@@ -16248,622 +1785,72 @@
 velocity field (after applying the pressure solver) may be
 significantly larger than with <span style="font-style: italic;">'leapfrog'</span>.<br>
-
-
-
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;">'euler'</span><br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">First order Euler scheme.&nbsp; <br>
-
-
-
-
-
-
-
-
-
-
+</div> <br> <span style="font-style: italic;">'euler'</span><br>
+<br> <div style="margin-left: 40px;">First order
+Euler scheme.&nbsp; <br>
 The Euler scheme must be used when treating the advection terms with
 the upstream-spline scheme (see <a href="#scalar_advec">scalar_advec</a>
-= <span style="font-style: italic;">'ups-scheme'</span> and <a href="#momentum_advec">momentum_advec</a>
+= <span style="font-style: italic;">'ups-scheme'</span>
+and <a href="#momentum_advec">momentum_advec</a>
 = <span style="font-style: italic;">'ups-scheme'</span>).</div>
-
-
-
-
-
-
-
-
-
-
-      <br><br>A differing timestep scheme can be choosed for the subgrid-scale TKE using parameter <a href="#use_upstream_for_tke">use_upstream_for_tke</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-      <td style="text-align: left; vertical-align: top;"><span style="font-weight: bold;"><a name="topography"></a></span><span style="font-weight: bold;">topography</span></td>
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 40</td>
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'flat'</span></td>
-
-
-
-
-
-
-
-
-
-      <td>
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Topography mode.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The user can choose between the following modes:<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'flat'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flat surface.</div>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'single_building'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flow around&nbsp;a single rectangular building mounted on a flat surface.<br>
+<br><br>A differing timestep scheme can be choosed for the
+subgrid-scale TKE using parameter <a href="#use_upstream_for_tke">use_upstream_for_tke</a>.<br>
+</td> </tr> <tr> <td style="text-align: left; vertical-align: top;"><span style="font-weight: bold;"><a name="topography"></a></span><span style="font-weight: bold;">topography</span></td>
+<td style="vertical-align: top;">C * 40</td> <td style="vertical-align: top;"><span style="font-style: italic;">'flat'</span></td> <td>
+<p>Topography mode.&nbsp; </p> <p>The user can
+choose between the following modes:<br> </p> <p><span style="font-style: italic;">'flat'</span><br> </p>
+<div style="margin-left: 40px;">Flat surface.</div> <p><span style="font-style: italic;">'single_building'</span><br>
+</p> <div style="margin-left: 40px;">Flow
+around&nbsp;a single rectangular building mounted on a flat surface.<br>
 The building size and location can be specified with the parameters <a href="#building_height">building_height</a>, <a href="#building_length_x">building_length_x</a>, <a href="#building_length_y">building_length_y</a>, <a href="#building_wall_left">building_wall_left</a> and <a href="#building_wall_south">building_wall_south</a>.</div>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;"></span>
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'read_from_file'</span><br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flow around arbitrary topography.<br>
-This mode requires the input file <a href="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</a><font color="#000000">. This file contains </font><font color="#000000"><font color="#000000">the&nbsp;</font></font><font color="#000000">arbitrary topography </font><font color="#000000"><font color="#000000">height information</font></font><font color="#000000"> in m. These data&nbsp;<span style="font-style: italic;"></span>must exactly match the horizontal grid.</font>
-
-
-
-
-
-
-
-
- 
-      </div>
-
-
-
-
-
-
-
-
-
-
-      <span style="font-style: italic;"><br>
-
-
-
-
-
-
-
-
-
-      </span><font color="#000000">
-Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a> to allow further topography modes.<br>
-
-
-
-
-
-
-
-
-      <br>
-All non-flat <span style="font-weight: bold;">topography</span> modes </font>require the use of <a href="#momentum_advec">momentum_advec</a>
+<span style="font-style: italic;"></span> <p><span style="font-style: italic;">'read_from_file'</span><br>
+</p> <div style="margin-left: 40px;">Flow around
+arbitrary topography.<br>
+This mode requires the input file <a href="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</a><font color="#000000">. This file contains </font><font color="#000000"><font color="#000000">the&nbsp;</font></font><font color="#000000">arbitrary topography </font><font color="#000000"><font color="#000000">height
+information</font></font><font color="#000000">
+in m. These data&nbsp;<span style="font-style: italic;"></span>must
+exactly match the horizontal grid.</font> </div> <span style="font-style: italic;"><br> </span><font color="#000000">
+Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a>
+to allow further topography modes.<br> <br>
+All non-flat <span style="font-weight: bold;">topography</span>
+modes </font>require the use of <a href="#momentum_advec">momentum_advec</a>
 = <a href="#scalar_advec">scalar_advec</a>
-= '<i>pw-scheme'</i>, <a href="chapter_4.2.html#psolver">psolver</a> = <i>'poisfft'</i> or '<i>poisfft_hybrid'</i>, <i>&nbsp;</i><a href="#alpha_surface">alpha_surface</a> = 0.0, <a href="#bc_lr">bc_lr</a> = <a href="#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>,&nbsp;<a style="" href="#galilei_transformation">galilei_transformation</a> = <span style="font-style: italic;">.F.</span>,&nbsp;<a href="#cloud_physics">cloud_physics&nbsp;</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#moisture">moisture</a> = <span style="font-style: italic;">.F.</span>, and <a href="#prandtl_layer">prandtl_layer</a> = .T..<br>
-      <font color="#000000"><br>
-
-
-
-
-
-
-
-
-Note that an inclined model domain requires the use of <span style="font-weight: bold;">topography</span> = <span style="font-style: italic;">'flat'</span> and a nonzero </font><a href="#alpha_surface">alpha_surface</a>.</td>
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><a name="top_heatflux"></a><span style="font-weight: bold;">top_heatflux</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
-heatflux</span></td><td style="vertical-align: top;"><p>Kinematic sensible heat flux at the top boundary (in K m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>If a value is assigned to this parameter, the internal two-dimensional surface heat flux field <span style="font-family: monospace;">tswst</span> is initialized with the value of <span style="font-weight: bold;">top_heatflux</span>&nbsp;as top (horizontally homogeneous) boundary condition for the
+= '<i>pw-scheme'</i>, <a href="chapter_4.2.html#psolver">psolver</a>
+= <i>'poisfft'</i> or '<i>poisfft_hybrid'</i>,
+<i>&nbsp;</i><a href="#alpha_surface">alpha_surface</a>
+= 0.0, <a href="#bc_lr">bc_lr</a> = <a href="#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>,&nbsp;<a style="" href="#galilei_transformation">galilei_transformation</a>
+= <span style="font-style: italic;">.F.</span>,&nbsp;<a href="#cloud_physics">cloud_physics&nbsp;</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#moisture">moisture</a> = <span style="font-style: italic;">.F.</span>, and <a href="#prandtl_layer">prandtl_layer</a> = .T..<br>
+<font color="#000000"><br>
+Note that an inclined model domain requires the use of <span style="font-weight: bold;">topography</span> = <span style="font-style: italic;">'flat'</span> and a
+nonzero </font><a href="#alpha_surface">alpha_surface</a>.</td>
+</tr> <tr><td style="vertical-align: top;"><a name="top_heatflux"></a><span style="font-weight: bold;">top_heatflux</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
+heatflux</span></td><td style="vertical-align: top;"><p>Kinematic
+sensible heat flux at the top boundary (in K m/s).&nbsp; </p>
+<p>If a value is assigned to this parameter, the internal
+two-dimensional surface heat flux field <span style="font-family: monospace;">tswst</span> is
+initialized with the value of <span style="font-weight: bold;">top_heatflux</span>&nbsp;as
+top (horizontally homogeneous) boundary condition for the
 temperature equation. This additionally requires that a Neumann
 condition must be used for the potential temperature (see <a href="chapter_4.1.html#bc_pt_t">bc_pt_t</a>),
 because otherwise the resolved scale may contribute to
 the top flux so that a constant value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-
-
-
-      
-      
-      
-      <p><span style="font-weight: bold;">Note:</span><br>The application of a top heat flux additionally requires the setting of initial parameter <a href="#use_top_fluxes">use_top_fluxes</a> = .T..<span style="font-style: italic;"></span><span style="font-weight: bold;"></span> </p><p>No Prandtl-layer is available at the top boundary so far.</p><p>See also <a href="#surface_heatflux">surface_heatflux</a>.</p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      </td></tr><tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ug_surface"></a><span style="font-weight: bold;">ug_surface</span></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">u-component of the geostrophic
-wind at the surface (in m/s).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<p><span style="font-weight: bold;">Note:</span><br>The
+application of a top heat flux additionally requires the setting of
+initial parameter <a href="#use_top_fluxes">use_top_fluxes</a>
+= .T..<span style="font-style: italic;"></span><span style="font-weight: bold;"></span> </p><p>No
+Prandtl-layer is available at the top boundary so far.</p><p>See
+also <a href="#surface_heatflux">surface_heatflux</a>.</p>
+</td></tr><tr> <td style="vertical-align: top;">
+<p><a name="ug_surface"></a><span style="font-weight: bold;">ug_surface</span></p>
+</td> <td style="vertical-align: top;">R<br> </td>
+<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
+<td style="vertical-align: top;">u-component of the
+geostrophic
+wind at the surface (in m/s).<br> <br>
 This parameter assigns the value of the u-component of the geostrophic
 wind (ug) at the surface (k=0). Starting from this value, the initial
 vertical profile of the <br>
-
-
-
-
-
-
-
-
-
-
-u-component of the geostrophic wind is constructed with <a href="#ug_vertical_gradient">ug_vertical_gradient</a> and <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>. The
+u-component of the geostrophic wind is constructed with <a href="#ug_vertical_gradient">ug_vertical_gradient</a>
+and <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>.
+The
 profile constructed in that way is used for creating the initial
 vertical velocity profile of the 3d-model. Either it is applied, as it
@@ -16871,608 +1858,56 @@
 = 'set_constant_profiles') or it is used for calculating a stationary
 boundary layer wind profile (<a href="#initializing_actions">initializing_actions</a>
-= 'set_1d-model_profiles'). If ug is constant with height (i.e. ug(k)=<span style="font-weight: bold;">ug_surface</span>) and&nbsp; has a large
+= 'set_1d-model_profiles'). If ug is constant with height (i.e. ug(k)=<span style="font-weight: bold;">ug_surface</span>)
+and&nbsp; has a large
 value, it is recommended to use a Galilei-transformation of the
 coordinate system, if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
-in order to obtain larger time steps.<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ug_vertical_gradient"></a><span style="font-weight: bold;">ug_vertical_gradient</span></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Gradient(s) of the initial
-profile of the&nbsp; u-component of the geostrophic wind (in 1/100s).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+in order to obtain larger time steps.<br> </td> </tr>
+<tr> <td style="vertical-align: top;"> <p><a name="ug_vertical_gradient"></a><span style="font-weight: bold;">ug_vertical_gradient</span></p>
+</td> <td style="vertical-align: top;">R(10)<br>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br> </td> <td style="vertical-align: top;">Gradient(s) of the initial
+profile of the&nbsp; u-component of the geostrophic wind (in
+1/100s).<br> <br>
 The gradient holds starting from the height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>
 (precisely: for all uv levels k where zu(k) &gt; <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>,
-ug(k) is set: ug(k) = ug(k-1) + dzu(k) * <span style="font-weight: bold;">ug_vertical_gradient</span>) up to the top
-boundary or up to the next height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>. A
+ug(k) is set: ug(k) = ug(k-1) + dzu(k) * <span style="font-weight: bold;">ug_vertical_gradient</span>)
+up to the top
+boundary or up to the next height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>.
+A
 total of 10 different gradients for 11 height intervals (10
 intervals&nbsp; if <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>(1)
-= 0.0) can be assigned. The surface geostrophic wind is assigned by <a href="#ug_surface">ug_surface</a>. <br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ug_vertical_gradient_level"></a><span style="font-weight: bold;">ug_vertical_gradient_level</span></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Height level from which on the
+= 0.0) can be assigned. The surface geostrophic wind is assigned by <a href="#ug_surface">ug_surface</a>. <br> </td>
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="ug_vertical_gradient_level"></a><span style="font-weight: bold;">ug_vertical_gradient_level</span></p>
+</td> <td style="vertical-align: top;">R(10)<br>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br> </td> <td style="vertical-align: top;">Height level from which on the
 gradient defined by <a href="#ug_vertical_gradient">ug_vertical_gradient</a>
-is effective (in m).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+is effective (in m).<br> <br>
 The height levels are to be assigned in ascending order. For the
 piecewise construction of a profile of the u-component of the
 geostrophic wind component (ug) see <a href="#ug_vertical_gradient">ug_vertical_gradient</a>.<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_e"></a><b>ups_limit_e</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Subgrid-scale turbulent kinetic energy difference used as
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="ups_limit_e"></a><b>ups_limit_e</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Subgrid-scale
+turbulent kinetic energy difference used as
 criterion for applying the upstream scheme when upstream-spline
 advection is switched on (in m<sup>2</sup>/s<sup>2</sup>).
-&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
+&nbsp; </p> <p>This variable steers the appropriate
+treatment of the
 advection of the subgrid-scale turbulent kinetic energy in case that
 the uptream-spline scheme is used . For further information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>ups_limit_e</b>. </p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_pt"></a><b>ups_limit_pt</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Temperature difference used as criterion for applying&nbsp;
-the upstream scheme when upstream-spline advection&nbsp; is switched on
-(in K).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This criterion is used if the upstream-spline scheme is
+<p>Only positive values are allowed for <b>ups_limit_e</b>.
+</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="ups_limit_pt"></a><b>ups_limit_pt</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Temperature
+difference used as criterion for applying&nbsp;
+the upstream scheme when upstream-spline advection&nbsp; is
+switched on
+(in K).&nbsp; </p> <p>This criterion is used if the
+upstream-spline scheme is
 switched on (see <a href="#scalar_advec">scalar_advec</a>).<br>
-
-
-
-
-
-
-
-
-
-
 If, for a given gridpoint, the absolute temperature difference with
 respect to the upstream
@@ -17487,1037 +1922,118 @@
 the upstream scheme. The numerical diffusion caused by the upstream
 schme remains small as long as the upstream gradients are small.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The percentage of grid points for which the upstream
+</p> <p>The percentage of grid points for which the
+upstream
 scheme is actually used, can be output as a time series with respect to
 the
-three directions in space with run parameter (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>, the timeseries names in the NetCDF file are <i>'splptx'</i>, <i>'splpty'</i>, <i>'splptz'</i>). The percentage
-of gridpoints&nbsp; should stay below a certain limit, however, it is
+three directions in space with run parameter (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>, the
+timeseries names in the NetCDF file are <i>'splptx'</i>, <i>'splpty'</i>,
+<i>'splptz'</i>). The percentage
+of gridpoints&nbsp; should stay below a certain limit, however, it
+is
 not possible to give
 a general limit, since it depends on the respective flow.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_pt</b>.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
+<p>Only positive values are permitted for <b>ups_limit_pt</b>.<br>
+</p>
 A more effective control of
-the &ldquo;overshoots&rdquo; can be achieved with parameter <a href="#cut_spline_overshoot">cut_spline_overshoot</a>. </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_u"></a><b>ups_limit_u</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Velocity difference (u-component) used as criterion for
+the &ldquo;overshoots&rdquo; can be achieved with parameter <a href="#cut_spline_overshoot">cut_spline_overshoot</a>.
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="ups_limit_u"></a><b>ups_limit_u</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Velocity
+difference (u-component) used as criterion for
 applying the upstream scheme
 when upstream-spline advection is switched on (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
+<p>This variable steers the appropriate treatment of the
 advection of the u-velocity-component in case that the upstream-spline
 scheme is used. For further
-information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_u</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_v"></a><b>ups_limit_v</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Velocity difference (v-component) used as criterion for
+information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp;
+</p> <p>Only positive values are permitted for <b>ups_limit_u</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="ups_limit_v"></a><b>ups_limit_v</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Velocity
+difference (v-component) used as criterion for
 applying the upstream scheme
 when upstream-spline advection is switched on (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
+<p>This variable steers the appropriate treatment of the
 advection of the v-velocity-component in case that the upstream-spline
 scheme is used. For further
-information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_v</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_w"></a><b>ups_limit_w</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Velocity difference (w-component) used as criterion for
+information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp;
+</p> <p>Only positive values are permitted for <b>ups_limit_v</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="ups_limit_w"></a><b>ups_limit_w</b></p>
+</td> <td style="vertical-align: top;">R</td>
+<td style="vertical-align: top;"><i>0.0</i></td>
+<td style="vertical-align: top;"> <p>Velocity
+difference (w-component) used as criterion for
 applying the upstream scheme
 when upstream-spline advection is switched on (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
+<p>This variable steers the appropriate treatment of the
 advection of the w-velocity-component in case that the upstream-spline
 scheme is used. For further
-information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_w</b>.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="use_surface_fluxes"></a><b>use_surface_fluxes</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to steer the treatment of the subgrid-scale vertical
-fluxes within the diffusion terms at k=1 (bottom boundary).<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>By default, the near-surface subgrid-scale fluxes are
+information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp;
+</p> <p>Only positive values are permitted for <b>ups_limit_w</b>.</p>
+</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="use_surface_fluxes"></a><b>use_surface_fluxes</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.F.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+steer the treatment of the subgrid-scale vertical
+fluxes within the diffusion terms at k=1 (bottom boundary).<br> </p>
+<p>By default, the near-surface subgrid-scale fluxes are
 parameterized (like in the remaining model domain) using the gradient
 approach. If <b>use_surface_fluxes</b>
-= <i>.TRUE.</i>, the user-assigned surface fluxes are used instead
-(see <a href="#surface_heatflux">surface_heatflux</a>, <a href="#surface_waterflux">surface_waterflux</a>
-and <a href="#surface_scalarflux">surface_scalarflux</a>) <span style="font-weight: bold;">or</span> the surface fluxes are
+= <i>.TRUE.</i>, the user-assigned surface fluxes are used
+instead
+(see <a href="#surface_heatflux">surface_heatflux</a>,
+<a href="#surface_waterflux">surface_waterflux</a>
+and <a href="#surface_scalarflux">surface_scalarflux</a>)
+<span style="font-weight: bold;">or</span> the
+surface fluxes are
 calculated via the Prandtl layer relation (depends on the bottom
-boundary conditions, see <a href="#bc_pt_b">bc_pt_b</a>, <a href="#bc_q_b">bc_q_b</a>
-and <a href="#bc_s_b">bc_s_b</a>).<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><b>use_surface_fluxes</b>
-is automatically set <i>.TRUE.</i>, if a Prandtl layer is used (see <a href="#prandtl_layer">prandtl_layer</a>).&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>The user may prescribe the surface fluxes at the bottom
-boundary without using a Prandtl layer by setting <span style="font-weight: bold;">use_surface_fluxes</span> = <span style="font-style: italic;">.T.</span> and <span style="font-weight: bold;">prandtl_layer</span> = <span style="font-style: italic;">.F.</span>. If , in this case, the
-momentum flux (u<sub>*</sub><sup>2</sup>) should also be prescribed,
+boundary conditions, see <a href="#bc_pt_b">bc_pt_b</a>,
+<a href="#bc_q_b">bc_q_b</a>
+and <a href="#bc_s_b">bc_s_b</a>).<br> </p>
+<p><b>use_surface_fluxes</b>
+is automatically set <i>.TRUE.</i>, if a Prandtl layer is
+used (see <a href="#prandtl_layer">prandtl_layer</a>).&nbsp;
+</p> <p>The user may prescribe the surface fluxes at the
+bottom
+boundary without using a Prandtl layer by setting <span style="font-weight: bold;">use_surface_fluxes</span> =
+<span style="font-style: italic;">.T.</span> and <span style="font-weight: bold;">prandtl_layer</span> = <span style="font-style: italic;">.F.</span>. If , in this
+case, the
+momentum flux (u<sub>*</sub><sup>2</sup>)
+should also be prescribed,
 the user must assign an appropriate value within the user-defined code.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><a name="use_top_fluxes"></a><span style="font-weight: bold;">use_top_fluxes</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td><td style="vertical-align: top;">
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to steer the treatment of the subgrid-scale vertical
-fluxes within the diffusion terms at k=nz (top boundary).</p><p>By default, the fluxes at nz are calculated using the gradient approach. If <b>use_top_fluxes</b>
-= <i>.TRUE.</i>, the user-assigned top fluxes are used instead
-(see <a href="chapter_4.1.html#top_heatflux">top_heatflux</a>).</p><p>Currently, only a value for the sensible heatflux can be assigned. In case of <span style="font-weight: bold;">use_top_fluxes</span> = <span style="font-style: italic;">.TRUE.</span>, the latent heat flux at the top will be automatically set to zero.</p></td></tr><tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="use_ug_for_galilei_tr"></a><b>use_ug_for_galilei_tr</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.T.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Switch to determine the translation velocity in case that a
-Galilean transformation is used.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>In case of a Galilean transformation (see <a href="#galilei_transformation">galilei_transformation</a>), <b>use_ug_for_galilei_tr</b>
+</td> </tr> <tr><td style="vertical-align: top;"><a name="use_top_fluxes"></a><span style="font-weight: bold;">use_top_fluxes</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td><td style="vertical-align: top;"> <p>Parameter to steer
+the treatment of the subgrid-scale vertical
+fluxes within the diffusion terms at k=nz (top boundary).</p><p>By
+default, the fluxes at nz are calculated using the gradient approach.
+If <b>use_top_fluxes</b>
+= <i>.TRUE.</i>, the user-assigned top fluxes are used
+instead
+(see <a href="chapter_4.1.html#top_heatflux">top_heatflux</a>).</p><p>Currently,
+only a value for the sensible heatflux can be assigned. In case of <span style="font-weight: bold;">use_top_fluxes</span> = <span style="font-style: italic;">.TRUE.</span>, the latent
+heat flux at the top will be automatically set to zero.</p></td></tr><tr>
+<td style="vertical-align: top;"> <p><a name="use_ug_for_galilei_tr"></a><b>use_ug_for_galilei_tr</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.T.</i></td>
+<td style="vertical-align: top;"> <p>Switch to
+determine the translation velocity in case that a
+Galilean transformation is used.<br> </p> <p>In
+case of a Galilean transformation (see <a href="#galilei_transformation">galilei_transformation</a>),
+<b>use_ug_for_galilei_tr</b>
 = <i>.T.</i>&nbsp; ensures
 that the coordinate system is translated with the geostrophic windspeed.<br>
-
-
-
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Alternatively, with <b>use_ug_for_galilei_tr</b> = <i>.F</i>.,
+</p> <p>Alternatively, with <b>use_ug_for_galilei_tr</b>
+= <i>.F</i>.,
 the
 geostrophic wind can be replaced as translation speed by the (volume)
 averaged velocity. However, in this case the user must be aware of fast
 growing gravity waves, so this
-choice is usually not recommended!</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr><td align="left" valign="top"><a name="use_upstream_for_tke"></a><span style="font-weight: bold;">use_upstream_for_tke</span></td><td align="left" valign="top">L</td><td align="left" valign="top"><span style="font-style: italic;">.F.</span></td><td align="left" valign="top">Parameter to choose the advection/timestep scheme to be used for the subgrid-scale TKE.<br><br>By
+choice is usually not recommended!</p> </td> </tr> <tr><td align="left" valign="top"><a name="use_upstream_for_tke"></a><span style="font-weight: bold;">use_upstream_for_tke</span></td><td align="left" valign="top">L</td><td align="left" valign="top"><span style="font-style: italic;">.F.</span></td><td align="left" valign="top">Parameter to choose the
+advection/timestep scheme to be used for the subgrid-scale TKE.<br><br>By
 default, the advection scheme and the timestep scheme to be used for
-the subgrid-scale TKE are set by the initialization parameters <a href="#scalar_advec">scalar_advec</a> and <a href="#timestep_scheme">timestep_scheme</a>, respectively. <span style="font-weight: bold;">use_upstream_for_tke</span> = <span style="font-style: italic;">.T.</span>
+the subgrid-scale TKE are set by the initialization parameters <a href="#scalar_advec">scalar_advec</a> and <a href="#timestep_scheme">timestep_scheme</a>,
+respectively. <span style="font-weight: bold;">use_upstream_for_tke</span>
+= <span style="font-style: italic;">.T.</span>
 forces the Euler-scheme and the upstream-scheme to be used as timestep
 scheme and advection scheme, respectively. By these methods, the strong
@@ -18526,128 +2042,16 @@
 velocities are used for advection of particles (see particle package
 parameter <a href="chapter_4.2.html#use_sgs_for_particles">use_sgs_for_particles</a>).</td></tr><tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="vg_surface"></a><span style="font-weight: bold;">vg_surface</span></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">v-component of the geostrophic
-wind at the surface (in m/s).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+<td style="vertical-align: top;"> <p><a name="vg_surface"></a><span style="font-weight: bold;">vg_surface</span></p>
+</td> <td style="vertical-align: top;">R<br> </td>
+<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
+<td style="vertical-align: top;">v-component of the
+geostrophic
+wind at the surface (in m/s).<br> <br>
 This parameter assigns the value of the v-component of the geostrophic
 wind (vg) at the surface (k=0). Starting from this value, the initial
 vertical profile of the <br>
-
-
-
-
-
-
-
-
-
-
-v-component of the geostrophic wind is constructed with <a href="#vg_vertical_gradient">vg_vertical_gradient</a> and <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>. The
+v-component of the geostrophic wind is constructed with <a href="#vg_vertical_gradient">vg_vertical_gradient</a>
+and <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>.
+The
 profile
 constructed in that way is used for creating the initial vertical
@@ -18656,5 +2060,6 @@
 = 'set_constant_profiles')
 or it is used for calculating a stationary boundary layer wind profile
-(<a href="#initializing_actions">initializing_actions</a> =
+(<a href="#initializing_actions">initializing_actions</a>
+=
 'set_1d-model_profiles'). If vg is constant
 with height (i.e. vg(k)=<span style="font-weight: bold;">vg_surface</span>)
@@ -18663,610 +2068,66 @@
 if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
 in order to obtain larger
-time steps.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="vg_vertical_gradient"></a><span style="font-weight: bold;">vg_vertical_gradient</span></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Gradient(s) of the initial
-profile of the&nbsp; v-component of the geostrophic wind (in 1/100s).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+time steps.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="vg_vertical_gradient"></a><span style="font-weight: bold;">vg_vertical_gradient</span></p>
+</td> <td style="vertical-align: top;">R(10)<br>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br> </td> <td style="vertical-align: top;">Gradient(s) of the initial
+profile of the&nbsp; v-component of the geostrophic wind (in
+1/100s).<br> <br>
 The gradient holds starting from the height level defined by <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>
 (precisely: for all uv levels k where zu(k)
 &gt; <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
 vg(k) is set: vg(k) = vg(k-1) + dzu(k)
-* <span style="font-weight: bold;">vg_vertical_gradient</span>) up to
+* <span style="font-weight: bold;">vg_vertical_gradient</span>)
+up to
 the top boundary or up to the next height
 level defined by <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>.
 A total of 10 different
-gradients for 11 height intervals (10 intervals&nbsp; if <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>(1) =
+gradients for 11 height intervals (10 intervals&nbsp; if <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>(1)
+=
 0.0) can be assigned. The surface
 geostrophic wind is assigned by <a href="#vg_surface">vg_surface</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="vg_vertical_gradient_level"></a><span style="font-weight: bold;">vg_vertical_gradient_level</span></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Height level from which on the
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="vg_vertical_gradient_level"></a><span style="font-weight: bold;">vg_vertical_gradient_level</span></p>
+</td> <td style="vertical-align: top;">R(10)<br>
+</td> <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br> </td> <td style="vertical-align: top;">Height level from which on the
 gradient defined by <a href="#vg_vertical_gradient">vg_vertical_gradient</a>
-is effective (in m).<br>
-
-
-
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-
-
-
+is effective (in m).<br> <br>
 The height levels are to be assigned in ascending order. For the
 piecewise construction of a profile of the v-component of the
 geostrophic wind component (vg) see <a href="#vg_vertical_gradient">vg_vertical_gradient</a>.</td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p><a name="wall_adjustment"></a><b>wall_adjustment</b></p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.T.</i></td>
-
-
-
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>Parameter to restrict the mixing length in the vicinity of the
+</tr> <tr> <td style="vertical-align: top;">
+<p><a name="wall_adjustment"></a><b>wall_adjustment</b></p>
+</td> <td style="vertical-align: top;">L</td>
+<td style="vertical-align: top;"><i>.T.</i></td>
+<td style="vertical-align: top;"> <p>Parameter to
+restrict the mixing length in the vicinity of the
 bottom
-boundary.&nbsp; </p>
-
-
-
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      <p>With <b>wall_adjustment</b> = <i>.TRUE., </i>the mixing
+boundary.&nbsp; </p> <p>With <b>wall_adjustment</b>
+= <i>.TRUE., </i>the mixing
 length is limited to a maximum of&nbsp; 1.8 * z. This condition
 typically affects only the
-first grid points above the bottom boundary.</p>
-
-
-
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="wall_heatflux"></a>wall_heatflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(5)</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">5 * 0.0</span></td>
-
-
-
-
-
-
-      <td>Prescribed kinematic sensible heat flux in W m<sup>-2</sup>
-at the five topography faces:<br>
-
-
-
-      <br>
-
-
-
-      
-      
-      
-      <div style="margin-left: 40px;"><span style="font-weight: bold;">wall_heatflux(0)&nbsp;&nbsp; &nbsp;</span>top face<br>
-
-
-
-      <span style="font-weight: bold;">wall_heatflux(1)&nbsp;&nbsp;&nbsp; </span>left face<br>
-
-
-
-      <span style="font-weight: bold;">wall_heatflux(2)&nbsp;&nbsp;&nbsp; </span>right face<br>
-
-
-
-      <span style="font-weight: bold;">wall_heatflux(3)&nbsp;&nbsp;&nbsp; </span>south face<br>
-
-
-
-      <span style="font-weight: bold;">wall_heatflux(4)&nbsp;&nbsp;&nbsp; </span>north face</div>
-
-
-
-      <br>
-
-
-
-This parameter applies only in case of a non-flat <a href="#topography">topography</a>.&nbsp;The parameter <a href="#random_heatflux">random_heatflux</a>
-can be used to impose random perturbations on the internal two-dimensional surface heat
-flux field <span style="font-style: italic;">shf</span> that is composed of <a href="#surface_heatflux">surface_heatflux</a> at the bottom surface and <span style="font-weight: bold;">wall_heatflux(0)</span> at the topography top face.&nbsp;</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-
-
-
-
-  
-  
-  
-  
-  
-  
-  
-  
-  
-  
-  </tbody>
-</table>
-
-
-
-
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-
-
-
-
-<p style="line-height: 100%;"><br>
-
-
-
-
-
-
-
-
-
-
-<font color="#000080"><font color="#000080"><a href="chapter_4.0.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.2.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
-
-
-
-
-
-
-
-
-
-
-<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 22/08/06 (SR) </p>
-
-
-
-
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-
-
-
-
+first grid points above the bottom boundary.</p> </td> </tr>
+<tr> <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="wall_heatflux"></a>wall_heatflux</span></td>
+<td style="vertical-align: top;">R(5)</td> <td style="vertical-align: top;"><span style="font-style: italic;">5 * 0.0</span></td> <td>Prescribed
+kinematic sensible heat flux in W m<sup>-2</sup>
+at the five topography faces:<br> <br> <div style="margin-left: 40px;"><span style="font-weight: bold;">wall_heatflux(0)&nbsp;&nbsp;
+&nbsp;</span>top face<br> <span style="font-weight: bold;">wall_heatflux(1)&nbsp;&nbsp;&nbsp;
+</span>left face<br> <span style="font-weight: bold;">wall_heatflux(2)&nbsp;&nbsp;&nbsp;
+</span>right face<br> <span style="font-weight: bold;">wall_heatflux(3)&nbsp;&nbsp;&nbsp;
+</span>south face<br> <span style="font-weight: bold;">wall_heatflux(4)&nbsp;&nbsp;&nbsp;
+</span>north face</div> <br>
+This parameter applies only in case of a non-flat <a href="#topography">topography</a>.&nbsp;The
+parameter <a href="#random_heatflux">random_heatflux</a>
+can be used to impose random perturbations on the internal
+two-dimensional surface heat
+flux field <span style="font-style: italic;">shf</span>
+that is composed of <a href="#surface_heatflux">surface_heatflux</a>
+at the bottom surface and <span style="font-weight: bold;">wall_heatflux(0)</span>
+at the topography top face.&nbsp;</td> </tr> </tbody>
+</table><br>
+<p style="line-height: 100%;"><br><font color="#000080"><font color="#000080"><a href="chapter_4.0.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.2.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last
+change:&nbsp;</i> $Id$ </p>
+<br><br>
 </body></html>
