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>
