Changeset 48 for palm

palm/trunk/DOC/app/chapter_3.4.html

-                      r5
+                      r48
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<html><head>
 …
   <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+  <title>chapter_3.4</title>
+</head>
+  <title>chapter_3.4</title></head>
 <body>
 …
+    <tr>
+      <td style="vertical-align: top; text-align: center;">
+      <p align="center">50&nbsp; </p>
+      <p align="center">and/or&nbsp; <br>
+possibly&nbsp; </p>
+      <p align="center">50-59</p>
+      </td>
+      <td style="vertical-align: top;">
+      <p><a name="PLOTTS_DATA"></a>PLOTTS_DATA&nbsp; </p>
+      <p>and/or&nbsp; <br>
+possibly&nbsp; </p>
+      <p>PLOTTS_DATA_0&nbsp; <br>
+PLOTTS_DATA_1&nbsp; <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+PLOTTS_DATA_9</p>
+      </td>
+      <td style="vertical-align: top;">O</td>
+      <td style="vertical-align: top;">Ascii<br>
+      </td>
+      <td style="vertical-align: top;">
+      <p>This file contains the data of the time series written by the
+model (see <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>)
+in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
+The data can only be visualized with <span style="font-weight: bold;">profil</span>
+using NAMELIST parameter sets, which are written by
+the model to the local file <a href="#PLOTTS_PAR">PLOTTS_PAR</a>.&nbsp;
+      </p>
+      <p>Regardless of the (sub)set of time series specified by <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>
+for actual output, this file allways contains all possible time series.
+They are arranged next to each other in 22 columns. The
+first column contains the time in s. With initial runs the
+variables in the individual columns are described in the comment lines
+at the beginning of the file (see also <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>).
+The text of these comment lines is used as a legend in the plot. The
+first line of the file is a comment line in case of initial runs
+and contains information about the used model version, the run
+identifier (base file name + number of the respective restart run),
+the name of the executing computer, as well as the date and time of the
+beginning of the run. At the end of this comment line is the name of
+the
+subdomain, to which the time series belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
+By default, it is the &ldquo;total domain&rdquo;, i.e. the time series
+apply to the whole model domain. If the model has to produce profiles
+for subdomains, up to 9 further files (units No. 51-59) are
+produced. The file names include the number of the respective
+subdomain (e.g. PLOTTS_DATA_1). In this case the name of the file with
+the data of the total domain is PLOTTS_DATA_0.&nbsp; </p>
+      <p>Time series data of restart runs <b>must
+always</b> be attached to existing data of preceding runs of a job
+chain, because
+they do not contain comment lines (see above) and otherwise are not
+visualizable with <span style="font-weight: bold;">profil</span>. Time
+series plotted with <span style="font-weight: bold;">profil</span>
+therefore always begin with t=0. An appending of the data to one file
+is
+obtained with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
+in the file connection statement. <br>
+      </p>
+      </td>
+    </tr>
 …
+    <tr>
+      <td style="vertical-align: top; text-align: center;">90<br>
+      </td>
+      <td style="vertical-align: top;">
+      <p><a name="PLOTTS_PAR"></a>PLOTTS_PAR&nbsp; </p>
+      <p>and/or&nbsp; <br>
+possibly&nbsp; </p>
+      <p>PLOTTS_PAR_0&nbsp; <br>
+PLOTTS_PAR_1&nbsp; <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+PLOTTS_PAR_9</p>
+      </td>
+      <td style="vertical-align: top;">O<br>
+      </td>
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+NAMELIST</td>
+      <td style="vertical-align: top;">
+      <p>NAMELIST parameter set, with which the layout of a plot
+of the time series data in the local file <a href="#PLOTTS_DATA">PLOTTS_DATA</a>
+can be steered, if these data are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.&nbsp;
+      </p>
+      <p>This file contains the so-called RAHMEN (frame)- and
+CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
+needed by <span style="font-weight: bold;">profil</span>. These
+parameter sets (and thus all details of the layout) can be edited after
+the model run by the user. By
+default, all time series are drawn in different panels on one page. The
+grouping is model-internally fixed and can only be
+changed manually later. Only those time series specified by the
+parameter <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>
+are actually drawn.&nbsp; </p>
+      <p>The file PLOTTS_PAR is allways produced by the model at
+the beginning and at the end of a run, whereby at the end of the run
+the file produced at the beginning is overwritten. Any later file
+differs from the initial file by the fact that it additionally contains
+ranges of values for the axes of coordinates. If a model run crashes
+uncontrolled (e.g. run time error or CPU - time exceeded) a
+parameter file is still available and the (incomplete) time
+series can - contrary to the vertical profiles - nevertheless be
+plotted.&nbsp; </p>
+      <p>If the model is to produce time series for different
+subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
+further files are output , whereby the file name gets an additionally
+underline and the number of the respective subdomain is appended (e.g.
+PLOTTS_PAR_1). The name of the file with NAMELIST-parameters for the
+total domain in this case&nbsp; reads PLOTTS_PAR_0.&nbsp;&nbsp; <br>
+      </p>
+      </td>
+    </tr>
 …
 format</font></font></td>
       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the timeseries (see <a href="../app/chapter_4.2.html#data_output_ts">data_output_ts</a>)
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>)
 in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
 …
+</body>
+</html>
+</body></html>

palm/trunk/DOC/app/chapter_3.5.1.html

-                      r46
+                      r48
 user-defined subdomains for statistic analysis and output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>
 and <a href="chapter_3.5.3.html">chapter
 .5.3</a>).&nbsp; <br>
+.5.3</a>) and of additional time series quantities (see comment line example in the file).&nbsp; <br>
 CPU time for <tt><font style="font-size: 10pt;" size="2">user_init</font></tt>
 …
       <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_statistics"></a>user_statistics</font></font></tt></p>
+      </td>
+      <td width="862">
+      <p>Horizontal averages of vertical profiles of additional
+quantities (for example user variables) can be computed and written to
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_statistics"></a>user_statistics<br>( sr )</font></font></tt></p>
+      </td>
+      <td width="862">
+      <p>Horizontal
+averages of vertical profiles of user-defined
+quantities can be computed here. Also, additional time series
+quantities can be calculated. They have to be defined before in routine
+<a href="#user_init"><span style="font-family: Courier New,Courier,monospace;">user_init</span></a>. The routine is called once for each defined statistic region (see <a href="chapter_4.1.html#statistic_region">statistic_region</a>).</p><p></p><p>The routine contains some simple examples (as comment lines) in order to demonstrate how to use it.</p><p><br>Profiles have to be written to
 the array <tt><font style="font-size: 10pt;" size="2">sums</font></tt>.
 Please use profile numbers starting from 70 upward (thus e.g. <tt><font style="font-size: 10pt;" size="2">sums (&hellip;,
 ) =</font></tt><font style="font-size: 10pt;" size="2">&hellip;)</font>. These additional
 profiles
+are temporally averaged in <tt><font style="font-size: 10pt;" size="2">flow_statistics</font></tt>.
+If these profiles should be displayed with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>,
+further instructions in the user-defined software are necessary. For
+this, an understanding of the operating mode of the subroutine <tt><font style="font-size: 10pt;" size="2">plot_1d</font></tt>
+is required.</p>
+are temporally averaged in <tt><font style="font-size: 10pt;" size="2">flow_statistics</font></tt>.</p>
       </td>

palm/trunk/DOC/app/chapter_3.5.3.html

-                      r5
+                      r48
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=windows-1252">
+  <title>PALM chapter 3.5.3</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+<html><head>
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+  <title>PALM chapter 3.5.3</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
   <meta name="AUTHOR" content="Siegfried Raasch">
   <meta name="CREATED" content="20040802;14001660">
 …
                 @page { size: 21cm 29.7cm }
         -->
         </style>
+</head>
+        </style></head>
 <body dir="ltr" lang="en-US">
 <h3 style="line-height: 100%;">3.5.3 Definition of user-defined
 subdomains</h3>
+<p style="line-height: 100%;">By default, the values of the time
+series (saved in local file <a href="chapter_3.4.html#PLOTTS_DATA">PLOTTS_DATA</a>)
+and the horizontally averaged vertical profiles (saved in local files
+<p style="line-height: 100%;">By default, the values of the timeseries quantities and the horizontally averaged vertical profiles (saved in local files
 <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
 and <a href="chapter_3.4.html#LIST_PROFIL">LIST_PROFIL</a>)
 …
 series or profiles for different user-defined subdomains can be
 computed and plotted additionally. Steering in principle is done
+via the initialization parameter <a
+ href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
+via the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
 </p>
 <p style="line-height: 100%;">The exact definition of these subdomains
 has to be made by the user within the user-defined subroutine
 <tt><font style="font-size: 10pt;" size="2">init_user</font></tt>. The
+subdomains are defined with a mask array named <tt><font
+ style="font-size: 10pt;" size="2">rmask</font></tt>,
+subdomains are defined with a mask array named <tt><font style="font-size: 10pt;" size="2">rmask</font></tt>,
 which has to be given the value 1.0 for all horizontal grid points
 belonging to
 …
 declared as: </p>
 <ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
+ size="2">REAL :: rmask (nys-1:nyn+1,nxl-1,nxr+1,0:9) .</font></tt></p>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">REAL :: rmask (nys-1:nyn+1,nxl-1,nxr+1,0:9) .</font></tt></p>
 </ul>
 <p style="line-height: 100%;">The first two indices are the grid point
+indices in y and x-direction. With parallel model runs <tt><font
+ style="font-size: 10pt;" size="2">nxl</font></tt><font
+ style="font-size: 10pt;" size="2">,
+</font><tt><font style="font-size: 10pt;" size="2">nxr</font></tt><font
+ style="font-size: 10pt;" size="2">,
+</font><tt><font style="font-size: 10pt;" size="2">nys</font></tt><font
+ style="font-size: 10pt;" size="2">
+<font size="3">and</font> </font><tt><font style="font-size: 10pt;"
+ size="2">nyn</font></tt>
+indices in y and x-direction. With parallel model runs <tt><font style="font-size: 10pt;" size="2">nxl</font></tt><font style="font-size: 10pt;" size="2">,
+</font><tt><font style="font-size: 10pt;" size="2">nxr</font></tt><font style="font-size: 10pt;" size="2">,
+</font><tt><font style="font-size: 10pt;" size="2">nys</font></tt><font style="font-size: 10pt;" size="2">
+<font size="3">and</font> </font><tt><font style="font-size: 10pt;" size="2">nyn</font></tt>
 are the array bounds of the respective subdomain (don't confuse this
 with the user-defined subdomain!) on the
+respective processor. With runs on one processor <tt><font
+ style="font-size: 10pt;" size="2">nys</font></tt><font
+ style="font-size: 10pt;" size="2">
+= </font><tt><font style="font-size: 10pt;" size="2">nxl</font></tt><font
+ style="font-size: 10pt;" size="2">
+= 0</font> and <font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">nxr
+respective processor. With runs on one processor <tt><font style="font-size: 10pt;" size="2">nys</font></tt><font style="font-size: 10pt;" size="2">
+= </font><tt><font style="font-size: 10pt;" size="2">nxl</font></tt><font style="font-size: 10pt;" size="2">
+= 0</font> and <font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">nxr
 =</font> </font><a href="chapter_4.1.html#nx">nx</a>
+and <font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">nyn
+and <font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">nyn
 =</font></font> <a href="chapter_4.1.html#ny">ny</a>.
 The third index determines the user-defined subdomain. The total model
 …
 assumed).
 The second subdomain should be defined by all points outside of this
+domain. This may be obtained by the following lines of code in <tt><font
+ style="font-size: 10pt;" size="2">user_init</font></tt>:
+domain. This may be obtained by the following lines of code in <tt><font style="font-size: 10pt;" size="2">user_init</font></tt>:
 </p>
 <ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
+ size="2"><font face="Cumberland, monospace">USE
+grid_variables</font></font></tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">USE indices</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">USE statistics</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">.</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">.</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">.</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">disc_center_x = dx * (nx + 1)/2</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">disc_center_y = dy * (ny + 1)/2</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">disc_radius = 0.5 * disc_center_x</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">DO&nbsp; i = nxl-1, nxr+1</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp; x = i * dx</font></font></tt><br>
+  <tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y = j * dy</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+radial_distance = SQRT( ( x - disc_center_x )**2 + &amp;</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+( y - disc_center_y )**2 )</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp; &nbsp; &nbsp; IF ( radial_distance
+&gt; disc_radius )&nbsp; THEN</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,1) = 0.0</font></font></tt><font style="font-size: 10pt;"
+ size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,2) = 1.0</font></font></tt><font style="font-size: 10pt;"
+ size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ELSE</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,1) = 1.0</font></font></tt><font style="font-size: 10pt;"
+ size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,2) = 0.0</font></font></tt><font style="font-size: 10pt;"
+ size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDIF</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">&nbsp;&nbsp; ENDDO</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">ENDDO</font></font></tt></p>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">USE
+grid_variables</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">USE indices</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">USE statistics</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">disc_center_x = dx * (nx + 1)/2</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">disc_center_y = dy * (ny + 1)/2</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">disc_radius = 0.5 * disc_center_x</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">DO&nbsp; i = nxl-1, nxr+1</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp; x = i * dx</font></font></tt><br>
+  <tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; y = j * dy</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+radial_distance = SQRT( ( x - disc_center_x )**2 + &amp;</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+( y - disc_center_y )**2 )</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp; &nbsp; &nbsp; IF ( radial_distance
+&gt; disc_radius )&nbsp; THEN</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,1) = 0.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,2) = 1.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ELSE</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,1) = 1.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+rmask(j,i,2) = 0.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDIF</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp; ENDDO</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
+  </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">ENDDO</font></font></tt></p>
 </ul>
+<p style="line-height: 100%;">The module <span
+ style="font-family: monospace;">statistics</span> must be used,
+<p style="line-height: 100%;">The module <span style="font-family: monospace;">statistics</span> must be used,
 because it contains <span style="font-family: monospace;">rmask</span>
 and the modules <span style="font-family: monospace;">grid_variables</span>
 …
 if
 the user sets <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>
 &#8805; <i>1</i>. Beyond that, names for the user-defined subdomains can be
+&ge; <i>1</i>. Beyond that, names for the user-defined subdomains can be
 assigned
 via the initialization parameter <a href="chapter_4.3.html#region">region</a>.
 …
 the local files <a href="chapter_3.4.html#HEADER">HEADER</a>
 and <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
+within the user-defined subroutine <tt><font style="font-size: 10pt;"
+ size="2">user_header</font></tt>.
+within the user-defined subroutine <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>.
 <br>
 &nbsp; </p>
 <hr>
 <p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.5.2.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a
+ href="chapter_3.5.4.html"><font color="#000080"><img src="right.gif"
+ name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 15/04/05 (SR)</p>
+</body>
+</html>
+<font color="#000080"><font color="#000080"><a href="chapter_3.5.2.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.4.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 07/03/07 (SR)</p>
+</body></html>

palm/trunk/DOC/app/chapter_4.1.html

-                      r46
+                      r48
 data on the file for the different domains can be distinguished by a
 suffix which is appended to the quantity names. Suffix 0 means data for
+the total domain, suffix 1 means data for subdomain 1, etc.</p><p>In case of <span style="font-weight: bold;">data_output_format</span> = <span style="font-style: italic;">'profil'</span>, individual local files for profiles (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
+and time series (<a href="chapter_3.4.html#PLOTTS_DATA">PLOTTS_DATA</a>)
+are created for each subdomain. The individual subdomain files differ by their name (the
+the total domain, suffix 1 means data for subdomain 1, etc.</p><p>In case of <span style="font-weight: bold;">data_output_format</span> = <span style="font-style: italic;">'profil'</span>, individual local files for profiles (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)&nbsp;are created for each subdomain. The individual subdomain files differ by their name (the
 number of the respective subdomain is attached, e.g.
 PLOT1D_DATA_1). In this case the names of the files with the data of
 the total domain are PLOT1D_DATA_0 and PLOTTS_DATA_0. If no subdomains
 are declared (<b>statistic_regions</b> = <i>0</i>), the names
 PLOT1D_DATA and PLOTTS_DATA are used (this must be considered in the
+PLOT1D_DATA_1). In this case the name of the file with the data of
+the total domain is PLOT1D_DATA_0. If no subdomains
+are declared (<b>statistic_regions</b> = <i>0</i>), the name
+PLOT1D_DATA is used (this must be considered in the
 respective file connection statements of the <span style="font-weight: bold;">mrun</span> configuration file).</p>
 …
 scheme is actually used, can be output as a time series with respect to
 the
+three directions in space with run parameter <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>
+= <i>'splptx'</i>, <i>'splpty'</i>, <i>'splptz'</i>. The percentage
+three directions in space with run parameter (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>, the timeseries names in the NetCDF file are <i>'splptx'</i>, <i>'splpty'</i>, <i>'splptz'</i>). The percentage
 of gridpoints&nbsp; should stay below a certain limit, however, it is
 not possible to give

palm/trunk/DOC/app/chapter_4.2.html

-                      r46
+                      r48
 <!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
+<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> 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
+<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
 parameter defines the time interval length for temporally averaged data
 (vertical profiles, spectra, 2d cross-sections, 3d volume data). By
+default,&nbsp;data are not subject to temporal averaging. The interval
+length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>. 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
+default,&nbsp;data are not subject to temporal averaging. The
+interval
+length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
+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
 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 an averaging interval can not be completed at the end of a run, it
+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> 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>
+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>
 interval</a><br>
+</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
+</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
 this parameter is given a non-zero value, temporally
 averaged vertical profile data are output. By default, profile data
 data are not subject to temporal averaging. The interval length is
+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 is calculated
+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
+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 be called only at the last substep of multistep Runge-Kutta
+timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>) by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span> = <span style="font-style: italic;">.F.</span>.
+pressure (see <a href="#psolver">psolver</a>) can
+be called only at the last substep of multistep Runge-Kutta
+timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>)
+by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span>
+= <span style="font-style: italic;">.F.</span>.
 In many cases, this sufficiently reduces the divergence of the velocity
 field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this
 case and in case
+of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span> = <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
+allowed </span>time step according to CFL and diffusion-criterion
+dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">= dt_max * <b>cfl_factor</b>
+of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span>
+= <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,
+.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
+dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">=
+dt_max * <b>cfl_factor</b>
 in order to avoid stability problems which may arise in the vicinity of
+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 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 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
+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
 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 divergence
+= <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
+divergence
 significantly effects the accuracy of the model results.</span><a href="chapter_4.1.html#scalar_advec"><span lang="en-GB"></span></a><span lang="en-GB"> Possibly larger values may
 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 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 impose random perturbations to the horizontal
+velocity field.&nbsp; </p>
+      <p>With <b>create_disturbances</b> = <i>.T.,</i> random
+</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
+impose random perturbations to the horizontal
+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 these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
+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>
 and <a href="#disturbance_level_t">disturbance_level_t</a>,
 …
 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 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 developed
 (e.g.&nbsp; convection has started), further imposing of perturbations
+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
+developed
+(e.g.&nbsp; convection has started), further imposing of
+perturbations
 is not necessary and can be omitted (this does not hold for non-cyclic
 lateral boundaries!). This can be steered by assigning
 …
 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 normalization applied to the x-coordinate of vertical
+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 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>,
+<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>,
 parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
 the x-values of the data points can be normalized with respect to
 …
 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>).
 …
 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 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 respect
+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
+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 respect
+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 respect
+</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 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 respect
+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
+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
+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 respect
+</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 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>, then the
+</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>,
+then the
 x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
+and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>. Data
+and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>.
+Data
 of the further coordinate systems (if any are to be drawn) are not
 normalized.&nbsp; </p>
       <p>Using a normalization leaves all vertical profile data on
+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>
+unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the normalization is steered
+unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the
+normalization is steered
 by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a>
 which may be changed subsequently by the user in the parameter file
 …
 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 normalization applied to the y-coordinate of vertical
+</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 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>,
+<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>,
 parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
 the y-values of the data points can be normalized with respect to
 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 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 respect
+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
+respect
 to the boundary layer height
 (determined from the height where the heat flux achieves its minimum
+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 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;<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 '
+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
+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;<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><br>
 * <span style="font-family: monospace; font-style: italic;">' '</span></p>
+      </ul>
       <p>If plot output of vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
+* <span style="font-family: monospace; font-style: italic;">'
+'</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>.
 Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
 which describes the layout for a plot to be generated with the plot
+program <span style="font-weight: bold;">profil</span>. The parameter <b>cross_profiles</b>
+program <span style="font-weight: bold;">profil</span>.
+The parameter <b>cross_profiles</b>
 determines how many coordinate systems (panels) the plot contains and
 which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
 …
 names are described at parameter <a href="#data_output_pr">data_output_pr</a>).
 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 plot consists of two coordinate systems
+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
+plot consists of two coordinate systems
 (panels) with the first panel containing the profiles of the horizontal
+velocity components (<span style="font-style: italic;">'u'</span> and <span style="font-style: italic;">'v'</span>) of all output times (see <a href="#dt_dopr">dt_dopr</a>)
+velocity components (<span style="font-style: italic;">'u'</span>
+and <span style="font-style: italic;">'v'</span>)
+of all output times (see <a href="#dt_dopr">dt_dopr</a>)
 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, depends on
+</p> <p>Whether the coordinate systems are actually drawn,
+depends on
 whether data of the appropriate profiles were output during the run
 (profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>).
 For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>,
       <span style="font-style: italic;">'v'</span> was assigned, then
+For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned,
+then
 the plot only consists of one panel, since no profiles of the potential
 temperature were output. On the other hand, if profiles were assigned
 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_ts_uymax"></a><b>cross_ts_uymax</b></p>
+      </td>
+      <td style="vertical-align: top;">R(10)</td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">10 *&nbsp; </span><br>
+&nbsp; 999.999</td>
+      <td style="vertical-align: top;">
+      <p>Maximum of the range of y-axis values for coordinate systems
+of time series plots.&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 time series are output and plotted (see <a href="#data_output_ts">data_output_ts</a>),
+their range of values (which are to be presented at the y axis) is
+determined by the absolute maximum or minimum values these variables
+take within the time series. Singular extreme events can make the
+timeseries difficult to interpret. In order to solve for this problem,
+the range of values of the y-axis can be assigned manually with the
+parameters <b>cross_ts_uymax</b> and <a href="#cross_ts_uymin">cross_ts_uymin</a>.
+This can be done separately for each of the time series coordinate
+systems (panels). These panels are listed in the description of
+parameter <a href="#data_output_ts">data_output_ts</a>.
+If, for example, the user wants to limit the range of values of theta<sub>*</sub>,
+this may bbe done by <b>cross_ts_uymax</b>(4) = <i>5.0 </i>and <b>cross_ts_uymin</b>(4)
+= <i>- 5.0 </i>(theta* is by default presented in the 4th panel (see <a href="#data_output_ts">data_output_ts</a>).
+A one-sided limitation of the range of values may also be assigned.</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="cross_ts_uymin"></a><b>cross_ts_uymin</b></p>
+      </td>
+      <td style="vertical-align: top;">R (10)</td>
+      <td style="vertical-align: top;">
+      <p><i>10 *</i>&nbsp; <br>
+&nbsp; <i>999.999</i></p>
+      </td>
+      <td style="vertical-align: top;">
+      <p>Minimum of the range of y-axis values for coordinate systems
+of time series plot.&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>For details see <a href="#cross_ts_uymax">cross_ts_uymax</a>.</p>
+      </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
+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
 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>
+* <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
+<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 are possible (write &ldquo; in front of, similar to TeX), as
+well as super- and subscripts (use "&gt;" or "&lt;" in front of each
+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
+each
 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 parameter determines which type of cycle is applied in
+</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
 perturbation pressure (see <a href="#psolver">psolver</a>).
 It defines in which way it is switched between the fine and coarse
 grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b>
+may be assigned the values <i>'v'</i> or <i>'w'</i>). The
+may be assigned the values <i>'v'</i> or <i>'w'</i>).
+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 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> 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>, and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>, respectively.<br><br>The
+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>
+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>,
+and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
+respectively.<br><br>The
 filenames already suggest that all files have NetCDF format.
 Informations about the file content (kind of quantities, array
 dimensions and grid coordinates) are part of the self describing NetCDF
 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:<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 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 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;">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 <a href="chapter_4.1.html#moisture">moisture</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 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 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 <a href="chapter_4.1.html#moisture">moisture</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></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
+"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:<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
+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
+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;">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 <a href="chapter_4.1.html#moisture">moisture</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 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 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 <a href="chapter_4.1.html#moisture">moisture</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></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
 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
+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
 cross section data, this string must be appended after the cross
 section string). Cross section data can also be (additionally) averaged
 …
 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 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 time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
+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
+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, 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 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 the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>&nbsp;
+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,
+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
+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
+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 total model
+domain. In the two horizontal directions all grid points with 0 &lt;= i
+grid point.<br> </p> Cross sections extend through the
+total model
+domain. In the two horizontal directions all grid points with 0
+&lt;= i
 &lt;= nx+1 and 0 &lt;= j
+&lt;= ny+1 are output so that in case of cyclic boundary conditions the
+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> 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
+&lt;= ny+1 are output so that in case of cyclic boundary conditions
+the
+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>
+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
 the standard quantities from the above list, the user can output any
 other quantities. These have to be defined and calculated within the
+user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>). They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a> for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
+user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>).
+They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>
+for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
 Output of the user defined quantities (time interval, averaging,
 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
 are
 constructed by appending the four digit processor ID, e.g.
+&lt;filename&gt;_0000, &lt;filename&gt;_0001, etc.). After PALM has
+&lt;filename&gt;_0000, &lt;filename&gt;_0001, etc.).
+After PALM has
 finished, the contents of these individual
+files are sampled into one final file<span style="font-weight: bold;"></span> using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
+files are sampled into one final file<span style="font-weight: bold;"></span>
+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 collect all grid points of a
+cross section on PE0 before output is done. In this case only one&nbsp;
+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
+one&nbsp;
 output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
+does not have to be called. In case of very large numbers of horizontal gridpoints, sufficient
+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 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
+the NetCDF format,&nbsp;2d cross section data and 3d volume data can
+does not have to be called. In case of very large numbers of horizontal
+gridpoints, sufficient
+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
+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
+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 assigning <span style="font-weight: bold;">data_output_format </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>.
+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>,
+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
 the plot software <span style="font-weight: bold;">AVS</span>.&nbsp;
 The order of data on the file follows the order used in the assignment
 for <b>data_output</b> (e.g. <b>data_output</b> = <span style="font-style: italic;">'p'</span>,
       <span style="font-style: italic;">'v'</span>,...&nbsp;
+for <b>data_output</b> (e.g. <b>data_output</b>
+= <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,...&nbsp;
 means that the file starts with the pressure data, followed by the
 v-component of the velocity, etc.). Both instantaneous and time
 …
 PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
 configuration file: &ldquo;<span style="font-family: monospace;">cat
+PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>&rdquo;) after PALM has
+finished.&nbsp;To reduce the amount of data, output to this file can be done
+PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>&rdquo;)
+after PALM has
+finished.&nbsp;To reduce the amount of data, output to this file
+can be done
 in
+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
+.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>.
+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
+.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
 the plot software&nbsp;<span style="font-weight: bold;">iso2d</span>.&nbsp;
 The order of data on the files follows the order used in the assignment
 for <b>data_output</b> (e.g. <b>data_output</b> = <span style="font-style: italic;">'p_xy'</span>,
       <span style="font-style: italic;">'v_xy_av'</span>,...&nbsp;
+for <b>data_output</b> (e.g. <b>data_output</b>
+= <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,...&nbsp;
 means that the file containing the horizontal cross section data starts
 with the instantaneous pressure data, followed by the
 …
 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
 …
 suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span>
 configuration file, e.g.: &ldquo;<span style="font-family: monospace;">cat
+PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</span>&rdquo;) after PALM has
+finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the respective data and
+PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</span>&rdquo;)
+after PALM has
+finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the
+respective data and
 parameter file. The plot layout is steered via the parameter input
 file.
 …
 (exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>).
 All parameter values can be changed by editing the parameter input
+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
+.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 default, all data (profiles, time
+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
+.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
+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 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 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 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 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 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 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> 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 * 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 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 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
+profiles always <span style="font-weight: bold;">all</span> vertical
+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
+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
+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
+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
+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
+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
+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>
+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 *
+&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
+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
+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
+profiles always <span style="font-weight: bold;">all</span>
+vertical
 grid points (0 &lt;= k &lt;= nz+1) are output to file. Vertical
 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 profiles is
+</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 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 assigned to <span style="font-weight: bold;">data_output_pr</span>.
+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
+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
+assigned to <span style="font-weight: bold;">data_output_pr</span>.
 The profile data is either defined on
+u-v-levels (variables marked in <font color="#ff6600">red</font>) or
+on w-levels (<font color="#33ff33">green</font>). According to this,
+u-v-levels (variables marked in <font color="#ff6600">red</font>)
+or
+on w-levels (<font color="#33ff33">green</font>).
+According to this,
 the
 z-coordinates of the individual profiles vary. Beyond that, with a
 Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>)
 the lowest output
+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 style="vertical-align: middle;"><font color="#ff6600">s</font></td>
+            <td style="vertical-align: top;">Scalar concentration (in
+kg/m<sup>3</sup>).</td>
+          </tr>
+          <tr>
+            <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
+            <td style="vertical-align: top;">Turbulent kinetic energy
+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 style="vertical-align: middle;"><font color="#ff6600">s</font></td>
+<td style="vertical-align: top;">Scalar concentration (in
+kg/m<sup>3</sup>).</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
+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
+</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
 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
+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 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
+</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
+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 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 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
++ <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
+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
 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>)</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>)</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 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 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 w-velocity
+</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
+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
+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 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
+</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
 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>
+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
 output (this output is only done once
 …
 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 the user or
+have been calculated by a 1d-model prerun.<br>
+      </p>In case of ASCII data output to local file PLOT1D_DATA,
+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
+the user or
+have been calculated by a 1d-model prerun.<br> </p>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>)
 which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>.
 …
 using these two files. The
 plot layout is
+steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters are determined by
+steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters
+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 profiles with <span style="font-weight: bold;">profil </span>can be found in <a href="chapter_4.5.2.html">chapter
+.5.2</a></td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="data_output_ts"></a><b>data_output_ts</b></p>
+      </td>
+      <td style="vertical-align: top;">C * 10 (100)<br>
+      </td>
+      <td style="vertical-align: top;"><i>100 * ' '</i></td>
+      <td style="vertical-align: top;">Quantities for which time series
+are to be output (plot).&nbsp; <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>. 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 historical reasons, data can also be output in ASCII-format on local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOTTS_DATA</a> which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a> for defining the format in which data shall be output.<br>
+      </p>
+Time series of different quantities can be output by assigning <b>data_output_ts</b>
+one or more of the following strings:<br>&nbsp;<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 kinetic
+energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup> </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 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 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
+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 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 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 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 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 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
+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
+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
+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
+(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
+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
+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
+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>
+Always <b>all</b> time series available are output to the file,
+regardless of the value of <span style="font-weight: bold;">data_output_ts</span>.
+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>.<br><br>The temporal interval of the data points of the time series is assigned via the parameter <a href="#dt_dots">dt_dots</a>.<br>
+      <p>In case of <span style="font-weight: bold;">data_output_format</span> = <span style="font-style: italic;">'profil'</span>, the data of the individual time series are output in columns
+to file  <a href="chapter_3.4.html#PLOT1D_DATA">PLOTTS_DATA</a>
+starting from the second column (the simulated time is output as the
+first column).&nbsp;Their sequence (with respect to the columns)
+corresponds to the list given above. Additional to the file
+PLOTTS_DATA, which contains the data,
+PALM creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOTTS_PAR">PLOTTS_PAR</a>)
+which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>.
+Time series can be directly plotted with <span style="font-weight: bold;">profil</span> using these two files. The
+plot layout is
+steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters are determined by
+a set of PALM-internal parameters. All
+parameter values can be changed by editing the parameter input file.<b> </b>In this case (<span style="font-weight: bold;">data_output_format</span> = <span style="font-style: italic;">'profil'</span>)<b> data_output_ts</b>
+determines which time series are actually to be plotted. They are
+plotted
+into individual coordinate systems (panels). Typically several time
+series are plotted
+together into one panel. The grouping is fixed PALM-internally (it can
+be changed by editing the parameter input file). The time series are
+assigned to the panels
+as: <br>
+      </p>
+      <ul>
+<p>panel 1:&nbsp; <i>E E *</i>&nbsp; <br>
+panel 2:&nbsp; <i>dt</i> <br>
+panel 3:&nbsp; <i>u* w*</i>&nbsp; <br>
+panel 4:&nbsp; <i>th*</i>&nbsp; <br>
+panel 5:&nbsp; <i>umax vmax wmax</i> <br>
+panel 6:&nbsp; <i>div_old div_new</i> <br>
+panel 7:&nbsp; <i>z_i_wpt z_i_pt</i> <br>
+panel 8:&nbsp; <i>w"pt"0 w"pt"wpt</i> <br>
+panel 9:&nbsp; <i>pt(0) pt(zp)</i> <br>
+panel 10: <i>splptx splpty splptz</i><br>
+panel 11: <i>L</i></p>
+      </ul>
+      <p>The range of values (y-axes) which are to be plotted can be
+assigned to each panel with the parameters <a href="chapter_4.2.html#cross_ts_uymin">cross_ts_uymin</a>
+and <a href="chapter_4.2.html#cross_ts_uymax">cross_ts_uymax</a>.
+If not a single time series of a panel is assigned by <span style="font-weight: bold;">data_output_ts</span>,
+then this panel is completely omitted in the plot.<br>
+      </p>
+      <p>Further details about plotting time series with <span style="font-weight: bold;">profil </span>can be found in <a href="chapter_4.5.3.html">chapter
+.5.3</a>.</p>
+      </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 default, each processor
+outputs cross section data of its subdomain&nbsp;into an individual file. After PALM
+has finished, the contents of these files have to be sampled into one file<span style="font-weight: bold;"></span> using
+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
+.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
+default, each processor
+outputs cross section data of its subdomain&nbsp;into an individual
+file. After PALM
+has finished, the contents of these files have to be sampled into one
+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> = <i>.F.,</i>
+<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
+into one file, so <tt>combine_plot_fields.x</tt> does not have to be
+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 perturbation amplitude of the random perturbations
+into one file, so <tt>combine_plot_fields.x</tt> does not
+have to be
+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
+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 limit value of the perturbation energy of
+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
+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"> describes how to impose
+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">
+describes how to impose
 random perturbations to the horizontal velocity field. The perturbation
 energy is defined as the volume average (over the total model domain)
 …
 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)</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)</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
+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
 parameter must hold the condition zu<i>(3)</i> &lt;= <b>disturbance_level_b</b>
+&lt;= <i>zu(</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">. 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. <br>
+      </font></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)</i></td>
+      <td style="vertical-align: top;">
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
+&lt;= <i>zu(</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">.
+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. <br> </font></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)</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
+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">. 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.<br>
+      </font></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="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>
+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
+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">.
+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.<br> </font></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="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>
 and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>.
+By assigning <b>do2d_at_begin</b> = <i>.T.</i> an additional output
+By assigning <b>do2d_at_begin</b> = <i>.T.</i>
+an additional output
 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 at the beginning
+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>)
+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
+d 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>.
+By assigning <b>do3d_at_begin</b> = <i>.T.</i> an additional output
+By assigning <b>do3d_at_begin</b> = <i>.T.</i>
+an additional output
 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 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 of 3d volume data may need huge amounts of disc storage
+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
+of 3d volume data may need huge amounts of disc storage
 (up to several Terabytes ore more). Data compression can serve to
 reduce this requirement. PALM is able to output 3d data in compressed
 form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span>
+= <span style="font-style: italic;">.T.</span> is assigned. This
+= <span style="font-style: italic;">.T.</span> is
+assigned. This
 yields a loss of accuracy, but the file size is clearly reduced. The
 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 output is only possible for Cray-T3E
+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
+.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;<a href="chapter_4.2.html#data_output_format">data_output_format</a> = <span style="font-style: italic;">'avs'</span>.</p><p>In case that data compression is used for output of 3d data
+.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 *
+&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;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
+= <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 clearly reduce the amount
+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
+quantity via a character string of the form <span style="font-style: italic;">'&lt;quantity name&gt;&lt;number of
+quantity via a character string of the form <span style="font-style: italic;">'&lt;quantity
+name&gt;&lt;number of
 significant digits&gt;'</span>, e.g. <span style="font-style: italic;">'pt2'</span>.
 Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a>
 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
+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 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">). Additionally, it may be
+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
+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">).
+Additionally, it may be
 used as a run parameter and then applies to all restart runs (until it
 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 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> &gt; <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"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
+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
+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>
+&gt; <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"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
 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 variable time step (see <span style="font-weight: bold;">dt</span>), the number of time levels entering the average can vary from one
+averaging interval to the next (for a more detailed explanation see </span></font><font><a href="#averaging_interval"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval</font></span></a>)</font><font face="Thorndale, serif"><span lang="en-GB">. It 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 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 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>,
+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
+averaging interval to the next (for a more detailed explanation see </span></font><font><a href="#averaging_interval"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval</font></span></a>)</font><font face="Thorndale, serif"><span lang="en-GB">. It
+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
+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
+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>,
 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 is allowed
+to change <b>dt_averaging_input</b> during a job chain. If the last averaging
+(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
+the last averaging
 interval of the run previous to the change could not be completed (i.e.
 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 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 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 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> &gt; <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"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
+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
+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
+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>
+&gt; <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"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
 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_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),
+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_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 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
+<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
 assign the temporal interval at which these data shall be
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>, which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of the simulation, i.e. output
+takes place at times t = <b>skip_time_data_output + dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span> + 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span> + 3*<b>dt_data_output</b>,
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
+simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>,
+which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
+time is the beginning of the simulation, i.e. output
+takes place at times t = <b>skip_time_data_output +
+dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
++ 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
++ 3*<b>dt_data_output</b>,
 etc. Since output is only done at the discrete time levels given by
+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 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>
+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
+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>
 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 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
+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
 assign the temporal interval at which they shall be
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>, which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of the simulation, i.e. output
+takes place at times t = <b>skip_time_data_output_av + dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span> + 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span> + 3*<b>dt_data_output_av</b>,
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
+simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>,
+which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
+time is the beginning of the simulation, i.e. output
+takes place at times t = <b>skip_time_data_output_av +
+dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
++ 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
++ 3*<b>dt_data_output_av</b>,
 etc. Since output is only done at the discrete time levels given by
+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 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 interval</font> at which random
+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
+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
+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"> 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 interval at
+(</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">
+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
+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
+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
+assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning
+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
+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
+assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> </font></span><span lang="en-GB"><font face="Thorndale">Output can
+be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has
+zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
+time is the beginning
 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> + 3*<b>dt_dopr</b>,
+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>
++ 3*<b>dt_dopr</b>,
 etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
 profiles can not be calculated for times lying within a time step
 …
 If a time step ranges from t = 1799.8 to t = 1800.2, then in the
 example above the output would take place at t = 1800.2. In general,
+the output always lie between t = 1800.0 and t = 1800.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 the model uses a variable time step, these
+the output always lie between t = 1800.0 and t = 1800.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 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 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>
+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>
 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
+= <i>900.0</i><span style="font-style: italic;">
+</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
+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
+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
+&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
+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
+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
 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 time is the beginning
+of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b> = 1800.0,
+assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
+time is the beginning
+of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b>
+= 1800.0,
 then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since
 profiles can not be calculated for times lying within a time step
 …
 If a time step ranges from t = 1799.8 to t = 1800.2, then in the
 example above the output would take place at t = 1800.2. In general,
 the output always lie between t = 1800.0 and t = 1800.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">(numbers are related to
+the output always lie between t = 1800.0 and t = 1800.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">(numbers
+are related to
 the
 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 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>
+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>
 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
+= <i>900.0</i><span style="font-style: italic;">
+</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 variable time steps are used
+&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
+variable time steps are used
 (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 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 internally fixed. In this file
+<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
+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 interval</font> at which&nbsp;time series data shall be output (</font>in <font face="Thorndale">s).&nbsp;
+      </font> </p>
+      <p><span lang="en-GB"><font face="Thorndale">If output of time
+series is switched on (see </font></span><a href="#data_output_ts"><span lang="en-GB"><font face="Thorndale">data_output_ts</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
+assign the temporal interval at which data points shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
+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
+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;
+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> =
+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
+assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
+time is the beginning of
 &nbsp;the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
+*<b>dt_dots</b>, 3*<b>dt_dots</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">).&nbsp; Is <b>dt_dots</b> &lt; </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">, then data of the time series are
+*<b>dt_dots</b>, 3*<b>dt_dots</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">).&nbsp;
+Is <b>dt_dots</b> &lt; </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">, then data
+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 value of <span style="font-weight: bold;">dt_dots</span> 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> = 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).</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
+= <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;
+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> =
+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
+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
+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
+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
+kinetic
+energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
+</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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+(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
+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
+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
+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
+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
+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
+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
 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 parameter can be used to
+<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
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference 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> + 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span> + 3*<b>dt_do2d_xy</b>,
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
+simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>,
+which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
+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>
++ 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>
 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
+</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 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
+</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
 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 be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
+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> + 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
+cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
+be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which
+has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
+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>
++ 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>
 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
+</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 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
+</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
 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 be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
+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> + 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 times
+cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
+be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which
+has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
+time is the beginning of
+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>
++ 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
+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>
 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
+</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 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 output of
+d-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 to assign
+</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
+output of
+d-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
+to assign
 th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
+interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the
+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> + 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
+interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
+be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has
+zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
+time is the
+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>
++ 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>
 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
+</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;">
+      <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 description
+</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
+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 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
+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
+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
+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
+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
 with information about the size of the time step, maximum speeds, total
 kinetic energy etc. is written to this file. Reference time is the
 beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>,
+*<b>dt_run_control</b>, 3*<b>dt_run_control</b>, etc., and always at
+*<b>dt_run_control</b>, 3*<b>dt_run_control</b>,
+etc., and always at
 the beginning of a model run (thus at the time t = 0 or at the
 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
+model (</font>in <font face="Thorndale">s).&nbsp; </font> </p>
+      <p><span lang="en-GB"><font face="Thorndale">The simulation time
+= <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
 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 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 parameters in use are
+</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
+parameters in use are
 output to the beginning of file RUN_CONTROL for initial runs only
 (these informations are identical to that which are output to the local
 file <a href="chapter_3.4.html#HEADER">HEADER</a>).
+With <b>force_print_header</b> = <i>.T.</i>, these informations are
+With <b>force_print_header</b> = <i>.T.</i>,
+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>- 1</i>), the number of cycles
+</p> <br>
+By default (<b>mg_cyles</b> = <i>- 1</i>), the
+number of cycles
 depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>)
 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>
 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 must
+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
+must
 examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
 regularly to check whether the divergence of the velocity field is
 …
 least by two orders of magnitude. For cyclic boundary conditions along
 both horizontal 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>) <span style="font-weight: bold;">mg_cycles</span> = <span style="font-style: italic;">2</span> is typically a good choice, for
+and <a href="chapter_4.1.html#bc_ns">bc_ns</a>) <span style="font-weight: bold;">mg_cycles</span> = <span style="font-style: italic;">2</span> is typically a
+good choice, for
 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>
+= <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>
 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>),
 …
 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 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 (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 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>
+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
+(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
+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>
 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>),
 …
 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 subdomain from which the normalization
+quantities are calculated.&nbsp; </p>
+      <p>If output data of the horizontally averaged vertical profiles
+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
+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>
+= <i>0</i>) and are thus representative for the total domain. Instead
+= <i>0</i>) and are thus representative for the total
+domain. Instead
 of that, normalization quantities can also be calculated for a
+subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>, where <i>1</i>
+&lt;= <b>normalizing_region</b> &lt;= <i>9 </i>must hold. These
+subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>,
+where <i>1</i>
+&lt;= <b>normalizing_region</b> &lt;= <i>9 </i>must
+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 parameter is only effective if the SOR-scheme is selected
+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>
+= <span style="font-style: italic;">'sor'</span>). The number of
+= <span style="font-style: italic;">'sor'</span>).
+The number of
 iterations necessary for a sufficient convergence of the scheme depends
 on the grid point numbers and is to be determined by appropriate test
 …
 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 default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
+</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
 (e.g. in order to reduce the amount of output data). It affects all
+output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output 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 the SOR-scheme is selected (<a href="#psolver">psolver</a>
+= <span style="font-style: italic;">'sor'</span>), this parameter
+determines the value of the convergence factor, where <i>1.0</i> &lt;=
+      <b>omega_sor</b> &lt; <i>2.0 </i>. The optimum value of <b>omega_sor</b>
+output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output
+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
+the SOR-scheme is selected (<a href="#psolver">psolver</a>
+= <span style="font-style: italic;">'sor'</span>),
+this parameter
+determines the value of the convergence factor, where <i>1.0</i>
+&lt;= <b>omega_sor</b> &lt; <i>2.0 </i>.
+The optimum value of <b>omega_sor</b>
 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 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>),
+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>),
 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;">
+      <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 determines the layout of plots of
+/ K<sub>h</sub>).</p> </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
+determines the layout of plots of
 horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
 when plotted with the plot software <span style="font-weight: bold;">profil</span>.
 Generally, the number and sequence of coordinate systems (panels) to be
 plotted on one page are
+determined by <a href="#cross_profiles">cross_profiles</a>. <b>profile_columns</b>
+determined by <a href="#cross_profiles">cross_profiles</a>.
+<b>profile_columns</b>
 determines how many panels are to be
 arranged next to each other in one row (number of columns). The
 …
 According to their order given by <a href="#data_output_pr">data_output_pr</a>,
 the panels are arranged beginning in the top row from left to right and
+then continued in the following row. If the number of panels cranz &gt;
+      <b>profile_columns</b> * <b>profile_rows</b>, the remaining
+then continued in the following row. If the number of panels cranz
+&gt; <b>profile_columns</b> * <b>profile_rows</b>,
+the remaining
 panels are drawn on an additional page. If cranz &lt; <b>profile_columns</b>,
+then <b>profile_columns</b> = cranz is automatically set. If
+then <b>profile_columns</b> = cranz is automatically set.
+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 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 determines the layout of plots of horizontally averaged
+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
+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 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
+</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
 along x and y, solution of a
 tridiagonal matrix along z, and backward
 …
 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 method using FFT
+</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
 tridiagonal matrix along z, and backward
 …
 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 scheme (see Uhlenbrock, diploma thesis). v-
+</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
 w-cycles (see <a href="#cycle_mg">cycle_mg</a>)
 …
 and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>)
 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>
+can be given via <a href="#residual_limit">residual_limit</a>.
+<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>
+<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 the number of
+multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
+the number of
 grid points in the three directions
 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
+where <i>n</i> &gt;= 5 must hold. With large <i>n,
+</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
 …
 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 points of
+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
 …
 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 relaxation
+</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>
+and <a href="chapter_4.1.html#nsor">nsor</a>.&nbsp; <br>
+Compared to the direct method and the multi-grid method, this scheme
+<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
+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>
+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 so-called Rayleigh damping is applied to all prognostic
+</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;
 If switched on, variables are forced towards the value of their
 …
 is assigned to.
 The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a>
+and rises according to a sin<sup>2</sup>-function to its maximum value
+and rises according to a sin<sup>2</sup>-function to its
+maximum value
 at
+the top boundary. </p>
+      <p>This method
+the top 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
 …
 or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>).
 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 hold the condition <i>0.0</i>
+= <i>0.01</i>) by default. Otherwise it remains switched
+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;">
+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 Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
+</td> <td style="vertical-align: top;"> <p>Height
+where 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
 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 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 multi-grid
+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
+multi-grid
 scheme (see <a href="#psolver">psolver</a>).
 The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>)
+is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If this
+is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If
+this
 is not the case after 1000 cycles, the PALM aborts with a corresponding
 error message.</p>
       <p>The reciprocal value of this parameter can be interpreted as
+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 after which a restart run is to be carried out
+(in s). </p>
+      <p>The simulated time refers to the beginning 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
+after which a restart run is to be carried out
+(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</a>).<br>
+      </p>
+      <p>The choice of <b>restart_time</b> or <b>dt_restart</b> does
+.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 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 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 parameter can be used to
+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
+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
+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
+parameter can be used to
 define the position(s) of the cross section(s). Up to 100 positions of
 cross sections can be selected by assigning <b>section_xy</b>
 …
 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>
+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>
+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>
 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 if several cross sections are selected (e.g. <b>section_xy</b>
+= <i>1</i>, <i>10</i>, <i>15</i>), then the respective data are
+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
+if several cross sections are selected (e.g. <b>section_xy</b>
+= <i>1</i>, <i>10</i>, <i>15</i>),
+then the respective data are
 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) 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
+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
+</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
+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
 define the position(s) of the cross section(s). Up to 100 positions of
+cross sections can be selected by assigning <b>section_xz</b> the
+cross sections can be selected by assigning <b>section_xz</b>
+the
 corresponding horizontal grid point index/indices j of the requested
 cross section(s). The exact position (in y-direction) of the cross
+section is given by j*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a> <span lang="en-GB"><font face="Thorndale">or (j-0.5)*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a><span lang="en-GB"><font face="Thorndale">, depending on which grid the output quantity is defined. However, in the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the 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>
+section is given by j*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a> <span lang="en-GB"><font face="Thorndale">or (j-0.5)*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a><span lang="en-GB"><font face="Thorndale">, depending
+on which grid the output quantity is defined. However, in
+the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
+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>
 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
+selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>, <i>27</i>),
+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>),
 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) 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
+</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
 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
 section(s). Up to 100 positions of cross sections can be selected by
+assigning <b>section_yz</b> the corresponding horizontal grid point
+assigning <b>section_yz</b> the corresponding horizontal
+grid point
 index/indices i of the requested cross section(s). The exact position
+(in x-direction) of the cross section is given by i*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a>
+      <span lang="en-GB"><font face="Thorndale">or (i-0.5)*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a><span lang="en-GB"><font face="Thorndale">, depending on which grid the output quantity is defined.&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">However, in the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the 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>
+(in x-direction) of the cross section is given by i*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a> <span lang="en-GB"><font face="Thorndale">or (i-0.5)*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a><span lang="en-GB"><font face="Thorndale">, depending
+on which grid the output quantity is defined.&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">However, in
+the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
+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>
 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
+selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>,
+      <span style="font-style: italic;">27</span>, 19), then 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
+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
+parameter causes that data output activities are starting not before this interval
+(counting from the beginning of the simulation, t=0) has passed. By default, 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
+(counting from the beginning of the simulation, t=0) has passed. By
+default, this
 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 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
+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 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
+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 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 instantaneous horizontal cross section 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 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 instantaneous vertical (xz) cross section 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 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 instantaneous vertical (yz) cross section 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 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
+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 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 needed for terminal actions at the end of a run in
+batch mode (in s).<br>
+      </p>
+      <p>If the environment variable <b>write_binary </b>is
+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
+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
+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
+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
+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
+instantaneous horizontal cross section 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
+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
+instantaneous vertical (xz) cross section 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
+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
+instantaneous vertical (yz) cross section 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
+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
+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
+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
+needed for terminal actions at the end of a run in
+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
+.3</a>), PALM checks the remaining CPU time of the job after each
+.3</a>), PALM checks the remaining CPU time of the job after
+each
 timestep. Time integration must not consume the CPU time completely,
 since several actions still have to be carried out after time
 …
 permanent destinations, etc.) which also takes some time. The maximum
 possible time needed for these activities plus a reserve is to be given
+with the parameter <b>termination_time_needed</b>. Among other things,
+with the parameter <b>termination_time_needed</b>. Among
+other things,
 it depends on
 the number of grid points used. If its value is selected too small,
 …
 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 variable <span style="font-weight: bold;">write_binary</span> is not set to <span style="font-style: italic;">true</span> and if moreover the job has
+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>
+On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of PALM
+</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>
+and if moreover the job has
+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>
+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 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 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 default, plots of horizontally averaged vertical profiles
+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
+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
+default, plots of horizontally averaged vertical profiles
 (see <a href="#data_output_pr">data_output_pr</a>)
 only contain profiles of data produced by the model
 run. If profiles of prior times (i.e. data of preceding jobs of a
 job chain) shall be plotted additionally (e.g. for comparison
+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
+.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
+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
+.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 &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
+plotted with <span style="font-weight: bold;">profil</span>
+(in
+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
+affects plots of horizontally averaged profiles
 (<a href="#data_output_pr">data_output_pr</a>)
 when plotted with the plot software <span style="font-weight: bold;">profil</span>.
 By default, profiles are plotted up to the top boundary. The height
+level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller value.
+Nevertheless, <span style="font-weight: bold;">all</span> vertical
+level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller
+value.
+Nevertheless, <span style="font-weight: bold;">all</span>
+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 level up to which horizontally averaged
+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 affects plots of horizontally averaged profiles
+</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>)
 when plotted with the plot software <span style="font-weight: bold;">profil</span>,
 …
 (see <a href="#cross_normalized_y">cross_normalized_y</a>).
 If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b>
+= <i>1.5</i> means that all profiles up to the height level of z =
+.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
+= <i>1.5</i> means that all profiles up to the height
+level of z =
+.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 &nbsp;<a href="#data_output_format">data_output_format</a> = <span style="font-style: italic;">'iso2d'</span>.</p><p>It affects plots of&nbsp; 2d vertical cross
+(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
+affects plots of&nbsp; 2d vertical cross
 sections (<a href="#data_output">data_output</a>)
+when plotted with <span style="font-weight: bold;">iso2d</span>. 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
+when plotted with <span style="font-weight: bold;">iso2d</span>.
+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
 visualization within
+the plot can be limited to a certain height level (0 &lt;= z &lt;= <b>z_max_do2d</b>).
+Nevertheless, <span style="font-weight: bold;">all</span> grid points
+the plot can be limited to a certain height level (0 &lt;= z
+&lt;= <b>z_max_do2d</b>).
+Nevertheless, <span style="font-weight: bold;">all</span>
+grid points
 of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>
 or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
 …
 (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="Paketparameter"></a>Package
+</td> </tr> </tbody>
+</table><br>
+<br><h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
 parameters: </h3>
+Package (<span style="font-weight: bold;">mrun</span> option -p): <span style="font-weight: bold;"><a name="particles_package"></a>particles</span>&nbsp;&nbsp;&nbsp;&nbsp;
+Package (<span style="font-weight: bold;">mrun</span>
+option -p): <span style="font-weight: bold;"><a name="particles_package"></a>particles</span>&nbsp;&nbsp;&nbsp;&nbsp;
 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 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
+</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
 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
+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
 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 set with the package parameter <a href="#end_time_prel">end_time_prel</a>. If <span style="font-weight: bold;">dt_prel</span> has been set, additional
+</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>
+has been set, additional
 releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>,
+t_init+2*<span style="font-weight: bold;">dt_prel</span>, t_init+3*<span style="font-weight: bold;">dt_prel</span>, etc.. Actual release times
+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
+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 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
+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
+t_init+2*<span style="font-weight: bold;">dt_prel</span>,
+t_init+3*<span style="font-weight: bold;">dt_prel</span>,
+etc.. Actual release times
+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
+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
+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
+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
 scale velocities can (optionally) be included for calculating the
 particle advection, using the method of Weil et al. (2004, JAS, 61,
 -2887). This method is switched on by the package
+parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>. This also forces the Euler/upstream method to be used for time 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="#use_sgs_for_particles">use_sgs_for_particles</a>.
+This also forces the Euler/upstream method to be used for time
+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
 default, particles are weightless and transported passively with the
 resolved scale flow. Particles can be given a mass and thus an inertia
 by assigning the
+package parameter </font></span><a href="#density_ratio"><span lang="en-GB"><font face="Thorndale, serif">density_ratio</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> a non-zero value (it
+package parameter </font></span><a href="#density_ratio"><span lang="en-GB"><font face="Thorndale, serif">density_ratio</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> a
+non-zero value (it
 defines the ratio of the density of the fluid and the density of the
 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 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 analysis, additional output of
+<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
+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 location of
+informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
+location of
 all
 particles at the end of the
 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 must be saved at the
+end of the run <tt><span lang="en-GB"></span></tt>and given as an
+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
+must be saved at the
+end of the run <tt><span lang="en-GB"></span></tt>and
+given as an
 input file to the restart run
 under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>
+u<span lang="en-GB"><font face="Thorndale, serif">sing respective file
+u<span lang="en-GB"><font face="Thorndale, serif">sing
+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
 particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by the package
 parameter </font></span><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"><font face="Thorndale, serif">dt_dvrp</font></span></a><font face="Thorndale, serif"><span lang="en-GB">. For visualization
+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
+parameter </font></span><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"><font face="Thorndale, serif">dt_dvrp</font></span></a><font face="Thorndale, serif"><span lang="en-GB">.
+For visualization
 purposes particles can be given a
 diameter by the parameter <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a>
 (this diameter only affects the visualization). All particles have the
 same size. Alternatively, particles can be given an individual size and
+a </span>color
+      <span lang="en-GB">by modifying the user-interface (subroutine</span></font>
+      <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">. Particles can pull a
+&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 particle transport realized in PALM does only
+a </span>color <span lang="en-GB">by modifying the
+user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">.
+Particles can pull a
+&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
+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 default, particles are reflected at the bottom boundary.
+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 boundary condition (x-direction) for particle
+transport. </p>
+      <p>By default, cyclic boundary conditions are used along x.
+= <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
+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 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 boundary condition (y-direction) for particle
+transport. </p>
+      <p>By default, cyclic boundary conditions are used along y.
+= <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
+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
+boundary condition (y-direction) for particle
+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>
+= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_ns</b>
+= <i>&acute;absorb&acute;</i>)
+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, particles are absorbed at the top boundary.
+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 of the fluid and the density of the
+particles. </p>
+      <p>With the default value<i> </i>the
+= <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 are weightless and transported passively with the resolved
 scale flow.
+In case of <span style="font-weight: bold;">density_ratio</span> /=
+In case of <span style="font-weight: bold;">density_ratio</span>
+/=
 .0 particles have a mass and hence inertia so that their velocity
 deviates more or less from the velocity of the surrounding flow.
 …
 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>, the particle density
+</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
 do not feel any buoyancy. Otherwise, particles will be accelerated
 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>), each group can be assigned a different value. If the number of values given for <span style="font-weight: bold;">density_ratio</span> is less than the number of
+</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>
+is less than the number of
 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 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 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 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
+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
+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
+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
+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
 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 more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
+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
+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 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
+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
+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
 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 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 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 visualized with the <span style="font-weight: bold;">dvrp</span> software (see <a href="chapter_4.5.7.html">chapter
+.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, the particle diameters can be set with the
+<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
+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
+visualized with the <span style="font-weight: bold;">dvrp</span>
+software (see <a href="chapter_4.5.7.html">chapter
+.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,
+the particle diameters can be set with the
 user-interface in routine <span style="font-family: monospace;">user_init_particles</span>
 (at the beginning of the simulation) and/or can be redefined after each
 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 the size
+<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>
+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>
 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>) 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 allows to set the number of particles for which
+<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
+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 of tailpoints that a particle tail can
+have.&nbsp; </p>
+      <p>&nbsp;<b>maximum_number_of_tailpoints</b>
+</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>
 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
 …
 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 same number of points. The maximum
+timestep.&nbsp; </p> <p>All particle tails have the
+same number of points. The maximum
 length of
 these
 …
 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 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
+</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
 particle tail and the current position of the particle becomes larger
+than the value given by <b>maximum_tailpoint_age</b>, this oldest
+than the value given by <b>maximum_tailpoint_age</b>, this
+oldest
 point (which defines the end of the tail) is
 removed. If this time is so small that the number of points defining
 …
 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 distance allowed between two adjacent points of a
+particle tail (in m).&nbsp; </p>
+      <p>In case of <b>minimum_tailpoint_distance</b> &gt; <i>0.0 </i>the
+= <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>
+&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 proportional to
+</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 coordinates of
+&gt; <i>0.0</i> is recommended, because then the tail
+coordinates of
 slowly moving particles require less memory and can also be drawn
 faster. The upper limit of <b>minimum_tailpoint_distance</b>
 …
 tails still appear as smooth lines. Example: with a model domain of
 m and a monitor resolution of 1280 * 1024 pixels it
+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>
+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 less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
+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>
+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
+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 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 to be released at the beginning of the
+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
+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 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 along x between particles within a particle source
+(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>
+= <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
+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
+along x between particles within a particle source
+(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>
 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> 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 along y between
+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>
+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
+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 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 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 (&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 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 (&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 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>
+(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
+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
+(&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
+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
+(&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
+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 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>
 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 given for <span style="font-weight: bold;">radius</span> is less than the number of
+/= <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
+given for <span style="font-weight: bold;">radius</span>
+is less than the number of
 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> particles is
+varied randomly within certain limits.&nbsp; </p>
+      <p>By default, the initial positions of particles within the
+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
+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
+pdz</a>. With <b>random_start_position</b> = <i>.T.
+</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> = <i>.T.</i>, the
+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;
 run synchronously. If random disturbances are applied to the velocity
 field
+(see <a href="#create_disturbances">create_disturbances</a>), <font color="#000000">then as consequence for parallel runs the
+(see <a href="#create_disturbances">create_disturbances</a>),
+<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, with restart runs particle data is read
+</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>,
 which is created by the preceding run. If this is not requested or if
 …
 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>
+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> = <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>
+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>
+= <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
 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>
+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>
+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
+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>
+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
 velocities are calculated from the resolved and subgrid-scale TKE using
 the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
 …
 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> = <span style="font-style: italic;">.TRUE.</span> automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a> = <span style="font-style: italic;">.TRUE.</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>
+= <span style="font-style: italic;">.TRUE.</span>.
 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, 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>
+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>
 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
 …
 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 may become very large
+and performance of PALM may decrease.</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<span style="font-weight: bold;"><br>
+<br>
+</span><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>
+</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>
+<br></span><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 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 particles can be displayed
+<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
+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 output of scenes created by dvrp software is switched on
+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>),
 this parameter can be used to assign the temporal interval at which
+scenes are to be created (and the respective&nbsp; graphical data is to
+scenes are to be created (and the respective&nbsp; graphical data
+is to
 be output to the streaming server). <span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
 &nbsp;the simulation, i.e. output takes place at times t = <b>dt_dvrp</b>,
+*<b>dt_dvrp</b>, 3*<b>dt_dvrp</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">).&nbsp; Is <b>dt_dvrp</b> &lt; </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">, then scenes are created and
+*<b>dt_dvrp</b>, 3*<b>dt_dvrp</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">).&nbsp;
+Is <b>dt_dvrp</b> &lt; </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">, then
+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 directory into which data created by the <span style="font-weight: bold;">dvrp</span>
+software shall be saved.&nbsp; </p>
+      <p>By default, the directory name is generated from the user
+= <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,
+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 file into which data created by the <span style="font-weight: bold;">dvrp</span> 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
+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
+file into which data created by the <span style="font-weight: bold;">dvrp</span>
+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
 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).
 …
 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 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>
+= <span style="font-style: italic;">'rtsp'</span> only the default
+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>
+= <span style="font-style: italic;">'rtsp'</span>
+only the default
 value is allowed (streaming server of
 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 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>
+= <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
+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 is transferred using
 a special transmission protocol to a so-called streaming server, which
 …
 (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 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 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 account on the computer to which data
+created by the <span style="font-weight: bold;">dvrp</span> software
+</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
+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
+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 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
+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
 to be created by the <span style="font-weight: bold;">dvrp</span>
 software.&nbsp; </p>
       <p>Several different objects can be assigned simultaneously and
+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>
 (isosurface), <span style="font-style: italic;">'slicer#'</span>
 …
 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> = <span style="font-style: italic;">'isosurface2'</span><i>,
+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 case one isosurface, two cross sections, and particles
+'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
 created have to be selected with
 the parameter <a href="#data_output">data_output</a>,
 those for cross sections with <a href="#data_output">data_output</a>
+(<span style="font-weight: bold;">data_output</span> also determines the
+orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> lists of variables may be
+(<span style="font-weight: bold;">data_output</span>
+also determines the
+orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> lists of
+variables may be
 assigned, the digit at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string
 selects the quantity, which is given
+at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface2'</span> selects the quantity
+at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface2'</span>
+selects the quantity
 given in the second position of <span style="font-weight: bold;">data_output</span>).
+If e.g. <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> are assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
+If e.g. <span style="font-weight: bold;">data_output</span>
+and <span style="font-weight: bold;">data_output</span>
+are assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
 'w_xz', 'v_yz'</i> and <b>data_output</b> = <span style="font-style: italic;">'pt'</span><i>,
 'u', 'w' </i>are
+indicated, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an isosurface of u, a
+indicated, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
+isosurface of u, a
 horizontal cross section of u and
 a vertical cross section (xz) of w is created. For locations of the
 …
 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 of mode_dvrp must correspond to those of data_output
+</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
 data_output! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>
 and <b>data_output</b>
+= 'w'<i> </i>was set, then only the digit "1" is allowed for <b>mode_dvrp</b>,
+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 given in <a href="chapter_4.5.7.html">chapter
+.5.7</a>.<br>
+      </p>
+      <b>Note:</b><br>
+= 'w'<i> </i>was set, then only the digit "1" is allowed
+for <b>mode_dvrp</b>,
+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
+given in <a href="chapter_4.5.7.html">chapter
+.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. according
+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.
+according
 to the local characteristics of the flow field) to be used for the
 visualization, must be carried out by adding respective code extensions
 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
 …
 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 domains with unfavorable ratio between the vertical and
+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
 (the vertical size is determined by <a href="#nz_do3d">nz_do3d</a>)
+a <span style="font-weight: bold;">superelevation</span> /= <span style="font-style: italic;">1.0</span> may be used. If e.g. the
+a <span style="font-weight: bold;">superelevation</span>
+/= <span style="font-style: italic;">1.0</span> may
+be used. If e.g. the
 horizontal size is substantially larger
 than the vertical size, a <span style="font-weight: bold;">superelevation</span>
+much larger than <span style="font-style: italic;">1.0</span> should
+much larger than <span style="font-style: italic;">1.0</span>
+should
 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 parameter can be used to stretch the displayed domain
+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 factor for the
+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 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 isosurfaces is switched on via
+</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
+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
+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
+isosurfaces is switched on via
 parameter <a href="#mode_dvrp">mode_dvrp</a>,
 then the respective threshold value for which the isosurface is to be
+created can be assigned via <b>threshold</b>. If several isosurfaces
+are given by <b>mode_dvrp</b>, then an individual threshold value for
+created can be assigned via <b>threshold</b>. If several
+isosurfaces
+are given by <b>mode_dvrp</b>, then an individual
+threshold value for
 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 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>
+/ &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a> (in s).&nbsp; </p>
+      <p>If
+<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>
+/ &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
+(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
 subject to temporal averaging. The interval length is limited by the
+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 is calculated
+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
+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 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 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>. 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 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 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>
+Beside <span style="font-weight: bold;">data_output_sp</span>, values <span style="font-weight: bold;">must</span> be given for each of the
+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
+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>.
+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
+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
+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>
+Beside <span style="font-weight: bold;">data_output_sp</span>,
+values <span style="font-weight: bold;">must</span>
+be given for each of the
 parameters,&nbsp; <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>,
 and <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a></font>,
+otherwise <span style="font-weight: bold;">no</span> output will be
+otherwise <span style="font-weight: bold;">no</span>
+output will be
 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>
+and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For historical reasons, data can also be output in ASCII-format on local files  <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
+and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a> (depending on the direction(s) along which spectra are to be calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font>
+which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a> for defining the format in which data shall be output.&nbsp;Within these file, the spectra are ordered with respect to their
+and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For
+historical reasons, data can also be output in ASCII-format on local
+files <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
+and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
+(depending on the direction(s) along which spectra are to be
+calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font>
+which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See
+parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
+for defining the format in which data shall be output.&nbsp;Within
+these file, the spectra are ordered with respect to their
 output times. Spectra can also be temporally averaged (see <a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a>
+      ).&nbsp;<font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a spectrum is output in a single line (1st column:
+).&nbsp;<font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a
+spectrum is output in a single line (1st column:
 wavenumber, 2nd column: spectral coefficient). If spectra are to be
 calculated and output for more than one height (see </font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font><font>),
 …
 (<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
 means that the file starts with the spectra of the u-component,
+followed by the v-component spectra, etc.). Additional to the files PLOTSP_X_DATA and PLOTSP_Y_DATA which contain
+followed by the v-component spectra, etc.). Additional to the files
+PLOTSP_X_DATA and PLOTSP_Y_DATA which contain
 the data,
 PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a>
 …
 plot layout is
 steered via the parameter input file. The vertical levels for which
 spectra are to be plotted must be given by <font><a href="chapter_4.2.html#plot_spectra_level"><span lang="en-GB"><font face="Thorndale">plot_spectra_level</font></span></a></font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"></span></a></font>.
       <span style="font-weight: bold;"></span>Otherwise, no spectra
+spectra are to be plotted must be given by <font><a href="chapter_4.2.html#plot_spectra_level"><span lang="en-GB"><font face="Thorndale">plot_spectra_level</font></span></a></font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"></span></a></font>. <span style="font-weight: bold;"></span>Otherwise, no
+spectra
 will appear on the plot, although data are available on file. All
 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 interval at which&nbsp;spectra data shall be output
+(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
+<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
+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
 assign the temporal interval at which spectral data&nbsp; shall be
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>, which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
+output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
+simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>,
+which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
 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> + 2*<b>dt_dosp</b>, skip_time_dosp + 3*<b>dt_dosp</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">).&nbsp; If <b>dt_dosp</b> &lt; </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">, then spectral data are output
+<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
+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">).&nbsp;
+If <b>dt_dosp</b> &lt; </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">, then
+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 level(s) for which horizontal spectra are to be
+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
+= <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
+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
+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 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 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
+<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
+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
+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
 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 requires cyclic boundary conditions
+direction<span style="font-weight: bold;"> </span>must
+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> 22/08/06 (SR)<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
+</span></span>
+<br>
+</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>
+/08/06 (SR)<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
+</span></span><br>
 </body></html>

palm/trunk/DOC/app/chapter_4.3.html

-                      r5
+                      r48
         -->
         </style></head>
 <body dir="ltr" lang="en-US">
 <h3 style="line-height: 200%;">4.3 User-defined parameters</h3>
 …
       <p>With this variable, names can be assigned to the subsections
 defined by the user (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>)
 which afterwards appear in the headers of the respective files (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>, <a href="chapter_3.4.html#PLOTTS_DATA">PLOTTS_DATA</a>)
+which afterwards appear in the headers of the respective files (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
 and within the respective plots. Up to 9 subdomains are allowed (<b>region</b>
 (1) to <b>region</b> (9)), the total domain has the index 0 (<b>region</b>

palm/trunk/DOC/app/chapter_4.5.1.html

-                      r5
+                      r48
 <a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
 (or <a href="chapter_4.2.html#skip_time_dopr">skip_time_dopr</a>),
+<a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">timeseries</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output_ts">data_output_ts</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.2.html#dt_dots">dt_dots</a>, <a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">spectra</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>,
+<a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">timeseries</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#dt_dots">dt_dots</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output_format">data_output_format</a>, <a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">spectra</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>,
 <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>,
 <a href="chapter_4.2.html#dt_data_output">dt_data_output</a>

palm/trunk/DOC/app/chapter_4.5.3.html

-                      r5
+                      r48
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=windows-1252">
+  <title>PALM chapter 4.5.3</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+<html><head>
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+  <title>PALM chapter 4.5.3</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
   <meta name="AUTHOR" content="Siegfried Raasch">
   <meta name="CREATED" content="20041026;14291096">
 …
                 @page { size: 21cm 29.7cm }
         -->
         </style>
+</head>
+        </style></head>
 <body dir="ltr" lang="en-US">
 <h4 style="line-height: 100%;"><font size="4">4.5.3 Plots of time
 series
+with profil</font></h4>
+<p style="line-height: 100%;">Output of time series is enabled
+by providing a value for the run parameter <a
+ href="chapter_4.2.html#dt_dots">dt_dots</a>,
+which specifies the temporal interval at which time series data is
+output. Output times cannot be defined
+directly but only via the output time interval, starting from the
+beginning of the initial 3d run (t=0, but no data is output at that
+time). The time series data
+represent sums, averages or extreme values which by default refer to
+the total model domain.
+Output of time series for user-defined subdomains is possible with the
+help of the initialization parameter
+<a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
+with profil</font></h4>Sorry, this feature isn't supported any more.<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.2.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.5.4.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;">&nbsp;<span style="font-style: italic;">Last
+change:</span> 06/03/07 (SR)<br>
 </p>
+<p style="line-height: 100%;">Time series are output into the local
+file <a href="chapter_3.4.html#PLOTTS_DATA">PLOTTS_DATA</a>.
+This file must be linked with a permanent file via a file connection
+statement in the <b>mrun</b> configuration file (see e.g. <a
+ href="chapter_3.2.html">Chapter
+.2</a>). At the end of the run the local file is copied to this
+file. Such a statement can look like this: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">PLOTTS_DATA  out:loc:tr  ts   ~/PLOT/$fname   _ts_in</font></pre>
+</ul>
+<p style="line-height: 100%;">If the respective <b>mrun</b> call is
+like<br>
+</p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -d test -r ts
+</font></pre>
+</ul>
+<p style="line-height: 100%;">then the local file <tt><font
+ style="font-size: 10pt;" size="2">PLOTTS_DATA</font></tt>
+is copied to the permanent file <tt><font style="font-size: 10pt;"
+ size="2">~/PLOT/test/test_ts_in</font>
+</tt><font face="Thorndale, serif">.</font> However, the character
+string <font style="font-size: 10pt;" size="2"></font><tt><font
+ style="font-size: 10pt;" size="2">ts</font></tt><font
+ style="font-size: 10pt;" size="2"></font>
+activating the file connection staement (see third column of the
+statement) must be given in the <b>mrun</b> call as argument of the
+option -r (and/or -o)<b>. </b>If this is
+forgotten by mistake, the model outputs the data to the local file, but
+this is
+not copied to the permanent file and thus the data are not available
+for the user after the run has finished. </p>
+<p style="line-height: 100%;">The time series data file always
+contains all time series available. Which time series are
+actually plotted can be specified via the parameter <a
+ href="chapter_4.2.html#data_output_ts">data_output_ts</a>.<br>
+</p>
+<p style="line-height: 100%;">The created data file can be directly
+used as input file for the plot
+routine <b>profil</b>. Beside the data file,&nbsp; <b>profil</b>
+needs another file, the
+so-called parameter file, which specifies the plot layout. This file is
+created by PALM under the local
+name <a href="chapter_3.4.html#PLOTTS_PAR">PLOTTS_PAR</a>
+and also needs a file connection statement, e.g.: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">PLOTTS_PAR out:loc:tr  ts  ~/PLOT/$fname  _ts_par</font></pre>
+</ul>
+<p style="line-height: 100%;">If you are in the directory
+<tt><font style="font-size: 10pt;" size="2">~/PLOT/test</font>,</tt>the
+data can be plotted by entering </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">profil -d  test_ts_in  -p test_ts_par</font></pre>
+</ul>
+<p style="line-height: 100%;">Which time series are actually plotted
+can be determined with the parameter <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>.
+</p>
+<p style="line-height: 100%;">By default plot layout as specified in
+the parameter file is as follows: the individual time series are
+plotted
+into individual coordinate systems (panels) which are arranged one upon
+the other. Typically several time
+series are plotted
+together into one panel. The grouping is fixed PALM-internally (it can
+be changed by editing the parameter input file). The parameter <b>data_output_ts</b>
+determines which time series are actually to be plotted. If none of the
+time series
+which are assigned to a certain panel is plotted,
+then this panel is completely omitted in the plot. </p>
+<p style="line-height: 100%;">The time series are always plotted
+one page only. or identification, each plot is
+provided with a title, which contains the model version number, the
+run identifier (base file name + number of the restart run), the name
+of the host where the run was executed, the date and time of the
+beginning
+of the run as well as the averaging domain (by default: <span
+ style="font-style: italic;">'total
+domain'</span>).
+The x axes of the panels have the label <i>time
+in s</i>, the y axes have no label. The
+run parameters <a href="chapter_4.2.html#cross_ts_uymin">cross_ts_uymin</a>
+and <a href="chapter_4.2.html#cross_ts_uymax">cross_ts_uymax</a>
+can be used to assign the range of values of the y axis individually
+for
+each panel. By default, the range of values is calculated
+from the minimum and maximum values of the time series. Each system
+has a legend which contains an entry for each time serias. The legend
+string is taken from file PLOTTS_DATA where the time
+series contained are noted in the comment lines at the
+beginning of the file. If a panel contains more than one time series
+then they are marked by different
+colors and types of lines. </p>
+<p style="line-height: 100%;">If a simulation needs restart runs, then
+one usually would like to have the time series of the complete
+simulation in one plot. Using the file connection statements shown
+above, a new cycle of time series data file and of the parameter file
+is created for each run and thus the time series could only be plotted
+in pieces. If one wants to have the complete time series in one
+plot, the configuration file must be changed such that for
+restart runs the time series data are appended to already existing
+data (thus all data are output into one file). Then the configuration
+file has two entries for PLOTTS_DATA:
+</p>
+<ul>
+  <pre style="line-height: 100%;"><font style="font-size: 10pt;"
+ size="2">PLOTTS_DATA out:loc:tr   ts#  ~/PLOT/$fname  _ts_in</font><br><font
+ style="font-size: 10pt;" size="2">PLOTTS_DATA out:loc:tra  tsf  ~/PLOT/$fname  _ts_in.</font></pre>
+</ul>
+<p style="line-height: 100%;">The first run of the job chain is now </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun  -d  test -r ts#
+</font></pre>
+</ul>
+<p style="line-height: 100%;">For the restart runs, the "#" in the <span
+ style="font-weight: bold;">mrun</span>
+call is automatically replaced by an "f". At the end of the job chain
+there will only be one data file containing the complete time series
+data. The file connection staement for the parameter file PLOTTS_PAR
+has not changed, thus a new cycle of the respective permanent file is
+created for each run. The highest
+cycle of this file can be used as parameter file in order to plot the
+complete time series. </p>
+<p style="line-height: 100%;">The default layout of the plots of time
+series described can be changed by editing the
+parameter file. For a detailed description of the <span
+ style="font-weight: bold;">profil</span> parameters see the
+<a
+ href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>
+manual (only in German).&nbsp;<br>
+</p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.2.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a
+ href="chapter_4.5.4.html"><font color="#000080"><img src="right.gif"
+ name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;">&nbsp;<span style="font-style: italic;">Last
+change:</span> 19/04/05 (SR)<br>
+</p>
+</body>
+</html>
+</body></html>

palm/trunk/DOC/app/chapter_4.6.html

-                      r46
+                      r48
+    <tr>
+      <td style="vertical-align: middle;" width="15%">
+      <p><a href="chapter_4.2.html#cross_ts_uymax"><b>cross_ts_uymax</b></a></p>
+      </td>
+      <td style="vertical-align: middle;" width="5%">
+      <p>R</p>
+      </td>
+      <td style="vertical-align: middle;" width="7%">
+      <p>R (10)</p>
+      </td>
+      <td style="vertical-align: middle;" width="16%">
+      <p><i>10 * 999.999</i></p>
+      </td>
+      <td style="vertical-align: middle;" width="57%">
+      <p>Maximum of the range of y-axis values for coordinate
+systems
+of time series plots. <br>
+      </p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: middle;" width="15%">
+      <p><a href="chapter_4.2.html#cross_ts_uymin"><b>cross_ts_uymin</b></a></p>
+      </td>
+      <td style="vertical-align: middle;" width="5%">
+      <p>R</p>
+      </td>
+      <td style="vertical-align: middle;" width="7%">
+      <p>R (10)</p>
+      </td>
+      <td style="vertical-align: middle;" width="16%">
+      <p><i>10 * 999.999</i></p>
+      </td>
+      <td style="vertical-align: middle;" width="57%">
+      <p>Minimum of the range of y-axis values for coordinate
+systems
+of time series plot. <br>
+      </p>
+      </td>
+    </tr>
 …
 and output.</td>
     </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#data_output_ts"><span style="font-weight: bold;">data_output_ts</span></a></td>
+      <td>R</td>
+      <td>C * 10 (100)</td>
+      <td><span style="font-style: italic;">100 * ' '</span></td>
+      <td>Quantities for which time series
+are to be output (plot).&nbsp; </td>
+    </tr>
     <tr>
       <td><a href="chapter_4.3.html#data_output_user"><span style="font-weight: bold;">data_output_user</span></a></td>
 …
 <p>&nbsp;<i>Last change:&nbsp;&nbsp;</i> 07/11/06 (ML) </p>
+<p>&nbsp;<i>Last change:&nbsp;&nbsp;</i> 07/03/07 (SR) </p>

palm/trunk/SOURCE/CURRENT_MODIFICATIONS

-                      r46
+                      r48
 new d3par-parameter netcdf_64bit_3d to switch on 64bit offset only for 3D files
+new initializing action "by_user" calls user_init_3d_model and allows the
+initial setting of all 3d arrays
+new initializing action "by_user" calls user_init_3d_model and allows the initial setting of all 3d arrays
+check_open, check_parameters, header, init_3d_model, modules, parin, user_interface
+topography height informations are stored on arrays zu_s_inner and zw_w_inner and output to the 2d/3d NetCDF files
+samples added to the user interface which show how to add user-define time series quantities.
+check_open, check_parameters, header, init_3d_model, modules, netcdf, parin, user_interface
 …
 Move call of user_actions( 'after_integration' ) below increment of times
 and counters
+and counters. user_actions is now called for each statistic region and has as an argument the number of the respective region (sr)
+time_integration
+d3par-parameter data_output_ts removed. Timeseries output for "profil" removed. Timeseries are now switched on by dt_dots. Timeseries data is collected in flow_statistics.
+check_parameters, data_output_ts, flow_statistics, init_3d_model, modules, parin, time_integration
 …
 Bugfix: preset of tendencies te_em, te_um, te_vm in init_1d_model
+in Makefile, default suffixes removed from the suffix list to avoid calling of m2c in
+# case of .mod files
+Makefile
 init_1d_model

palm/trunk/SOURCE/Makefile

-                      r3
+                      r48
 # Actual revisions:
 # -----------------
+#
+# default suffixes removed from the suffix list to avoid calling of m2c in
+# case of .mod files
+#
 # Former revisions:
 …
 LDFLAGS =
+.SUFFIXES: $(SUFFIXES) .f90
+.SUFFIXES:
+.SUFFIXES: .o .f90

palm/trunk/SOURCE/check_parameters.f90

-                      r46
+                      r48
 ! Actual revisions:
 ! -----------------
 ! "by_user" allowed as initializing action
+! "by_user" allowed as initializing action, -data_output_ts
+!
 ! Former revisions:
 …
     ENDIF
+!
-!-- Determine parameters for time series output and check whether permissible
-    i = 0
-    DO  WHILE ( data_output_ts(i+1) /= '          '  .AND.  i+1 <= 100 )
-       dots_n = dots_n + 1
-       i = i + 1
+!
-!--    Check whether time series is permissible and determine internal number
-       SELECT CASE ( TRIM( data_output_ts(i) ) )
-          CASE ( 'E' )
-             dots_index(i) = 1
-          CASE ( 'E*' )
-             dots_index(i) = 2
-          CASE ( 'dt' )
-             dots_index(i) = 3
-          CASE ( 'u*' )
-             dots_index(i) = 4
-          CASE ( 'th*' )
-             dots_index(i) = 5
-          CASE ( 'umax' )
-             dots_index(i) = 6
-          CASE ( 'vmax' )
-             dots_index(i) = 7
-          CASE ( 'wmax' )
-             dots_index(i) = 8
-          CASE ( 'div_new' )
-             dots_index(i) = 9
-          CASE ( 'div_old' )
-             dots_index(i) = 10
-          CASE ( 'z_i_wpt' )
-             dots_index(i) = 11
-          CASE ( 'z_i_pt' )
-             dots_index(i) = 12
-          CASE ( 'w*' )
-             dots_index(i) = 13
-          CASE ( 'w"pt"0' )
-             dots_index(i) = 14
-          CASE ( 'w"pt"' )
-             dots_index(i) = 15
-          CASE ( 'wpt' )
-             dots_index(i) = 16
-          CASE ( 'pt(0)' )
-             dots_index(i) = 17
-          CASE ( 'pt(zp)' )
-             dots_index(i) = 18
-          CASE ( 'splptx'  )
-             dots_index(i) = 19
-          CASE ( 'splpty'  )
-             dots_index(i) = 20
-          CASE ( 'splptz'  )
-             dots_index(i) = 21
-          CASE ( 'L'       )
-             dots_index(i) = 22
-          CASE DEFAULT
-             IF ( myid == 0 )  THEN
-                PRINT*, '+++ check_parameters:  unknown time series:  ', &
-                             'data_output_ts = ',&
-                        data_output_ts(i)
-             ENDIF
-             CALL local_stop
-       END SELECT
+!
-!--    Check, to which predefined coordinate system the time series belongs, and
-!--    store corresponding internal number. Furthermore determine, how many and
-!--    which graphs are being drawn into the corresponding system
-       DO  k = 1, crmax
-          IF ( INDEX( cross_ts_profiles(k), ' ' // TRIM( data_output_ts(i) ) &
-                      // ' ' ) /=0 )  &
-          THEN
-             dots_crossindex(i) = k
-             cross_ts_number_count(k) = cross_ts_number_count(k) + 1
-             cross_ts_numbers(cross_ts_number_count(k),k) = dots_index(i)
-             EXIT
-          ENDIF
-       ENDDO
-    ENDDO
+!

palm/trunk/SOURCE/data_output_tseries.f90

-                      r4
+                      r48
 ! Actual revisions:
 ! -----------------
+!
+! Collection of time series quantities moved to routine flow_statistics,
+! output for "profil" removed
+!
 ! Former revisions:
 …
     INTEGER ::  file_id, i, j, sr
-    REAL    ::  ts_value(30)
 …
 !--    applicable)
        DO  sr = 0, statistic_regions
+!
-!--       Open file for time series output.
-          IF ( profil_output )  THEN
-             file_id = 50 + sr
-             CALL check_open( file_id )
-          ENDIF
+!
-!--       Collect and printout all time series quantities in a single line.
-          ts_value(1) = hom(nzb+4,1,var_hom,sr)     ! E
-          ts_value(2) = hom(nzb+5,1,var_hom,sr)     ! E*
-          ts_value(3) = dt_3d
-          ts_value(4) = hom(nzb,1,var_hom,sr)       ! u*
-          ts_value(5) = hom(nzb+3,1,var_hom,sr)     ! th*
-          ts_value(6) = u_max
-          ts_value(7) = v_max
-          ts_value(8) = w_max
-          ts_value(9) = hom(nzb+10,1,var_sum,sr)    ! new divergence
-          ts_value(10) = hom(nzb+9,1,var_hom,sr)    ! old Divergence
-          ts_value(11) = hom(nzb+6,1,var_hom,sr)    ! z_i(1)
-          ts_value(12) = hom(nzb+7,1,var_hom,sr)    ! z_i(2)
-          ts_value(13) = hom(nzb+8,1,var_hom,sr)    ! w*
-          ts_value(14) = hom(nzb,1,16,sr)           ! w'pt'   at k=0
-          ts_value(15) = hom(nzb+1,1,16,sr)         ! w'pt'   at k=1
-          ts_value(16) = hom(nzb+1,1,18,sr)         ! wpt     at k=1
-          ts_value(17) = hom(nzb,1,4,sr)            ! pt(0)
-          ts_value(18) = hom(nzb+1,1,4,sr)          ! pt(zp)
-          ts_value(19) = hom(nzb+9,1,var_hom-1,sr)  ! splptx
-          ts_value(20) = hom(nzb+10,1,var_hom-1,sr) ! splpty
-          ts_value(21) = hom(nzb+11,1,var_hom-1,sr) ! splptz
-          IF ( ts_value(5) /= 0.0 )  THEN
-             ts_value(22) = ts_value(4)**2 / &
-                            ( kappa * g * ts_value(5) / ts_value(18) )  ! L
-          ELSE
-             ts_value(22) = 10000.0
-          ENDIF
 #if defined( __netcdf )
 …
              DO  i = 1, dots_num
                 nc_stat = NF90_PUT_VAR( id_set_ts, id_var_dots(i,sr),  &
                                         (/ ts_value(i) /),             &
+                                        (/ ts_value(i,sr) /),          &
                                         start = (/ dots_time_count /), &
                                         count = (/ 1 /) )
 …
 #endif
+          IF ( profil_output )  THEN
+             WRITE ( file_id, 500 )  simulated_time, ts_value(1:22)
+!
+!--          y-value range of the crosses to be drawn by PROFIL
+!--          If required, enlarge them, provided they have not yet been
+!--          specified in
+!--          check_parameters
+             DO  i = 1, dots_n
+                j = dots_crossindex(i)
+                IF ( cross_ts_uymin(j) == 999.999 )  THEN
+!
+!--                When the value range of the first line in the corresponding
+!--                cross is determined, its value range is simply adopted.
+                   IF ( cross_ts_uymin_computed(j) == 999.999 ) &
+                   THEN
+                      cross_ts_uymin_computed(j) = ts_value(dots_index(i))
+                   ELSE
+                      cross_ts_uymin_computed(j) = &
+                         MIN(cross_ts_uymin_computed(j),ts_value(dots_index(i)))
+                   ENDIF
+                ENDIF
+                IF ( cross_ts_uymax(j) == 999.999 )  THEN
+!
+!--                When the value range of the first line in the corresponding
+!--                cross is determined, its value range is simply adopted.
+                   IF ( cross_ts_uymax_computed(j) == 999.999 ) &
+                   THEN
+                      cross_ts_uymax_computed(j) = ts_value(dots_index(i))
+                   ELSE
+                      cross_ts_uymax_computed(j) = &
+                         MAX(cross_ts_uymax_computed(j),ts_value(dots_index(i)))
+                   ENDIF
+                ENDIF
+             ENDDO
+          ENDIF
+       ENDDO   ! Loop of subregions.
+       ENDDO
     ENDIF

palm/trunk/SOURCE/flow_statistics.f90

-                      r39
+                      r48
        ENDIF
+!
+!--    Collect the time series quantities
+       ts_value(1,sr) = hom(nzb+4,1,var_hom,sr)     ! E
+       ts_value(2,sr) = hom(nzb+5,1,var_hom,sr)     ! E*
+       ts_value(3,sr) = dt_3d
+       ts_value(4,sr) = hom(nzb,1,var_hom,sr)       ! u*
+       ts_value(5,sr) = hom(nzb+3,1,var_hom,sr)     ! th*
+       ts_value(6,sr) = u_max
+       ts_value(7,sr) = v_max
+       ts_value(8,sr) = w_max
+       ts_value(9,sr) = hom(nzb+10,1,var_sum,sr)    ! new divergence
+       ts_value(10,sr) = hom(nzb+9,1,var_hom,sr)    ! old Divergence
+       ts_value(11,sr) = hom(nzb+6,1,var_hom,sr)    ! z_i(1)
+       ts_value(12,sr) = hom(nzb+7,1,var_hom,sr)    ! z_i(2)
+       ts_value(13,sr) = hom(nzb+8,1,var_hom,sr)    ! w*
+       ts_value(14,sr) = hom(nzb,1,16,sr)           ! w'pt'   at k=0
+       ts_value(15,sr) = hom(nzb+1,1,16,sr)         ! w'pt'   at k=1
+       ts_value(16,sr) = hom(nzb+1,1,18,sr)         ! wpt     at k=1
+       ts_value(17,sr) = hom(nzb,1,4,sr)            ! pt(0)
+       ts_value(18,sr) = hom(nzb+1,1,4,sr)          ! pt(zp)
+       ts_value(19,sr) = hom(nzb+9,1,var_hom-1,sr)  ! splptx
+       ts_value(20,sr) = hom(nzb+10,1,var_hom-1,sr) ! splpty
+       ts_value(21,sr) = hom(nzb+11,1,var_hom-1,sr) ! splptz
+       IF ( ts_value(5,sr) /= 0.0 )  THEN
+          ts_value(22,sr) = ts_value(4,sr)**2 / &
+                            ( kappa * g * ts_value(5,sr) / ts_value(18,sr) ) ! L
+       ELSE
+          ts_value(22,sr) = 10000.0
+       ENDIF
+!
+!--    Calculate additional statistics provided by the user interface
+       CALL user_statistics( sr )
     ENDDO    ! loop of the subregions
+!
-!-- Calculate additional statistics provided by the user interface
-    CALL user_statistics
+!

palm/trunk/SOURCE/init_3d_model.f90

-                      r46
+                      r48
 ! Actual revisions:
 ! -----------------
+! New initializing action "by_user" calls user_init_3d_model
+! New initializing action "by_user" calls user_init_3d_model,
+! ts_value is allocated
+!
 ! Former revisions:
 …
               sums_l_l(nzb:nzt+1,0:statistic_regions,0:threads_per_task-1), &
               sums_up_fraction_l(10,3,0:statistic_regions),                 &
+              sums_wsts_bc_l(nzb:nzt+1,0:statistic_regions) )
+              sums_wsts_bc_l(nzb:nzt+1,0:statistic_regions),                &
+              ts_value(var_ts,0:statistic_regions) )
     ALLOCATE( km_damp_x(nxl-1:nxr+1), km_damp_y(nys-1:nyn+1) )

palm/trunk/SOURCE/init_grid.f90

r39	r48
4	4	! Actual revisions:
5	5	! -----------------
6		!
	6	! storage of topography height arrays zu_s_inner and zw_s_inner
7	7	!
8	8	! Former revisions:

palm/trunk/SOURCE/modules.f90

-                      r46
+                      r48
 ! Actual revisions:
 ! -----------------
+! +netcdf_64bit_3d
+! +netcdf_64bit_3d, zu_s_inner, zw_w_inner, id_var_zusi_*, id_var_zwwi_*,
+! ts_value
+! -data_output_ts, dots_n
+! arrays dots_label and dots_unit now dimensioned with dots_max
+!
 ! Former revisions:
 …
     CHARACTER (LEN=10), DIMENSION(100) ::  data_output = ' ',    &
                                            data_output_pr = ' ', &
-                                           data_output_ts = ' ', &
                                            data_output_user = ' ', doav = ' '
     CHARACTER (LEN=20), DIMENSION(10)  ::  netcdf_precision = ' '
 …
                 disturbance_level_ind_t, doav_n = 0, dopr_n = 0, &
                 dopr_time_count = 0, dopts_time_count = 0, &
                 dosp_time_count = 0, dots_n = 0, dots_time_count = 0, &
+                dosp_time_count = 0, dots_time_count = 0, &
                 do2d_xy_n = 0, do2d_xz_n = 0, do2d_yz_n = 0, do3d_avs_n = 0, &
                 dvrp_filecount = 0, dz_stretch_level_index, gamma_mg, &
 …
     REAL, DIMENSION(:), ALLOCATABLE ::  ddx2_mg, ddy2_mg
+    REAL, DIMENSION(:,:), ALLOCATABLE ::  fwxm, fwxp, fwym, fwyp, fxm, fxp, &
+                                          fym, fyp, wall_e_x, wall_e_y, &
+                                          wall_u, wall_v, wall_w_x, wall_w_y
+    REAL, DIMENSION(:,:), ALLOCATABLE ::  fwxm, fwxp, fwym, fwyp, fxm, fxp,   &
+                                          fym, fyp, wall_e_x, wall_e_y,       &
+                                          wall_u, wall_v, wall_w_x, wall_w_y, &
+                                          zu_s_inner, zw_w_inner
     SAVE
 …
 #endif
     INTEGER, PARAMETER ::  dopr_norm_num = 7, dopts_num = 26, dots_num = 22, &
+    INTEGER, PARAMETER ::  dopr_norm_num = 7, dopts_num = 26, dots_max = 100, &
                            replace_num = 6
+    INTEGER ::  dots_num = 22
     CHARACTER, DIMENSION( replace_num ) :: &
 …
              'm2/s2  ', 'number2' /)
     CHARACTER (LEN=7), DIMENSION(dots_num) :: dots_label = &
+    CHARACTER (LEN=7), DIMENSION(dots_max) :: dots_label = &
           (/ 'E      ', 'E*     ', 'dt     ', 'u*     ', 'th*    ', 'umax   ', &
              'vmax   ', 'wmax   ', 'div_new', 'div_old', 'z_i_wpt', 'z_i_pt ', &
              'w*     ', 'w"pt"0 ', 'w"pt"  ', 'wpt    ', 'pt(0)  ', 'pt(zp) ', &
+             'splptx ', 'splpty ', 'splptz ', 'mo_L   ' /)
+    CHARACTER (LEN=7), DIMENSION(dots_num) :: dots_unit = &
+             'splptx ', 'splpty ', 'splptz ', 'mo_L   ',                       &
+             ( 'unknown', i9 = 1, 78) /)
+    CHARACTER (LEN=7), DIMENSION(dots_max) :: dots_unit = &
           (/ 'm2/s2  ', 'm2/s2  ', 's      ', 'm/s    ', 'K      ', 'm/s    ', &
              'm/s    ', 'm/s    ', 's-1    ', 's-1    ', 'm      ', 'm      ', &
              'm/s    ', 'K m/s  ', 'K m/s  ', 'k m/s  ', 'K      ', 'K      ', &
+             '%      ', '%      ', '%      ', 'm      ' /)
+             '%      ', '%      ', '%      ', 'm      ',                       &
+             ( 'unknown', i9 = 1, 78 ) /)
     CHARACTER (LEN=7), DIMENSION(100) ::  dopr_unit = 'unknown'
 …
                 id_var_xu_yz, id_var_x_3d, id_var_xu_3d, id_var_y_xy, &
                 id_var_yv_xy, id_var_y_xz, id_var_yv_xz, id_var_y_yz, &
+                id_var_yv_yz, id_var_y_3d, id_var_yv_3d, id_var_zu_xy, &
+                id_var_zu1_xy, id_var_zu_xz, id_var_zu_yz, id_var_zu_3d, &
+                id_var_yv_yz, id_var_y_3d, id_var_yv_3d, id_var_zusi_xy, &
+                id_var_zusi_3d, id_var_zu_xy, id_var_zu1_xy, id_var_zu_xz, &
+                id_var_zu_yz, id_var_zu_3d, id_var_zwwi_xy, id_var_zwwi_3d, &
                 id_var_zw_xy, id_var_zw_xz, id_var_zw_yz, id_var_zw_3d
 …
     INTEGER, DIMENSION(100,0:9)        ::  id_dim_z_pr, id_var_dopr, &
                                            id_var_z_pr
     INTEGER, DIMENSION(dots_num,0:9)   ::  id_var_dots
+    INTEGER, DIMENSION(dots_max,0:9)   ::  id_var_dots
 …
     CHARACTER (LEN=40) ::  region(0:9)
     INTEGER ::  statistic_regions = 0, var_hom = 80, var_sum = 80
+    INTEGER ::  statistic_regions = 0, var_hom = 80, var_sum = 80, var_ts = 100
     INTEGER ::  u_max_ijk(3), v_max_ijk(3), w_max_ijk(3)
     LOGICAL ::  flow_statistics_called = .FALSE.
     REAL ::     u_max, v_max, w_max
     REAL, DIMENSION(:), ALLOCATABLE       ::  sums_divnew_l, sums_divold_l
     REAL, DIMENSION(:,:), ALLOCATABLE     ::  sums, sums_wsts_bc_l
+    REAL, DIMENSION(:,:), ALLOCATABLE     ::  sums, sums_wsts_bc_l, ts_value
     REAL, DIMENSION(:,:,:), ALLOCATABLE   ::  hom_sum, rmask, spectrum_x, &
                                               spectrum_y, sums_l, sums_l_l, &

palm/trunk/SOURCE/netcdf.f90

-                      r4
+                      r48
 ! Current revisions:
 ! ------------------
+!
+! Output topography height information (zu_s_inner, zw_s_inner) to 2d-xy and 3d
+! datasets
+!
 ! Former revisions:
 …
+!
+!--       In case of non-flat topography define 2d-arrays containing the height
+!--       informations
+          IF ( TRIM( topography ) /= 'flat' )  THEN
+!
+!--          Define zusi = zu(nzb_s_inner)
+             nc_stat = NF90_DEF_VAR( id_set_3d(av), 'zusi', NF90_DOUBLE,     &
+                                     (/ id_dim_x_3d(av), id_dim_y_3d(av) /), &
+                                     id_var_zusi_3d(av) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 413 )
+             nc_stat = NF90_PUT_ATT( id_set_3d(av), id_var_zusi_3d(av), &
+                                     'units', 'meters' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 414 )
+             nc_stat = NF90_PUT_ATT( id_set_3d(av), id_var_zusi_3d(av), &
+                                     'long_name', 'zu(nzb_s_inner)' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 415 )
+!
+!--          Define zwwi = zw(nzb_w_inner)
+             nc_stat = NF90_DEF_VAR( id_set_3d(av), 'zwwi', NF90_DOUBLE,     &
+                                     (/ id_dim_x_3d(av), id_dim_y_3d(av) /), &
+                                     id_var_zwwi_3d(av) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 416 )
+             nc_stat = NF90_PUT_ATT( id_set_3d(av), id_var_zwwi_3d(av), &
+                                     'units', 'meters' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 417 )
+             nc_stat = NF90_PUT_ATT( id_set_3d(av), id_var_zwwi_3d(av), &
+                                     'long_name', 'zw(nzb_w_inner)' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 418 )
+          ENDIF
+!
 !--       Define the variables
           var_list = ';'
 …
 !--       No arrays to output
           IF ( i == 1 )  RETURN
-!             nc_stat = NF90_CLOSE( id_set_3d(av) )
-!             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 9999 )
-!             RETURN
-!          ENDIF
+!
 …
           IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 86 )
+!
+!--       In case of non-flat topography write height information
+          IF ( TRIM( topography ) /= 'flat' )  THEN
+             nc_stat = NF90_PUT_VAR( id_set_3d(av), id_var_zusi_3d(av), &
+                                     zu_s_inner(0:nx+1,0:ny+1), &
+                                     start = (/ 1, 1 /), &
+                                     count = (/ nx+2, ny+2 /) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 419 )
+             nc_stat = NF90_PUT_VAR( id_set_3d(av), id_var_zwwi_3d(av), &
+                                     zw_w_inner(0:nx+1,0:ny+1), &
+                                     start = (/ 1, 1 /), &
+                                     count = (/ nx+2, ny+2 /) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 420 )
+          ENDIF
        CASE ( '3d_ext' )
 …
+!
+!--       In case of non-flat topography define 2d-arrays containing the height
+!--       informations
+          IF ( TRIM( topography ) /= 'flat' )  THEN
+!
+!--          Define zusi = zu(nzb_s_inner)
+             nc_stat = NF90_DEF_VAR( id_set_xy(av), 'zusi', NF90_DOUBLE, &
+                                     (/ id_dim_x_xy(av), id_dim_y_xy(av) /), &
+                                     id_var_zusi_xy(av) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 421 )
+             nc_stat = NF90_PUT_ATT( id_set_xy(av), id_var_zusi_xy(av), &
+                                     'units', 'meters' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 422 )
+             nc_stat = NF90_PUT_ATT( id_set_xy(av), id_var_zusi_xy(av), &
+                                     'long_name', 'zu(nzb_s_inner)' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 423 )
+!
+!--          Define zwwi = zw(nzb_w_inner)
+             nc_stat = NF90_DEF_VAR( id_set_xy(av), 'zwwi', NF90_DOUBLE, &
+                                     (/ id_dim_x_xy(av), id_dim_y_xy(av) /), &
+                                     id_var_zwwi_xy(av) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 424 )
+             nc_stat = NF90_PUT_ATT( id_set_xy(av), id_var_zwwi_xy(av), &
+                                     'units', 'meters' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 425 )
+             nc_stat = NF90_PUT_ATT( id_set_xy(av), id_var_zwwi_xy(av), &
+                                     'long_name', 'zw(nzb_w_inner)' )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 426 )
+          ENDIF
+!
 !--       Define the variables
           var_list = ';'
 …
 !--       No arrays to output. Close the netcdf file and return.
           IF ( i == 1 )  RETURN
-!             nc_stat = NF90_CLOSE( id_set_xy(av) )
-!             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 9999 )
-!             RETURN
-!          ENDIF
+!
 …
           DEALLOCATE( netcdf_data )
+!
+!--       In case of non-flat topography write height information
+          IF ( TRIM( topography ) /= 'flat' )  THEN
+             nc_stat = NF90_PUT_VAR( id_set_xy(av), id_var_zusi_xy(av), &
+                                     zu_s_inner(0:nx+1,0:ny+1), &
+                                     start = (/ 1, 1 /), &
+                                     count = (/ nx+2, ny+2 /) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 427 )
+             nc_stat = NF90_PUT_VAR( id_set_xy(av), id_var_zwwi_xy(av), &
+                                     zw_w_inner(0:nx+1,0:ny+1), &
+                                     start = (/ 1, 1 /), &
+                                     count = (/ nx+2, ny+2 /) )
+             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 428 )
+          ENDIF
 …
 !--       No arrays to output. Close the netcdf file and return.
           IF ( i == 1 )  RETURN
-!             nc_stat = NF90_CLOSE( id_set_xz(av) )
-!             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 9999 )
-!             RETURN
-!          ENDIF
+!
 …
 !--       No arrays to output. Close the netcdf file and return.
           IF ( i == 1 )  RETURN
-!             nc_stat = NF90_CLOSE( id_set_yz(av) )
-!             IF ( nc_stat /= NF90_NOERR )  CALL handle_netcdf_error( 9999 )
-!             RETURN
-!          ENDIF
+!

palm/trunk/SOURCE/parin.f90

-                      r46
+                      r48
 ! Actual revisions:
 ! -----------------
 ! +netcdf_64bit_3d in d3par
+! +netcdf_64bit_3d in d3par, -data_output_ts
+!
 ! Former revisions:
 …
                        cross_normalized_y, cross_profiles, cross_ts_uymax, &
                        cross_ts_uymin, cross_xtext, cycle_mg, data_output, &
                        data_output_format, data_output_pr, data_output_ts, &
+                       data_output_format, data_output_pr, &
                        data_output_2d_on_each_pe, disturbance_amplitude, &
                        disturbance_energy_limit, disturbance_level_b, &

palm/trunk/SOURCE/time_integration.f90

r46	r48
380	380	!-- Graphic output for time series
381	381	IF ( time_dots >= dt_dots ) THEN
382		~~IF ( dots_n /= 0 )~~ CALL data_output_tseries
	382	CALL data_output_tseries
383	383	time_dots = MOD( time_dots, MAX( dt_dots, dt_3d ) )
384	384	ENDIF

palm/trunk/SOURCE/user_interface.f90

-                      r46
+                      r48
 ! -----------------
 ! New routine user_init_3d_model which allows the initial setting of all 3d
+! arrays under control of the user
+! arrays under control of the user,
+! routine user_statistics now has one argument (sr),
+! sample for generating time series quantities added
+!
 ! Former revisions:
 …
 !       ENDDO
 !    ENDIF
+!
+!-- Sample for user-defined time series
+!-- For each time series quantity you have to give a label and a unit,
+!-- which will be used for the NetCDF file. They must not contain more than
+!-- seven characters. The value of dots_num has to be increased by the
+!-- number of new time series quantities. Its old value has to be store in
+!-- dots_num_palm. See routine user_statistics on how to output calculate
+!-- and output these quantities.
+!    dots_label(dots_num+1) = 'abs_umx'
+!    dots_unit(dots_num+1)  = 'm/s'
+!    dots_label(dots_num+2) = 'abs_vmx'
+!    dots_unit(dots_num+2)  = 'm/s'
+!
+!    dots_num_palm = dots_num
+!    dots_num = dots_num + 2
  END SUBROUTINE user_init
 …
  SUBROUTINE user_statistics
+ SUBROUTINE user_statistics( sr )
 !------------------------------------------------------------------------------!
 …
 ! ------------
 ! Calculation of user-defined statistics
+! This routine is called for every statistic region sr defined by the user,
+! but at least for the region "total domain" (sr=0).
 !------------------------------------------------------------------------------!
 …
     IMPLICIT NONE
+    INTEGER ::  sr
+!
+!-- Sample on how to add values for the user-defined time series quantities.
+!-- These have to be defined before in routine user_init. This sample
+!-- creates two time series for the absolut values of the horizontal
+!-- velocities u and v.
+!    ts_value(dots_num_palm+1,sr) = ABS( u_max )
+!    ts_value(dots_num_palm+2,sr) = ABS( v_max )
  END SUBROUTINE user_statistics

Context Navigation

Legend:

palm/trunk/DOC/app/chapter_3.4.html

palm/trunk/DOC/app/chapter_3.5.1.html

palm/trunk/DOC/app/chapter_3.5.3.html

palm/trunk/DOC/app/chapter_4.1.html

palm/trunk/DOC/app/chapter_4.2.html

palm/trunk/DOC/app/chapter_4.3.html

palm/trunk/DOC/app/chapter_4.5.1.html

palm/trunk/DOC/app/chapter_4.5.3.html

palm/trunk/DOC/app/chapter_4.6.html

palm/trunk/SOURCE/CURRENT_MODIFICATIONS

palm/trunk/SOURCE/Makefile

palm/trunk/SOURCE/check_parameters.f90

palm/trunk/SOURCE/data_output_tseries.f90

palm/trunk/SOURCE/flow_statistics.f90

palm/trunk/SOURCE/init_3d_model.f90

palm/trunk/SOURCE/init_grid.f90

palm/trunk/SOURCE/modules.f90

palm/trunk/SOURCE/netcdf.f90

palm/trunk/SOURCE/parin.f90

palm/trunk/SOURCE/time_integration.f90

palm/trunk/SOURCE/user_interface.f90

Download in other formats: