Index: palm/trunk/DOC/app/chapter_4.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.1.html	(revision 103)
+++ palm/trunk/DOC/app/chapter_4.1.html	(revision 108)
@@ -1,17 +1,126 @@
 <!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
+<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
+
+
+
+
+<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
@@ -25,11 +134,26 @@
 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
+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
+
+
+
+
+      
+      
+      
+      <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>
+      <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
@@ -37,32 +161,155 @@
 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>
+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>
+      </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
+
+
+
+
+      </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
+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>
+      <b>bc_e_b</b>
 = <span style="font-style: italic;">'neumann'</span>
 yields to
@@ -76,15 +323,74 @@
 is reset
 to <span style="font-style: italic;">'neumann'</span>.&nbsp;
-</p> <p style="font-style: normal;">At the top
+      </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
+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/radiation'</span>
@@ -93,5 +399,13 @@
 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&nbsp;<a href="#bc_ns">bc_ns</a>).<br> <br>
+and it also requires cyclic boundary conditions along y (see&nbsp;<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 -
@@ -101,10 +415,26 @@
 gradient) condition is used for the scalars. 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
@@ -115,21 +445,89 @@
 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
+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/radiation'</span>
@@ -139,5 +537,17 @@
 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 -
@@ -147,15 +557,67 @@
 gradient) condition is used for the scalars. 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
+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>
+      <span style="font-style: italic;">'neumann'</span>
 and <span style="font-style: italic;">'neumann+inhomo'</span>.&nbsp;
-<span style="font-style: italic;">'dirichlet'</span>
+      <span style="font-style: italic;">'dirichlet'</span>
 sets
 p(k=0)=0.0,&nbsp; <span style="font-style: italic;">'neumann'</span>
@@ -168,5 +630,13 @@
 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
+otherwise the run is terminated.&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>Since
 at the bottom boundary of the model the vertical
 velocity
@@ -177,11 +647,67 @@
 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>
+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
+(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>)
@@ -189,11 +715,58 @@
 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
+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>
@@ -202,13 +775,72 @@
 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>
 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
+
+
+
+      
+      
+      
+      <p>In the <a href="chapter_3.8.html">coupled</a> atmosphere executable,&nbsp;<a href="chapter_4.2.html#bc_pt_b">bc_pt_b</a> is internally set and does not need to be prescribed.</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>
@@ -218,23 +850,109 @@
 calculated from the initial
 temperature profile (see <a href="#pt_surface">pt_surface</a>,
-<a href="#pt_vertical_gradient">pt_vertical_gradient</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) =
+
+
+
+
+      
+      
+      
+      <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
+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>
+      <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
+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>
@@ -243,13 +961,65 @@
 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>
 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
+
+
+
+
+      </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
@@ -259,15 +1029,99 @@
 from the
 initial humidity profile (see <a href="#q_surface">q_surface</a>,
-<a href="#q_vertical_gradient">q_vertical_gradient</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 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>
@@ -277,13 +1131,65 @@
 (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>
 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
+
+
+
+
+      </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
@@ -294,23 +1200,162 @@
 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;"><a name="bc_sa_t"></a><span style="font-weight: bold;">bc_sa_t</span></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 salinity.&nbsp; </p> <p>This parameter only comes into effect for ocean runs (see parameter <a href="#ocean">ocean</a>).</p><p style="font-style: normal;">Allowed are the
+solved).</p>
+
+
+
+ </td>
+
+
+
+ </tr>
+
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="bc_sa_t"></a><span style="font-weight: bold;">bc_sa_t</span></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 salinity.&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>This parameter only comes into effect for ocean runs (see parameter <a href="#ocean">ocean</a>).</p>
+
+
+
+      
+      
+      
+      <p style="font-style: normal;">Allowed are the
 values <span style="font-style: italic;">'dirichlet' </span>(sa(k=nz+1)
 does not change during the run) and <span style="font-style: italic;">'neumann'</span>
-(sa(k=nz+1)=sa(k=nz))<span style="font-style: italic;"></span>.&nbsp;<br><br>
+(sa(k=nz+1)=sa(k=nz))<span style="font-style: italic;"></span>.&nbsp;<br>
+
+
+
+      <br>
+
+
+
+
 When a constant salinity flux is used at the top boundary (<a href="chapter_4.1.html#top_salinityflux">top_salinityflux</a>),
-<b>bc_sa_t</b> = <span style="font-style: italic;">'neumann'</span>
+      <b>bc_sa_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_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
+the top flux so that a constant value cannot be guaranteed.</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;">'neumann'</span>. <b>bc_uv_b</b>
 = <span style="font-style: italic;">'dirichlet'</span>
 yields the
@@ -319,6 +1364,38 @@
 (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
+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) =
@@ -326,9 +1403,57 @@
 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
+
+
+
+
+      </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>.
@@ -338,26 +1463,177 @@
 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;"><a name="bottom_salinityflux"></a><span style="font-weight: bold;">bottom_salinityflux</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td><td style="vertical-align: top;"><p>Kinematic salinity flux near the surface (in psu m/s).&nbsp;</p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).<p>The
+for the velocities are solved).</p>
+
+
+
+      
+      
+      
+      <p>In the <a href="chapter_3.8.html">coupled</a> ocean executable, <a href="chapter_4.2.html#bc_uv_t">bc_uv_t</a>&nbsp;is internally set ('neumann') and does not need to be prescribed.</p>
+
+
+
+ </td>
+
+
+
+ </tr>
+
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="bottom_salinityflux"></a><span style="font-weight: bold;">bottom_salinityflux</span></td>
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      <p>Kinematic salinity flux near the surface (in psu m/s).&nbsp;</p>
+
+
+
+This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).
+      
+      
+      
+      <p>The
 respective salinity flux value is used
 as bottom (horizontally homogeneous) boundary condition for the salinity equation. This additionally requires that a Neumann
-condition must be used for the salinity, which is currently the only available condition.<br> </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
+condition must be used for the salinity, which is currently the only available condition.<br>
+
+
+
+ </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>
+
+
+
+
+    </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>.
+      </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>
+
+
+
+
+    </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
@@ -365,9 +1641,41 @@
 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
+
+
+
+
+    </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>
+
+
+
+
+      <br>
+
+
+
+
 Currently, <span style="font-weight: bold;">building_wall_left</span>
 must be at least <span style="font-style: italic;">1
@@ -376,14 +1684,54 @@
 This parameter requires the use of&nbsp;<a href="#topography">topography</a>
 = <span style="font-style: italic;">'single_building'</span>.<br>
-<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
+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>
+
+
+
+
+      <br>
+
+
+
+
 Currently, <span style="font-weight: bold;">building_wall_south</span>
 must be at least <span style="font-style: italic;">1
@@ -392,14 +1740,66 @@
 This parameter requires the use of&nbsp;<a href="#topography">topography</a>
 = <span style="font-style: italic;">'single_building'</span>.<br>
-<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>
+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
@@ -408,15 +1808,71 @@
 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>)
+      <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>
+
+
+
+
+      <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
+
+
+
+
+      </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
@@ -428,25 +1884,129 @@
 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>
+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&nbsp;<a href="#humidity">humidity</a>
+      </span>requires&nbsp;<a href="#humidity">humidity</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>
+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>
+
+
+
+
+      </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
+
+
+
+
+      </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
+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
@@ -459,17 +2019,73 @@
 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
+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>,
+      <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
+
+
+
+
+      </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
+(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
@@ -482,28 +2098,152 @@
 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
+      <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>
+
+
+
+
+      <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>
+= (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.
+
+
+
+
+      </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>
+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
@@ -511,14 +2251,77 @@
 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 * <a href="chapter_4.2.html#dt_max">dt_max</a> (with dt_max
-= 20.0)</p> </ul> <p>the simulation will be
+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
+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
+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>
@@ -538,12 +2341,59 @@
 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
+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
+(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
@@ -551,79 +2401,690 @@
 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
+
+
+
+
+      </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
+(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 y-direction (in m).&nbsp; </p> <p>Along y-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
+
+
+
+
+      </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>
+
+
+
+      
+      
+      
+      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
+and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</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 y-direction (in m).&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>Along y-direction only a constant grid spacing is allowed.</p>
+
+
+
+      
+      
+      
+      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
+and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</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
+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
+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
+
+
+
+
+      
+      
+      
+      <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
+      <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
+      </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
+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/below which the grid is to be stretched
+vertically (in m).&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>For <a href="chapter_4.1.html#ocean">ocean</a> = .F., <b>dz_stretch_level </b>is the height level (in m)&nbsp;<span style="font-weight: bold;">above </span>which the grid is to be stretched
+vertically. The vertical grid
 spacings <a href="#dz">dz</a>
-above this level are calculated as&nbsp; </p> <ul> <p><b>dz</b>(k+1)
+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).
+
+
+
+
+      
+      
+      
+      </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
+w-levels are then defined as:&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <ul>
+
+
+
+ 
+        
+        
+        
+        <p>zw(k)
+= ( zu(k) + zu(k+1) ) * 0.5.
+
+ 
+      
+      </p>
+
+      
+      </ul>
+
+      
+      <p>For <a href="#ocean">ocean</a> = .T., <b>dz_stretch_level </b>is the height level (in m, negative) <span style="font-weight: bold;">below</span> which the grid is to be stretched
+vertically. The vertical grid
+spacings <a href="chapter_4.1.html#dz">dz</a> below this level are calculated correspondingly as 
+
+ 
+      
+      </p>
+
+      
+      <ul>
+
+        
+        <p><b>dz</b>(k-1)
+= <b>dz</b>(k) * <a href="chapter_4.1.html#dz_stretch_factor">dz_stretch_factor</a>.</p>
+
+      
+      </ul>
+
+
+
+ </td>
+
+
+
+ </tr>
+
+
+
+
+    <tr>
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="e_init"></a>e_init</span></td>
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
+
+
+      <td>Initial subgrid-scale TKE in m<sup>2</sup>s<sup>-2</sup>.<br>
+
+
+
+
+      <br>
+
+
+
+This
+option prescribes an initial&nbsp;subgrid-scale TKE from which the initial diffusion coefficients K<sub>m</sub> and K<sub>h</sub> will be calculated if <span style="font-weight: bold;">e_init</span> is positive. This option only has an effect if&nbsp;<a href="#km_constant">km_constant</a> is not set.</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
+
+
+
+
+      <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
+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
@@ -633,36 +3094,173 @@
 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
+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
+      </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>
+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
@@ -680,15 +3278,67 @@
 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>
+      </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
+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>
+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
@@ -699,5 +3349,13 @@
 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
@@ -707,17 +3365,77 @@
 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>),
@@ -726,9 +3444,53 @@
 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>),
@@ -737,30 +3499,132 @@
 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
+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>
+        <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>,
+        <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>
+        <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
+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,
@@ -770,10 +3634,48 @@
 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
+        <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
+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
@@ -790,6 +3692,30 @@
 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
+(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>
@@ -804,16 +3730,91 @@
 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
+
+
+
+
+      
+      
+      
+      </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>
+      <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
+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
+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
@@ -822,10 +3823,54 @@
 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>),
@@ -837,5 +3882,13 @@
 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
@@ -846,12 +3899,72 @@
 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
@@ -861,5 +3974,17 @@
 = <i>0.01</i>
 sufficiently removes the small-scale waves without affecting the
-longer waves.<br> </p> <p>By default, the filter is
+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
@@ -870,56 +3995,324 @@
 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
 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="loop_optimization"></a><span style="font-weight: bold;">loop_optimization</span></td><td style="vertical-align: top;">C*16</td><td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td><td>Method used to optimize loops for solving the prognostic equations .<br><br>By
+Pielke, quoted above). </p>
+
+
+
+ </td>
+
+
+
+ </tr>
+
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="loop_optimization"></a><span style="font-weight: bold;">loop_optimization</span></td>
+
+
+
+      <td style="vertical-align: top;">C*16</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
+
+
+
+      <td>Method used to optimize loops for solving the prognostic equations .<br>
+
+
+
+      <br>
+
+
+
+By
 default, the optimization method depends on the host on which PALM is
 running. On machines with vector-type CPUs, single 3d-loops are used to
 calculate each tendency term of each prognostic equation, while on all
 other machines, all prognostic equations are solved within one big loop
-over the two horizontal indices<span style="font-family: Courier New,Courier,monospace;"> i </span>and<span style="font-family: Courier New,Courier,monospace;"> j </span>(giving a good cache uitilization).<br><br>The default behaviour can be changed by setting either <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'vector'</span> or <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'cache'</span>.</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>
+over the two horizontal indices<span style="font-family: Courier New,Courier,monospace;"> i </span>and<span style="font-family: Courier New,Courier,monospace;"> j </span>(giving a good cache uitilization).<br>
+
+
+
+      <br>
+
+
+
+The default behaviour can be changed by setting either <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'vector'</span> or <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'cache'</span>.</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>
+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="humidity"></a><b>humidity</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
+
+
+
+
+      </td>
+
+
+
+ </tr>
+
+
+
+ <tr>
+
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      
+      <p><a name="humidity"></a><b>humidity</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
+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
+
+
+
+
+&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
 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
+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
@@ -938,19 +4331,47 @@
 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
+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
+
+
+
+
+      </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&nbsp;<a href="#humidity">humidity</a>
@@ -960,49 +4381,452 @@
 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>
+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>
+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>
+      </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
+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
+net.&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>For parallel runs, the total
 number of processors to be used
 is given by
@@ -1027,10 +4851,21 @@
 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
+
+
+
+
+      
+      
+      
+      <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>
@@ -1038,15 +4873,115 @@
 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
+      </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
+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>
@@ -1063,27 +4998,146 @@
 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
+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
+      <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
+      <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
+transposition restrictions).</p>
+
+
+
+      
+      
+      
+      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
+and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</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
@@ -1091,16 +5145,83 @@
 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>
+
+
+
+
+      
+      
+      
+      <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
+      <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
+transposition restrictions).</p>
+
+
+
+      
+      
+      
+      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
+and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</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
@@ -1115,34 +5236,264 @@
 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
+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
+      <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;"><a name="ocean"></a><span style="font-weight: bold;">ocean</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;">Parameter to switch on&nbsp;ocean runs.<br><br>By default PALM is configured to simulate&nbsp;atmospheric flows. However, starting from version 3.3, <span style="font-weight: bold;">ocean</span> = <span style="font-style: italic;">.T.</span> allows&nbsp;simulation of ocean turbulent flows. Setting this switch has several effects:<br><br><ul><li>An additional prognostic equation for salinity is solved.</li><li>Potential temperature in buoyancy and stability-related terms is replaced by potential density.</li><li>Potential
+restrictions).</p>
+
+
+
+ </td>
+
+
+
+ </tr>
+
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="ocean"></a><span style="font-weight: bold;">ocean</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;">Parameter to switch on&nbsp;ocean runs.<br>
+
+
+
+      <br>
+
+
+
+By default PALM is configured to simulate&nbsp;atmospheric flows. However, starting from version 3.3, <span style="font-weight: bold;">ocean</span> = <span style="font-style: italic;">.T.</span> allows&nbsp;simulation of ocean turbulent flows. Setting this switch has several effects:<br>
+
+
+
+      <br>
+
+
+
+      
+      
+      
+      <ul>
+
+
+
+        <li>An additional prognostic equation for salinity is solved.</li>
+
+
+
+        <li>Potential temperature in buoyancy and stability-related terms is replaced by potential density.</li>
+
+
+
+        <li>Potential
 density is calculated from the equation of state for seawater after
 each timestep, using the algorithm proposed by Jackett et al. (2006, J.
-Atmos. Oceanic Technol., <span style="font-weight: bold;">23</span>, 1709-1728).<br>So far, only the initial hydrostatic pressure is entered into this equation.</li><li>z=0 (sea surface) is assumed at the model top (vertical grid index <span style="font-family: Courier New,Courier,monospace;">k=nzt</span> on the w-grid), with negative values of z indicating the depth.</li><li>Initial profiles are constructed (e.g. from <a href="#pt_vertical_gradient">pt_vertical_gradient</a> / <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>) starting from the sea surface, using surface values&nbsp;given by <a href="#pt_surface">pt_surface</a>, <a href="#sa_surface">sa_surface</a>, <a href="#ug_surface">ug_surface</a>, and <a href="#vg_surface">vg_surface</a>.</li><li>Zero salinity flux is used as default boundary condition at the bottom of the sea.</li><li>If switched on, random perturbations are by default imposed to the upper model domain from zu(nzt*2/3) to zu(nzt-3).</li></ul><br>Relevant parameters to be exclusively used for steering ocean runs are <a href="#bc_sa_t">bc_sa_t</a>, <a href="#bottom_salinityflux">bottom_salinityflux</a>, <a href="#sa_surface">sa_surface</a>, <a href="#sa_vertical_gradient">sa_vertical_gradient</a>, <a href="#sa_vertical_gradient_level">sa_vertical_gradient_level</a>, and <a href="#top_salinityflux">top_salinityflux</a>.<br><br>Section <a href="chapter_4.2.2.html">4.4.2</a> gives an example for appropriate settings of these and other parameters neccessary for ocean runs.<br><br><span style="font-weight: bold;">ocean</span> = <span style="font-style: italic;">.T.</span> does not allow settings of <a href="#timestep_scheme">timestep_scheme</a> = <span style="font-style: italic;">'leapfrog'</span> or <span style="font-style: italic;">'leapfrog+euler'</span> as well as <a href="#scalar_advec">scalar_advec</a> = <span style="font-style: italic;">'ups-scheme'</span>.<br><br><span style="font-weight: bold;">Current limitations:</span><br>Using
-a vertical grid stretching is not recommended since it would still
-stretch the grid towards the top boundary of the model (sea surface)
-instead of the bottom boundary.</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
+Atmos. Oceanic Technol., <span style="font-weight: bold;">23</span>, 1709-1728).<br>
+
+
+
+So far, only the initial hydrostatic pressure is entered into this equation.</li>
+
+
+
+        <li>z=0 (sea surface) is assumed at the model top (vertical grid index <span style="font-family: Courier New,Courier,monospace;">k=nzt</span> on the w-grid), with negative values of z indicating the depth.</li>
+
+
+
+        <li>Initial profiles are constructed (e.g. from <a href="#pt_vertical_gradient">pt_vertical_gradient</a> / <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>) starting from the sea surface, using surface values&nbsp;given by <a href="#pt_surface">pt_surface</a>, <a href="#sa_surface">sa_surface</a>, <a href="#ug_surface">ug_surface</a>, and <a href="#vg_surface">vg_surface</a>.</li>
+
+
+
+        <li>Zero salinity flux is used as default boundary condition at the bottom of the sea.</li>
+
+
+
+        <li>If switched on, random perturbations are by default imposed to the upper model domain from zu(nzt*2/3) to zu(nzt-3).</li>
+
+
+
+      
+      
+      
+      </ul>
+
+
+
+      <br>
+
+
+
+Relevant parameters to be exclusively used for steering ocean runs are <a href="#bc_sa_t">bc_sa_t</a>, <a href="#bottom_salinityflux">bottom_salinityflux</a>, <a href="#sa_surface">sa_surface</a>, <a href="#sa_vertical_gradient">sa_vertical_gradient</a>, <a href="#sa_vertical_gradient_level">sa_vertical_gradient_level</a>, and <a href="#top_salinityflux">top_salinityflux</a>.<br>
+
+
+
+      <br>
+
+
+
+Section <a href="chapter_4.2.2.html">4.4.2</a> gives an example for appropriate settings of these and other parameters neccessary for ocean runs.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">ocean</span> = <span style="font-style: italic;">.T.</span> does not allow settings of <a href="#timestep_scheme">timestep_scheme</a> = <span style="font-style: italic;">'leapfrog'</span> or <span style="font-style: italic;">'leapfrog+euler'</span> as well as <a href="#scalar_advec">scalar_advec</a> = <span style="font-style: italic;">'ups-scheme'</span>.<span style="font-weight: bold;"></span><br>
+      </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
+      </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>),
@@ -1153,12 +5504,56 @@
 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
+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
+      </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>),
@@ -1166,64 +5561,446 @@
 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
+
+
+
+
+      
+      
+      
+      <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
+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
+(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
+(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
+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>
+      <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>
+      </p>
+
+
+
+ 
+      
+      
+      
+      <p><b>Note:</b> <br>
+
+
+
+
 With <span style="font-weight: bold;">passive_scalar</span>
 switched
 on, the simultaneous use of humidity (see&nbsp;<a href="#humidity">humidity</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
+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,
+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>
@@ -1234,5 +6011,13 @@
 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
+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
@@ -1242,9 +6027,68 @@
 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
+
+
+
+
+      
+      
+      
+      <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
@@ -1252,40 +6096,254 @@
 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><p>The precipitation rate and amount can be output by assigning the runtime parameter <a href="chapter_4.2.html#data_output">data_output</a> = <span style="font-style: italic;">'prr*'</span> or <span style="font-style: italic;">'pra*'</span>, respectively. The time interval on which the precipitation amount is defined can be controlled via runtime parameter <a href="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_interval</a>.</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
+content exceeds the critical value of 0.5 g/kg.</p>
+
+
+
+      
+      
+      
+      <p>The precipitation rate and amount can be output by assigning the runtime parameter <a href="chapter_4.2.html#data_output">data_output</a> = <span style="font-style: italic;">'prr*'</span> or <span style="font-style: italic;">'pra*'</span>, respectively. The time interval on which the precipitation amount is defined can be controlled via runtime parameter <a href="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_interval</a>.</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.<br><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>), always a reference temperature is used in the buoyancy terms with a default value of <span style="font-weight: bold;">pt_reference</span> = <a href="#pt_surface">pt_surface</a>.</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
+domain is used.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>), always a reference temperature is used in the buoyancy terms with a default value of <span style="font-weight: bold;">pt_reference</span> = <a href="#pt_surface">pt_surface</a>.</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
-<span style="font-weight: bold;">pt</span> at the surface (k=0)<b>.</b> Starting from this value,
+      <span style="font-weight: bold;">pt</span> 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>.
-This profile is also used for the 1d-model as a stationary profile.</p><p><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="#ocean">ocean</a>),
+      </a>.
+This profile is also used for the 1d-model as a stationary profile.</p>
+
+
+
+      
+      
+      
+      <p><span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="#ocean">ocean</a>),
 this parameter gives the temperature value at the sea surface, which is
 at k=nzt. The profile is then constructed from the surface down to the
 bottom of the model.</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
+
+
+
+
+      </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>
+(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
+
+
+
+
+      </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
+/ 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>
@@ -1299,8 +6357,52 @@
 = <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>
+      </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
+
+
+
+
+        <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
@@ -1310,23 +6412,149 @@
 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><p><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
+with uv levels).</p>
+
+
+
+      
+      
+      
+      <p><span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
 the profile is constructed like described above, but starting from the
 sea surface (k=nzt) down to the bottom boundary of the model. Height
-levels have then to be given as negative values, e.g. <span style="font-weight: bold;">pt_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.</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 have to be assigned in ascending order. The
+levels have then to be given as negative values, e.g. <span style="font-weight: bold;">pt_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.</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 have 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><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.
-</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
+For the piecewise construction of temperature profiles see <a href="#pt_vertical_gradient">pt_vertical_gradient</a>.</p>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.
+      </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
@@ -1335,20 +6563,124 @@
 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
+
+
+
+
+      </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
+
+
+
+
+      </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
+(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>
@@ -1363,8 +6695,47 @@
 assigned
 via <a href="#q_surface">q_surface</a>. </p>
-<p>Example:&nbsp; </p> <ul> <p><b>q_vertical_gradient</b>
+
+
+
+
+      
+      
+      
+      <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>
+
+
+
+
+        <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
@@ -1376,9 +6747,65 @@
 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
+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 humidity gradient defined by <a href="#q_vertical_gradient">q_vertical_gradient</a>
-is effective (in m).&nbsp; </p> <p>The height levels
+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
@@ -1386,20 +6813,132 @@
 (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
+
+
+
+
+      </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
+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
+= .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
+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>
@@ -1408,5 +6947,13 @@
 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
@@ -1414,14 +6961,70 @@
 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
+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
+      <br>
+
+
+
+ </p>
+
+
+
+If a near surface heat flux is used as bottom
 boundary
 condition (see <a href="#surface_heatflux">surface_heatflux</a>),
@@ -1434,7 +7037,15 @@
 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>
+every timestep.<br>
+
+
+
+ <br>
+
+
+
+
 In case of a non-flat <a href="#topography">topography</a>,&nbsp;assigning
-<b>random_heatflux</b>
+      <b>random_heatflux</b>
 = <i>.T.</i> imposes random perturbations on the
 combined&nbsp;heat
@@ -1442,9 +7053,53 @@
 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
+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>
@@ -1459,26 +7114,209 @@
 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
+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
+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;"><a name="sa_surface"></a><span style="font-weight: bold;">sa_surface</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">35.0</span></td><td style="vertical-align: top;"> <p>Surface salinity (in psu).&nbsp;</p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).<p>This
+
+
+
+
+      </td>
+
+
+
+ </tr>
+
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="sa_surface"></a><span style="font-weight: bold;">sa_surface</span></td>
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      
+      <p>Surface salinity (in psu).&nbsp;</p>
+
+
+
+This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).
+      
+      
+      
+      <p>This
 parameter assigns the value of the salinity <span style="font-weight: bold;">sa</span> at the sea surface (k=nzt)<b>.</b> Starting from this value,
 the
 initial vertical salinity profile is constructed from the surface down to the bottom of the model (k=0) by using&nbsp;<a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
 and&nbsp;<a href="chapter_4.1.html#sa_vertical_gradient_level">sa_vertical_gradient_level
-</a>.</p></td></tr><tr><td style="vertical-align: top;"><a name="sa_vertical_gradient"></a><span style="font-weight: bold;">sa_vertical_gradient</span></td><td style="vertical-align: top;">R(10)</td><td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td><td style="vertical-align: top;"><p>Salinity gradient(s) of the initial salinity profile (in psu
-/ 100 m).&nbsp; </p> <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p><p>This salinity gradient
+      </a>.</p>
+
+
+
+      </td>
+
+
+
+    </tr>
+
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="sa_vertical_gradient"></a><span style="font-weight: bold;">sa_vertical_gradient</span></td>
+
+
+
+      <td style="vertical-align: top;">R(10)</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      <p>Salinity gradient(s) of the initial salinity profile (in psu
+/ 100 m).&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p>
+
+
+
+      
+      
+      
+      <p>This salinity gradient
 holds starting from the height&nbsp;
 level defined by <a href="chapter_4.1.html#sa_vertical_gradient_level">sa_vertical_gradient_level</a>
@@ -1491,8 +7329,50 @@
 = <i>0.0</i>) can be assigned. The surface salinity at k=nzt is
 assigned via <a href="chapter_4.1.html#sa_surface">sa_surface</a>.&nbsp;
-</p> <p>Example:&nbsp; </p> <ul><p><b>sa_vertical_gradient</b>
+      </p>
+
+
+
+ 
+      
+      
+      
+      <p>Example:&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <ul>
+
+
+
+        
+        
+        
+        <p><b>sa_vertical_gradient</b>
 = <i>1.0</i>, <i>0.5</i>,&nbsp; <br>
-<b>sa_vertical_gradient_level</b> = <i>-500.0</i>,
--<i>1000.0</i>,</p></ul> <p>That
+
+
+
+
+        <b>sa_vertical_gradient_level</b> = <i>-500.0</i>,
+-<i>1000.0</i>,</p>
+
+
+
+      
+      
+      
+      </ul>
+
+
+
+ 
+      
+      
+      
+      <p>That
 defines the salinity to be constant down to z = -500.0 m with a salinity given by <a href="chapter_4.1.html#sa_surface">sa_surface</a>.
 For -500.0 m &lt; z &lt;= -1000.0 m the salinity gradient is
@@ -1500,25 +7380,176 @@
 100 m and for z &lt; -1000.0 m down to the bottom boundary it is
 0.5 psu / 100 m (it is assumed that the assigned height levels correspond
-with uv levels).</p></td></tr><tr><td style="vertical-align: top;"><a name="sa_vertical_gradient_level"></a><span style="font-weight: bold;">sa_vertical_gradient_level</span></td><td style="vertical-align: top;">R(10)</td><td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td><td style="vertical-align: top;"><p>Height level from which on the salinity gradient defined by <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
-is effective (in m).&nbsp; </p> <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p><p>The height levels have to be assigned in descending order. The
+with uv levels).</p>
+
+
+
+      </td>
+
+
+
+    </tr>
+
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="sa_vertical_gradient_level"></a><span style="font-weight: bold;">sa_vertical_gradient_level</span></td>
+
+
+
+      <td style="vertical-align: top;">R(10)</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      <p>Height level from which on the salinity gradient defined by <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
+is effective (in m).&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p>
+
+
+
+      
+      
+      
+      <p>The height levels have to be assigned in descending order. The
 default values result in a constant salinity profile regardless of the
 values of <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
 (unless the bottom boundary of the model is lower than -100000.0 m).
-For the piecewise construction of salinity profiles see <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</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
+For the piecewise construction of salinity profiles see <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</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
 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
 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
+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.
@@ -1539,10 +7570,37 @@
 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
+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,
@@ -1560,19 +7618,47 @@
 because otherwise the momentum would
 be subject to large numerical diffusion due to the upstream
-scheme.&nbsp; </p> <p style="margin-left: 40px;">Since
+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
+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&nbsp;<a href="#humidity">humidity</a>
@@ -1582,16 +7668,67 @@
 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
+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
+
+
+
+
+    </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
+made.&nbsp; </p>
+
+
+
+ 
+      
+      
+      
+      <p>By default, vertical profiles and
 other statistical quantities
 are calculated as horizontal and/or volume average of the total model
@@ -1606,14 +7743,28 @@
 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
+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>).
+      <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
+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>,
@@ -1628,9 +7779,65 @@
 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
+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>
@@ -1647,5 +7854,12 @@
 heat
 flux field <span style="font-style: italic;">shf</span>.&nbsp;</p>
-<p>
+
+
+
+
+      
+      
+      
+      <p>
 In case of a non-flat <a href="#topography">topography</a>,&nbsp;the
 internal two-dimensional&nbsp;surface heat
@@ -1657,5 +7871,13 @@
 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
+      </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>
@@ -1665,11 +7887,62 @@
 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
+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
+
+
+
+
+      </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
@@ -1678,11 +7951,53 @@
 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
+
+
+
+
+    </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
+
+
+
+
+      
+      
+      
+      <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
@@ -1694,5 +8009,17 @@
 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
+are not allowed. <br>
+
+
+
+ </p>
+
+
+
+ 
+      
+      
+      
+      <p>If no surface scalar
 flux is assigned (<b>surface_scalarflux</b>
 = <i>0.0</i>),
@@ -1703,9 +8030,57 @@
 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
+
+
+
+
+      </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
@@ -1718,5 +8093,17 @@
 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
+are not allowed.<br>
+
+
+
+ </p>
+
+
+
+ 
+      
+      
+      
+      <p>If no surface water
 flux is assigned (<b>surface_waterflux</b>
 = <i>0.0</i>),
@@ -1726,35 +8113,177 @@
 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
+
+
+
+
+      </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>
+
+
+
+
+      </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
+
+
+
+
+    </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
+
+
+
+
+      
+      
+      
+      <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
+
+
+
+
+      </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
+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
@@ -1765,9 +8294,56 @@
 = <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>
+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
+
+
+
+
+        <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>.
@@ -1779,9 +8355,69 @@
 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
+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
+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
@@ -1790,24 +8426,168 @@
 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
+
+
+
+
+      </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
+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
+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
+
+
+
+
+      </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
@@ -1820,10 +8600,38 @@
 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
+= '<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.
@@ -1832,7 +8640,35 @@
 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
+
+
+
+
+      </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>
@@ -1840,23 +8676,161 @@
 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
+
+
+
+
+      <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
+
+
+
+
+      </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
+
+
+
+
+      <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">
+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>
+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>
@@ -1864,14 +8838,61 @@
 = '<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>
+      <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;&nbsp;<a href="#humidity">humidity</a> = <span style="font-style: italic;">.F.</span>, and <a href="#prandtl_layer">prandtl_layer</a> = .T..<br>
-<font color="#000000"><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
+
+
+
+
+    </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
+
+
+
+
+      
+      
+      
+      <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
@@ -1881,36 +8902,247 @@
 because otherwise the resolved scale may contribute to
 the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-<p><span style="font-weight: bold;">Note:</span><br>The
+
+
+
+
+      
+      
+      
+      <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
+= .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;"><a name="top_momentumflux_u"></a><span style="font-weight: bold;">top_momentumflux_u</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">no prescribed momentumflux</span></td><td style="vertical-align: top;">Momentum flux along x at the top boundary (in m2/s2).<br><p>If a value is assigned to this parameter, the internal
+
+
+
+
+      </td>
+
+
+
+    </tr>
+
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="top_momentumflux_u"></a><span style="font-weight: bold;">top_momentumflux_u</span></td>
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed momentumflux</span></td>
+
+
+
+      <td style="vertical-align: top;">Momentum flux along x at the top boundary (in m2/s2).<br>
+
+
+
+      
+      
+      
+      <p>If a value is assigned to this parameter, the internal
 two-dimensional u-momentum flux field <span style="font-family: monospace;">uswst</span> is
 initialized with the value of <span style="font-weight: bold;">top_momentumflux_u</span> as
-top (horizontally homogeneous) boundary condition for the u-momentum equation.</p><p><span style="font-weight: bold;">Notes:</span><br>The
+top (horizontally homogeneous) boundary condition for the u-momentum equation.</p>
+
+
+
+      
+      
+      
+      <p><span style="font-weight: bold;">Notes:</span><br>
+
+
+
+The
 application of a top momentum flux additionally requires the setting of
 initial parameter <a href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a>
-= .T.. Setting of <span style="font-weight: bold;">top_momentumflux_u</span> requires setting of <a href="#top_momentumflux_v">top_momentumflux_v</a> also.</p><p>A&nbsp;Neumann
+= .T.. Setting of <span style="font-weight: bold;">top_momentumflux_u</span> requires setting of <a href="#top_momentumflux_v">top_momentumflux_v</a> also.</p>
+
+
+
+      
+      
+      
+      <p>A&nbsp;Neumann
 condition should be used for the u velocity component (see <a href="chapter_4.1.html#bc_uv_t">bc_uv_t</a>),
 because otherwise the resolved scale may contribute to
 the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-<span style="font-weight: bold;"></span><p>No
-Prandtl-layer is available at the top boundary so far.</p></td></tr><tr><td style="vertical-align: top;"><a name="top_momentumflux_v"></a><span style="font-weight: bold;">top_momentumflux_v</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">no prescribed momentumflux</span></td><td style="vertical-align: top;">Momentum flux along y at the top boundary (in m2/s2).<br><p>If a value is assigned to this parameter, the internal
+
+
+
+
+      <span style="font-weight: bold;"></span>
+      
+      
+      
+      <p>No
+Prandtl-layer is available at the top boundary so far.</p>
+
+
+
+      
+      
+      
+      <p> The <a href="chapter_3.8.html">coupled</a> ocean parameter file&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a> should include dummy REAL value assignments to both <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> and&nbsp;<a href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a> (e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to enable the momentum flux coupling.</p>
+
+
+
+      </td>
+
+
+
+    </tr>
+
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="top_momentumflux_v"></a><span style="font-weight: bold;">top_momentumflux_v</span></td>
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed momentumflux</span></td>
+
+
+
+      <td style="vertical-align: top;">Momentum flux along y at the top boundary (in m2/s2).<br>
+
+
+
+      
+      
+      
+      <p>If a value is assigned to this parameter, the internal
 two-dimensional v-momentum flux field <span style="font-family: monospace;">vswst</span> is
 initialized with the value of <span style="font-weight: bold;">top_momentumflux_v</span> as
-top (horizontally homogeneous) boundary condition for the v-momentum equation.</p><p><span style="font-weight: bold;">Notes:</span><br>The
+top (horizontally homogeneous) boundary condition for the v-momentum equation.</p>
+
+
+
+      
+      
+      
+      <p><span style="font-weight: bold;">Notes:</span><br>
+
+
+
+The
 application of a top momentum flux additionally requires the setting of
 initial parameter <a href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a>
-= .T.. Setting of <span style="font-weight: bold;">top_momentumflux_v</span> requires setting of <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> also.</p><p>A&nbsp;Neumann
+= .T.. Setting of <span style="font-weight: bold;">top_momentumflux_v</span> requires setting of <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> also.</p>
+
+
+
+      
+      
+      
+      <p>A&nbsp;Neumann
 condition should be used for the v velocity component (see <a href="chapter_4.1.html#bc_uv_t">bc_uv_t</a>),
 because otherwise the resolved scale may contribute to
 the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-<span style="font-weight: bold;"></span><p>No
-Prandtl-layer is available at the top boundary so far.</p></td></tr><tr><td style="vertical-align: top;"><a name="top_salinityflux"></a><span style="font-weight: bold;">top_salinityflux</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
-salinityflux</span></td><td style="vertical-align: top;"><p>Kinematic
+
+
+
+
+      <span style="font-weight: bold;"></span>
+      
+      
+      
+      <p>No
+Prandtl-layer is available at the top boundary so far.</p>
+
+
+
+      
+      
+      
+      <p> The <a href="chapter_3.8.html">coupled</a> ocean parameter file&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a> should include dummy REAL value assignments to both <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> and&nbsp;<a href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a> (e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to enable the momentum flux coupling.</p>
+
+
+
+      </td>
+
+
+
+    </tr>
+
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="top_salinityflux"></a><span style="font-weight: bold;">top_salinityflux</span></td>
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
+
+
+
+
+salinityflux</span></td>
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      <p>Kinematic
 salinity flux at the top boundary, i.e. the sea surface (in psu m/s).&nbsp; </p>
-<p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p><p>If a value is assigned to this parameter, the internal
+
+
+
+
+      
+      
+      
+      <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p>
+
+
+
+      
+      
+      
+      <p>If a value is assigned to this parameter, the internal
 two-dimensional surface heat flux field <span style="font-family: monospace;">saswst</span> is
 initialized with the value of <span style="font-weight: bold;">top_salinityflux</span>&nbsp;as
@@ -1919,18 +9151,91 @@
 because otherwise the resolved scale may contribute to
 the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-<p><span style="font-weight: bold;">Note:</span><br>The
+
+
+
+
+      
+      
+      
+      <p><span style="font-weight: bold;">Note:</span><br>
+
+
+
+The
 application of a salinity flux at the model top additionally requires the setting of
 initial parameter <a href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a>
-= .T..<span style="font-style: italic;"></span><span style="font-weight: bold;"></span> </p><p>See
-also <a href="chapter_4.1.html#bottom_salinityflux">bottom_salinityflux</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
+= .T..<span style="font-style: italic;"></span><span style="font-weight: bold;"></span> </p>
+
+
+
+      
+      
+      
+      <p>See
+also <a href="chapter_4.1.html#bottom_salinityflux">bottom_salinityflux</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>
+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>.
@@ -1945,14 +9250,78 @@
 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><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
+in order to obtain larger time steps.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
 this parameter gives the velocity value at the sea surface, which is
 at k=nzt. The profile is then constructed from the surface down to the
-bottom of the model.<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
+bottom of the model.<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>
+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>,
@@ -1963,39 +9332,217 @@
 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><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
+= 0.0) can be assigned. The surface geostrophic wind is assigned by <a href="#ug_surface">ug_surface</a>.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
 the profile is constructed like described above, but starting from the
 sea surface (k=nzt) down to the bottom boundary of the model. Height
-levels have then to be given as negative values, e.g. <span style="font-weight: bold;">ug_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.<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
+levels have then to be given as negative values, e.g. <span style="font-weight: bold;">ug_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.<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 have 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><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.</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
+geostrophic wind component (ug) see <a href="#ug_vertical_gradient">ug_vertical_gradient</a>.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.</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
+&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
+
+
+
+
+      
+      
+      
+      <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
+(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
@@ -2010,5 +9557,17 @@
 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
+
+
+
+
+      </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
@@ -2016,56 +9575,283 @@
 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
+      <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
+      </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
+      </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
+      </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
+      </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
+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>
@@ -2073,43 +9859,172 @@
 instead
 (see <a href="#surface_heatflux">surface_heatflux</a>,
-<a href="#surface_waterflux">surface_waterflux</a>
+      <a href="#surface_waterflux">surface_waterflux</a>
 and <a href="#surface_scalarflux">surface_scalarflux</a>)
-<span style="font-weight: bold;">or</span> the
+      <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>
+      <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
+      </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
+      <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
+
+
+
+
+      </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
+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>, <a href="#top_momentumflux_u">top_momentumflux_u</a>, <a href="#top_momentumflux_v">top_momentumflux_v</a>, <a href="#top_salinityflux">top_salinityflux</a>).</p><p>Currently, no value for the latent 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
+(see <a href="chapter_4.1.html#top_heatflux">top_heatflux</a>, <a href="#top_momentumflux_u">top_momentumflux_u</a>, <a href="#top_momentumflux_v">top_momentumflux_v</a>, <a href="#top_salinityflux">top_salinityflux</a>).</p>
+
+
+
+      
+      
+      
+      <p>Currently, no value for the latent 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
+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>
+      <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>
+
+
+
+
+      </p>
+
+
+
+ 
+      
+      
+      
+      <p>Alternatively, with <b>use_ug_for_galilei_tr</b>
 = <i>.F</i>.,
 the
@@ -2117,6 +10032,42 @@
 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>,
@@ -2128,14 +10079,66 @@
 are significantly reduced. This is required when subgrid-scale
 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
+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>
+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>.
@@ -2155,13 +10158,73 @@
 if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
 in order to obtain larger
-time steps.<br><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
+time steps.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
 this parameter gives the velocity value at the sea surface, which is
 at k=nzt. The profile is then constructed from the surface down to the
-bottom of the model.</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
+bottom of the model.</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>
+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)
@@ -2176,39 +10239,217 @@
 =
 0.0) can be assigned. The surface
-geostrophic wind is assigned by <a href="#vg_surface">vg_surface</a>.<br><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
+geostrophic wind is assigned by <a href="#vg_surface">vg_surface</a>.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
 the profile is constructed like described above, but starting from the
 sea surface (k=nzt) down to the bottom boundary of the model. Height
 levels have then to be given as negative values, e.g. <span style="font-weight: bold;">vg_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.</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 have 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>.<br><br><span style="font-weight: bold;">Attention:</span><br>In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.</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
+geostrophic wind component (vg) see <a href="#vg_vertical_gradient">vg_vertical_gradient</a>.<br>
+
+
+
+      <br>
+
+
+
+      <span style="font-weight: bold;">Attention:</span><br>
+
+
+
+In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.</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
 bottom
-boundary.&nbsp; </p> <p>With <b>wall_adjustment</b>
+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
+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>
+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>
@@ -2218,9 +10459,50 @@
 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>
+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>
+
+
+
+
+<br>
+
+
+
+<br>
+
+
+
+
+</body>
+</html>
