Index: palm/trunk/DOC/app/chapter_3.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.4.html	(revision 103)
+++ palm/trunk/DOC/app/chapter_3.4.html	(revision 108)
@@ -1,8 +1,27 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html><head>
-<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>chapter_3.4</title></head>
-<body><h3 style="line-height: 100%;"><font color="#000000">3.4 Input and
+<html>
+<head>
+
+
+  
+  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+
+  
+  <title>PALM chapter 3.4</title>
+</head>
+
+
+<body>
+
+
+<h3 style="line-height: 100%;"><font color="#000000">3.4
+Input and
 output files</font></h3>
-<p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The
+
+
+<p style="line-height: 100%;"></p>
+
+
+<p style="line-height: 100%;"><font color="#000000">The
 model works
 with a set of files, which are all located in the temporary working
@@ -22,5 +41,11 @@
 NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on
 machines where a NetCDF library is available.<br>
-</font></p><p style="line-height: 100%;"><font color="#000000">The file
+
+
+</font></p>
+
+
+<p style="line-height: 100%;"><font color="#000000">The
+file
 names described in the list correspond to the names indicated in the
 respective OPEN instruction, i.e. the files are expected and saved
@@ -34,5 +59,10 @@
 4.5.1</a> which gives more details about the PALM-NetCDF-output).</font>
 </p>
-<p style="line-height: 100%;"> </p><p style="line-height: 100%;"><font color="#000000">On
+
+
+<p style="line-height: 100%;"> </p>
+
+
+<p style="line-height: 100%;"><font color="#000000">On
 parallel
 computers many of the files are read and/or written by the central
@@ -67,19 +97,129 @@
 expected and/or to which output files are written. The file names in
 these directories are always named _0000, _0001, _0002 etc. </font>
-</font></p><font color="#000000"><font color="#000000">For internal use,
+</font></p>
+
+
+<p><font color="#000000"><font color="#000000">For
+internal use,
 the model may open a set of further files, which are not
 defined by the user but contain no usable information and
-therefore are not included in this list. <br>
-<br></font>
-<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr valign="top"> <td width="8%"> <p><font size="4"><b>Unit</b></font></p> </td>
-<td width="12%"> <p><font size="4"><b>Name</b></font></p>
-</td> <td width="4%"> <p><font size="4"><b>I/O</b></font></p>
-</td> <td width="9%"> <p><font size="4"><b>Format</b></font></p>
-</td> <td colspan="1" width="67%"> <p><font size="4"><b>Description/contents</b></font></p>
-</td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> 11<br> </td>
-<td width="12%"> <p><a name="PARIN"></a>PARIN</p>
-</td> <td width="4%"> <p align="center">I</p>
-</td> <td style="width: 9%;"> <p>ASCII/&nbsp;
-<br>NAMELIST</p> </td> <td colspan="1" width="67%"> <p><font color="#000000">Parameter
+therefore are not included in this list.</font></font></p>
+<p><font color="#000000"><font color="#000000">
+
+<a name="coupled"></a>In case of <a href="chapter_3.8.html">coupled</a> atmosphere-ocean
+runs (see <a href="chapter_3.8.html">chapter 3.8</a>),
+both the atmosphere and the </font></font><font color="#000000"><font color="#000000"><a href="chapter_4.1.html#ocean">ocean</a> executable use
+the same temporary working directory. However, each executable requires its own, unique set of files for I/O. In order to
+distinguish between atmosphere and ocean files, coupled </font></font><font color="#000000"><font color="#000000">atmosphere-ocean
+</font></font><font color="#000000"><font color="#000000">runs use the </font></font><font color="#000000"><font color="#000000">following
+filename convention</font></font><font color="#000000"><font color="#000000">. </font></font><font color="#000000"><font color="#000000">The
+atmosphere executable uses the set of normal filenames given in the
+table below. The ocean executable uses a set of modified filenames that
+have the string '_O' added to their normal name. The coupled
+ocean filenames are given in brackets in the table below where
+applicable. The string '_O' is simply appended </font></font><font color="#000000"><font color="#000000">to most
+filenames</font></font><font color="#000000"><font color="#000000">; exceptions are highlighted in bold face. (<span style="font-weight: bold;">Note:</span> uncoupled
+ocean runs use the normal set of filenames without '_O'.)</font></font></p>
+<p></p>
+<font color="#000000"><font color="#000000">
+
+<br>
+
+
+</font>
+<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
+
+
+  <tbody>
+
+
+    <tr valign="top">
+
+
+      <td width="8%">
+      
+      <p><font size="4"><b>Unit</b></font></p>
+
+
+      </td>
+
+
+      <td width="12%">
+      
+      <p><font size="4"><b>Name</b></font></p>
+
+
+      </td>
+
+
+      <td width="4%">
+      
+      <p><font size="4"><b>I/O</b></font></p>
+
+
+      </td>
+
+
+      <td width="9%">
+      
+      <p><font size="4"><b>Format</b></font></p>
+
+
+      </td>
+
+
+      <td colspan="1" width="67%">
+      
+      <p><font size="4"><b>Description/contents</b></font></p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr valign="top">
+
+
+      <td style="text-align: center;" width="8%"> 11<br>
+
+
+      </td>
+
+
+      <td width="12%">
+      
+      <p><a name="PARIN"></a>PARIN<br>
+
+
+(PARIN_O)</p>
+
+
+      </td>
+
+
+      <td width="4%">
+      
+      <p align="center">I</p>
+
+
+      </td>
+
+
+      <td style="width: 9%;">
+      
+      <p>ASCII/&nbsp; <br>
+
+
+NAMELIST</p>
+
+
+      </td>
+
+
+      <td colspan="1" width="67%">
+      
+      <p><font color="#000000">Parameter
 for model steering. This file
 is needed by the model in each case. Its content and structure is
@@ -87,9 +227,54 @@
 4.0</a>. <a href="chapter_4.4.1.html">Chapter
 4.4.1</a> <font color="#000000">shows a simple
-example. </font> </p> </td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> <p align="center">13</p> </td>
-<td width="12%"> <p><a name="BININ"></a>BININ/</p>
-</td> <td width="4%"> <p align="center">I</p>
-</td> <td width="9%"> <p>Binary</p> </td>
-<td colspan="1" width="67%"> <p>Binary data,
+example. </font> </p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr valign="top">
+
+
+      <td style="text-align: center;" width="8%">
+      
+      <p align="center">13</p>
+
+
+      </td>
+
+
+      <td width="12%">
+      
+      <p><a name="BININ"></a>BININ/<br>
+
+
+(BININ<span style="font-weight: bold;">_O</span>/)</p>
+
+
+      </td>
+
+
+      <td width="4%">
+      
+      <p align="center">I</p>
+
+
+      </td>
+
+
+      <td width="9%">
+      
+      <p>Binary</p>
+
+
+      </td>
+
+
+      <td colspan="1" width="67%">
+      
+      <p>Binary data,
 which are read in by the model at the beginning
 of a restart run (see <a href="chapter_3.3.html">chapter
@@ -106,10 +291,18 @@
 reads its own file and the file content is processor-dependent. The
 number of processors which can be used must not be changed during a job
-chain and/or if a job chain is continued.&nbsp; </p> <p>Knowledge
+chain and/or if a job chain is continued.&nbsp; </p>
+
+
+      
+      <p>Knowledge
 of the file structure is usually not necessary,
 because the file is produced and also read again by the model, but it
 can be useful for error determination in case of read errors .
 Therefore the file structure is described in the following.&nbsp; </p>
-<p>The first record of this file contains a version number (ten
+
+
+      
+      <p>The first record of this file contains a version number
+(ten
 character string) of the subroutine, which, which output the data that
 follows (write_var_list.f90). This number has to
@@ -117,5 +310,9 @@
 (read_var_list.f90) in case of a restart run. Otherwise the model run
 is aborted. Version numbers are changed whenever new code revisions
-require a change of the file format.&nbsp; </p> <p>Starting
+require a change of the file format.&nbsp; </p>
+
+
+      
+      <p>Starting
 from the second record, all initial parameters follow
 (exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>),
@@ -128,9 +325,17 @@
 and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
 If a variable with unknown name is found the model run is
-aborted.&nbsp; </p> <p>At the end of the initial
+aborted.&nbsp; </p>
+
+
+      
+      <p>At the end of the initial
 parameters a record with the string "<i>***
 end ***</i>"follows (filled up with trailing blanks up to a
 length of
-30 characters).&nbsp; </p> <p>Afterwards the fields
+30 characters).&nbsp; </p>
+
+
+      
+      <p>Afterwards the fields
 of the prognostic and diagnostic
 variables follow. This part of the file also begins with a record
@@ -138,5 +343,9 @@
 version number of the subroutine that wrote the arrays that follow
 (write_3d_binary.f90). It must agree with the number of the reading
-subroutine (read_3d_binary.f90).&nbsp; </p> <p>The
+subroutine (read_3d_binary.f90).&nbsp; </p>
+
+
+      
+      <p>The
 following record contains the number of processors which
 were used in the model run producing this file, the processor ID of the
@@ -147,5 +356,9 @@
 particular on parallel computers, because the jobs of a job chain
 always have to use the same number of processors and the same virtual
-processor grid.&nbsp; </p> <p>After these tests the
+processor grid.&nbsp; </p>
+
+
+      
+      <p>After these tests the
 individual arrays as well as parameters
 and variables for plots of horizontally averaged vertical profiles
@@ -158,15 +371,63 @@
 parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
 = <i>.TRUE</i> is selected, otherwise they will be
-skipped.&nbsp; </p> <p>At the end of the file there
+skipped.&nbsp; </p>
+
+
+      
+      <p>At the end of the file there
 has to be a record with the
 character string "<span style="font-style: italic;"></span><i>***
 end
 ***</i>"(filled up with trailing blanks up to a length of 20
-characters).</p> </td> </tr> <tr valign="top">
-<td style="text-align: center;" width="8%"> <p align="center">14</p> </td> <td width="12%">
-<p><a name="BINOUT"></a>BINOUT/</p> </td>
-<td width="4%"> <p align="center">O</p>
-</td> <td width="9%"> <p>Binary</p> </td>
-<td colspan="1" width="67%"> <p>Binary data,
+characters).</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr valign="top">
+
+
+      <td style="text-align: center;" width="8%">
+      
+      <p align="center">14</p>
+
+
+      </td>
+
+
+      <td width="12%">
+      
+      <p><a name="BINOUT"></a>BINOUT/<br>
+
+
+(BINOUT<span style="font-weight: bold;">_O</span>/)</p>
+
+
+      </td>
+
+
+      <td width="4%">
+      
+      <p align="center">O</p>
+
+
+      </td>
+
+
+      <td width="9%">
+      
+      <p>Binary</p>
+
+
+      </td>
+
+
+      <td colspan="1" width="67%">
+      
+      <p>Binary data,
 which are written by the model at the end of the
 run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
@@ -185,5 +446,9 @@
 the
 description of the file <a href="#BININ">BININ</a>.&nbsp;
-</p> <p>The file BINOUT is written by the model only if,
+      </p>
+
+
+      
+      <p>The file BINOUT is written by the model only if,
 with the help
 of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is
@@ -192,10 +457,44 @@
 variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span>
 (see <a href="chapter_3.3.html">chapter
-3.3</a>).&nbsp; </p> <p>With large grid point
+3.3</a>).&nbsp; </p>
+
+
+      
+      <p>With large grid point
 numbers the file BINOUT (or the
 files residing in directory BINOUT/) will be very large and should
 be stored (if available) on the archive system of the remote computer.</p>
-</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">15<br>
-</td> <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td> <td style="vertical-align: top;">O</td> <td style="vertical-align: top;">Ascii</td> <td colspan="1" width="67%"> <p>This file contains
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">15<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL<br>
+
+
+(RUN_CONTROL_O)</td>
+
+
+      <td style="vertical-align: top;">O</td>
+
+
+      <td style="vertical-align: top;">Ascii</td>
+
+
+      <td colspan="1" width="67%">
+      
+      <p>This file contains
 the so-called time step control output of
 the model. At certain temporal intervals, which are described by the
@@ -206,9 +505,17 @@
 file. Additionally, such a control line is always written, whenever the
 time step of the model changes. All data and quantities always refer to
-the entire model domain.&nbsp; </p> <p>If the
+the entire model domain.&nbsp; </p>
+
+
+      
+      <p>If the
 1D-model is switched on for the initialization of the
 3D-models, then control lines are likewise written into this file at
 certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>).&nbsp;
-</p> <p>By default, the file RUN_CONTROL only lists
+      </p>
+
+
+      
+      <p>By default, the file RUN_CONTROL only lists
 information
 about the selected model parameters at the beginning of the
@@ -220,42 +527,213 @@
 it can be achieved that this information is also written at the
 beginning of the file RUN_CONTROL at restart runs.&nbsp; </p>
-<p>The individual columns of the 1D - time step control output
+
+
+      
+      <p>The individual columns of the 1D - time step control
+output
 have the following meaning (listed by the respective heading of the
 appropriate
-column in the file):&nbsp; <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2">
-<tbody> <tr> <td style="vertical-align: top;">ITER.</td>
-<td style="vertical-align: top;">Number of time steps
-accomplished so far</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (in hours: minutes:
-seconds)</td> </tr> <tr> <td style="vertical-align: top;">DT</td> <td style="vertical-align: top;">Time step (in s)</td> </tr>
-<tr> <td style="vertical-align: top;">UMAX</td>
-<td style="vertical-align: top;">Maximum absolute wind
+column in the file):&nbsp; <br>
+
+
+      </p>
+
+
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">ITER.</td>
+
+
+            <td style="vertical-align: top;">Number of
+time steps
+accomplished so far</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">HH:MM:SS</td>
+
+
+            <td style="vertical-align: top;">Time (in
+hours: minutes:
+seconds)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">DT</td>
+
+
+            <td style="vertical-align: top;">Time step (in
+s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">UMAX</td>
+
+
+            <td style="vertical-align: top;">Maximum
+absolute wind
 velocity
-(u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind
+(u-component) (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">VMAX</td>
+
+
+            <td style="vertical-align: top;">Maximum
+absolute wind
 velocity
-(v-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">U *</td> <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td> </tr>
-<tr> <td style="vertical-align: top;">ALPHA</td>
-<td style="vertical-align: top;">Angle of the wind vector
+(v-component) (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">U *</td>
+
+
+            <td style="vertical-align: top;">Friction
+velocity (<font color="#000000">in </font>m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">ALPHA</td>
+
+
+            <td style="vertical-align: top;">Angle of the
+wind vector
 (to the x-axis) at the top of the
 Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td>
-</tr> <tr> <td style="vertical-align: middle;">ENERG.</td>
-<td style="vertical-align: top;">Kinetic energy of the
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">ENERG.</td>
+
+
+            <td style="vertical-align: top;">Kinetic
+energy of the
 1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
-averaged over all grid points</td> </tr> </tbody> </table>
-<p>&nbsp;
+averaged over all grid points</td>
+
+
+          </tr>
+
+
+        
+        </tbody>
+      
+      </table>
+
+
+      
+      <p>&nbsp;
 The individual columns of the 3D - time step control output
 have the following meaning (listed by the respective heading of the
 appropriate
-column in the file):<br> </p> <table style="text-align: left; width: 100%;" cellpadding="2">
-<tbody> <tr> <td style="vertical-align: top;">RUN</td>
-<td style="vertical-align: top;">Serial-number of the job
+column in the file):<br>
+
+
+      </p>
+
+
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">RUN</td>
+
+
+            <td style="vertical-align: top;">Serial-number
+of the job
 in the job chain. The initial
 run has the number 0, restart runs accordingly have larger numbers.</td>
-</tr> <tr> <td style="vertical-align: top;">ITER.</td>
-<td style="vertical-align: top;">Number of time steps
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">ITER.</td>
+
+
+            <td style="vertical-align: top;">Number of
+time steps
 accomplished since starting time t=0 of
-the initial run.</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (<font color="#000000">in
-</font>hours: minutes:
+the initial run.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">HH:MM:SS</td>
+
+
+            <td style="vertical-align: top;">Time (<font color="#000000">in </font>hours: minutes:
 seconds) since starting time t=0 of the
-initial run.</td> </tr> <tr> <td style="vertical-align: top;">DT (E)</td> <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
+initial run.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">DT (E)</td>
+
+
+            <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
 following character indicates whether the
 time
@@ -268,7 +746,18 @@
 Euler). This
 does
-not apply for the default Runge-Kutta timestep scheme.</td> </tr>
-<tr> <td style="vertical-align: top;">UMAX</td>
-<td style="vertical-align: top;">Maximum absolute wind
+not apply for the default Runge-Kutta timestep scheme.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">UMAX</td>
+
+
+            <td style="vertical-align: top;">Maximum
+absolute wind
 velocity (u-component) (<font color="#000000">in </font>m/s).
 If at
@@ -277,6 +766,17 @@
 horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
 the character D will appear directly after the velocity value.</td>
-</tr> <tr> <td style="vertical-align: top;">VMAX</td>
-<td style="vertical-align: top;">Maximum absolute wind
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">VMAX</td>
+
+
+            <td style="vertical-align: top;">Maximum
+absolute wind
 velocity (v-component) (<font color="#000000">in </font>m/s).
 If at
@@ -285,70 +785,266 @@
 horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
 the character D will appear directly after the velocity value.</td>
-</tr> <tr> <td style="vertical-align: top;">WMAX</td>
-<td style="vertical-align: top;">Maximum absolute wind
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">WMAX</td>
+
+
+            <td style="vertical-align: top;">Maximum
+absolute wind
 velocity (w-component) (<font color="#000000">in </font>m/s).</td>
-</tr> <tr> <td style="vertical-align: top;">U
-*</td> <td style="vertical-align: top;">Horizontal
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">U
+*</td>
+
+
+            <td style="vertical-align: top;">Horizontal
 average of the
 friction velocity (<font color="#000000">in </font>m/s).</td>
-</tr> <tr> <td style="vertical-align: top;">W
-*</td> <td style="vertical-align: top;">Convective
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">W
+*</td>
+
+
+            <td style="vertical-align: top;">Convective
 velocity scale
 (<font color="#000000">in </font>m/s). The assumed
 boundary layer
-height is determined via the heat flux minimum criterion.</td> </tr>
-<tr> <td style="vertical-align: top;">THETA *</td>
-<td style="vertical-align: top;">Characteristic
+height is determined via the heat flux minimum criterion.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">THETA *</td>
+
+
+            <td style="vertical-align: top;">Characteristic
 temperature
 of the Prandtl - layer (<font color="#000000">in </font>K).</td>
-</tr> <tr> <td style="vertical-align: top;">Z_I</td>
-<td style="vertical-align: top;">Height of the convective
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">Z_I</td>
+
+
+            <td style="vertical-align: top;">Height of the
+convective
 boundary layer (<font color="#000000">in </font>m),
 determined via
-the criterion of the heat flux minimum.</td> </tr> <tr>
-<td style="vertical-align: middle;">ENERG.</td> <td style="vertical-align: top;">Average resolved total
+the criterion of the heat flux minimum.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">ENERG.</td>
+
+
+            <td style="vertical-align: top;">Average
+resolved total
 energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
-normalized with the total number of grid points.</td> </tr>
-<tr> <td style="vertical-align: middle;">DISTENERG</td>
-<td style="vertical-align: top;">Average resolved
+normalized with the total number of grid points.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">DISTENERG</td>
+
+
+            <td style="vertical-align: top;">Average
+resolved
 disturbance energy of flow field (<font color="#000000">in
-</font>m<sup>2</sup>/s<sup>2</sup>),
-normalized with the total number of grid points.</td> </tr>
-<tr> <td style="vertical-align: top;">DIVOLD</td>
-<td style="vertical-align: top;"><font color="#000000">Divergence
+            </font>m<sup>2</sup>/s<sup>2</sup>),
+normalized with the total number of grid points.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">DIVOLD</td>
+
+
+            <td style="vertical-align: top;"><font color="#000000">Divergence
 of the velocity field (sum of
 the absolute values) (</font><font color="#000000">in
-</font><font color="#000000">1/s) before call of the
+            </font><font color="#000000">1/s) before
+call of the
 pressure solver,
 normalized with the total number of grid points.</font></td>
-</tr> <tr> <td style="vertical-align: top;">DIVNEW</td>
-<td style="vertical-align: top;"><font color="#000000">Divergence
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">DIVNEW</td>
+
+
+            <td style="vertical-align: top;"><font color="#000000">Divergence
 of the velocity field (sum of
 the absolute values) (</font><font color="#000000">in
-</font><font color="#000000">1/s) after call of the
+            </font><font color="#000000">1/s) after
+call of the
 pressure solver, normalized</font>
-with the total number of grid points.</td> </tr> <tr>
-<td style="vertical-align: top;">UMAX (KJI)</td> <td style="vertical-align: top;">Indices of the grid point
+with the total number of grid points.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">UMAX (KJI)</td>
+
+
+            <td style="vertical-align: top;">Indices of
+the grid point
 with the maximum absolute
-u-component of the wind velocity (sequence: k, j, i).</td> </tr>
-<tr> <td style="vertical-align: top;">VMAX (KJI)</td>
-<td style="vertical-align: top;">Indices of the grid point
+u-component of the wind velocity (sequence: k, j, i).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">VMAX (KJI)</td>
+
+
+            <td style="vertical-align: top;">Indices of
+the grid point
 with the maximum absolute
-v-component of the wind velocity (sequence: k, j, i).</td> </tr>
-<tr> <td style="vertical-align: top;">WMAX (KJI)</td>
-<td style="vertical-align: top;">Indices of the grid point
+v-component of the wind velocity (sequence: k, j, i).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">WMAX (KJI)</td>
+
+
+            <td style="vertical-align: top;">Indices of
+the grid point
 with the maximum absolute
-w-component of the wind velocity (sequence: k, j, i).</td> </tr>
-<tr> <td style="vertical-align: top;">ADVECX</td>
-<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
+w-component of the wind velocity (sequence: k, j, i).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">ADVECX</td>
+
+
+            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
 coordinate system has been moved in
 x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
-</tr> <tr> <td style="vertical-align: top;">ADVECY</td>
-<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;">ADVECY</td>
+
+
+            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
 coordinate system has been moved in
 y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
-</tr> </tbody> </table> </td> </tr> <tr>
-<td style="vertical-align: top; text-align: center;">16<br>
-</td> <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This file contains horizontally
+
+
+          </tr>
+
+
+        
+        </tbody>
+      
+      </table>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">16<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL<br>
+
+
+(LIST_PROFIL_O) </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">This file contains
+horizontally
 (and possibly temporally)
 averaged vertical profiles of some model variables. The quantities
@@ -363,4 +1059,6 @@
 the respective subdomain (see <a href="chapter_4.3.html#region">region</a>)
 appears in the header of the respective table. <br>
+
+
 In each case the tables consist of a header, followed by the
 profiles arranged next to each other in columns. The header contains
@@ -370,89 +1068,423 @@
 computer, date, time of the beginning of the run, name of the
 subdomain, output time, kind of averaging). On the u-v-level the
-following columns are written: <br> <table style="text-align: left; width: 100%;" cellpadding="2">
-<tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br>
-</td> <td style="text-align: left; vertical-align: middle;">Vertical
-grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br>
-</td> <td style="text-align: left; vertical-align: middle;">Height
+following columns are written: <br>
+
+
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">k<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Vertical
+grid point index.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">zu<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Height
 of the grid point
 level (<font color="#000000">in </font>m).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br>
-</td> <td style="text-align: left; vertical-align: middle;">u-component
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">u<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">u-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">du<br>
-</td> <td style="text-align: left; vertical-align: middle;">Deviation
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">du<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Deviation
 of the
 u-component from the initial profile at the
 time t=0 (initialization profile) (<font color="#000000">in
-</font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br>
-</td> <td style="text-align: left; vertical-align: middle;">v-component
+            </font>m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">v<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">v-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">dv<br>
-</td> <td style="text-align: left; vertical-align: middle;">Deviation
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">dv<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Deviation
 of the
 v-component from the initial profile at the
 time t=0 (initialization profile) (<font color="#000000">in
-</font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<br> </td> <td style="text-align: left; vertical-align: middle;">Potential
+            </font>m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+            <br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Potential
 temperature (<font color="#000000">in </font>K).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">dpt<br>
-</td> <td style="text-align: left; vertical-align: middle;">Deviation
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">dpt<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Deviation
 of potential
 temperature from the initial profile at
 the time t=0 (initialization profile) (<font color="#000000">in
-</font>K).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br>
-</td> <td style="text-align: left; vertical-align: middle;">Turbulent
+            </font>K).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">e<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
 kinetic energy
 (subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br>
-</td> <td style="text-align: left; vertical-align: middle;">Turbulent
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">Km<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br>
-</td> <td style="text-align: left; vertical-align: middle;">Turbulent
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">Kh<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br>
-</td> <td style="text-align: left; vertical-align: middle;">Mixing
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">l<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Mixing
 length (<font color="#000000">in </font>m).</td>
-</tr> <tr> <td style="vertical-align: top;"><br>
-</td> <td style="vertical-align: top;"><br> </td>
-</tr> </tbody> </table>
-On the w-level the following columns are written:<br> <br>
-<table style="text-align: left; width: 100%;" cellpadding="2">
-<tbody> <tr> <td style="vertical-align: middle;">k<br>
-</td> <td style="vertical-align: middle;">Vertical
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><br>
+
+
+            </td>
+
+
+            <td style="vertical-align: top;"><br>
+
+
+            </td>
+
+
+          </tr>
+
+
+        
+        </tbody>
+      
+      </table>
+
+
+On the w-level the following columns are written:<br>
+
+
+      <br>
+
+
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">k<br>
+
+
+            </td>
+
+
+            <td style="vertical-align: middle;">Vertical
 grid point
-index.</td> </tr> <tr> <td style="vertical-align: middle;">zw<br> </td> <td style="vertical-align: middle;">Height of the grid
+index.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">zw<br>
+
+
+            </td>
+
+
+            <td style="vertical-align: middle;">Height of
+the grid
 point
 level (<font color="#000000">in </font>m).</td>
-</tr> <tr> <td style="vertical-align: middle;">w'pt'</td>
-<td style="vertical-align: middle;">Vertical subgrid-scale
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">w'pt'</td>
+
+
+            <td style="vertical-align: middle;">Vertical
+subgrid-scale
 kinematic heat flux (<font color="#000000">in </font>K
-m/s).</td> </tr> <tr> <td style="vertical-align: middle;">wpt</td> <td style="vertical-align: middle;">Vertical total (
+m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">wpt</td>
+
+
+            <td style="vertical-align: middle;">Vertical
+total (
 subgrid-scale + resolved)
 kinematic heat flux (<font color="#000000">in </font>K
-m/s).</td> </tr> <tr> <td style="vertical-align: middle;">w'u'</td> <td style="vertical-align: middle;">u-component of the
+m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">w'u'</td>
+
+
+            <td style="vertical-align: middle;">u-component
+of the
 vertical subgrid-scale momentum flux (<font color="#000000">in
-</font>m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;">wu</td>
-<td style="vertical-align: middle;">u-component of the
+            </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">wu</td>
+
+
+            <td style="vertical-align: middle;">u-component
+of the
 total
 vertical momentum flux (
 subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;">w'v'</td>
-<td style="vertical-align: middle;">v-component of the
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">w'v'</td>
+
+
+            <td style="vertical-align: middle;">v-component
+of the
 vertical subgrid-scale momentum flux (<font color="#000000">in
-</font>m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;">wv</td>
-<td style="vertical-align: middle;">v-component of the
+            </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: middle;">wv</td>
+
+
+            <td style="vertical-align: middle;">v-component
+of the
 total
 vertical momentum flux (
 subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> </tbody> </table> <br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">17
-</td> <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This file contains the vertical
+
+
+          </tr>
+
+
+        
+        </tbody>
+      
+      </table>
+
+
+      <br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">17
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D<br>
+
+
+(LIST_PROFIL_1D_O)</td>
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+      <td style="vertical-align: top;">This file contains
+the vertical
 profiles calculated by the
 1D-model within initial runs. The quantities saved are set
@@ -466,42 +1498,215 @@
 only switched on at initial runs), executing computer, date,
 time of the beginning of the run, output time). Afterwards the
-following columns appear:<br> <table style="text-align: left; width: 100%;" cellpadding="2">
-<tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br>
-</td> <td style="text-align: left; vertical-align: middle;">Vertical
-grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br>
-</td> <td style="text-align: left; vertical-align: middle;">Height
+following columns appear:<br>
+
+
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">k<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Vertical
+grid point index.</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">zu<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Height
 of the grid point
 level (<font color="#000000">in </font>m).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br>
-</td> <td style="text-align: left; vertical-align: middle;">u-component
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">u<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">u-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br>
-</td> <td style="text-align: left; vertical-align: middle;">v-component
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">v<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">v-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">pt<br>
-</td> <td style="text-align: left; vertical-align: middle;">Potential
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">pt<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Potential
 temperature (<font color="#000000">in </font>K).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br>
-</td> <td style="text-align: left; vertical-align: middle;">Turbulent
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">e<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
 kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">rif<br>
-</td> <td style="text-align: left; vertical-align: middle;">Flux
-Richardson number</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br>
-</td> <td style="text-align: left; vertical-align: middle;">Turbulent
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">rif<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Flux
+Richardson number</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">Km<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br>
-</td> <td style="text-align: left; vertical-align: middle;">Turbulent
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">Kh<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-</tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br>
-</td> <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
-length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> </tr> </tbody>
-</table> <br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">18 </td>
-<td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
-</td> <td style="vertical-align: top;">O </td>
-<td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">Time measurements are
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="text-align: left; vertical-align: middle;">l<br>
+
+
+            </td>
+
+
+            <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
+length (</font><font color="#000000">in </font><font color="#000000">m).</font></td>
+
+
+          </tr>
+
+
+        
+        </tbody>
+      
+      </table>
+
+
+      <br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">18
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES<br>
+
+
+(CPU_MEASURES_O)</td>
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+      <td style="vertical-align: top;">Time measurements
+are
 accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file
 CPU_MEASURES contains a header with some basic information of the
@@ -517,4 +1722,6 @@
 measures) overlaps (in particular with the parts described in the first
 table) are possible.&nbsp; <br>
+
+
 For each model part it is indicated in the following columns how much
 CPU time was needed (absolutely and relative), and how often it was
@@ -527,11 +1734,39 @@
 parallelization the CPU times on the individual processors should
 differ only little from each other and the standard deviation should be
-small.&nbsp; </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">19 </td>
-<td style="vertical-align: top;"><a name="HEADER"></a>HEADER
-</td> <td style="vertical-align: top;">O </td>
-<td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>Information about
+small.&nbsp; </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">19
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="HEADER"></a>HEADER<br>
+
+
+(HEADER_O) </td>
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>Information about
 the selected model parameters (physical and
 numerical values) as well as general information about the
-run.&nbsp; </p> <p>This file contains the values of
+run.&nbsp; </p>
+
+
+      
+      <p>This file contains the values of
 all important steering
 parameters
@@ -554,5 +1789,9 @@
 time reached is missing etc.) and then briefly before the normal end of
 the simulation. The second, now complete output overwrites the first
-output.).&nbsp; </p> <p>At the end of the file,
+output.).&nbsp; </p>
+
+
+      
+      <p>At the end of the file,
 information about the values of user
 parameters (see <a href="chapter_3.7.html">chapter
@@ -571,10 +1810,41 @@
 profiles and time series are output. All further information to appear
 here, must be provided by the user (by appropriate
-WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p> </td>
-</tr> <tr> <td style="vertical-align: top; text-align: center;">21 </td>
-<td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY
-</td> <td style="vertical-align: top;">O<br> </td>
-<td style="vertical-align: top;">Binary<br> </td>
-<td style="vertical-align: top;"> <p>This file
+WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">21
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY<br>
+
+
+(PLOT2D_XY_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>This file
 contains data of the two-dimensional horizontal
 cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>)
@@ -588,5 +1858,9 @@
 local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
 and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.&nbsp;
-</p> <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
+      </p>
+
+
+      
+      <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
 = <i>.T.</i> each processing element writes the data of
 its subdomain
@@ -608,24 +1882,132 @@
 possibly existing files of the other cross sections (xz and/or yz)
 and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
-are also combined.&nbsp; </p> <p>Further information
+are also combined.&nbsp; </p>
+
+
+      
+      <p>Further information
 about the output of plots of
 two-dimensional cross sections is found in the description of the run
 parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">22<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">22<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ<br>
+
+
+(PLOT2D_XZ_O) </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>This file contains
 the data of the xz
 cross sections written by the model.&nbsp; </p>
+
+
 The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
-applies to this file, respectively </td> </tr> <tr>
-<td style="vertical-align: top; text-align: center;">23<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains
+applies to this file, respectively </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">23<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ<br>
+
+
+      <font color="#000000">(PLOT2D_YZ_O)</font></td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>This file contains
 the data of the xz
 cross sections written by the model.&nbsp; </p>
+
+
 The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
-applies to this file, respectively </td> </tr> <tr>
-<td style="vertical-align: top; text-align: center;">27<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL </td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td>
-<td style="vertical-align: top;"> <p>NAMELIST -
+applies to this file, respectively </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">27<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL<br>
+
+
+(PLOT2D_XY_LOCAL_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST -
 parameter sets, with which the plot layout of the
 data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
@@ -635,5 +2017,9 @@
 field
 present at the file PLOT2D_XY). After the model run these parameter
-sets can be edited by the user, if neccessary.&nbsp; </p> <p>Additionally
+sets can be edited by the user, if neccessary.&nbsp; </p>
+
+
+      
+      <p>Additionally
 ISO2D still needs another so-called global
 parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>.
@@ -650,25 +2036,138 @@
 (only then e.g. when the final value of the global ISO2D - parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
 is known), while the local parameter sets are written continuously
-to the file PLOT2D_XY_LOCAL during the run.</p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">28<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL </td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td>
-<td style="vertical-align: top;"> <p>NAMELIST -
+to the file PLOT2D_XY_LOCAL during the run.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">28<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL<br>
+
+
+      <font color="#000000">(PLOT2D_XZ_LOCAL_O)</font>
+      </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST -
 parameter sets, with which the plot layout of the
 data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.&nbsp;
-</p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
-applies to this file, respectively. </p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">29<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL </td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td>
-<td style="vertical-align: top;"> <p>NAMELIST -
+      </p>
+
+
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
+applies to this file, respectively. </p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">29<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL<br>
+
+
+      <font color="#000000">(PLOT2D_YZ_LOCAL_O)</font></td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST -
 parameter sets, with which the plot layout of the
 data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.&nbsp;
-</p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
-applies to this file, respectively. </p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">30<br>
-</td> <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>This file contains
+      </p>
+
+
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
+applies to this file, respectively. </p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">30<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA<br>
+
+
+(PLOT3D_DATA_O) </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>This file contains
 the data of the three-dimensional arrays
 (see <a href="chapter_4.2.html#data_output">data_output</a>)
@@ -685,5 +2184,9 @@
 the file PLOT3D_FLD by the user after the end of the model run (e.g.
 with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR
-&gt;&gt; PLOT3D_FLD</span>").&nbsp; </p> <p>With
+&gt;&gt; PLOT3D_FLD</span>").&nbsp; </p>
+
+
+      
+      <p>With
 parallel runs each processing element writes the data of
 its subdomain to a separate file with the name
@@ -701,5 +2204,9 @@
 found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
 also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>)
-are combined.&nbsp; </p> <p>With parallel runs the
+are combined.&nbsp; </p>
+
+
+      
+      <p>With parallel runs the
 output of data of large volume is also
 possible in compressed form. For this purpose the initialization
@@ -714,18 +2221,96 @@
 and a further entry in the MRUN-configuration file are needed. More
 details can be found in <a href="chapter_4.5.6.html">chapter
-4.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">31<br>
-</td> <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;"> <p>Coordinate
+4.5.6</a>.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">31<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>Coordinate
 information concerning
 the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
-needed by the visualization software AVS.&nbsp; </p> <p>The
+needed by the visualization software AVS.&nbsp; </p>
+
+
+      
+      <p>The
 file PLOT3D_COOR should be saved by the user into the same
-permanent directory as the file PLOT3D_DATA.&nbsp; </p> <p>For
-parallel runs PLOT3D_COOR is written by PE0 only.</p> </td>
-</tr> <tr> <td style="vertical-align: top; text-align: center;">32<br>
-</td> <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
-AVS-Fld </td> <td style="vertical-align: top;"> <p>AVS-fld-file
+permanent directory as the file PLOT3D_DATA.&nbsp; </p>
+
+
+      
+      <p>For
+parallel runs PLOT3D_COOR is written by PE0 only.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">32<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+AVS-Fld </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>AVS-fld-file
 describing the three-dimensional
 array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>,
-needed by the visualization software AVS.&nbsp; </p> <p>This
+needed by the visualization software AVS.&nbsp; </p>
+
+
+      
+      <p>This
 file describes the structure of the file PLOT3D_DATA
 (e.g. number of arrays, array dimensions, data type etc.). It uses the
@@ -745,5 +2330,9 @@
 that AVS can find the file PLOT3D_DATA without any problems. If the two
 files lie in different directories, then the path name of the file
-PLOT3D_DATA must be added.&nbsp; </p> <p>AVS-fld-files
+PLOT3D_DATA must be added.&nbsp; </p>
+
+
+      
+      <p>AVS-fld-files
 are expected by AVS to have the
 suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font>
@@ -754,5 +2343,9 @@
 if&nbsp;"<span style="font-family: monospace;">fld</span>"
 is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column
-6 </a>of the file connection statement.&nbsp; </p> <p>Likewise,
+6 </a>of the file connection statement.&nbsp; </p>
+
+
+      
+      <p>Likewise,
 AVS expects information about the coordinate
 system underlying the arrays on this file. This information is output
@@ -763,14 +2356,51 @@
 MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR
 &gt;&gt;
-PLOT3D_FLD&rdquo;).&nbsp; </p> <p>For parallel
-runs, PLOT3D_FLD is produced by PE0 only.</p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">33
-</td> <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
-AVS-Fld </td> <td style="vertical-align: top;"> <p>File
+PLOT3D_FLD&rdquo;).&nbsp; </p>
+
+
+      
+      <p>For parallel
+runs, PLOT3D_FLD is produced by PE0 only.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">33
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+AVS-Fld </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>File
 for the description of the coordinate information output
 by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
 which is needed for the visualization of three-dimensional array data
-by visualization-software AVS.&nbsp; </p> <p>This
+by visualization-software AVS.&nbsp; </p>
+
+
+      
+      <p>This
 file describes the structure of the file PLOT3D_COOR
 (e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format.
@@ -785,5 +2415,9 @@
 registered as "unknown" in the file
 PLOT3D_FLD_COOR and the actual name
-must be inserted later by hand.&nbsp; </p> <p>AVS
+must be inserted later by hand.&nbsp; </p>
+
+
+      
+      <p>AVS
 expects the information contained in the file
 PLOT3D_FLD_COOR, as well as the remaining information about the
@@ -794,14 +2428,85 @@
 MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR
 &gt;&gt;
-PLOT3D_FLD&rdquo;).&nbsp; </p> <p>For parallel
-runs, PLOT3D_FLD_COOR is written by PE0 only.</p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">
-<p align="center">40&nbsp; </p> <p align="center">and/or&nbsp; <br>
-possibly&nbsp; </p> <p align="center">40-49</p>
-</td> <td style="vertical-align: top;"> <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA&nbsp; </p>
-<p>and/or&nbsp; <br>
+PLOT3D_FLD&rdquo;).&nbsp; </p>
+
+
+      
+      <p>For parallel
+runs, PLOT3D_FLD_COOR is written by PE0 only.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">
+      
+      <p align="center">40&nbsp; </p>
+
+
+      
+      <p align="center">and/or&nbsp; <br>
+
+
 possibly&nbsp; </p>
+
+
+      
+      <p align="center">40-49</p>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA<br>
+
+
+(PLOT1D_DATA_O) </p>
+
+
+      
+      <p>and/or&nbsp; <br>
+
+
+possibly&nbsp; </p>
+
+
 PLOT1D_DATA_0&nbsp; <br>
-PLOT1D_DATA_1&nbsp; </td> <td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>This file contains
+
+
+PLOT1D_DATA_1<br>
+
+
+...<br>
+
+
+      <br>
+
+
+(PLOT1D_DATA<span style="font-weight: bold;">_O</span>_0&nbsp;<br>
+
+
+      <font color="#000000">PLOT1D_DATA<span style="font-weight: bold;">_O</span>_1 <br>
+
+
+      </font><font color="#000000">...)<span style="font-weight: bold;"></span>&nbsp;</font></td>
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>This file contains
 data (possibly horizontally and/or
 temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>)
@@ -818,9 +2523,19 @@
 (<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
 means that the file starts with the data of the u-component profile,
-followed by the v-component profile, etc.).&nbsp;</p> <p><br>
+followed by the v-component profile, etc.).&nbsp;</p>
+
+
+      
+      <p><br>
+
+
 The data can only be visualized with <span style="font-weight: bold;">profil</span>
 using NAMELIST-parameter sets, which are saved by the
 model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp;
-</p> <p>The profile data written to the file are described
+      </p>
+
+
+      
+      <p>The profile data written to the file are described
 with the
 run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
@@ -847,5 +2562,9 @@
 to the file name (e.g. PLOT1D_DATA_1). The name of the file with the
 data of the total
-domain in this case reads PLOT1D_DATA_0.&nbsp; </p> <p>For
+domain in this case reads PLOT1D_DATA_0.&nbsp; </p>
+
+
+      
+      <p>For
 presentation in the same plot, profile data of the restart
 runs can be attached to existing data of preceding runs of a job chain.
@@ -857,10 +2576,40 @@
 wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
 = .T.</span> and "<span style="font-family: monospace;">tra</span>"
-must be specified together)!&nbsp; </p> <p>Further
+must be specified together)!&nbsp; </p>
+
+
+      
+      <p>Further
 information about output of
 vertical profile data is given in the description of the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">80 </td>
-<td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/ </td>
-<td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">80
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/<br>
+
+
+(PARTICLE_INFOS<span style="font-weight: bold;">_O</span>/)
+      </td>
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+      <td style="vertical-align: top;">This
 file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles
 package</a>). It contains statistical informations about the
@@ -869,9 +2618,33 @@
 single PE. These informations are output after every timestep if
 switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>.
-</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">81 </td>
-<td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR
-</td> <td style="vertical-align: top;">O </td>
-<td style="vertical-align: top;">Ascii/<br>
-NAMELIST </td> <td style="vertical-align: top;">This
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">81
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR<br>
+
+
+(PLOTSP_X_PAR_O)</td>
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+      <td style="vertical-align: top;">Ascii/<br>
+
+
+NAMELIST </td>
+
+
+      <td style="vertical-align: top;">This
 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
 package</a>). It contains the NAMELIST parameter set, with which
@@ -880,10 +2653,20 @@
 of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
 can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br>
-<p>It contains the so-called RAHMEN (frame)- and
+
+
+      
+      <p>It contains the so-called RAHMEN (frame)- and
 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or
 &amp;CROSS</span>)
 needed by <span style="font-weight: bold;">profil</span>.
 The user can edit these parameter sets (and thus all details of the
-plot layout) after the run.<br> </p> <p>By default,
+plot layout) after the run.<br>
+
+
+      </p>
+
+
+      
+      <p>By default,
 for one quantity, all spectra at different heights
 are plotted into a single panel. Different colors and line styles are
@@ -892,6 +2675,40 @@
 additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
 additional pages will be plotted for each single output time. </p>
-</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">82<br>
-</td> <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">82<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA<br>
+
+
+(PLOTSP_X_DATA_O) </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">This
 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
 package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
@@ -900,9 +2717,18 @@
 using NAMELIST parameter sets, which are written by
 the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
-<br>
+
+
+      <br>
+
+
 Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
 for actual plotting, this file contains all data of spectra specified
 by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br>
-<br> <font>Each data point of a spectrum is output in a
+
+
+      <br>
+
+
+      <font>Each data point of a spectrum is output in a
 single line
 (1st column:
@@ -912,11 +2738,46 @@
 subsequent columns. </font>The order
 of the data in the file follows the order used in the assignment for <span style="font-style: italic;"></span><span style="font-style: italic;"></span><a href="chapter_4.2.html#data_output_sp">data_output_sp</a>.<br>
-<br>
+
+
+      <br>
+
+
 For orientation, a header of comment lines (one for each height level)
 is placed in front of the spectral data of each quantity. They indicate
 the respective quantity and the output time. The text of these comment
-lines is used as a legend in the plot. </td> </tr> <tr>
-<td style="vertical-align: top; text-align: center;">83<br>
-</td> <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR </td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This
+lines is used as a legend in the plot. </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">83<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR<br>
+
+
+(PLOTSP_Y_PAR_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">This
 file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
 package</a>). It contains the NAMELIST parameter set, with which
@@ -925,8 +2786,46 @@
 of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
 can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br>
-<br>
+
+
+      <br>
+
+
 For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
-</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">84<br>
-</td> <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii<br> </td> <td style="vertical-align: top;">This
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">84<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA<br>
+
+
+(PLOTSP_Y_DATA_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">This
 file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
 package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
@@ -935,13 +2834,52 @@
 using NAMELIST parameter sets, which are written by
 the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
-<br>
+
+
+      <br>
+
+
 For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td>
-</tr> <tr> <td style="vertical-align: top; text-align: center;">85<br>
-</td> <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td> <td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Binary<br> </td> <td style="vertical-align: top;">This
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">85<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/<br>
+
+
+(PARTICLE_DATA<span style="font-weight: bold;">_O</span>/)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">This
 file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
 package</a>) and contains all particle data for one or several
 output
 times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
-<br>
+
+
+      <br>
+
+
 The first record of this file contains an identification string (PALM
 version number, run identifier, etc., 80 characters long). The second
@@ -953,9 +2891,35 @@
 the actual particle data. A FORTRAN TYPE structure is used for storing
 the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span>
-for the detailed format.</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90</td>
-<td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
-DATA_IN/</td> <td style="vertical-align: top;">I<br>
-</td> <td style="vertical-align: top;">Binary<br>
-</td> <td style="vertical-align: top;">Binary
+for the detailed format.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90</td>
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
+
+
+DATA_IN/</td>
+
+
+      <td style="vertical-align: top;">I<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary
 data, which are read in by the model at the beginning
 of a restart run (see <a href="chapter_3.3.html">chapter
@@ -971,5 +2935,10 @@
 The
 number of processors which can be used must not be changed during a job
-chain and/or if a job chain is continued. <br> <br>
+chain and/or if a job chain is continued. <br>
+
+
+      <br>
+
+
 The first record of this file contains a version number (four character
 string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>,
@@ -992,9 +2961,41 @@
 attributes. For detailed informations about the file format see the
 corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span>
-.<br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90<br>
-</td> <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
-DATA_OUT/</td> <td style="vertical-align: top;">O<br>
-</td> <td style="vertical-align: top;">Binary<br>
-</td> <td style="vertical-align: top;">Binary
+.<br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
+
+
+DATA_OUT/</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Binary
 data, which are output at the end of the
 run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
@@ -1004,22 +3005,109 @@
 package</a>). For a more detailed description of the file
 structure see <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
-</tr> <tr> <td style="vertical-align: top; text-align: center;">90<br>
-</td> <td style="vertical-align: top;"> <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
-<p>and/or&nbsp; <br>
-possibly&nbsp; </p> <p>PLOT1D_PAR_0&nbsp; <br>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR<br>
+
+
+(PLOT1D_PAR_O) </p>
+
+
+      
+      <p>and/or&nbsp; <br>
+
+
+possibly&nbsp; </p>
+
+
+      
+      <p>PLOT1D_PAR_0&nbsp; <br>
+
+
 PLOT1D_PAR_1&nbsp; <br>
+
+
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 .&nbsp; <br>
+
+
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 .&nbsp; <br>
+
+
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 .&nbsp; <br>
-PLOT1D_PAR_9</p> </td> <td style="vertical-align: top;">O<br>
-</td> <td style="vertical-align: top;">Ascii/
-NAMELIST<br> </td> <td style="vertical-align: top;">
-<p>NAMELIST parameter set, with which the layout of a plot
+
+
+PLOT1D_PAR_9</p>
+
+
+      
+      <p></p>
+
+
+      
+      <p>(PLOT1D_PAR<span style="font-weight: bold;">_O</span>_0&nbsp;
+      <br>
+
+
+PLOT1D_PAR<font color="#000000"><span style="font-weight: bold;">_O</span></font>_1&nbsp;
+      <br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+
+
+PLOT1D_PAR<font color="#000000"><span style="font-weight: bold;">_O</span></font>_9)</p>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/
+NAMELIST<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST parameter set, with which the layout of a plot
 of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a>
 can be steered, if these data are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.&nbsp;
-</p> <p>This file contains the so-called RAHMEN (frame)-
+      </p>
+
+
+      
+      <p>This file contains the so-called RAHMEN (frame)-
 and
 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or
@@ -1032,11 +3120,19 @@
 into which plane and how these planes are arranged on the
 plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
-<a href="chapter_4.2.html#profile_columns">profile_columns</a>
+      <a href="chapter_4.2.html#profile_columns">profile_columns</a>
 and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.&nbsp;
-</p> <p>The file PLOT1D_PAR is created by the model
+      </p>
+
+
+      
+      <p>The file PLOT1D_PAR is created by the model
 briefly before
 the end of a run. If a model run crashes uncontrolled (run time
 errors or CPU - time exceeded), this file is usually missing, although
-profile data were saved to the file PLOT1D_DATA.&nbsp; </p> <p>If
+profile data were saved to the file PLOT1D_DATA.&nbsp; </p>
+
+
+      
+      <p>If
 the model has to create profiles for different subdomains
 (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
@@ -1044,5 +3140,9 @@
 the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of
 the file with NAMELIST parameters of the total domain is
-PLOT1D_PAR_0.&nbsp; </p> <p>For presentation in the
+PLOT1D_PAR_0.&nbsp; </p>
+
+
+      
+      <p>For presentation in the
 same plot, profile data of the restart
 runs can be appended to existing data of preceding runs of a job chain.
@@ -1055,9 +3155,43 @@
 wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
 = .T.</span> and "<span style="font-family: monospace;">tra</span>"
-must be specified together)!</p> </td> </tr> <tr>
-<td style="vertical-align: top; text-align: center;">90<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
-NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
+must be specified together)!</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL<br>
+
+
+(PLOT2D_XY_GLOBAL_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+NAMELIST</td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST
 parameter set, with which the plot layout
 of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
@@ -1070,5 +3204,8 @@
 will be drawn onto a separate page (thus no color shading
 presentation, no vector arrows, streamlines etc.).&nbsp; </p>
-<p>Additionally <span style="font-weight: bold;">iso2d</span>
+
+
+      
+      <p>Additionally <span style="font-weight: bold;">iso2d</span>
 needs the so-called local parameter
 sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
@@ -1089,26 +3226,127 @@
 to the file PLOT2D_XY_LOCAL during the run. Since the file
 PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit
-90 is used, which is also used for other files.</p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">90<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
-NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
+90 is used, which is also used for other files.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL<br>
+
+
+(PLOT2D_XZ_GLOBAL_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+NAMELIST</td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST
 parameter set, with which the plot layout of the data
 in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.&nbsp;
-</p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
-applies to this file, respectively.</p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">90<br>
-</td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td>
-<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
-NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
+      </p>
+
+
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
+applies to this file, respectively.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL<br>
+
+
+(PLOT2D_YZ_GLOBAL_O)</td>
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+NAMELIST</td>
+
+
+      <td style="vertical-align: top;">
+      
+      <p>NAMELIST
 parameter set, with which the plot layout of the data
 in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
 can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.&nbsp;
-</p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
-applies to this file, respectively.</p> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">90</td>
-<td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;">Ascii</td> <td>Two-dimensional&nbsp;<font color="#000000">topography height information</font>
+      </p>
+
+
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
+applies to this file, respectively.</p>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">90</td>
+
+
+      <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td>
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+      <td style="vertical-align: top;">Ascii</td>
+
+
+      <td>Two-dimensional&nbsp;<font color="#000000">topography
+height information</font>
 in m.<br>
+
+
 In case of &nbsp;<a href="chapter_4.1.html#topography">topography</a>
 = <span style="font-style: italic;">'read_from_file'</span>
@@ -1117,136 +3355,495 @@
 a free floating point format. The data on file are laid out naturally,
 i.e. in W-E orientation horizontally and in S-N orientation vertically,
-they must thus be organized as follows:<br> <ul> <li>each
+they must thus be organized as follows:<br>
+
+
+      
+      <ul>
+
+
+        <li>each
 line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li>
-<li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the
+
+
+        <li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the
 bottom line for <span style="font-style: italic;">j = 0</span>
-(South),</li> <li>individual data must be separated by at
-least one blank.</li> </ul>
-Layout sketch:<br> <span style="font-family: Cumberland AMT;">&nbsp;
+(South),</li>
+
+
+        <li>individual data must be separated by at
+least one blank.</li>
+
+
+      
+      </ul>
+
+
+Layout sketch:<br>
+
+
+      <span style="font-family: Cumberland AMT;">&nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;N<br>
+
+
 &nbsp; &nbsp; (0,ny) &nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny)
 &nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) &nbsp;
 ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) &nbsp;
 &nbsp; &nbsp;<span style="font-family: Times New Roman,Times,serif;"></span></span></font><font color="#000000">&nbsp;top of file</font><font color="#000000"><span style="font-family: Cumberland AMT;"><span style="font-family: Times New Roman,Times,serif;"></span></span></font><br>
-<font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
+
+
+      <font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
 (0,ny-1)&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-1)&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-1)
 ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) &nbsp;<br>
-</span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W &nbsp;
+
+
+      </span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W &nbsp;
 (0,ny-2)&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-2)&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-2)
 ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) &nbsp; E<br>
-</span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp;
+
+
+      </span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp;
 &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
+
+
 &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
-&nbsp;:<br> </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
+&nbsp;:<br>
+
+
+      </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp;
+&nbsp;
 (0,0) &nbsp;&nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0)
 &nbsp;&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0)
 &nbsp; &nbsp;...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0)
 &nbsp; &nbsp; &nbsp;&nbsp;</span></font></font></font><font color="#000000">&nbsp;bottom of file</font><br>
-<font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
+
+
+      <font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;S</span></font><br>
-<span style="font-family: Arial;"></span><br>
+
+
+      <span style="font-family: Arial;"></span><br>
+
+
 These data must exactly match the horizontal grid.<br>
+
+
 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 different data formats.</td> <td><br> </td>
-</tr> <tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000">Binary/<br>
+to allow different data formats.</td>
+
+
+      <td><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF<br>
+
+
+(DATA_2D_XY_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file
+
+
+format</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file
 contains data of the two-dimensional horizontal
 cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF<br>
+
+
+(DATA_2D_XZ_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the two-dimensional vertical (xz)
 cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF<br>
+
+
+(DATA_2D_YZ_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the two-dimensional vertical
 (yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF<br>
+
+
+(DATA_1D_PR_NETCFD_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF<br>
+
+
+(DATA_1D_TS_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF<br>
+
+
+(DATA_3D_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF<br>
+
+
+(DATA_1D_SP_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/</font></td>
-<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/<br>
+
+
+(DATA_PRT_NETCDF<span style="font-weight: bold;">_O</span>/)</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td style="vertical-align: top;"><br> </td> </tr>
-<tr> <td style="vertical-align: top; text-align: center;">109</td>
-<td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td>
-<td align="left" valign="top">I/O</td> <td align="left" valign="top">Binary/<br>
+
+
+      <td style="vertical-align: top;"><br>
+
+
+      </td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top; text-align: center;">109</td>
+
+
+      <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF<br>
+
+
+(DATA_1D_PTS_NETCDF_O)</td>
+
+
+      <td align="left" valign="top">I/O</td>
+
+
+      <td align="left" valign="top">Binary/<br>
+
+
 NetCDF-<br>
-format</td> <td align="left" valign="top">This
+
+
+format</td>
+
+
+      <td align="left" valign="top">This
 file contains data of the timeseries of particle quantities (<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">see <a href="chapter_4.2.html#dt_prel">dt_prel</a>)
 in NetCDF format.&nbsp;</font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data
 in this file can be visualized by any graphic software which provides a
 NetCDF interface (e.g. <span style="font-weight: bold;">NCL
-</span>or<span style="font-weight: bold;"> ferret</span>).
+      </span>or<span style="font-weight: bold;">
+ferret</span>).
 For a list of available output quantities see </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"> <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>.</font></font></font></font></font><br>
-<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
-</font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of
+
+
+      <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
+
+
+      </font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of
 using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
 seperate time series are output for each of the groups. The long names
@@ -1254,54 +3851,220 @@
 timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle
 group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
-<br> </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the
+
+
+      <br>
+
+
+      </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the
 PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp;
 4.5.1</a>.</font></font></font></font></td>
-<td align="left" valign="top"></td> </tr>
-<tr> <td style="text-align: center; vertical-align: top;">111</td>
-<td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td>
-<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td align="left" valign="top"></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="text-align: center; vertical-align: top;">111</td>
+
+
+      <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF<br>
+
+
+(DATA_2D_XY_AV_NETCDF_O)</td>
+
+
+      <td style="vertical-align: top;">I/O</td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+
+
+format</font></font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
 contains data of the temporally averaged two-dimensional horizontal
 cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-<td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">112</td>
-<td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td>
-<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="text-align: center; vertical-align: top;">112</td>
+
+
+      <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF<br>
+
+
+(DATA_2D_XZ_AV_NETCDF_O)</td>
+
+
+      <td style="vertical-align: top;">I/O</td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally
+
+
+format</font></font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file
+contains data of the temporally
 averaged two-dimensional vertical (xz)
 cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
-<td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">113</td>
-<td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td>
-<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="text-align: center; vertical-align: top;">113</td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF<br>
+
+
+(DATA_2D_YZ_AV_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;">I/O</td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally
+
+
+format</font></font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file
+contains data of the temporally
 averaged two-dimensional vertical
 (yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
-<td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">116</td>
-<td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td>
-<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
+      <td></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td style="text-align: center; vertical-align: top;">116</td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF<br>
+
+
+(DATA_3D_AV_NETCDF_O)</font></td>
+
+
+      <td style="vertical-align: top;">I/O</td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+
 NetCDF-<br>
-format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally
+
+
+format</font></font></font></td>
+
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file
+contains data of the temporally
 averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
 in NetCDF format. The data in this file can be visualized by any
-graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+
+      <br>
+
+
 More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
-<td></td> </tr> </tbody>
-</table><font color="#000000"><br>
+
+
+      <td></td>
+
+
+    </tr>
+
+
+  
+  </tbody>
+</table>
+
+
+<font color="#000000"><br>
+
+
 </font><br>
-<font color="#000080"><font color="#000080"><a href="chapter_3.3.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>&nbsp;
+
+
+<font color="#000080"><font color="#000080"><a href="chapter_3.3.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>
+
+
+&nbsp;
 <br>
+
+
 &nbsp;
 <span style="font-style: italic;">Last change:</span>
 $Id$<br>
-</font><br></body></html>
+
+
+</font><br>
+
+
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.7.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.7.html	(revision 103)
+++ palm/trunk/DOC/app/chapter_3.7.html	(revision 108)
@@ -1,12 +1,29 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><head>
-<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
-chapter 3.7</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040809;13460943"> <meta name="CHANGED" content="20041112;15085727"> <meta name="KEYWORDS" content="parallel LES model"> <style>
+<html>
+<head>
+
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+  <title>PALM chapter 3.7</title>
+ 
+  <meta name="GENERATOR" content="StarOffice 7 (Win32)">
+ 
+  <meta name="AUTHOR" content="Siegfried Raasch">
+ 
+  <meta name="CREATED" content="20040809;13460943">
+ 
+  <meta name="CHANGED" content="20041112;15085727">
+ 
+  <meta name="KEYWORDS" content="parallel LES model">
+ 
+  <style>
 <!--
 @page { size: 21cm 29.7cm }
 -->
-</style></head>
+  </style>
+</head>
 
-<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.7 Optional software packages</h3>
+<body style="direction: ltr;" lang="en-US">
+<h3 style="line-height: 100%;">3.7 Optional software packages</h3>
+
 <p style="line-height: 100%;">Starting from version 2.1
 PALM includes
@@ -19,4 +36,5 @@
 compilation time as well as the memory demand of the model is limited
 to the real needs. </p>
+
 <p style="line-height: 100%;">To use software packages in
 a model run,
@@ -31,7 +49,13 @@
 the <b>mrun</b> call
 has to be: </p>
-<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">mrun ... -p
+
+<ul>
+ 
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">mrun ... -p
 &ldquo;package1 package2&rdquo; </font>.</tt></p>
-</ul><p style="line-height: 100%;">Starting from version 3.2, the particles-package is part of the default model, so it does not have to be switched on using <span style="font-weight: bold;">mrun</span>-option <span style="font-family: Courier New,Courier,monospace;">-p</span>. However, the respective parameters have still to be set by using the NAMELIST group <span style="font-family: Courier New,Courier,monospace;">particles_par</span>.</p><p style="line-height: 100%;">Further package
+
+</ul>
+<p style="line-height: 100%;">Starting from version 3.2, the particles-package is part of the default model, so it does not have to be switched on using <span style="font-weight: bold;">mrun</span>-option <span style="font-family: Courier New,Courier,monospace;">-p</span>. However, the respective parameters have still to be set by using the NAMELIST group <span style="font-family: Courier New,Courier,monospace;">particles_par</span>.</p>
+<p style="line-height: 100%;">Further package
 names can be added to
 the list, separated by blanks. If the respective packages permit user
@@ -43,41 +67,113 @@
 group name is given in the table below. For the example above one
 would have to add the following lines to PARIN (example): &nbsp; </p>
-<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">&amp;namelist_packagename1
+
+<ul>
+ 
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">&amp;namelist_packagename1
 var1 = 1,0, var2 =
 &ldquo;abcd&rdquo; /</font></tt><font style="font-size: 10pt;" size="2"> </font> </p>
-<p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">&amp;namelist_packagename2
+
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">&amp;namelist_packagename2
 var3 = .TRUE.,
 var4 = 0 /</font></tt></p>
-</ul><p style="margin-bottom: 0cm; line-height: 100%;">The
+
+</ul>
+<p style="margin-bottom: 0cm; line-height: 100%;">The
 following
 packages are available: <br>
+
 &nbsp; <br>
+
 &nbsp; </p>
-<table border="1" cellpadding="2" cellspacing="2" width="100%"> <tbody> <tr> <td> <p><b>Package
-name:</b></p> </td> <td> <p><b>NAMELIST
-group name:</b></p> </td> <td> <p><b>Functionality:</b></p>
-</td> <td> <p><b>Control parameter:</b></p>
-</td> </tr> <tr valign="top"> <td> <p>--- (see above)</p>
-</td> <td> <p>particles_par</p> </td> <td>
-<p>Release and advection of particles. The particle sources can
+
+<table border="1" cellpadding="2" cellspacing="2" width="100%">
+ <tbody>
+ <tr>
+ <td> 
+      <p><b>Package
+name:</b></p>
+ </td>
+ <td> 
+      <p><b>NAMELIST
+group name:</b></p>
+ </td>
+ <td> 
+      <p><b>Functionality:</b></p>
+
+      </td>
+ <td> 
+      <p><b>Control parameter:</b></p>
+
+      </td>
+ </tr>
+ <tr valign="top">
+ <td> 
+      <p>--- (see above)</p>
+
+      </td>
+ <td> 
+      <p>particles_par</p>
+ </td>
+ <td>
+      <p>Release and advection of particles. The particle sources can
 additionally be defined by the user in subroutine <tt><font style="font-size: 10pt;" size="2">user_init_particles</font></tt>
-.</p> </td> <td> <p>see section 4.2</p>
-</td> </tr> <tr valign="top"> <td> <p>dvrp_graphics</p>
-</td> <td> <p>dvrp_graphics_par</p> </td>
-<td> <p>Graphical output with the dvrp software of the
+.</p>
+ </td>
+ <td> 
+      <p>see section 4.2</p>
+
+      </td>
+ </tr>
+ <tr valign="top">
+ <td> 
+      <p>dvrp_graphics</p>
+
+      </td>
+ <td> 
+      <p>dvrp_graphics_par</p>
+ </td>
+
+      <td> 
+      <p>Graphical output with the dvrp software of the
 RRZN. This is
 only available on the IBM Regatta "hanni" of the HLRN. Possible output
 are iso-surfaces, cross-sections and particles (if the particle package
-is selected). The use of this package is described in section <a href="chapter_4.5.7.html">4.5.7</a>.</p> </td>
-<td> <p>see section 4.2</p> </td> </tr>
-<tr valign="top"> <td> <p>spectra</p> </td>
-<td> <p>spectra_par</p> </td> <td> <p>Computation
+is selected). The use of this package is described in section <a href="chapter_4.5.7.html">4.5.7</a>.</p>
+ </td>
+
+      <td> 
+      <p>see section 4.2</p>
+ </td>
+ </tr>
+
+    <tr valign="top">
+ <td> 
+      <p>spectra</p>
+ </td>
+
+      <td> 
+      <p>spectra_par</p>
+ </td>
+ <td> 
+      <p>Computation
 and output of horizontal power spectra of the
-prognostic variables. </p> </td> <td> <p>see
+prognostic variables. </p>
+ </td>
+ <td> 
+      <p>see
 section <a href="chapter_4.2.html#spectra_package">4.2</a></p>
-</td> </tr> </tbody>
-</table><hr>
-<p style="line-height: 100%;"><br><font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+
+      </td>
+ </tr>
+ 
+  </tbody>
+</table>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.8.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="right.gif" name="Grafik3"></font></a></font></font></p>
+
 <p style="line-height: 100%;"><i>Last
 change:&nbsp;</i> $Id$</p>
-</body></html>
+
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.8.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.8.html	(revision 108)
+++ palm/trunk/DOC/app/chapter_3.8.html	(revision 108)
@@ -0,0 +1,149 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+
+
+  
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+
+  
+
+
+  
+  <title>PALM chapter 3.8</title>
+  <meta name="GENERATOR" content="StarOffice 7 (Win32)">
+
+
+  
+  <meta name="AUTHOR" content="Siegfried Raasch">
+
+
+  
+  <meta name="CREATED" content="20040809;13460943">
+
+
+  
+  <meta name="CHANGED" content="20041112;15085727">
+
+
+  
+  <meta name="KEYWORDS" content="parallel LES model">
+
+
+  
+  <style>
+<!--
+@page { size: 21cm 29.7cm }
+-->
+  </style>
+</head>
+
+
+<body style="direction: ltr;" lang="en-US">
+
+
+<h3 style="line-height: 100%;">3.8 Coupled model runs</h3>
+
+
+<p style="line-height: 100%;">Starting from version 3.4
+PALM allows coupled atmosphere-ocean model runs. By analogy with the
+modular structure of PALM, <span style="font-weight: bold;">mrun</span>
+starts the coupled model as two concurrent executables, the atmosphere
+version and&nbsp;the ocean version of PALM.</p>
+
+
+<p style="line-height: 100%;">Currently, the coupler
+is at an experimental stage using a simple MPI2 intercommunicator that
+matches the atmosphere and ocean processors one-to-one. This approach
+has&nbsp;limited flexibility and performance, because it requires
+identical horizontal numerical grids and it uses the same number of
+atmosphere and ocean processors, which does not necessarily guarrantee
+a good load balancing.</p>
+
+
+<p style="line-height: 100%;">The coupler establishes a
+one-way interaction between the
+atmosphere and the ocean. The atmosphere sends its bottom surface
+fluxes
+(temperature, humidity, momentum) to the ocean. The ocean sends its top
+surface temperature to the atmosphere. The atmosphere assumes
+saturation of humidity and zero wind speed at its bottom surface. For
+calculations with <a href="chapter_4.1.html#humidity">humidity</a>
+= .T. the atmospheric evaporation leads to a salinity flux in the ocean
+(see e.g. Steinhorn 1991, JPO 21, p. 1681).</p>
+
+
+<p style="line-height: 100%;">To start a
+coupled&nbsp;model run,
+this must be requested with the <b>mrun</b> option <tt><font style="font-size: 10pt;" size="2">-Y</font>.</tt>
+This tells <span style="font-weight: bold;">mrun</span>
+to start two PALM executables. Coupled runs are only possible in
+parallel mode, which means that the <b>mrun</b> option <tt><font style="font-size: 10pt;" size="2">-K parallel</font></tt>
+must also be set.&nbsp;The <b>mrun</b> call
+for coupled runs has to include the following coupling-related options:
+</p>
+
+
+<ul>
+
+
+  
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">mrun </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2"> -K parallel -r
+&ldquo;d3# d3o# </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2">&rdquo;</font></tt><tt><font style="font-size: 10pt;" size="2"> </font></tt><tt><font style="font-size: 10pt;" size="2">-X </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2"> -Y</font></tt><tt>.</tt></p>
+
+
+</ul>
+
+
+<p style="line-height: 100%;">The <tt><font style="font-size: 10pt;" size="2">-X </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2">&nbsp;</font></tt>option
+here specifies the total number of processors assigned to the coupled
+model. Half of them are assigned to each of the two coupled
+executables. Therefore it is advisable to specify an even number
+with&nbsp;<tt><font style="font-size: 10pt;" size="2">-X </font></tt><font style="font-size: 10pt;" size="2">...</font><tt>
+</tt>. Otherwise, in case of an odd total number of processors,
+one processor remains idle.</p>
+
+
+<p style="line-height: 100%;">Each coupled executable has
+its own, unique set of I/O filenames; <a href="chapter_3.4.html#coupled">chapter 3.4</a> gives
+information on file name conventions of coupled runs. The configuration
+file .mrun.config has to be extended for coupled runs. It is
+recommended to duplicate existing file connection identifiers such as
+"d3#", "pr#" etc. using the coupled ocean filenames accordingly. For
+example,&nbsp;the example of the previous chapters could be
+duplicated as follows:</p>
+
+
+<pre style="line-height: 100%;"><a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font style="font-size: 10pt;" size="2"> in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d</font><br><font style="font-size: 10pt;" size="2">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font><br><a href="chapter_3.4.html#BININ"><font style="font-size: 10pt;" size="2">BININ</font></a><font style="font-size: 10pt;" size="2"> in:loc d3f ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><a href="chapter_3.4.html#BINOUT"><font style="font-size: 10pt;" size="2">BINOUT</font></a><font style="font-size: 10pt;" size="2"> out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT _d3d<br>#</font><br><a href="chapter_3.4.html#RUN_CONTROL"><font style="font-size: 10pt;" size="2">RUN_CONTROL</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _rc</font><br><a href="chapter_3.4.html#HEADER"><font style="font-size: 10pt;" size="2">HEADER</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _header</font><br><a href="chapter_3.4.html#PLOT1D_PAR"><font style="font-size: 10pt;" size="2">PLOT1D_PAR</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_par</font><br><a href="chapter_3.4.html#PLOT1D_DATA"><font style="font-size: 10pt;" size="2">PLOT1D_DATA</font></a><font style="font-size: 10pt;" size="2"> out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_in<br>#<br></font><font style="font-size: 10pt;" size="2">PARIN</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> in:job:npe d3<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/INPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">p3d</font><br><font style="font-size: 10pt;" size="2">PARIN<span style="font-weight: bold;">_O</span> in:job:npe d3<span style="font-weight: bold;">o</span>f ~/palm/current_version/JOBS/$fname/INPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">p3df</font><br><font style="font-size: 10pt;" size="2">BININ</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> in:loc d3<span style="font-weight: bold;">o</span>f ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">d3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><font style="font-size: 10pt;" size="2">BINOUT</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">d3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><font style="font-size: 10pt;" size="2">RUN_CONTROL<span style="font-weight: bold;">_O</span></font><font style="font-size: 10pt;" size="2"> out:loc:tr d3<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/MONITORING <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">rc</font><br><font style="font-size: 10pt;" size="2">HEADER</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> out:loc:tr d3<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/MONITORING <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">header</font><br><font style="font-size: 10pt;" size="2">PLOT1D_PAR<span style="font-weight: bold;">_O</span></font><font style="font-size: 10pt;" size="2"> out:loc:tr pr<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">pr_par</font><br><font style="font-size: 10pt;" size="2">PLOT1D_DATA</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> out:loc:tr pr<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">pr_in</font><br></pre>
+
+
+<p style="line-height: 100%;">The coupled ocean model
+filenames in the first column (e.g.<font style="font-size: 10pt;" size="2"><span style="font-family: mon;"> </span><a href="chapter_3.4.html#PARIN">PARIN_O</a></font>)&nbsp;must
+be specified as given in <a href="chapter_3.4.html#coupled">chapter
+3.4</a>; the file connection identifiers (e.g.&nbsp; <font style="font-size: 10pt;" size="2">d3o#</font>)
+and the file name extension (e.g. &nbsp;<font style="font-size: 10pt;" size="2"><span style="font-weight: bold;"><span style="font-family: mon;"></span></span>_</font><font style="font-size: 10pt;" size="2">o_</font><font style="font-size: 10pt;" size="2">p3d</font>)
+may be changed at the user's discretion.</p>
+
+
+
+
+<p style="line-height: 100%;">The coupler requires the
+following parameters to be equal in both <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>:
+<a href="chapter_4.1.html#dx">dx</a>, <a href="chapter_4.1.html#dy">dy</a>, <a href="chapter_4.1.html#nx">nx</a>, <a href="chapter_4.1.html#ny">ny</a>, <a href="chapter_4.2.html#dt_coupling">dt_coupling</a>, <a href="chapter_4.2.html#end_time">end_time</a>, <a href="chapter_4.2.html#restart_time">restart_time</a>,
+<a href="chapter_4.2.html#dt_restart">dt_restart</a>. In the coupled 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; in the coupled 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. The coupled 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>
+<p style="line-height: 100%;">The coupling interval  <a href="chapter_4.2.html#dt_coupling">dt_coupling</a> must be explicity set. In order to ensure synchronous coupling throughout the simulation, <a href="chapter_4.2.html#dt_coupling">dt_coupling</a> should be chosen larger than
+<a href="chapter_4.2.html#dt_max">dt_max</a>.</p>
+<hr>
+<p style="line-height: 100%;"><br>
+
+
+<font color="#000080"><font color="#000080"><a href="chapter_3.7.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="left.gif" name="Grafik1"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+
+
+<p style="line-height: 100%;"><i>Last
+change:&nbsp;</i> ++</p>
+
+
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.0.html	(revision 103)
+++ palm/trunk/DOC/app/chapter_4.0.html	(revision 108)
@@ -1,11 +1,48 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><head>
-<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 4.0</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040809;14214479"> <meta name="CHANGED" content="20041112;15151993"> <meta name="KEYWORDS" content="parallel LES model"> <style>
+<html>
+<head>
+
+
+  
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+
+  
+ 
+  
+  <title>PALM chapter 4.0</title>
+  <meta name="GENERATOR" content="StarOffice 7 (Win32)">
+
+ 
+  
+  <meta name="AUTHOR" content="Siegfried Raasch">
+
+ 
+  
+  <meta name="CREATED" content="20040809;14214479">
+
+ 
+  
+  <meta name="CHANGED" content="20041112;15151993">
+
+ 
+  
+  <meta name="KEYWORDS" content="parallel LES model">
+
+ 
+  
+  <style>
 <!--
 @page { size: 21cm 29.7cm }
 -->
-</style></head>
-<body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">4.0
+  </style>
+</head>
+
+
+<body style="direction: ltr;" lang="en-US">
+
+<h2 style="line-height: 100%;"><font size="4">4.0
 Steering parameters</font></h2>
+
+
 <p style="line-height: 100%;">Before carrying out a model
 run, the user
@@ -17,5 +54,9 @@
 should be, at which times and points plot output are supposed to be
 made, etc. <br>
-</p><p style="line-height: 100%;">These data are
+
+
+</p>
+
+<p style="line-height: 100%;">These data are
 assigned with the help of
 so-called&nbsp;&ldquo;NAMELIST-driven input&rdquo; (FORTRAN -
@@ -31,22 +72,56 @@
 example shows the format of the file
 PARIN: <br>
-&nbsp; </p>
-<ul> <p style="line-height: 100%; font-family: monospace;">&amp;inipar
+
+
+&nbsp; </p>
+
+
+<ul>
+
+ 
+  
+  <p style="line-height: 100%; font-family: monospace;">&amp;inipar
 nx
 = 79, ny = 79, nz = 40, <br>
+
+
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 dx = 50.0, dy = 50.0, dz =
 50.0, <br>
+
+
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 initializing_actions =
 "set_1d-model_profiles", <br>
+
+
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-prandtl_layer = .TRUE.,/ </p> <p style="line-height: 100%; font-family: monospace;">&amp;d3par&nbsp;
-end_time = 9000.0, section_xy = 1, 10, 20,/ </p> <p style="line-height: 100%; font-family: monospace;">&amp;packagename
-var1 = .TRUE. / </p> <p style="line-height: 100%;"><span style="font-family: monospace;">&amp;userpar
+prandtl_layer = .TRUE.,/ </p>
+
+ 
+  
+  <p style="line-height: 100%; font-family: monospace;">&amp;d3par&nbsp;
+end_time = 9000.0, section_xy = 1, 10, 20,/ </p>
+
+ 
+  
+  <p style="line-height: 100%; font-family: monospace;">&amp;packagename
+var1 = .TRUE. / </p>
+
+ 
+  
+  <p style="line-height: 100%;"><span style="font-family: monospace;">&amp;userpar
 abcd = 1234,0,/ </span><br>
+
+
 &nbsp; <br>
+
+
 &nbsp;</p>
-</ul><p style="line-height: 100%;">The parameters
+
+
+</ul>
+
+<p style="line-height: 100%;">The parameters
 are separated into four
 different groups which all start with the so-called NAMELIST group
@@ -65,5 +140,9 @@
 concerning the NAMELIST syntax, refer to
 appropriate FORTRAN manuals. <br>
-</p><p style="line-height: 100%;">Parameters
+
+
+</p>
+
+<p style="line-height: 100%;">Parameters
 belonging to the group <span style="font-family: monospace;">inipar</span>
 are first read by PALM.
@@ -84,8 +163,16 @@
 (see chapter <a href="chapter_3.7.html">3.7</a>),
 further NAMELIST groups may be inserted before the group <span style="font-family: monospace;">userpar</span>.
-</p><p style="line-height: 100%;"><b>The
+</p>
+
+<p style="line-height: 100%;"><b>The
 initialization, run</b> and
 <b>package parameters</b> differ as follows: </p>
-<ul> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
+
+
+<ul>
+
+ <li> 
+    
+    <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
 parameters </b>are steering the basic settings of the model run.
 They
@@ -101,5 +188,13 @@
 value<span style="font-family: thorndale,serif,mon;"> </span><span style="font-family: monospace; font-style: italic;">read_restart_data</span><span style="font-family: thorndale,serif,mon;"> for </span>restart
 runs). <br>
-&nbsp; </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
+
+
+&nbsp; </p>
+
+ </li>
+
+ <li> 
+    
+    <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
 parameters</b> are generally steering actions to be carried out
 during
@@ -111,9 +206,23 @@
 usually keep their values, provided that the NAMELIST input file was
 not changed by the user in the meantime). <br>
-&nbsp; </p> </li> <li> <p style="line-height: 100%;"><b>Package parameters</b>
+
+
+&nbsp; </p>
+
+ </li>
+
+ <li> 
+    
+    <p style="line-height: 100%;"><b>Package parameters</b>
 behave like <b>run parameters</b>. Package parameters
 determine the behavior of
-the additional (not user-defined) software packages . </p> </li>
-</ul><p style="line-height: 100%;">The user-defined
+the additional (not user-defined) software packages . </p>
+
+ </li>
+
+
+</ul>
+
+<p style="line-height: 100%;">The user-defined
 parameters are assigned
 by the user within the NAMELIST group name <tt>&amp;userpar</tt>
@@ -137,4 +246,6 @@
 (described in <a href="chapter_3.2.html">chapter
 3.2</a>) for the execution of a model test run. </p>
+
+
 <p style="line-height: 100%;">PALM assigns default
 values to nearly all parameters. They become effective
@@ -142,9 +253,25 @@
 default values as well as the parameter name, type and its
 explanation are described in the lists of the following subsections. <br>
-&nbsp; </p>
-<hr><p style="line-height: 100%;"><br>
-<font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.1.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>&nbsp;
+
+
+&nbsp; </p>
+
+
+<hr>
+<p style="line-height: 100%;"><br>
+
+
+<font color="#000080"><font color="#000080"><a href="chapter_3.8.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="left.gif" name="Grafik1"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.1.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>
+
+&nbsp;
 <br>
+
+
 &nbsp;<span style="font-style: italic;">Last change:</span>
 $Id$<br>
-</p></body></html>
+
+
+</p>
+
+</body>
+</html>
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>
Index: palm/trunk/DOC/app/chapter_4.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.2.html	(revision 103)
+++ palm/trunk/DOC/app/chapter_4.2.html	(revision 108)
@@ -1,20 +1,109 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html><head>
-<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>PALM chapter 4.2</title></head>
-<body><h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
+<html>
+<head>
+
+
+
+  
+  
+  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+
+
+  
+  
+  <title>PALM chapter 4.2</title>
+</head>
+
+
+<body>
+
+
+<h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
 parameters</a>, <a href="#particle_parameters">particle parameters</a>, and <a href="#Paketparameter">package
 parameters</a></h3>
+
+
+
 <h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3>
-<br><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;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
-</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;">Averaging interval for
-all&nbsp;output of temporally averaged data (in s).<br><br>This
+
+
+
+<br>
+
+
+<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;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
+
+
+
+      </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;">Averaging interval for
+all&nbsp;output of temporally averaged data (in s).<br>
+
+
+      <br>
+
+
+This
 parameter defines the time interval length for temporally averaged data
 (vertical profiles, spectra, 2d cross-sections, 3d volume data). By
@@ -24,27 +113,90 @@
 In any case, <span style="font-weight: bold;">averaging_interval</span>
 &lt;= <span style="font-weight: bold;">dt_data_output_av</span>
-must hold.<br><br>If
+must hold.<br>
+
+
+      <br>
+
+
+If
 an interval is defined, then by default the average is calculated from
 the data values of all timesteps lying within this interval. The number
 of time levels entering into the average can be reduced with the
-parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br><br>If
+parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br>
+
+
+      <br>
+
+
+If
 an averaging interval can not be completed at the end of a run, it
 will be finished at the beginning of the next restart run. Thus for
 restart runs, averaging intervals do not
-necessarily begin at the beginning of the run.<br><br>Parameters
-<a href="#averaging_interval_pr">averaging_interval_pr</a>
+necessarily begin at the beginning of the run.<br>
+
+
+      <br>
+
+
+Parameters
+      <a href="#averaging_interval_pr">averaging_interval_pr</a>
 and <a href="#averaging_interval_sp">averaging_interval_sp</a>
 can be used to define different averaging intervals for vertical
-profile data and spectra, respectively.<br> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
+profile data and spectra, respectively.<br>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
+
+
+
 interval</a><br>
-</span> </td> <td style="vertical-align: top;"><p>Averaging
+
+
+
+      </span> </td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p>Averaging
 interval for output of vertical profiles&nbsp;to
 local
 file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
-</font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
-(in s).&nbsp; </p> <p>If
+      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
+(in s).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If
 this parameter is given a non-zero value, temporally
 averaged vertical profile data are output. By default, profile data
@@ -52,20 +204,61 @@
 limited by the parameter <a href="#dt_dopr">dt_dopr</a>.
 In any case <b>averaging_interval_pr</b> &lt;= <b>dt_dopr
-</b>must
-hold.</p>If an interval is defined, then by default the average
+      </b>must
+hold.</p>
+
+
+If an interval is defined, then by default the average
 is calculated
 from the data values of all timesteps lying within this interval. The
 number of time levels entering into the average can be reduced with the
 parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>.
-<p>If
+      
+      
+      <p>If
 an averaging interval can not be completed at the end of a run, it will
 be finished at the beginning of the next restart run. Thus for restart
 runs, averaging intervals do not
-necessarily begin at the beginning of the run.</p> </td> </tr>
-<tr> <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
-substeps</span></td> <td style="vertical-align: top;">L<br>
-</td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
-<td style="vertical-align: top;">Switch
-to steer the call of the pressure solver.<br> <br>
+necessarily begin at the beginning of the run.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
+
+
+
+substeps</span></td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">Switch
+to steer the call of the pressure solver.<br>
+
+
+ <br>
+
+
+
 In order to speed-up performance, the Poisson equation for perturbation
 pressure (see <a href="#psolver">psolver</a>) can
@@ -80,10 +273,54 @@
 = <span style="font-style: italic;">.T.</span>
 should be used.&nbsp;<span style="font-weight: bold;"></span></td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="fcl_factor"></a><b>cfl_factor</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"> <p><i>0.1,
-0.8 or 0.9</i> <br> <i>(see right)</i></p>
-</td> <td style="vertical-align: top;"> <p lang="en-GB">Time step limiting factor.&nbsp; </p>
-<p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="fcl_factor"></a><b>cfl_factor</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><i>0.1,
+0.8 or 0.9</i> <br>
+
+
+ <i>(see right)</i></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB">Time step limiting factor.&nbsp; </p>
+
+
+
+      
+      
+      <p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
 allowed </span>time step according to CFL and
 diffusion-criterion
@@ -93,9 +330,35 @@
 the maximum allowed timestep. The condition <i>0.0</i>
 &lt; <b>cfl_factor</b>
-&lt; <i>1.0 </i>applies.<br> </span></p>
-<p><span lang="en-GB">The default value of
+&lt; <i>1.0 </i>applies.<br>
+
+
+ </span></p>
+
+
+
+      
+      
+      <p><span lang="en-GB">The default value of
 cfl_factor depends on
-the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br> </span></p> <p><span lang="en-GB">For the third order Runge-Kutta scheme it
-is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br> </span></p> <p><span lang="en-GB">In case of the leapfrog scheme a quite
+the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br>
+
+
+ </span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB">For the third order Runge-Kutta scheme it
+is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br>
+
+
+ </span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB">In case of the leapfrog scheme a quite
 restrictive value of <span style="font-weight: bold;">cfl_factor</span>
 = <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
@@ -104,17 +367,71 @@
 be used with the leapfrog scheme but these are to be determined by
 appropriate test runs.<span style="font-family: times new roman;"><br>
-</span></span></p> <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
+
+
+
+      </span></span></p>
+
+
+ <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
 scheme is <span style="font-weight: bold;">cfl_factor</span>
 = <span style="font-style: italic;">0.8</span> .</font></span></td>
-</tr><tr> <td style="vertical-align: top;"> <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
-</td> <td style="vertical-align: top;">L<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
-<td style="vertical-align: top;"> <p>Switch to
+
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Switch to
 impose random perturbations to the horizontal
-velocity field.&nbsp; </p> <p>With <b>create_disturbances</b>
+velocity field.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>With <b>create_disturbances</b>
 = <i>.T.,</i> random
 perturbations can be imposed to the horizontal velocity field at
 certain times e.g. in order to trigger off the onset of convection,
-etc..<br> </p> <p>The temporal interval between
+etc..<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>The temporal interval between
 these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
 the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a>
@@ -130,7 +447,25 @@
 After this, the arrays of u and v are smoothed by applying a
 Shuman-filter twice and made divergence-free by applying the pressure
-solver.<br> </p> <p>The random number generator to
+solver.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>The random number generator to
 be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br>
-</p> <p>As soon as the desired flow features have
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>As soon as the desired flow features have
 developed
 (e.g.&nbsp; convection has started), further imposing of
@@ -143,16 +478,65 @@
 As soon as the perturbation energy has exceeded this energy limit, no
 more random perturbations are assigned<br>
+
+
+
 .&nbsp; <br>
+
+
+
 Timesteps where a random perturbation has been imposed are marked in
 the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
 by the character "D" appended to the values of the maximum horizontal
-velocities. </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
-</td> <td style="vertical-align: top;">C*10&nbsp;
-<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td>
-<td style="vertical-align: top;"> <p>Type of
+velocities. </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*10&nbsp;
+      <br>
+
+
+&nbsp;&nbsp; (100)</td>
+
+
+ <td style="vertical-align: top;"><i>100 * ' '</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Type of
 normalization applied to the x-coordinate of vertical
 profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
-<p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>If
+
+
+
+      
+      
+      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>If
 vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
 local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
@@ -167,6 +551,14 @@
 accordingly. If the value of a normalization quantity becomes zero,
 then normalization for the total respective coordinate system (panel)
-is switched off automatically (also for the y-axis).<br> </p>
-<p>By default, the normalization quantities are calculated as the
+is switched off automatically (also for the y-axis).<br>
+
+
+ </p>
+
+
+
+      
+      
+      <p>By default, the normalization quantities are calculated as the
 horizontal mean of the total model domain and and these values are also
 used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
@@ -174,40 +566,145 @@
 subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a>
 (however, they are used again for all subdomains and even for the total
-domain).&nbsp; </p> <p>The user can choose between
+domain).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>The user can choose between
 the following normalization
-quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'wpt0'</i></td>
-<td style="vertical-align: top;">Normalization with
+quantities: <br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
+
+
+ <tbody>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>'wpt0'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
 to the total surface sensible heat
-flux (k=0 ).</td> </tr> <tr> <td style="vertical-align: middle;"><i>'ws2'</i></td>
-<td style="vertical-align: top;">Normalization with
+flux (k=0 ).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><i>'ws2'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
 to w<sub>*</sub> <sup>2</sup>
 (square of the characteristic vertical wind speed of the CBL)</td>
-</tr> <tr> <td style="vertical-align: top;"><i>'tsw2'</i></td>
-<td style="vertical-align: top;">Normalization with
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>'tsw2'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
 to the square of the characteristic
 temperature of the CBL theta<sub>*</sub> (this is defined
 as ratio of
-the surface heat flux and w<sub>*</sub>).</td> </tr>
-<tr> <td style="vertical-align: middle;"><i>'ws3'</i></td>
-<td style="vertical-align: top;">Normalization with
+the surface heat flux and w<sub>*</sub>).</td>
+
+
+ </tr>
+
+
+
+          <tr>
+
+
+ <td style="vertical-align: middle;"><i>'ws3'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
-to w<sub>*</sub> <sup>3</sup>.</td> </tr>
-<tr> <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
-<td style="vertical-align: top;">Normalization with
+to w<sub>*</sub> <sup>3</sup>.</td>
+
+
+ </tr>
+
+
+
+          <tr>
+
+
+ <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
 to w<sub>*</sub><sup>2</sup>theta<sub>*</sub>
 (for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
-<td style="vertical-align: top;">Normalization with
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
 to w<sub>*</sub><sup>2 </sup>theta<sub>*</sub>
 (for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
-</tr> </tbody> </table> <p>For each
+
+
+
+          </tr>
+
+
+ 
+        
+        
+        </tbody> 
+      
+      
+      </table>
+
+
+ 
+      
+      
+      <p>For each
 coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>)
 an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> =
-<span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
+      <span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
 then the
 x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
@@ -215,5 +712,11 @@
 Data
 of the further coordinate systems (if any are to be drawn) are not
-normalized.&nbsp; </p> <p>Using a normalization
+normalized.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Using a normalization
 leaves all vertical profile data on
 local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
@@ -223,15 +726,64 @@
 which may be changed subsequently by the user in the parameter file
 (local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
+
+
+
 &nbsp;<br>
+
+
+
 The assigned normalization quantity is noted in the axes labels of the
 respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
-</td> <td style="vertical-align: top;">C*10&nbsp;
-<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td>
-<td style="vertical-align: top;"> <p>Type of
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*10&nbsp;
+      <br>
+
+
+&nbsp;&nbsp; (100)</td>
+
+
+ <td style="vertical-align: top;"><i>100 * ' '</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Type of
 normalization applied to the y-coordinate of vertical
 profiles to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;</p>
-<p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>If
+
+
+
+      
+      
+      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>If
 vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
 local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
@@ -240,32 +792,172 @@
 certain quantities (at present only the normalization with respect to
 the boundary layer height is possible) in order to ensure a better
-comparability. </p> <p>The user can choose between the
+comparability. </p>
+
+
+ 
+      
+      
+      <p>The user can choose between the
 following normalization
-quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'z_i'</i></td>
-<td style="vertical-align: top;">Normalization with
+quantities: <br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
+
+
+ <tbody>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>'z_i'</i></td>
+
+
+
+            <td style="vertical-align: top;">Normalization with
 respect
 to the boundary layer height
 (determined from the height where the heat flux achieves its minimum
-value).</td> </tr> </tbody> </table> <p>For
+value).</td>
+
+
+ </tr>
+
+
+ 
+        
+        
+        </tbody> 
+      
+      
+      </table>
+
+
+ 
+      
+      
+      <p>For
 further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
-</td> <td style="vertical-align: top;">C*100&nbsp;
-<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;">see right<br> </td>
-<td style="vertical-align: top;"> <p>Determines
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*100&nbsp;
+      <br>
+
+
+&nbsp;&nbsp; (100)</td>
+
+
+ <td style="vertical-align: top;">see right<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Determines
 which vertical profiles are to be presented in
 which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used.
-&nbsp; </p> <p>This parameter only applies for
+&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for
 &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>The
-default assignment is:&nbsp; </p> <p><b>cross_profiles</b>
-=&nbsp; </p> <ul> <p><span style="font-family: monospace; font-style: italic;">'
-u v ',</span><br> <span style="font-family: monospace; font-style: italic;">' pt
-',&nbsp; </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">'
-w"pt" w*pt* w*pt*BC wpt wptBC ',&nbsp; </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">'
-w"u" w*u* wu w"v"w*v* wv ',&nbsp; </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' km
-kh ',</span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' l '
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>The
+default assignment is:&nbsp; </p>
+
+
+ 
+      
+      
+      <p><b>cross_profiles</b>
+=&nbsp; </p>
+
+
+ 
+      
+      
+      <ul>
+
+
+ 
+        
+        
+        <p><span style="font-family: monospace; font-style: italic;">'
+u v ',</span><br>
+
+
+ <span style="font-family: monospace; font-style: italic;">' pt
+',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
+
+
+ <span style="font-family: monospace; font-style: italic;">'
+w"pt" w*pt* w*pt*BC wpt wptBC ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
+
+
+ <span style="font-family: monospace; font-style: italic;">'
+w"u" w*u* wu w"v"w*v* wv ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
+
+
+ <span style="font-family: monospace; font-style: italic;">' km
+kh ',</span><br style="font-family: monospace; font-style: italic;">
+
+
+ <span style="font-family: monospace; font-style: italic;">' l '
 ,</span><br>
+
+
+
 14 * <span style="font-family: monospace; font-style: italic;">'
-'</span></p> </ul> <p>If plot output of
+'</span></p>
+
+
+ 
+      
+      
+      </ul>
+
+
+ 
+      
+      
+      <p>If plot output of
 vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
 the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.
@@ -282,7 +974,36 @@
 The single names have to be separated by one blank (' ') and a blank
 must be spent also at the beginning and at the end of the
-string.&nbsp; </p> <p>Example:&nbsp; </p> <ul>
-<p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
-' pt '</span></p> </ul> <p>In this case the
+string.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Example:&nbsp; </p>
+
+
+ 
+      
+      
+      <ul>
+
+
+
+        
+        
+        <p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
+' pt '</span></p>
+
+
+ 
+      
+      
+      </ul>
+
+
+ 
+      
+      
+      <p>In this case the
 plot consists of two coordinate systems
 (panels) with the first panel containing the profiles of the horizontal
@@ -292,5 +1013,14 @@
 and the second one containing the profiles of the potential temperature
 (<span style="font-style: italic;">'pt'</span>).<br>
-</p> <p>Whether the coordinate systems are actually drawn,
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>Whether the coordinate systems are actually drawn,
 depends on
 whether data of the appropriate profiles were output during the run
@@ -302,35 +1032,141 @@
 to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>,
 then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
-but they are not drawn in the plot. <br> </p>
+but they are not drawn in the plot. <br>
+
+
+ </p>
+
+
+
 The arrangement of the panels in the plot can be controlled
 with the parameters <a href="#profile_columns">profile_columns</a>
 and <a href="#profile_rows">profile_rows</a>.
 Up to 100 panels systems are allowed in a plot (however, they may be
-distributed on several pages).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
-</td> <td style="vertical-align: top;">C*40&nbsp;
-<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;">see right<br> </td>
-<td style="vertical-align: top;"> <p>x-axis labels
+distributed on several pages).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*40&nbsp;
+      <br>
+
+
+&nbsp;&nbsp; (100)</td>
+
+
+ <td style="vertical-align: top;">see right<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>x-axis labels
 of vertical profile coordinate systems to be
 plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
-</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>The
-default assignment is:&nbsp; </p> <p><b>cross_xtext</b>
-=&nbsp; </p> <ul> <p><span style="font-style: italic;">'wind speed in
-ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'pot. temperature in
+      </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>The
+default assignment is:&nbsp; </p>
+
+
+ 
+      
+      
+      <p><b>cross_xtext</b>
+=&nbsp; </p>
+
+
+ 
+      
+      
+      <ul>
+
+
+ 
+        
+        
+        <p><span style="font-style: italic;">'wind speed in
+ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
+
+
+ <span style="font-style: italic;">'pot. temperature in
 K',&nbsp; </span><br style="font-style: italic;">
-<span style="font-style: italic;">'heat flux in K
-ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'momentum flux in
-m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'eddy diffusivity in
-m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
-<br>14 * <span style="font-style: italic;">' '</span></p>
-</ul> <p>This parameter can be used to assign x-axis
+
+
+
+        <span style="font-style: italic;">'heat flux in K
+ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
+
+
+ <span style="font-style: italic;">'momentum flux in
+m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;">
+
+
+ <span style="font-style: italic;">'eddy diffusivity in
+m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
+
+
+ <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
+        <br>
+
+
+14 * <span style="font-style: italic;">' '</span></p>
+
+
+
+      
+      
+      </ul>
+
+
+ 
+      
+      
+      <p>This parameter can be used to assign x-axis
 labels to vertical
 profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output
 of vertical
 profile data see <a href="#data_output_pr">data_output_pr</a>).<br>
+
+
+
 The labels are assigned to those coordinate systems (panels) defined by
-<a href="#cross_profiles">cross_profiles</a>
+      <a href="#cross_profiles">cross_profiles</a>
 according to their respective order (compare the default values of <b>cross_xtext</b>
-and <b>cross_profiles</b>). </p> <p>Umlauts
+and <b>cross_profiles</b>). </p>
+
+
+ 
+      
+      
+      <p>Umlauts
 are possible (write &ldquo; in front of, similar to TeX), as
 well as super- and subscripts (use "&gt;" or "&lt;" in front of
@@ -338,9 +1174,45 @@
 character), special characters etc. (see UNIRAS manuals) when using the
 plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
-</td> <td style="vertical-align: top;">C*1</td>
-<td style="vertical-align: top;"><i>'w'</i></td>
-<td style="vertical-align: top;"> <p>Type of cycle
-to be used with the multi-grid method.&nbsp; </p> <p>This
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*1</td>
+
+
+
+      <td style="vertical-align: top;"><i>'w'</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Type of cycle
+to be used with the multi-grid method.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This
 parameter determines which type of cycle is applied in
 the multi-grid method used for solving the Poisson equation for
@@ -351,24 +1223,75 @@
 The
 computational cost of w-cycles is much higher than that of v-cycles,
-however, w-cycles give a much better convergence. </p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="data_output"></a><b>data_output</b></p>
-</td> <td style="vertical-align: top;">C * 10 (100)<br>
-</td> <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
-</td> <td style="vertical-align: top;">Quantities
-for which 2d cross section and/or 3d volume data are to be output.<br><br>PALM
+however, w-cycles give a much better convergence. </p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="data_output"></a><b>data_output</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C * 10 (100)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">Quantities
+for which 2d cross section and/or 3d volume data are to be output.<br>
+
+
+      <br>
+
+
+PALM
 allows the output of instantaneous data as well as of temporally
 averaged data which is steered by the strings assigned to this
-parameter (see below).<br><br>By default, cross section
+parameter (see below).<br>
+
+
+      <br>
+
+
+By default, cross section
 data are output (depending on the selected cross sections(s), see
 below)&nbsp; to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>,
-<a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
+      <a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
 and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>.
 Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>.
 If the user has switched on the output of temporally averaged data,
 these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>,
-<a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
-<a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
+      <a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
+      <a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
 and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
-respectively.<br><br>The
+respectively.<br>
+
+
+      <br>
+
+
+The
 filenames already suggest that all files have NetCDF format.
 Informations about the file content (kind of quantities, array
@@ -376,58 +1299,571 @@
 format and can be extracted from the NetCDF files using the command
 "ncdump -c &lt;filename&gt;". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing
-the PALM NetCDF data.<br><br>The following quantities are
-available for output by default (quantity names ending with '*' are only allowed for the output of horizontal cross sections):<br><br><table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="width: 106px;"><span style="font-weight: bold;">quantity
-name</span></td><td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td><td><span style="font-weight: bold;">unit</span></td><td><span style="font-weight: bold;">remarks</span></td></tr><tr><td style="width: 106px;"><span style="font-style: italic;">e</span></td><td style="width: 196px;">SGS TKE</td><td>m<sup>2</sup>/s<sup>2</sup></td><td></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td><td style="width: 196px; vertical-align: top;">liquid water path</td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">only horizontal cross section
+the PALM NetCDF data.<br>
+
+
+      <br>
+
+
+The following quantities are
+available for output by default (quantity names ending with '*' are only allowed for the output of horizontal cross sections):<br>
+
+
+      <br>
+
+
+      
+      
+      <table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="width: 106px;"><span style="font-weight: bold;">quantity
+name</span></td>
+
+
+            <td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td>
+
+
+            <td><span style="font-weight: bold;">unit</span></td>
+
+
+            <td><span style="font-weight: bold;">remarks</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px;"><span style="font-style: italic;">e</span></td>
+
+
+            <td style="width: 196px;">SGS TKE</td>
+
+
+            <td>m<sup>2</sup>/s<sup>2</sup></td>
+
+
+            <td></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">liquid water path</td>
+
+
+            <td style="vertical-align: top;">m</td>
+
+
+            <td style="vertical-align: top;">only horizontal cross section
 is allowed,&nbsp;requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td><td style="width: 196px; vertical-align: top;">perturpation
-pressure</td><td style="vertical-align: top;">N/m<sup>2</sup>,
-Pa</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td><td style="width: 196px; vertical-align: top;">particle/droplet
-concentration</td><td style="vertical-align: top;">#/gridbox</td><td style="vertical-align: top;">requires that particle
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">perturpation
+pressure</td>
+
+
+            <td style="vertical-align: top;">N/m<sup>2</sup>,
+Pa</td>
+
+
+            <td style="vertical-align: top;"></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">particle/droplet
+concentration</td>
+
+
+            <td style="vertical-align: top;">#/gridbox</td>
+
+
+            <td style="vertical-align: top;">requires that particle
 advection is switched on by <span style="font-weight: bold;">mrun</span>-option
-"-p particles"</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td><td style="width: 196px; vertical-align: top;">mean
-particle/droplet radius </td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">requires that particle
+"-p particles"</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">mean
+particle/droplet radius </td>
+
+
+            <td style="vertical-align: top;">m</td>
+
+
+            <td style="vertical-align: top;">requires that particle
 advection is switched on by <span style="font-weight: bold;">mrun</span>-option
-"-p particles"</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">pra*</span></td><td style="vertical-align: top;">precipitation amount</td><td style="vertical-align: top;">mm</td><td style="vertical-align: top;">only horizontal cross section
+"-p particles"</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><span style="font-style: italic;">pra*</span></td>
+
+
+            <td style="vertical-align: top;">precipitation amount</td>
+
+
+            <td style="vertical-align: top;">mm</td>
+
+
+            <td style="vertical-align: top;">only horizontal cross section
 is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
-= <span style="font-style: italic;">.TRUE., </span>time interval on which amount refers to is defined by <a href="#precipitation_amount_interval">precipitation_amount_interval</a></td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">prr*</span></td><td style="vertical-align: top;">precipitation rate</td><td style="vertical-align: top;">mm/s</td><td style="vertical-align: top;">only horizontal cross section
+= <span style="font-style: italic;">.TRUE., </span>time interval on which amount refers to is defined by <a href="#precipitation_amount_interval">precipitation_amount_interval</a></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><span style="font-style: italic;">prr*</span></td>
+
+
+            <td style="vertical-align: top;">precipitation rate</td>
+
+
+            <td style="vertical-align: top;">mm/s</td>
+
+
+            <td style="vertical-align: top;">only horizontal cross section
 is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td><td style="width: 196px; vertical-align: top;">potential
-temperature<br></td><td style="vertical-align: top;">K</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td><td style="width: 196px; vertical-align: top;">specific humidity
-(or total water content, if cloud physics is switched on)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td><td style="width: 196px; vertical-align: top;">liquid water
-content</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">potential
+temperature<br>
+
+
+            </td>
+
+
+            <td style="vertical-align: top;">K</td>
+
+
+            <td style="vertical-align: top;"></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">specific humidity
+(or total water content, if cloud physics is switched on)</td>
+
+
+            <td style="vertical-align: top;">kg/kg</td>
+
+
+            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">liquid water
+content</td>
+
+
+            <td style="vertical-align: top;">kg/kg</td>
+
+
+            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
 = <span style="font-style: italic;">.TRUE.</span>
 or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td><td style="width: 196px; vertical-align: top;">change in liquid
-water content due to condensation/evaporation during last timestep</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td><td style="width: 196px; vertical-align: top;">volume of liquid
-water</td><td style="vertical-align: top;">m<sup>3</sup>/gridbox</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td><td style="width: 196px; vertical-align: top;">weighting factor</td><td style="vertical-align: top;"></td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td><td style="width: 196px; vertical-align: top;">water vapor
-content (specific humidity)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic;">rho</span></td><td align="undefined" valign="undefined">potential density</td><td align="undefined" valign="undefined">kg/m<sup>3</sup></td><td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td><td style="width: 196px; vertical-align: top;">concentration of
-the scalar</td><td style="vertical-align: top;">1/m<sup>3</sup></td><td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic;">sa</span></td><td align="undefined" valign="undefined">salinity</td><td align="undefined" valign="undefined">psu</td><td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
-= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td><td style="width: 196px; vertical-align: top;">(near surface)
-characteristic temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">only horizontal cross section
-is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td><td style="width: 196px; vertical-align: top;">u-component of
-the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td><td style="width: 196px; vertical-align: top;">(near surface)
-friction velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;">only horizontal cross section
-is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td><td style="width: 196px; vertical-align: top;">v-component of
-the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td><td style="width: 196px; vertical-align: top;">virtual potential
-temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td><td style="width: 196px; vertical-align: top;">w-component of
-the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">z0*</span></td><td style="vertical-align: top;">roughness length</td><td style="vertical-align: top;">m</td><td></td></tr></tbody></table><br>Multiple
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">change in liquid
+water content due to condensation/evaporation during last timestep</td>
+
+
+            <td style="vertical-align: top;">kg/kg</td>
+
+
+            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">volume of liquid
+water</td>
+
+
+            <td style="vertical-align: top;">m<sup>3</sup>/gridbox</td>
+
+
+            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">weighting factor</td>
+
+
+            <td style="vertical-align: top;"></td>
+
+
+            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">water vapor
+content (specific humidity)</td>
+
+
+            <td style="vertical-align: top;">kg/kg</td>
+
+
+            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic;">rho</span></td>
+
+
+            <td align="undefined" valign="undefined">potential density</td>
+
+
+            <td align="undefined" valign="undefined">kg/m<sup>3</sup></td>
+
+
+            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">concentration of
+the scalar</td>
+
+
+            <td style="vertical-align: top;">1/m<sup>3</sup></td>
+
+
+            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic;">sa</span></td>
+
+
+            <td align="undefined" valign="undefined">salinity</td>
+
+
+            <td align="undefined" valign="undefined">psu</td>
+
+
+            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
+= <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">(near surface)
+characteristic temperature</td>
+
+
+            <td style="vertical-align: top;">K</td>
+
+
+            <td style="vertical-align: top;">only horizontal cross section
+is allowed</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">u-component of
+the velocity</td>
+
+
+            <td style="vertical-align: top;">m/s</td>
+
+
+            <td style="vertical-align: top;"></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">(near surface)
+friction velocity</td>
+
+
+            <td style="vertical-align: top;">m/s</td>
+
+
+            <td style="vertical-align: top;">only horizontal cross section
+is allowed</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">v-component of
+the velocity</td>
+
+
+            <td style="vertical-align: top;">m/s</td>
+
+
+            <td style="vertical-align: top;"></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">virtual potential
+temperature</td>
+
+
+            <td style="vertical-align: top;">K</td>
+
+
+            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td>
+
+
+            <td style="width: 196px; vertical-align: top;">w-component of
+the velocity</td>
+
+
+            <td style="vertical-align: top;">m/s</td>
+
+
+            <td style="vertical-align: top;"></td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><span style="font-style: italic;">z0*</span></td>
+
+
+            <td style="vertical-align: top;">roughness length</td>
+
+
+            <td style="vertical-align: top;">m</td>
+
+
+            <td></td>
+
+
+          </tr>
+
+
+        
+        
+        </tbody>
+      
+      
+      </table>
+
+
+      <br>
+
+
+Multiple
 quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span>
-= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br><br>By
+= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br>
+
+
+      <br>
+
+
+By
 assigning the pure strings from the above table, 3d volume data is
 output. Cross section data can be output by appending the string <span style="font-style: italic;">'_xy'</span>, <span style="font-style: italic;">'_xz'</span>, or <span style="font-style: italic;">'_yz'</span> to the
 respective quantities. Time averaged&nbsp;output is created by
 appending the string <span style="font-style: italic;">'_av'
-</span>(for
+      </span>(for
 cross section data, this string must be appended after the cross
 section string). Cross section data can also be (additionally) averaged
 along the direction normal to the respective section (see below).
 Assignments of quantities can be given in arbitrary
-order:<br><br>Example:<br><br><div style="margin-left: 40px;"><span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'pt_xz_av'</span>, <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'u_av'</span>.<br></div><br>This
+order:<br>
+
+
+      <br>
+
+
+Example:<br>
+
+
+      <br>
+
+
+      
+      
+      <div style="margin-left: 40px;"><span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'pt_xz_av'</span>, <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'u_av'</span>.<br>
+
+
+      </div>
+
+
+      <br>
+
+
+This
 example will create the following output: instantaneous 3d volume data
 of u-velocity component (by default on file DATA_3D_NETCDF), temporally
@@ -436,23 +1872,58 @@
 w-velocity component (by default on file DATA_2D_XY_NETCDF), and
 temporally averaged vertical cross section data of potential
-temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br><br>The
+temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br>
+
+
+      <br>
+
+
+The
 user is allowed to extend the above list of quantities by defining his
-own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br><br>The
+own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br>
+
+
+      <br>
+
+
+The
 time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
 This is valid for all types of output quantities by default. Individual
 time intervals for instantaneous &nbsp;(!) 3d and section data can
 be
-declared using <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="#dt_do2d_xz">dt_do2d_xz</a>, and <a href="#dt_do2d_yz">dt_do2d_yz</a>.<br><br>Also,
+declared using <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="#dt_do2d_xz">dt_do2d_xz</a>, and <a href="#dt_do2d_yz">dt_do2d_yz</a>.<br>
+
+
+      <br>
+
+
+Also,
 an individual time interval for output of temporally averaged data can
 be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
 This applies to both 3d volume and cross section data. The length of
-the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br><br>The
+the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br>
+
+
+      <br>
+
+
+The
 parameter <a href="#skip_time_data_output">skip_time_data_output</a>
 can be used to shift data output activities for a given time interval.
 Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>,
-<a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><p>With
+      <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br>
+
+
+      
+      
+      <p>With
 the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>&nbsp;
 the output can be limited in the vertical direction up to a certain
-grid point.<br> </p> Cross sections extend through the
+grid point.<br>
+
+
+ </p>
+
+
+ Cross sections extend through the
 total model
 domain. In the two horizontal directions all grid points with 0
@@ -463,7 +1934,22 @@
 complete total domain is represented. The location(s) of the cross
 sections can be defined with parameters <a href="#section_xy">section_xy</a>,
-<a href="#section_xz">section_xz</a>, and <a href="#section_yz">section_yz</a>. Assigning <span style="font-weight: bold;">section_..</span> = <span style="font-style: italic;">-1</span>
+      <a href="#section_xz">section_xz</a>, and <a href="#section_yz">section_yz</a>. Assigning <span style="font-weight: bold;">section_..</span> = <span style="font-style: italic;">-1</span>
 causes&nbsp;the output data to be averaged along the direction
-normal to the respective section.<br><br><br><span style="font-weight: bold;">Output of user defined quantities:</span><br><br>Beside
+normal to the respective section.<br>
+
+
+      <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Output of user defined quantities:</span><br>
+
+
+      <br>
+
+
+Beside
 the standard quantities from the above list, the user can output any
 other quantities. These have to be defined and calculated within the
@@ -474,6 +1960,19 @@
 selection of cross sections, etc.) is controlled with the parameters
 listed above and data are written to the same file(s) as the standard
-quantities.<br><br><p style="font-weight: bold;">Output
-on parallel machines:</p><p>
+quantities.<br>
+
+
+      <br>
+
+
+      
+      
+      <p style="font-weight: bold;">Output
+on parallel machines:</p>
+
+
+      
+      
+      <p>
 By default, with parallel runs, processors output only data
 of their respective subdomains into seperate local files (file names
@@ -486,5 +1985,11 @@
 using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
 (to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
-configuration file).</p> <p>Alternatively, PALM is able to
+configuration file).</p>
+
+
+ 
+      
+      
+      <p>Alternatively, PALM is able to
 collect all grid points of a
 cross section on PE0 before output is done. In this case only
@@ -495,14 +2000,37 @@
 memory is required on PE0.&nbsp; This method can be used by
 assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
-= <i>.F.</i>.</p><p>3d volume data output is
+= <i>.F.</i>.</p>
+
+
+      
+      
+      <p>3d volume data output is
 always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span>
-has to be called anyway after PALM has been finished.</p><p><br><span style="font-weight: bold;">Old formats:</span></p>
-<p>Beside
+has to be called anyway after PALM has been finished.</p>
+
+
+      
+      
+      <p><br>
+
+
+      <span style="font-weight: bold;">Old formats:</span></p>
+
+
+
+      
+      
+      <p>Beside
 the NetCDF format,&nbsp;2d cross section data and 3d volume data
 can
 also be output, for historical reasons, in a different (binary) format
-using parameter <a href="#data_output_format">data_output_format</a>.</p><p>By
+using parameter <a href="#data_output_format">data_output_format</a>.</p>
+
+
+      
+      
+      <p>By
 assigning <span style="font-weight: bold;">data_output_format
-</span>= <span style="font-style: italic;">'avs'</span>,
+      </span>= <span style="font-style: italic;">'avs'</span>,
 the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
 Output is in FORTRAN binary format&nbsp;readable by
@@ -533,7 +2061,10 @@
 compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>).
 Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in
-<a href="chapter_4.5.5.html">chapter
-4.5.5</a>.</p>By assigning <span style="font-weight: bold;">data_output_format </span>=
-<span style="font-style: italic;">'iso2d'</span>,
+      <a href="chapter_4.5.5.html">chapter
+4.5.5</a>.</p>
+
+
+By assigning <span style="font-weight: bold;">data_output_format </span>=
+      <span style="font-style: italic;">'iso2d'</span>,
 the cross section data is output to the local files <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>, <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>, and <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
 Output is in FORTRAN binary format&nbsp;readable by
@@ -549,9 +2080,9 @@
 creates NAMELIST parameter files
 (local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>,
-<a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
-<a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
-<a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
-<a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
-<a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
+      <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
+      <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
+      <a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
+      <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
+      <a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
 which can be used as parameter input files for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
 That needs local files with suffix _LOCAL to be appended to the
@@ -571,55 +2102,227 @@
 file.&nbsp;Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found
 in <a href="chapter_4.5.4.html">chapter
-4.5.4</a>.<br><br><span style="font-weight: bold;">Important:</span><br>There
+4.5.4</a>.<br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Important:</span><br>
+
+
+There
 is no guarantee that iso2d- and avs-output will be available in future
-PALM versions (later than 3.0). </td> </tr> <tr> <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
-</td> <td style="vertical-align: top;">C * 10 (10) </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
-<td style="vertical-align: top;">Format of output data.<br><br>By
+PALM versions (later than 3.0). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C * 10 (10) </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
+
+
+
+      <td style="vertical-align: top;">Format of output data.<br>
+
+
+      <br>
+
+
+By
 default, all data (profiles, time
 series, spectra, particle data, cross sections, volume data) are output
 in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).
 Exception: restart data (local files <a href="chapter_3.4.html#BININ">BININ</a>, <a href="chapter_3.4.html#BINOUT">BINOUT</a>, <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
-<a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
-are always output in FORTRAN binary format.<br><br>The
-numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br><br>The
+      <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
+are always output in FORTRAN binary format.<br>
+
+
+      <br>
+
+
+The
+numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br>
+
+
+      <br>
+
+
+The
 maximum file size for NetCDF files is 2 GByte by default. Use the
 parameter <a href="#netcdf_64bit">netcdf_64bit</a>
-if larger files have to be created.<br><br>For historical
+if larger files have to be created.<br>
+
+
+      <br>
+
+
+For historical
 reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span>
-may be assigned the following values:<br><br><table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td><td>output
+may be assigned the following values:<br>
+
+
+      <br>
+
+
+      
+      
+      <table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td>
+
+
+            <td>output
 of profiles,&nbsp;time series and spectra in ASCII format to be
 read by the graphic software <span style="font-weight: bold;">profil
-</span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
-<a href="#chapter_4.5.3.html">4.5.3</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td><td>output
+            </span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
+            <a href="#chapter_4.5.3.html">4.5.3</a>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td>
+
+
+            <td>output
 of 2d cross-sections in FORTRAN binary format to be read by the graphic
 software <span style="font-weight: bold;">iso2d</span>
-(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td><td>output
+(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td>
+
+
+            <td>output
 of 3d volume data in FORTRAN binary format to be read by the graphic
 software <span style="font-weight: bold;">AVS</span>
-(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td></tr></tbody></table><br>Multiple
+(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td>
+
+
+          </tr>
+
+
+        
+        
+        </tbody>
+      
+      
+      </table>
+
+
+      <br>
+
+
+Multiple
 values can be assigned to <span style="font-weight: bold;">data_output_format</span>,
 i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as
 cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> =
-<span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
-assigned.<br><br><span style="font-weight: bold;">Warning:</span>
+      <span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
+assigned.<br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Warning:</span>
 There is no guarantee that the "old" formats will be available in
-future PALM versions (beyond 3.0)!<br> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
-</td> <td style="vertical-align: top;">C *
+future PALM versions (beyond 3.0)!<br>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C *
 10&nbsp; <br>
-(100)</td> <td style="vertical-align: top;"><i>100
-* ' '</i></td> <td style="vertical-align: top;">
-<p>Quantities for which vertical profiles (horizontally averaged)
-are to be output.&nbsp; </p> <p>By default vertical
+
+
+
+(100)</td>
+
+
+ <td style="vertical-align: top;"><i>100
+* ' '</i></td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p>Quantities for which vertical profiles (horizontally averaged)
+are to be output.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>By default vertical
 profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>.
 The file's format is NetCDF.&nbsp; Further details about processing
-NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>For
+NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
+
+
+      
+      
+      <p>For
 historical reasons, data can also be output in ASCII-format on local
 file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
 which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See
 parameter <a href="#data_output_format">data_output_format</a>
-for defining the format in which data shall be output.<br> </p>
-<p>For horizontally averaged vertical
+for defining the format in which data shall be output.<br>
+
+
+ </p>
+
+
+
+      
+      
+      <p>For horizontally averaged vertical
 profiles always <span style="font-weight: bold;">all</span>
 vertical
@@ -627,12 +2330,32 @@
 profile data refers to the total domain but profiles for subdomains can
 also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).&nbsp;
-</p> <p>The temporal interval of the output times of
+      </p>
+
+
+ 
+      
+      
+      <p>The temporal interval of the output times of
 profiles is
 assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>.
 Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
 the profiles are ordered with respect to their
-output times.</p><p>Profiles can also be temporally
+output times.</p>
+
+
+      
+      
+      <p>Profiles can also be temporally
 averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>).&nbsp;<br>
-</p> <p>The following list shows the values which can be
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>The following list shows the values which can be
 assigned to <span style="font-weight: bold;">data_output_pr</span>.
 The profile data is either defined on
@@ -647,151 +2370,872 @@
 level is z = zu(1) instead of z = zw(0) for profiles <i>w''
 u'',w''v"</i>, <i>wu</i> and <i>wv</i>
-.&nbsp; <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
-<td style="vertical-align: top;">u-component of the
-velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
-<td style="vertical-align: top;">v-component of the
-velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
-<td style="vertical-align: top;">w-component of the
-velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
-<td style="vertical-align: top;">Potential temperature (in
-K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
-<td style="vertical-align: top;">Virtual potential
-temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
-<td style="vertical-align: top;">Potential liquid water
-temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
-<td style="vertical-align: top;">Total water content
-(in kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
-<td style="vertical-align: top;">Specific humidity (in
-kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
-<td style="vertical-align: top;">Liquid water content
-(in kg/kg).</td> </tr> <tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 102, 0);">rho</span></td><td align="undefined" valign="undefined">Potential density (in kg/m<sup>3</sup>).</td></tr><tr> <td style="vertical-align: middle; font-style: italic;"><font color="#ff6600">s</font></td>
-<td style="vertical-align: top;">Scalar concentration (in
-kg/m<sup>3</sup>).</td> </tr> <tr><td align="undefined" valign="undefined"><span style="font-style: italic; background-color: rgb(255, 255, 255); color: rgb(255, 102, 0);">sa</span></td><td align="undefined" valign="undefined">Salinity (in psu).</td></tr><tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
-<td style="vertical-align: top;">Turbulent kinetic energy
+.&nbsp; <br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
+
+
+ <tbody>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
+
+
+
+            <td style="vertical-align: top;">u-component of the
+velocity (in m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
+
+
+
+            <td style="vertical-align: top;">v-component of the
+velocity (in m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
+
+
+
+            <td style="vertical-align: top;">w-component of the
+velocity (in m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Potential temperature (in
+K).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Virtual potential
+temperature (in K).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Potential liquid water
+temperature (in K).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total water content
+(in kg/kg).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Specific humidity (in
+kg/kg).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Liquid water content
+(in kg/kg).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 102, 0);">rho</span></td>
+
+
+            <td align="undefined" valign="undefined">Potential density (in kg/m<sup>3</sup>).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+ <td style="vertical-align: middle; font-style: italic;"><font color="#ff6600">s</font></td>
+
+
+
+            <td style="vertical-align: top;">Scalar concentration (in
+kg/m<sup>3</sup>).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic; background-color: rgb(255, 255, 255); color: rgb(255, 102, 0);">sa</span></td>
+
+
+            <td align="undefined" valign="undefined">Salinity (in psu).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Turbulent kinetic energy
 (TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
-<td style="vertical-align: top;">Perturbation energy
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Perturbation energy
 (resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
-<td style="vertical-align: top;">Eddy diffusivity for
-momentum (in m<sup>2</sup>/s).</td> </tr> <tr>
-<td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
-<td style="vertical-align: top;">Eddy diffusivity for heat
-(in m<sup>2</sup>/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
-<td style="vertical-align: top;">Mixing length (in m).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
-<td style="vertical-align: top;">u-component of the
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Eddy diffusivity for
+momentum (in m<sup>2</sup>/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Eddy diffusivity for heat
+(in m<sup>2</sup>/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Mixing length (in m).</td>
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">u-component of the
 subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td>
-<td style="vertical-align: top;">u-component of the
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">u-component of the
 resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
-<td style="vertical-align: top;">u-component of the total
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
+
+
+
+            <td style="vertical-align: top;">u-component of the total
 vertical momentum flux (<i>w"u"</i> + <i>w*u*</i>)
-(in m<sup>2</sup>/s<sup>2</sup>).</td> </tr>
-<tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
-<td style="vertical-align: top;">v-component of the
+(in m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+ </tr>
+
+
+
+          <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">v-component of the
 subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td>
-<td style="vertical-align: top;">v-component of the
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">v-component of the
 resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
-<td style="vertical-align: top;">v-component of the total
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
+
+
+
+            <td style="vertical-align: top;">v-component of the total
 vertical momentum flux (<i>w"v"</i> + <i>w*v*</i>)
-(in m<sup>2</sup>/s<sup>2</sup>).</td> </tr>
-<tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
-<td style="vertical-align: top;">Subgrid-scale vertical
-sensible heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
-<td style="vertical-align: top;">Resolved vertical
+(in m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+ </tr>
+
+
+
+          <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale vertical
+sensible heat flux (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Resolved vertical
 sensible
-heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
-<td style="vertical-align: top;">Total vertical sensible
+heat flux (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total vertical sensible
 heat flux (<i>w"pt"</i> + <i>w*pt*</i>)
 (in K
-m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td>
-<td style="vertical-align: top;">Subgrid-scale vertical
+m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale vertical
 sensible heat flux using the
-Bott-Chlond scheme (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
-<td style="vertical-align: top;">Total vertical sensible
+Bott-Chlond scheme (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total vertical sensible
 heat flux using the Bott-Chlond scheme
 (<i>w"pt"</i>
-+ <i>w*pt*BC</i>) (in K m/s).</td> </tr> <tr>
-<td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
-<td style="vertical-align: top;">Subgrid-scale vertical
-buoyancy flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
-<td style="vertical-align: top;">Resolved vertical
++ <i>w*pt*BC</i>) (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale vertical
+buoyancy flux (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Resolved vertical
 buoyancy
-flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
-<td style="vertical-align: top;">Total vertical buoyancy
-flux (w"vpt" + w*vpt*) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
-<td style="vertical-align: top;">Subgrid-scale vertical
-water flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td>
-<td style="vertical-align: top;">Resolved vertical water
-flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
-<td style="vertical-align: top;">Total vertical water flux
-(w"q" + w*q*) (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
-<td style="vertical-align: top;">Subgrid-scale vertical
-latent heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td>
-<td style="vertical-align: top;">Resolved vertical latent
-heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
-<td style="vertical-align: top;">Total vertical latent
+flux (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total vertical buoyancy
+flux (w"vpt" + w*vpt*) (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale vertical
+water flux (in kg/kg m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Resolved vertical water
+flux (in kg/kg m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total vertical water flux
+(w"q" + w*q*) (in kg/kg m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale vertical
+latent heat flux (in kg/kg m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Resolved vertical latent
+heat flux (in kg/kg m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total vertical latent
 heat
-flux (w"qv" + w*qv*) (in kg/kg m/s).</td> </tr> <tr>
-<td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
-<td style="vertical-align: top;">Subgrid-scale vertical
+flux (w"qv" + w*qv*) (in kg/kg m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale vertical
 scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td>
-</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td>
-<td style="vertical-align: top;">Resolved vertical scalar
-concentration flux (in kg/m<sup>3</sup> m/s).</td> </tr>
-<tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
-<td style="vertical-align: top;">Total vertical scalar
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Resolved vertical scalar
+concentration flux (in kg/m<sup>3</sup> m/s).</td>
+
+
+ </tr>
+
+
+
+          <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Total vertical scalar
 concentration flux (w"s" + w*s*) (in kg/m<sup>3 </sup>m/s).</td>
-</tr> <tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w"sa"</span></td><td align="undefined" valign="undefined">Subgrid-scale vertical
-salinity flux (in psu<sup> </sup>m/s).</td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w*sa*</span></td><td align="undefined" valign="undefined">Resolved vertical salinity flux (in psu m/s).</td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td><td align="undefined" valign="undefined">Total vertical salinity flux (w"sa" + w*sa*) (in psu<sup> </sup>m/s).</td></tr><tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td>
-<td style="vertical-align: top;">Vertical flux of
-perturbation energy (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
-<td style="vertical-align: top;">Variance of the
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w"sa"</span></td>
+
+
+            <td align="undefined" valign="undefined">Subgrid-scale vertical
+salinity flux (in psu<sup> </sup>m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w*sa*</span></td>
+
+
+            <td align="undefined" valign="undefined">Resolved vertical salinity flux (in psu m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td>
+
+
+            <td align="undefined" valign="undefined">Total vertical salinity flux (w"sa" + w*sa*) (in psu<sup> </sup>m/s).</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Vertical flux of
+perturbation energy (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Variance of the
 u-velocity
-component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
-<td style="vertical-align: top;">Variance of the
+component (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Variance of the
 v-velocity
-component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
-<td style="vertical-align: top;">Variance of the potential
-temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
-<td style="vertical-align: top;">Variance of the potential
-temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
-<td style="vertical-align: top;">Third moment of the
-w-velocity component (resolved)</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
-<td style="vertical-align: top;">Skewness of the
+component (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Variance of the potential
+temperature (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Variance of the potential
+temperature (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Third moment of the
+w-velocity component (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Skewness of the
 w-velocity
 component (resolved, S<sub>w</sub>
 = W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td>
-</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td>
-<td style="vertical-align: top;">Third moment (resolved)</td>
-</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td>
-<td style="vertical-align: top;">Third moment (resolved)</td>
-</tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*/dz</i></font></td>
-<td style="vertical-align: top;">Energy production by
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Third moment (resolved)</td>
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Third moment (resolved)</td>
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*/dz</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Energy production by
 shear
-(resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*/dz</i></font></td>
-<td style="vertical-align: top;">Energy production by
+(resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*/dz</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Energy production by
 turbulent transport of pressure
-fluctuations (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
-<td style="vertical-align: top;">Energy production by
-transport of resolved-scale TKE</td> </tr> </tbody>
-</table> <br>Beyond that, initial profiles (t=0) of some
-variables can be also be
+fluctuations (resolved)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
+
+
+
+            <td style="vertical-align: top;">Energy production by
+transport of resolved-scale TKE</td>
+
+
+ </tr>
+
+
+ 
+        
+        
+        </tbody>
+      
+      
+      </table>
+
+
+ <br>
+
+
+Beyond that, initial profiles (t=0) of some
+variables can additionally be
 output (this output is only done once
 with the first plot output and not repeated with the profile output at
 later
 times). The names of these profiles result from the ones specified
-above leaded by a hash "#".&nbsp; Allowed values are:<br> <ul>
-<p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
-<i>#km</i>, <i>#kh</i>, <i>#l</i></p>
-</ul> <p>These initial profiles have been either set by
+above leaded by a hash "#".&nbsp; Allowed values are:<br>
+
+
+ 
+      
+      
+      <ul>
+
+
+
+        
+        
+        <p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
+        <i>#km</i>, <i>#kh</i>, <i>#l, #lpt, #q, #qv, #s, #sa, #vpt</i></p>
+
+
+
+      
+      
+      </ul>
+
+
+ 
+      
+      
+      <p>Profile names preceded by a hash automatically imply that
+profiles for these variables are also output at later times. It is not
+necessary and not allowed to specify the same profile name with and
+without hash simultaneously(this would lead to an NetCDF error). </p>
+      <p>These initial profiles have been either set by
 the user or
-have been calculated by a 1d-model prerun.</p>The
+have been calculated by a 1d-model prerun.</p>
+
+
+The
 user is allowed to extend the above list of quantities by defining his
-own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>).<br><br>In case
+own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>).<br>
+
+
+      <br>
+
+
+In case
 of ASCII data output to local file PLOT1D_DATA,
 PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
@@ -803,17 +3247,59 @@
 are determined by
 a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>,
-<a href="chapter_4.2.html#profile_rows">profile_rows</a>,
-<a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
-<a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
+      <a href="chapter_4.2.html#profile_rows">profile_rows</a>,
+      <a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
+      <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
 etc.) All parameter values can be changed by editing the parameter
 input
-file. <br><br>Further details about plotting vertical
+file. <br>
+
+
+      <br>
+
+
+Further details about plotting vertical
 profiles with <span style="font-weight: bold;">profil </span>can
 be found in <a href="chapter_4.5.2.html">chapter
-4.5.2</a></td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
-<br> <b>_each_pe</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
-<td style="vertical-align: top;">Output 2d cross section
+4.5.2</a></td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
+      <br>
+
+
+ <b>_each_pe</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">Output 2d cross section
 data by one or
-all processors.&nbsp; <p>In runs with several processors, by
+all processors.&nbsp; 
+      
+      
+      <p>In runs with several processors, by
 default, each processor
 outputs cross section data of its subdomain&nbsp;into an individual
@@ -822,5 +3308,10 @@
 file<span style="font-weight: bold;"></span> using
 the program <tt>combine_plot_fields.x</tt>.&nbsp; </p>
-<p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
+
+
+
+      
+      
+      <p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
 = <i>.F.,</i>
 the respective data is gathered on PE0 and output is done directly
@@ -829,23 +3320,100 @@
 called. However, in case of very large numbers of horizontal
 gridpoints, sufficient
-memory is required on PE0. </p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="disturbance_amplitude"></a><b>disturbance<br>
-_amplitude</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.25</i></td>
-<td style="vertical-align: top;"> <p>Maximum
+memory is required on PE0. </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="disturbance_amplitude"></a><b>disturbance<br>
+
+
+
+_amplitude</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+ <td style="vertical-align: top;"><i>0.25</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Maximum
 perturbation amplitude of the random perturbations
 imposed to the horizontal velocity field (in m/s).&nbsp; </p>
-<p>The parameter <a href="#create_disturbances">create_disturbances</a>
+
+
+
+      
+      
+      <p>The parameter <a href="#create_disturbances">create_disturbances</a>
 describes how to impose random perturbations to the horizontal velocity
 field. Since the perturbation procedure includes two filter operations,
 the amplitude assigned by <b>disturbance_amplitude</b> is
 only an
-approximate value of the real magnitude of the perturbation.</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
-<br> <b>_limit</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.01</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB">Upper
+approximate value of the real magnitude of the perturbation.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
+      <br>
+
+
+ <b>_limit</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+ <td style="vertical-align: top;"><i>0.01</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB">Upper
 limit value of the perturbation energy of
 the velocity field used as a criterion for imposing random
 perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
-</p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
+      </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
 describes how to impose
 random perturbations to the horizontal velocity field. The perturbation
@@ -856,42 +3424,184 @@
 velocities are imposed no more. The value of this parameter usually
 must be determined by trial and error (it depends e.g. on the total
-number of grid points).</span> </font> </p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>zu(3) or<br>zu(nz*2/3)<br>see right</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
+number of grid points).</span> </font> </p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>zu(3) or<br>
+
+
+zu(nz*2/3)<br>
+
+
+see right</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
 limit of the vertical range for which random perturbations are to be
 imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
-</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This
+      </font></font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">This
 parameter must hold the condition zu(3) &lt;= <b>disturbance_level_b</b>
-&lt;= zu(</font></span><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span><span lang="en-GB"><font face="Thorndale, serif">.
-Additionally, <b>disturbance_level_b</b>
+&lt;= zu(</font></span><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-2</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span><span lang="en-GB"><font face="Thorndale, serif">. Additionally, <b>disturbance_level_b</b>
 &lt;= </font></span><a href="#disturbance_level_t"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_t</font></span></a>
-<span lang="en-GB"><font face="Thorndale, serif">must
-also hold.</font></span></p><p><span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_b</span> = <span style="font-style: italic;">(nz * 2) / 3</span>.</span></span><a href="chapter_4.1.html#nz"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">The
+      <span lang="en-GB"><font face="Thorndale, serif">must
+also hold.</font></span></p>
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_b</span> = <span style="font-style: italic;">zu(nz * 2 / 3) </span>(negative).</span></span><a href="chapter_4.1.html#nz"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">The
 parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
 describes how to impose
 random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
-</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>zu(nz/3) or<br>zu(nzt-3)<br>see right</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
+      </font> </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>zu(nz/3) or<br>
+
+
+zu(nzt-3)<br>
+
+
+see right</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
 limit of the vertical range for which random perturbations are to be
 imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
-</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This
+      </font></font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">This
 parameter must hold the condition <b>disturbance_level_t</b>
-&lt;= zu<i>(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">.
+&lt;= zu<i>(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-2</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">.
 Additionally, </font></span><a href="#disturbance_level_b"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_b</font></span></a>
-<span lang="en-GB"><font face="Thorndale, serif">&lt;=
-<b>disturbance_level_t</b>
-must also hold.</font></span></p><span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_t</span> = <span style="font-style: italic;">nzt - 3</span>.</span></span><p><span lang="en-GB"><font face="Thorndale, serif">The
+      <span lang="en-GB"><font face="Thorndale, serif">&lt;=
+      <b>disturbance_level_t</b>
+must also hold.</font></span></p>
+
+
+      <span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_t</span> = <span style="font-style: italic;">zu(nzt - 3</span>)</span></span><span lang="en-GB"><span style="font-family: Thorndale,serif;"><span style="font-style: italic;"> </span>(negative)</span></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">.</span></span>
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">The
 parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
 describes how to impose
 random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
-</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
-</td> <td style="vertical-align: top;">L<br> </td>
-<td style="vertical-align: top;">.F.<br> </td>
-<td style="vertical-align: top;"> <p>Output of 2d
-cross section data at the beginning of a run.&nbsp; </p> <p>The
+      </font> </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">.F.<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Output of 2d
+cross section data at the beginning of a run.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>The
 temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>)
 are usually determined with parameters <a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_xy</a>, <a href="chapter_4.2.html#dt_do2d_xz">dt_do2d_xz</a>
@@ -901,11 +3611,50 @@
 will be made at the
 beginning of a run (thus at the time t = 0 or at the respective
-starting times of restart runs).</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
-</td> <td style="vertical-align: top;">L<br> </td>
-<td style="vertical-align: top;">.F.<br> </td>
-<td style="vertical-align: top;">Output of 3d volume data
+starting times of restart runs).</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">.F.<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">Output of 3d volume data
 at the beginning
-of a run.<br><br>The temporal intervals of output times of
+of a run.<br>
+
+
+      <br>
+
+
+The temporal intervals of output times of
 3d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
 is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>.
@@ -914,11 +3663,55 @@
 will be made at the
 beginning of a run (thus at the time t = 0 or at the respective
-starting times of restart runs).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
-</td> <td style="vertical-align: top;">L<br> </td>
-<td style="vertical-align: top;">.F.<br> </td>
-<td style="vertical-align: top;"> <p>Output of data
-for 3d plots in compressed form.&nbsp; </p> <p>This
+starting times of restart runs).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">.F.<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Output of data
+for 3d plots in compressed form.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This
 parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'avs'</span>.</p><p>Output
+= <span style="font-style: italic;">'avs'</span>.</p>
+
+
+      
+      
+      <p>Output
 of 3d volume data may need huge amounts of disc storage
 (up to several Terabytes ore more). Data compression can serve to
@@ -930,21 +3723,85 @@
 parameter <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>
 can be used to separately define the number of significant digits for
-each quantity.<br> </p> <p>So far compressed data
+each quantity.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>So far compressed data
 output is only possible for Cray-T3E
 machines. Additional information for
 handling compressed data is given in <a href="chapter_4.5.6.html">chapter
-4.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_precision"></a><b>do3d_precision</b></p>
-</td> <td style="vertical-align: top;">C *
+4.5.6</a>.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="do3d_precision"></a><b>do3d_precision</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C *
 7&nbsp; <br>
-&nbsp; (100)</td> <td style="vertical-align: top;">see
-right<br> </td> <td style="vertical-align: top;">
-<p>Significant digits in case of compressed data
-output.&nbsp; </p> <p>This parameter only applies for
+
+
+
+&nbsp; (100)</td>
+
+
+ <td style="vertical-align: top;">see
+right<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p>Significant digits in case of compressed data
+output.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for
 &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'avs'</span>.</p><p>In
+= <span style="font-style: italic;">'avs'</span>.</p>
+
+
+      
+      
+      <p>In
 case that data compression is used for output of 3d data
 (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>),
 this parameter determines the number of significant digits
-which are to be output.<br> </p> <p>Fewer digits
+which are to be output.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>Fewer digits
 clearly reduce the amount
 of data. Assignments have to be given separately for each individual
@@ -955,14 +3812,58 @@
 are admitted. Up to 9 significant digits are allowed (but large values
 are not very reasonable
-because they do not effect a significant compression).<br> </p>
-<p>The default assignment is <span style="font-weight: bold;">do3d_precision</span>
-= <span style="font-style: italic;">'u2'</span>, <span style="font-style: italic;">'v2'</span>, <span style="font-style: italic;">'w2'</span>, <span style="font-style: italic;">'p5'</span>, <span style="font-style: italic;">'pt2'</span>.</p> </td>
-</tr><tr> <td style="vertical-align: top;"> <p><a name="dt_laufparameter"></a><b>dt</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>variable</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Time
+because they do not effect a significant compression).<br>
+
+
+ </p>
+
+
+
+      
+      
+      <p>The default assignment is <span style="font-weight: bold;">do3d_precision</span>
+= <span style="font-style: italic;">'u2'</span>, <span style="font-style: italic;">'v2'</span>, <span style="font-style: italic;">'w2'</span>, <span style="font-style: italic;">'p5'</span>, <span style="font-style: italic;">'pt2'</span>.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_laufparameter"></a><b>dt</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>variable</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Time
 step to be used by the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
-</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This parameter</font></span>
-<font face="Thorndale, serif"><span lang="en-GB">is
+      </font></font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">This parameter</font></span>
+      <font face="Thorndale, serif"><span lang="en-GB">is
 described in
 detail with the initialization parameters (see</span></font><span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB">).
@@ -971,9 +3872,45 @@
 is changed again). A switch from a constant time step to a variable
 time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span>
-</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
-</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;">Temporal interval
-of&nbsp;data which are subject to temporal averaging (in s).<br><br>By
+      </font> </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
+
+
+
+      </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;">Temporal interval
+of&nbsp;data which are subject to temporal averaging (in s).<br>
+
+
+      <br>
+
+
+By
 default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>
 are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span>
@@ -981,5 +3918,11 @@
 the number of time levels entering the average can be minimized. This
 reduces the CPU-time of a run but may worsen the quality of the
-average's statistics.<br><br><font face="Thorndale, serif"><span lang="en-GB">With
+average's statistics.<br>
+
+
+      <br>
+
+
+      <font face="Thorndale, serif"><span lang="en-GB">With
 variable time step (see <span style="font-weight: bold;">dt</span>),
 the number of time levels entering the average can vary from one
@@ -987,14 +3930,29 @@
 is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> /
 MAX(<span style="font-weight: bold;"> dt_averaging_input</span>,
-<span style="font-weight: bold;">dt</span>) (which
+      <span style="font-weight: bold;">dt</span>) (which
 gives a more or less exact value if a fixed timestep is used and if
 this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font>&nbsp;
-<br><br><span style="font-weight: bold;">Example:</span><br>With
+      <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+With
 an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> =
-<span style="font-style: italic;">10.0</span>,
+      <span style="font-style: italic;">10.0</span>,
 the time levels entering the average have a (minimum) distance of 10.0
 s (their distance may of course be larger if the current timestep is
 larger than 10.0 s), so the average is calculated from the data of
-(maximum) 10 time levels.<br><br><font face="Thorndale, serif"><span lang="en-GB">It
+(maximum) 10 time levels.<br>
+
+
+      <br>
+
+
+      <font face="Thorndale, serif"><span lang="en-GB">It
 is allowed
 to change <b>dt_averaging_input</b> during a job chain. If
@@ -1003,14 +3961,62 @@
 has to be finished in the current run), the individual profiles and/or
 spectra entering the averaging are not uniformly distributed over the
-averaging interval.<br><br></span></font>Parameter&nbsp;<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>&nbsp;can
+averaging interval.<br>
+
+
+      <br>
+
+
+      </span></font>Parameter&nbsp;<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>&nbsp;can
 be used to define&nbsp;a different temporal interval&nbsp;for
-vertical profile data and spectra.<br> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>averaging_<br>input</a></span></td>
-<td style="vertical-align: top;"> <p lang="en-GB">Temporal
+vertical profile data and spectra.<br>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>
+
+
+averaging_<br>
+
+
+input</a></span></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB">Temporal
 interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
 profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
-</font></font> </p> <p>By default, data from
+      </font></font> </p>
+
+
+ 
+      
+      
+      <p>By default, data from
 each timestep within the interval defined by<font face="Thorndale, serif"><span lang="en-GB"> </span></font><a href="#averaging_interval_pr"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_pr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><span lang="en-GB"><font face="Thorndale, serif">and </font></span><a href="#averaging_interval_sp"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_sp</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> </font></span>are
 used for calculating the temporal average.&nbsp;By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span>
@@ -1018,15 +4024,96 @@
 the number of time levels entering the average can be minimized. This
 reduces the CPU-time of a run but may worsen the quality of the
-average's statistics. <span lang="en-GB"><font face="Thorndale, serif"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span></font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><br> </p><p>For
-more explanations see parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font></p></td>
-</tr> <tr><td style="vertical-align: top;"><a name="dt_coupling"></a><span style="font-weight: bold;">dt_coupling</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;">Temporal interval for the data exchange in case of runs with coupled models (e.g. atmosphere - ocean) (in s).<br><br>This parameter has an effect only in case of a run with coupled models.<br>It is available starting from version 3.3a. A more detailed explanation will be given soon.</td></tr><tr> <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
-</td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
+average's statistics. <span lang="en-GB"><font face="Thorndale, serif"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span></font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><br>
+
+
+ </p>
+
+
+      
+      
+      <p>For
+more explanations see parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font></p>
+
+
+      </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+      <td style="vertical-align: top;"><a name="dt_coupling"></a><span style="font-weight: bold;">dt_coupling</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;">Temporal interval for the data exchange in case of <a href="chapter_3.8.html">runs with coupled models</a> (e.g. atmosphere - ocean) (in s).<br>
+
+
+      <br>
+
+
+This parameter has an effect only in case of a run with coupled models. It is available starting from version 3.3a. <br>
+
+
+      <br>
+
+
+This parameter specifies the temporal interval at which data are
+exchanged at the interface between coupled models (currently: interface
+between atmosphere and ocean). If this parameter is not explicitly
+specified in the parameter files for both coupled models, or if there
+is an inconsistency between its values for both coupled models,
+the&nbsp;execution will terminate and an informative error message will
+be given.&nbsp;In order to ensure synchronous coupling throughout the simulation, <span style="font-weight: bold;">dt_coupling</span> should be chosen larger than
+      <a href="#dt_max">dt_max</a>.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
 at which&nbsp;data (3d volume data (instantaneous or time
 averaged),
 cross sections (instantaneous or time averaged), vertical profiles,
 spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-<span lang="en-GB"><font face="Thorndale">If
+
+
+
+      <span lang="en-GB"><font face="Thorndale">If
 data output&nbsp;is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">, <a href="#data_output_pr">data_output_pr</a>, <a href="#data_output_sp">data_output_sp</a>, and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
 parameter can be used to
@@ -1043,15 +4130,54 @@
 the&nbsp;timestep used, the actual output times can slightly
 deviate
-from these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br>Individual temporal
+from these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br>
+
+
+      <br>
+
+
+Individual temporal
 intervals for the different output quantities can be assigned using
 parameters <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="dt_do2d_xz">dt_do2d_xz</a>, <a href="#dt_do2d_yz">dt_do2d_yz</a>, <a href="#dt_dopr">dt_dopr</a>, <a href="#dt_dosp">dt_dosp</a>,
 and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span>
-</td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i>
-</td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i>
+      </td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
 at which time averaged 3d volume data and/or 2d cross section data
-shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p><span lang="en-GB"><font face="Thorndale">If data
+shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
+
+
+      <span lang="en-GB"><font face="Thorndale">If data
 output of time averaged 2d and 3d data is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>&nbsp;<span lang="en-GB"><font face="Thorndale">and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
 parameter can be used to
@@ -1068,27 +4194,105 @@
 the&nbsp;timestep used, the actual output times can slightly
 deviate from
-these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br></font></span>The
+these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br>
+
+
+      <br>
+
+
+      </font></span>The
 length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td>
-</tr><tr> <td style="vertical-align: top;"> <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which random
 perturbations are to be imposed on the horizontal velocity field
 (</font>in <font face="Thorndale">s).&nbsp; </font>
-</p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
+      </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
 describes how to impose
 random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
-</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="#dt_data_output">dt_data_<br>output</a></i></td>
-<td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale">Temporal
+      </font> </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Temporal
 interval at
 which data&nbsp;of vertical profiles shall be output (to local
 file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
 or/and </font></span><a href="chapter_3.4.html#PLOT1D_DATA"><span lang="en-GB"><font face="Thorndale">PLOT1D_DATA</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
-<span lang="en-GB"><font face="Thorndale">s).&nbsp;
-</font></span> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
+      <span lang="en-GB"><font face="Thorndale">s).&nbsp;
+      </font></span> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If output of
 horizontally averaged vertical profiles is switched on (see </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
 parameter can be used to
@@ -1099,5 +4303,5 @@
 of the simulation, thus t = 0,&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">i.e. output
 takes place at times t = <b>skip_time_dopr + dt_dopr</b>, <span style="font-weight: bold;">skip_time_dopr</span> + 2*<b>dt_dopr</b>,
-<span style="font-weight: bold;">skip_time_dopr</span>
+      <span style="font-weight: bold;">skip_time_dopr</span>
 + 3*<b>dt_dopr</b>,
 etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
@@ -1109,26 +4313,76 @@
 model uses a variable time step, these
 deviations from the theoretical output times will of course be
-different for each output time.<br> </font></span></p>
-<p><span lang="en-GB"><font face="Thorndale">In
+different for each output time.<br>
+
+
+ </font></span></p>
+
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">In
 order to
 guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">,&nbsp;
-<span style="font-weight: bold;">end_time</span>
+      <span style="font-weight: bold;">end_time</span>
 should be equal or a little bit
 larger than the respective theoretical output time. For example, if <b>dt_dopr</b>
 = <i>900.0</i><span style="font-style: italic;">
-</span>and 3600.0
+      </span>and 3600.0
 seconds are to be simulated, then <b>end_time</b>
 &gt;= 3600.0 should be chosen.</font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span>&nbsp; </font></span>
-</p> <p><span lang="en-GB"><font face="Thorndale">A selection of
+      </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">A selection of
 profiles to be output can be done via parameter </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">.&nbsp;</font></span>
-</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
+      </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
 interval</font> at which data <font face="Thorndale">of
 vertical
 profiles shall be output (output for printouts, local file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
-<span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
-</p> <p>T<span lang="en-GB"></span><a href="chapter_4.2.html#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
+      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
+      </p>
+
+
+ 
+      
+      
+      <p>T<span lang="en-GB"></span><a href="chapter_4.2.html#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
 parameter can be used to
 assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
@@ -1146,13 +4400,21 @@
 example above). If the model uses a variable time step, these
 deviations from the theoretical output times will of course be
-different for each output time.<br> </font></span></p>
-<p><span lang="en-GB"><font face="Thorndale">In
+different for each output time.<br>
+
+
+ </font></span></p>
+
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">In
 order to
 guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">,&nbsp;
-<span style="font-weight: bold;">end_time</span>
+      <span style="font-weight: bold;">end_time</span>
 should be a little bit
 larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b>
 = <i>900.0</i><span style="font-style: italic;">
-</span>and 3600.0
+      </span>and 3600.0
 seconds are to be simulated, then it should be at least&nbsp; <b>end_time</b>
 &gt; 3600.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If
@@ -1160,29 +4422,92 @@
 (which is the default), <span style="font-weight: bold;">dt</span>
 should be properly estimated.&nbsp; </font></span> </p>
-<p><span lang="en-GB"><font face="Thorndale">Data
+
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Data
 and output
 format of the file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a>
-<span lang="en-GB"><font face="Thorndale">is
+      <span lang="en-GB"><font face="Thorndale">is
 internally fixed. In this file
 the profiles of the most important model variables are arranged in
-adjacent columns.</font></span> </p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="dt_dots"></a><b>dt_dots</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+adjacent columns.</font></span> </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_dots"></a><b>dt_dots</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which&nbsp;time series data shall be
 output (</font>in <font face="Thorndale">s).&nbsp;</font>
-</p> <p>The default interval for the output of timeseries
+      </p>
+
+
+ 
+      
+      
+      <p>The default interval for the output of timeseries
 is calculated as shown below (this tries to minimize the number of
-calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p><p style="font-family: Courier New,Courier,monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p>
+
+
+      
+      
+      <p style="font-family: Courier New,Courier,monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
-== 0.0 )&nbsp; THEN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<span style="font-weight: bold;">dt_dots</span> =
-MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-ELSE<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<span style="font-weight: bold;">dt_dots</span> =
+== 0.0 )&nbsp; THEN<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+      <span style="font-weight: bold;">dt_dots</span> =
+MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ELSE<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+      <span style="font-weight: bold;">dt_dots</span> =
 MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
-)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-ENDIF</p><p>This parameter can be used to
+)<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ENDIF</p>
+
+
+      
+      
+      <p>This parameter can be used to
 assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
 time is the beginning of
@@ -1194,128 +4519,515 @@
 of the time series are
 written after each time step (if this is requested it should be <b>dt_dots</b>
-= <i>0</i>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">The default
+= <i>0</i>).</font></span></p>
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">The default
 value of <span style="font-weight: bold;">dt_dots</span>
-is calculated as follows:</font></span></p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+is calculated as follows:</font></span></p>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
-== 0.0 )&nbsp; THEN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<span style="font-weight: bold;">dt_dots</span> =
-MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-ELSE<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<span style="font-weight: bold;">dt_dots</span> =
+== 0.0 )&nbsp; THEN<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+      <span style="font-weight: bold;">dt_dots</span> =
+MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ELSE<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+      <span style="font-weight: bold;">dt_dots</span> =
 MIN( <span style="font-weight: bold;">dt_run_control</span>,
-<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
-)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-ENDIF<br><br>(which minimizes the number of calls of
-routine flow_statistics).<br><p>By default time series data
+      <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
+)<br>
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ENDIF<br>
+
+
+      <br>
+
+
+(which minimizes the number of calls of
+routine flow_statistics).<br>
+
+
+      
+      
+      <p>By default time series data
 is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>.
 Because of the default settings of <span style="font-weight: bold;">dt_dots</span>,
 it will&nbsp;generally be created for each model run. The file's
 format is NetCDF.&nbsp; Further details about processing NetCDF
-data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>The
+data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
+
+
+The
 file contains the following timeseries quantities (the first column
-gives the name of the quantities as used in the NetCDF file):<br><table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="font-style: italic; vertical-align: middle;">E<br>
-</td> <td style="vertical-align: top;">Total
+gives the name of the quantities as used in the NetCDF file):<br>
+
+
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
+
+
+ <tbody>
+
+
+ <tr>
+
+
+ <td style="font-style: italic; vertical-align: middle;">E<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Total
 kinetic energy of
 the flow (in m<sup>2</sup>/s<sup>2</sup>)
 (normalized with respect to the total number of grid points).</td>
-</tr> <tr> <td style="font-style: italic; vertical-align: middle;">E*<br>
-</td> <td style="vertical-align: top;">Perturbation
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="font-style: italic; vertical-align: middle;">E*<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Perturbation
 kinetic
 energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
-</sup>(normalized
+            </sup>(normalized
 with respect to the total number of grid
-points)</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">dt<br>
-</td> <td style="vertical-align: top;">Time step
-size (in s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
-<td style="vertical-align: top;">Friction velocity (in
+points)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">dt<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Time step
+size (in s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
+
+
+
+            <td style="vertical-align: top;">Friction velocity (in
 m/s)
-(horizontal average).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
-<td style="vertical-align: top;">Vertical velocity scale
+(horizontal average).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
+
+
+
+            <td style="vertical-align: top;">Vertical velocity scale
 of
-the CBL (in m/s) (horizontal average)</td> </tr> <tr>
-<td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
-<td style="vertical-align: top;">Temperature
+the CBL (in m/s) (horizontal average)</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
+
+
+
+            <td style="vertical-align: top;">Temperature
 scale (Prandtl layer), defined as <i>w"pt"0
 /&nbsp;</i><i>u<sub>*</sub></i>
 (horizontal
-average) (in K).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">umax<br>
-</td> <td style="vertical-align: top;">Maximum
+average) (in K).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">umax<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Maximum
 u-component of the
-velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">vmax<br>
-</td> <td style="vertical-align: top;">Maximum
+velocity (in m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">vmax<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Maximum
 v-component of the
-velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wmax<br>
-</td> <td style="vertical-align: top;">Maximum
+velocity (in m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">wmax<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Maximum
 w-component of the
-velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_old<br>
-</td> <td style="vertical-align: top;">Divergence
+velocity (in m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">div_old<br>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Divergence
 of the velocity
 field before the pressure
 solver has been called (normalized with respect to the total number of
-grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_new</td>
-<td style="vertical-align: top;">Divergence of the
+grid points) (in 1/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">div_new</td>
+
+
+
+            <td style="vertical-align: top;">Divergence of the
 velocity
 field after the pressure
 solver has been called (normalized with respect to the total number of
-grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
-<td style="vertical-align: top;">Height of the convective
+grid points) (in 1/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
+
+
+
+            <td style="vertical-align: top;">Height of the convective
 boundary layer (horizontal average)
 determined by the height of the minimum sensible heat flux (in m).</td>
-</tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
-<td style="vertical-align: top;">Height of the convective
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
+
+
+
+            <td style="vertical-align: top;">Height of the convective
 boundary layer (horizontal average)
-determined by the temperature profile (in m).</td> </tr> <tr>
-<td style="vertical-align: top; font-style: italic;">w"pt"0</td>
-<td style="vertical-align: top;">Subgrid-scale sensible
+determined by the temperature profile (in m).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top; font-style: italic;">w"pt"0</td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale sensible
 heat flux near the surface (horizontal
 average)
 between z = 0 and z = z<sub>p</sub> = zu(1) (there it
 corresponds to
-the total heat flux) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w"pt"</td>
-<td style="vertical-align: top;">Subgrid-scale heat flux
+the total heat flux) (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">w"pt"</td>
+
+
+
+            <td style="vertical-align: top;">Subgrid-scale heat flux
 (horizontal average) for z = zw(1) (in K
-m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wpt</td>
-<td style="vertical-align: top;">Total heat flux
-(horizontal average) for z = zw(1) (in K m/s).</td> </tr> <tr>
-<td style="vertical-align: top; font-style: italic;">pt(0)</td>
-<td style="vertical-align: top;">Potential temperature at
-the surface (horizontal average) (in K).</td> </tr> <tr>
-<td style="vertical-align: top; font-style: italic;">pt(zp)</td>
-<td style="vertical-align: top;">Potential temperature for
-z = zu(1) (horizontal average) (in K).</td> </tr> <tr>
-<td style="vertical-align: top; font-style: italic;">splptx</td>
-<td style="vertical-align: top;">Percentage of grid points
+m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">wpt</td>
+
+
+
+            <td style="vertical-align: top;">Total heat flux
+(horizontal average) for z = zw(1) (in K m/s).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top; font-style: italic;">pt(0)</td>
+
+
+
+            <td style="vertical-align: top;">Potential temperature at
+the surface (horizontal average) (in K).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top; font-style: italic;">pt(zp)</td>
+
+
+
+            <td style="vertical-align: top;">Potential temperature for
+z = zu(1) (horizontal average) (in K).</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top; font-style: italic;">splptx</td>
+
+
+
+            <td style="vertical-align: top;">Percentage of grid points
 using upstream scheme along x with
-upstream-spline advection switched on.</td> </tr> <tr>
-<td style="vertical-align: top; font-style: italic;">splpty</td>
-<td style="vertical-align: top;">Percentage of grid points
+upstream-spline advection switched on.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+            <td style="vertical-align: top; font-style: italic;">splpty</td>
+
+
+
+            <td style="vertical-align: top;">Percentage of grid points
 using upstream scheme along y with
 upstream-spline
-advection switched on.</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">splptz</td>
-<td style="vertical-align: top;">Percentage of grid points
+advection switched on.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">splptz</td>
+
+
+
+            <td style="vertical-align: top;">Percentage of grid points
 using upstream scheme along z with
 upstream-spline
-advection switched on.<br> </td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">L</td>
-<td style="vertical-align: top;">Monin-Obukhov length.</td>
-</tr> </tbody> </table><br>Additionally, the
+advection switched on.<br>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top; font-style: italic;">L</td>
+
+
+
+            <td style="vertical-align: top;">Monin-Obukhov length.</td>
+
+
+
+          </tr>
+
+
+ 
+        
+        
+        </tbody> 
+      
+      
+      </table>
+
+
+      <br>
+
+
+Additionally, the
 user can add his own timeseries quantities to the file, by using the
 user-interface subroutines<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_init">user_init</a> </span>and<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_statistics">user_statistics</a></span>.
 These routines contain (as comment lines) a simple example how to do
-this.<br><br>Time series data refers to the total
+this.<br>
+
+
+      <br>
+
+
+Time series data refers to the total
 domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
 However, the following time series always present the values of the
 total model domain (even with output for subdomains): <i>umax</i>,
-<i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
-<i>div_new</i>.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+      <i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
+      <i>div_new</i>.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which&nbsp;horizontal cross section data
 shall be output (</font>in <font face="Thorndale">s).&nbsp;
-</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If output of
 horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
-<span lang="en-GB"><font face="Thorndale">and
-</font></span><a href="#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
+      <span lang="en-GB"><font face="Thorndale">and
+      </font></span><a href="#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
 parameter can be used to
 assign the temporal interval at which cross section data shall be
@@ -1325,24 +5037,72 @@
 time is the beginning of the simulation, i.e. output
 takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>,
-<span style="font-weight: bold;">skip_time_do2d_xy</span>
+      <span style="font-weight: bold;">skip_time_do2d_xy</span>
 + 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span>
 + 3*<b>dt_do2d_xy</b>,
 etc. The actual output times can deviate from these theoretical values
 (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
-</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
+
+
+
+      </font></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
 has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
 the time t = 0 or at the
 respective starting times of restart runs).</font></span> </p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which&nbsp;vertical cross sections data
 (xz) shall be output (</font>in <font face="Thorndale">s).&nbsp;
-</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If output of
 horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
-<span lang="en-GB"><font face="Thorndale">and
-</font></span><a href="#section_xz"><span lang="en-GB"><font face="Thorndale">section_xz</font></span></a><span lang="en-GB"><font face="Thorndale">),
+      <span lang="en-GB"><font face="Thorndale">and
+      </font></span><a href="#section_xz"><span lang="en-GB"><font face="Thorndale">section_xz</font></span></a><span lang="en-GB"><font face="Thorndale">),
 this parameter can be used to assign the temporal interval at which
 cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
@@ -1351,23 +5111,71 @@
 the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz
 + dt_do2d_xz</b>,
-<span style="font-weight: bold;">skip_time_do2d_xz</span>
+      <span style="font-weight: bold;">skip_time_do2d_xz</span>
 + 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span>
 + 3*<b>dt_do2d_xz</b>, etc. The actual output times
 can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
-</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
+
+
+
+      </font></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
 has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
 the time t = 0 or at the
 respective starting times of restart runs).</font></span> </p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which&nbsp;vertical cross section data
 (yz) shall be output (</font>in s<font face="Thorndale">).&nbsp;
-</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If output of
 horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
-<span lang="en-GB"><font face="Thorndale">and
-</font></span><a href="#section_yz"><span lang="en-GB"><font face="Thorndale">section_yz</font></span></a><span lang="en-GB"><font face="Thorndale">),
+      <span lang="en-GB"><font face="Thorndale">and
+      </font></span><a href="#section_yz"><span lang="en-GB"><font face="Thorndale">section_yz</font></span></a><span lang="en-GB"><font face="Thorndale">),
 this parameter can be used to assign the temporal interval at which
 cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
@@ -1377,21 +5185,68 @@
 the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz
 + dt_do2d_yz</b>,
-<span style="font-weight: bold;">skip_time_do2d_yz</span>
+      <span style="font-weight: bold;">skip_time_do2d_yz</span>
 + 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz
-</span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
+      </span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
 times
 can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
-</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
+
+
+
+      </font></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
 has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
 the time t = 0 or at the
 respective starting times of restart runs).</font></span> </p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which 3d volume data shall be output (</font>in
-<font face="Thorndale">s).&nbsp; </font> </p>
-<p><span lang="en-GB"><font face="Thorndale">If
+      <font face="Thorndale">s).&nbsp; </font> </p>
+
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If
 output of
 3d-volume data is switched on (see </font></span><font><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>)<span style="font-family: thorndale;">, this parameter can be used
@@ -1404,33 +5259,142 @@
 beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d
 + dt_do3d</b>,
-<span style="font-weight: bold;">skip_time_do3d</span>
+      <span style="font-weight: bold;">skip_time_do3d</span>
 + 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span>
 + 3*<b>dt_do3d</b>, etc. The actual output times can
 deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). <br>
-</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do3d_at_begin"><span lang="en-GB"><font face="Thorndale">do3d_at_begin</font></span></a>
+
+
+
+      </font></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do3d_at_begin"><span lang="en-GB"><font face="Thorndale">do3d_at_begin</font></span></a>
 has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
 the time t = 0 or at the
 respective starting times of restart runs).</font></span> </p>
-</td> </tr> <tr><td style="vertical-align: top;"><a name="dt_max"></a><span style="font-weight: bold;">dt_max</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">20.0</span></td><td>Maximum
-allowed value of the timestep (in s).<br><br>By default,
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+      <td style="vertical-align: top;"><a name="dt_max"></a><span style="font-weight: bold;">dt_max</span></td>
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">20.0</span></td>
+
+
+      <td>Maximum
+allowed value of the timestep (in s).<br>
+
+
+      <br>
+
+
+By default,
 the maximum timestep is restricted to be 20 s. This might be o.k. for
 simulations of any kind of atmospheric turbulence but may have to be
-changed for other situations.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="dt_restart"></a><b>dt_restart</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+changed for other situations.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_restart"></a><b>dt_restart</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which a new
-restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p> <p><span lang="en-GB"><font face="Thorndale">For a
+restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">For a
 description
 how to assign restart times manually see run time parameter </font></span><a href="#restart_time"><span lang="en-GB"><font face="Thorndale">restart_time</font></span></a><span lang="en-GB"><font face="Thorndale">. <span style="font-weight: bold;">dt_restart</span>
 does not show any effect, if <span style="font-weight: bold;">restart_time</span>
-has not been set.</font></span> </p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="dt_run_control"></a><b>dt_run_control</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>60.0</i></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+has not been set.</font></span></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="dt_run_control"></a><b>dt_run_control</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>60.0</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which run control
 output is to be made (</font>in <font face="Thorndale">s).&nbsp;
-</font> </p> <p><span lang="en-GB"><font face="Thorndale">Run control
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Run control
 information is output to the local ASCII-file </font></span><a href="chapter_3.4.html#RUN_CONTROL"><span lang="en-GB"><font face="Thorndale">RUN_CONTROL</font></span></a><span lang="en-GB"><font face="Thorndale">. At each
 output time, one line
@@ -1443,21 +5407,105 @@
 respective starting times of restart runs). The actual output times can
 deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
-</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Run control
+
+
+
+      </font></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Run control
 information is output after each time step can be achieved via <b>dt_run_control</b>
-= <i>0.0</i>.</font></span> </p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="end_time"></a><b>end_time</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 lang="en-GB"><font face="Thorndale">Simulation time of the 3D
+= <i>0.0</i>.</font></span> </p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="end_time"></a><b>end_time</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 lang="en-GB"><font face="Thorndale">Simulation time of the 3D
 model (</font>in <font face="Thorndale">s).&nbsp;
-</font> </p> <p><span lang="en-GB"><font face="Thorndale">The simulation time
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">The simulation time
 is starting from the beginning of the initialization run (t = 0), not
-starting from the beginning of the respective restart run.</font></span>
-</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="force_print_header"></a><b>force_print_header</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>Steering of
+starting from the beginning of the respective restart run.</font></span></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="force_print_header"></a><b>force_print_header</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>Steering of
 header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
-</p> <p>By default, informations about the model
+      </p>
+
+
+ 
+      
+      
+      <p>By default, informations about the model
 parameters in use are
 output to the beginning of file RUN_CONTROL for initial runs only
@@ -1467,14 +5515,59 @@
 these informations are
 also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
-at restart runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
-</td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><i>-1</i></td>
-<td style="vertical-align: top;"> <p>Number of
-cycles to be used with the multi-grid scheme.<br> <br>
+at restart runs.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><i>-1</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Number of
+cycles to be used with the multi-grid scheme.<br>
+
+
+ <br>
+
+
+
 This parameter determines the number of cycles to be carried out in the
 multi-grid method used for solving the Poisson equation for
 perturbation pressure (see <a href="#psolver">psolver</a>).
 The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br>
-</p> <br>By default (<b>mg_cyles</b> = <i>-
+
+
+
+      </p>
+
+
+ <br>
+
+
+By default (<b>mg_cyles</b> = <i>-
 1</i>), the
 number of cycles
@@ -1482,9 +5575,21 @@
 and may vary from time step to time step. In this case, the CPU time
 for a run will be difficult to estimate, since it heavily depends on
-the total number of the cycles to be carried out.<br> <br>
+the total number of the cycles to be carried out.<br>
+
+
+ <br>
+
+
+
 By assigning <b>mg_cycles</b> a value (&gt;=<span style="font-style: italic;">1</span>), the number of
 cycles can be
-fixed so that the CPU time can be clearly estimated. <br> <br>
-<b>Note:</b> When using a fixed number of cycles, the user
+fixed so that the CPU time can be clearly estimated. <br>
+
+
+ <br>
+
+
+
+      <b>Note:</b> When using a fixed number of cycles, the user
 must
 examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
@@ -1497,8 +5602,38 @@
 non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span>
 = <span style="font-style: italic;">4</span> may be
-sufficient.</td> </tr> <tr> <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
-level</b></td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;">Grid
-level at which data shall be gathered on PE0.<br> <br>
+sufficient.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
+
+
+
+level</b></td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">Grid
+level at which data shall be gathered on PE0.<br>
+
+
+ <br>
+
+
+
 In case of a run using several PEs and the multigrid method for solving
 the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
@@ -1509,26 +5644,131 @@
 It is only possible to gather data from a level larger than the one
 determined automatically. A test run may be neccessary to determine
-this level.</td> </tr> <tr> <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</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;">NetCDF files will have 64
-bit offset format.<br><br>By
+this level.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</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;">NetCDF files will have 64
+bit offset format.<br>
+
+
+      <br>
+
+
+By
 default, the maximum file size of the NetCDF files opened by PALM is 2
 GByte. Using netcdf_64bit = .TRUE. allows file sizes larger than 2
-GByte.<br><br>The 64 bit offset format can be separately
+GByte.<br>
+
+
+      <br>
+
+
+The 64 bit offset format can be separately
 switched off for those NetCDF files containing 3d volume date (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
-<span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>)
-using <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br><br><span style="font-weight: bold;">Warning:</span><br>Some
+      <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>)
+using <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Warning:</span><br>
+
+
+Some
 (PD or commercial) software may not support the 64 bit offset format.<br>
-</td> </tr><tr><td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;">.T.</td><td style="vertical-align: top;">NetCDF files containing 3d
-volume data will have 64 bit offset format.<br><br>This
+
+
+
+      </td>
+
+
+ </tr>
+
+
+    <tr>
+
+
+      <td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td>
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+      <td style="vertical-align: top;">.T.</td>
+
+
+      <td style="vertical-align: top;">NetCDF files containing 3d
+volume data will have 64 bit offset format.<br>
+
+
+      <br>
+
+
+This
 switch&nbsp;only comes into effect if <a href="#netcdf_64bit">netcdf_64bit</a>
 = .TRUE.. It allows to switch off separately the 64 bit offset format
 for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
-<span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>).</td></tr><tr>
-<td style="vertical-align: top;"> <p><a name="ngsrb"></a><b>ngsrb</b></p> </td>
-<td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>2</i></td>
-<td style="vertical-align: top;">Grid
-level at which data shall be gathered on PE0.<br> <br>
+      <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>).</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="ngsrb"></a><b>ngsrb</b></p>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+ <td style="vertical-align: top;"><i>2</i></td>
+
+
+
+      <td style="vertical-align: top;">Grid
+level at which data shall be gathered on PE0.<br>
+
+
+ <br>
+
+
+
 In case of a run using several PEs and the multigrid method for solving
 the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
@@ -1539,14 +5779,50 @@
 It is only possible to gather data from a level larger than the one
 determined automatically. A test run may be neccessary to determine
-this level.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
-</td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><span style="font-style: italic;">0</span><br> </td>
-<td style="vertical-align: top;"> <p>Determines the
+this level.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Determines the
 subdomain from which the normalization
-quantities are calculated.&nbsp; </p> <p>If output
+quantities are calculated.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If output
 data of the horizontally averaged vertical profiles
 (see <a href="#data_output_pr">data_output_pr</a>)
 is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>,
-<a href="#cross_normalized_y">cross_normalized_y</a>),
+      <a href="#cross_normalized_y">cross_normalized_y</a>),
 the respective normalization quantities are by default calculated from
 the averaged data of the total model domain (<b>normalizing_region</b>
@@ -1559,9 +5835,45 @@
 hold. These
 quantities are then used for normalizing of all profiles (even for that
-of the total domain).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nsor"></a><b>nsor</b></p>
-</td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><i>20</i></td>
-<td style="vertical-align: top;"> <p>Number of
-iterations to be used with the SOR-scheme.&nbsp; </p> <p>This
+of the total domain).</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="nsor"></a><b>nsor</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><i>20</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Number of
+iterations to be used with the SOR-scheme.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This
 parameter is only effective if the SOR-scheme is selected
 as pressure solver (<a href="#psolver">psolver</a>
@@ -1573,9 +5885,42 @@
 point numbers). The number of iterations used for the first call of the
 SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
-</td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><i>nz+1</i></td>
-<td style="vertical-align: top;"> Limits the output of 3d
-volume data along the vertical direction (grid point index k).<br><br>By
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><i>nz+1</i></td>
+
+
+
+      <td style="vertical-align: top;"> Limits the output of 3d
+volume data along the vertical direction (grid point index k).<br>
+
+
+      <br>
+
+
+By
 default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
 can be used to limit the output up to a certain vertical grid point
@@ -1584,9 +5929,42 @@
 for <span style="font-weight: bold;">dvrp</span>-software,
 see <a href="#mode_dvrp">mode_dvrp</a>).</td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="omega_sor"></a><b>omega_sor</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>1.8</i></td>
-<td style="vertical-align: top;"> <p>Convergence
-factor to be used with the the SOR-scheme.&nbsp; </p> <p>If
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="omega_sor"></a><b>omega_sor</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>1.8</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Convergence
+factor to be used with the the SOR-scheme.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If
 the SOR-scheme is selected (<a href="#psolver">psolver</a>
 = <span style="font-style: italic;">'sor'</span>),
@@ -1597,25 +5975,141 @@
 depends on the number of grid points along the different directions in
 space. For non-equidistant grids it can only be determined by
-appropriate test runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="prandtl_number"></a><b>prandtl_number</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>Ratio of the
+appropriate test runs.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="prandtl_number"></a><b>prandtl_number</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>Ratio of the
 eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).&nbsp;
-</p> <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
+      </p>
+
+
+ 
+      
+      
+      <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
 this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub>
-/ K<sub>h</sub>).</p> </td> </tr> <tr><td style="vertical-align: top;"><a name="precipitation_amount_interval"></a><span style="font-weight: bold;">precipitation_amount_</span><br style="font-weight: bold;"><span style="font-weight: bold;">interval</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>xy</a></i></td><td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+/ K<sub>h</sub>).</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+      <td style="vertical-align: top;"><a name="precipitation_amount_interval"></a><span style="font-weight: bold;">precipitation_amount_</span><br style="font-weight: bold;">
+
+
+      <span style="font-weight: bold;">interval</span></td>
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>
+
+
+xy</a></i></td>
+
+
+      <td style="vertical-align: top;">
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;
-</font> </p> <p><span lang="en-GB"></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"></span></a><span lang="en-GB"></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">This
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"></span></a><span lang="en-GB"></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">This
 parameter requires <a href="chapter_4.1.html#precipitation">precipitation</a> = <span style="font-style: italic;">.TRUE.</span>.&nbsp;</font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>The interval must be smaller or equal than the output interval for 2d horizontal cross sections given by </font></span><a href="chapter_4.2.html#dt_do2d_xy"><span lang="en-GB"><font face="Thorndale">dt_do2d_xy</font></span></a><span lang="en-GB"><font face="Thorndale">). The output of the precipitation amount also requires setting of <a href="chapter_4.2.html#data_output">data_output</a> =<span style="font-style: italic;"> 'pra*'</span>.<br>
-</font></span></p> <span lang="en-GB"></span></td></tr><tr>
-<td style="vertical-align: top;"> <p><a name="profile_columns"></a><b>profile_columns</b></p>
-</td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><i>3</i></td>
-<td style="vertical-align: top;"> <p>Number of
+
+
+
+      </font></span></p>
+
+
+ <span lang="en-GB"></span></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="profile_columns"></a><b>profile_columns</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><i>3</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Number of
 coordinate systems to be plotted<span style="font-weight: bold;"></span>
 in one row by <span style="font-weight: bold;">profil</span>.&nbsp;
-</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>It
+      </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>It
 determines the layout of plots of
 horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
@@ -1624,5 +6118,5 @@
 plotted on one page are
 determined by <a href="#cross_profiles">cross_profiles</a>.
-<b>profile_columns</b>
+      <b>profile_columns</b>
 determines how many panels are to be
 arranged next to each other in one row (number of columns). The
@@ -1637,32 +6131,151 @@
 If
 row&nbsp; contains any panel, then the value of <b>profile_rows</b>
-is reduced automatically.</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="profile_rows"></a><b>profile_rows</b></p>
-</td> <td style="vertical-align: top;">I</td>
-<td style="vertical-align: top;"><i>2</i></td>
-<td style="vertical-align: top;"> <p>Number of rows
+is reduced automatically.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="profile_rows"></a><b>profile_rows</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+
+      <td style="vertical-align: top;"><i>2</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Number of rows
 of coordinate systems to be plotted on one page
 by <span style="font-weight: bold;">profil</span>.&nbsp;
-</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>It
+      </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>It
 determines the layout of plots of horizontally averaged
 profiles. See <a href="#profile_columns">profile_columns</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psolver"></a><b>psolver</b></p>
-</td> <td style="vertical-align: top;">C * 10</td>
-<td style="vertical-align: top;"><i>'poisfft'</i></td>
-<td style="vertical-align: top;"> <p>Scheme to be
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="psolver"></a><b>psolver</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C * 10</td>
+
+
+
+      <td style="vertical-align: top;"><i>'poisfft'</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Scheme to be
 used to solve the Poisson equation for the
-perturbation pressure.&nbsp; </p> <br>
-The user can choose between the following schemes:<br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>poisfft</i></td>
-<td style="vertical-align: top;">Direct method using FFT
+perturbation pressure.&nbsp; </p>
+
+
+ <br>
+
+
+
+The user can choose between the following schemes:<br>
+
+
+ 
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
+
+
+ <tbody>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>poisfft</i></td>
+
+
+
+            <td style="vertical-align: top;">Direct method using FFT
 along x and y, solution of a
 tridiagonal matrix along z, and backward
 FFT (see Siano, institute reports, volume 54). The FFT routines to be
 used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
+
+
+
 This solver is specially optimized for 1d domain decompositions.
 Vectorization is optimized for domain decompositions along x only.</td>
-</tr> <tr> <td style="vertical-align: top;"><p><i>poisfft_</i>
-<br> <i>hybrid</i></p>
-</td> <td style="vertical-align: top;">Direct
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+            
+            
+            <p><i>poisfft_</i>
+            <br>
+
+
+ <i>hybrid</i></p>
+
+
+
+            </td>
+
+
+ <td style="vertical-align: top;">Direct
 method using FFT
 along x and y, solution of a
@@ -1670,8 +6283,26 @@
 FFT (see Siano, institute reports, volume 54). The FFT routines to be
 used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
+
+
+
 This solver is specially optimized for 1d domain decompositions.
 Vectorization is optimized for domain decompositions along x only.</td>
-</tr> <tr> <td style="vertical-align: top;"><i>multigrid</i></td>
-<td style="vertical-align: top;"> <p>Multi-grid
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>multigrid</i></td>
+
+
+
+            <td style="vertical-align: top;"> 
+            
+            
+            <p>Multi-grid
 scheme (see Uhlenbrock, diploma thesis). v-
 and
@@ -1683,9 +6314,15 @@
 to be carried out on each grid level. Instead the requested accuracy
 can be given via <a href="#residual_limit">residual_limit</a>.
-<span style="font-weight: bold;">This is the default!</span>
+            <span style="font-weight: bold;">This is the default!</span>
 The
 smaller this limit is, the more cycles have to be carried out in this
 case and the number of cycles may vary from timestep to timestep.</p>
-<br>If <a href="#mg_cycles">mg_cycles</a>
+
+
+
+            <br>
+
+
+If <a href="#mg_cycles">mg_cycles</a>
 is set to its optimal value, the computing time of the
 multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
@@ -1694,5 +6331,5 @@
 of space corresponds to a power-of-two (2<sup>n</sup>)
 where <i>n</i> &gt;= 5 must hold. With large <i>n,
-</i>the
+            </i>the
 multi-grid scheme can even be faster than the direct solver (although
 its accuracy is several orders of magnitude worse, but this does not
@@ -1701,36 +6338,120 @@
 for <a href="#mg_cycles">mg_cycles</a>,
 because the CPU time of a run very critically depends on this
-parameter. <p>This scheme requires that the number of grid
+parameter. 
+            
+            
+            <p>This scheme requires that the number of grid
 points of
 the
 subdomains (or of the total domain, if only one PE is uesd) along each
 of the directions can at least be devided once by 2 without rest.</p>
+
+
+
 With parallel runs, starting from a certain grid level the
 data of the subdomains are possibly gathered on PE0 in order to allow
 for a further coarsening of the grid. The grid level for gathering can
 be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
-<p>Using this procedure requires the subdomains to be of
+
+
+
+            
+            
+            <p>Using this procedure requires the subdomains to be of
 identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p>
-</td> </tr> <tr> <td style="vertical-align: top;"><i>sor</i></td>
-<td style="vertical-align: top;">Successive over
+
+
+
+            </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>sor</i></td>
+
+
+
+            <td style="vertical-align: top;">Successive over
 relaxation
 method (SOR). The convergence of
 this
 iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>,
-<a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
+            <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
 and <a href="chapter_4.1.html#nsor">nsor</a>.&nbsp;
-<br>Compared to the direct method and the multi-grid method, this
+            <br>
+
+
+Compared to the direct method and the multi-grid method, this
 scheme
 needs substantially
 more computing time. It should only be used for test runs, e.g. if
-errors in the other pressure solver methods are assumed.</td> </tr>
-</tbody> </table> <br>In order to speed-up
+errors in the other pressure solver methods are assumed.</td>
+
+
+ </tr>
+
+
+
+        
+        
+        </tbody> 
+      
+      
+      </table>
+
+
+ <br>
+
+
+In order to speed-up
 performance, the Poisson equation is by default
 only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver
 at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>).&nbsp;
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
-<br> <b>_factor</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.0 or</i><br>
-<i>0.01</i></td> <td style="vertical-align: top;">
-<p>Factor for Rayleigh damping.&nbsp; </p> <p>A
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
+      <br>
+
+
+ <b>_factor</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+ <td style="vertical-align: top;"><i>0.0 or</i><br>
+
+
+
+      <i>0.01</i></td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p>Factor for Rayleigh damping.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>A
 so-called Rayleigh damping is applied to all prognostic
 variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>.&nbsp;
@@ -1743,8 +6464,14 @@
 maximum value
 at
-the top boundary. </p> <p>This method
+the top (ocean: bottom) boundary. </p>
+
+
+ 
+      
+      
+      <p>This method
 effectively damps gravity waves, caused by boundary layer convection,
 which may spread out vertically in the inversion layer and which are
-reflected&nbsp; at the top
+reflected&nbsp;at the top (ocean: bottom)
 boundary. This particularly happens with the upstream-spline scheme
 switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
@@ -1752,24 +6479,115 @@
 Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b>
 = <i>0.01</i>) by default. Otherwise it remains switched
-off.&nbsp; </p> <p>The Rayleigh damping factor must
+off.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>The Rayleigh damping factor must
 hold the condition <i>0.0</i>
 &lt;= <b>rayleigh_damping_factor</b>
 &lt;= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
-numerical instabilities.</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
-<br> <b>_height</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"> <p><i>2/3 *</i>
-<br><span style="font-style: italic;">zu</span><i style="font-style: italic;">(nz)</i></p>
-</td> <td style="vertical-align: top;"> <p>Height
-where the Rayleigh damping starts (in m).&nbsp; </p> <p>With
+numerical instabilities.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
+      <br>
+
+
+ <b>_height</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><i>2/3 *</i>
+      <br>
+
+
+      <span style="font-style: italic;">zu</span><i style="font-style: italic;">(nz)</i></p>
+      <p> (ocean:<i style="font-style: italic;">&nbsp;</i><i>2/3 *</i>
+      <i style="font-style: italic;"> zu(0)</i>)</p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Height above (ocean: below) which the Rayleigh damping starts (in m).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>With
 Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
 this parameter determines the range where damping is applied. By
-default, Rayleigh damping will be applied in the upper third of the
+default, Rayleigh damping will be applied in the upper (ocean: lower) third of the
 model
-domain.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="residual_limit"></a><b>residual_limit</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>1.0E-6</i></td>
-<td style="vertical-align: top;"> <p>Largest
+domain.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="residual_limit"></a><b>residual_limit</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>1.0E-6</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Largest
 residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>).&nbsp;
-</p> <p>This is a parameter to steer the accuracy of the
+      </p>
+
+
+ 
+      
+      
+      <p>This is a parameter to steer the accuracy of the
 multi-grid
 scheme (see <a href="#psolver">psolver</a>).
@@ -1778,33 +6596,141 @@
 this
 is not the case after 1000 cycles, the PALM aborts with a corresponding
-error message.</p> <p>The reciprocal value of this
+error message.</p>
+
+
+ 
+      
+      
+      <p>The reciprocal value of this
 parameter can be interpreted as
 a factor by the divergence of the provisional
 velocity field is approximately reduced after the multi-grid scheme has
 been applied (thus the default value causes a reduction of the
-divergence by approx. 6 orders of magnitude).&nbsp; </p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="restart_time"></a><b>restart_time</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p>Simulated time
+divergence by approx. 6 orders of magnitude).&nbsp; </p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="restart_time"></a><b>restart_time</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Simulated time
 after which a restart run is to be carried out
-(in s). </p> <p>The simulated time refers to the
+(in s). </p>
+
+
+ 
+      
+      
+      <p>The simulated time refers to the
 beginning of the
 initial run (t = 0), not to the beginning of the respective
 restart run. Restart runs can additionally be forced to be carried out
-in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p> <p><span style="font-weight: bold;">Note:</span><br>
+in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p>
+
+
+ 
+      
+      
+      <p><span style="font-weight: bold;">Note:</span><br>
+
+
+
 A successful operation of this parameter requires additional
 modifications in the <span style="font-weight: bold;">mrun</span>-call
 for the respective run (see <a href="chapter_3.3.html">chapter
-3.3</a>).<br> </p> <p>The choice of <b>restart_time</b>
+3.3</a>).<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>The choice of <b>restart_time</b>
 or <b>dt_restart</b> does
 not override the automatic start of restart runs in case that the job
-runs out of CPU time. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="section_xy"></a><b>section_xy</b></p>
-</td> <td style="vertical-align: top;">I(100)<br>
-</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
-</td> <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position
+runs out of CPU time. <br>
+
+      </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="section_xy"></a><b>section_xy</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I(100)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale">Position
 of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
-sections (grid point index k).&nbsp; </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output
+sections (grid point index k).&nbsp; </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If output
 of
 horizontal cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this
@@ -1819,14 +6745,27 @@
 Information about the exact location of the cross section is contained
 in the NetCDF output file (if the default NetCDF output is switched on;
-see <a href="#data_output_format">data_output_format</a>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
+see <a href="#data_output_format">data_output_format</a>).</font></span></p>
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
 creates the output of horizontal cross sections averaged along z. In
 the
 NetCDF output file these (averaged) cross sections are given the
-z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
+z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p>
+
+
+      
+      
+      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
 does not effect the output of horizontal cross sections of variable u<sub>*</sub>
 and theta<sub>*</sub> and the liquid water path lwp*. For
 these quantities always only one cross
-section (for z=zu(1)) is output.</font></span></p><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
-<span style="font-style: italic;">'iso2d'</span> and
+section (for z=zu(1)) is output.</font></span></p>
+
+
+      <span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
+      <span style="font-style: italic;">'iso2d'</span> and
 if several cross sections are selected (e.g. <b>section_xy</b>
 = <i>1</i>, <i>10</i>, <i>15</i>),
@@ -1834,10 +6773,43 @@
 successively written to file. The output order follows the order given
 by <b>section_xy</b>.&nbsp;</font></span></td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="section_xz"></a><b>section_xz</b></p>
-</td> <td style="vertical-align: top;">I(100)<br>
-</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="section_xz"></a><b>section_xz</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I(100)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
 for&nbsp;output of 2d (xz) vertical cross sections (grid point
-index j).&nbsp; </font> </p> <span lang="en-GB"><font face="Thorndale">If output of
+index j).&nbsp; </font> </p>
+
+
+ <span lang="en-GB"><font face="Thorndale">If output of
 vertical xz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this
 parameter can be used to
@@ -1852,20 +6824,65 @@
 default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
 no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all
-positions.<br><br>Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
+positions.<br>
+
+
+      <br>
+
+
+Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
 creates the output of vertical cross sections averaged along y. In the
 NetCDF output file these (averaged) cross sections are given the
-y-coordinate <span style="font-style: italic;">-1.0</span>.<br></font></span><span lang="en-GB"><font face="Thorndale"><br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
-<span style="font-style: italic;">'iso2d'</span> and
-</font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
+y-coordinate <span style="font-style: italic;">-1.0</span>.<br>
+
+
+      </font></span><span lang="en-GB"><font face="Thorndale"><br>
+
+
+      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
+      <span style="font-style: italic;">'iso2d'</span> and
+      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
 selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>,
-<i>27</i>),
+      <i>27</i>),
 then the respective data are successively written to file. The output
 order follows the order given by <b>section_xz</b>.</font></span></td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="section_yz"></a><b>section_yz</b></p>
-</td> <td style="vertical-align: top;">I(100)<br>
-</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
-<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="section_yz"></a><b>section_yz</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I(100)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
 for&nbsp;output of 2d (yz) vertical cross sections (grid point
-index i).&nbsp; </font> </p> <span lang="en-GB"><font face="Thorndale">If output of
+index i).&nbsp; </font> </p>
+
+
+ <span lang="en-GB"><font face="Thorndale">If output of
 vertical yz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">),
 this parameter can be used to define the position(s) of the cross
@@ -1879,18 +6896,63 @@
 default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
 no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all
-positions.<br><br></font></span><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_yz</span> = <span style="font-style: italic;">-1</span>
+positions.<br>
+
+
+      <br>
+
+
+      </font></span><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_yz</span> = <span style="font-style: italic;">-1</span>
 creates the output of vertical cross sections averaged along x. In the
 NetCDF output file these (averaged) cross sections are given the
-x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
-<span style="font-style: italic;">'iso2d'</span> and
-</font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
+x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br>
+
+
+      <span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br>
+
+
+      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
+      <span style="font-style: italic;">'iso2d'</span> and
+      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
 selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the
 respective data are successively written to file. The output order
 follows the order given by <b>section_yz</b>.</font></span></td>
-</tr> <tr> <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
-</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;">No data output before
-this interval has passed (in s).<br><br>This
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
+
+
+
+      </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;">No data output before
+this interval has passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
@@ -1899,87 +6961,390 @@
 applies for output of instantaneous 3d volume data, cross section data,
 spectra and vertical profile data as well as for temporally averaged 2d
-and 3d data. Individual intervals can be assigned using parameters <a href="#skip_time_do3d">skip_time_do3d</a>, <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, <a href="#skip_time_dosp">skip_time_dosp</a>,&nbsp;<a href="#skip_time_dopr">skip_time_dopr</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><br><span style="font-weight: bold;">Example:</span><br>If
+and 3d data. Individual intervals can be assigned using parameters <a href="#skip_time_do3d">skip_time_do3d</a>, <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, <a href="#skip_time_dosp">skip_time_dosp</a>,&nbsp;<a href="#skip_time_dopr">skip_time_dopr</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_data_output">dt_data_output</a>
 = <span style="font-style: italic;">3600.0</span>
 and <span style="font-weight: bold;">skip_time_data_output</span>
 = <span style="font-style: italic;">1800.0</span>,
-then the first output will be done at t = 5400 s.<br> </td>
-</tr> <tr><td style="vertical-align: top;"><a name="skip_time_data_output_av"></a><span style="font-weight: bold;">skip_time_data_output_av</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>data_output</a></span></td><td style="vertical-align: top;">No output of temporally
-averaged 2d/3d data before this interval has passed (in s).<br><br>This
+then the first output will be done at t = 5400 s.<br>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+      <td style="vertical-align: top;"><a name="skip_time_data_output_av"></a><span style="font-weight: bold;">skip_time_data_output_av</span></td>
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+
+      <td style="vertical-align: top;">No output of temporally
+averaged 2d/3d data before this interval has passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_data_output_av">dt_data_output_av</a>
 = <span style="font-style: italic;">3600.0</span>
 and <span style="font-weight: bold;">skip_time_data_output_av</span>
 = <span style="font-style: italic;">1800.0</span>,
-then the first output will be done at t = 5400 s.</td></tr><tr>
-<td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
-</td> <td style="vertical-align: top;">No output of
-vertical profile data before this interval has passed (in s).<br><br>This
+then the first output will be done at t = 5400 s.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span>
+      </td>
+
+
+ <td style="vertical-align: top;">No output of
+vertical profile data before this interval has passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_dopr">dt_dopr</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dopr</span> = <span style="font-style: italic;">1800.0</span>, then the
-first output will be done at t = 5400 s. </td> </tr> <tr>
-<td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
-</td> <td style="vertical-align: top;">No output of
+first output will be done at t = 5400 s. </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span>
+      </td>
+
+
+ <td style="vertical-align: top;">No output of
 instantaneous horizontal cross section data before this interval has
-passed (in s).<br><br>This
+passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a>
 = <span style="font-style: italic;">3600.0</span>
 and <span style="font-weight: bold;">skip_time_do2d_xy</span>
 = <span style="font-style: italic;">1800.0</span>,
-then the first output will be done at t = 5400 s. </td> </tr>
-<tr> <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
-</td> <td style="vertical-align: top;">No output of
+then the first output will be done at t = 5400 s. </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span>
+      </td>
+
+
+ <td style="vertical-align: top;">No output of
 instantaneous vertical (xz) cross section data before this interval has
-passed (in s).<br><br>This
+passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a>
 = <span style="font-style: italic;">3600.0</span>
 and <span style="font-weight: bold;">skip_time_do2d_xz</span>
 = <span style="font-style: italic;">1800.0</span>,
-then the first output will be done at t = 5400 s. </td> </tr>
-<tr> <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
-</td> <td style="vertical-align: top;">No output of
+then the first output will be done at t = 5400 s. </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span>
+      </td>
+
+
+ <td style="vertical-align: top;">No output of
 instantaneous vertical (yz) cross section data before this interval has
-passed (in s).<br><br>This
+passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a>
 = <span style="font-style: italic;">3600.0</span>
 and <span style="font-weight: bold;">skip_time_do2d_yz</span>
 = <span style="font-style: italic;">1800.0</span>,
-then the first output will be done at t = 5400 s. </td> </tr>
-<tr> <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
-</td> <td style="vertical-align: top;">No output of
-instantaneous 3d volume data before this interval has passed (in s).<br><br>This
+then the first output will be done at t = 5400 s. </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span>
+      </td>
+
+
+ <td style="vertical-align: top;">No output of
+instantaneous 3d volume data before this interval has passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_do3d">dt_do3d</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_do3d</span> = <span style="font-style: italic;">1800.0</span>, then the
-first output will be done at t = 5400 s. </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="termination_time_needed"></a><b>termination_time</b>
-<br> <b>_needed</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br> </td>
-<td style="vertical-align: top;"> <p>CPU time
+first output will be done at t = 5400 s. </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="termination_time_needed"></a><b>termination_time</b>
+      <br>
+
+
+ <b>_needed</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>CPU time
 needed for terminal actions at the end of a run in
-batch mode (in s).<br> </p> <p>If the environment
+batch mode (in s).<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>If the environment
 variable <b>write_binary </b>is
 set <i>true</i> (see <a href="chapter_3.3.html">chapter
@@ -1999,5 +7364,14 @@
 respective job will be prematurely aborted by the queuing system, which
 may result in a data loss and will possibly interrupt the job chain.<br>
-</p> <p>An abort happens in any way, if the environment
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>An abort happens in any way, if the environment
 variable <span style="font-weight: bold;">write_binary</span>
 is not set to <span style="font-style: italic;">true</span>
@@ -2005,17 +7379,73 @@
 been assigned an insufficient CPU time by <b>mrun</b>
 option <tt><tt>-t</tt></tt>. <i><br>
-</i> </p> <p><span style="font-weight: bold;">Note:</span><br>
+
+
+
+      </i> </p>
+
+
+ 
+      
+      
+      <p><span style="font-weight: bold;">Note:</span><br>
+
+
+
 On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of
 PALM
 have also to be accounted for (e.g. for
-compilation and copying of input files).</p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
-<br> <b>_parameters</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>Additional
+compilation and copying of input files).</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
+      <br>
+
+
+ <b>_parameters</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>Additional
 plot of vertical profile data with <span style="font-weight: bold;">profil</span>
 from preceding runs of the
-job chain.&nbsp; </p> <p>This parameter only applies
+job chain.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies
 for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>By
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>By
 default, plots of horizontally averaged vertical profiles
 (see <a href="#data_output_pr">data_output_pr</a>)
@@ -2025,16 +7455,65 @@
 purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>.
 must be
-set.<br> </p> <p>For further explanation see <a href="chapter_4.5.2.html">chapter
-4.5.2</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>zu(nzt+1) (model
-top)</i></td> <td style="vertical-align: top;">
-<p>Height level up to which horizontally averaged profiles are to
+set.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>For further explanation see <a href="chapter_4.5.2.html">chapter
+4.5.2</a>.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>zu(nzt+1) (model
+top)</i></td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p>Height level up to which horizontally averaged profiles are to
 be
 plotted with <span style="font-weight: bold;">profil</span>
 (in
-m).&nbsp; </p> <p>This parameter only applies for
+m).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for
 &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>It
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>It
 affects plots of horizontally averaged profiles
 (<a href="#data_output_pr">data_output_pr</a>)
@@ -2046,13 +7525,68 @@
 vertical
 grid points (0 &lt;= k &lt;= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p>
-<p>If a normalization for the vertical axis was selected (see <a href="#cross_normalized_y">cross_normalized_y</a>), <b>z_max_do1d</b>
+
+
+
+      
+      
+      <p>If a normalization for the vertical axis was selected (see <a href="#cross_normalized_y">cross_normalized_y</a>), <b>z_max_do1d</b>
 has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a>
-must be used.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
-<br> <b>_normalized</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>determined by plot</i>
-<br> <i>data</i> <br> </td> <td style="vertical-align: top;"> <p>Normalized height
+must be used.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
+      <br>
+
+
+ <b>_normalized</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+ <td style="vertical-align: top;"><i>determined by plot</i>
+      <br>
+
+
+ <i>data</i> <br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Normalized height
 level up to which horizontally averaged
 profiles are to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
-</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'profil'</span>.</p><p>It
+      </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <span style="font-style: italic;">'profil'</span>.</p>
+
+
+      
+      
+      <p>It
 affects plots of horizontally averaged profiles
 (<a href="#data_output_pr">data_output_pr</a>)
@@ -2063,14 +7597,61 @@
 = <i>1.5</i> means that all profiles up to the height
 level of z =
-1.5* z<sub>i </sub>are plotted.</p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br> </td>
-<td style="vertical-align: top;"> <p>Height level
+1.5* z<sub>i </sub>are plotted.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Height level
 up to which 2d cross sections are to be plotted
 with <span style="font-weight: bold;">iso2d</span>
-(in m).&nbsp; </p> <p>This parameter only applies for
+(in m).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter only applies for
 &nbsp;<a href="#data_output_format">data_output_format</a>
-= <span style="font-style: italic;">'iso2d'</span>.</p><p>It
+= <span style="font-style: italic;">'iso2d'</span>.</p>
+
+
+      
+      
+      <p>It
 affects plots of&nbsp; 2d vertical cross
 sections (<a href="#data_output">data_output</a>)
@@ -2078,5 +7659,5 @@
 By
 default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d
-</b>the
+      </b>the
 visualization within
 the plot can be limited to a certain height level (0 &lt;= z
@@ -2092,27 +7673,122 @@
 (the respective <span style="font-weight: bold;">iso2d</span>-parameter
 is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p>
-</td> </tr> </tbody></table><br>
-<br><h3 style="line-height: 100%;"><a name="particle_parameters"></a>Particle
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ 
+  
+  
+  </tbody>
+</table>
+
+
+<br>
+
+
+
+<br>
+
+
+<h3 style="line-height: 100%;"><a name="particle_parameters"></a>Particle
 parameters: </h3>
+
+
+
 <span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>NAMELIST group name: <span style="font-weight: bold;">particles_par<br>
-</span><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
+
+
+
+</span>
+<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;"> <p><font size="4"><b>Explanation</b></font></p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_prel"></a><b>dt_prel</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
+
+
+
+      <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;"> 
+      
+      
+      <p><font size="4"><b>Explanation</b></font></p>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_prel"></a><b>dt_prel</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
 interval at
 which particles are to be released <span lang="en-GB">from
 a particle
 source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;
-</font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">By default
+      </font> </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">By default
 particles are released only at the beginning of a simulation
 (t_init=0). The time of the first release (t_init) can be changed with
 package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>.
-</font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
+      </font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
 set with the package parameter <a href="#end_time_prel">end_time_prel</a>.
 If <span style="font-weight: bold;">dt_prel</span>
@@ -2124,20 +7800,37 @@
 may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see
 e.g. </font></span><a href="#dt_dopr"><span lang="en-GB"><font face="Thorndale, serif">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">).</font></span></p>
-<p><span lang="en-GB"><font face="Thorndale, serif"> The domain
+
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif"> The domain
 of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as
 well as the distance of&nbsp; released particles
 within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package
 parameters </font></span><a href="#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="#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="#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="#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="#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="#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="#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="#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="#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"><font face="Thorndale, serif"> By
+      <span lang="en-GB"><font face="Thorndale, serif">and
+      </font></span><a href="#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"><font face="Thorndale, serif"> By
 default, one particle is released at all points defined by these
 parameters. The package parameter <a href="#particles_per_point">particles_per_point</a>
 can be used to start more than one particle per point.<br>
-</font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
+
+
+
+      </font></span></p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
 different groups of particles can be released at the same time (see </font></span><a href="chapter_4.2.html#number_of_particle_groups"><span lang="en-GB"><font face="Thorndale, serif">number_of_particle_groups</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)
 where each group may have a different source. All particles belonging
 to one group have the same density ratio and the same radius. All other
 particle features (e.g. location of the source) are
-identical for all groups of particles.</font></span></p>Subgrid
+identical for all groups of particles.</font></span></p>
+
+
+Subgrid
 scale velocities can (optionally) be included for calculating the
 particle advection, using the method of Weil et al. (2004, JAS, 61,
@@ -2147,5 +7840,8 @@
 advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>).
 The minimum timestep during the sub-timesteps is controlled by package
-parameter <a href="#dt_min_part">dt_min_part</a>. <p><span lang="en-GB"><font face="Thorndale, serif">By
+parameter <a href="#dt_min_part">dt_min_part</a>. 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">By
 default, particles are weightless and transported passively with the
 resolved scale flow. Particles can be given a mass and thus an inertia
@@ -2156,21 +7852,53 @@
 particles). In these cases their </font></span><a href="#radius"><span lang="en-GB"><font face="Thorndale, serif">radius</font></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">
 must also be defined, which affects their flow resistance. </font></span><a href="#diameter"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif"> </font></span> </p>
-<p><span lang="en-GB"><font face="Thorndale, serif">Boundary
+
+
+
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">Boundary
 conditions for the particle transport can be defined with package
 parameters </font></span><a href="#bc_par_t"><span lang="en-GB"><font face="Thorndale, serif">bc_par_t</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#bc_par_lr"><span lang="en-GB"><font face="Thorndale, serif">bc_par_lr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="bc_par_ns"><span lang="en-GB"><font face="Thorndale, serif">bc_par_ns</font></span></a>
-<span lang="en-GB"><font face="Thorndale, serif">and
-</font></span><a href="#bc_par_b"><span lang="en-GB"><font face="Thorndale, serif">bc_par_b</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span></p><span lang="en-GB"><font face="Thorndale, serif">Timeseries
+      <span lang="en-GB"><font face="Thorndale, serif">and
+      </font></span><a href="#bc_par_b"><span lang="en-GB"><font face="Thorndale, serif">bc_par_b</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span></p>
+
+
+      <span lang="en-GB"><font face="Thorndale, serif">Timeseries
 of particle quantities in NetCDF format can be output to local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>
-by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br></font></span><p>For
+by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br>
+
+
+      </font></span>
+      
+      
+      <p>For
 analysis, additional output of
 particle
 information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a>
 (file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br>
-</p> <p><span style="font-family: thorndale,serif;">Statistical
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p><span style="font-family: thorndale,serif;">Statistical
 informations</span> (e.g. the total number of particles used, the
 number of particles exchanged between the PEs, etc.) are output to the
 local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>,
 if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>.
-<br> </p> <p><span lang="en-GB"><font face="Thorndale, serif">If a job
+      <br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">If a job
 chain is to be carried out, particle
 informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
@@ -2180,5 +7908,5 @@
 run) is output to
 the local file</font></span> <font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font><a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a><font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font>,
-<span lang="en-GB"><font face="Thorndale, serif">which
+      <span lang="en-GB"><font face="Thorndale, serif">which
 must be saved at the
 end of the run <tt><span lang="en-GB"></span></tt>and
@@ -2189,5 +7917,10 @@
 respective file
 connection statements in the <span style="font-weight: bold;">mrun</span>
-configuration file. </font></span> <span lang="en-GB"></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
+configuration file. </font></span> <span lang="en-GB"></span></p>
+
+
+      
+      
+      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
 particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by
 the package
@@ -2203,56 +7936,263 @@
 &ldquo;tail&rdquo; behind themselves to improve their
 visualization.
-This is steered via the parameter&nbsp;<a href="chapter_4.2.html#use_particle_tails">use_particle_tails</a>.</font></span><a href="chapter_4.2.html#maximum_number_of_tailpoints"><span lang="en-GB"></span></a></p> <span lang="en-GB"></span><p><b>So far, the
+This is steered via the parameter&nbsp;<a href="chapter_4.2.html#use_particle_tails">use_particle_tails</a>.</font></span><a href="chapter_4.2.html#maximum_number_of_tailpoints"><span lang="en-GB"></span></a></p>
+
+
+ <span lang="en-GB"></span>
+      
+      
+      <p><b>So far, the
 particle transport realized in PALM does only
 work
-duly in case of a constant vertical grid spacing!</b></p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="bc_par_b"></a><b>bc_par_b</b></p>
-</td> <td style="vertical-align: top;">C*15</td>
-<td style="vertical-align: top;"><i>&acute;reflect&acute;</i></td>
-<td style="vertical-align: top;"> <p>Bottom
-boundary condition for particle transport. </p> <p>By
+duly in case of a constant vertical grid spacing!</b></p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="bc_par_b"></a><b>bc_par_b</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*15</td>
+
+
+
+      <td style="vertical-align: top;"><i>&acute;reflect&acute;</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Bottom
+boundary condition for particle transport. </p>
+
+
+ 
+      
+      
+      <p>By
 default, particles are reflected at the bottom boundary.
 Alternatively, a particle absorption can set by <b>bc_par_b</b>
-= <i>&acute;absorb&acute;</i>.</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
-</td> <td style="vertical-align: top;">C*15</td>
-<td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
-<td style="vertical-align: top;"> <p>Lateral
+= <i>&acute;absorb&acute;</i>.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*15</td>
+
+
+
+      <td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Lateral
 boundary condition (x-direction) for particle
-transport. </p> <p>By default, cyclic boundary conditions
+transport. </p>
+
+
+ 
+      
+      
+      <p>By default, cyclic boundary conditions
 are used along x.
 Alternatively, reflection (<b>bc_par_lr</b>
 = <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_lr</b>
 = <i>&acute;absorb&acute;</i>)
-can be set. <br> </p> <p>This lateral boundary
+can be set. <br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>This lateral boundary
 conditions should correspond to the
-lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
-</td> <td style="vertical-align: top;">C*15</td>
-<td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
-<td style="vertical-align: top;"> <p>Lateral
+lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*15</td>
+
+
+
+      <td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Lateral
 boundary condition (y-direction) for particle
-transport. </p> <p>By default, cyclic boundary conditions
+transport. </p>
+
+
+ 
+      
+      
+      <p>By default, cyclic boundary conditions
 are used along y.
 Alternatively, reflection (<b>bc_par_ns</b>
 = <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_ns</b>
 = <i>&acute;absorb&acute;</i>)
-can be set.<br> </p>
+can be set.<br>
+
+
+ </p>
+
+
+
 This lateral boundary conditions should correspond to the lateral
-boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
-</td> <td style="vertical-align: top;">C*15</td>
-<td style="vertical-align: top;"><i>&acute;absorb&acute;</i></td>
-<td style="vertical-align: top;"> <p>Top boundary
-condition for particle transport. </p> <p>By default,
+boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*15</td>
+
+
+
+      <td style="vertical-align: top;"><i>&acute;absorb&acute;</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Top boundary
+condition for particle transport. </p>
+
+
+ 
+      
+      
+      <p>By default,
 particles are absorbed at the top boundary.
 Alternatively, a reflection condition can be set by <b>bc_par_t</b>
-= <i>&acute;reflect&acute;</i>.</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="density_ratio"></a><b>density_ratio</b></p>
-</td> <td style="vertical-align: top;">R (10)</td>
-<td style="vertical-align: top;"> <p><i>0.0, 9</i>
-*<br> <i>9999999.9</i></p> </td> <td style="vertical-align: top;"> <p>Ratio of the density
+= <i>&acute;reflect&acute;</i>.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="density_ratio"></a><b>density_ratio</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)</td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><i>0.0, 9</i>
+*<br>
+
+
+ <i>9999999.9</i></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Ratio of the density
 of the fluid and the density of the
-particles. </p> <p>With the default value<i> </i>the
+particles. </p>
+
+
+ 
+      
+      
+      <p>With the default value<i> </i>the
 particles are weightless and transported passively with the resolved
 scale flow.
@@ -2266,5 +8206,11 @@
 particle radius which is determined via <a href="#radius">radius</a>
 as well as on the molecular viscosity (assumed as 1.461E-5 m<sup>2</sup>/s).
-</p> <p>If <b>density_ratio</b> = <i>1.0</i>,
+      </p>
+
+
+ 
+      
+      
+      <p>If <b>density_ratio</b> = <i>1.0</i>,
 the particle density
 corresponds to the density of the surrounding fluid and the particles
@@ -2272,5 +8218,14 @@
 upwards (<b>density_ratio</b> &gt; <i>1.0</i>)
 or downwards (<b>density_ratio</b> &lt; <i>1.0</i>).<br>
-</p> <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
 each group can be assigned a different value. If the number of values
 given for <span style="font-weight: bold;">density_ratio</span>
@@ -2279,78 +8234,569 @@
 then the last assigned value is used for all remaining groups. This
 means that by default the particle density ratio for all groups will be
-<span style="font-style: italic;">0.0</span>.</p>
-</td> </tr> <tr><td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td><td align="left" valign="top"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+      <span style="font-style: italic;">0.0</span>.</p>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+      <td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td>
+
+
+      <td align="left" valign="top">R</td>
+
+
+      <td align="left" valign="top"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+      <td align="left" valign="top">
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which time series data of particle quantities
 shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-<span lang="en-GB"><font face="Thorndale">If
+
+
+
+      <span lang="en-GB"><font face="Thorndale">If
 particle advection is switched on (see</font></span><font><span style="font-family: thorndale;"> <a href="#dt_prel">dt_prel</a>)
 this parameter can be used to assign
 th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
 interval at which time series of particle quantities shall be output.
-Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br><br>The
+Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br>
+
+
+      <br>
+
+
+The
 following list gives a short description of the&nbsp;quantities
 available. Most quantities are averages over all particles. The
 quantity name given in the first column is identical to the respective
 name of the variable on the NetCDF file (see section <a href="chapter_4.5.1.html">4.5.1</a> for a general
-description of the NetCDF files).<br><br>In case of using
+description of the NetCDF files).<br>
+
+
+      <br>
+
+
+In case of using
 more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
 seperate time series are output for each of the groups. The long names
 of the variables in the NetCDF file containing the respective
 timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle
-group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>&nbsp;</font></span><table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td><td align="undefined" valign="undefined">total number of
-particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td><td align="undefined" valign="undefined">particle
-x-coordinate&nbsp;with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td><td align="undefined" valign="undefined">particle
-y-coordinate&nbsp;with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td><td align="undefined" valign="undefined">particle
-z-coordinate&nbsp;with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td><td align="undefined" valign="undefined">absolute
-particle z-coordinate (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td><td align="undefined" valign="undefined">u particle
-velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td><td align="undefined" valign="undefined">v particle
-velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td><td align="undefined" valign="undefined">w particle
-velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td><td align="undefined" valign="undefined">subgrid-scale u
-particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td><td align="undefined" valign="undefined">subgrid-scale v
-particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td><td align="undefined" valign="undefined">subgrid-scale w
-particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td><td align="undefined" valign="undefined">total number of
-upward moving particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td><td align="undefined" valign="undefined">vertical
-velocity of the upward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td><td align="undefined" valign="undefined">vertical
-velocity of the downward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td><td align="undefined" valign="undefined">maximum number
-of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td><td align="undefined" valign="undefined">minimum number
-of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td><td align="undefined" valign="undefined">variance of the
-particle x-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td><td align="undefined" valign="undefined">variance of the
-particle y-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td><td align="undefined" valign="undefined">variance of the
-particle z-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td><td align="undefined" valign="undefined">variance of the
-u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v*2</td><td align="undefined" valign="undefined">variance of the
-v particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">v </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w*2</td><td align="undefined" valign="undefined">variance of the
-w particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">w </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">u"2</td><td align="undefined" valign="undefined">variance of the
-subgrid-scale u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v"2</td><td align="undefined" valign="undefined">variance of the
-subgrid-scale v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w"2</td><td align="undefined" valign="undefined">variance of the
-subgrid-scale w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">npt*2</td><td align="undefined" valign="undefined">variance of the
+group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
+
+
+&nbsp;</font></span>
+      
+      
+      <table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2">
+
+
+        <tbody>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td>
+
+
+            <td align="undefined" valign="undefined">total number of
+particles</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td>
+
+
+            <td align="undefined" valign="undefined">particle
+x-coordinate&nbsp;with respect to the particle origin (in m)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td>
+
+
+            <td align="undefined" valign="undefined">particle
+y-coordinate&nbsp;with respect to the particle origin (in m)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td>
+
+
+            <td align="undefined" valign="undefined">particle
+z-coordinate&nbsp;with respect to the particle origin (in m)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td>
+
+
+            <td align="undefined" valign="undefined">absolute
+particle z-coordinate (in m)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td>
+
+
+            <td align="undefined" valign="undefined">u particle
+velocity component (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td>
+
+
+            <td align="undefined" valign="undefined">v particle
+velocity component (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td>
+
+
+            <td align="undefined" valign="undefined">w particle
+velocity component (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td>
+
+
+            <td align="undefined" valign="undefined">subgrid-scale u
+particle velocity component (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td>
+
+
+            <td align="undefined" valign="undefined">subgrid-scale v
+particle velocity component (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td>
+
+
+            <td align="undefined" valign="undefined">subgrid-scale w
+particle velocity component (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td>
+
+
+            <td align="undefined" valign="undefined">total number of
+upward moving particles</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td>
+
+
+            <td align="undefined" valign="undefined">vertical
+velocity of the upward moving particles (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td>
+
+
+            <td align="undefined" valign="undefined">vertical
+velocity of the downward moving particles (in m/s)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td>
+
+
+            <td align="undefined" valign="undefined">maximum number
+of particles in a subdomain (=tnpt for non-parallel runs)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td>
+
+
+            <td align="undefined" valign="undefined">minimum number
+of particles in a subdomain (=tnpt for non-parallel runs)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+particle x-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+particle y-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+particle z-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined">v*2</td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+v particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">v </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined">w*2</td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+w particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">w </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined">u"2</td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+subgrid-scale u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined">v"2</td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+subgrid-scale v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined">w"2</td>
+
+
+            <td align="undefined" valign="undefined">variance of the
+subgrid-scale w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
+
+
+          </tr>
+
+
+          <tr>
+
+
+            <td align="undefined" valign="undefined">npt*2</td>
+
+
+            <td align="undefined" valign="undefined">variance of the
 number of particles with respect to the average number of particles per
-subdomain</td></tr></tbody></table><span lang="en-GB"></span><span lang="en-GB"></span></td></tr><tr><td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td><td align="left" valign="top">Minimum value for the
-particle timestep when SGS velocities are used (in s).<br><br>For
-a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td></tr><tr>
-<td style="vertical-align: top;"> <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b>
-<b>data</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p>Temporal
-interval for output of particle data (in s). </p> <p>T<span lang="en-GB"></span><a href="#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
+subdomain</td>
+
+
+          </tr>
+
+
+        
+        
+        </tbody>
+      
+      
+      </table>
+
+
+      <span lang="en-GB"></span><span lang="en-GB"></span></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td>
+
+
+      <td align="left" valign="top">R</td>
+
+
+      <td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td>
+
+
+      <td align="left" valign="top">Minimum value for the
+particle timestep when SGS velocities are used (in s).<br>
+
+
+      <br>
+
+
+For
+a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b>
+      <b>data</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Temporal
+interval for output of particle data (in s). </p>
+
+
+ 
+      
+      
+      <p>T<span lang="en-GB"></span><a href="#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
 parameter can be used to
 assign the temporal interval at which particle data shall be output.</font></span>
 Data are output to
 the local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>.
-<span style="font-family: mon;">See the file description
+      <span style="font-family: mon;">See the file description
 for more
-details about its format</span>. </p> <p>By
-default, no particle data are output.</p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;">0.2 * dx<br> </td>
-<td style="vertical-align: top;"> <p>Diameter that
+details about its format</span>. </p>
+
+
+ 
+      
+      
+      <p>By
+default, no particle data are output.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">0.2 * dx<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Diameter that
 the particles is given in visualizations with
 the <span style="font-weight: bold;">dvrp</span>
 software (in
-m).&nbsp; </p> <p>In case that particles are
+m).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>In case that particles are
 visualized with the <span style="font-weight: bold;">dvrp</span>
 software (see <a href="chapter_4.5.7.html">chapter
 4.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>.
 All
-particles are displayed with this same size.<br> </p> <p>Alternatively,
+particles are displayed with this same size.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>Alternatively,
 the particle diameters can be set with the
 user-interface in routine <span style="font-family: monospace;">user_init_particles</span>
@@ -2358,40 +8804,180 @@
 timestep in routine <tt>user<font style="font-size: 11pt;" size="2">_particle_attributes</font></tt>
 (both routines can be found in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt><font style="font-size: 11pt;" size="2">)</font>.&nbsp;</p>
-<p><b>Note:</b> This parameter determines exclusively
+
+
+
+      
+      
+      <p><b>Note:</b> This parameter determines exclusively
 the size
 under which particles appear in the <span style="font-weight: bold;">dvrp</span>
 visualization. The flow relevant particle radius is determined via the
 particle package parameter <a href="#radius">radius</a>!</p>
-</td> </tr> <tr><td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td><td align="left" valign="top">Time of the last release of
-particles (in s).<br><br>See also <a href="#particle_advection_start">particle_advection_start</a>.</td></tr><tr>
-<td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td>
-<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br> </td>
-<td style="vertical-align: top;">Factor to define the real
-number of initial droplets in a grid box.<br> <br>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+      <td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td>
+
+
+      <td align="left" valign="top">R</td>
+
+
+      <td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td>
+
+
+      <td align="left" valign="top">Time of the last release of
+particles (in s).<br>
+
+
+      <br>
+
+
+See also <a href="#particle_advection_start">particle_advection_start</a>.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td>
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">Factor to define the real
+number of initial droplets in a grid box.<br>
+
+
+ <br>
+
+
+
 In case of explicitly simulating cloud droplets (see <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>),
 the real number of initial droplets in a grid box is equal to the
 initial number of droplets in this box (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 <span style="font-weight: bold;">initial_weighting_factor</span>.</td>
-</tr><tr> <td style="vertical-align: top;"> <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b>
-<br> <b>particles</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>1000</i></td>
-<td style="vertical-align: top;"> <p>Maximum number
-of particles (on a PE).&nbsp; </p> <p>This parameter
+
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b>
+      <br>
+
+
+ <b>particles</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">I</td>
+
+
+ <td style="vertical-align: top;"><i>1000</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Maximum number
+of particles (on a PE).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter
 allows to set the number of particles for which
 memory must be allocated at the beginning of the run.
 If this memory becomes insufficient during the run, due to the
 release of further particles (see <a href="#dt_prel">dt_prel</a>),
-then more memory is automatically allocated.<br> </p>
+then more memory is automatically allocated.<br>
+
+
+ </p>
+
+
+
 For runs on several processors, <span style="font-weight: bold;">maximum_number_of_particles</span>
 defines
 the maximum number on each PE. This number must be larger than the
 maximum number of particles initially released in a subdomain.</td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b>
-<br> <b>tailpoints</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>Maximum number
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b>
+      <br>
+
+
+ <b>tailpoints</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>Maximum number
 of tailpoints that a particle tail can
-have.&nbsp; </p> <p>&nbsp;<b>maximum_number_of_tailpoints</b>
+have.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>&nbsp;<b>maximum_number_of_tailpoints</b>
 sets the number of descrete points the tail consists of. A new point is
 added to the particle tails after each time step. If the maximum number
@@ -2399,5 +8985,11 @@
 points is reached after the corresponding number of timesteps, the
 oldest respective tail points is deleted within the following
-timestep.&nbsp; </p> <p>All particle tails have the
+timestep.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>All particle tails have the
 same number of points. The maximum
 length of
@@ -2409,8 +9001,46 @@
 between the current position of the particle and the oldest point of
 the tail may become not larger than a value to be assigned by <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b>
-<br> <b>age</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;">100000.0</td> <td style="vertical-align: top;"> <p>Maximum age that the
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b>
+      <br>
+
+
+ <b>age</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+ <td style="vertical-align: top;">100000.0</td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Maximum age that the
 end point of a particle tail is allowed to have (in s).&nbsp; </p>
-<p>If the temporal displacement between the oldest point of a
+
+
+
+      
+      
+      <p>If the temporal displacement between the oldest point of a
 particle tail and the current position of the particle becomes larger
 than the value given by <b>maximum_tailpoint_age</b>, this
@@ -2424,19 +9054,70 @@
 particle velocity. Fast particles will have long tails, slow particles
 shorter ones (note: this will not neccessarily hold if <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>
-= <i>0.0</i>).</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</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>Minimum
+= <i>0.0</i>).</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</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>Minimum
 distance allowed between two adjacent points of a
-particle tail (in m).&nbsp; </p> <p>In case of <b>minimum_tailpoint_distance</b>
+particle tail (in m).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>In case of <b>minimum_tailpoint_distance</b>
 &gt; <i>0.0 </i>the
 particle tail is extended by a new point only if the distance between
 its current position and the most recent tail point exceed the
 distance given via <b>minimum_tailpoint_distance</b>.<br>
-</p> <p>If the length of the particle tails shall be
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>If the length of the particle tails shall be
 proportional to
 the respective particle velocity, the parameter <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>
-must also be set appropriately. </p> <b>Note:</b><br>
+must also be set appropriately. </p>
+
+
+ <b>Note:</b><br>
+
+
+
 A suitable choice of <b>minimum_tailpoint_distance</b>
 &gt; <i>0.0</i> is recommended, because then the tail
@@ -2449,101 +9130,562 @@
 should be sufficient to set <b>minimum_tailpoint_distance</b>
 = <i>5.0</i>
-(m). </td> </tr> <tr> <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br>
-</td> <td style="vertical-align: top;">I<br> </td>
-<td style="vertical-align: top;">1<br> </td> <td style="vertical-align: top;">Number of particle groups to be
-used.<br> <br>
+(m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">1<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">Number of particle groups to be
+used.<br>
+
+
+ <br>
+
+
+
 Each particle group can be assigned its own source region (see <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
-<a href="#psr">psr</a>, etc.), particle diameter (<a href="#radius">radius</a>) and particle density ratio (<a href="density_ratio">density_ratio</a>).<br><br>If
+      <a href="#psr">psr</a>, etc.), particle diameter (<a href="#radius">radius</a>) and particle density ratio (<a href="density_ratio">density_ratio</a>).<br>
+
+
+      <br>
+
+
+If
 less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
 etc. than the number of particle groups, then the last value is used
 for the remaining values (or the default value, if the user did not set
-the parameter).<br> <br>
-The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br> </td>
-</tr><tr><td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td><td align="left" valign="top">I</td><td align="left" valign="top">1</td><td align="left" valign="top">Number of particles to be
-started per point.<br><br>By default, one particle is
+the parameter).<br>
+
+
+ <br>
+
+
+
+The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+    <tr>
+
+
+      <td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td>
+
+
+      <td align="left" valign="top">I</td>
+
+
+      <td align="left" valign="top">1</td>
+
+
+      <td align="left" valign="top">Number of particles to be
+started per point.<br>
+
+
+      <br>
+
+
+By default, one particle is
 started at all points of the particle source,&nbsp;defined by <span style="font-family: Thorndale,serif;">the </span><span lang="en-GB"><font face="Thorndale, serif">package
 parameters </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"><font face="Thorndale, serif">.</font></span><span lang="en-GB"></span></td></tr><tr> <td style="vertical-align: top;"> <p><a name="particle_advection_start"></a><b>particle_advection_</b>
-<br> <b>start</b></p> </td> <td style="vertical-align: top;">R </td> <td style="vertical-align: top;">0.0 </td> <td style="vertical-align: top;"> <p>Time of the first
-release of particles (in s). </p> <p>If particles are not
+      <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"><font face="Thorndale, serif">.</font></span><span lang="en-GB"></span></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="particle_advection_start"></a><b>particle_advection_</b>
+      <br>
+
+
+ <b>start</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">R </td>
+
+
+ <td style="vertical-align: top;">0.0 </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Time of the first
+release of particles (in s). </p>
+
+
+ 
+      
+      
+      <p>If particles are not
 to be released at the beginning of the
 run, the release time can be set via <b>particle_advection_start</b>.<br>
+
+
+
 If particle transport is switched on in a restart run, then <a href="#read_particles_from_restartfile">read_particles_from_restartfile</a>
 = <span style="font-style: italic;">.F.</span> is
-also required.</p><p>See also <a href="#end_time_prel">end_time_prel</a>.
-</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p>
-</td> <td style="vertical-align: top;">R </td>
-<td style="vertical-align: top;"><i>9999999.9</i>
-</td> <td style="vertical-align: top;"> <p>Maximum
-allowed age of particles (in s).&nbsp; </p> <p>If the
+also required.</p>
+
+
+      
+      
+      <p>See also <a href="#end_time_prel">end_time_prel</a>.
+      </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R </td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i>
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Maximum
+allowed age of particles (in s).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If the
 age of a particle exceeds the time set by <b>particle_maximum_age</b>,
-the particle as well as its tail is deleted.</p> </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="pdx"></a><b>pdx</b></p> </td>
-<td style="vertical-align: top;">R (10)<br> </td>
-<td style="vertical-align: top;"><i>10 * dx</i>
-</td> <td style="vertical-align: top;"> <p>Distance
+the particle as well as its tail is deleted.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="pdx"></a><b>pdx</b></p>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">R (10)<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><i>10 * dx</i>
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Distance
 along x between particles within a particle source
-(in m).&nbsp; </p> <p>If the particle source shall be
+(in m).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If the particle source shall be
 confined to one grid point,
 the distances given by <span style="font-weight: bold;">pdx</span>,
-<a href="#pdy">pdy</a>
+      <a href="#pdy">pdy</a>
 and <a href="#pdz">pdz</a>
 must be set larger than the respective domain size or <a href="#psl">psl</a>
 = <a href="#psr">psr</a> has to be set
 alternatively.<br>
-</p> <p><span style="font-weight: bold;">pdx</span>
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p><span style="font-weight: bold;">pdx</span>
 can be assigned a different value for each particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>).<br>
-</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pdy"></a><b>pdy</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* dy</i> </td> <td style="vertical-align: top;">Distance
+
+
+
+      </p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="pdy"></a><b>pdy</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* dy</i> </td>
+
+
+ <td style="vertical-align: top;">Distance
 along y between
 particles within a
-particle source (in m).&nbsp; </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="pdz"></a><b>pdz</b></p> </td>
-<td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* ( zu(2) - zu(1) )</i> </td> <td style="vertical-align: top;">Distance along z between
+particle source (in m).&nbsp; </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="pdz"></a><b>pdz</b></p>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* ( zu(2) - zu(1) )</i> </td>
+
+
+ <td style="vertical-align: top;">Distance along z between
 particles within a particle source
-(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psb"></a><b>psb</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10&nbsp;
-* zu(nz/2)</i> </td> <td style="vertical-align: top;">Bottom
+(in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="psb"></a><b>psb</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10&nbsp;
+* zu(nz/2)</i> </td>
+
+
+ <td style="vertical-align: top;">Bottom
 edge of a particle
-source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psl"></a><b>psl</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* 0.0</i> </td> <td style="vertical-align: top;">Left
+source (in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="psl"></a><b>psl</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* 0.0</i> </td>
+
+
+ <td style="vertical-align: top;">Left
 edge of a particle source
-(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psn"></a><b>psn</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* (ny * dy)</i> </td> <td style="vertical-align: top;">Rear
+(in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="psn"></a><b>psn</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* (ny * dy)</i> </td>
+
+
+ <td style="vertical-align: top;">Rear
 (&ldquo;north&rdquo;) edge of a
-particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psr"></a><b>psr</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* (nx * dx)</i> </td> <td style="vertical-align: top;">Right
+particle source (in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="psr"></a><b>psr</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* (nx * dx)</i> </td>
+
+
+ <td style="vertical-align: top;">Right
 edge of a particle
-source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pss"></a><b>pss</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* 0.0</i> </td> <td style="vertical-align: top;">Front
+source (in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="pss"></a><b>pss</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* 0.0</i> </td>
+
+
+ <td style="vertical-align: top;">Front
 (&ldquo;south&rdquo;) edge of a
-particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pst"></a><b>pst</b></p>
-</td> <td style="vertical-align: top;">R (10)<br>
-</td> <td style="vertical-align: top;"><i>10
-* zu(nz/2)</i> </td> <td style="vertical-align: top;">Top
+particle source (in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="pst"></a><b>pst</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"><i>10
+* zu(nz/2)</i> </td>
+
+
+ <td style="vertical-align: top;">Top
 edge of a particle source
-(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="radius"></a><b>radius</b></p>
-</td> <td style="vertical-align: top;">R (10)</td>
-<td style="vertical-align: top;"><i>0.0, 9</i>*<br>
-<i>9999999.9</i></td> <td style="vertical-align: top;">Particle radius (in m).<br>
-<br>The viscous friction (in case of a velocity difference
+(in m). </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="radius"></a><b>radius</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R (10)</td>
+
+
+
+      <td style="vertical-align: top;"><i>0.0, 9</i>*<br>
+
+
+
+      <i>9999999.9</i></td>
+
+
+ <td style="vertical-align: top;">Particle radius (in m).<br>
+
+
+
+      <br>
+
+
+The viscous friction (in case of a velocity difference
 between
 particles and surrounding fluid) depends on the particle radius which
 must be assigned as soon as <a href="chapter_4.2.html#density_ratio">density_ratio</a>
-/= <i>0.0</i>.<br> <br>
+/= <i>0.0</i>.<br>
+
+
+ <br>
+
+
+
 With several groups of particles (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
 each group can be assigned a different value. If the number of values
@@ -2552,23 +9694,71 @@
 groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
 then the last assigned value is used for all remaining groups. This
-means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br> </td>
-</tr><tr> <td style="vertical-align: top;"> <p><a name="random_start_position"></a><b>random_start_position</b></p>
-</td> <td style="vertical-align: top;">L<br> </td>
-<td style="vertical-align: top;"><i>.F.</i> </td>
-<td style="vertical-align: top;"> <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
+means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="random_start_position"></a><b>random_start_position</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><i>.F.</i> </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
 particles is
-varied randomly within certain limits.&nbsp; </p> <p>By
+varied randomly within certain limits.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>By
 default, the initial positions of particles within the
 source excatly correspond with the positions given by <a href="#psl">psl</a>,
-<a href="#psr">psr</a>, <a href="#psn">psn</a>,
-<a href="#pss">pss</a>, <a href="#psb">psb</a>,
-<a href="#pst">pst</a>, <a href="#pdx">pdx</a>,
-<a href="#pdy">pdy</a>,
+      <a href="#psr">psr</a>, <a href="#psn">psn</a>,
+      <a href="#pss">pss</a>, <a href="#psb">psb</a>,
+      <a href="#pst">pst</a>, <a href="#pdx">pdx</a>,
+      <a href="#pdy">pdy</a>,
 and<a href="#pdz">
 pdz</a>. With <b>random_start_position</b> = <i>.T.
-</i>the initial
+      </i>the initial
 positions of the particles are allowed to randomly vary from these
-positions within certain limits.&nbsp; </p> <p><b>Very
-important:<br> </b>In case of <b>random_start_position</b>
+positions within certain limits.&nbsp; </p>
+
+
+ 
+      
+      
+      <p><b>Very
+important:<br>
+
+
+ </b>In case of <b>random_start_position</b>
 = <i>.T.</i>, the
 random-number generators on the individual PEs no longer&nbsp;
@@ -2576,12 +9766,54 @@
 field
 (see <a href="#create_disturbances">create_disturbances</a>),
-<font color="#000000">then as consequence for parallel
+      <font color="#000000">then as consequence for parallel
 runs the
 realizations of the turbulent flow
 fields will deviate between runs which used different numbers of PEs!</font></p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b>
-<br> <b>restartfile</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td>
-<td style="vertical-align: top;"> <p>Read particle
-data from the previous run.&nbsp; </p> <p>By default,
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b>
+      <br>
+
+
+ <b>restartfile</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><i>.T.</i> </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Read particle
+data from the previous run.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>By default,
 with restart runs particle data is read
 from file <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
@@ -2590,28 +9822,148 @@
 first time (see <a href="#particle_advection_start">particle_advection_start</a>),
 then <b>read_particles_from_restartfile</b> = <i>.F.</i>
-is required.</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br>
-</td> <td style="vertical-align: top;">I<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">1</span><br> </td>
-<td style="vertical-align: top;">Limit the number of
-particle tails.<br> <br>
+is required.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">1</span><br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;">Limit the number of
+particle tails.<br>
+
+
+ <br>
+
+
+
 If particle tails are switched on (see <a href="#use_particle_tails">use_particle_tails</a>),
 every particle is given a tail by default. <span style="font-weight: bold;">skip_particles_for_tail </span>can
-be used to give only every n'th particle a tail.<br> <br> <span style="font-weight: bold;">Example:</span><br> <span style="font-weight: bold;">skip_particles_for_tail</span>
+be used to give only every n'th particle a tail.<br>
+
+
+ <br>
+
+
+ <span style="font-weight: bold;">Example:</span><br>
+
+
+ <span style="font-weight: bold;">skip_particles_for_tail</span>
 = <span style="font-style: italic;">10</span> means
-that only every 10th particle will be given a tail.<br> </td>
-</tr> <tr> <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</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;">Give particles a tail.<br>
-<br>A particle tail is defined by the path a particle has moved
+that only every 10th particle will be given a tail.<br>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</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;">Give particles a tail.<br>
+
+
+
+      <br>
+
+
+A particle tail is defined by the path a particle has moved
 along starting from some point of time in the past. It consists of a
 set of descrete points in space which may e.g. be connected by a line
-in order visualize how the particle has moved.<br> <br>
+in order visualize how the particle has moved.<br>
+
+
+ <br>
+
+
+
 By default, particles have no tail. Parameter&nbsp;<a href="#skip_particles_for_tail">skip_particles_for_tail</a>
-can be used to give only every n'th particle a tail.<br> <br>
+can be used to give only every n'th particle a tail.<br>
+
+
+ <br>
+
+
+
 The length of the tail is controlled by parameters&nbsp;<a href="#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>,&nbsp;<a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>,
 and <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.<br>
-</td> </tr><tr><td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</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">Use subgrid-scale
-velocities for particle advection.<br><br>These
+
+
+
+      </td>
+
+
+ </tr>
+
+
+    <tr>
+
+
+      <td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</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">Use subgrid-scale
+velocities for particle advection.<br>
+
+
+      <br>
+
+
+These
 velocities are calculated from the resolved and subgrid-scale TKE using
 the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
@@ -2623,6 +9975,12 @@
 order to limit the number of sub-timesteps (and to limit the CPU-time),
 the minimum value for the particle timestep is defined by the package
-parameter <a href="#dt_min_part">dt_min_part</a>.<br><br>Setting
-<span style="font-weight: bold;">use_sgs_for_particles</span>
+parameter <a href="#dt_min_part">dt_min_part</a>.<br>
+
+
+      <br>
+
+
+Setting
+      <span style="font-weight: bold;">use_sgs_for_particles</span>
 = <span style="font-style: italic;">.TRUE.</span>
 automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>
@@ -2630,16 +9988,103 @@
 This inhibits the occurrence of large (artificial) spatial gradients of
 the subgrid-scale TKE which otherwise would lead to wrong results for
-the particle advection.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b>
-<br> <b>advection</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td>
-<td style="vertical-align: top;"> <p>Switch on/off
-vertical particle transport. </p> <p>By default,
+the particle advection.</td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b>
+      <br>
+
+
+ <b>advection</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><i>.T.</i> </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Switch on/off
+vertical particle transport. </p>
+
+
+ 
+      
+      
+      <p>By default,
 particles are transported along all three
 directions in space. With <b>vertical_particle_advection</b>
 = <i>.F., </i>the
-particles will only be transported horizontally.</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="write_particle_statistics"></a><b>write_particle_</b>
-<br> <b>statistics</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.F.</i> </td>
-<td style="vertical-align: top;"> <p>Switch on/off
-output of particle informations.<br> </p> <p><br>
+particles will only be transported horizontally.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="write_particle_statistics"></a><b>write_particle_</b>
+      <br>
+
+
+ <b>statistics</b></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;">L<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><i>.F.</i> </td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Switch on/off
+output of particle informations.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p><br>
+
+
+
 For <span style="font-weight: bold;">write_particle_statistics</span>
 = <span style="font-style: italic;">.T.</span> s<span style="font-family: thorndale,serif;">tatistical
@@ -2648,29 +10093,135 @@
 for debugging are output to the
 local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>.&nbsp;
-</p> <p><b>Note:</b> For parallel runs files
+      </p>
+
+
+ 
+      
+      
+      <p><b>Note:</b> For parallel runs files
 may become very large
-and performance of PALM may decrease.</p> </td> </tr>
-</tbody></table><span style="font-weight: bold;"><br>
-</span><br><h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
-parameters: </h3><br><span style="font-weight: bold;">Package
+and performance of PALM may decrease.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+
+  
+  
+  </tbody>
+</table>
+
+
+<span style="font-weight: bold;"><br>
+
+
+
+</span><br>
+
+
+<h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
+parameters: </h3>
+
+
+<br>
+
+
+<span style="font-weight: bold;">Package
 (<span style="font-weight: bold;">mrun</span> option
 -p): <span style="font-weight: bold;"><a name="dvrp_graphics"></a>dvrp_graphics</span>
 &nbsp;&nbsp;&nbsp;
 NAMELIST group name: <span style="font-weight: bold;">dvrp_graphics_par<br>
-<br></span></span><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="dt_dvrp"></a><b>dt_dvrp</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>9999999.9</i></td>
-<td style="vertical-align: top;"> <p>Temporal
+
+
+
+<br>
+
+
+</span></span>
+<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="dt_dvrp"></a><b>dt_dvrp</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>9999999.9</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Temporal
 interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
-s).&nbsp; </p> <p>Isosurfaces, cross sections and
+s).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Isosurfaces, cross sections and
 particles can be displayed
 simultaneous. The display of particles requires that the particle
 transport is switched on (see <a href="#dt_prel">dt_prel</a>).
-Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p> <p>If
+Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p>
+
+
+ 
+      
+      
+      <p>If
 output of scenes created by dvrp software is switched on
 (see <a href="#mode_dvrp">mode_dvrp</a>),
@@ -2686,25 +10237,97 @@
 scenes are created and
 output after each time step (if this is requested it should be <b>dt_dvrp</b>
-= <i>0</i>).</font></span> </p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="dvrp_directory"></a><b>dvrp_directory</b></p>
-</td> <td style="vertical-align: top;">C*80</td>
-<td style="vertical-align: top;"><i>'default'</i></td>
-<td style="vertical-align: top;"> <p>Name of the
+= <i>0</i>).</font></span> </p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="dvrp_directory"></a><b>dvrp_directory</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*80</td>
+
+
+
+      <td style="vertical-align: top;"><i>'default'</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Name of the
 directory into which data created by the <span style="font-weight: bold;">dvrp</span>
-software shall be saved.&nbsp; </p> <p>By default,
+software shall be saved.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>By default,
 the directory name is generated from the user
 name
 (see package parameter <a href="#dvrp_username">dvrp_username</a>)
 and the base file name (given as the argument of <span style="font-weight: bold;">mrun</span> option -d) as <span style="font-style: italic;">'&lt;user
-name&gt;/&lt;base file name&gt;'</span>.</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="dvrp_file"></a><b>dvrp_file</b></p>
-</td> <td style="vertical-align: top;">C*80</td>
-<td style="vertical-align: top;"><i>'default'</i></td>
-<td style="vertical-align: top;"> <p>Name of the
+name&gt;/&lt;base file name&gt;'</span>.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="dvrp_file"></a><b>dvrp_file</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*80</td>
+
+
+
+      <td style="vertical-align: top;"><i>'default'</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Name of the
 file into which data created by the <span style="font-weight: bold;">dvrp</span>
-software shall be output.&nbsp; </p> <p>This
+software shall be output.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This
 parameter can be given a value only in case of <a href="#dvrp_output">dvrp_output</a>
 = <span style="font-style: italic;">'local'</span><i>
-</i>which
+      </i>which
 determines that the data created by <span style="font-weight: bold;">dvrp</span>
 is output to a local file (on the machine where PALM is executed).
@@ -2712,11 +10335,56 @@
 means that no output is really stored). This can be used for special
 runtime measurements of the <span style="font-weight: bold;">dvrp</span>
-software.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_host"></a><b>dvrp_host</b></p>
-</td> <td style="vertical-align: top;">C*80</td>
-<td style="vertical-align: top;"> <p><i>'origin.rvs.</i>
-<br>u<i>ni- hanover.de'</i></p> </td> <td style="vertical-align: top;"> <p>Name of the computer
+software.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dvrp_host"></a><b>dvrp_host</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*80</td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><i>'origin.rvs.</i>
+      <br>
+
+
+u<i>ni- hanover.de'</i></p>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Name of the computer
 to which data created by the <span style="font-weight: bold;">dvrp</span>
 software shall be
-transferred.&nbsp; </p> <p>In case of <a href="#dvrp_output">dvrp_output</a>
+transferred.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>In case of <a href="#dvrp_output">dvrp_output</a>
 = <span style="font-style: italic;">'rtsp'</span>
 only the default
@@ -2724,18 +10392,81 @@
 the RRZN). For <a href="#dvrp_output">dvrp_output</a>
 = <span style="font-style: italic;">'local'</span><i>
-</i>the
-assigned value is ignored.</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="dvrp_output"></a><b>dvrp_output</b></p>
-</td> <td style="vertical-align: top;">C*10</td>
-<td style="vertical-align: top;"><i>'rtsp'</i></td>
-<td style="vertical-align: top;"> <p>Output mode
+      </i>the
+assigned value is ignored.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dvrp_output"></a><b>dvrp_output</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*10</td>
+
+
+
+      <td style="vertical-align: top;"><i>'rtsp'</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Output mode
 for the <span style="font-weight: bold;">dvrp</span>
-software. <br> <br> </p>
-The following settings are allowed:<br> <br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'rtsp'</i></td>
-<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
+software. <br>
+
+
+ <br>
+
+
+ </p>
+
+
+
+The following settings are allowed:<br>
+
+
+ <br>
+
+
+ 
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
+
+
+ <tbody>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>'rtsp'</i></td>
+
+
+
+            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
 software is transferred using
 a special transmission protocol to a so-called streaming server, which
 is able to continuously transfer visualization data with a
 high transmission rate.&nbsp; <br>
+
+
+
 Additionally, with this output mode a
 set of files is generated automatically
@@ -2745,42 +10476,194 @@
 (streaming-server) and directory can be defined by the user with <a href="#dvrp_host">dvrp_host</a>
 and <a href="#dvrp_directory">dvrp_directory</a>.</td>
-</tr> <tr> <td style="vertical-align: top;"><i>'ftp'</i></td>
-<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
+
+
+
+          </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>'ftp'</i></td>
+
+
+
+            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
 software is transferred to the destination host (see <a href="#dvrp_host">dvrp_host</a>
 and <a href="#dvrp_directory">dvrp_directory</a>)
-using ftp.</td> </tr> <tr> <td style="vertical-align: top;"><i>'local'</i></td>
-<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
+using ftp.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><i>'local'</i></td>
+
+
+
+            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
 software is output locally on a file defined by <a href="#dvrp_file">dvrp_file
-</a>.</td> </tr> </tbody> </table> <br>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_password"></a><b>dvrp_password</b></p>
-</td> <td style="vertical-align: top;">C*80</td>
-<td style="vertical-align: top;">'********'</td> <td style="vertical-align: top;"> <p>Password for the
+            </a>.</td>
+
+
+ </tr>
+
+
+ 
+        
+        
+        </tbody> 
+      
+      
+      </table>
+
+
+ <br>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dvrp_password"></a><b>dvrp_password</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*80</td>
+
+
+
+      <td style="vertical-align: top;">'********'</td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Password for the
 computer to which data created by the <span style="font-weight: bold;">dvrp</span> software is to
 be
-transferred.&nbsp; </p> <p>Assigning a password is
+transferred.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Assigning a password is
 only necessary in case of <a href="#dvrp_output">dvrp_output</a>
 = <span style="font-style: italic;">'ftp'</span>.
 For <a href="#dvrp_output">dvrp_output</a>
 = <span style="font-style: italic;">'rtsp'</span><i>
-</i>the default
-value must not be changed!</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="dvrp_username"></a><b>dvrp_username</b></p>
-</td> <td style="vertical-align: top;">C*80</td>
-<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>User name of a valid
+      </i>the default
+value must not be changed!</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dvrp_username"></a><b>dvrp_username</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*80</td>
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>User name of a valid
 account on the computer to which data
 created by the <span style="font-weight: bold;">dvrp</span>
 software
 is to be
-transferred.&nbsp; </p> <p>Assigning a value to this
+transferred.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Assigning a value to this
 parameter is required in case of <a href="#dvrp_output">dvrp_output</a>
 = <span style="font-style: italic;">'rtsp'</span>
 or <span style="font-style: italic;">'ftp'</span>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p>
-</td> <td style="vertical-align: top;">C*20&nbsp;
-<br>(10)</td> <td style="vertical-align: top;"><i>10
-* ''</i></td> <td style="vertical-align: top;">
-<p>Graphical objects (isosurfaces, slicers, particles) which are
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*20&nbsp;
+      <br>
+
+
+(10)</td>
+
+
+ <td style="vertical-align: top;"><i>10
+* ''</i></td>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p>Graphical objects (isosurfaces, slicers, particles) which are
 to be created by the <span style="font-weight: bold;">dvrp</span>
-software.&nbsp; </p> <p>Several different objects can
+software.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Several different objects can
 be assigned simultaneously and
 will be displayed in the same scene. Allowed values for <span style="font-weight: bold;">mode_dvrp</span> are <span style="font-style: italic;">'isosurface#'</span>
@@ -2789,8 +10672,20 @@
 Within the strings the hash character ("#") has to be replaced by a
 digit &le;9. Up to 10 objects
-can be assigned at the same time, e.g. :&nbsp; </p> <blockquote><b>mode_dvrp</b>
+can be assigned at the same time, e.g. :&nbsp; </p>
+
+
+ 
+      
+      
+      <blockquote><b>mode_dvrp</b>
 = <span style="font-style: italic;">'isosurface2'</span><i>,
 'slicer1',
-'particles', 'slicer2'</i></blockquote> <p>In this
+'particles', 'slicer2'</i></blockquote>
+
+
+ 
+      
+      
+      <p>In this
 case one isosurface, two cross sections, and particles
 will be created. The quantities for which an isosurface are to be
@@ -2819,7 +10714,30 @@
 The theshold value for which the isosurface is
 to be created can be defined with parameter <a href="#threshold">threshold</a>.<br>
-</p> <p>The vertical extension of the displayed domain is
-given by <a href="#nz_do3d">nz_do3d</a>.<br> </p>
-<p>The vertical extension of the displayed domain is given by <a href="#nz_do3d">nz_do3d</a>. </p> <p><b>Assignments
+
+
+
+      </p>
+
+
+ 
+      
+      
+      <p>The vertical extension of the displayed domain is
+given by <a href="#nz_do3d">nz_do3d</a>.<br>
+
+
+ </p>
+
+
+
+      
+      
+      <p>The vertical extension of the displayed domain is given by <a href="#nz_do3d">nz_do3d</a>. </p>
+
+
+ 
+      
+      
+      <p><b>Assignments
 of mode_dvrp must correspond to those of data_output
 and
@@ -2830,11 +10748,29 @@
 thus <span style="font-style: italic;">'isosurface1'</span>
 and/or <span style="font-style: italic;">'slicer1'</span><i>.</i>&nbsp;
-</p> <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are
+      </p>
+
+
+ 
+      
+      
+      <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are
 given in <a href="chapter_4.5.7.html">chapter
-4.5.7</a>.<br> </p> <b>Note:</b><br>
+4.5.7</a>.<br>
+
+
+ </p>
+
+
+ <b>Note:</b><br>
+
+
+
 The declaration color charts to be
 used still have to be given "manually" in subroutine <span style="font-family: monospace;">user_dvrp_coltab</span>
 (file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;
-<br>A change of particle colors and/or particle diameters (e.g.
+      <br>
+
+
+A change of particle colors and/or particle diameters (e.g.
 according
 to the local characteristics of the flow field) to be used for the
@@ -2842,10 +10778,37 @@
 to <tt><font style="font-size: 11pt;" size="2">user_particle_attributes</font></tt>
 (in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;</td>
-</tr> <tr> <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br>
-dvrp</span></td> <td style="vertical-align: top;">R(2,10)</td>
-<td style="vertical-align: top;"><span style="font-style: italic;">10
-* (-1,1)</span></td> <td style="vertical-align: top;">Ranges
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br>
+
+
+
+dvrp</span></td>
+
+
+ <td style="vertical-align: top;">R(2,10)</td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10
+* (-1,1)</span></td>
+
+
+ <td style="vertical-align: top;">Ranges
 of values to which a color table has to be mapped (units of the
-respective quantity).<br> <br>
+respective quantity).<br>
+
+
+ <br>
+
+
+
 In case that slicers have to be displayed (see <a href="#threshold">mode_dvrp</a>),
 this parameter defines the ranges of values of the respective
@@ -2857,14 +10820,59 @@
 within these limits will be displayed by a continuous color gradient
 from blue to red and Temperatures outside the limits will
-be displayed either in dark blue or in dark red.<br> <br>
+be displayed either in dark blue or in dark red.<br>
+
+
+ <br>
+
+
+
 Up to ten different ranges can be assigned in case that more than one
-slicer has to be displayed.<br> <br>
+slicer has to be displayed.<br>
+
+
+ <br>
+
+
+
 See <a href="#threshold">mode_dvrp</a>
-for the declaration of color charts.</td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="superelevation"></a><b>superelevation</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>Superelevation
-factor for the vertical coordinate.&nbsp; </p> <p>For
+for the declaration of color charts.</td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="superelevation"></a><b>superelevation</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>Superelevation
+factor for the vertical coordinate.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>For
 domains with unfavorable ratio between the vertical and
 the horizontal size
@@ -2879,27 +10887,147 @@
 be used, since otherwise the domain appears as a
 "flat disk" in the visualization and thus the vertical direction is
-only very poorly resolved.</p> </td> </tr> <tr>
-<td style="vertical-align: top;"> <p><a name="superelevation_x"></a><b>superelevation_x</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top; font-style: italic;">1.0<br>
-</td> <td style="vertical-align: top;"> <p>Superelevation
-factor for the horizontal (x) coordinate.&nbsp; </p> <p>This
+only very poorly resolved.</p>
+
+
+ </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="superelevation_x"></a><b>superelevation_x</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top; font-style: italic;">1.0<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Superelevation
+factor for the horizontal (x) coordinate.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This
 parameter can be used to stretch the displayed domain
 along the x-direction. See also <a href="#superelevation">superelevation</a>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="superelevation_y"></a><b>superelevation_y</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top; font-style: italic;">1.0<br>
-</td> <td style="vertical-align: top;">Superelevation
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="superelevation_y"></a><b>superelevation_y</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top; font-style: italic;">1.0<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">Superelevation
 factor for the
-horizontal (y) coordinate.&nbsp; <p>This parameter can be
+horizontal (y) coordinate.&nbsp; 
+      
+      
+      <p>This parameter can be
 used to
-stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="threshold"></a><b>threshold</b></p>
-</td> <td style="vertical-align: top;">R(10)<br>
-</td> <td style="vertical-align: top; font-style: italic;">0.0<br>
-</td> <td style="vertical-align: top;"> <p>Threshold
+stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="threshold"></a><b>threshold</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R(10)<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top; font-style: italic;">0.0<br>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Threshold
 value for which an isosurface is to be created by
 the <span style="font-weight: bold;">dvrp</span>
-software.&nbsp; </p> <p>If the creation of
+software.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If the creation of
 isosurfaces is switched on via
 parameter <a href="#mode_dvrp">mode_dvrp</a>,
@@ -2911,22 +11039,114 @@
 each isosurface can be assigned. The order of the threshold values
 refers to the order of the isosurfaces given by <b>mode_dvrp</b>.</p>
-</td> </tr> </tbody></table><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ 
+  
+  
+  </tbody>
+</table>
+
+
+<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
+
+
+
 </span></span><span style="font-weight: bold;"><span style="font-weight: bold;">Package (<span style="font-weight: bold;">mrun</span>
 option -p): <span style="font-weight: bold;"><a name="spectra"></a>spectra</span>&nbsp;&nbsp;&nbsp;&nbsp;
 NAMELIST group name: <span style="font-weight: bold;">spectra_par<br>
-<br></span></span></span><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="averaging_interval_sp"></a><b>averaging_interval_sp</b></p>
-</td> <td style="vertical-align: top;">R<br> </td>
-<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
-interval</a></span> </td> <td style="vertical-align: top;"> <p>Averaging interval
+
+
+
+<br>
+
+
+</span></span></span>
+<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="averaging_interval_sp"></a><b>averaging_interval_sp</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
+
+
+
+interval</a></span> </td>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p>Averaging interval
 for spectra output to local
 file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
-</font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
+      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
 / &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
-(in s).&nbsp; </p> <p>If
+(in s).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>If
 this parameter is given a non-zero value, temporally
 averaged spectra data are output. By default, spectra data data are not
@@ -2934,34 +11154,134 @@
 parameter <a href="#dt_dosp">dt_dosp</a>. In any
 case <b>averaging_interval_sp</b> &lt;= <b>dt_dosp
-</b>must
-hold.</p>If an interval is defined, then by default the average
+      </b>must
+hold.</p>
+
+
+If an interval is defined, then by default the average
 is calculated
 from the data values of all timesteps lying within this interval. The
 number of time levels entering into the average can be reduced with the
 parameter <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>.
-<p>If
+      
+      
+      <p>If
 an averaging interval can not be completed at the end of a run, it will
 be finished at the beginning of the next restart run. Thus for restart
 runs, averaging intervals do not
-necessarily begin at the beginning of the run.</p></td> </tr>
-<tr> <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td>
-<td style="vertical-align: top;">I(10)</td> <td style="vertical-align: top;"><i>no level</i></td>
-<td style="vertical-align: top;"> <p>Vertical level
+necessarily begin at the beginning of the run.</p>
+
+
+      </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td>
+
+
+
+      <td style="vertical-align: top;">I(10)</td>
+
+
+ <td style="vertical-align: top;"><i>no level</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Vertical level
 for which horizontal spectra are to be
-calculated and output (gridpoints).<br> </p> <br>
-Spectra can be calculated for up to ten levels.</td> </tr>
-<tr><td style="vertical-align: top;"><p><a name="data_output_sp"></a><b>data_output_sp</b></p></td><td style="vertical-align: top;">C*10 (10)</td><td style="vertical-align: top;"><i>10 * ' '</i></td><td style="vertical-align: top;"><p>Quantities for which
+calculated and output (gridpoints).<br>
+
+
+ </p>
+
+
+ <br>
+
+
+
+Spectra can be calculated for up to ten levels.</td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+      <td style="vertical-align: top;">
+      
+      
+      <p><a name="data_output_sp"></a><b>data_output_sp</b></p>
+
+
+      </td>
+
+
+      <td style="vertical-align: top;">C*10 (10)</td>
+
+
+      <td style="vertical-align: top;"><i>10 * ' '</i></td>
+
+
+      <td style="vertical-align: top;">
+      
+      
+      <p>Quantities for which
 horizontal spectra are to be calculated
-and output.</p> <p>Allowed values are:&nbsp; <b>data_output_sp</b>
-= <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>, <span style="font-style: italic;">'w'</span>, <span style="font-style: italic;">'pt'</span>, <span style="font-style: italic;">'q'</span>.<br> </p>
-<p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p>
-<p>By default spectra data are output to the local file <a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>.
+and output.</p>
+
+
+ 
+      
+      
+      <p>Allowed values are:&nbsp; <b>data_output_sp</b>
+= <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>, <span style="font-style: italic;">'w'</span>, <span style="font-style: italic;">'pt'</span>, <span style="font-style: italic;">'q'</span>.<br>
+
+
+ </p>
+
+
+
+      
+      
+      <p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p>
+
+
+
+      
+      
+      <p>By default spectra data are output to the local file <a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>.
 The file's format is NetCDF.&nbsp; Further details about processing
-NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>The
+NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
+
+
+      
+      
+      <p>The
 temporal interval of the output times of profiles is
-assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>.&nbsp;</p><p>The
+assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>.&nbsp;</p>
+
+
+      
+      
+      <p>The
 vertical levels for which spectra are to be computed and output must be
 given by parameter <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.
-</p><span style="font-weight: bold;">Note:</span><br>
+      </p>
+
+
+      <span style="font-weight: bold;">Note:</span><br>
+
+
+
 Beside <span style="font-weight: bold;">data_output_sp</span>,
 values <span style="font-weight: bold;">must</span>
@@ -2971,5 +11291,14 @@
 otherwise <span style="font-weight: bold;">no</span>
 output will be
-created!<br><br><br>
+created!<br>
+
+
+      <br>
+
+
+      <br>
+
+
+
 Calculation of spectra requires cyclic boundary conditions
 along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
@@ -3009,12 +11338,51 @@
 parameter values can be changed by editing the parameter
 input
-file.<span style="font-weight: bold;"><br></span></td></tr><tr>
-<td style="vertical-align: top;"> <p><a name="dt_dosp"></a><b>dt_dosp</b></p>
-</td> <td style="vertical-align: top;">R</td>
-<td style="vertical-align: top;"><i>value of
-&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
-<td style="vertical-align: top;"> <p>Temporal
+file.<span style="font-weight: bold;"><br>
+
+
+      </span></td>
+
+
+    </tr>
+
+
+    <tr>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="dt_dosp"></a><b>dt_dosp</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">R</td>
+
+
+
+      <td style="vertical-align: top;"><i>value of
+&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+
+
+output</a></i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Temporal
 interval at which&nbsp;spectra data shall be output
-(in s).&nbsp; </p> <p><span lang="en-GB"><font face="Thorndale">If output of
+(in s).&nbsp; </p>
+
+
+ 
+      
+      
+      <p><span lang="en-GB"><font face="Thorndale">If output of
 horizontal spectra is switched on (see </font></span><a href="#data_output_sp"><span lang="en-GB"><font face="Thorndale">data_output_sp</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
 parameter can be used to
@@ -3025,5 +11393,5 @@
 time is the beginning of
 &nbsp;the simulation, i.e. output takes place at times t = <span style="font-weight: bold;">skip_time_dosp</span> + <b>dt_dosp</b>,
-<span style="font-weight: bold;">skip_time_dosp</span>
+      <span style="font-weight: bold;">skip_time_dosp</span>
 + 2*<b>dt_dosp</b>, skip_time_dosp + 3*<b>dt_dosp</b>,
 etc. The actual output times can
@@ -3032,41 +11400,194 @@
 spectral data are output
 after each time step (if this is requested it should be <b>dt_dosp</b>
-= <i>0</i>).</font></span> </p> </td>
-</tr> <tr> <td style="vertical-align: top;"><p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p>
-</td> <td style="vertical-align: top;">I(10)</td>
-<td style="vertical-align: top;"><i>no level</i></td>
-<td style="vertical-align: top;"> <p>Vertical
+= <i>0</i>).</font></span> </p>
+
+
+ </td>
+
+
+
+    </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;">
+      
+      
+      <p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">I(10)</td>
+
+
+
+      <td style="vertical-align: top;"><i>no level</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Vertical
 level(s) for which horizontal spectra are to be
-plotted (in gridpoints).&nbsp; </p> <p>This parameter
+plotted (in gridpoints).&nbsp; </p>
+
+
+ 
+      
+      
+      <p>This parameter
 only affects the display of spectra in plots
 created with <span style="font-weight: bold;">profil</span>.
 The
 spectral data created and output to file are exclusively determined via
-<font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p>
-</td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td>
-<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
-</td> <td style="vertical-align: top;">No output of
-spectra data before this interval has passed (in s).<br><br>This
+      <font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ <tr>
+
+
+ <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td>
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+ </td>
+
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span>
+      </td>
+
+
+ <td style="vertical-align: top;">No output of
+spectra data before this interval has passed (in s).<br>
+
+
+      <br>
+
+
+This
 parameter causes that data output activities are starting not before
 this interval
-(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
+(counting from the beginning of the simulation, t=0) has passed. <br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">Example:</span><br>
+
+
+If
 the user has set <a href="#dt_dosp">dt_dosp</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dosp</span> = <span style="font-style: italic;">1800.0</span>, then the
-first output will be done at t = 5400 s. </td> </tr>
-<tr> <td style="vertical-align: top;"> <p><a name="spectra_direction"></a><b>spectra_direction</b></p>
-</td> <td style="vertical-align: top;">C*2 (10)</td>
-<td style="vertical-align: top;"><i>10 * ' '</i></td>
-<td style="vertical-align: top;"> <p>Direction(s)
-along which spectra are to be calculated.&nbsp; </p> <p>Allowed
+first output will be done at t = 5400 s. </td>
+
+
+ </tr>
+
+
+
+    <tr>
+
+
+ <td style="vertical-align: top;"> 
+      
+      
+      <p><a name="spectra_direction"></a><b>spectra_direction</b></p>
+
+
+
+      </td>
+
+
+ <td style="vertical-align: top;">C*2 (10)</td>
+
+
+
+      <td style="vertical-align: top;"><i>10 * ' '</i></td>
+
+
+
+      <td style="vertical-align: top;"> 
+      
+      
+      <p>Direction(s)
+along which spectra are to be calculated.&nbsp; </p>
+
+
+ 
+      
+      
+      <p>Allowed
 values are <span style="font-style: italic;">'x'</span>,
-<span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For
+      <span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For
 every quantity given by <a href="#data_output_sp">data_output_sp</a>
 a corresponding
 direction<span style="font-weight: bold;"> </span>must
-be assigned.<br> </p> <p>Calculation of spectra
+be assigned.<br>
+
+
+ </p>
+
+
+ 
+      
+      
+      <p>Calculation of spectra
 requires cyclic boundary conditions
 along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
 and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</p>
-</td> </tr> </tbody></table><span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
-</span></span></span><h3 style="line-height: 100%;"><br><a href="chapter_4.1.html"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></a><a href="index.html"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></a><a href="chapter_4.3.html"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></a></h3><span style="font-style: italic;">Last change:</span>
+
+
+
+      </td>
+
+
+ </tr>
+
+
+ 
+  
+  
+  </tbody>
+</table>
+
+
+<span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
+
+
+
+</span></span></span>
+<h3 style="line-height: 100%;"><br>
+
+
+<a href="chapter_4.1.html"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></a><a href="index.html"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></a><a href="chapter_4.3.html"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></a></h3>
+
+
+<span style="font-style: italic;">Last change:</span>
 $Id$ <span style="font-weight: bold;"><span style="font-weight: bold;"><br>
-</span></span><br></body></html>
+
+
+
+</span></span><br>
+
+
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.6.html	(revision 103)
+++ palm/trunk/DOC/app/chapter_4.6.html	(revision 108)
@@ -1,564 +1,2935 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><head>
-<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 4.6</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Marcus Oliver Letzel"> <meta name="CREATED" content="20041103;9554421"> <meta name="CHANGED" content="20041117;12591937"> <meta name="KEYWORDS" content="parallel LES model"> <style>
+<html>
+<head>
+
+
+  
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+
+  
+ 
+  
+  <title>PALM chapter 4.6</title>
+  <meta name="GENERATOR" content="StarOffice 7 (Win32)">
+
+ 
+  
+  <meta name="AUTHOR" content="Marcus Oliver Letzel">
+
+ 
+  
+  <meta name="CREATED" content="20041103;9554421">
+
+ 
+  
+  <meta name="CHANGED" content="20041117;12591937">
+
+ 
+  
+  <meta name="KEYWORDS" content="parallel LES model">
+
+ 
+  
+  <style>
 <!--
 @page { size: 21cm 29.7cm }
 -->
-</style></head>
-<body style="direction: ltr;" lang="en-US"><h3>4.6
+  </style>
+</head>
+
+
+<body style="direction: ltr;" lang="en-US">
+
+<h3>4.6
 Listing of the steering parameters in alphabetical order<br>
-</h3><p style="margin-bottom: 0cm;">Initialization
+
+
+</h3>
+
+<p style="margin-bottom: 0cm;">Initialization
 parameters
 (class = I),
 run parameters (R), package parameters (P) as well as user-defined
 parameters (U) are alphabetically listed in the following table. <br>
+
+
 &nbsp;
-</p><p style="margin-bottom: 0cm;" align="center"><br>
-</p><table style="width: 100%;" border="1" cellpadding="2" cellspacing="4"> <col width="38*">
-<col width="12*"> <col width="18*"> <col width="42*"> <col width="146*"> <tbody>
-<tr> <td style="vertical-align: middle;" width="15%">
-<h3><b>Parameter name</b></h3> </td> <td style="vertical-align: middle;" width="5%"> <h3>Class</h3>
-</td> <td style="vertical-align: middle;" width="7%">
-<h3>Type</h3> </td> <td style="vertical-align: middle;" width="16%"> <h3>Default<br>
-value</h3> </td> <td style="vertical-align: middle;" width="57%"> <h3>Explanation</h3> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#adjust_mixing_length"><b>adjust_mixing_length</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Near-surface
+</p>
+
+<p style="margin-bottom: 0cm;" align="center"><br>
+
+
+</p>
+
+<table style="width: 100%;" border="1" cellpadding="2" cellspacing="4">
+
+ <col width="38*">
+  <col width="12*"> <col width="18*"> <col width="42*"> <col width="146*"> <tbody>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <h3><b>Parameter name</b></h3>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="5%"> 
+      
+      <h3>Class</h3>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="7%">
+      
+      <h3>Type</h3>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <h3>Default<br>
+
+
+value</h3>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <h3>Explanation</h3>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#adjust_mixing_length"><b>adjust_mixing_length</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Near-surface
 adjustment of the
-mixing length to the Prandtl-layer law.</p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#alpha_surface"><b>alpha_surface</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Inclination
+mixing length to the Prandtl-layer law.</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#alpha_surface"><b>alpha_surface</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Inclination
 of the model domain
-with respect to the horizontal (in degrees).</p> </td> </tr>
-<tr> <td><a href="chapter_4.2.html#averaging_interval"><span style="font-weight: bold;">averaging_interval</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">0.0</span></td> <td>Averaging
+with respect to the horizontal (in degrees).</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#averaging_interval"><span style="font-weight: bold;">averaging_interval</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">0.0</span></td>
+
+ <td>Averaging
 interval for all&nbsp;output of temporally averaged data (in s).</td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#averaging_interval_pr"><b>averaging_interval_pr</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
-interval</a></span></td> <td style="width: 57%; text-align: left; vertical-align: middle;">
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#averaging_interval_pr"><b>averaging_interval_pr</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
+
+
+interval</a></span></td>
+
+ <td style="width: 57%; text-align: left; vertical-align: middle;">
 Averaging interval for vertical profiles&nbsp;output to local
 file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
-</font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
-(in s).&nbsp;</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#averaging_interval_sp"><b>averaging_interval_sp</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
-interval</a></span></td> <td style="vertical-align: middle;" width="57%">Averaging
+      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
+(in s).&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#averaging_interval_sp"><b>averaging_interval_sp</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
+
+
+interval</a></span></td>
+
+ <td style="vertical-align: middle;" width="57%">Averaging
 interval for spectra output to local
 file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
-</font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
+      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
 / &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
-(in s).&nbsp;</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_e_b"><b>bc_e_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'neumann'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom boundary condition of the
-TKE. <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#bc_lr"><b>bc_lr</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">C * 20<br> </td>
-<td style="vertical-align: middle;"><span style="font-style: italic;">&acute;cyclic&acute;</span><br>
-</td> <td style="vertical-align: middle;">Boundary
-condition along x (for all quantities).</td> </tr> <tr>
-<td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#bc_ns"><b>bc_ns</b></a></b></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">C * 20</td> <td style="vertical-align: middle;"><span style="font-style: italic;">'cyclic'</span></td>
-<td style="vertical-align: middle;">Boundary
-condition along y (for all quantities).</td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_p_b"><b>bc_p_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'neumann'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom boundary condition of the
-perturbation pressure. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#bc_p_t"><b>bc_p_t</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'dirichlet'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Top boundary condition of the
-perturbation pressure. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_b"><b>bc_par_b</b></a></b></td>
-<td style="vertical-align: middle;">P<br> </td>
-<td style="vertical-align: middle;">C*15</td> <td style="vertical-align: middle;"><i>&acute;reflect&acute;</i></td>
-<td style="vertical-align: middle;"> <p>Bottom
-boundary condition for particle transport. </p> </td> </tr>
-<tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_lr"><b>bc_par_lr</b></a></b></td>
-<td style="vertical-align: middle;">P<br> </td>
-<td style="vertical-align: middle;">C*15</td> <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
-<td style="vertical-align: middle;">Lateral boundary
+(in s).&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_e_b"><b>bc_e_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'neumann'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom boundary condition of the
+TKE. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#bc_lr"><b>bc_lr</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">C * 20<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">&acute;cyclic&acute;</span><br>
+
+
+      </td>
+
+ <td style="vertical-align: middle;">Boundary
+condition along x (for all quantities).</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#bc_ns"><b>bc_ns</b></a></b></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">C * 20</td>
+
+ <td style="vertical-align: middle;"><span style="font-style: italic;">'cyclic'</span></td>
+
+
+      <td style="vertical-align: middle;">Boundary
+condition along y (for all quantities).</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_p_b"><b>bc_p_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'neumann'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom boundary condition of the
+perturbation pressure. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#bc_p_t"><b>bc_p_t</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'dirichlet'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Top boundary condition of the
+perturbation pressure. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_b"><b>bc_par_b</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+ <td style="vertical-align: middle;"><i>&acute;reflect&acute;</i></td>
+
+
+      <td style="vertical-align: middle;"> 
+      
+      <p>Bottom
+boundary condition for particle transport. </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_lr"><b>bc_par_lr</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+ <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
+
+
+      <td style="vertical-align: middle;">Lateral boundary
 condition
 (x-direction) for particle
-transport.</td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_ns"><b>bc_par_ns</b></a></b></td>
-<td style="vertical-align: middle;">P<br> </td>
-<td style="vertical-align: middle;">C*15</td> <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
-<td style="vertical-align: middle;">Lateral boundary
+transport.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_ns"><b>bc_par_ns</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+ <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
+
+
+      <td style="vertical-align: middle;">Lateral boundary
 condition
 (y-direction) for particle
-transport.</td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_t"><b>bc_par_t</b></a></b></td>
-<td style="vertical-align: middle;">P<br> </td>
-<td style="vertical-align: middle;">C*15</td> <td style="vertical-align: middle;"><i>&acute;absorb&acute;</i></td>
-<td style="vertical-align: middle;">Top boundary
+transport.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_t"><b>bc_par_t</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+ <td style="vertical-align: middle;"><i>&acute;absorb&acute;</i></td>
+
+
+      <td style="vertical-align: middle;">Top boundary
 condition for
-particle transport.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_pt_b"><b>bc_pt_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'dirichlet'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom boundary condition of the
-potential temperature. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#pc_pt_t"><b>bc_pt_t</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'initial_gradient'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Top boundary condition of the
-potential temperature. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#bc_q_b"><b>bc_q_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'dirichlet'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom boundary condition of the
-specific humidity / total water content. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_q_t"><b>bc_q_t</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'neumann'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Top boundary condition of the
-specific humidity / total water content. <br> </p> </td>
-</tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_s_b"><b>bc_s_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'dirichlet'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom boundary condition of the
-scalar concentration. <br> </p> </td> </tr>
-<tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_s_t"><b>bc_s_t</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>&acute;neumann&acute;</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Top boundary condition of the
-scalar concentration. <br> </p> </td> </tr>
-<tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#bc_sa_t"><span style="font-weight: bold;">bc_sa_t</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">C * 20</td><td align="undefined" valign="undefined"><span style="font-style: italic;">'neumann'</span></td><td align="undefined" valign="undefined">Top boundary condition of the salinity.&nbsp;</td></tr><tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#bc_uv_b"><b>bc_uv_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'dirichlet'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom boundary condition of the horizontal wind
+particle transport.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_pt_b"><b>bc_pt_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'dirichlet'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom boundary condition of the
+potential temperature. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#pc_pt_t"><b>bc_pt_t</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'initial_gradient'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Top boundary condition of the
+potential temperature. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#bc_q_b"><b>bc_q_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'dirichlet'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom boundary condition of the
+specific humidity / total water content. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_q_t"><b>bc_q_t</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'neumann'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Top boundary condition of the
+specific humidity / total water content. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_s_b"><b>bc_s_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'dirichlet'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom boundary condition of the
+scalar concentration. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_s_t"><b>bc_s_t</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>&acute;neumann&acute;</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Top boundary condition of the
+scalar concentration. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#bc_sa_t"><span style="font-weight: bold;">bc_sa_t</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">C * 20</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">'neumann'</span></td>
+
+      <td align="undefined" valign="undefined">Top boundary condition of the salinity.&nbsp;</td>
+
+    </tr>
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#bc_uv_b"><b>bc_uv_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'dirichlet'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom boundary condition of the horizontal wind
 components u
-and v.</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#bc_uv_t"><b>bc_uv_t</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'dirichlet'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Top boundary condition of the
-horizontal velocity components u and v.</p> </td> </tr>
-<tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#bottom_salinityflux"><span style="font-weight: bold;">bottom_salinityflux</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.0</span></td><td align="undefined" valign="undefined">Kinematic salinity flux near the surface (in psu m/s).</td></tr><tr> <td style="font-weight: bold;"><a href="chapter_4.1.html#building_height">building_height</a></td>
-<td>I</td> <td>R</td> <td style="font-style: italic;">50.0</td> <td>Height
-of a single building in m.</td> </tr> <tr> <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_x">building_length_x</a></td>
-<td>I</td> <td>R</td> <td style="font-style: italic;">50.0</td> <td>Width
-of a single building in m.</td> </tr> <tr> <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_y">building_length_y</a></td>
-<td>I</td> <td>R</td> <td style="font-style: italic;">50.0</td> <td>Depth
-of a single building in m.</td> </tr> <tr> <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_left">building_wall_left</a></td>
-<td style="vertical-align: middle;">I</td> <td style="vertical-align: middle;">R</td> <td style="font-style: italic;"><span style="font-style: italic;">building centered in x-direction</span></td>
-<td style="vertical-align: middle;">x-coordinate of the
-left building wall in m.</td> </tr> <tr> <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_south">building_wall_south</a></td>
-<td style="vertical-align: middle;">I</td> <td style="vertical-align: middle;">R</td> <td style="font-style: italic;"><span style="font-style: italic;">building centered in y-direction</span></td>
-<td style="vertical-align: middle;">y-coordinate of the
-South building wall&nbsp;in m.</td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#call_psolver_at_all_substeps"><b>call_psolver_at_all_substeps</b></a></b></td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;">L<br> </td>
-<td style="vertical-align: middle;"><span style="font-style: italic;">.T..</span><br> </td>
-<td style="vertical-align: middle;">Switch
-to steer the call of the pressure solver.</td> </tr> <tr>
-<td><b><a href="chapter_4.2.html#fcl_factor"><b>cfl_factor</b></a></b></td>
-<td>R</td> <td>R</td> <td><i>0.1,
-0.8&nbsp;or 0.9 </i>(see parameter description)</td> <td>Time
-step limiting factor.</td> </tr> <tr> <td style="vertical-align: top;"><a href="chapter_4.1.html#cloud_droplets"><span style="font-weight: bold;">cloud_droplets</span></a><br>
-</td> <td style="vertical-align: top;">I<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.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#cloud_physics"><b>cloud_physics</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
-to switch on the condensation scheme. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#comp_spectra_level"><b>comp_spectra_level</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>no level</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Vertical level for which horizontal spectra are to be
-calculated and output (gridpoints).</p> </td> </tr>
-<tr> <td><a href="chapter_4.1.html#conserve_volume_flow"><span style="font-weight: bold;">conserve_volume_flow</span></a></td>
-<td>I</td> <td>L</td> <td><span style="font-style: italic;">.F.</span></td> <td>Conservation
-of volume flow in x- and y-direction.</td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#create_disturbances"><b>create_disturbances</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.T.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Switch
+and v.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#bc_uv_t"><b>bc_uv_t</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'dirichlet'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Top boundary condition of the
+horizontal velocity components u and v.</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#bottom_salinityflux"><span style="font-weight: bold;">bottom_salinityflux</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">0.0</span></td>
+
+      <td align="undefined" valign="undefined">Kinematic salinity flux near the surface (in psu m/s).</td>
+
+    </tr>
+
+    <tr>
+
+ <td style="font-weight: bold;"><a href="chapter_4.1.html#building_height">building_height</a></td>
+
+
+      <td>I</td>
+
+ <td>R</td>
+
+ <td style="font-style: italic;">50.0</td>
+
+ <td>Height
+of a single building in m.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_x">building_length_x</a></td>
+
+
+      <td>I</td>
+
+ <td>R</td>
+
+ <td style="font-style: italic;">50.0</td>
+
+ <td>Width
+of a single building in m.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_y">building_length_y</a></td>
+
+
+      <td>I</td>
+
+ <td>R</td>
+
+ <td style="font-style: italic;">50.0</td>
+
+ <td>Depth
+of a single building in m.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_left">building_wall_left</a></td>
+
+
+      <td style="vertical-align: middle;">I</td>
+
+ <td style="vertical-align: middle;">R</td>
+
+ <td style="font-style: italic;"><span style="font-style: italic;">building centered in x-direction</span></td>
+
+
+      <td style="vertical-align: middle;">x-coordinate of the
+left building wall in m.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_south">building_wall_south</a></td>
+
+
+      <td style="vertical-align: middle;">I</td>
+
+ <td style="vertical-align: middle;">R</td>
+
+ <td style="font-style: italic;"><span style="font-style: italic;">building centered in y-direction</span></td>
+
+
+      <td style="vertical-align: middle;">y-coordinate of the
+South building wall&nbsp;in m.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#call_psolver_at_all_substeps"><b>call_psolver_at_all_substeps</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">L<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">.T..</span><br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">Switch
+to steer the call of the pressure solver.</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td><b><a href="chapter_4.2.html#fcl_factor"><b>cfl_factor</b></a></b></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><i>0.1,
+0.8&nbsp;or 0.9 </i>(see parameter description)</td>
+
+ <td>Time
+step limiting factor.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: top;"><a href="chapter_4.1.html#cloud_droplets"><span style="font-weight: bold;">cloud_droplets</span></a><br>
+
+
+      </td>
+
+ <td style="vertical-align: top;">I<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.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#cloud_physics"><b>cloud_physics</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
+to switch on the condensation scheme. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#comp_spectra_level"><b>comp_spectra_level</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>no level</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Vertical level for which horizontal spectra are to be
+calculated and output (gridpoints).</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.1.html#conserve_volume_flow"><span style="font-weight: bold;">conserve_volume_flow</span></a></td>
+
+
+      <td>I</td>
+
+ <td>L</td>
+
+ <td><span style="font-style: italic;">.F.</span></td>
+
+ <td>Conservation
+of volume flow in x- and y-direction.</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#create_disturbances"><b>create_disturbances</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.T.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Switch
 to impose random perturbations to the horizontal
-velocity field. <br> </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#cross_normalized_x"><b>cross_normalized_x</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 10 (100)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>100
-* ' '</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Type
+velocity field. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#cross_normalized_x"><b>cross_normalized_x</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 10 (100)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>100
+* ' '</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Type
 of normalization applied to the x-coordinate of
 vertical
 profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#cross_normalized_y"><b>cross_normalized_y</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#cross_normalized_y"><b>cross_normalized_y</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
 * 10&nbsp; <br>
-(100)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>100 * ' '</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Type of normalization applied to the y-coordinate of
+
+
+(100)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>100 * ' '</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Type of normalization applied to the y-coordinate of
 vertical
 profiles to be plotted with <span style="font-weight: bold;">profil</span>.
-<br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#cross_profiles"><b>cross_profiles</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 100 (100)</p> </td> <td style="vertical-align: middle;" width="16%"> <p>see
-parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Determines
+      <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#cross_profiles"><b>cross_profiles</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 100 (100)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p>see
+parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Determines
 which vertical profiles are to be presented
 in
 which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is
-used.&nbsp; <br> </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#cross_xtext"><b>cross_xtext</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
+used.&nbsp; <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#cross_xtext"><b>cross_xtext</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
 * 40&nbsp; <br>
-&nbsp;(100)</p> </td> <td style="vertical-align: middle;" width="16%"> <p>see
-parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>x-axis
+
+
+&nbsp;(100)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p>see
+parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>x-axis
 labels of vertical profile coordinate systems to
 be
 plotted with <span style="font-weight: bold;">profil</span>.
-<br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#cut_spline_overshoot"><b>cut_spline_overshoot</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.T.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Cut
+      <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#cut_spline_overshoot"><b>cut_spline_overshoot</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.T.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Cut
 off of so-called overshoots, which can occur with
-the upstream-spline-scheme.</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#cycle_mg"><b>cycle_mg</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 1</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'w'</i></p> </td>
-<td style="vertical-align: middle;" width="57%">Type
+the upstream-spline-scheme.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#cycle_mg"><b>cycle_mg</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 1</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'w'</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%">Type
 of cycle to
 be used with the multi-grid
-method.&nbsp;</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#damp_level_1d"><b>damp_level_1d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>zu(nz+1)</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Height
+method.&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#damp_level_1d"><b>damp_level_1d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>zu(nz+1)</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Height
 where the damping layer begins in the 1d-model
-(in m). <br> </p> </td> </tr> <tr> <td><a href="chapter_4.2.html#data_output"><span style="font-weight: bold;">data_output</span></a></td>
-<td>R</td> <td>C * 10 (100)</td> <td><span style="font-style: italic;">100 * &acute; &acute;</span></td>
-<td>Quantities for which 2d cross section and/or 3d volume data
-are to be output.</td> </tr> <tr> <td><a href="chapter_4.2.html#data_output_format"><span style="font-weight: bold;">data_output_format</span></a></td>
-<td>R</td> <td>C * 10 (10)</td> <td><span style="font-style: italic;">'netcdf'</span></td>
-<td>Format of output data.</td> </tr> <tr> <td><a href="chapter_4.2.html#data_output_pr"><span style="font-weight: bold;">data_output_pr</span></a></td>
-<td>R</td> <td>C * 10 (100)</td> <td><span style="font-style: italic;">100 * ' '</span></td>
-<td>Quantities for which vertical profiles (horizontally
+(in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#data_output"><span style="font-weight: bold;">data_output</span></a></td>
+
+
+      <td>R</td>
+
+ <td>C * 10 (100)</td>
+
+ <td><span style="font-style: italic;">100 * &acute; &acute;</span></td>
+
+
+      <td>Quantities for which 2d cross section and/or 3d volume data
+are to be output.</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#data_output_format"><span style="font-weight: bold;">data_output_format</span></a></td>
+
+
+      <td>R</td>
+
+ <td>C * 10 (10)</td>
+
+ <td><span style="font-style: italic;">'netcdf'</span></td>
+
+
+      <td>Format of output data.</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#data_output_pr"><span style="font-weight: bold;">data_output_pr</span></a></td>
+
+
+      <td>R</td>
+
+ <td>C * 10 (100)</td>
+
+ <td><span style="font-style: italic;">100 * ' '</span></td>
+
+
+      <td>Quantities for which vertical profiles (horizontally
 averaged)
-are to be output.</td> </tr> <tr><td><a href="chapter_4.3.html#data_output_pr_user"><span style="font-weight: bold;">data_output_pr_user</span></a></td><td>U</td><td>C * 10<br>(200)</td><td><span style="font-style: italic;">200 * ' '</span></td><td>User defined quantities for which horizontally averaged profile data is to be output.</td></tr><tr> <td><a href="chapter_4.2.html#data_output_sp"><span style="font-weight: bold;">data_output_sp</span></a></td>
-<td>P</td> <td>C * 10 (10)</td> <td><span style="font-style: italic;">10 * ' '</span></td>
-<td>Quantities for which horizontal spectra are to be calculated
-and output.</td> </tr> <tr> <td><a href="chapter_4.3.html#data_output_user"><span style="font-weight: bold;">data_output_user</span></a></td>
-<td>U</td> <td>C * 10 (100)</td> <td><span style="font-style: italic;">100 * ' '</span></td>
-<td>User defined quantities for which 2d cross section and/or 3d
-volume data are to be output.</td> </tr> <tr> <td><a href="chapter_4.2.html#data_output_2d_on_each_pe"><span style="font-weight: bold;">data_output_2d_on_each_pe</span></a></td>
-<td>R</td> <td>L</td> <td><span style="font-style: italic;">.T.</span></td> <td>Output
+are to be output.</td>
+
+ </tr>
+
+ <tr>
+
+      <td><a href="chapter_4.3.html#data_output_pr_user"><span style="font-weight: bold;">data_output_pr_user</span></a></td>
+
+      <td>U</td>
+
+      <td>C * 10<br>
+
+(200)</td>
+
+      <td><span style="font-style: italic;">200 * ' '</span></td>
+
+      <td>User defined quantities for which horizontally averaged profile data is to be output.</td>
+
+    </tr>
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#data_output_sp"><span style="font-weight: bold;">data_output_sp</span></a></td>
+
+
+      <td>P</td>
+
+ <td>C * 10 (10)</td>
+
+ <td><span style="font-style: italic;">10 * ' '</span></td>
+
+
+      <td>Quantities for which horizontal spectra are to be calculated
+and output.</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.3.html#data_output_user"><span style="font-weight: bold;">data_output_user</span></a></td>
+
+
+      <td>U</td>
+
+ <td>C * 10 (100)</td>
+
+ <td><span style="font-style: italic;">100 * ' '</span></td>
+
+
+      <td>User defined quantities for which 2d cross section and/or 3d
+volume data are to be output.</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#data_output_2d_on_each_pe"><span style="font-weight: bold;">data_output_2d_on_each_pe</span></a></td>
+
+
+      <td>R</td>
+
+ <td>L</td>
+
+ <td><span style="font-style: italic;">.T.</span></td>
+
+ <td>Output
 2d cross section data by one or
-all processors.&nbsp;</td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#density_ratio"><b>density_ratio</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>0.0, 9</i> * <i>9999999.9</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Ratio of the density of the fluid and the density of the
-particles.</p> </td> </tr> <tr> <td><a href="chapter_4.1.html#dissipation_1d"><span style="font-weight: bold;">dissipation_1d</span></a></td>
-<td>I</td> <td>C * 20</td> <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
-<td>Calculation method for the energy dissipation term in the TKE
-equation of the 1d-model.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#disturbance_amplitude"><b>disturbance</b></a>&nbsp;&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#disturbance_amplitude">&nbsp;<b>_amplitude</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.25</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Maximum
+all processors.&nbsp;</td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#density_ratio"><b>density_ratio</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>0.0, 9</i> * <i>9999999.9</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Ratio of the density of the fluid and the density of the
+particles.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#dissipation_1d"><span style="font-weight: bold;">dissipation_1d</span></a></td>
+
+
+      <td>I</td>
+
+ <td>C * 20</td>
+
+ <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
+
+
+      <td>Calculation method for the energy dissipation term in the TKE
+equation of the 1d-model.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#disturbance_amplitude"><b>disturbance</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#disturbance_amplitude">&nbsp;<b>_amplitude</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.25</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Maximum
 perturbation amplitude of the random
 perturbations
-imposed to the horizontal velocity field (in m/s). <br> </p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#disturbance_energy_limit"><b>disturbance_energy</b></a>&nbsp;&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#disturbance_energy_limit">&nbsp;<b>_limit</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.01</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB">Upper limit value of the
+imposed to the horizontal velocity field (in m/s). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#disturbance_energy_limit"><b>disturbance_energy</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#disturbance_energy_limit">&nbsp;<b>_limit</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.01</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB">Upper limit value of the
 perturbation energy of
 the velocity field used as a criterion for imposing random
 perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;</p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#disturbance_level_b"><b>disturbance_level_b</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>zu(3) or zu(nz*2/3)</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#disturbance_level_b"><b>disturbance_level_b</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>zu(3) or zu(nz*2/3)</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
 limit of the vertical range for which random perturbations are to be
 imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
-</font></font> </p> <span lang="en-GB"></span></td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#disturbance_level_t"><b>disturbance_level_t</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>zu(nz/3) or zu(nzt-3)</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
+      </font></font> </p>
+
+ <span lang="en-GB"></span></td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#disturbance_level_t"><b>disturbance_level_t</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>zu(nz/3) or zu(nzt-3)</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
 limit of the vertical range for which random perturbations are to be
 imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m). <br>
-</font></font></p> </td> </tr> <tr>
-<td><a href="chapter_4.2.html#do2d_at_begin"><span style="font-weight: bold;">do2d_at_begin</span></a></td>
-<td>R</td> <td>L</td> <td><span style="font-style: italic;">.F.</span></td> <td>Output
+
+
+      </font></font></p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td><a href="chapter_4.2.html#do2d_at_begin"><span style="font-weight: bold;">do2d_at_begin</span></a></td>
+
+
+      <td>R</td>
+
+ <td>L</td>
+
+ <td><span style="font-style: italic;">.F.</span></td>
+
+ <td>Output
 2d cross section data by one or
-all processors.&nbsp;</td> </tr> <tr> <td><a href="chapter_4.2.html#do3d_at_begin"><span style="font-weight: bold;">do3d_at_begin</span></a></td>
-<td>R</td> <td>L</td> <td><span style="font-style: italic;">.F.</span></td> <td>Output
+all processors.&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#do3d_at_begin"><span style="font-weight: bold;">do3d_at_begin</span></a></td>
+
+
+      <td>R</td>
+
+ <td>L</td>
+
+ <td><span style="font-style: italic;">.F.</span></td>
+
+ <td>Output
 of 3d volume data at the beginning
-of a run.</td> </tr> <tr> <td><a href="chapter_4.2.html#do3d_compress"><span style="font-weight: bold;">do3d_compress</span></a></td>
-<td>R</td> <td>L</td> <td><span style="font-style: italic;">.F.</span></td> <td>Output
-of data for 3d plots in compressed form.&nbsp;</td> </tr>
-<tr> <td><a href="chapter_4.2.html#do3d_precision"><span style="font-weight: bold;">do3d_precision</span></a></td>
-<td>R</td> <td>C * 7 (100)</td> <td>see
-parameter description</td> <td>Significant digits in case
-of compressed data output.&nbsp;</td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dt"><b>dt</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I/R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>variable</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p><font face="Thorndale, serif"><font size="3">Time
+of a run.</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#do3d_compress"><span style="font-weight: bold;">do3d_compress</span></a></td>
+
+
+      <td>R</td>
+
+ <td>L</td>
+
+ <td><span style="font-style: italic;">.F.</span></td>
+
+ <td>Output
+of data for 3d plots in compressed form.&nbsp;</td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#do3d_precision"><span style="font-weight: bold;">do3d_precision</span></a></td>
+
+
+      <td>R</td>
+
+ <td>C * 7 (100)</td>
+
+ <td>see
+parameter description</td>
+
+ <td>Significant digits in case
+of compressed data output.&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dt"><b>dt</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I/R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>variable</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p><font face="Thorndale, serif"><font size="3">Time
 step for the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s). <br>
-</font></font></p> </td> </tr> <tr>
-<td><a href="chapter_4.2.html#dt_averaging_input"><span style="font-weight: bold;">dt_averaging_input</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">0.0</span></td> <td>Temporal
+
+
+      </font></font></p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td><a href="chapter_4.2.html#dt_averaging_input"><span style="font-weight: bold;">dt_averaging_input</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">0.0</span></td>
+
+ <td>Temporal
 interval of&nbsp;data which are subject to temporal averaging (in
-s).</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_averaging_input_pr"><b>dt_averaging_input_pr</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#dt_averaging_input">dt_<br>
+s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_averaging_input_pr"><b>dt_averaging_input_pr</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#dt_averaging_input">dt_<br>
+
+
 averaging_<br>
-input</a></span></td> <td style="vertical-align: middle;" width="57%">Temporal
+
+
+input</a></span></td>
+
+ <td style="vertical-align: middle;" width="57%">Temporal
 interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
 profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;</font></font></td>
-</tr> <tr><td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.2.html#dt_coupling">dt_coupling</a></td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined">9999999.9</td><td align="undefined" valign="undefined">Temporal interval for the data exchange in case of runs with coupled models (e.g. atmosphere - ocean) (in s).</td></tr><tr> <td><a href="chapter_4.2.html#dt_data_output"><span style="font-weight: bold;">dt_data_output</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">9999999.9</span></td>
-<td> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
+
+
+    </tr>
+
+ <tr>
+
+      <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.2.html#dt_coupling">dt_coupling</a></td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined">9999999.9</td>
+
+      <td align="undefined" valign="undefined">Temporal interval for the data exchange in case of runs with coupled models (e.g. atmosphere - ocean) (in s).</td>
+
+    </tr>
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#dt_data_output"><span style="font-weight: bold;">dt_data_output</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">9999999.9</span></td>
+
+
+      <td> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
 at which&nbsp;data (3d volume data (instantaneous or time
 averaged),
 cross sections (instantaneous or time averaged), vertical profiles,
 spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-</td> </tr> <tr> <td><a href="chapter_4.2.html#dt_data_output_av"><span style="font-weight: bold;">dt_data_output_av</span></a></td>
-<td>R</td> <td>R</td> <td><i>value
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#dt_data_output_av"><span style="font-weight: bold;">dt_data_output_av</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+
+
+output</a></i></td>
+
+ <td> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font>
 at which time averaged 3d volume data and/or 2d cross section data
 shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_disturb"><b>dt_disturb</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>9999999.9</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_disturb"><b>dt_disturb</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>9999999.9</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
 which random
 perturbations are to be imposed on the horizontal velocity field
-(</font>in <font face="Thorndale">s). <br> </font></p>
-</td> </tr> <tr> <td><a href="chapter_4.2.html#dt_dopr"><span style="font-weight: bold;">dt_dopr</span></a></td>
-<td>R</td> <td>R</td> <td><i>value
+(</font>in <font face="Thorndale">s). <br>
+
+ </font></p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#dt_dopr"><span style="font-weight: bold;">dt_dopr</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td><span lang="en-GB"><font face="Thorndale">Temporal interval at
+
+
+output</a></i></td>
+
+ <td><span lang="en-GB"><font face="Thorndale">Temporal interval at
 which data&nbsp;of vertical profiles shall be output (to local
 file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
 or/and </font></span><a href="chapter_3.4.html#PLOT1D_DATA"><span lang="en-GB"><font face="Thorndale">PLOT1D_DATA</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
-<span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span></td>
-</tr> <tr> <td><a href="chapter_4.2.html#dt_dopr_listing"><span style="font-weight: bold;">dt_dopr_listing</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">9999999.9</span></td>
-<td> <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
+      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span></td>
+
+
+    </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#dt_dopr_listing"><span style="font-weight: bold;">dt_dopr_listing</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">9999999.9</span></td>
+
+
+      <td> 
+      
+      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
 interval</font> at which data <font face="Thorndale">of
 vertical
 profiles shall be output (output for printouts, local file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
-<span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
-</p> </td> </tr> <tr> <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_dopts"><span style="font-weight: bold;">dt_dopts</span></a></td>
-<td align="undefined" valign="undefined">P</td>
-<td align="undefined" valign="undefined">R</td>
-<td align="undefined" valign="undefined"><i>value
+      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_dopts"><span style="font-weight: bold;">dt_dopts</span></a></td>
+
+
+      <td align="undefined" valign="undefined">P</td>
+
+
+      <td align="undefined" valign="undefined">R</td>
+
+
+      <td align="undefined" valign="undefined"><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td align="undefined" valign="undefined"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+
+
+output</a></i></td>
+
+ <td align="undefined" valign="undefined"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which time series data of particle quantities
 shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_dosp"><b>dt_dosp</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><i>value
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_dosp"><b>dt_dosp</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td style="vertical-align: middle;" width="57%">Temporal
+
+
+output</a></i></td>
+
+ <td style="vertical-align: middle;" width="57%">Temporal
 interval at which&nbsp;spectra data shall be output
-(in s).&nbsp;</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_dots"><b>dt_dots</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>see parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which&nbsp;time series data shall be output (</font>in <font face="Thorndale">s). <br> </font></p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_do2d_xy"><b>dt_do2d_xy</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><i>value
+(in s).&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_dots"><b>dt_dots</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>see parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which&nbsp;time series data shall be output (</font>in <font face="Thorndale">s). <br>
+
+ </font></p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_do2d_xy"><b>dt_do2d_xy</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which horizontal cross section data shall be output (</font>in <font face="Thorndale">s). <br> </font></p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_do2d_xz"><b>dt_do2d_xz</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><i>value
+
+
+output</a></i></td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which horizontal cross section data shall be output (</font>in <font face="Thorndale">s). <br>
+
+ </font></p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_do2d_xz"><b>dt_do2d_xz</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+
+
+output</a></i></td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
 which vertical cross section data (xz) shall be output&nbsp;(</font>in
-<font face="Thorndale">s). <br> </font></p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_do2d_yz"><b>dt_do2d_yz</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><i>value
+      <font face="Thorndale">s). <br>
+
+ </font></p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_do2d_yz"><b>dt_do2d_yz</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+
+
+output</a></i></td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
 which vertical cross section data (yz)&nbsp;shall be
 output&nbsp;(</font>in s<font face="Thorndale">).</font></p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_do3d"><b>dt_do3d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><i>value
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_do3d"><b>dt_do3d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-output</a></i></td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which 3d volume data shall be output (</font>in <font face="Thorndale">s). <br> </font></p> </td>
-</tr> <tr> <td><b><a href="chapter_4.2.html#dt_dvrp"><b>dt_dvrp</b></a></b></td>
-<td>P</td> <td>R</td> <td><span style="font-style: italic;">9999999.9</span></td>
-<td>Temporal interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
-s). </td> </tr> <tr><td><a style="font-weight: bold;" href="chapter_4.2.html#dt_max">dt_max</a></td><td>R</td><td>R</td><td><span style="font-style: italic;">20.0</span></td><td>Maximum
-allowed value of the timestep (in s).</td></tr><tr> <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_min_part"><span style="font-weight: bold;">dt_min_part</span></a></td>
-<td align="undefined" valign="undefined">P</td>
-<td align="undefined" valign="undefined">R</td>
-<td align="undefined" valign="undefined"><span style="font-style: italic;">0.0002</span></td> <td align="undefined" valign="undefined">Minimum value
+
+
+output</a></i></td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which 3d volume data shall be output (</font>in <font face="Thorndale">s). <br>
+
+ </font></p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td><b><a href="chapter_4.2.html#dt_dvrp"><b>dt_dvrp</b></a></b></td>
+
+
+      <td>P</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">9999999.9</span></td>
+
+
+      <td>Temporal interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
+s). </td>
+
+ </tr>
+
+ <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.2.html#dt_max">dt_max</a></td>
+
+      <td>R</td>
+
+      <td>R</td>
+
+      <td><span style="font-style: italic;">20.0</span></td>
+
+      <td>Maximum
+allowed value of the timestep (in s).</td>
+
+    </tr>
+
+    <tr>
+
+ <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_min_part"><span style="font-weight: bold;">dt_min_part</span></a></td>
+
+
+      <td align="undefined" valign="undefined">P</td>
+
+
+      <td align="undefined" valign="undefined">R</td>
+
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">0.0002</span></td>
+
+ <td align="undefined" valign="undefined">Minimum value
 for the particle timestep when SGS velocities are used (in s).</td>
-</tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_prel"><b>dt_prel</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>9999999.9</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
+
+
+    </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_prel"><b>dt_prel</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>9999999.9</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
 interval at
 which particles are to be released <span lang="en-GB">from
 a particle
 source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;</font></p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dt_pr_1d"><b>dt_pr_1d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>9999999.9</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Temporal
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dt_pr_1d"><b>dt_pr_1d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>9999999.9</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Temporal
 interval of vertical profile output of the
 1D-model
-(in s).&nbsp;</p> </td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_restart"><b>dt_restart</b></a></b></td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;">9999999.9<br> </td>
-<td style="vertical-align: middle;"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+(in s).&nbsp;</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_restart"><b>dt_restart</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">9999999.9<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><font face="Thorndale"><font face="Thorndale, serif">Temporal
 interval</font> at which a new
-restart run is to be carried out (</font>in <font face="Thorndale">s).</font></td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dt_run_control"><b>dt_run_control</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>60.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+restart run is to be carried out (</font>in <font face="Thorndale">s).</font></td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dt_run_control"><b>dt_run_control</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>60.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
 which run control
 output is to be made (</font>in <font face="Thorndale">s).
-<br> </font></p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dt_run_control_1d"><b>dt_run_control_1d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>60.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Temporal
+      <br>
+
+ </font></p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dt_run_control_1d"><b>dt_run_control_1d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>60.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Temporal
 interval of runtime control output of the
 1d-model
-(in s).</p> </td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_write_particle_data"><b>dt_write_particle_data</b></a></b></td>
-<td style="vertical-align: middle;">P<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;"><i>9999999.9</i></td>
-<td style="vertical-align: middle;">Temporal
+(in s).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_write_particle_data"><b>dt_write_particle_data</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><i>9999999.9</i></td>
+
+
+      <td style="vertical-align: middle;">Temporal
 interval for output
-of particle data (in s).</td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_directory"><b>dvrp_directory</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 80</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'default'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Name of the directory into which data created by the <span style="font-weight: bold;">dvrp</span>
-software shall be saved. <br> </p> </td> </tr>
-<tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_file"><b>dvrp_file</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 80</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'default'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Name of the file into which data created by the <span style="font-weight: bold;">dvrp</span> software shall
-be output.</p> </td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_host"><b>dvrp_host</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 80</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'origin.rvs. <br>
-uni- hanover.de'</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Name
+of particle data (in s).</td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_directory"><b>dvrp_directory</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 80</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'default'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Name of the directory into which data created by the <span style="font-weight: bold;">dvrp</span>
+software shall be saved. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_file"><b>dvrp_file</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 80</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'default'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Name of the file into which data created by the <span style="font-weight: bold;">dvrp</span> software shall
+be output.</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_host"><b>dvrp_host</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 80</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'origin.rvs. <br>
+
+
+uni- hanover.de'</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Name
 of the computer to which data created by the <span style="font-weight: bold;">dvrp</span> software shall
 be
-transferred. <br> </p> </td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_output"><b>dvrp_output</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 10</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'rtsp'</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Output
+transferred. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_output"><b>dvrp_output</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 10</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'rtsp'</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Output
 mode for the <span style="font-weight: bold;">dvrp</span>
-software. </p> </td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_password"><b>dvrp_password</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 80</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'********'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">Password
+software. </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_password"><b>dvrp_password</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 80</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'********'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">Password
 for the
 computer to which data created
 by the <span style="font-weight: bold;">dvrp</span>
 software is to be
-transferred.</td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_psize"><b>dvrp_psize</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.2</i> * <i>dx</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Diameter
+transferred.</td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_psize"><b>dvrp_psize</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.2</i> * <i>dx</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Diameter
 that the particles is given in visualizations
 with
 the <span style="font-weight: bold;">dvrp</span>
 software (in
-m). <br> </p> </td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#dvrp_username"><b>dvrp_username</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 80</p> </td> <td style="vertical-align: middle;" width="16%"> <p>no default value </p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>User
+m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#dvrp_username"><b>dvrp_username</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 80</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p>no default value </p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>User
 name of a valid account on the computer to which
 data
@@ -566,951 +2937,5232 @@
 software
 is to be
-transferred. <br> </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dx"><b>dx</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Horizontal
-grid spacing along the x-direction (in m). <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dy"><b>dy</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Horizontal
-grid spacing along the y-direction (in m). <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dz"><b>dz</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>no default, see parameter description </p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Vertical
-grid spacing (in m).</p> </td> </tr> <tr> <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#dz_max">dz_max</a></td>
-<td align="undefined" valign="undefined">I</td>
-<td align="undefined" valign="undefined">R</td>
-<td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
-<td align="undefined" valign="undefined">Allowed
-maximum vertical grid spacing (in m).<br> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#dz_stretch_factor"><b>dz_stretch_factor</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.08</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Stretch
+transferred. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dx"><b>dx</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Horizontal
+grid spacing along the x-direction (in m). <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dy"><b>dy</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Horizontal
+grid spacing along the y-direction (in m). <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dz"><b>dz</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>no default, see parameter description </p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Vertical
+grid spacing (in m).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#dz_max">dz_max</a></td>
+
+
+      <td align="undefined" valign="undefined">I</td>
+
+
+      <td align="undefined" valign="undefined">R</td>
+
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
+
+
+      <td align="undefined" valign="undefined">Allowed
+maximum vertical grid spacing (in m).<br>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#dz_stretch_factor"><b>dz_stretch_factor</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.08</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Stretch
 factor for a vertically stretched grid (see <a href="chapter_4.1.html#dz_stretch_level">dz_stretch_level</a>).</p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#dz_stretch_level"><b>dz_stretch_level</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>100000.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Height
-level above which the grid is to be stretched
-vertically (in m). <br> </p> </td> </tr> <tr>
-<td><a href="chapter_4.1.html#e_min"><b>e_min</b></a></td>
-<td>I</td> <td>R</td> <td>0.0</td>
-<td>Minimum TKE in m<sup>2</sup>s<sup>-2</sup>.</td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#end_time"><b>end_time</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p lang="en-GB"><font face="Thorndale">Simulation
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#dz_stretch_level"><b>dz_stretch_level</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>100000.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Height
+level above/below which the grid is to be stretched
+vertically (in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+      <td><a href="chapter_4.1.html#e_init"><span style="font-weight: bold;">e_init</span></a></td>
+
+      <td>I</td>
+
+      <td>R</td>
+
+      <td style="font-style: italic;">0.0</td>
+
+      <td>Initial TKE in m<sup>2</sup>s<sup>-2</sup>.</td>
+
+    </tr>
+
+    <tr>
+
+
+      <td><a href="chapter_4.1.html#e_min"><b>e_min</b></a></td>
+
+
+      <td>I</td>
+
+ <td>R</td>
+
+ <td style="font-style: italic;">0.0</td>
+
+
+      <td>Minimum TKE in m<sup>2</sup>s<sup>-2</sup>.</td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#end_time"><b>end_time</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p lang="en-GB"><font face="Thorndale">Simulation
 time of the 3D
-model (</font>in <font face="Thorndale">s)</font><font face="Thorndale">.</font></p> </td> </tr>
-<tr> <td align="undefined" valign="undefined"><a href="chapter_4.2.html#end_time_prel"><span style="font-weight: bold;">end_time_prel</span></a></td>
-<td align="undefined" valign="undefined">P</td>
-<td align="undefined" valign="undefined">R</td>
-<td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
-<td align="undefined" valign="undefined">Time of
-the last release of particles (in s).</td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#end_time_1d"><b>end_time_1d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>864000.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Time
-to be simulated for the 1D-model (in s).&nbsp;</p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#fft_method"><b>fft_method</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'system specific'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>FFT-method to be used.</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#force_print_header"><b>force_print_header</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="width: 57%; vertical-align: middle;"> <p>Steering
+model (</font>in <font face="Thorndale">s)</font><font face="Thorndale">.</font></p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td align="undefined" valign="undefined"><a href="chapter_4.2.html#end_time_prel"><span style="font-weight: bold;">end_time_prel</span></a></td>
+
+
+      <td align="undefined" valign="undefined">P</td>
+
+
+      <td align="undefined" valign="undefined">R</td>
+
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
+
+
+      <td align="undefined" valign="undefined">Time of
+the last release of particles (in s).</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#end_time_1d"><b>end_time_1d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>864000.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Time
+to be simulated for the 1D-model (in s).&nbsp;</p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#fft_method"><b>fft_method</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'system specific'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>FFT-method to be used.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#force_print_header"><b>force_print_header</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="width: 57%; vertical-align: middle;"> 
+      
+      <p>Steering
 of header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. </p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#galilei_transformation"><b>galilei_transformation</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Application
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#galilei_transformation"><b>galilei_transformation</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Application
 of a Galilei-transformation to the
 coordinate
-system of the model.</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#grid_matching"><b>grid_matching</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 6</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'match'</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Variable
-to adjust the subdomain sizes in parallel runs.</p> </td> </tr>
-<tr><td><b><a href="chapter_4.1.html#humidity"><b>humidity</b></a></b></td><td>I</td><td>L</td><td><span style="font-style: italic;">.F.</span></td><td>Parameter
+system of the model.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#grid_matching"><b>grid_matching</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 6</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'match'</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Variable
+to adjust the subdomain sizes in parallel runs.</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+      <td><b><a href="chapter_4.1.html#humidity"><b>humidity</b></a></b></td>
+
+      <td>I</td>
+
+      <td>L</td>
+
+      <td><span style="font-style: italic;">.F.</span></td>
+
+      <td>Parameter
 to switch on the prognostic equation for
 specific
-humidity q.</td></tr><tr> <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#inflow_disturbance_begin"><b>inflow_disturbance_begin</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;"><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: middle;">Lower
+humidity q.</td>
+
+    </tr>
+
+    <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#inflow_disturbance_begin"><b>inflow_disturbance_begin</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><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: middle;">Lower
 limit of the horizontal range for which random perturbations are to be
-imposed on the horizontal velocity field (gridpoints).</td> </tr>
-<tr> <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#inflow_disturbance_end"><b>inflow_disturbance_end</b></a></b></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;"><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: middle;">Upper
+imposed on the horizontal velocity field (gridpoints).</td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#inflow_disturbance_end"><b>inflow_disturbance_end</b></a></b></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><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: middle;">Upper
 limit of the horizontal range for which random perturbations are
 to be imposed on the horizontal velocity field (gridpoints).</td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#initializing_actions"><b>initializing_actions</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 100</p> </td> <td style="vertical-align: middle;" width="16%"> <p>no default, see parameter description</p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p style="font-style: normal;">Initialization
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#initializing_actions"><b>initializing_actions</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 100</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p>no default, see parameter description</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p style="font-style: normal;">Initialization
 actions
-to be carried out. <br> </p> </td> </tr> <tr>
-<td style="vertical-align: top;"><a href="chapter_4.2.html#initial_weighting_factor"><span style="font-weight: bold;">initial_weighting_factor</span></a><br>
-</td> <td style="vertical-align: top;">P<br> </td>
-<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br> </td>
-<td style="vertical-align: top;">Factor to define
-the real number of initial droplets in a grid cell.</td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#km_constant"><b>km_constant</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>variable (computed from TKE)</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Constant
+to be carried out. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: top;"><a href="chapter_4.2.html#initial_weighting_factor"><span style="font-weight: bold;">initial_weighting_factor</span></a><br>
+
+
+      </td>
+
+ <td style="vertical-align: top;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: top;">R<br>
+
+ </td>
+
+ <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br>
+
+ </td>
+
+
+      <td style="vertical-align: top;">Factor to define
+the real number of initial droplets in a grid cell.</td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#km_constant"><b>km_constant</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>variable (computed from TKE)</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Constant
 eddy diffusivities are used (laminar
-simulations).&nbsp;</p> </td> </tr> <tr>
-<td style="vertical-align: middle;"><b><a href="chapter_4.1.html#km_damp_max"><b>km_damp_max</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;"><span style="font-style: italic;">0.5*(dx
-or dy)</span></td> <td style="vertical-align: middle;">Maximum
+simulations).&nbsp;</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#km_damp_max"><b>km_damp_max</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">0.5*(dx
+or dy)</span></td>
+
+ <td style="vertical-align: middle;">Maximum
 diffusivity used for filtering the velocity field in the vicinity of
-the outflow (in m<sup>2</sup>/s).</td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#long_filter_factor"><b>long_filter_factor</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Filter
-factor for the so-called Long-filter.</p> </td> </tr>
-<tr><td><a style="font-weight: bold;" href="chapter_4.1.html#loop_optimization">loop_optimization</a></td><td>I</td><td>C * 16</td><td>see parameter description</td><td>Method used to optimize loops for solving the prognostic equations .</td></tr><tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.2.html#maximum_number_of_particles"><b>maximum_number_</b></a>
-<br> <a href="chapter_4.2.html#maximum_number_of_particles"><b>of_particles</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1000</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Maximum
-number of particles (on a PE). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>maximum_number_</b></a>
-<br> <a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>of_tailpoints</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>100</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Maximum
+the outflow (in m<sup>2</sup>/s).</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#long_filter_factor"><b>long_filter_factor</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Filter
+factor for the so-called Long-filter.</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.1.html#loop_optimization">loop_optimization</a></td>
+
+      <td>I</td>
+
+      <td>C * 16</td>
+
+      <td>see parameter description</td>
+
+      <td>Method used to optimize loops for solving the prognostic equations .</td>
+
+    </tr>
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.2.html#maximum_number_of_particles"><b>maximum_number_</b></a>
+      <br>
+
+ <a href="chapter_4.2.html#maximum_number_of_particles"><b>of_particles</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1000</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Maximum
+number of particles (on a PE). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>maximum_number_</b></a>
+      <br>
+
+ <a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>of_tailpoints</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>100</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Maximum
 number of tailpoints that a particle tail can
-have. <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#maximum_tailpoint_age"><b>maximum_tailpoint_</b></a>
-<br> <a href="chapter_4.2.html#maximum_tailpoint_age"><b>age</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>100000.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Maximum
+have. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#maximum_tailpoint_age"><b>maximum_tailpoint_</b></a>
+      <br>
+
+ <a href="chapter_4.2.html#maximum_tailpoint_age"><b>age</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>100000.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Maximum
 age that the end point of a particle tail is allowed to have (in s). <br>
-</p> </td> </tr> <tr> <td><b><a href="chapter_4.2.html#mg_cycles"><b>mg_cycles</b></a></b></td>
-<td>R</td> <td>I</td> <td><i>- 1</i></td>
-<td>Number of cycles to be used with the multi-grid scheme.</td>
-</tr> <tr> <td><b><b><a href="chapter_4.2.html#mg_switch_to_pe0_level"><b>mg_switch_to_pe0_level</b></a></b></b></td>
-<td>R</td> <td>I</td> <td>see parameter
-description</td> <td>Grid
-level at which data shall be gathered on PE0.</td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#minimum_tailpoint_distance"><b>minimum_tailpoint_</b></a>
-<br> <a href="chapter_4.2.html#minimum_tailpoint_distance"><b>distance</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Minimum
+
+
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><b><a href="chapter_4.2.html#mg_cycles"><b>mg_cycles</b></a></b></td>
+
+
+      <td>R</td>
+
+ <td>I</td>
+
+ <td><i>- 1</i></td>
+
+
+      <td>Number of cycles to be used with the multi-grid scheme.</td>
+
+
+    </tr>
+
+ <tr>
+
+ <td><b><b><a href="chapter_4.2.html#mg_switch_to_pe0_level"><b>mg_switch_to_pe0_level</b></a></b></b></td>
+
+
+      <td>R</td>
+
+ <td>I</td>
+
+ <td>see parameter
+description</td>
+
+ <td>Grid
+level at which data shall be gathered on PE0.</td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#minimum_tailpoint_distance"><b>minimum_tailpoint_</b></a>
+      <br>
+
+ <a href="chapter_4.2.html#minimum_tailpoint_distance"><b>distance</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Minimum
 distance allowed between two adjacent points of
 a
-particle tail (in m). <br> </p> </td> </tr>
-<tr> <td><a href="chapter_4.1.html#mixing_length_1d"><span style="font-weight: bold;">mixing_length_1d</span></a></td>
-<td>I</td> <td>C * 20</td> <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
-<td>Mixing length used in the 1d-model.</td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#mode_dvrp"><b>mode_dvrp</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20 (10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * ' '</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Graphical objects (isosurfaces, slicers, particles)
+particle tail (in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.1.html#mixing_length_1d"><span style="font-weight: bold;">mixing_length_1d</span></a></td>
+
+
+      <td>I</td>
+
+ <td>C * 20</td>
+
+ <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
+
+
+      <td>Mixing length used in the 1d-model.</td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#mode_dvrp"><b>mode_dvrp</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20 (10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * ' '</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Graphical objects (isosurfaces, slicers, particles)
 which are
 to be created by the <span style="font-weight: bold;">dvrp</span>
-software. <br> </p> </td> </tr>  <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#momentum_advec"><b>momentum_advec</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 10</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'pw-scheme</i>'</p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Advection scheme to be used for the momentum equations.</p>
-</td> </tr> <tr> <td><a href="chapter_4.1.html#netcdf_precision"><span style="font-weight: bold;">netcdf_precision</span></a></td>
-<td>I</td> <td>C * 20 (10)</td> <td><span style="font-style: italic;">single preci</span><span style="font-style: italic;">sion for all</span><br style="font-style: italic;"> <span style="font-style: italic;">output quan</span><span style="font-style: italic;">tities</span></td> <td>Defines
-the accuracy of the NetCDF output.<br> </td> </tr> <tr>
-<td><a href="chapter_4.2.html#netcdf_64bit"><span style="font-weight: bold;">netcdf_64bit</span></a></td>
-<td>R</td> <td>L</td> <td><span style="font-style: italic;">.F.</span></td> <td>NetCDF
-files will have 64 bit offset format.</td> </tr> <tr><td><a style="font-weight: bold;" href="chapter_4.2.html#netcdf_64bit_3d">netcdf_64bit_3d</a></td><td>R</td><td>L</td><td><span style="font-style: italic;">.T.</span></td><td>NetCDF
-files containing 3d volume data will have 64 bit offset format.</td></tr><tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#ngsrb"><b>ngsrb</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>2</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Grid
-level at which data shall be gathered on PE0.</p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.2.html#normalizing_region"><b>normalizing_region</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Determines
+software. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+  <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#momentum_advec"><b>momentum_advec</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 10</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'pw-scheme</i>'</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Advection scheme to be used for the momentum equations.</p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#netcdf_precision"><span style="font-weight: bold;">netcdf_precision</span></a></td>
+
+
+      <td>I</td>
+
+ <td>C * 20 (10)</td>
+
+ <td><span style="font-style: italic;">single preci</span><span style="font-style: italic;">sion for all</span><br style="font-style: italic;">
+
+ <span style="font-style: italic;">output quan</span><span style="font-style: italic;">tities</span></td>
+
+ <td>Defines
+the accuracy of the NetCDF output.<br>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td><a href="chapter_4.2.html#netcdf_64bit"><span style="font-weight: bold;">netcdf_64bit</span></a></td>
+
+
+      <td>R</td>
+
+ <td>L</td>
+
+ <td><span style="font-style: italic;">.F.</span></td>
+
+ <td>NetCDF
+files will have 64 bit offset format.</td>
+
+ </tr>
+
+ <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.2.html#netcdf_64bit_3d">netcdf_64bit_3d</a></td>
+
+      <td>R</td>
+
+      <td>L</td>
+
+      <td><span style="font-style: italic;">.T.</span></td>
+
+      <td>NetCDF
+files containing 3d volume data will have 64 bit offset format.</td>
+
+    </tr>
+
+    <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#ngsrb"><b>ngsrb</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>2</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Grid
+level at which data shall be gathered on PE0.</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.2.html#normalizing_region"><b>normalizing_region</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Determines
 the subdomain from which the normalization
-quantities are calculated. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#npex"><b>npex</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>no default, see parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
+quantities are calculated. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#npex"><b>npex</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>no default, see parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
 of processors along x-direction of the virtual
 processor
-net. <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#npey"><b>npey</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>no default, see parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
+net. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#npey"><b>npey</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>no default, see parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
 of processors along y-direction of the virtual
 processor
-net. <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#nsor"><b>nsor</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>20</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
-of iterations to be used with the SOR-scheme. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#nsor_ini"><b>nsor_ini</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>100</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Initial
-number of iterations with the SOR algorithm</p> </td> </tr>
-<tr> <td><a href="chapter_4.2.html#number_of_particle_groups"><span style="font-weight: bold;">number_of_particle_groups</span></a></td>
-<td>P</td> <td>I</td> <td><span style="font-style: italic;">1</span></td> <td>Number
-of particle groups to be used.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#nx"><b>nx</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>no default, see parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
-of grid points in x-direction. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#ny"><b>ny</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>no default, see parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
-of grid points in y-direction.</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#nz"><b>nz</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p>no default, see parameter description</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
-of grid points in z-direction.</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#nz_do3d"><b>nz_do3d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>nz+1</i></p> </td> <td style="vertical-align: middle;" width="57%"> Limits
+net. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#nsor"><b>nsor</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>20</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
+of iterations to be used with the SOR-scheme. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#nsor_ini"><b>nsor_ini</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>100</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Initial
+number of iterations with the SOR algorithm</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#number_of_particle_groups"><span style="font-weight: bold;">number_of_particle_groups</span></a></td>
+
+
+      <td>P</td>
+
+ <td>I</td>
+
+ <td><span style="font-style: italic;">1</span></td>
+
+ <td>Number
+of particle groups to be used.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#nx"><b>nx</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>no default, see parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
+of grid points in x-direction. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#ny"><b>ny</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>no default, see parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
+of grid points in y-direction.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#nz"><b>nz</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p>no default, see parameter description</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
+of grid points in z-direction.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#nz_do3d"><b>nz_do3d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>nz+1</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> Limits
 the output of 3d volume data along the vertical direction (grid point
-index k).</td> </tr> <tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#ocean"><span style="font-weight: bold;">ocean</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">L</td><td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td><td align="undefined" valign="undefined">Parameter to switch on&nbsp;ocean runs.</td></tr><tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#omega"><b>omega</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>7.29212E-5</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Angular
+index k).</td>
+
+ </tr>
+
+ <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#ocean"><span style="font-weight: bold;">ocean</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">L</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
+
+      <td align="undefined" valign="undefined">Parameter to switch on&nbsp;ocean runs.</td>
+
+    </tr>
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#omega"><b>omega</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>7.29212E-5</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Angular
 velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;</p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#omega_sor"><b>omega_sor</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.8</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Convergence
-factor to be used with the the SOR-scheme. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#outflow_damping_width"><b>outflow_damping_width</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;"><span style="font-style: italic;">MIN(20,
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#omega_sor"><b>omega_sor</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.8</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Convergence
+factor to be used with the the SOR-scheme. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#outflow_damping_width"><b>outflow_damping_width</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(20,
 nx/2</span> or <span style="font-style: italic;">ny/2)</span></td>
-<td style="vertical-align: middle;">Width of
+
+
+      <td style="vertical-align: middle;">Width of
 the damping range in the vicinity of the outflow (gridpoints).</td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#overshoot_limit_e"><b>overshoot_limit_e</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Allowed
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_e"><b>overshoot_limit_e</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <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>).</p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#overshoot_limit_pt"><b>overshoot_limit_pt</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Allowed
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_pt"><b>overshoot_limit_pt</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Allowed
 limit for the overshooting of potential
 temperature in
 case that the upstream-spline scheme is switched on (in K). <br>
-</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#overshoot_limit_u"><b>overshoot_limit_u</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Allowed
+
+
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_u"><b>overshoot_limit_u</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>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> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#overshoot_limit_v"><b>overshoot_limit_v</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Allowed
+switched on (in m/s).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_v"><b>overshoot_limit_v</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <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). <br> </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#overshoot_limit_w"><b>overshoot_limit_w</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Allowed
+(in m/s). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_w"><b>overshoot_limit_w</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <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). <br> </p> </td> </tr> <tr>
-<td align="undefined" valign="undefined"><a href="chapter_4.2.html#particles_per_point"><span style="font-weight: bold;">particles_per_point</span></a></td>
-<td align="undefined" valign="undefined">P</td>
-<td align="undefined" valign="undefined">I</td>
-<td align="undefined" valign="undefined"><span style="font-style: italic;">1</span></td> <td align="undefined" valign="undefined">Number of
-particles to be started per point.</td> </tr> <tr> <td style="vertical-align: top;"><b><a href="chapter_4.2.html#particle_advection_start"><b>particle_advection_start</b></a></b></td>
-<td style="vertical-align: top;">P<br> </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;">Time of the first
+(in m/s). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#particles_per_point"><span style="font-weight: bold;">particles_per_point</span></a></td>
+
+
+      <td align="undefined" valign="undefined">P</td>
+
+
+      <td align="undefined" valign="undefined">I</td>
+
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">1</span></td>
+
+ <td align="undefined" valign="undefined">Number of
+particles to be started per point.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: top;"><b><a href="chapter_4.2.html#particle_advection_start"><b>particle_advection_start</b></a></b></td>
+
+
+      <td style="vertical-align: top;">P<br>
+
+ </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;">Time of the first
 release of
-particles (in s).</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#particle_maximum_age"><b>particle_maximum_age</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>9999999.9</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Maximum
-allowed age of particles (in s). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#passive_scalar"><b>passive_scalar</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
+particles (in s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#particle_maximum_age"><b>particle_maximum_age</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>9999999.9</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Maximum
+allowed age of particles (in s). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#passive_scalar"><b>passive_scalar</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
 to switch on the prognostic equation for a
 passive
-scalar. </p> </td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#pdx"><b>pdx</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * dx</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Distance
+scalar. </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#pdx"><b>pdx</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * dx</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Distance
 along x between particles within a particle
 source
-(in m). <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#pdy"><b>pdy</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * dy</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Distance
+(in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#pdy"><b>pdy</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * dy</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Distance
 along y between
 particles within a
-particle source (in m). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.2.html#pdz"><b>pdz</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * ( zu(2) - zu(1) )</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Distance along z between
+particle source (in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.2.html#pdz"><b>pdz</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * ( zu(2) - zu(1) )</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Distance along z between
 particles within a particle source
-(in m).</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#phi"><b>phi</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>55.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Geographical
-latitude (in degrees). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.2.html#plot_spectra_level"><b>plot_spectra_level</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>No level</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Vertical level(s) for which horizontal spectra are to be
-plotted (in gridpoints). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#prandtl_layer"><b>prandtl_layer</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.T.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
-to switch on a Prandtl layer. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.2.html#prandtl_number"><b>prandtl_number</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Ratio
+(in m).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#phi"><b>phi</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>55.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Geographical
+latitude (in degrees). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.2.html#plot_spectra_level"><b>plot_spectra_level</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>No level</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Vertical level(s) for which horizontal spectra are to be
+plotted (in gridpoints). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#prandtl_layer"><b>prandtl_layer</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.T.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
+to switch on a Prandtl layer. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.2.html#prandtl_number"><b>prandtl_number</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Ratio
 of the eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).
-<br> </p> </td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#precipitation"><b>precipitation</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">L<br> </td>
-<td style="vertical-align: middle;"><span style="font-style: italic;">.F.</span></td> <td style="vertical-align: middle;">Parameter to
+      <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#precipitation"><b>precipitation</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">L<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">.F.</span></td>
+
+ <td style="vertical-align: middle;">Parameter to
 switch on the
-precipitation scheme.</td> </tr> <tr><td><a style="font-weight: bold;" href="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_<br>interval</a></td><td>R</td><td>R</td><td><i>value
+precipitation scheme.</td>
+
+ </tr>
+
+ <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_<br>
+
+interval</a></td>
+
+      <td>R</td>
+
+      <td>R</td>
+
+      <td><i>value
 of &nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>
-xy</a></i></td><td><font face="Thorndale"><font face="Thorndale, serif">Temporal
-interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;</font></td></tr><tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#profile_columns"><b>profile_columns</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>3</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
+
+
+xy</a></i></td>
+
+      <td><font face="Thorndale"><font face="Thorndale, serif">Temporal
+interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;</font></td>
+
+    </tr>
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#profile_columns"><b>profile_columns</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>3</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
 of coordinate systems to be plotted<span style="font-weight: bold;"></span>
 in one row by <span style="font-weight: bold;">profil</span>.
-<br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#profile_rows"><b>profile_rows</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>2</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
+      <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#profile_rows"><b>profile_rows</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>2</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
 of rows of coordinate systems to be plotted on
 one page
 by <span style="font-weight: bold;">profil</span>. <br>
-</p> </td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#psb"><b>psb</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * zu(nz/2)</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Bottom edge of a particle
-source (in m).</p> </td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#psl"><b>psl</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * 0.0</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Left edge of a particle source
-(in m). </p> </td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#psn"><b>psn</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * ( ny * dy )</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Rear (&ldquo;north&rdquo;) edge of a particle
-source (in m).</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#psolver"><b>psolver</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 10</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'poisfft'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Scheme to be used to solve the Poisson equation for the
-perturbation pressure. <br> </p> </td> </tr>
-<tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#psr"><b>psr</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * ( nx * dx )</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Right edge of a particle source (in m).</p> </td>
-</tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#pss"><b>pss</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * 0.0</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Front (&ldquo;south&rdquo;) edge of a particle
-source (in m).</p> </td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#pst"><b>pst</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * zu(nz/2)</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Top edge of a particle source (in m).</p> </td> </tr>
-<tr><td><a style="font-weight: bold;" href="chapter_4.1.html#pt_reference">pt_reference</a></td><td>I</td><td>R</td><td><span style="font-style: italic;">use horizontal average as
-reference</span></td><td>Reference temperature to be
-used in all buoyancy terms (in K).</td></tr><tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#pt_surface"><b>pt_surface</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>300.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Surface
-potential temperature (in K). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#pt_surface_initial_change"><b>pt_surface_initial</b></a>&nbsp;&nbsp;&nbsp;
-<br> <a href="chapter_4.1.html#pt_surface_initial_change">&nbsp;<b>_change</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%">Change
+
+
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#psb"><b>psb</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * zu(nz/2)</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Bottom edge of a particle
+source (in m).</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#psl"><b>psl</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * 0.0</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Left edge of a particle source
+(in m). </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#psn"><b>psn</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * ( ny * dy )</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Rear (&ldquo;north&rdquo;) edge of a particle
+source (in m).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#psolver"><b>psolver</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 10</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'poisfft'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Scheme to be used to solve the Poisson equation for the
+perturbation pressure. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#psr"><b>psr</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * ( nx * dx )</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Right edge of a particle source (in m).</p>
+
+ </td>
+
+
+    </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#pss"><b>pss</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * 0.0</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Front (&ldquo;south&rdquo;) edge of a particle
+source (in m).</p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#pst"><b>pst</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * zu(nz/2)</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Top edge of a particle source (in m).</p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.1.html#pt_reference">pt_reference</a></td>
+
+      <td>I</td>
+
+      <td>R</td>
+
+      <td><span style="font-style: italic;">use horizontal average as
+reference</span></td>
+
+      <td>Reference temperature to be
+used in all buoyancy terms (in K).</td>
+
+    </tr>
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#pt_surface"><b>pt_surface</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>300.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Surface
+potential temperature (in K). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#pt_surface_initial_change"><b>pt_surface_initial</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.1.html#pt_surface_initial_change">&nbsp;<b>_change</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%">Change
 in surface
 temperature to be made at the
 beginning of
 the 3d run
-(in K).&nbsp;</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#pt_vertical_gradient"><b>pt_vertical_gradient</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * 0.0</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Temperature gradient(s) of the initial temperature
+(in K).&nbsp;</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#pt_vertical_gradient"><b>pt_vertical_gradient</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * 0.0</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Temperature gradient(s) of the initial temperature
 profile (in
 K
-/ 100 m). <br> </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#pt_vertical_gradient_level"><b>pt_vertical_gradient</b></a>&nbsp;&nbsp;&nbsp;
-<br> <a href="chapter_4.1.html#pt_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 *</i>&nbsp; <i>0.0</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Height level from which on the temperature gradient
+/ 100 m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#pt_vertical_gradient_level"><b>pt_vertical_gradient</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.1.html#pt_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Height level from which on the temperature gradient
 defined by <a href="chapter_4.1.html#pt_vertical_gradient">pt_vertical_gradient</a>
-is effective (in m).&nbsp;</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#q_surface"><b>q_surface</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Surface
-specific humidity / total water content (kg/kg). <br> </p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#q_surface_initial_change"><b>q_surface_initial</b></a>
-<br> <a href="chapter_4.1.html#q_surface_initial_change">&nbsp;<b>_change</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Change
+is effective (in m).&nbsp;</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#q_surface"><b>q_surface</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Surface
+specific humidity / total water content (kg/kg). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#q_surface_initial_change"><b>q_surface_initial</b></a>
+      <br>
+
+ <a href="chapter_4.1.html#q_surface_initial_change">&nbsp;<b>_change</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Change
 in surface specific humidity / total water
 content to
 be made at the beginning
-of the 3d run (kg/kg). <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#q_vertical_gradient"><b>q_vertical_gradient</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * 0.0</i></p>
-</td> <td style="width: 57%; vertical-align: middle;">
-<p>Humidity gradient(s) of the initial humidity profile
-(in 1/100 m). </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#q_vertical_gradient_level"><b>q_vertical_gradient</b></a>
-<br> <a href="chapter_4.1.html#q_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 *</i>&nbsp; <i>0.0</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Height level from which on the humidity gradient defined
+of the 3d run (kg/kg). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#q_vertical_gradient"><b>q_vertical_gradient</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * 0.0</i></p>
+
+
+      </td>
+
+ <td style="width: 57%; vertical-align: middle;">
+      
+      <p>Humidity gradient(s) of the initial humidity profile
+(in 1/100 m). </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#q_vertical_gradient_level"><b>q_vertical_gradient</b></a>
+      <br>
+
+ <a href="chapter_4.1.html#q_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Height level from which on the humidity gradient defined
 by <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
-is effective (in m).&nbsp;</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#radiation"><b>radiation</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
+is effective (in m).&nbsp;</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#radiation"><b>radiation</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
 to switch on longwave radiation cooling at
-cloud-tops. <br> </p> </td> </tr> <tr>
-<td><a href="chapter_4.2.html#radius"><span style="font-weight: bold;">radius</span></a></td>
-<td>P</td> <td>R (10)</td> <td><i>0.0,
-9</i>*<br> <i>9999999.9</i></td> <td>Particle
-radius (in m).</td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#random_generator"><b>random_generator</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'numerical recipes'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Random number generator to be used for creating
+cloud-tops. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td><a href="chapter_4.2.html#radius"><span style="font-weight: bold;">radius</span></a></td>
+
+
+      <td>P</td>
+
+ <td>R (10)</td>
+
+ <td><i>0.0,
+9</i>*<br>
+
+ <i>9999999.9</i></td>
+
+ <td>Particle
+radius (in m).</td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#random_generator"><b>random_generator</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'numerical recipes'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Random number generator to be used for creating
 uniformly
-distributed random numbers. </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#random_heatflux"><b>random_heatflux</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
+distributed random numbers. </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#random_heatflux"><b>random_heatflux</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
 to impose random perturbations on the internal two-dimensional near
 surface heat flux field <span style="font-style: italic;">shf</span>.
-</p> </td> </tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#random_start_position"><b>random_start_position</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#random_start_position"><b>random_start_position</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
 particles is
 varied randomly within certain limits.&nbsp;</span></p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#rayleigh_damping_factor"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#rayleigh_damping_factor">&nbsp;<b>_factor</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><span style="font-style: italic;">0.0</span>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#rayleigh_damping_factor"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#rayleigh_damping_factor">&nbsp;<b>_factor</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><span style="font-style: italic;">0.0</span>
 and/or <span style="font-style: italic;">0.01</span>
-(see parameter description)</p> </td> <td style="vertical-align: middle;" width="57%"> <p>Factor
-for Rayleigh damping.&nbsp;</p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#rayleigh_damping_height"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#rayleigh_damping_height">&nbsp;<b>_height</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle; font-style: italic;" width="16%"> <p>2/3 * zu(nz)</p> </td> <td style="width: 57%; text-align: left; vertical-align: middle;">
-<p>Height where the Rayleigh damping starts (in
-m).&nbsp; </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#read_particles_from_restartfile"><b>read_particles_from_</b></a>
-<br> <a href="chapter_4.2.html#read_particles_from_restartfile"><b>restartfile</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.T.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Read
-particle data from the previous run. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.3.html#region"><b>region</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>U</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 40 (0:9)</p> </td> <td style="vertical-align: middle;" width="16%"> <p>&nbsp;</p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Name(s) of the subdomain(s) defined by the user.</p> </td>
-</tr> <tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#residual_limit"><b>residual_limit</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0E-6</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Largest
+(see parameter description)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Factor
+for Rayleigh damping.&nbsp;</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#rayleigh_damping_height"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#rayleigh_damping_height">&nbsp;<b>_height</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle; font-style: italic;" width="16%"> 
+      
+      <p>2/3 * zu(nz)</p>
+
+ </td>
+
+ <td style="width: 57%; text-align: left; vertical-align: middle;">
+      
+      <p>Height where the Rayleigh damping starts (in
+m).&nbsp; </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#read_particles_from_restartfile"><b>read_particles_from_</b></a>
+      <br>
+
+ <a href="chapter_4.2.html#read_particles_from_restartfile"><b>restartfile</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.T.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Read
+particle data from the previous run. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.3.html#region"><b>region</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>U</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 40 (0:9)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p>&nbsp;</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Name(s) of the subdomain(s) defined by the user.</p>
+
+ </td>
+
+
+    </tr>
+
+ <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#residual_limit"><b>residual_limit</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0E-6</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Largest
 residual permitted for the multi-grid scheme (in
-s<sup>-2</sup>m<sup>-3</sup>). <br> </p>
-</td> </tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#restart_time"><b>restart_time</b></a></b></td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;">9999999.9<br> </td>
-<td style="vertical-align: middle;">Simulated time
+s<sup>-2</sup>m<sup>-3</sup>). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#restart_time"><b>restart_time</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">9999999.9<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">Simulated time
 after which a
 restart run is to be carried out
-(in s).</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#rif_max"><b>rif_max</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Upper
-limit of the flux-Richardson number. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#rif_min"><b>rif_min</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>- 5.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Lower
-limit of the flux-Richardson number. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#roughness_length"><b>roughness_length</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.1</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Roughness
-length (in m). <br> </p> </td> </tr> <tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_surface"><span style="font-weight: bold;">sa_surface</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">35.0</span></td><td align="undefined" valign="undefined">Surface salinity (in psu).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_vertical_gradient"><span style="font-weight: bold;">sa_vertical_gradient</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R(10)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">10 * 0.0</span></td><td align="undefined" valign="undefined">Salinity gradient(s) of the initial salinity profile (in psu
-/ 100 m).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_vertical_gradient_level"><span style="font-weight: bold;">sa_vertical_gradient_level</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R(10)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">10 * 0.0</span></td><td align="undefined" valign="undefined">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).</td></tr><tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#scalar_advec"><b>scalar_advec</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 10</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'pw-scheme'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Advection scheme to be used for the scalar quantities. <br>
-</p> </td> </tr> <tr> <td><a href="chapter_4.2.html#section_xy"><span style="font-weight: bold;">section_xy</span></a></td>
-<td>R</td> <td>I (100)</td> <td><span style="font-style: italic;">no section</span></td>
-<td><font face="Thorndale">Position
+(in s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#rif_max"><b>rif_max</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Upper
+limit of the flux-Richardson number. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#rif_min"><b>rif_min</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>- 5.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Lower
+limit of the flux-Richardson number. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#roughness_length"><b>roughness_length</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.1</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Roughness
+length (in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_surface"><span style="font-weight: bold;">sa_surface</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">35.0</span></td>
+
+      <td align="undefined" valign="undefined">Surface salinity (in psu).</td>
+
+    </tr>
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_vertical_gradient"><span style="font-weight: bold;">sa_vertical_gradient</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R(10)</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">10 * 0.0</span></td>
+
+      <td align="undefined" valign="undefined">Salinity gradient(s) of the initial salinity profile (in psu
+/ 100 m).</td>
+
+    </tr>
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_vertical_gradient_level"><span style="font-weight: bold;">sa_vertical_gradient_level</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R(10)</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">10 * 0.0</span></td>
+
+      <td align="undefined" valign="undefined">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).</td>
+
+    </tr>
+
+    <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#scalar_advec"><b>scalar_advec</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 10</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'pw-scheme'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Advection scheme to be used for the scalar quantities. <br>
+
+
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#section_xy"><span style="font-weight: bold;">section_xy</span></a></td>
+
+
+      <td>R</td>
+
+ <td>I (100)</td>
+
+ <td><span style="font-style: italic;">no section</span></td>
+
+
+      <td><font face="Thorndale">Position
 of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
-sections (grid point index k).&nbsp;</font></td> </tr>
-<tr> <td><a href="chapter_4.2.html#section_xz"><span style="font-weight: bold;">section_xz</span></a></td>
-<td>R</td> <td>I (100)</td> <td><span style="font-style: italic;">no section</span></td>
-<td><font face="Thorndale">Position
+sections (grid point index k).&nbsp;</font></td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#section_xz"><span style="font-weight: bold;">section_xz</span></a></td>
+
+
+      <td>R</td>
+
+ <td>I (100)</td>
+
+ <td><span style="font-style: italic;">no section</span></td>
+
+
+      <td><font face="Thorndale">Position
 of&nbsp;cross section(s) for&nbsp;output of 2d (xz) vertical
-cross sections (grid point index j).&nbsp;</font></td> </tr>
-<tr> <td><a href="chapter_4.2.html#section_yz"><span style="font-weight: bold;">section_yz</span></a></td>
-<td>R</td> <td>I (100)</td> <td><span style="font-style: italic;">no section</span></td>
-<td><font face="Thorndale">Position
+cross sections (grid point index j).&nbsp;</font></td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#section_yz"><span style="font-weight: bold;">section_yz</span></a></td>
+
+
+      <td>R</td>
+
+ <td>I (100)</td>
+
+ <td><span style="font-style: italic;">no section</span></td>
+
+
+      <td><font face="Thorndale">Position
 of&nbsp;cross section(s) for&nbsp;output of 2d (yz) vertical
-cross sections (grid point index i).&nbsp;</font></td> </tr>
-<tr> <td><a href="chapter_4.2.html#skip_particles_for_tail"><span style="font-weight: bold;">skip_particles_for_tail</span></a></td>
-<td>P</td> <td>I</td> <td><span style="font-style: italic;">1</span></td> <td>Limit
-the number of particle tails.</td> </tr> <tr> <td><a href="chapter_4.2.html#skip_time_data_output"><span style="font-weight: bold;">skip_time_data_output</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">0.0</span></td> <td>No
-data output before this interval has passed (in s).</td> </tr>
-<tr> <td><a href="chapter_4.2.html#skip_time_data_output_av"><span style="font-weight: bold;">skip_time_data_output_av</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
+cross sections (grid point index i).&nbsp;</font></td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#skip_particles_for_tail"><span style="font-weight: bold;">skip_particles_for_tail</span></a></td>
+
+
+      <td>P</td>
+
+ <td>I</td>
+
+ <td><span style="font-style: italic;">1</span></td>
+
+ <td>Limit
+the number of particle tails.</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_data_output"><span style="font-weight: bold;">skip_time_data_output</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">0.0</span></td>
+
+ <td>No
+data output before this interval has passed (in s).</td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_data_output_av"><span style="font-weight: bold;">skip_time_data_output_av</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
 temporally averaged 2d/3d data before this interval has passed (in s).</td>
-</tr> <tr> <td><a href="chapter_4.2.html#skip_time_dopr"><span style="font-weight: bold;">skip_time_dopr</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
+
+
+    </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_dopr"><span style="font-weight: bold;">skip_time_dopr</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
 vertical profile data before this interval has passed (in s).</td>
-</tr> <tr> <td><a href="chapter_4.2.html#skip_time_dosp"><span style="font-weight: bold;">skip_time_dosp</span></a></td>
-<td>P</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
-spectra data before this interval has passed (in s).</td> </tr>
-<tr> <td><a href="chapter_4.2.html#skip_time_do2d_xy"><span style="font-weight: bold;">skip_time_do2d_xy</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
+
+
+    </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_dosp"><span style="font-weight: bold;">skip_time_dosp</span></a></td>
+
+
+      <td>P</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
+spectra data before this interval has passed (in s).</td>
+
+ </tr>
+
+
+    <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_do2d_xy"><span style="font-weight: bold;">skip_time_do2d_xy</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
 instantaneous horizontal cross section data before this interval has
-passed (in s).</td> </tr> <tr> <td><a href="chapter_4.2.html#skip_time_do2d_xz"><span style="font-weight: bold;">skip_time_do2d_xz</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
+passed (in s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_do2d_xz"><span style="font-weight: bold;">skip_time_do2d_xz</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
 instantaneous vertical (xz) cross section data before this interval has
-passed (in s).</td> </tr> <tr> <td><a href="chapter_4.2.html#skip_time_do2d_yz"><span style="font-weight: bold;">skip_time_do2d_yz</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
+passed (in s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_do2d_yz"><span style="font-weight: bold;">skip_time_do2d_yz</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
 instantaneous vertical (yz) cross section data before this interval has
-passed (in s).<br> </td> </tr> <tr> <td><a href="chapter_4.2.html#skip_time_do3d"><span style="font-weight: bold;">skip_time_do3d</span></a></td>
-<td>R</td> <td>R</td> <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-data_output</a></span></td> <td>No output of
+passed (in s).<br>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#skip_time_do3d"><span style="font-weight: bold;">skip_time_do3d</span></a></td>
+
+
+      <td>R</td>
+
+ <td>R</td>
+
+ <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+
+
+data_output</a></span></td>
+
+ <td>No output of
 instantaneous 3d volume data before this interval has passed (in s).</td>
-</tr> <tr> <td style="vertical-align: middle;"><b><a href="file:///home/raasch/public_html/PALM_group/doc/app/chapter_4.2.html#spectra_direction"><b>slicer_range_limits_dvrp</b></a></b></td>
-<td style="vertical-align: middle;">P<br> </td>
-<td style="vertical-align: middle;">R(2,10)<br> </td>
-<td style="vertical-align: middle;"><span style="font-style: italic;">10
-* (-1,1)</span></td> <td style="vertical-align: middle;">Ranges
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="file:///home/raasch/public_html/PALM_group/doc/app/chapter_4.2.html#spectra_direction"><b>slicer_range_limits_dvrp</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">P<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R(2,10)<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">10
+* (-1,1)</span></td>
+
+ <td style="vertical-align: middle;">Ranges
 of values to which a color table has to be mapped (units of the
-respective quantity).</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#spectra_direction"><b>spectra_direction</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 2 (10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>10 * ' '</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Direction(s) along which spectra are to be calculated. <br>
-</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#statistic_regions"><b>statistic_regions</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>I</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Number
+respective quantity).</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#spectra_direction"><b>spectra_direction</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 2 (10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>10 * ' '</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Direction(s) along which spectra are to be calculated. <br>
+
+
+      </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#statistic_regions"><b>statistic_regions</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>I</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Number
 of additional user-defined subdomains for which
 statistical analysis
 and corresponding output (profiles, time series) shall be made.</p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#superelevation"><b>superelevation</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Superelevation
-factor for the vertical coordinate. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#superelevation_x"><b>superelevation_x</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Superelevation
-factor for the horizontal (x) coordinate. <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#superelevation_y"><b>superelevation_y</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Superelevation
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#superelevation"><b>superelevation</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Superelevation
+factor for the vertical coordinate. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#superelevation_x"><b>superelevation_x</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Superelevation
+factor for the horizontal (x) coordinate. <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#superelevation_y"><b>superelevation_y</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Superelevation
 factor for the
-horizontal (y) coordinate. <br> </p> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#surface_heatflux"><b>surface_heatflux</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><span style="font-style: italic;">no prescribed
-heatflux</span></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Kinematic
-sensible heat flux at the bottom surface (in K m/s).</p> </td>
-</tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#surface_pressure"><b>surface_pressure</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>1013.25</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Atmospheric
-pressure at the surface (in hPa)</p> </td> </tr> <tr>
-<td style="vertical-align: middle;"><b><a href="chapter_4.1.html#surface_scalarflux"><b>surface_scalarflux</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;"><i>0.0</i></td>
-<td style="vertical-align: middle;">Scalar flux at
+horizontal (y) coordinate. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#surface_heatflux"><b>surface_heatflux</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><span style="font-style: italic;">no prescribed
+heatflux</span></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Kinematic
+sensible heat flux at the bottom surface (in K m/s).</p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#surface_pressure"><b>surface_pressure</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>1013.25</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Atmospheric
+pressure at the surface (in hPa)</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#surface_scalarflux"><b>surface_scalarflux</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><i>0.0</i></td>
+
+
+      <td style="vertical-align: middle;">Scalar flux at
 the surface
-(in kg/(m<sup>2</sup> s)). <br> </td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#surface_waterflux"><b>surface_waterflux</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Kinematic
-water flux near the surface (in m/s). <br> </p> </td>
-</tr> <tr> <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#s_surface"><b>s_surface</b></a></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;"><i>0.0</i></td>
-<td style="vertical-align: middle;">Surface value of
+(in kg/(m<sup>2</sup> s)). <br>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#surface_waterflux"><b>surface_waterflux</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Kinematic
+water flux near the surface (in m/s). <br>
+
+ </p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#s_surface"><b>s_surface</b></a></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><i>0.0</i></td>
+
+
+      <td style="vertical-align: middle;">Surface value of
 the passive
-scalar (in kg/m<sup>3</sup>). <br> </td> </tr>
-<tr> <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_surface_initial_change"><b>s_surface_initial_change</b></a></b></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">R<br> </td>
-<td style="vertical-align: middle;"><i>0.0</i></td>
-<td style="vertical-align: middle;">Change in
+scalar (in kg/m<sup>3</sup>). <br>
+
+ </td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_surface_initial_change"><b>s_surface_initial_change</b></a></b></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><i>0.0</i></td>
+
+
+      <td style="vertical-align: middle;">Change in
 surface scalar
 concentration to be made at the
-beginning of the 3d run (in kg/m<sup>3</sup>). <br> </td>
-</tr> <tr> <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_vertical_gradient"><b>s_vertical_gradient</b></a></b></b></td>
-<td style="vertical-align: middle;">I<br> </td>
-<td style="vertical-align: middle;">R(10)<br> </td>
-<td style="vertical-align: middle;"><i>10 * 0</i><i>.0</i></td>
-<td style="vertical-align: middle;">Scalar
+beginning of the 3d run (in kg/m<sup>3</sup>). <br>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_vertical_gradient"><b>s_vertical_gradient</b></a></b></b></td>
+
+
+      <td style="vertical-align: middle;">I<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;">R(10)<br>
+
+ </td>
+
+
+      <td style="vertical-align: middle;"><i>10 * 0</i><i>.0</i></td>
+
+
+      <td style="vertical-align: middle;">Scalar
 concentration
 gradient(s) of the initial scalar
 concentration profile (in kg/m<sup>3 </sup>/
-100 m). <br> </td> </tr> <tr> <td><a href="chapter_4.1.html#s_vertical_gradient_level"><span style="font-weight: bold;">s_vertical_gradient_level</span></a></td>
-<td>I</td> <td>R(10)</td> <td><span style="font-style: italic;">10 * 0.0</span></td>
-<td>Height level from which on the scalar gradient defined by <a href="chapter_4.1.html#s_vertical_gradient">s_vertical_gradient</a>
-is effective (in m).</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#termination_time_needed"><b>termination_time</b></a>&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#termination_time_needed">&nbsp;<b>_needed</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>35.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>CPU
+100 m). <br>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#s_vertical_gradient_level"><span style="font-weight: bold;">s_vertical_gradient_level</span></a></td>
+
+
+      <td>I</td>
+
+ <td>R(10)</td>
+
+ <td><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+      <td>Height level from which on the scalar gradient defined by <a href="chapter_4.1.html#s_vertical_gradient">s_vertical_gradient</a>
+is effective (in m).</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#termination_time_needed"><b>termination_time</b></a>&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#termination_time_needed">&nbsp;<b>_needed</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>35.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>CPU
 time needed for terminal actions at the end of a run
 in
-batch mode (in s).</p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#threshold"><b>threshold</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>P</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R
-(10)</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>0.0</i></p> </td>
-<td style="vertical-align: middle;" width="57%"> <p>Threshold
+batch mode (in s).</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#threshold"><b>threshold</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>P</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R
+(10)</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+
+      <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Threshold
 value for which an isosurface is to be created
 by
 the <span style="font-weight: bold;">dvrp</span>
-software. <br> </p> </td> </tr> <tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#timestep_scheme"><b>timestep_scheme</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>C
-* 20</p> </td> <td style="vertical-align: middle;" width="16%"> <p><i>'runge-kutta-3'</i></p>
-</td> <td style="vertical-align: middle;" width="57%">
-<p>Time step scheme to be used for integration of the prognostic
-variables. <br> </p> </td> </tr> <tr>
-<td><a href="chapter_4.1.html#topography"><span style="font-weight: bold;">topography</span></a></td>
-<td>I</td> <td>C * 40</td> <td><span style="font-style: italic;">'flat'</span></td> <td>Topography
-mode.</td> </tr> <tr><td><a style="font-weight: bold;" href="chapter_4.1.html#top_heatflux">top_heatflux</a></td><td>I</td><td>R</td><td><span style="font-style: italic;">no prescribed heatflux</span></td><td>Kinematic
-sensible heat flux at the top surface (in K m/s).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#top_momentumflux_u"><span style="font-weight: bold;">top_momentumflux_u</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed momentumflux</span></td><td align="undefined" valign="undefined">Momentum flux along x at the top boundary (in m2/s2).</td></tr><tr><td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed momentumflux</span></td><td align="undefined" valign="undefined">Momentum flux along y at the top boundary (in m2/s2).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#top_salinityflux"><span style="font-weight: bold;">top_salinityflux</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed</span><br style="font-style: italic;"><span style="font-style: italic;">salinityflux</span></td><td align="undefined" valign="undefined">Kinematic
-salinity flux at the top boundary, i.e. the sea surface (in psu m/s).</td></tr><tr>
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#ug_surface"><b>ug_surface</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>u-component
-of the geostrophic wind at the surface (in m/s). <br> </p>
-</td> </tr> <tr> <td><a href="chapter_4.1.html#ug_vertical_gradient"><span style="font-weight: bold;">ug_vertical_gradient</span></a></td>
-<td>I</td> <td>R(10)</td> <td><span style="font-style: italic;">10 * 0.0</span></td>
-<td>Gradient(s) of the initial
+software. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#timestep_scheme"><b>timestep_scheme</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>C
+* 20</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="16%"> 
+      
+      <p><i>'runge-kutta-3'</i></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="57%">
+      
+      <p>Time step scheme to be used for integration of the prognostic
+variables. <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td><a href="chapter_4.1.html#topography"><span style="font-weight: bold;">topography</span></a></td>
+
+
+      <td>I</td>
+
+ <td>C * 40</td>
+
+ <td><span style="font-style: italic;">'flat'</span></td>
+
+ <td>Topography
+mode.</td>
+
+ </tr>
+
+ <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.1.html#top_heatflux">top_heatflux</a></td>
+
+      <td>I</td>
+
+      <td>R</td>
+
+      <td><span style="font-style: italic;">no prescribed heatflux</span></td>
+
+      <td>Kinematic
+sensible heat flux at the top surface (in K m/s).</td>
+
+    </tr>
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#top_momentumflux_u"><span style="font-weight: bold;">top_momentumflux_u</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed momentumflux</span></td>
+
+      <td align="undefined" valign="undefined">Momentum flux along x at the top boundary (in m2/s2).</td>
+
+    </tr>
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed momentumflux</span></td>
+
+      <td align="undefined" valign="undefined">Momentum flux along y at the top boundary (in m2/s2).</td>
+
+    </tr>
+
+    <tr>
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#top_salinityflux"><span style="font-weight: bold;">top_salinityflux</span></a></td>
+
+      <td align="undefined" valign="undefined">I</td>
+
+      <td align="undefined" valign="undefined">R</td>
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed</span><br style="font-style: italic;">
+
+      <span style="font-style: italic;">salinityflux</span></td>
+
+      <td align="undefined" valign="undefined">Kinematic
+salinity flux at the top boundary, i.e. the sea surface (in psu m/s).</td>
+
+    </tr>
+
+    <tr>
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#ug_surface"><b>ug_surface</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>u-component
+of the geostrophic wind at the surface (in m/s). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#ug_vertical_gradient"><span style="font-weight: bold;">ug_vertical_gradient</span></a></td>
+
+
+      <td>I</td>
+
+ <td>R(10)</td>
+
+ <td><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+      <td>Gradient(s) of the initial
 profile of the&nbsp; u-component of the geostrophic wind (in
-1/100s).</td> </tr> <tr> <td><a href="chapter_4.1.html#ug_vertical_gradient_level"><span style="font-weight: bold;">ug_vertical_gradient_level</span></a></td>
-<td>I</td> <td>R(10)</td> <td><span style="font-style: italic;">10 * 0.0</span></td>
-<td>Height level from which on the
+1/100s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#ug_vertical_gradient_level"><span style="font-weight: bold;">ug_vertical_gradient_level</span></a></td>
+
+
+      <td>I</td>
+
+ <td>R(10)</td>
+
+ <td><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+      <td>Height level from which on the
 gradient defined by <a href="chapter_4.1.html#ug_vertical_gradient">ug_vertical_gradient</a>
-is effective (in m).<br> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#ups_limit_e"><b>ups_limit_e</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Subgrid-scale
+is effective (in m).<br>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#ups_limit_e"><b>ups_limit_e</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <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> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#ups_limit_pt"><b>ups_limit_pt</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Temperature
+&nbsp;</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#ups_limit_pt"><b>ups_limit_pt</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Temperature
 difference used as criterion for
 applying&nbsp;
 the upstream scheme when upstream-spline advection&nbsp; is
 switched on
-(in K). <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#ups_limit_u"><b>ups_limit_u</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Velocity
+(in K). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#ups_limit_u"><b>ups_limit_u</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Velocity
 difference (u-component) used as criterion for
 applying the upstream scheme
-when upstream-spline advection is switched on (in m/s). <br> </p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#ups_limit_v"><b>ups_limit_v</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Velocity
+when upstream-spline advection is switched on (in m/s). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#ups_limit_v"><b>ups_limit_v</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Velocity
 difference (v-component) used as criterion for
 applying the upstream scheme
-when upstream-spline advection is switched on (in m/s). <br> </p>
-</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#ups_limit_w"><b>ups_limit_w</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Velocity
+when upstream-spline advection is switched on (in m/s). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#ups_limit_w"><b>ups_limit_w</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Velocity
 difference (w-component) used as criterion for
 applying the upstream scheme
-when upstream-spline advection is switched on (in m/s). <br> </p>
-</td> </tr> <tr> <td><a href="chapter_4.2.html#use_particle_tails"><span style="font-weight: bold;">use_particle_tails</span></a></td>
-<td>P</td> <td>L</td> <td>.F.</td>
-<td>Give particles a tail.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#use_prior_plot1d_parameters"><b>use_prior_plot1d</b></a>&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#use_prior_plot1d_parameters">&nbsp;<b>_parameters</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="width: 57%; text-align: left; vertical-align: middle;">
-<p>Additional plot of vertical profile data with <span style="font-weight: bold;">profil</span> from
+when upstream-spline advection is switched on (in m/s). <br>
+
+ </p>
+
+
+      </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.2.html#use_particle_tails"><span style="font-weight: bold;">use_particle_tails</span></a></td>
+
+
+      <td>P</td>
+
+ <td>L</td>
+
+ <td>.F.</td>
+
+
+      <td>Give particles a tail.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#use_prior_plot1d_parameters"><b>use_prior_plot1d</b></a>&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#use_prior_plot1d_parameters">&nbsp;<b>_parameters</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="width: 57%; text-align: left; vertical-align: middle;">
+      
+      <p>Additional plot of vertical profile data with <span style="font-weight: bold;">profil</span> from
 preceding runs of the
-job chain.&nbsp; </p> </td> </tr> <tr> <td align="undefined" valign="undefined"><a href="chapter_4.2.html#use_sgs_for_particles"><span style="font-weight: bold;">use_sgs_for_particles</span></a></td>
-<td align="undefined" valign="undefined">P</td>
-<td align="undefined" valign="undefined">L</td>
-<td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td> <td align="undefined" valign="undefined">Use
-subgrid-scale velocities for particle advection.</td> </tr>
-<tr> <td style="vertical-align: middle;" width="15%">
-<p><a href="chapter_4.1.html#use_surface_fluxes"><b>use_surface_fluxes</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.F.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
+job chain.&nbsp; </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td align="undefined" valign="undefined"><a href="chapter_4.2.html#use_sgs_for_particles"><span style="font-weight: bold;">use_sgs_for_particles</span></a></td>
+
+
+      <td align="undefined" valign="undefined">P</td>
+
+
+      <td align="undefined" valign="undefined">L</td>
+
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
+
+ <td align="undefined" valign="undefined">Use
+subgrid-scale velocities for particle advection.</td>
+
+ </tr>
+
+
+    <tr>
+
+ <td style="vertical-align: middle;" width="15%">
+      
+      <p><a href="chapter_4.1.html#use_surface_fluxes"><b>use_surface_fluxes</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.F.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
 to steer the treatment of the subgrid-scale
 vertical
-fluxes within the diffusion terms at k=1 (bottom boundary).</p> </td>
-</tr> <tr><td><a style="font-weight: bold;" href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a></td><td>I</td><td>L</td><td><span style="font-style: italic;">.F.</span></td><td>Parameter
+fluxes within the diffusion terms at k=1 (bottom boundary).</p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+      <td><a style="font-weight: bold;" href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a></td>
+
+      <td>I</td>
+
+      <td>L</td>
+
+      <td><span style="font-style: italic;">.F.</span></td>
+
+      <td>Parameter
 to steer the treatment of the subgrid-scale
 vertical
-fluxes within the diffusion terms at k=nz (top boundary).</td></tr><tr valign="top"> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#use_ug_for_galilei_tr"><b>use_ug_for_galilei_tr</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.T.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Switch
+fluxes within the diffusion terms at k=nz (top boundary).</td>
+
+    </tr>
+
+    <tr valign="top">
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#use_ug_for_galilei_tr"><b>use_ug_for_galilei_tr</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.T.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Switch
 to determine the translation velocity in case
 that a
-Galilean transformation is used.</p> </td> </tr> <tr>
-<td align="undefined" valign="undefined"><a href="chapter_4.1.html#use_upstream_for_tke"><span style="font-weight: bold;">use_upstream_for_tke</span></a></td>
-<td align="undefined" valign="undefined">I</td>
-<td align="undefined" valign="undefined">L</td>
-<td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td> <td align="undefined" valign="undefined">Parameter to
+Galilean transformation is used.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#use_upstream_for_tke"><span style="font-weight: bold;">use_upstream_for_tke</span></a></td>
+
+
+      <td align="undefined" valign="undefined">I</td>
+
+
+      <td align="undefined" valign="undefined">L</td>
+
+
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
+
+ <td align="undefined" valign="undefined">Parameter to
 choose the advection/timestep scheme to be used for the subgrid-scale
-TKE.</td> </tr> <tr> <td style="vertical-align: middle;"> <p><a href="chapter_4.2.html#vertical_particle_advection"><b>vertical_particle_advection</b></a><br>
-</p> </td> <td style="vertical-align: middle;">P<br>
-</td> <td style="vertical-align: middle;">L<br>
-</td> <td style="vertical-align: middle;"><i>.T.</i></td>
-<td style="vertical-align: middle;">Switch on/off
+TKE.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"> 
+      
+      <p><a href="chapter_4.2.html#vertical_particle_advection"><b>vertical_particle_advection</b></a><br>
+
+
+      </p>
+
+ </td>
+
+ <td style="vertical-align: middle;">P<br>
+
+
+      </td>
+
+ <td style="vertical-align: middle;">L<br>
+
+
+      </td>
+
+ <td style="vertical-align: middle;"><i>.T.</i></td>
+
+
+      <td style="vertical-align: middle;">Switch on/off
 vertical
-particle transport.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#vg_surface"><b>vg_surface</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>v-component
-of the geostrophic wind at the surface (in m/s).</p> </td>
-</tr> <tr> <td><a href="chapter_4.1.html#vg_vertical_gradient"><span style="font-weight: bold;">vg_vertical_gradient</span></a></td>
-<td>I</td> <td>R(10)</td> <td><span style="font-style: italic;">10 * 0.0</span></td>
-<td>Gradient(s) of the initial
+particle transport.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#vg_surface"><b>vg_surface</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>0.0</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>v-component
+of the geostrophic wind at the surface (in m/s).</p>
+
+ </td>
+
+
+    </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#vg_vertical_gradient"><span style="font-weight: bold;">vg_vertical_gradient</span></a></td>
+
+
+      <td>I</td>
+
+ <td>R(10)</td>
+
+ <td><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+      <td>Gradient(s) of the initial
 profile of the&nbsp; v-component of the geostrophic wind (in
-1/100s).</td> </tr> <tr> <td><a href="chapter_4.1.html#vg_vertical_gradient_level"><span style="font-weight: bold;">vg_vertical_gradient_level</span></a></td>
-<td>I</td> <td>R(10)</td> <td><span style="font-style: italic;">10 * 0.0</span></td>
-<td>Height level from which on the
+1/100s).</td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#vg_vertical_gradient_level"><span style="font-weight: bold;">vg_vertical_gradient_level</span></a></td>
+
+
+      <td>I</td>
+
+ <td>R(10)</td>
+
+ <td><span style="font-style: italic;">10 * 0.0</span></td>
+
+
+      <td>Height level from which on the
 gradient defined by <a href="chapter_4.1.html#vg_vertical_gradient">vg_vertical_gradient</a>
-is effective (in m).</td> </tr> <tr valign="top">
-<td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.1.html#wall_adjustment"><b>wall_adjustment</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>I</p> </td> <td style="vertical-align: middle;" width="7%"> <p>L</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>.T.</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Parameter
+is effective (in m).</td>
+
+ </tr>
+
+ <tr valign="top">
+
+
+      <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.1.html#wall_adjustment"><b>wall_adjustment</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>I</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>L</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>.T.</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Parameter
 to restrict the mixing length in the vicinity
 of the
 bottom
-boundary.</p> </td> </tr> <tr> <td><a href="chapter_4.1.html#wall_heatflux"><span style="font-weight: bold;">wall_heatflux</span></a></td>
-<td>I</td> <td>R(5)</td> <td><span style="font-style: italic;">5 * 0.0</span></td> <td>Prescribed
+boundary.</p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td><a href="chapter_4.1.html#wall_heatflux"><span style="font-weight: bold;">wall_heatflux</span></a></td>
+
+
+      <td>I</td>
+
+ <td>R(5)</td>
+
+ <td><span style="font-style: italic;">5 * 0.0</span></td>
+
+ <td>Prescribed
 kinematic sensible heat flux in W m<sup>-2</sup>&nbsp;at
-the five topography faces.</td> </tr> <tr> <td style="vertical-align: middle;"> <p><a href="chapter_4.2.html#write_particle_statistics"><b>write_particle_</b></a>
-<br> <a href="chapter_4.2.html#write_particle_statistics"><b>statistics</b></a>
-</p> </td> <td style="vertical-align: middle;">P<br>
-</td> <td style="vertical-align: middle;">L<br>
-</td> <td style="vertical-align: middle;"><i>.F.</i></td>
-<td style="vertical-align: middle;">Switch on/off
+the five topography faces.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;"> 
+      
+      <p><a href="chapter_4.2.html#write_particle_statistics"><b>write_particle_</b></a>
+      <br>
+
+ <a href="chapter_4.2.html#write_particle_statistics"><b>statistics</b></a>
+      </p>
+
+ </td>
+
+ <td style="vertical-align: middle;">P<br>
+
+
+      </td>
+
+ <td style="vertical-align: middle;">L<br>
+
+
+      </td>
+
+ <td style="vertical-align: middle;"><i>.F.</i></td>
+
+
+      <td style="vertical-align: middle;">Switch on/off
 output of
-particle informations.</td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#z_max_do1d"><b>z_max_do1d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%"><i>zu(nzt+1)
-(model top)</i></td> <td style="vertical-align: middle;" width="57%"> <p>Height level up to which horizontally
+particle informations.</td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#z_max_do1d"><b>z_max_do1d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%"><i>zu(nzt+1)
+(model top)</i></td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Height level up to which horizontally
 averaged profiles
 are to
@@ -1518,28 +8170,127 @@
 plotted with <span style="font-weight: bold;">profil</span>
 (in
-m). <br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#z_max_do1d_normalized"><b>z_max_do1d</b></a>&nbsp;&nbsp;
-<br> <a href="chapter_4.2.html#z_max_do1d_normalized">&nbsp;<b>_normalized</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>determined by plot <br>
-data</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Normalized
+m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#z_max_do1d_normalized"><b>z_max_do1d</b></a>&nbsp;&nbsp;
+      <br>
+
+ <a href="chapter_4.2.html#z_max_do1d_normalized">&nbsp;<b>_normalized</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>determined by plot <br>
+
+
+data</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Normalized
 height level up to which horizontally
 averaged
 profiles are to be plotted with <span style="font-weight: bold;">profil</span>.
-<br> </p> </td> </tr> <tr> <td style="vertical-align: middle;" width="15%"> <p><a href="chapter_4.2.html#z_max_do2d"><b>z_max_do2d</b></a></p>
-</td> <td style="vertical-align: middle;" width="5%">
-<p>R</p> </td> <td style="vertical-align: middle;" width="7%"> <p>R</p>
-</td> <td style="vertical-align: middle;" width="16%">
-<p><i>zu(nz)</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Height
+      <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ <tr>
+
+ <td style="vertical-align: middle;" width="15%"> 
+      
+      <p><a href="chapter_4.2.html#z_max_do2d"><b>z_max_do2d</b></a></p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="5%">
+      
+      <p>R</p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="7%"> 
+      
+      <p>R</p>
+
+
+      </td>
+
+ <td style="vertical-align: middle;" width="16%">
+      
+      <p><i>zu(nz)</i></p>
+
+ </td>
+
+ <td style="vertical-align: middle;" width="57%"> 
+      
+      <p>Height
 level up to which 2d cross sections are to be
 plotted
 with <span style="font-weight: bold;">iso2d</span>
-(in m). <br> </p> </td> </tr> </tbody>
-</table><hr>
-<p><br><font color="#000080"><a href="chapter_4.5.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_5.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></p>
+(in m). <br>
+
+ </p>
+
+ </td>
+
+ </tr>
+
+ 
+  
+  </tbody>
+</table>
+
+<hr>
+<p><br>
+
+<font color="#000080"><a href="chapter_4.5.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_5.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></p>
+
+
 <p>&nbsp;<i>Last change:&nbsp;&nbsp;</i>
 $Id$ </p>
-<p><br><br>
-<br></p>
-</body></html>
+
+
+<p><br>
+
+<br>
+
+
+<br>
+
+</p>
+
+
+</body>
+</html>
Index: palm/trunk/DOC/app/index.html
===================================================================
--- palm/trunk/DOC/app/index.html	(revision 103)
+++ palm/trunk/DOC/app/index.html	(revision 108)
@@ -1,10 +1,24 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml"><head>
+<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml">
+<head>
+
+  
   <meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
+
+  
   <meta content="Word.Document" name="ProgId">
+
+  
   <meta content="Microsoft Word 11" name="Generator">
+
+  
   <meta content="Microsoft Word 11" name="Originator">
+
+  
   <link href="index-Dateien/filelist.xml" rel="File-List">
-  <link href="index-Dateien/editdata.mso" rel="Edit-Time-Data"><!--[if !mso]>
+
+  
+  <link href="index-Dateien/editdata.mso" rel="Edit-Time-Data">
+<!--[if !mso]>
 <style>
 v\:* {behavior:url(#default#VML);}
@@ -13,5 +27,7 @@
 .shape {behavior:url(#default#VML);}
 </style>
-<![endif]--><title>PALM table of contents</title><!--[if gte mso 9]><xml>
+<![endif]-->
+  <title>PALM table of contents</title>
+<!--[if gte mso 9]><xml>
  <w:WordDocument>
   <w:SpellingState>Clean</w:SpellingState>
@@ -31,4 +47,5 @@
   
 
+  
   <style>
 <!--
@@ -104,8 +121,16 @@
 </style>
 <![endif]-->
+  
   <meta content="Marcus Oliver Letzel" name="AUTHOR">
+
+  
   <meta content="20041117;10075861" name="CREATED">
+
+  
   <meta content="20041119;12040014" name="CHANGED">
-  <meta content="parallel LES model" name="KEYWORDS"><!--[if gte mso 9]><xml>
+
+  
+  <meta content="parallel LES model" name="KEYWORDS">
+<!--[if gte mso 9]><xml>
  <u1:DocumentProperties>
   <u1:Author>pooluser</u1:Author>
@@ -136,85 +161,136 @@
 </xml><![endif]--><!--[if gte mso 9]><xml>
  <u3:LatentStyles DefLockedState="false" LatentStyleCount="156">  </u3:LatentStyles>
-</xml><![endif]--></head>
+</xml><![endif]-->
+</head>
+
 <body style="" lang="DE" link="blue" vlink="blue">
+
 <div class="Section1">
 <p style="margin-bottom: 0.0001pt;"><span style="font-size: 36pt; font-family: Thorndale;">PALM </span><span style="font-family: Thorndale;">a <span class="SpellE"><b>pa</b>rallelized</span>
 <b>L</b>ES <span class="SpellE"><b>m</b>odel</span>
 <o:p></o:p></span></p>
+
 <div style="text-align: center;" class="MsoNormal" align="center"><span style="font-family: Thorndale;">
 <hr align="center" size="2" width="100%"></span></div>
+
 <p><span style="font-family: Thorndale;" lang="EN-GB"><br>
+
 </span><span style="font-size: 18pt; font-family: Thorndale;" lang="EN-GB">Documentation </span><span style="font-family: Thorndale;" lang="EN-GB"><o:p></o:p></span></p>
+
 <p><span style="font-family: Thorndale;" lang="EN-GB">Current
 model
-version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.3<br>For date of last change see bottom line of each page. <o:p></o:p></span></p>
+version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.3<br>
+For date of last change see bottom line of each page. <o:p></o:p></span></p>
+
 <div style="text-align: center;" class="MsoNormal" align="center"><span style="font-family: Thorndale;">
 <hr align="center" size="2" width="100%"></span></div>
+
 <p><span style="font-size: 18pt; font-family: Thorndale;" lang="EN-GB">Table
 of contents</span><span style="font-family: Thorndale;" lang="EN-GB"> <br>
+
 &nbsp; <o:p></o:p></span></p>
+
 <p style="margin-left: 36pt;"><span style="font-family: Thorndale;"><a href="chapter_1.0.html"><span style="" lang="EN-GB">1.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Introduction <o:p></o:p></span></p>
+
 <p style="margin-left: 36pt;"><span style="font-family: Thorndale;"><a href="chapter_2.0.html"><span style="" lang="EN-GB">2.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Basic
 techniques of the LES model and its parallelization <o:p></o:p></span></p>
+
 <p style="margin: 5pt 0cm 0.0001pt 36pt;"><span style="font-family: Thorndale;"><a href="chapter_3.0.html"><span style="" lang="EN-GB">3.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Execution of
 model runs<o:p></o:p></span></p>
+
 <p style="margin: 0cm 0cm 0.0001pt 72pt;"><span style="font-family: Thorndale;"><a href="chapter_3.1.html"><span style="" lang="EN-GB">3.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Job control
 with <span class="SpellE"><b>mrun</b></span> <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.2.html"><span style="" lang="EN-GB">3.2</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Example of a
 minimum configuration file <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.3.html"><span style="" lang="EN-GB">3.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB">
 Initialization and restart runs <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.4.html"><span style="" lang="EN-GB">3.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Input and
 output files <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.5.html"><span style="" lang="EN-GB">3.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Programming
 of user-defined code extensions <o:p></o:p></span></p>
+
 <p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;"><a href="chapter_3.5.1.html"><span style="" lang="EN-GB">3.5.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Interfaces for
 user-defined&nbsp; code <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.5.2.html"><span style="" lang="EN-GB">3.5.2</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Definition of
 user-defined parameters <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.5.3.html"><span style="" lang="EN-GB">3.5.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Definition of
-<span class="SpellE">user-defined subdomains</span></span></p><p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;" lang="EN-GB"><span class="SpellE"></span> <a href="chapter_3.5.4.html">3.5.4</a> User-defined output quantities<br>
+<span class="SpellE">user-defined subdomains</span></span></p>
+<p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;" lang="EN-GB"><span class="SpellE"></span> <a href="chapter_3.5.4.html">3.5.4</a> User-defined output quantities<br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_3.5.5.html"><span style="" lang="EN-GB">3.5.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Compiling and linking
 user-defined code <o:p></o:p></span></p>
+
 <p style="margin: 0cm 0cm 5pt 72pt;"><span style="font-family: Thorndale;"><a href="chapter_3.6.html"><span style="" lang="EN-GB">3.6</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Interactive mode and
 debugging <br>
+
 </span><span style="font-family: Thorndale;"></span><span style="font-family: Thorndale;" lang="EN-GB"><a href="chapter_3.7.html">3.7</a> Optional
-software packages<o:p></o:p></span></p>
+software packages</span><span style="font-family: Thorndale;" lang="EN-GB"><br>
+
+</span><span style="font-family: Thorndale;"></span><span style="font-family: Thorndale;" lang="EN-GB"><a href="chapter_3.8.html">3.8</a> Coupled model runs</span></p>
+
 <p style="margin: 12pt 0cm 0.0001pt 36pt;"><span style="font-family: Thorndale;"><a href="chapter_4.0.html"><span style="" lang="EN-GB">4.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Steering
 parameters <o:p></o:p></span></p>
+
 <p style="margin: 0cm 0cm 0.0001pt 72pt;"><span style="font-family: Thorndale;"><a href="chapter_4.1.html"><span style="" lang="EN-GB">4.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB">
 Initialization parameters <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_4.2.html"><span style="" lang="EN-GB">4.2</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Runtime
 parameters and package parameters <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_4.3.html"><span style="" lang="EN-GB">4.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> User-defined
 parameters <br>
-</span><span style="font-family: Thorndale;"><a href="chapter_4.4.html"><span style="" lang="EN-GB">4.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Examples of parameter sets</span></p><div style="margin-left: 120px;">&nbsp; <a href="chapter_4.4.1.html">4.4.1</a> A minimum parameter set for the CBL<br>&nbsp; <a href="chapter_4.4.2.html">4.4.2</a> A parameter set for ocean runs</div><p style="margin: 0cm 0cm 0.0001pt 72pt;"><span style="font-family: Thorndale;" lang="EN-GB">
+
+</span><span style="font-family: Thorndale;"><a href="chapter_4.4.html"><span style="" lang="EN-GB">4.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Examples of parameter sets</span></p>
+<div style="margin-left: 120px;">&nbsp; <a href="chapter_4.4.1.html">4.4.1</a> A minimum parameter set for the CBL<br>
+&nbsp; <a href="chapter_4.4.2.html">4.4.2</a> A parameter set for ocean runs</div>
+<p style="margin: 0cm 0cm 0.0001pt 72pt;"><span style="font-family: Thorndale;" lang="EN-GB">
 </span><span style="font-family: Thorndale;"><a href="chapter_4.5.html"><span style="" lang="EN-GB">4.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Data analysis and
 visualization <o:p></o:p></span></p>
 
+
 <p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;"><a href="chapter_4.5.1.html"><span style="" lang="EN-GB">4.5.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> NetCDF data output<b></b><br>
+
 <a href="chapter_4.5.2.html">4.5.2</a> </span><span style="font-family: Thorndale;" lang="EN-GB">Plots of
 vertical profiles with <b>profil</b></span><br>
+
 <span style="font-family: Thorndale;"><a href="chapter_4.5.3.html"><span style="" lang="EN-GB">4.5.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of time
 series with <b>profil</b> <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_4.5.4.html"><span style="" lang="EN-GB">4.5.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of 2D
 cross sections with <b>iso2d</b> <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_4.5.5.html"><span style="" lang="EN-GB">4.5.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of 3D
 volume data with <b>AVS</b> <br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_4.5.6.html"><span style="" lang="EN-GB">4.5.6</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of
 compressed 3D volume data with <b>AVS</b><br>
+
 </span><span style="font-family: Thorndale;"><a href="chapter_4.5.7.html"><span style="" lang="EN-GB">4.5.7</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of <span class="SpellE">isosurfaces</span>, 2D cross sections and particles
 with <span class="SpellE"><b>dvrp</b></span><o:p></o:p></span></p>
+
 <p style="margin: 0cm 0cm 5pt 72pt;"><span style="font-family: Thorndale;"><a href="chapter_4.6.html"><span style="" lang="EN-GB">4.6</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Listing of the steering
 parameters in alphabetical&nbsp; order<o:p></o:p></span></p>
+
 <p style="margin: 12pt 0cm 0.0001pt 36pt;"><span style="font-family: Thorndale;"><a href="chapter_5.0.html"><span style="" lang="EN-GB">5.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Installation
 of the model <o:p></o:p></span></p>
+
 <p style="margin: 0cm 0cm 5.1pt 72pt;"><span style="font-family: Thorndale;"><a href="chapter_5.1.html">5.1</a>
 Installation of <span class="SpellE">new</span><span class="SpellE"></span> / other
-<span class="SpellE">versions, version update</span><o:p></o:p></span></p><font color="#000000">&nbsp;
+<span class="SpellE">versions, version update</span><o:p></o:p></span></p>
+<font color="#000000">&nbsp;
 <br>
+
 &nbsp;
 <span style="font-style: italic;">Last change:</span>
 $Id$<br>
+
 </font></div>
-</body></html>
+
+</body>
+</html>
