Index: palm/trunk/DOC/app/chapter_1.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_1.0.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_1.0.html	(revision 5)
@@ -0,0 +1,87 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta content="text/html; charset=windows-1252"
+ http-equiv="CONTENT-TYPE">
+  <title>PALM chapter 1.0</title>
+  <meta content="StarOffice 7  (Win32)" name="GENERATOR">
+  <meta content="Marcus Oliver Letzel" name="AUTHOR">
+  <meta content="20040719;13375546" name="CREATED">
+  <meta content="20041112;13163393" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body lang="de-DE" dir="ltr">
+<h2 style="line-height: 100%;"><font size="4">1.0 Introduction</font></h2>
+<p style="line-height: 100%;">This documentation wants to give
+assistance how to carry out runs with the large eddy simulation
+model <span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">PALM.</span>
+It contains
+<font color="#000000">instructions</font><font color="#800000"> </font>for
+the installation of the model (<a href="chapter_5.0.html">chapter
+5.0</a>), for the practical execution of application runs (<a
+ href="chapter_3.0.html">chapter
+3.0</a>) and for the steering of the model by parameters (<a
+ href="chapter_4.0.html">chapter
+4.0</a>). New users should first of all read <a href="chapter_2.0.html">chapters
+2.0</a> and <a href="chapter_3.0.html">3.0</a>
+(up to and including <a href="chapter_3.5.html">3.5</a>).
+</p>
+<p style="line-height: 100%;"><b>This documentation does not explain
+the <font color="#000000">mathematical,</font> numerical and physical
+background of large eddy simulation models and it also does not
+provide appropriate meteorological background knowledge. Good
+knowledge concerning this is presupposed and is indispensable for a
+successful application of the model.</b> In addition to this,
+knowledge of the operating system<span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
+Unix, </span>the <span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">Queueing
+System (NQS, PBS, Load Leveler, etc.)</span> to generate batch jobs,
+the basic functionality of <font color="#000000">parallel computers
+</font>and the programming language <span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">FORTRAN90
+(particularly</span>, if code extensions are to be written by the
+user) are presupposed. Programming user-defined software usually
+requires exact knowledge of the internal model structure. First insight
+herei<span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">n
+<font color="#000000">is
+given</font></span> in <a href="chapter_2.0.html">chapter
+2.0</a> and in the <a href="../tec/index.html">technical/numerical
+documentation</a>. The information obtained there is usually not
+<font color="#000000">sufficient</font> and has to be accompanied by
+detailed study of the source code of the model. A<span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">dditional
+</span>experience in parallel programming with the
+message passing interface<span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
+(MPI)</span> maybe presupposed. </p>
+<p style="line-height: 100%;">A documentation lives on criticism and
+suggestions by users. T<font color="#000000">hi</font>s is expressly
+requested. Please contact&nbsp; the PALM group
+(<span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">see
+<a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">members</a></span>).
+The model documentation is regularly maintained and brought up-to-date
+by the PALM group. The date of the last code
+revision is specified at the top of the table of contents of this
+documentation. <br>
+&nbsp;
+</p>
+<hr><font color="#000080"><font color="#000080"><br>
+<a href="index.html"><font color="#000080"><img width="32" height="32"
+ border="2" align="bottom" name="Grafik1" src="up.gif"></font></a><a
+ href="chapter_2.0.html"><font color="#000080"><img width="32"
+ height="32" border="2" align="bottom" name="Grafik2" src="right.gif"></font></a></font></font><br>
+<br>
+<span style="font-style: italic;">Last change:</span> 14/04/05 (SR)<br>
+<br>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_2.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_2.0.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_2.0.html	(revision 5)
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta content="text/html; charset=windows-1252"
+ http-equiv="CONTENT-TYPE">
+  <title>PALM chapter 2.0</title>
+  <meta content="StarOffice 7  (Win32)" name="GENERATOR">
+  <meta content="Marcus Oliver Letzel" name="AUTHOR">
+  <meta content="20040719;14534028" name="CREATED">
+  <meta content="20041117;10385730" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body lang="en-US" dir="ltr">
+<h2 style="line-height: 100%;"><font size="4">2.0 Basic techniques of
+the LES model and its parallelization </font>
+</h2>
+<p style="line-height: 100%;">LES models generally permit the
+simulation of turbulent flows, whereby those eddies, that carry the
+main energy are resolved by the numerical grid. Only the
+effect of such turbulence elements with diameter equal to or smaller
+than the grid spacing are parameterized in the model and
+by so-called subgrid-scale (SGS) transport. Larger structures are
+simulated directly (they are explicitly resolved) and their effects are
+represented by the advection terms. </p>
+<p style="font-style: normal; line-height: 100%;">PALM is based on the
+non-hydrostatic incompressible Boussinesq equations. It contains a
+water cycle with cloud formation and takes into account infrared
+radiative cooling in cloudy conditions. The model has six prognostic
+quantities in total  u,v,w, liquid water potential temperature
+<font face="Thorndale, serif">&#920;</font><sub>l </sub>(BETTS,
+1973), total water content q and subgrid-scale turbulent kinetic energy
+e. The
+subgrid-scale turbulence is modeled according to DEARDOFF (1980) and
+requires the solution of an additional prognostic equation for the
+turbulent kinetic energy e. The long wave radiation scheme is based
+on the parametrization of cloud effective emissivity (e.g. Cox, 1976)
+and condensation is considered by a simple '0%-or-100%'-scheme, which
+assumes that within each grid box the air is either entirely
+unsaturated or entirely saturated ( see e.g., CUIJPERS and DUYNKERKE,
+1993). The water cycle is closed by using a simplified version of
+KESSLERs scheme (KESSLER, 1965; 1969) to parameterize precipitation
+processes (MÜLLER and CHLOND, 1996). Incompressibility is
+applied by means of a Poisson equation for pressure, which is solved
+with a direct method (SCHUMANN and SWEET, 1988). The Poisson equation
+is Fourier transformed in both horizontal directions and the
+resulting tridiagonal matrix is solved for the transformed pressure
+which is then transformed back. Alternatively, a multigrid method can
+also be used. Lateral boundary conditions of the model are cyclic and
+MONIN-OBUKHOV similarity is assumed between the surface and the first
+computational grid level above. Alternatively, noncyclic boundary
+conditions
+(Dirichlet/Neumann) can be used along one of the
+horizontal directions. At the lower surface, either temperature/
+humidity or their respective fluxes can be prescribed. </p>
+<p style="font-style: normal; line-height: 100%;">The advection terms
+are treated by the scheme proposed by PIACSEK and WILLIAMS (1970),
+which conserves the integral of linear and quadratic quantities up to
+very small errors. The advection of scalar quantities can optionally
+be performed by the monotone, locally modified version of Botts
+advection scheme (CHLOND, 1994). The time integration is performed
+with the third-order Runge-Kutta scheme. A second-order Runge-Kutta
+scheme, a leapfrog scheme and an Euler scheme are also implemented.</p>
+<p style="line-height: 100%;">By default, the time step is computed
+with respect to the different criteria (CFL, diffusion) and adapted
+automatically. In case of a non-zero geostrophic
+wind the coordinate system can be moved along with the mean wind in
+order to maximize the time step (Galilei-Transformation). </p>
+<p style="font-style: normal; line-height: 100%;">In principle a model
+run is carried out in the following way: After reading the control
+parameters given by the user, all prognostic variables are
+initialized. Initial values can be e.g. vertical profiles of the
+horizontal wind, calculated using a 1D subset of the 3D prognostic
+equation and are set in the 3D-Model as horizontally homogeneous
+initial values. Temperature profiles can only be prescribed linear
+(with constant gradients, which may change for different vertical
+height intervals) and they are assumed in the 1D-Model as stationary.
+After the initialization phase during which also different kinds of
+disturbances may be imposed to the prognostic fields, the time
+integration begins. Here for each individual time step the prognostic
+equations are successively solved for the velocity components u, v and
+w
+as well as for the potential temperature and possibly for the TKE.
+After the calculation of the boundary values in accordance with the
+given boundary conditions the provisional velocity fields are
+corrected with the help of the pressure solver. Following this, all
+diagnostic turbulence quantities including possible
+Prandtl-layerquantities are computed. At the end of a time
+step the data output requested by the user is made
+(e.g. statistic of analyses for control purposes or profiles and/or
+graphics data). If the given end-time was reached, binary data maybe
+be saved for restart. </p>
+<p style="font-style: normal; line-height: 100%;">The model is based
+on the originally non-parallel LES model which has been operated at the
+institute since 1989
+and which was parallelized for massively parallel computers with
+distributed memory using the Message-Passing-Standard MPI. It is
+still applicable on a single processor and also well optimized for
+vector machines. The parallelization takes place via a so-called domain
+decomposition, which divides the entire model
+domain into individual, vertically standing cubes, which extend from
+the bottom to the top of the model domain. One processor (processing
+element, PE) is assigned to each cube, which
+accomplishes the computations on all grid points of the subdomain.
+Users can choose between a two- and a one-dimensional domain
+decomposition. A 1D-decomposition is preferred on machines with a
+slow&nbsp; network interconnection. In case of a 1D-decomposition, the
+grid points along x direction are
+distributed among the individual processors, but in y- and z-direction
+all respective grid points belong to the same PE. </p>
+<p style="line-height: 100%;">The calculation of central differences or
+non-local arithmetic operations (e.g. global
+sums, FFT) demands communication and an appropriate data exchange
+between the PEs. As a substantial innovation in relation to
+the non-parallel model version the individual subdomains are
+surrounded by so-called ghost points, which contain the grid point
+information of the neighbor processors. The appropriate grid point
+values must be exchanged after each change (i.e. in particular after
+each time step). For this purpose MPI routines (<tt>MPI_SENDRCV</tt>)
+are used. For the solution of the FFT conventional (non-parallelized)
+procedures are used. Given that the FFTs are used in x and/or
+y-direction, the data which lie distributed on the individual central
+processing elements, have to be collected and/or relocated before.
+This happens by means of the routine <tt>MPI_ALLTOALLV</tt>. Certain
+global operations like e.g. the search for absolute maxima or minima
+within the 3D-arrays likewise require the employment of special MPI
+routines (<tt>MPI_ALLREDUCE</tt>). </p>
+<p style="line-height: 100%;">Further details of the internal model
+structure are described in the <a href="../tec/index.html">technical/numerical
+documentation</a>. <br>
+&nbsp; </p>
+<hr><font color="#000080"><font color="#000080"><br>
+<a href="chapter_1.0.html"><font color="#000080"><img width="32"
+ height="32" border="2" align="bottom" name="Grafik1" src="left.gif"></font></a><a
+ href="index.html"><font color="#000080"><img width="32" height="32"
+ border="2" align="bottom" name="Grafik2" src="up.gif"></font></a><a
+ href="chapter_3.0.html"><font color="#000080"><img width="32"
+ height="32" border="2" align="bottom" name="Grafik3" src="right.gif"></font></a><br>
+</font></font><br>
+<p style="line-height: 100%;"><span style="font-style: italic;">Last
+change: </span>14/04/05 (SR)<font color="#000080"><font color="#000080"><br>
+</font></font></p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.0.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.0.html	(revision 5)
@@ -0,0 +1,123 @@
+<!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.0</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Marcus Oliver Letzel">
+  <meta name="CREATED" content="20040723;15213734">
+  <meta name="CHANGED" content="20041112;13170538">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h2 style="font-style: normal; line-height: 100%;"><font size="4">3.0
+Execution of model runs</font></h2>
+<p style="line-height: 100%;">Given that the model was
+installed by the user (look at <a href="chapter_5.0.html">chapter
+5.0</a>) and that it is clear, which phenomenon is to be simulated,
+there is a whole set of questions which must be answered before
+executing
+the actual application run, e.g.: </p>
+<ul>
+  <li>
+    <p
+ style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
+large does the model domain have to be and what grid size does
+phenomenon to be simulated require? </p>
+  </li>
+  <li>
+    <p
+ style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
+long is the time which should be simulated, i.e. which typical time
+scale does the phenomenon have? </p>
+  </li>
+  <li>
+    <p
+ style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">Which
+boundary conditions and initial conditions are to be selected? </p>
+  </li>
+  <li>
+    <p style="font-style: normal; line-height: 100%;">Which model
+output data are necessary at which points in time, in order to be able
+to analyze the phenomenon afterwards? </p>
+  </li>
+</ul>
+<p style="line-height: 100%;">The answers to these questions
+substantially determine the choice of values for the most important
+model parameters, with which the model run is steered. All possible
+parameters are described in chapters <a href="chapter_4.1.html">4.1</a>,
+<a href="chapter_4.2.html">4.2</a>
+and <a href="chapter_4.3.html">4.3</a>.
+The basic steering of the model with these parameters is explained in
+the introduction to <a href="chapter_4.0.html">chapter
+4</a>. The user will rarely use all model parameters, since many are
+preset with consistent default values and therefore do not have to be
+changed by the user. Some of the most important parameters are not
+preset with default values and must be adjusted by the user in each
+case. Such a typical, minimum parameter set is described in <a
+ href="chapter_4.4.html">chapter
+4.4</a>. For the subsequent analysis of model runs, graphical
+visualization of model data is particularly important. <a
+ href="chapter_4.5.html">Chapter
+4.5</a> describes, how such outputs are produced with the model. </p>
+<p style="line-height: 100%;">The selected parameters and their values
+have to be supplied to the model as an input file. The
+structure of this file is described in the introduction to <a
+ href="chapter_4.0.html">chapter
+4</a>. The data, produced by the model, are located in a number of
+different output files. The model works with relative file names
+(i.e. without absolute path information). Thus all input and output
+files are
+expected and put in the directory, in which the actual model (the
+executable program created from the FORTRAN source code) is started
+(but also see next paragraph).
+All user-relevant input and output files are described in <a
+ href="chapter_3.4.html">chapter
+3.4</a>. </p>
+<p style="line-height: 100%;">The actual model (the executable
+program) is not started directly via the user, but with the help of
+the shell script <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>,which
+can be called by the user. This script takes over the entire pre- and
+postprocessing work, which is necessary for a model run. In addition
+to this, it generates e.g. automatically batch jobs for model runs on
+remote computers, provides for the appropriate file transfers of the
+input and output files to these computers, secures data on existing
+archives systems, starts if necessary restart jobs, and much more.
+<span style="font-weight: bold;">mrun</span> allows to specify
+individual path names for each simulation and
+for the different types of input/output files. The start of model runs
+with <b>mrun</b> is described in <a href="chapter_3.1.html">chapter
+3.1</a>. </p>
+<p style="line-height: 100%;">The implementation of user code
+extensions in
+the model is made possible by a set of defined interfaces. You will
+find references to the programming of such extensions in <a
+ href="chapter_3.5.html">chapter
+3.5</a>. Frequently errors arise during the execution of the model
+after such changes, which can often be found only by interactive
+model steering and error tracing (debugging), which are described in
+<a href="chapter_3.6.html">chapter
+3.6</a>. </p>
+<hr>
+<p style="font-style: normal; line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_2.0.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.1.html"><font
+ color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
+ border="2" height="32" width="32"></font></a></font></font>
+<br>
+</p>
+<p style="font-style: normal; line-height: 100%;"><span
+ style="font-style: italic;">Last change:</span> 14/04/05 (SR)<br>
+</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.1.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.1.html	(revision 5)
@@ -0,0 +1,134 @@
+<!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.1</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Marcus Oliver Letzel">
+  <meta name="CREATED" content="20040806;13565279">
+  <meta name="CHANGED" content="20040806;13575492">
+  <meta name="KEYWORDS" content="parallel LES model">
+</head>
+<body dir="ltr" lang="de-DE">
+<h3 style="line-height: 100%;">3.1 Job control with mrun</h3>
+<p style="line-height: 100%;">The start of model runs in principle
+takes place via executing the shell script <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun.</a>
+With this script it is possible to operate the model both
+interactively and in batch mode. Batch operation is possible on the
+local computer as well as on a remote computer (supposed that a batch
+queuing system is available). Here only the batch operation on a remote
+computer is
+described, because this represents the usual mode of operation due to
+the large computing time requirements of the model. The interactive
+execution differs only in some points and is described in <a
+ href="chapter_3.6.html">chapter
+3.6</a>. </p>
+<p style="line-height: 100%;">By the call of <b>mrun </b>a complete
+batch job is produced, transferred to the user determined remote
+computer
+and submitted to its queuing system (LoadLeveler, PBS, etc.).
+After processing of the job, the so-called job protocol is sent back
+to the local computer of the user (the local computer is the
+computer, on which the user calls <b>mrun</b>). The following actions
+are implemented by the job, amongst other: </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">Change to a
+temporary working directory. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">The input files
+needed by the model are copied into this directory. These files are
+transferred from the local computer. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">Execute the
+model. </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">Copy the output
+files produced by the model into the directories determined by the user
+(these are also allowed to lie on the local computer). Depending on the
+choice of the user, the files may also be saved on an archiving system
+(if existing). </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">Delete the
+temporary working direction. </p>
+  </li>
+  <li>
+    <p style="line-height: 100%;">Transfer the job protocol to the
+local computer. </p>
+  </li>
+</ul>
+<p style="line-height: 100%;">From this list it becomes clear that two
+of the substantial functions of <b>mrun</b> are the supply of input
+files for the model and the storage of output files produced by the
+model. The model exclusively works with so-called local files, which
+lie in the temporary working directory created by <b>mrun.</b> The
+local names of these files are determined by the model
+(in the appropriate OPEN instructions). In <a href="chapter_3.4.html">chapter
+3.4</a> all possible input and output filenames are specified. In
+contrast to this, the input files, made available by the user,
+usually lie in permanent directories (e.g. in the /home directory) and
+the output data, produced by the model, may also be
+stored there. The directory names are arbitrary. The actual file name
+(without path) of these input and output files is specified by an
+option of <b>mrun</b>. All input and output files of the model
+receive this file name (e.g. <i>abcde</i>), but each individual file
+is still provided with an extension (e.g. <i>abcde_par</i>, etc.
+<i>abcde_dat</i>) - otherwise the files would not be distinguishable.
+The linkage of local file names with the names of the permanent
+directories and the file name extensions takes place in a
+configuration file, which <b>mrun</b> expects to find in the
+respective current working directory of the user. A detailed
+description of this configuration file - which still offers a variety
+of further functions  is found in the
+documentation of the shell script <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>
+(sorry: this is only available in German, so far. If you think that you
+would profit from an English version, please give a message to the PALM
+group).
+In the next chapter a simple example of a minimum configuration file
+is described. </p>
+<p style="line-height: 100%;">A simple call of <b>mrun</b> could read
+as follows: </p>
+<ul>
+  <p style="line-height: 100%;"><tt>mrun - h <i>ibmh</i> -d <i>abcde</i></tt></p>
+</ul>
+<p style="line-height: 100%;">The model is started by option -<tt>h
+<i>ibmh</i></tt> on the IBM Regatta hanni at the HLRN, i.e. on the
+local computer a batch job is generated, transferred to the remote
+computer (IBM) and submitted to a suitable queue of the queuing system.
+With the
+option <tt>-d</tt> the so-called basis file name (<i>abcde</i>) is
+specified, from which, together with the path names and file name
+extensions, the complete file names (including the path) of the
+permanent input and output files are <font color="#000000">formed.</font><font
+ color="#800000">
+</font>Usually the specification of a set of further options is
+necessary, e.g. the CPU time needed by the model and the memory size
+needed as well as, on parallel computers, the number of processing
+elements which are to be used (options <tt>-t</tt>, <tt>-m</tt> and
+<tt>-X</tt>). A precondition for the call of <b>mrun</b> of course is
+that the installation of the model on the local computer and the
+remote machine is complete (see <a href="chapter_5.0.html">chapter
+5.0</a>). </p>
+<p>Beyond these options a variety of further options for model
+steering can be used in the call of <b>mrun</b>. These are fully
+described in the <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>
+documentation (in German). <br>
+&nbsp; </p>
+<hr>
+<p><a href="chapter_3.0.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.2.html"><font color="#000080"><img src="right.gif"
+ name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></p>
+<p><i>Last change:&nbsp;</i> 14/04/05 (SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.2.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.2.html	(revision 5)
@@ -0,0 +1,398 @@
+<!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.2</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Marcus Oliver Letzel">
+  <meta name="CREATED" content="20040726;13164873">
+  <meta name="CHANGED" content="20050119;9245042">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">3.2 Example of a minimum configuration
+file</h3>
+<p style="line-height: 100%;">In this chapter a sample configuration
+file is described. It contains only instructions which are really
+necessary for the execution of a simple model run (configuration
+files can be much more complex). The example presented here is stored
+in an appropriate <a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">example
+file</a> (containing more than the configuration data presented here)
+and can be used, together with the <a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">parameter
+file</a> presented in <a href="chapter_4.4.html">chapter
+4.4</a>, for the execution of a simple model run. In chapter 4.4 the
+complete <b>mrun</b> options which are necessary for the appropriate
+parameter file are described. Furthermore not all details of the
+configuration file are described here. Therefore you should take a
+look at the <a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a>
+documentation (sorry: this is only available in German, so far. If you
+think that you
+would profit from an English version, please give a message to the PALM
+group). </p>
+<p style="line-height: 100%;">The following configuration data
+exclusively applies to model runs on the IBM Regatta hanni of the
+HLRN when using several processing elements (i.e. for the parallel
+version of the model). The proper installation of the model is
+presumed (see <a href="chapter_5.0.html">chapter
+5.0</a>). Furthermore it is supposed that the user is located in the
+directory <tt><font style="font-size: 10pt;" size="2">$HOME/palm/current_version/SOURCE</font></tt>
+on its local computer. There are the FORTRAN source codes of the
+model (<tt><font style="font-size: 10pt;" size="2">*.f90</font></tt>)
+as
+well as the configuration file (name: <tt><font
+ style="font-size: 10pt;" size="2">.mrun.config</font></tt>)
+and the make file (name: <tt><font style="font-size: 10pt;" size="2">Makefile</font></tt>).
+The configuration file has the following contents (among other things):
+<br>
+&nbsp;
+</p>
+<pre style="line-height: 100%;"><font style="font-size: 10pt;" size="2">% source_path  <i>$HOME/palm/current_version/SOURCE</i></font><br><font
+ style="font-size: 10pt;" size="2">% mainprog     <i>palm.f90</i></font><br><font
+ style="font-size: 10pt;" size="2">% use_makefile <i>true</i></font><br><font
+ style="font-size: 10pt;" size="2">% fopts        <i>-O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape    ibmh parallel<span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></i></font><br><font
+ style="font-size: 10pt;" size="2">% lopts        <span
+ style="font-style: italic;">-O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape:-lesslsmp   ibmh parallel</span></font><br><font
+ style="font-size: 10pt;" size="2">#</font><br><font
+ style="font-size: 10pt;" size="2">EC:[[ \$locat = execution]] &amp; &amp; <i>cat </i>RUN_CONTROL </font><br><font
+ style="font-size: 10pt;" size="2">#</font><br><a
+ href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font
+ style="font-size: 10pt;" size="2">        in:job:npe d3#   ~/palm/current_version/JOBS/$fname/INPUT      _p3d</font><br><font
+ style="font-size: 10pt;" size="2">#</font><br><a
+ href="chapter_3.4.html#RUN_CONTROL"><font style="font-size: 10pt;"
+ size="2">RUN_CONTROL</font></a><font style="font-size: 10pt;" size="2">  out:loc:tr d3#   ~/palm/current_version/JOBS/$fname/MONITORING _rc</font><br><a
+ href="chapter_3.4.html#HEADER"><font style="font-size: 10pt;" size="2">HEADER</font></a><font
+ style="font-size: 10pt;" size="2">       out:loc:tr d3#   ~/palm/current_version/JOBS/$fname/MONITORING _header</font><br><a
+ href="chapter_3.4.html#PLOT1D_PAR"><font style="font-size: 10pt;"
+ size="2">PLOT1D_PAR</font></a><font style="font-size: 10pt;" size="2">   out:loc:tr pr#   ~/palm/current_version/JOBS/$fname/OUTPUT     _pr_par</font><br><a
+ href="chapter_3.4.html#PLOT1D_DATA"><font style="font-size: 10pt;"
+ size="2">PLOT1D_DATA</font></a><font style="font-size: 10pt;" size="2">  out:loc:tr pr#   ~/palm/current_version/JOBS/$fname/OUTPUT     _pr_in</font></pre>
+<p style="line-height: 100%;"><font face="Thorndale, serif">The first
+five lines specify values of
+so-called environment variables. Such lines begin with a %-
+sign. After at least one blank the name of the variable</font> <font
+ face="Thorndale, serif">(e.g.
+</font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font
+ face="Thorndale, serif">)
+follows and then seperated by at least one blank the value of the
+variable. Again separated by blank t<font face="Thorndale, serif">he
+so-called validity domain</font> can be indicated (later more).
+With the first three variables <b>mrun</b> gets to know in which
+directory the source code lies (</font><tt><i><font
+ face="Thorndale, serif">source_path</font></i></tt><font
+ face="Thorndale, serif">),
+the file name of the main program (</font><tt><i><font
+ face="Thorndale, serif">mainprog</font></i></tt><font
+ face="Thorndale, serif">)
+and that the <font face="Thorndale, serif">make mechanism should be
+used </font>for compiling (</font><tt><font face="Thorndale, serif"><i>use_makefile
+=</i> <i>true</i></font></tt><font face="Thorndale, serif">). <b>mrun
+</b>needs these information, <font color="#000000">because for each
+model run the executable is created by compiling the source files.</font>
+Normally, only the main program (palm.f90) will be compiled while all
+other object files are just linked. These object files have already
+been created from the source code files during the installation of the
+model
+(see </font><a href="chapter_5.0.html"><font face="Thorndale, serif">chapter
+5.0</font></a><font face="Thorndale, serif">). <b>mrun</b> uses
+certain standard options for the compilation process. Beyond that you
+can
+declare additional options with the environment variable </font><tt><i><font
+ face="Thorndale, serif">fopts</font></i></tt><font
+ face="Thorndale, serif">.
+Within the value assignment of an environment variable in the
+configuration file no blanks must be
+used. If blanks are necessary they must <font face="Thorndale, serif">be
+replaced </font>by colons (:). <b>mrun</b> will
+interpret these colons as blanks (2 colons written one behind the
+other will be interpreted as a colon). Thus in the example above </font><tt><font
+ face="Thorndale, serif">fopts
+has the value </font></tt><font
+ style="font-size: 10pt; font-family: monospace;" size="2"><i>-O3 -g
+-qrealsize=8 -Q -q64 -qmaxmem=-1 -qtune=pwr4 -qarch=pwr4 -qnosave
+-qnoescape</i></font><tt><i><font face="Thorndale, serif"><font
+ color="#000000"></font></font></i></tt><font face="Thorndale, serif"><font
+ color="#000000">.
+Thus a PALM executable is generated using high level optimization (</font></font><font
+ color="#000000"><span
+ style="font-style: italic; font-family: monospace;">-O3</span></font><font
+ face="Thorndale, serif"><font color="#000000">).</font></font><font
+ color="#000000"><font face="Thorndale, serif"> For all other options
+see the compiler manual on the IBM (</font><font size="2"><font
+ face="Cumberland, monospace">man</font></font></font><tt><font
+ color="#000000">
+<font size="2"><font face="Cumberland, monospace">f90</font></font></font></tt><font
+ face="Thorndale, serif"><font color="#000000">). Additional libraries
+which the compiler should use are described by
+the environment variable </font></font><tt><font size="2"><font
+ face="Cumberland, monospace"><font color="#000000">lopts</font></font></font></tt><font
+ color="#000000">
+<font face="Thorndale, serif">(loader options).</font></font><font
+ color="#800000">
+</font><font face="Thorndale, serif"><font color="#000000">Here you
+have to indicate a special IBM library (ESSL, </font></font>Engineering
+and Scientific Subroutine Library)<font face="Thorndale, serif"><font
+ color="#000000">.</font><font color="#800000"> </font>On the
+IBM-Regatta, all compiler options have also to be given to the linker.</font><font
+ color="#000000"><font face="Thorndale, serif"> </font></font>
+</p>
+<p style="line-height: 100%;"><font color="#000000">Compiler and
+loader options usually differ from computer to computer. In the
+configuration file therefore several value assignments for the
+variables </font><tt><font style="font-size: 10pt;" size="2"><font
+ color="#000000">fopts</font></font></tt><font color="#000000">
+and </font><tt><font style="font-size: 10pt;" size="2"><font
+ color="#000000">lopts</font></font></tt><font color="#000000">
+exist which become active for different computers.</font><font
+ color="#800000">
+<font color="#000000">Which value assignment is used is described by
+the so-called validity domain which follows in the appropriate
+variable lines after the value of variables.</font></font><font
+ color="#000000">
+In the example above the entry </font><font color="#000000"><font
+ style="font-size: 11pt; font-style: italic; font-family: monospace;"
+ size="2">ibmh</font></font><tt><font color="#000000"><span
+ style="font-style: italic; font-family: monospace;">
+</span></font><font color="#000000"><i><font style="font-size: 11pt;"
+ size="2">parallel</font></i></font></tt><font color="#000000">
+stands for </font><tt><font style="font-size: 10pt;" size="2"><font
+ color="#000000">fopts</font></font></tt><font color="#000000">
+and </font><tt><font style="font-size: 10pt;" size="2"><font
+ color="#000000">lopts</font></font></tt><font color="#000000">.
+These lines only become active if a run on the parallel computer of
+the HLRN (</font><tt><i><font style="font-size: 10pt;" size="2">ibmh</font></i></tt><font
+ color="#000000">)
+on several <font color="#000000">(</font><tt><i><font
+ style="font-size: 10pt;" size="2"><font color="#000000">parallel</font></font></i></tt><font
+ color="#000000">)
+</font>processors is started. The activation takes place when you
+appropriately specify the <span style="font-weight: bold;">mrun</span>
+options </font><tt><font color="#000000">-h</font></tt><font
+ color="#000000">
+and </font><tt><font color="#000000">-K</font></tt><font
+ color="#000000">
+(see below). This way, the validity domain can be limited also for all
+other environment-variables. If no validity domain
+is indicated then the given values of variables are valid on all
+computers. </font>
+</p>
+<p style="line-height: 100%;">After the value assignment for the
+variables the so-called error commands follow which have to begin with <tt><font
+ style="font-size: 11pt;" size="2">EC:</font></tt>
+in the first column (comment lines begin with <tt>#</tt>). Directly
+after the colon Unix commands follow (korn shell syntax) which are
+processed by <b>mrun</b> if errors arise during
+the model run. The command described in the example (<tt><font
+ style="font-size: 10pt;" size="2">cat
+RUN_CONTROL</font></tt>) is executed thereby only on the
+condition that errors during the execution of the model (<tt><font
+ style="font-size: 10pt;" size="2">execution</font></tt>)
+arise. An <b>mrun </b>internal environment variable which indicates
+the
+respective abort place in case of errors is <tt><a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#locat">locat</a></tt>.
+In order to determine the actual value of this variable at the
+execution of <b>mrun</b> the <tt>$</tt> - prefix
+must be protected by a \ since the configuration file has been
+already interpreted once when reading in through <b>mrun</b> and the
+value from
+<tt>locat</tt> would then supply the empty character string. If
+errors arise during the model run this command
+copies the data written by the model up to then to the local file
+<a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
+on the standard output where they can be checked after
+job end.<font color="#000000"> RUN_CONTROL is an output file of the
+model which has to be copied according to the default configuration
+file
+(see below) after the end of the model run to a permanent file of the
+user but this action would not be performed in case of errors
+in the model run, so that the file content would be lost.</font> With
+the help of the error command one can secure it nevertheless. </p>
+<p style="line-height: 100%;">Before and/or after
+the error commands in the example file you can find the so-called input
+and/or output commands which are implemented before and/or after the
+model run. </p>
+<p style="line-height: 100%;">After the output commands<font
+ color="#000000">
+<font color="#000000">in the example file t</font>he so-called file
+connection statements</font> <font color="#000000">follow </font>via
+which tell <span style="font-weight: bold;">mrun</span> how to connect
+the local files in the temporary working
+directory of the model with the respective permanent files of the user.
+<b>mrun</b> copies the input and output files in accordance with the
+data in these connection statements. The file connection statements are
+explained in detail in the <b>mrun</b>
+description (<a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.3">chapter
+6.3</a>, in German) and are described here only as far as being
+necessary. A
+file connection statement usually consists of entries in 5 columns
+whereby all columns are separated from each other by one or more blanks
+(the blanks define the individual columns). In the
+first column the local file name (e.g. <tt><font size="2">PARIN</font></tt>)
+is given as it is addressed by the model. It must begin directly at
+the start of the line. In the second column the so-called file
+attributes
+are given. These determine whether the file is an input file (<tt><font
+ style="font-size: 10pt;" size="2">in</font></tt>)
+or an output file (<tt><font size="2">out</font></tt>), whether output
+files are to be transferred to the local computer of the user (<tt><font
+ style="font-size: 10pt;" size="2">tr</font></tt>)
+or whether they are to be archived (<font size="2"><font
+ face="Cumberland, monospace">fl</font></font>).
+If a file has several attributes then they are separated by a <font
+ color="#000000">colon
+in each case .</font> </p>
+<p style="line-height: 100%;">With the entries in the third column one
+specifies the conditions under which a file connection statement
+becomes active i.e. under
+which circumstances it is executed by <b>mrun</b>. Then <b>mrun</b>
+copies the appropriate in or output files only if at least one of the
+character strings registered in column 3 (again two or more character
+strings have to be separated from each other by a colon) is
+indicated within the mrun <b>call</b> by the option <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-r">-r</a>.
+Thus a call of the form </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun - h ibmh -d abcde -r d3</font></pre>
+</ul>
+<p style="line-height: 100%;">would lead to the fact that the input
+file with the local name PARIN is made available and the output files
+RUN_CONTROL and HEADER are copied to permanent files. The output
+files PLOT1D_PAR and PLOT1D_DATA are not copied so that their
+contents are not available to the user after the end of the job. If
+these files are to be copied of <b>mrun</b> then the call must be</p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -r "d3 pr"</font></pre>
+</ul>
+<p style="line-height: 100%;">Instead of the option -r you can
+separately address the file connection statements for input and/or
+output files with the options -i and -o. If one likes to make sure with
+these two options that in the example configuration
+file all file connection statements are actually executed then
+the call must be: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -i d3 -o "d3 pr"</font></pre>
+</ul>
+<p style="line-height: 100%;"><font color="#000000">The names of the
+local files assigned permanent files are build from the entries in
+the 4th and 5th column of the file connection statements and the
+value of the <span style="font-weight: bold;">mrun</span> option </font><tt><font
+ style="font-size: 10pt;" size="2"><font color="#000000">-d</font></font></tt><font
+ color="#000000">
+in the following way:</font><font color="#800000"> </font>
+</p>
+<ul>
+  <p style="line-height: 100%;">File name (inclusive path) = value of
+the 4th column + value of the option <tt><font size="2">-d</font></tt>
++ value of the 5th column.</p>
+</ul>
+<p style="line-height: 100%;">The 4th column contains the path name
+whereby <tt><a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#fname">$fname</a></tt>
+is replaced by the value indicated for the option <tt><font size="2">-d</font></tt>.
+The 5th column contains the so-called file name extension. The name
+of the permanent file which was copied by <b>mrun</b> to the local
+file <tt>PARIN</tt> thereby reads: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d.</font></pre>
+</ul>
+<p style="line-height: 100%;">In the same way the names of the
+permanent files of the remaining <font color="#000000">file
+connection statements </font>can be formed. </p>
+<p style="line-height: 100%;">With this example configuration file
+exactly one input file is copied into the temporary working directory
+of the model. This file has the local name <a
+ href="chapter_3.4.html#PARIN">PARIN</a>
+and contains the steering parameters for the model and has to be
+provided by the user for each model run. </p>
+<p style="line-height: 100%;">The example configuration file also
+instructs <b>mrun</b> to copy four output files of the model to
+appropriate permanent files of the user at the end of the run.
+There are timestep information (local file name <tt><a
+ href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a></tt>),
+the so-called header file, in which the values of the most selected
+parameters for this run (<tt><a href="chapter_3.4.html#HEADER">HEADER</a></tt>)
+are located, as well as a file with data of horizontally averaged
+vertical profiles
+(<tt><a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a></tt>)
+and an associated parameter file (<tt><a
+ href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a></tt>),
+which can be used as input files for the plot program <a
+ href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
+A model run does not presuppose neither the file connection statements
+for
+output files nor their activation. But without declaring AND activating
+them usually the data produced by the model
+are lost after the end of the model run! </p>
+<p style="line-height: 100%;">As already mentioned the configuration
+file offers a variety of further possibilities to steer the
+execution of the model run. Some of them are described in the next
+chapter. Same applies to possible other options of the <b>mrun</b>
+call. For these please refer to the <a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a>
+documentation (in German). An <b>mrun </b>call for the execution of a
+model run
+on several processors on the IBM Regatta "hanni" of the HLRN must be
+supplemented by the following options in each case: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun - K parallel -X 
+ -t 
+ -m 
+</font></pre>
+</ul>
+<p style="line-height: 100%;">Only the indication of <tt><font
+ style="font-size: 11pt;" size="2">-K
+parallel</font></tt> causes the parallel execution of the run on
+several processors (otherwise a scalar execution on one processor is
+accomplished). In addition to this the number of the
+processing elements which shall be used has to be pre-scribed with the
+option <tt><font style="font-size: 10pt;" size="2">-X</font> </tt><font
+ size="2">(</font><font style="font-size: 10pt;" size="2">e.g.
+</font><tt><font style="font-size: 10pt;" size="2">-X 4</font></tt><font
+ size="2">).</font>
+In each case the permitted CPU time in seconds and the required memory
+size in MB must be indicated by the options <tt><font
+ style="font-size: 11pt;" size="2">-t</font></tt>
+and <tt><font style="font-size: 11pt;" size="2">-m</font></tt>,
+respectively<font face="Thorndale, serif">.</font>
+Alternatively, these can be set by the appropriate environment
+variables in the configuration file: </p>
+<blockquote style="line-height: 100%;"><tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">%
+memory&nbsp; <i>1630</i> ibmh parallel</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">%
+cputime <i>1000</i> ibmh parallel</font></font></tt></blockquote>
+<p style="line-height: 100%;">The values indicated there can be
+overridden with the values of the options <tt><font
+ style="font-size: 10pt;" size="2">-t</font></tt>
+and/or <tt><font style="font-size: 10pt;" size="2">-m</font></tt>,
+respectivly. </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.1.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.3.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> 14/04/05 (SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.3.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.3.html	(revision 5)
@@ -0,0 +1,303 @@
+<!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.3</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Marcus Oliver Letzel">
+  <meta name="CREATED" content="20040728;14053490">
+  <meta name="CHANGED" content="20041112;14150257">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">3.3 Initialization and restart runs</h3>
+<p style="line-height: 100%;">A job started by <b>mrun</b> will
+- according to its requested computing time, its memory size
+requirement and
+the number of necessary processing elements (on parallel computers) -
+be queued by the queuing-system of the remote computer into a suitable
+job
+class which fulfills these requirements. Each job class permits only
+jobs with certain maximum requirements (e.g.
+the job class <tt><font style="font-size: 11pt;" size="2">cdev</font></tt>
+on the IBM Regatta "hanni" of the HLRN permits only jobs with no more
+than 7200 seconds required computing time and with using no more than
+32
+processing elements). The job classes are important for the scheduling
+process of&nbsp; the computer. Jobs with small requirements usually
+come to execution
+very fast, jobs with higher requirements must wait longer (sometimes
+several days). </p>
+<p style="line-height: 100%;">Before the start of a model run the user
+must estimate how much CPU time the model will need for the simulation.
+The necessary time in seconds has to be indicated with the mrun
+<b>option</b> <tt><a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-t">-t</a></tt>
+and has an influence on the job class into which the job is queued. Due
+to the fact that the model usually uses a variable
+time step and thus the number of time steps to be executed and
+consequently the time needed by the model is not
+known at the beginning, this can be measured only very roughly in
+many cases. So it may happen that the model needs more time than
+indicated for the option <tt><u><font style="font-size: 10pt;" size="2">-t</font></u>,</tt>
+which normally leads to an abort of the job as soon as the available
+CPU time is consumed. In principle one could solve this problem by
+setting a very generously estimated value for <u><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-t</font></font></u>,
+but this will possibly lead to the disadvantage that the queued job has
+to wait longer for execution.<br>
+</p>
+<p style="line-height: 100%;">To avoid this problem <b>mrun </b>offers
+the possibility of so-called <b>restart runs</b>. During the model
+run PALM continuously examines how much time is left for the
+execution of the job. If the run is not completed and finished shortly
+before
+expiration of this time, the model stops and writes down the values
+of (nearly) all model variables in binary form to a file (local name
+<a href="chapter_3.4.html#BINOUT">BINOUT</a>).
+After copying the output files required by the user, <b>mrun</b>
+automatically starts a restart run. For this purpose a new <b>mrun</b>
+call is set off automatically on the local computer of the user; <b>mrun</b>
+thus calls itself. The options with this call correspond to a large
+extent to those which the user had selected with his initial call of <b>mrun</b>.
+The model restarts and this time at the beginning it reads in the
+binary data written before and continues the run with them. If in
+this job the CPU time is not sufficient either, in order to terminate
+the run, at the end of the job another restart run is started, etc.,
+until the time which shall be simulated by the model, is reached.
+Thus a set of restart runs can develop - a so-called job chain. The
+first run of this chain (model start at t=0) is called
+<b>initial run</b>. </p>
+<p style="line-height: 100%;">Working with restart runs and their
+generation through <b>mrun</b> requires certain entries in the
+mrun-configuration file and in the parameter file, which are
+described and explained in the following. The configuration file must
+contain the following entries (example for the IBM Regatta of the
+HLRN): </p>
+<ul>
+  <pre style="line-height: 100%;"><font style="font-size: 10pt;"
+ size="2">%write_binary    true    restart</font><br><font
+ style="font-size: 10pt;" size="2">#</font><br><a
+ href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font
+ style="font-size: 10pt;" size="2">   in:job:npe   d3#   ~/palm/current_version/JOBS/$fname/INPUT    _p3d</font><br><font
+ style="font-size: 10pt;" size="2">PARIN   in:job:npe   d3f   ~/palm/current_version/JOBS/$fname/INPUT    _p3df</font><br><a
+ href="chapter_3.4.html#BININ"><font style="font-size: 10pt;" size="2">BININ</font></a><font
+ style="font-size: 10pt;" size="2">   in:loc       d3f   ~/palm/current_version/JOBS/$fname/OUTPUT   _d3d</font><br><font
+ style="font-size: 10pt;" size="2">#</font><br><a
+ href="chapter_3.4.html#BINOUT"><font style="font-size: 10pt;" size="2">BINOUT</font></a><font
+ style="font-size: 10pt;" size="2">  out:loc   restart  ~/palm/current_version/JOBS/$fname/OUTPUT   _d3d</font></pre>
+</ul>
+<p style="line-height: 100%;">The <b>mrun</b> call for the
+initialization run of the job chain must look as follows: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -t 900 -r "d3# restart"</font></pre>
+</ul>
+<p style="line-height: 100%;">The specification of the environment
+variable <tt><tt><font style="font-size: 10pt;" size="2">writ</font></tt></tt><tt><tt><font
+ style="font-size: 10pt;" size="2">e_binary</font><font
+ style="font-size: 11pt;" size="2">, </font></tt></tt>which must be
+assigned the value <tt><tt><font style="font-size: 10pt;" size="2">true</font></tt></tt>,
+is essential. Only in this case the model writes
+binary-coded data for a possible restart run to the local file <tt><tt><a
+ href="chapter_3.4.html#BINOUT">BINOUT</a></tt></tt>
+at the end of the run. Then of course this output file must be stored
+on a permanent file with an appropriate file connection statement
+(last line of the example above). As you can see, both instructions
+(variable declaration and connection statements) are only carried out
+by <b>mrun</b>, if the character string <tt><tt><font
+ style="font-size: 10pt;" size="2">restart</font></tt></tt>
+is given for the option <tt><font style="font-size: 10pt;" size="2">-r</font>
+</tt>in the <span style="font-weight: bold;">mrun</span> call. Thus
+the example above can also be used
+if no restart runs are intended. In such cases the character string
+<tt><tt><font style="font-size: 10pt;" size="2">restart</font></tt></tt>
+with the option <tt><font style="font-size: 10pt;" size="2">-r</font></tt>
+can simply be omitted. </p>
+<p style="line-height: 100%;">Only by the specification of
+<tt><font style="font-size: 10pt;" size="2">write_binary=true</font><font
+ style="font-size: 11pt;" size="2">
+</font><font face="Thorndale, serif">the</font></tt> model is
+instructed to compute the remaining CPU time after each time step and
+stop, if the run is not going to be completed and finished briefly
+before expiration of
+this time. Actually the stop takes place when the
+difference from the available job time (determined by the <b>mrun</b>
+option <tt><font style="font-size: 10pt;" size="2">-t</font></tt>) and
+the time used so far by the job becomes smaller than the time given
+by the model variable <a
+ href="chapter_4.2.html#termination_time_needed">termination_time_needed</a>.
+With the variable <b>termination_time_needed </b>the user determines,
+how much time is needed for binary copying of the data for restart
+runs, as
+well as for the following data archiving and transfer of result data
+etc. (as long as this is part of the job). Thus, as soon as the
+remaining job time is less than <b>termination_time_needed</b>, the
+model stops
+the time step procedure and copies the data for a restart run to the
+local binary file BINOUT. The so-called initialization parameters are
+also written to this file (see <a href="chapter_4.0.html">chapter
+4.0</a>). In a last step the model produces another file with the
+local name CONTINUE_RUN. The presence of this file signals <b>mrun</b>
+the fact that a restart run must be started and leads to the
+start of an appropriate job. </p>
+<p style="line-height: 100%;"><font color="#000000">During the initial
+phase of a restart ru</font>n different actions than during the initial
+phase of an initial run of the model are neccessary. In this
+case the model must read in the binary data written by the preceding
+run at the beginning of the run. Beyond that it also reads the
+initialization parameters from this file. Therefore these do not need
+to be indicated in the parameter file (local name <a
+ href="chapter_3.4.html#PARIN">PARIN</a>).
+If they are indicated nevertheless and if their value deviates from
+their value of the initial run, then this is ignored. There is
+exactly one exception to this rule: with the help of the
+initialization parameter <a
+ href="chapter_4.1.html#initializing_actions">initializing_actions</a>
+it is determined whether the job is a restart run or an
+initial run. If <b>initializing_actions</b> =
+<i>read_restart_data</i>, then it is a restart
+run, otherwise an initial run. The previous remarks make it
+clear that the model obviously needs two different parameter files
+(local name PARIN) for the case of job chains. One is needed for the
+initial run and contains all initialization parameters set by
+the user and the other one is needed for restart runs. The
+last one only contains the initialization parameter
+<b>initializing_actions</b> (also, initialization
+parameters with values different from the initial run may appear in
+this file, but they will be ignored), which
+must have the value <i>read_restart_data</i>.
+Therefore the user must produce two different parameter files if he
+wants to operate job chains. Since the model always expects the
+parameter file on the local file <tt>PARIN</tt>, two different file
+connection statements must be given for this file in the
+configuration file. One may be active only at the initial run,
+the other one only at restart runs. The <b>mrun </b>call for the
+initial run shown above activates the first of the two
+specified connection statements, because the character string <tt><font
+ style="font-size: 10pt;" size="2">d3#</font></tt>
+with the option <tt><font style="font-size: 10pt;" size="2">-r</font></tt>
+coincides with the character
+string in the third column of the connection statement. Obviously
+the next statement must be active</p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font></pre>
+</ul>
+<p style="line-height: 100%;">with the restart runs. Given that t<font
+ color="#000000">his statement only gets</font> active if the option <tt><font
+ style="font-size: 10pt;" size="2">-r</font></tt> is given the value
+<tt><font style="font-size: 11pt;" size="2">d3f</font></tt> and that
+the <b>mrun</b> call for this restart run is produced
+automatically (thus not by the user), <b>mrun</b> obviously has to
+replace <tt><font style="font-size: 10pt;" size="2">"d3#"</font></tt>
+of the initial run with <tt><tt><font style="font-size: 10pt;" size="2">"d3f"</font>
+</tt></tt>within the call of this restart run. Actually, with restart
+runs all <tt><font style="font-size: 10pt;" size="2">"#"</font></tt>
+characters within the strings given for the options <tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-r</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">-i</font></font></tt>
+and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> are
+replaced by <tt><font style="font-size: 10pt;" size="2">f</font></tt>.
+</p>
+<p style="line-height: 100%;">For example, for the initial run
+the permanent file </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d</pre>
+</ul>
+<p style="line-height: 100%;">and for restart runs the permanent file<span
+ style="font-family: monospace;"> </span></p>
+<ul style="font-family: monospace;">
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3df</font></pre>
+</ul>
+<p style="line-height: 100%;">is used. Only with restart runs the
+local file <tt>BININ</tt> is made available as input file, because
+the appropriate file connection statement also contains the
+character string <tt><font style="font-size: 10pt;" size="2">"d3f"</font></tt>
+in the third column. This is logical and necessary since in BININ the
+binary data, produced by the model of the preceding job of the chain,
+are expected and the initial run does not need these
+data The permanent names of this input file (local name BININ) and
+the corresponding output file (local name BINOUT) are identical and
+read </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/OUTPUT/abcde_d3d.</font></pre>
+</ul>
+<p style="line-height: 100%;">However, after the file produced by the
+previous job was read in by the model and after at the local file
+<tt>BINOUT </tt>was produced at the end of the job, the
+restart job does not overwrite this permanent file (<tt>
+/<font
+ style="font-size: 10pt;" size="2">abcde_d3d</font></tt>)
+with the new data. Instead of that, it is examined whether already
+a permanent file with the name <tt><font style="font-size: 10pt;"
+ size="2">
+/abcde_d3d</font>
+<font face="Thorndale, serif">exists </font></tt>when copying the
+output file (<tt><font style="font-size: 10pt;" size="2">BINOUT</font></tt>)
+of <b>mrun</b>. If this is the case, <tt><font
+ style="font-size: 10pt;" size="2">BINOUT</font></tt>
+is copied to the file<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">
+/abcde_d3d.1</font></font></tt><font
+ style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font>
+Even if this file is already present, <tt><font
+ style="font-size: 10pt;" size="2">
+/abcde_d3d.2</font></tt>
+is tried etc. For an input file the highest existing cycle
+of the respective permanent file is copied. In the example above this
+means: the initial run creates the permanent file
+<tt><font style="font-size: 10pt;" size="2">
+/abcde_d3d</font></tt><font
+ style="font-size: 11pt;" size="2">,</font>
+the first restart run uses this file and creates <tt>
+/<font
+ style="font-size: 10pt;" size="2">abcde_d3d.1</font></tt>,
+the second restart run creates <tt><font style="font-size: 10pt;"
+ size="2">
+/abcde_d3d.2</font></tt><font style="font-size: 10pt;"
+ size="2">
+</font>etc. After completion of the job chain the user can still
+access all files created by the jobs. This makes it possible for the
+user for example to restart the model run of a certain job of the job
+chain again. </p>
+<p style="line-height: 100%;">Therefore restart jobs can not only be
+started automatically through <b>mrun</b>, but also manually by the
+user. This is necessary e.g. whenever after the end of a job chain
+it is decided that the simulation must be continued further, because
+the phenomenon which should be examined did not reach the desired
+state yet. In such cases the <b>mrun</b> options completely
+correspond to those of the initial call; simply the <tt><font
+ style="font-size: 10pt;" size="2">"#"</font></tt> characters in the
+arguments of options <tt><font style="font-size: 10pt;" size="2"><font
+ face="Cumberland, monospace">-r</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">-i</font></font></tt>
+and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> must be
+replaced by <tt><font style="font-size: 10pt;" size="2">"f"</font></tt>.
+</p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.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.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> 14/04/05 (SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.4.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.4.html	(revision 5)
@@ -0,0 +1,6455 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+
+
+
+
+  
+  
+  
+  
+  
+  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
+  <title>chapter_3.4</title>
+</head>
+
+<body>
+
+
+
+
+
+<h3 style="line-height: 100%;"><font color="#000000">3.4 Input and
+output files</font></h3>
+
+
+
+
+
+<p style="line-height: 100%;"><font color="#000000"></font></p>
+
+<p style="line-height: 100%;"><font color="#000000">The model works
+with a set of files, which are all located in the temporary working
+directory and which are either expected at the beginning of the run
+(the so-called input files) or which are
+produced during the run and/or at the end of the simulation (output
+files).</font><font color="#800000">
+<font color="#000000">The following table lists all default files
+addressed by the model. They are arranged according to the
+associated FORTRAN unit (unit number).</font> </font><font color="#000000">The
+unit 90 is used for different files, which are opened only briefly
+and uniquely in the model and closed directly afterwards.
+Unit numbers 101 - 109, 111 - 113, and 116&nbsp;refer to data files which have NetCDF format.
+These are not opened by a FORTRAN-OPEN-statement but by a corresponding
+NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on
+machines where a NetCDF library is available.<br>
+
+</font></p>
+
+
+<p style="line-height: 100%;"><font color="#000000">The file
+names described in the list correspond to the names indicated in the
+respective OPEN instruction, i.e. the files are expected and saved
+under these names in the temporary working directory of the model. By
+default, file names are always written in capital letters. The
+third column indicates whether it is an input or output file (I
+and/or O). The NetCDF files can be both input and output files (I/O).
+If restart jobs shall append data to an existing NetCDF file (created
+by a previous job of the job chain), the respective file has to be
+given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a> which gives more details about the PALM-NetCDF-output).</font> </p>
+
+<p style="line-height: 100%;"> </p>
+
+
+
+
+
+
+<p style="line-height: 100%;"><font color="#000000">On parallel
+computers many of the files are read and/or written by the central
+processing element 0 (PE0) only. These files have processor-independent
+content (and therefore they can be read or written by other
+PEs just as well). However, certain files have processor-dependent
+content. For the binary output of data for restart runs (local file
+<a href="#BINOUT">BINOUT</a>),
+for example, <font color="#000000">each PE outputs only the data of
+its subdomain. So each processing element writes
+into its own file with its own file name. These files lie in a
+subdirectory of the temporary working directory. Their names are build
+off from the underline ("_ ") and the four digit
+processor ID. The data written for restart runs would be e.g. on the
+files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc.
+Such files, which have processor-dependent content on parallel
+computers, are marked in the following list by the fact, that to the
+file name a line (&rdquo;/&ldquo;) is attached. If appropriate output
+files are to be copied through <b>mrun</b> to permanent files, and/or
+files with processor-dependent content are supposed to be copied as
+input files into the temporary working directory of the model, you have
+to indicate a special file attribute in the appropriate file
+connection statement </font>(see <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#arpe">arpe</a>,
+<a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#flpe">flpe</a>
+<font color="#000000">in the <b>mrun </b>description).</font><font color="#800000">
+</font><font color="#000000">Then the permanent file name will be
+interpreted as a directory name, in which the input files are
+expected and/or to which output files are written. The file names in
+these directories are always named _0000, _0001, _0002 etc. </font>
+</font></p>
+
+
+
+
+
+<font color="#000000"><font color="#000000">For internal use,
+the model may open a set of further files, which are not
+defined by the user but contain no usable information and
+therefore are not included in this list. <br>
+
+
+
+
+
+<br>
+
+
+
+
+
+</font>
+<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
+
+
+
+
+
+  <tbody>
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+      <td width="8%">
+      
+      
+      
+      
+      
+      <p><font size="4"><b>Unit</b></font></p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="12%">
+      
+      
+      
+      
+      
+      <p><font size="4"><b>Name</b></font></p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="4%">
+      
+      
+      
+      
+      
+      <p><font size="4"><b>I/O</b></font></p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="9%">
+      
+      
+      
+      
+      
+      <p><font size="4"><b>Format</b></font></p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td colspan="1" width="67%">
+      
+      
+      
+      
+      
+      <p><font size="4"><b>Description/contents</b></font></p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+      <td style="text-align: center;" width="8%"> 11<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="12%">
+      
+      
+      
+      
+      
+      <p><a name="PARIN"></a>PARIN</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="4%">
+      
+      
+      
+      
+      
+      <p align="center">I</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="width: 9%;">
+      
+      
+      
+      
+      
+      <p>ASCII/&nbsp; <br>
+
+
+
+
+
+NAMELIST</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td colspan="1" width="67%">
+      
+      
+      
+      
+      
+      <p><font color="#000000">Parameter for model steering. This file
+is needed by the model in each case. Its content and structure is
+described in detail in</font> <a href="chapter_4.0.html">chapter
+4.0</a>. <a href="chapter_4.4.html">Chapter
+4.4</a> <font color="#000000">shows a simple example. </font> </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+      <td style="text-align: center;" width="8%">
+      
+      
+      
+      
+      
+      <p align="center">13</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="12%">
+      
+      
+      
+      
+      
+      <p><a name="BININ"></a>BININ/</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="4%">
+      
+      
+      
+      
+      
+      <p align="center">I</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="9%">
+      
+      
+      
+      
+      
+      <p>Binary</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td colspan="1" width="67%">
+      
+      
+      
+      
+      
+      <p>Binary data, which are read in by the model at the beginning
+of a restart run (see <a href="chapter_3.3.html">chapter
+3.3</a>). The appropriate file must have been written by the preceding
+job of the job chain (see <a href="#BINOUT">BINOUT</a>).
+This file contains the initial parameters (see <a href="chapter_4.1.html">chapter
+4.1</a>) of the job chain, arrays of the prognostic and diagnostic
+variables as well as those parameters and variables for plots of
+horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>),
+which have been determined by the job chain so far. Concerning runs on
+several processors it has to be noted that each processing element
+reads its own file and the file content is processor-dependent. The
+number of processors which can be used must not be changed during a job
+chain and/or if a job chain is continued.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Knowledge of the file structure is usually not necessary,
+because the file is produced and also read again by the model, but it
+can be useful for error determination in case of read errors .
+Therefore the file structure is described in the following.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The first record of this file contains a version number (ten
+character string) of the subroutine, which, which output the data that
+follows (write_var_list.f90). This number has to
+agree with the version number subroutine which is reading the file
+(read_var_list.f90) in case of a restart run. Otherwise the model run
+is aborted. Version numbers are changed whenever new code revisions
+require a change of the file format.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Starting from the second record, all initial parameters follow
+(exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>),
+whereby each parameter fills two records. In the first record the name
+of the parameter is saved as a character string (30 characters long,
+short names are filled by trailing blanks, longer names are cut off at
+the end), in the second record the value (or the values) of the
+parameter follow. The sequence of parameters on the file may be
+arbitrary, however the first and second variable must be <a href="chapter_4.1.html#nz">nz</a>
+and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
+If a variable with unknown name is found the model run is
+aborted.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>At the end of the initial parameters a record with the string "<i>***
+end ***</i>"follows (filled up with trailing blanks up to a length of
+30 characters).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Afterwards the fields of the prognostic and diagnostic
+variables follow. This part of the file also begins with a record
+consisting of a character string of length 10, which contains the
+version number of the subroutine that wrote the arrays that follow
+(write_3d_binary.f90). It must agree with the number of the reading
+subroutine (read_3d_binary.f90).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The following record contains the number of processors which
+were used in the model run producing this file, the processor ID of the
+special processor, which creates the file, as well as the lower and
+upper array indices of the subdomain belonging to this processing
+element. If no complete agreement with the values of the current model
+run exists, then this is aborted. This examination must be made in
+particular on parallel computers, because the jobs of a job chain
+always have to use the same number of processors and the same virtual
+processor grid.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>After these tests the individual arrays as well as parameters
+and variables for plots of horizontally averaged vertical profiles
+follow. Like the initialization parameters, they consist of two
+records. In the first record, the name of the array or the variable
+(character string, consisting of 20 characters, filled with trailing
+blanks) is located, in the second one its values follow. The sequence
+of the individual variables may be arbitrary again. The parameters for
+the plot and the respective variables are only read in if for the run
+parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
+= <i>.TRUE</i> is selected, otherwise they will be skipped.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>At the end of the file there has to be a record with the
+character string "<span style="font-style: italic;"></span><i>*** end
+***</i>"(filled up with trailing blanks up to a length of 20
+characters).</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+      <td style="text-align: center;" width="8%">
+      
+      
+      
+      
+      
+      <p align="center">14</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="12%">
+      
+      
+      
+      
+      
+      <p><a name="BINOUT"></a>BINOUT/</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="4%">
+      
+      
+      
+      
+      
+      <p align="center">O</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td width="9%">
+      
+      
+      
+      
+      
+      <p>Binary</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td colspan="1" width="67%">
+      
+      
+      
+      
+      
+      <p>Binary data, which are written by the model at the end of the
+run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
+3.3</a>) for the initialization. This output file is then read in as
+file <a href="#BININ">BININ</a>.
+It contains the initial parameters (see <a href="chapter_4.1.html">chapter
+4.1</a>) of the model run, arrays of the prognostic and diagnostic
+variables as well as those parameters determined so far during a job
+chain and variables for plots of horizontally averaged vertical
+profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
+With runs on several processors it has to be noted that each processing
+element writes its own file and the file content is
+processor-dependent. A specification of the file format can be found in
+the
+description of the file <a href="#BININ">BININ</a>.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The file BINOUT is written by the model only if, with the help
+of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is assigned for the
+environment
+variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span>
+(see <a href="chapter_3.3.html">chapter
+3.3</a>).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>With large grid point numbers the file BINOUT (or the
+files residing in directory BINOUT/) will be very large and should
+be stored (if available) on the archive system of the remote computer.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">15<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O</td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii</td>
+
+
+
+
+
+      <td colspan="1" width="67%">
+      
+      
+      
+      
+      
+      <p>This file contains the so-called time step control output of
+the model. At certain temporal intervals, which are described by the
+run
+parameter <a href="chapter_4.1.html#dt_run_control">dt_run_control</a>,
+a line with the values of certain control parameters is written into
+this
+file. Additionally, such a control line is always written, whenever the
+time step of the model changes. All data and quantities always refer to
+the entire model domain.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>If the 1D-model is switched on for the initialization of the
+3D-models, then control lines are likewise written into this file at
+certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>).&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>By default, the file RUN_CONTROL only lists information
+about the selected model parameters at the beginning of the
+initial run. These informations are written at the beginnning of a run.
+They correspond to those of the file <a href="#HEADER">HEADER</a>
+(however without data concerning the consumed CPU time, because these
+are
+only known at the end of a run). With the run parameter <a href="chapter_4.2.html#force_print_header">force_print_header</a>
+it can be achieved that this information is also written at the
+beginning of the file RUN_CONTROL at restart runs.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The individual columns of the 1D - time step control output
+have the following meaning (listed by the respective heading of the
+appropriate
+column in the file):&nbsp; <br>
+
+
+
+
+
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+
+
+
+        <tbody>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">ITER.</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Number of time steps
+accomplished so far</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">HH:MM:SS</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Time (in hours: minutes:
+seconds)</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">DT</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Time step (in s)</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">UMAX</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Maximum absolute wind
+velocity
+(u-component) (in m/s)</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">VMAX</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Maximum absolute wind
+velocity
+(v-component) (in m/s)</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">U *</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">ALPHA</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Angle of the wind vector
+(to the x-axis) at the top of the
+Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">ENERG.</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Kinetic energy of the
+1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
+averaged over all grid points</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+        
+        
+        
+        
+        
+        </tbody>
+      
+      
+      
+      
+      
+      </table>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>&nbsp;
+The individual columns of the 3D - time step control output
+have the following meaning (listed by the respective heading of the
+appropriate
+column in the file):<br>
+
+
+
+
+
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+
+
+
+        <tbody>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">RUN</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Serial-number of the job
+in the job chain. The initial
+run has the number 0, restart runs accordingly have larger numbers.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">ITER.</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Number of time steps
+accomplished since starting time t=0 of
+the initial run.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">HH:MM:SS</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Time (<font color="#000000">in
+            </font>hours: minutes:
+seconds) since starting time t=0 of the
+initial run.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">DT (E)</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
+following character indicates whether the
+time
+step is limited by the advection criterion (A) or the diffusion
+criterion (D). After changes of the time step a further character
+follows,
+which indicates with which time step procedure the changed time step
+was accomplished (<span style="font-family: monospace;">L:</span>
+Leapfrog, <span style="font-family: monospace;">E:</span> Euler). This
+does
+not apply for the default Runge-Kutta timestep scheme.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">UMAX</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Maximum absolute wind
+velocity (u-component) (<font color="#000000">in </font>m/s). If at
+the
+appropriate output time a random disturbance was added to the
+horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
+the character D will appear directly after the velocity value.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">VMAX</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Maximum absolute wind
+velocity (v-component) (<font color="#000000">in </font>m/s). If at
+the
+appropriate output time a random disturbance was added to the
+horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
+the character D will appear directly after the velocity value.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">WMAX</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Maximum absolute wind
+velocity (w-component) (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">U *</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Horizontal average of the
+friction velocity (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">W *</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Convective velocity scale
+(<font color="#000000">in </font>m/s). The assumed boundary layer
+height is determined via the heat flux minimum criterion.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">THETA *</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Characteristic temperature
+of the Prandtl - layer (<font color="#000000">in </font>K).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">Z_I</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Height of the convective
+boundary layer (<font color="#000000">in </font>m), determined via
+the criterion of the heat flux minimum.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">ENERG.</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Average resolved total
+energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
+normalized with the total number of grid points.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">DISTENERG</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Average resolved
+disturbance energy of flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
+normalized with the total number of grid points.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">DIVOLD</td>
+
+
+
+
+
+            <td style="vertical-align: top;"><font color="#000000">Divergence
+of the velocity field (sum of
+the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) before call of the pressure solver,
+normalized with the total number of grid points.</font></td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">DIVNEW</td>
+
+
+
+
+
+            <td style="vertical-align: top;"><font color="#000000">Divergence
+of the velocity field (sum of
+the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) after call of the pressure solver, normalized</font>
+with the total number of grid points.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">UMAX (KJI)</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Indices of the grid point
+with the maximum absolute
+u-component of the wind velocity (sequence: k, j, i).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">VMAX (KJI)</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Indices of the grid point
+with the maximum absolute
+v-component of the wind velocity (sequence: k, j, i).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">WMAX (KJI)</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Indices of the grid point
+with the maximum absolute
+w-component of the wind velocity (sequence: k, j, i).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">ADVECX</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
+coordinate system has been moved in
+x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;">ADVECY</td>
+
+
+
+
+
+            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
+coordinate system has been moved in
+y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+        
+        
+        
+        
+        
+        </tbody>
+      
+      
+      
+      
+      
+      </table>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">16<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This file contains horizontally
+(and possibly temporally)
+averaged vertical profiles of some model variables. The quantities
+saved are set model-internally and can not be determined by the user.
+At each output time (see <a href="chapter_4.2.html#dt_dopr_listing">dt_dopr_listing</a>)
+two tables are written to the file consecutively. The first contains
+variables which are defined on the scalar / u-v-grid-levels, the
+second table contains variables which are defined on the w-grid-levels.
+If subdomains were defined with the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions </a>for
+additional statistic evaluation, then the tables
+described above are written for each individual subdomain. The name of
+the respective subdomain (see <a href="chapter_4.3.html#region">region</a>)
+appears in the header of the respective table. <br>
+
+
+
+
+
+In each case the tables consist of a header, followed by the
+profiles arranged next to each other in columns. The header contains
+some basic information of the respective run (model version, run
+identifier consisting of
+basic file name and number of the job in the job chain, executing
+computer, date, time of the beginning of the run, name of the
+subdomain, output time, kind of averaging). On the u-v-level the
+following columns are written: <br>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+
+
+
+        <tbody>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">k<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Vertical
+grid point index.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">zu<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Height
+of the grid point
+level (<font color="#000000">in </font>m).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">u<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">u-component
+of the wind
+velocity (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">du<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Deviation
+of the
+u-component from the initial profile at the
+time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">v<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">v-component
+of the wind
+velocity (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">dv<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Deviation
+of the
+v-component from the initial profile at the
+time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+            <br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Potential
+temperature (<font color="#000000">in </font>K).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">dpt<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Deviation
+of potential
+temperature from the initial profile at
+the time t=0 (initialization profile) (<font color="#000000">in </font>K).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">e<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
+kinetic energy
+(subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Km<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
+diffusion
+coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Kh<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
+diffusion
+coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">l<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Mixing
+length (<font color="#000000">in </font>m).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: top;"><br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="vertical-align: top;"><br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+        
+        
+        
+        
+        
+        </tbody>
+      
+      
+      
+      
+      
+      </table>
+
+
+
+
+
+On the w-level the following columns are written:<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+
+
+
+        <tbody>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">k<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="vertical-align: middle;">Vertical grid point
+index.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">zw<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="vertical-align: middle;">Height of the grid
+point
+level (<font color="#000000">in </font>m).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">w'pt'</td>
+
+
+
+
+
+            <td style="vertical-align: middle;">Vertical subgrid-scale
+kinematic heat flux (<font color="#000000">in </font>K m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">wpt</td>
+
+
+
+
+
+            <td style="vertical-align: middle;">Vertical total (
+subgrid-scale + resolved)
+kinematic heat flux (<font color="#000000">in </font>K m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">w'u'</td>
+
+
+
+
+
+            <td style="vertical-align: middle;">u-component of the
+vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">wu</td>
+
+
+
+
+
+            <td style="vertical-align: middle;">u-component of the
+total
+vertical momentum flux (
+subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">w'v'</td>
+
+
+
+
+
+            <td style="vertical-align: middle;">v-component of the
+vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="vertical-align: middle;">wv</td>
+
+
+
+
+
+            <td style="vertical-align: middle;">v-component of the
+total
+vertical momentum flux (
+subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+        
+        
+        
+        
+        
+        </tbody>
+      
+      
+      
+      
+      
+      </table>
+
+
+
+
+
+      <br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">17 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This file contains the vertical
+profiles calculated by the
+1D-model within initial runs. The quantities saved are set
+model-internally and cannot be determined by the user. At the
+respective output times (see <a href="chapter_4.1.html#dt_pr_1d">dt_pr_1d</a>)
+a table with the following information is written to the file: The
+table header contains some basic information of the respective run
+(model version, run identifier consisting of basic file name and number
+of the job in the
+job chain (this number should always be 00, because the 1D-model is
+only switched on at initial runs), executing computer, date,
+time of the beginning of the run, output time). Afterwards the
+following columns appear:<br>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <table style="text-align: left; width: 100%;" cellpadding="2">
+
+
+
+
+
+        <tbody>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">k<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Vertical
+grid point index.</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">zu<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Height
+of the grid point
+level (<font color="#000000">in </font>m).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">u<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">u-component
+of the wind
+velocity (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">v<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">v-component
+of the wind
+velocity (<font color="#000000">in </font>m/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">pt<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Potential
+temperature (<font color="#000000">in </font>K).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">e<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
+kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">rif<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Flux
+Richardson number</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Km<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
+diffusion
+coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Kh<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">Turbulent
+diffusion
+coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+          <tr>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;">l<br>
+
+
+
+
+
+            </td>
+
+
+
+
+
+            <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
+length (</font><font color="#000000">in </font><font color="#000000">m).</font></td>
+
+
+
+
+
+          </tr>
+
+
+
+
+
+        
+        
+        
+        
+        
+        </tbody>
+      
+      
+      
+      
+      
+      </table>
+
+
+
+
+
+      <br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">18 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Time measurements are
+accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file
+CPU_MEASURES contains a header with some basic information of the
+respective run
+(model version, run identifier consisting of basic file name and
+number of the job in the job chain, executing computer, date, time of
+the beginning of the run) and afterwards two tables with data of CPU
+times which have been consumed by certain model parts. The model parts
+analyzed in the first table do not overlap and the CPU times needed for
+them therefore approximately add up to the &ldquo;total&rdquo; value given in the
+first line of this table. In the second table (heading: special
+measures) overlaps (in particular with the parts described in the first
+table) are possible.&nbsp; <br>
+
+
+
+
+
+For each model part it is indicated in the following columns how much
+CPU time was needed (absolutely and relative), and how often it was
+called.&nbsp; With runs on several processors the average values of all
+processors are indicated. In the case of parallel runs information for
+those processors with the largest and smallest CPU time follow as
+well as the standard deviation of all PEs from the average value. With
+good
+parallelization the CPU times on the individual processors should
+differ only little from each other and the standard deviation should be
+small.&nbsp; </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">19 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="HEADER"></a>HEADER </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>Information about the selected model parameters (physical and
+numerical values) as well as general information about the run.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>This file contains the values of all important steering
+parameters
+(numerical procedures, computing grid and model dimensions, boundary
+conditions, physical dimension, turbulence quantities, actions during
+the simulation, 1D-model-parameters) as well as data concerning the
+selected plot and list outputs. The headlines of the file list the
+program version used, date and time of the beginning of the run, the
+name of the executing computer, the run identifier (corresponds to the
+selected base file name) and the number of the run (number of the
+restart run). With parallel runs the number of processors as well as
+the assigned virtual processor net also appear. After these headlines
+run time and time step information appear (point of starting time,
+related to t=0 of the initial run, end-time, time actually reached, CPU
+time, etc.). If a model run is incorrectly terminated (e.g.
+run time error or excess of the permitted CPU time), information over
+the time reached and the necessary CPU time is missing (to understand:
+the file HEADER is written twice by the model; once briefly after
+beginning of the simulation (naturally here the information over the
+time reached is missing etc.) and then briefly before the normal end of
+the simulation. The second, now complete output overwrites the first
+output.).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>At the end of the file, information about the values of user
+parameters (see <a href="chapter_3.7.html">chapter
+3.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter
+4.3</a>) can be output by the user with the help of the subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt> (located in
+the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>).
+If no user parameters were found, the string &ldquo;<tt><font style="font-size: 10pt;" size="2">*** no user-defined variables found</font></tt>&rdquo;
+appears at the end of the file.
+If user parameters were indicated, the string &ldquo;<tt><font style="font-size: 11pt;" size="2">user-defined variables and actions</font></tt>&rdquo;
+is printed, followed by informations about the user-defined subdomains
+for which
+profiles and time series are output. All further information to appear
+here, must be provided by the user (by appropriate
+WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">21 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>This file contains data of the two-dimensional horizontal
+cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>)
+in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>
+(the first record contains the coordinate information <tt><font style="font-size: 11pt;" size="2">dx</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">eta</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">hu</font></tt><font style="font-size: 11pt;" size="2">, <tt>ho</tt></font>, then
+the individual arrays follow). The data are visualized with the help of
+ISO2D using
+NAMELIST - parameter sets, which are directly written by the model to
+the
+local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
+and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
+= <i>.T.</i> each processing element writes the data of its subdomain
+to a separate file with the name PLOT2D_XY_&lt;processor-Id&gt;,
+whereby &lt;processor-Id&gt; is a four digit number (e.g.
+PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the
+end
+of the model run they can be combined to one file readable by ISO2D
+with
+the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
+This tool expects the files of the individual processing
+elements under the names described above and outputs the combined file
+under the name PLOT2D_XY. Usually it is called by an appropriate OUTPUT
+- command (OC:) in the MRUN-configuration file. The tool writes
+informative messages about the actions accomplished into the job
+protocol (e.g., even if no files were found).
+By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
+possibly existing files of the other cross sections (xz and/or yz)
+and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
+are also combined.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Further information about the output of plots of
+two-dimensional cross sections is found in the description of the run
+parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">22<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>This file contains the data of the xz
+cross sections written by the model.&nbsp; </p>
+
+
+
+
+
+The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
+applies to this file, respectively </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">23<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>This file contains the data of the xz
+cross sections written by the model.&nbsp; </p>
+
+
+
+
+
+The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
+applies to this file, respectively </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">27<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST - parameter sets, with which the plot layout of the
+data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
+can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.
+This file contains the so-called local parameter set (NAMELIST - group
+name: &amp;LOCAL) required by ISO2D (one parameter set for each field
+present at the file PLOT2D_XY). After the model run these parameter
+sets can be edited by the user, if neccessary.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Additionally ISO2D still needs another so-called global
+parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>.
+Due to the fact that ISO2D expects global and local parameter sets on
+one and the same
+file, in fact the global parameter set first, the user has to append
+the
+contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
+before the call of ISO2D (e.g. by an OUTPUT-command in the
+MRUN-configuration file: &ldquo;PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL&rdquo;).
+This relatively pedantic proceeding is due to the fact that the model
+can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation
+(only then e.g. when the final value of the global ISO2D - parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
+is known), while the local parameter sets are written continuously
+to the file PLOT2D_XY_LOCAL during the run.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">28<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST - parameter sets, with which the plot layout of the
+data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
+can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
+applies to this file, respectively. </p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">29<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST - parameter sets, with which the plot layout of the
+data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
+can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
+applies to this file, respectively. </p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">30<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>This file contains the data of the three-dimensional arrays
+(see <a href="chapter_4.2.html#data_output">data_output</a>)
+written by the model in a format readable for the visualization
+software AVS. Beyond that AVS
+needs coordinate information, which are output into the
+local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
+as well as the local files <a href="#PLOT3D_FLD">PLOT3D_FLD</a>
+and <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
+which describe the structure of the files PLOT3D_DATA and PLOT3D_COOR
+in the so-called AVS-FLD-format. Due to
+the fact that AVS expects these information in only one (so-called FLD
+-) file, the content of the file PLOT3D_FLD_COOR must be appended to
+the file PLOT3D_FLD by the user after the end of the model run (e.g.
+with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>").&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>With parallel runs each processing element writes the data of
+its subdomain to a separate file with the name
+PLOT3D_DATA_&lt;Processor-Id&gt;, where &lt;Processor-Id&gt; is a
+four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable
+for AVS, but after the end of the model run they can be combined to one
+file readable for AVS with the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
+This tool expects the files of the individual processing
+elements under the names described above and outputs the combined file
+into a new file PLOT3D_DATA. Usually it is called by an appropriate
+OUTPUT - command in the MRUN-configuration file. The tool
+writes informative messages about the accomplished actions into
+the job protocol (e.g., even if no files were
+found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
+also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>)
+are combined.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>With parallel runs the output of data of large volume is also
+possible in compressed form. For this purpose the initialization
+parameter&nbsp; <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>
+= <i>.TRUE.</i> must be set and the desired output accuracy has to be
+indicated
+with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
+In favorable cases the file size can be reduced by
+a factor of up to 5. For the visualization of compressed data a special
+AVS module (<tt><font style="font-size: 11pt;" size="2">read_compressed_field</font></tt>)
+and a further entry in the MRUN-configuration file are needed. More
+details can be found in <a href="chapter_4.5.6.html">chapter
+4.5.6</a>.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">31<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>Coordinate information concerning
+the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
+needed by the visualization software AVS.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The file PLOT3D_COOR should be saved by the user into the same
+permanent directory as the file PLOT3D_DATA.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>For parallel runs PLOT3D_COOR is written by PE0 only.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">32<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+
+
+
+AVS-Fld </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>AVS-fld-file describing the three-dimensional
+array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>,
+needed by the visualization software AVS.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>This file describes the structure of the file PLOT3D_DATA
+(e.g. number of arrays, array dimensions, data type etc.). It uses the
+so-called AVS-Fld-format. It also contains the name of the file
+(inclusive cycle number, but without path) under which the local file
+PLOT3D_DATA is saved (this is the file name given in the file
+connection statement of the MRUN &ndash; configuration) in the permanent
+directory of the user (possibly on remote computers). Under this name
+AVS expects the data which are to be visualized. If there is no file
+connection statement for PLOT3D_DATA indicated in the configuration
+file, that file (filename) is registered &ldquo;unknown&rdquo; in the file
+PLOT3D_FLD and the
+actual name must be inserted later by hand. The file PLOT3D_FLD should
+be saved by the user in the same permanent directory as PLOT3D_DATA, so
+that AVS can find the file PLOT3D_DATA without any problems. If the two
+files lie in different directories, then the path name of the file
+PLOT3D_DATA must be added.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>AVS-fld-files are expected by AVS to have the
+suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font>
+Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix. This suffix is
+attached to the permanent file names (still after
+possible cycle numbers) by <span style="font-weight: bold;">mrun</span>
+if&nbsp;"<span style="font-family: monospace;">fld</span>"
+is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column
+6 </a>of the file connection statement.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Likewise, AVS expects information about the coordinate
+system underlying the arrays on this file. This information is output
+by the model
+into the local file <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
+whose content the user has to append to the file PLOT3D_FLD after the
+end of the model run (e.g. with an appropriate OUTPUT-command in the
+MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR &gt;&gt;
+PLOT3D_FLD&rdquo;).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>For parallel runs, PLOT3D_FLD is produced by PE0 only.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">33 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+
+
+
+AVS-Fld </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>File for the description of the coordinate information output
+by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
+which is needed for the visualization of three-dimensional array data
+by visualization-software AVS.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>This file describes the structure of the file PLOT3D_COOR
+(e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format.
+It also contains the name of the file (inclusive cycle number, but
+without path) into which the local file PLOT3D_COOR (this is the file
+name described in the file connection statement of the MRUN -
+configuration file) is output in the permanent directory of the user
+(possibly on remote computers). Under this name AVS expects the data
+which are to be visualized. If there is no file connection statement
+for
+PLOT3D_COOR indicated in the configuration file, that file is
+registered as "unknown" in the file
+PLOT3D_FLD_COOR and the actual name
+must be inserted later by hand.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>AVS expects the information contained in the file
+PLOT3D_FLD_COOR, as well as the remaining information about the
+three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>)
+in one and the same file. This is satisfied by appending the file
+PLOT3D_FLD_COOR after the end of a run are to the
+file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the
+MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR &gt;&gt;
+PLOT3D_FLD&rdquo;).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>For parallel runs, PLOT3D_FLD_COOR is written by PE0 only.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">
+      
+      
+      
+      
+      
+      <p align="center">40&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p align="center">and/or&nbsp; <br>
+
+
+
+
+
+possibly&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p align="center">40-49</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>and/or&nbsp; <br>
+
+
+
+
+
+possibly&nbsp; </p>
+
+
+
+
+
+PLOT1D_DATA_0&nbsp; <br>
+
+
+
+
+
+PLOT1D_DATA_1&nbsp; </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>This file contains data (possibly horizontally and/or
+temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>)
+written by the model in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. It is created only if <a href="chapter_4.2.html#data_output_format">data_output_format</a> = <span style="font-style: italic;">'profil'</span> is assigned. This file's format is suitable to be read by the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
+Each data point of the profiles is output in one single line (1st
+column: height in m, 2nd column: value of the respective quantity).
+Within the file, data
+of the individual profiles are located one behind the other. The order
+of the data in the file follows the order used in the assignment for <b>data_output_pr</b>
+(<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
+means that the file starts with the data of the u-component profile,
+followed by the v-component profile, etc.).&nbsp;</p>
+      <p><br>
+The data can only be visualized with <span style="font-weight: bold;">profil</span>
+using NAMELIST-parameter sets, which are saved by the
+model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The profile data written to the file are described with the
+run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
+Plots produced with these data using the parameter file PLOT1D_PAR do
+not have to contain all these profiles. The profiles which can be drawn
+in the plot are described with run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>.
+By subsequent editing of the file PLOT1D_PAR all profiles can be
+plotted (also the basic layout of the plots can be
+changed). For orientation, each profile existing on the file
+PLOT1D_DATA, starts with a comment line, which indicates the
+presented variable and the output time. The text of these comment
+lines is used as a legend in the plot. The very first line of the file
+is a
+comment line, containing 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 profiles belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
+By default, the profiles present averages of the total model domain. If
+the model has to produce profiles for other subdomains beyond that, up
+to 9 further files (units No. 41-49) are created, whereby the number of
+the respective subdomain is attached
+to the file name (e.g. PLOT1D_DATA_1). The name of the file with the
+data of the total
+domain in this case reads PLOT1D_DATA_0.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>For presentation in the same plot, profile data of the restart
+runs can be attached to existing data of preceding runs of a job chain.
+One can do this 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. The model produces a parameter file
+(PLOT1D_PAR) for these combined data, if the run parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
+= <i>.T</i>. If this is omitted, then the parameter file gives
+wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
+= .T.</span> and "<span style="font-family: monospace;">tra</span>"
+must be specified together)!&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Further information about output of
+vertical profile data is given in the description of the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">
+      
+      
+      
+      
+      
+      <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;">80 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This
+file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles
+package</a>). It contains statistical informations about the number of
+particles used and about the number of particles exchanged between each
+single PE. These informations are output after every timestep if
+switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>.
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">81 </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/<br>
+
+
+
+
+
+NAMELIST </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This
+file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
+package</a>). It contains the NAMELIST parameter set, with which the
+layout of a plot
+of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
+can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>It contains the so-called RAHMEN (frame)- and
+CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
+needed by <span style="font-weight: bold;">profil</span>.
+The user can edit these parameter sets (and thus all details of the
+plot layout) after the run.<br>
+
+
+
+
+
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>By default, for one quantity, all spectra at different heights
+are plotted into a single panel. Different colors and line styles are
+used for each height. Panels of up to four quantities are arranged on
+one page in two lines (and two columns). More quantities are plotted on
+additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
+additional pages will be plotted for each single output time. </p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">82<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This
+file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
+package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
+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="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
+for actual plotting, this file contains all data of spectra specified
+by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+      <font>Each data point of a spectrum is output in a 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>),
+the spectral coefficients for the further heights can be found in the
+subsequent columns. </font>The order
+of the data in the file follows the order used in the assignment for <span style="font-style: italic;"></span><span style="font-style: italic;"></span><a href="chapter_4.2.html#data_output_sp">data_output_sp</a>.<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+For orientation, a header of comment lines (one for each height level)
+is placed in front of the spectral data of each quantity. They indicate
+the respective quantity and the output time. The text of these comment
+lines is used as a legend in the plot. </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">83<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This
+file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
+package</a>). It contains the NAMELIST parameter set, with which the
+layout of a plot
+of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
+can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">84<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This
+file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
+package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
+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="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">85<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">This
+file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
+package</a>) and contains all particle data for one or several output
+times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+The first record of this file contains an identification string (PALM
+version number, run identifier, etc., 80 characters long). The second
+record also contains a version string (80 characters long) followed by
+two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>). Then, for each
+output time, two records follow, where the first one gives some general
+information (numbers of particles, etc.) and the second one contains
+the actual particle data. A FORTRAN TYPE structure is used for storing
+the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span>
+for the detailed format.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90</td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
+
+
+
+
+
+DATA_IN/</td>
+
+
+
+
+
+      <td style="vertical-align: top;">I<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary
+data, which are read in by the model at the beginning
+of a restart run (see <a href="chapter_3.3.html">chapter
+3.3</a>). The appropriate file must have been written by the preceding
+job of the job chain (see <a href="#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>).
+This file is needed if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
+package</a>) and contains all particle informations (particle
+positions, velocities, etc.) from the end of the preceding run.
+Concerning runs on
+several processors it has to be noted that each processing element
+reads its own file and that the file content is processor-dependent.
+The
+number of processors which can be used must not be changed during a job
+chain and/or if a job chain is continued. <br>
+
+
+
+
+
+      <br>
+
+
+
+
+
+The first record of this file contains a version number (four character
+string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>, see end of
+file <span style="font-family: monospace;">advec_particles.f90</span>).
+This number has to
+agree with the version number of the subroutine which is reading the
+file
+(<span style="font-family: monospace;">init_parrticles.f90</span>) in
+case of a restart run. Otherwise the model run
+is aborted. Version numbers are changed whenever new code revisions
+require a change of the file format. Some general informations like the
+number of particles stored in the file, the number of particle groups,
+etc.. are stored in the second record. The third record includes the
+particles to be released at the source and the fourth record contains
+all current particles. In case that particle tails are used (see <a href="chapter_4.2.html#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>),
+a further record may follow, which contains the particle tail
+informations. A FORTRAN TYPE structure is used for storing the particle
+attributes. For detailed informations about the file format see the
+corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span> .<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
+
+
+
+
+
+DATA_OUT/</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Binary
+data, which are output at the end of the
+run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
+3.3</a>) for the initialization. This output file is then read as
+file <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.
+The file is only written if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
+package</a>). For a more detailed description of the file structure see
+      <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p><a name="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>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>and/or&nbsp; <br>
+
+
+
+
+
+possibly&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>PLOT1D_PAR_0&nbsp; <br>
+
+
+
+
+
+PLOT1D_PAR_1&nbsp; <br>
+
+
+
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+
+
+
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+
+
+
+
+
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+.&nbsp; <br>
+
+
+
+
+
+PLOT1D_PAR_9</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST parameter set, with which the layout of a plot
+of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a>
+can be steered, if these data are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>This file contains the so-called RAHMEN (frame)- 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 plot layout) can be
+edited after the model run by the user. By default, all profiles of one
+variable saved at different times are drawn into one panel. Different
+colors are used for each output time. Which profiles are drawn
+into which plane and how these planes are arranged on the
+plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>, <a href="chapter_4.2.html#profile_columns">profile_columns</a>
+and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The file PLOT1D_PAR is created by the model briefly before
+the end of a run. If a model run crashes uncontrolled (run time
+errors or CPU - time exceeded), this file is usually missing, although
+profile data were saved to the file PLOT1D_DATA.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>If the model has to create profiles for different subdomains
+(see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
+further files are created, whereby the file name includes the number of
+the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of
+the file with NAMELIST parameters of the total domain is
+PLOT1D_PAR_0.&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>For presentation in the same plot, profile data of the restart
+runs can be appended to existing data of preceding runs of a job chain.
+One can do this 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 for PLOT1D_DATA. The model produces
+a parameter file PLOT1D_PAR for these combined data, if the run
+parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
+= <i>.T</i>. If this is omitted, then the parameter file gives
+wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
+= .T.</span> and "<span style="font-family: monospace;">tra</span>"
+must be specified together)!</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+
+
+
+NAMELIST</td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST parameter set, with which the plot layout
+of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
+can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
+This file contains the so-called global parameter set (NAMELIST - group
+name: &amp;GLOBAL) needed by <span style="font-weight: bold;">iso2d</span>.
+This parameter set can be edited
+after the model run by the user. By default, the arrays are drawn using
+isolines and each array
+will be drawn onto a separate page (thus no color shading
+presentation, no vector arrows, streamlines etc.).&nbsp; </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>Additionally <span style="font-weight: bold;">iso2d</span>
+needs the so-called local parameter
+sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
+Due to the fact that <span style="font-weight: bold;">iso2d</span>
+expects global and local parameter sets on one and the same
+file, in fact the global parameter set first, the user has to append
+the contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
+before call of <span style="font-weight: bold;">iso2d</span> (e.g. by
+an OUTPUT - command in the MRUN -
+configuration file: &ldquo;cat PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL&rdquo;).
+This
+relatively pedantic proceedure is due to the fact that the model can
+create the file PLOT2D_XY_GLOBAL only at the end of the simulation
+(only then, when the final value of the global <span style="font-weight: bold;">iso2d</span>-parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
+is known), while the local parameter sets are written continuously
+to the file PLOT2D_XY_LOCAL during the run. Since the file
+PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit
+90 is used, which is also used for other files.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+
+
+
+NAMELIST</td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST parameter set, with which the plot layout of the data
+in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
+can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
+applies to this file, respectively.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td>
+
+
+
+
+
+      <td style="vertical-align: top;">O<br>
+
+
+
+
+
+      </td>
+
+
+
+
+
+      <td style="vertical-align: top;">Ascii/&nbsp; <br>
+
+
+
+
+
+NAMELIST</td>
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      <p>NAMELIST parameter set, with which the plot layout of the data
+in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
+can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.&nbsp;
+      </p>
+
+
+
+
+
+      
+      
+      
+      
+      
+      <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
+applies to this file, respectively.</p>
+
+
+
+
+
+      </td>
+
+
+
+
+
+    </tr>
+
+
+
+
+    <tr>
+
+
+
+
+      <td style="vertical-align: top; text-align: center;">90</td>
+
+
+
+
+      <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td>
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+      <td style="vertical-align: top;">Ascii</td>
+
+
+
+
+      <td>Two-dimensional&nbsp;<font color="#000000">topography height information</font> in m.<br>
+
+
+
+
+In case of &nbsp;<a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'read_from_file'</span> the&nbsp;subroutine <span style="font-family: Cumberland AMT;">init_grid</span>&nbsp;reads the topography height information in m for each grid point in
+a free floating point format. The data on file are laid out naturally,
+i.e. in W-E orientation horizontally and in S-N orientation vertically,
+they must thus be organized as follows:<br>
+
+
+      
+      
+      <ul>
+
+
+        <li>each line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li>
+
+
+        <li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the bottom line for <span style="font-style: italic;">j = 0</span> (South),</li>
+
+
+        <li>individual data must be separated by at least one blank.</li>
+
+
+      
+      
+      </ul>
+
+
+Layout sketch:<br>
+
+
+      <span style="font-family: Cumberland AMT;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;N<br>
+
+
+&nbsp; &nbsp; (0,ny) &nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny) &nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) &nbsp; ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) &nbsp; &nbsp; &nbsp;<span style="font-family: Times New Roman,Times,serif;"></span></span></font><font color="#000000">&nbsp;top of file</font><font color="#000000"><span style="font-family: Cumberland AMT;"><span style="font-family: Times New Roman,Times,serif;"></span></span></font><br>
+
+
+      <font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp; (0,ny-1)&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-1)&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-1) ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) &nbsp;<br>
+
+
+      </span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W &nbsp; (0,ny-2)&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-2)&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-2) ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) &nbsp; E<br>
+
+
+      </span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
+
+
+&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
+
+
+      </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp; (0,0) &nbsp;&nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0) &nbsp;&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0) &nbsp; &nbsp;...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0) &nbsp; &nbsp; &nbsp;&nbsp;</span></font></font></font><font color="#000000">&nbsp;bottom of file</font><br>
+
+
+      <font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;S</span></font><br>
+
+
+      <font style="font-family: Arial;" color="#000000"></font><span style="font-family: Arial;"></span><br>
+
+
+
+
+These data must exactly match the horizontal grid.<br>
+
+
+Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a> to allow different data formats.</td>
+
+
+
+
+      <td><br>
+
+      </td>
+
+
+
+
+    </tr>
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional horizontal
+cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional vertical (xz)
+cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional vertical
+(yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+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>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></td>
+
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+    </tr>
+    <tr>
+      <td style="vertical-align: top; text-align: center;">109</td>
+      <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td>
+      <td align="left" valign="top">I/O</td>
+      <td align="left" valign="top">Binary/<br>
+NetCDF-<br>
+format</td>
+      <td align="left" valign="top">This file contains data of the timeseries of particle quantities (<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">see <a href="chapter_4.2.html#dt_prel">dt_prel</a>)
+in NetCDF format.&nbsp;</font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>). For a list of available output quantities see </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"> <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>.</font></font></font></font></font><br>
+      <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
+      </font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
+seperate time series are output for each of the groups. The long names
+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>
+      <br>
+      </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
+      <td align="left" valign="top"></td>
+    </tr>
+    <tr>
+      <td style="text-align: center; vertical-align: top;">111</td>
+      <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td>
+      <td style="vertical-align: top;">I/O</td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></font></td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged two-dimensional horizontal
+cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td style="text-align: center; vertical-align: top;">112</td>
+      <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td>
+      <td style="vertical-align: top;">I/O</td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></font></td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged two-dimensional vertical (xz)
+cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td style="text-align: center; vertical-align: top;">113</td>
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td>
+      <td style="vertical-align: top;">I/O</td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></font></td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged two-dimensional vertical
+(yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
+      <td></td>
+    </tr>
+    <tr>
+      <td style="text-align: center; vertical-align: top;">116</td>
+      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td>
+      <td style="vertical-align: top;">I/O</td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
+
+NetCDF-<br>
+
+format</font></font></font></td>
+      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
+in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
+
+      <br>
+
+More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></font></td>
+      <td></td>
+    </tr>
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  </tbody>
+</table>
+
+
+
+
+
+<font color="#000000"><br>
+
+
+
+
+
+</font>
+<br>
+
+
+
+
+
+<font color="#000080"><font color="#000080"><a href="chapter_3.3.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>
+
+
+
+
+
+&nbsp;
+<br>
+
+
+
+
+
+&nbsp;
+<span style="font-style: italic;">Last change:</span> 07/11/06 (ML)<br>
+
+
+
+
+
+</font><br>
+
+
+
+
+
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_3.5.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.1.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.5.1.html	(revision 5)
@@ -0,0 +1,445 @@
+<!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.1</title><meta name="GENERATOR" content="StarOffice 7 (Win32)">
+
+  <meta name="AUTHOR" content="Siegfried Raasch">
+
+  <meta name="CREATED" content="20040802;11451548">
+
+  <meta name="CHANGED" content="20041112;14401801">
+
+  <meta name="KEYWORDS" content="parallel LES model">
+
+  <style>
+<!--
+@page { size: 21cm 29.7cm }
+-->
+  </style></head>
+<body style="direction: ltr;" lang="en-US">
+
+<h3 style="line-height: 100%;">3.5.1 Interfaces for
+user-defined code<br>
+
+</h3>
+
+<p style="margin-bottom: 0cm; line-height: 100%;">The
+following table
+describes the available interfaces for user-defined code in the model,
+the
+names and possible arguments of the subroutines involved as well as
+actions which can be accomplished in these subroutines. <br>
+
+&nbsp; </p>
+
+<table style="width: 100%;" border="1" cellpadding="2" cellspacing="4">
+
+  <col width="211"> <col width="117"> <col width="862"> <tbody>
+
+    <tr>
+
+      <td width="211">
+      <p><font size="4"><b>Call location</b></font></p>
+
+      </td>
+
+      <td width="117">
+      <p><font size="4"><b>Subroutine name and
+argument</b></font></p>
+
+      </td>
+
+      <td style="width: 862px;">
+      <p><font size="4"><b>Possible actions</b></font></p>
+
+      </td>
+
+    </tr>
+
+    <tr><td>---</td><td><span style="font-family: monospace;"><a name="user"></a>MODULE user</span></td><td>All
+user-defined variables which are used outside the respective local
+scopes of the user-defined subroutines have to be declared here.</td></tr><tr valign="top">
+
+      <td width="211">
+      <p>End of <tt><font style="font-size: 10pt;" size="2">parin.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_parin"></a>user_parin</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>Declaration of user-defined parameters in the NAMELIST
+group <tt><font style="font-size: 10pt;" size="2">&amp;userpar</font></tt>.
+These
+parameters can be read from the local file <a href="chapter_3.4.html#PARIN">PARIN</a>
+and be used for steering the user-defined code (see <a href="chapter_4.0.html">chapter
+4.0</a>). The user-defined parameter <a href="chapter_4.3.html#region">region</a>
+is already pre-defined in <tt><font style="font-size: 10pt;" size="2">&amp;userpar</font></tt>
+and must not be changed. Additional NAMELIST groups may be declared if
+desired.&nbsp; <br>
+
+The CPU time needed for executing <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt>
+is included in the
+local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
+within the category &ldquo;initialisation&rdquo;.</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p>End of <tt><font style="font-size: 10pt;" size="2">header.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_header"></a>user_header( io )</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>Output of the values of the user-defined parameters to
+the
+local files <a href="chapter_3.4.html#HEADER">HEADER</a>
+and <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
+This output should be made anyway in order to subsequently check the
+parameter values used for the respective run. The number of the output
+unit is passed as an argument and must be used in each WRITE statement
+(e.g.: &ldquo;<tt><font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2">WRITE </font><font style="font-size: 10pt;" size="2">( io,&hellip;</font></font></tt><font style="font-size: 10pt;" size="2">&rdquo;))</font>.
+By default, this
+subroutine only creates output if a user-defined NAMELIST is found in
+file <a href="chapter_3.4.html#PARIN">PARIN</a>
+(in this case <tt><font face="Thorndale, serif">the</font></tt>
+variable <tt><font style="font-size: 10pt;" size="2">user_defined_namelist_found</font></tt>
+is set&nbsp; <i>.TRUE.</i> in <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt>).
+The names of any
+user-defined
+subdomains are displayed by default (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p>End of <tt><font style="font-size: 10pt;" size="2">init_3d_model.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init"></a>user_init</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>Here, user-defined initialization actions which should
+be
+accomplished before the start of the 3D-model can be implemented (e.g.
+inhomogenous change of the surface temperature, the roughness length,
+or similar). At this point, all default parameter initializations of
+the model (<a href="chapter_4.1.html">chapter
+4.1</a>) have already been carried out at all.&nbsp; </p>
+
+      <p>One of the most important actions here is the definition
+of
+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
+3.5.3</a>).&nbsp; <br>
+
+CPU time for <tt><font style="font-size: 10pt;" size="2">user_init</font></tt>
+is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
+within the category &ldquo;initialisation&rdquo;.</p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2">DEFAULT</font></tt>
+case of <tt><font style="font-size: 10pt;" size="2">SELECT
+CASE( TRIM(topography) ) </font></tt>command in the
+middle&nbsp;of <tt><font style="font-size: 10pt;" size="2">init_grid.f90</font></tt></td>
+
+      <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_grid"></a>user_init_grid</font></font></tt></td>
+
+      <td>
+      <p>Execution of user-defined grid initializing actions.</p>
+
+      <p>Here, the user can define the two-dimensional index
+array&nbsp;<tt><font style="font-size: 10pt;" size="2">nzb_local</font></tt> that is used to
+set up a non-flat topography. This requires definition of at least one
+new <a href="chapter_4.1.html#topography">topography</a>&nbsp;mode
+in the&nbsp;<tt><font style="font-size: 10pt;" size="2">SELECT CASE( TRIM(topography) ) </font></tt>command
+in&nbsp;<tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt>.
+Note that the <a href="chapter_4.1.html#topography">topography</a>&nbsp;modes
+      <span style="font-style: italic;">'flat'</span>
+and <span style="font-style: italic;">'single_building'</span>
+are not allowed here since these are the standard cases used in the
+calling routine <tt><font style="font-size: 10pt;" size="2">init_grid</font></tt>. </p>
+
+      <p>CPU time for <tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt>
+is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
+within the category &ldquo;initialisation&rdquo;.</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p>In the middle of <tt><font style="font-size: 10pt;" size="2">init_particles.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_particles"></a>user_init_</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">particles</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>With this routine e.g. size and color of particles,
+which have
+been released initially from a source, can be specified. Like the
+calling routine <tt><font style="font-size: 10pt;" size="2">init_particles</font><font style="font-size: 11pt;" size="2">,</font></tt>
+this routine is only
+called if particle advection is switched on (see package parameter <a href="chapter_4.2.html#dt_prel">dt_prel</a>).</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p>End of <tt><font style="font-size: 10pt;" size="2">advec_particles.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_particle_attributes"></a>user_particle_</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">attributes</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>Here the particles can be assigned new attributes
+(diameter,
+color etc.) after each time step. Like the calling routine <tt><font style="font-size: 10pt;" size="2">advec_particles</font><font style="font-size: 11pt;" size="2">,</font> </tt>this
+routine is only
+called if particle advection is switched on (see package parameter <a href="chapter_4.2.html#dt_prel">dt_prel</a>).</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p>Before the plot of particles and cross-sections in <br>
+
+      <tt><font style="font-size: 10pt;" size="2">dvrp_plot.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_dvrp_coltab"></a>user_dvrp_coltab
+(</font></font></tt><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> mode )</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>With this routine, color tables can be adjusted which
+should
+be used for output with the dvrp software. Individuell color tables for
+particles and cross-sections are possible. For this purpose the two
+arrays <tt><font style="font-size: 10pt;" size="2">interval_values_dvrp</font></tt>
+and <tt><font style="font-size: 10pt;" size="2">interval_h_dvrp</font></tt>
+(declared in the module <tt><font style="font-size: 10pt;" size="2">dvrp_variables</font></tt>)
+have to be preset with appropriate values. The number of color table
+entries must be assigned to the variable of <tt><font style="font-size: 10pt;" size="2">dvrp_colourtable_entries</font></tt>.
+The value of the subroutine argument <span style="font-family: monospace;">mode</span> defines,
+whether the color
+table is valid for particles or for cross-sections<span style="font-family: monospace;"></span> (i.e. <tt><font size="2">mode</font></tt>
+can have the values &ldquo;<i>particles&rdquo;</i>
+or &ldquo;<i>slicer&rdquo;</i>).&nbsp; <br>
+
+This routine only becomes active if dvrp-graphics is switched on (see
+package parameter <a href="chapter_4.2.html#dt_dvrp">dt_dvrp</a>).</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p>Beginning and end of the time integration loop
+of&nbsp; <br>
+
+      <tt><font style="font-size: 10pt;" size="2">time_integration.f90</font></tt>
+as well as after each prognostic equation in <br>
+
+      <tt><font style="font-size: 10pt;" size="2">prognostic_equations.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_actions"></a>user_actions( location )</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> </font></font> </p>
+
+      <p>or<br>
+
+      <font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2"> </font></font>
+      </p>
+
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">user_actions( i, j,</font></font></tt><span style="font-family: Cumberland,monospace;"> </span><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">location )</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      
+
+      <p>In this routine user actions can be implemented which
+are to
+be executed either at each time step or at certain times (defined by
+the user). Since in each case the routine is called at the beginning
+and at the end of a time step as well as after each prognostic equation
+it must be defined at which place (and/or at which places) the
+respective actions are supposed to be executed. For this purpose an
+appropriate CASE structure is already inserted in this routine. The
+location of the calling routine is passed to this routine via the
+argument <tt><font style="font-size: 10pt;" size="2">location</font></tt>.
+For example, if called at the beginning of a time step, <tt><font style="font-size: 10pt;" size="2">location</font></tt>
+=&nbsp;<i>'before_timestep' </i>and if
+called at the end, <tt><font style="font-size: 10pt;" size="2">location</font></tt><font style="font-size: 10pt;" size="2"> </font>=&nbsp;<i>'after_timestep'</i><span style="font-weight: bold;">.</span></p><p>Calculation of user-defined output quantities should be carried out at <span style="font-family: monospace;">location</span> = <span style="font-style: italic;">'after_integration'</span>.<span style="font-weight: bold;"></span></p><p><span style="font-weight: bold;">Important:</span>
+if the
+cache-optimized version of <span style="font-family: monospace;">prognostic_equation.f90</span>
+is used (this is the default for IBM-Regatta-Systems), the loop
+variables <tt>i</tt> and <tt>j</tt> must be
+passed as arguments for
+all calls within <span style="font-family: monospace;">prognostic_equations</span>.
+      </p>
+
+      <p>CPU time for <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt>
+appears within the category &ldquo;user_actions&rdquo; in the
+local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>.
+If the cache-optimized version of <span style="font-family: monospace;">prognostic_equation.f90</span>
+is used, this time measurement only considers the CPU time which was
+needed outside of the prognostic equations. Time needed for calls
+within prognostic_equations is considered within the category "all
+prog.equations".<br>
+
+      </p>
+
+      <p><b>Important:</b> this subroutine is written
+as a FORTRAN
+module, which uses so-called function overloading. It can be called in
+two ways: with one argument (<tt><font style="font-size: 10pt;" size="2">location</font></tt>)
+and with three arguments <font style="font-size: 10pt;" size="2">(</font><tt><font style="font-size: 10pt;" size="2">i, j, location</font></tt><font style="font-size: 10pt;" size="2">)</font>. The
+three argument version
+is used in the cache-optimized version of <span style="font-family: monospace;">prognostic_equations</span>.
+Depending
+on the number of given arguments the subroutine internally calls <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt>
+or <tt><font style="font-size: 10pt;" size="2">user_actions_ij</font></tt>.
+So the
+user must insert the actions (code extensions) desired for the
+respective prognostic equation either in the CASE structure of <tt><font style="font-size: 10pt;" size="2">user_actions</font><font style="font-size: 11pt;" size="2">,</font> </tt>or/and
+in the CASE
+structure of <tt><font style="font-size: 10pt;" size="2">user_actions_ij</font></tt>!</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td width="211">
+      <p><tt><font style="font-size: 10pt;" size="2">flow_statistics.f90</font></tt>
+before the summation of array <span style="font-family: monospace;">hom</span>
+(horizontal averages)<br>
+
+      </p>
+
+      </td>
+
+      <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
+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;,
+60) =</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>
+
+      </td>
+
+    </tr>
+
+    <tr><td style="vertical-align: top;">End of <span style="font-family: monospace;">check_parameters.f90</span> where output quantities are checked</td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_check_data_output"></a>user_check_data_<br>output( variable, unit )</span></td><td style="vertical-align: top;">Here the <span style="font-family: monospace;">unit</span>(s) of user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) have to be set. Input parameter <span style="font-family: monospace;">variable</span> contains the string identifier of the respective variable. For those variables not recognized by the user, the parameter <span style="font-family: monospace;">unit</span> is set to "illegal", which tells the calling routine that the output variable is not defined and leads to a program abort.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;"><span style="font-family: monospace;">netcdf.f90</span> (4 times) where the vertical grid coordinates for cross sections and volume data are defined</td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_define_netcdf_grid"></a>user_define_<br>netcdf_grid( variable, found, grid_x, grid_y, grid_z )</span></td><td style="vertical-align: top;">Set the grid on which user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) are defined. Input parameter <span style="font-family: monospace;">variable</span> contains the string identifier of the respective variable. Allowed values are <span style="font-style: italic;">'x'</span> and <span style="font-style: italic;">'xu'</span> for <span style="font-family: monospace;">grid_x</span>, <span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'yv'</span> for <span style="font-family: monospace;">grid_y</span>, and<span style="font-family: monospace;"></span>&nbsp;<span style="font-style: italic;">'zu'</span> and <span style="font-style: italic;">'zw'</span> for <span style="font-family: monospace;">grid_z</span>. The output parameter <span style="font-family: monospace;">found</span> has to be set <span style="font-style: italic;">.TRUE.</span> by the user, otherwise an error message will appear in the job protocol for the respective output quantity.<br><br><span style="font-weight: bold;">Example:</span><br>If an output quantity is defined at the center of the grid boxes, the following settings have to be used:<br><br><div style="margin-left: 40px;"><span style="font-family: monospace;">grid_x = <span style="font-style: italic;">'x'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_y = <span style="font-style: italic;">'y'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_z = <span style="font-style: italic;">'zu'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">found &nbsp;= <span style="font-style: italic;">.TRUE.</span></span><br></div><br>For defining an output quantity at the grid points where the u-velocity-component is defined, please use<br><br><div style="margin-left: 40px;"><span style="font-family: monospace;">grid_x = <span style="font-style: italic;">'xu'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_y = <span style="font-style: italic;">'y'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">grid_z = <span style="font-style: italic;">'zu'</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">found &nbsp;= <span style="font-style: italic;">.TRUE.</span></span><br></div><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;">Middle of <span style="font-family: monospace;">data_output_2d.f90</span></td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_data_output_2d"></a>user_data_<br>output_2d( av, variable, found, grid, local_pf )</span></td><td style="vertical-align: top;">Resorts&nbsp;user-defined&nbsp;quantities (to be output as cross-section data;&nbsp;see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) with indices (k,j,i) to a temporary array <span style="font-family: monospace;">local_pf</span> with indices (i,j,k) and sets the <span style="font-family: monospace;">grid</span> on which they are defined. Depending on the value of input parameter <span style="font-family: monospace;">av</span> resorting is done for instantaneous (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">0</span>) or time averaged data (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">1</span>). Input parameter <span style="font-family: monospace;">variable</span> contains the string identifier of the respective variable. Allowed values for <span style="font-family: monospace;">grid</span> are&nbsp;<span style="font-style: italic;">'zu'</span> and&nbsp;<span style="font-style: italic;">'zw'</span>. The output parameter <span style="font-family: monospace;">found</span> has to be set <span style="font-style: italic;">.TRUE.</span> by the user, otherwise an error message will appear in the job protocol for the respective output quantity.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;"><span style="font-family: monospace;">data_output_3d.f90</span> at the end of the CASE structure</td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_data_output_3d"></a>user_data_<br>output_3d( av, variable, found, local_pf, nz_do )</span></td><td style="vertical-align: top;">Resorts&nbsp;user-defined&nbsp;quantities (to be output as volume data;&nbsp;see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) with indices (k,j,i) to a temporary array <span style="font-family: monospace;">local_pf</span> with indices (i,j,k) and sets the <span style="font-family: monospace;">grid</span> on which they are defined. Depending on the value of input parameter <span style="font-family: monospace;">av</span> resorting is done for instantaneous (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">0</span>) or time averaged data (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">1</span>). Input parameter <span style="font-family: monospace;">variable</span> contains the string identifier of the respective variable<span style="font-family: monospace;"></span><span style="font-style: italic;"></span><span style="font-style: italic;"></span>. The input parameter <span style="font-family: monospace;">nz_do</span> defines the upper limit of vertical grid index k of the output array (see <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>). The output parameter <span style="font-family: monospace;">found</span> has to be set <span style="font-style: italic;">.TRUE.</span> by the user, otherwise an error message will appear in the job protocol for the respective output quantity.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;">End of <span style="font-family: monospace;">average_3d_data.f90</span>, middle and end of <span style="font-family: monospace;">sum_up_3d_data.f90</span></td><td style="vertical-align: top;"><span style="font-family: monospace;"><a name="user_3d_data_averaging"></a>user_3d_data_<br>averaging( mode, variable )</span></td><td style="vertical-align: top;">Sum up and time-average of user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>) as well as allocation of the arrays necessary for storing the respective averages. Input parameter <span style="font-family: monospace;">variable</span> contains the string identifier of the respective variable. Depending on the requested action, input parameter <span style="font-family: monospace;">mode</span> has the value <span style="font-style: italic;">'allocate'</span>, <span style="font-style: italic;">'sum'</span>, or <span style="font-style: italic;">'average'</span>.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about creating user-defined output quantities. </td></tr><tr valign="top">
+
+      <td width="211">
+      <p>End of <tt><font style="font-size: 10pt;" size="2">palm.f90</font></tt></p>
+
+      </td>
+
+      <td width="117">
+      <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_last_action"></a>user_last_</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">action</font></font></tt></p>
+
+      </td>
+
+      <td width="862">
+      <p>User-defined actions which are to be executed at the end
+of a
+model run. When <tt><font style="font-size: 10pt;" size="2">user_last_actions</font></tt>
+is called all model actions are already completed, but the files opened
+by the model are not closed yet and possibly terminating actions for
+these files (see subroutine of <tt><font style="font-size: 10pt;" size="2">close_files</font></tt>)
+are also not carried
+out yet.&nbsp; <br>
+
+CPU time for <tt><font style="font-size: 10pt;" size="2">user_last_actions</font></tt>
+appears in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
+within the category &ldquo;last actions&rdquo; (the time
+necessary for <tt><font style="font-size: 10pt;" size="2">close_files</font></tt> is included).</p>
+
+      </td>
+
+    </tr>
+
+  </tbody>
+</table>
+
+<hr>
+<p style="line-height: 100%;"><br>
+
+<font color="#000080"><font color="#000080"><a href="chapter_3.5.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.2.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>&nbsp;23/03/06 (SR)</p>
+
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.5.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.2.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.5.2.html	(revision 5)
@@ -0,0 +1,82 @@
+<!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.2</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040802;13321506">
+  <meta name="CHANGED" content="20041112;14455666">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style></head>
+
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">&nbsp;3.5.2 Definition of user-defined
+parameters</h3>
+<p style="line-height: 100%;">As for the model in general, also the
+user-defined code will have to be steered by parameters. For each
+run the model should to be able to read in current values of these
+parameters. The declaration of user-defined parameters takes place in
+the user-defined module <tt><font style="font-size: 10pt;" size="2">user</font></tt>
+(located at the beginning of the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>).
+This module must be declared in all relevant user-defined routines via
+a USE statement, in order to make the parameters available. </p>
+<p style="line-height: 100%;">The user can assign values to the
+user-defined parameters within the NAMELIST group <tt><font style="font-size: 11pt;" size="2">&amp;userpar
+<font size="3"><font face="Thorndale, serif">in the local file</font></font>
+<a href="chapter_3.4.html#PARIN">PARIN</a></font></tt>.
+This NAMELIST group must be located after the initialization
+parameters and run parameters (<tt><font style="font-size: 10pt;" size="2">&amp;inipar</font></tt><font style="font-size: 10pt;" size="2">,
+</font><tt><font style="font-size: 10pt;" size="2">&amp;d3par</font></tt>)
+(see <a href="chapter_4.0.html">chapter
+4.0</a>). Before values of the user-defined parameters can be assigned,
+the parameters must be declared within the appropriate NAMELIST
+statement in the user-defined subroutine <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt>.
+</p>
+<p style="line-height: 100%;">The following example illustrates the
+procedure. The example assumes that the user declares a
+LOGICAL variable named <tt><font style="font-size: 10pt;" size="2">abcd</font></tt>
+for steering the user-defined code. This variable
+must be declared in the module <tt>user</tt>: </p>
+<ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">LOGICAL:: abcd = .FALSE.</font></tt></p>
+</ul>
+<p style="line-height: 100%;">Pay attention that in this example a
+default value (.FALSE.) is assigned to the variable and it will keep
+this value if nothing else is assigned within the file <tt>PARIN</tt>.
+In <tt><font style="font-size: 10pt;" size="2">user_parin</font> <font face="Thorndale, serif">the</font></tt>
+NAMELIST must be extended by the name of the new variable: </p>
+<ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">NAMELIST /userpar/ &nbsp;abcd, data_output_user, region.</font></tt></p>
+</ul>
+<p style="line-height: 100%;">In the parameter file PARIN a value can
+be assigned: </p>
+<ul>
+  <p style="line-height: 100%;">. <br>
+. <br>
+  <tt><font style="font-size: 10pt;" size="2">&amp;userpar abcd = .T.,</font></tt><font style="font-size: 10pt;" size="2"> ...</font></p>
+</ul>
+<p style="line-height: 100%;">User defined parameters in the file PARIN
+are
+considered as run parameters, i.e. they must be specified again for
+each restart run.</p>
+<p style="line-height: 100%;">In each case the user should carry out
+a control output of the parameter values, so
+that their values during the respective model run are really known. For
+this
+purpose the user-defined subroutine <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>
+which writes into the files <a href="chapter_3.4.html#HEADER">HEADER</a>
+and <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
+is available. <br>
+&nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+&nbsp;<font color="#000080"><font color="#000080"><a href="chapter_3.5.1.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.3.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a><br>
+</font></font></p>
+<p style="line-height: 100%;"><span style="font-style: italic;">Last
+change:</span> 24/03/06 (SR)<font color="#000080"><font color="#000080"><br>
+</font></font></p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.5.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.3.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.5.3.html	(revision 5)
@@ -0,0 +1,200 @@
+<!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)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040802;14001660">
+  <meta name="CHANGED" content="20041112;14483720">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</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
+<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
+and <a href="chapter_3.4.html#LIST_PROFIL">LIST_PROFIL</a>)
+always refer to the total model domain. Independently, up to 9 time
+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>.
+</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>,
+which has to be given the value 1.0 for all horizontal grid points
+belonging to
+the user-defined subdomain and the value 0.0, where grid points do not
+belong
+to the user-defined subdomain. In the model <tt><font size="2">rmask</font></tt>
+is
+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>
+</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>
+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
+=</font> </font><a href="chapter_4.1.html#nx">nx</a>
+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
+domain
+carries the index 0, the user-defined subdomains have the values 1 to
+9. </p>
+<p style="line-height: 100%;">The following example should illustrate
+this. Two subdomains are defined by the user. The first is determined
+by all grid
+points which lie within a circle whose center is equal to the
+(horizontal) center of the model domain and whose diameter is equal
+to half of the total horizontal domain size (square total domain
+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>:
+</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>
+</ul>
+<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>
+and <span style="font-family: monospace;">indices</span> are
+necessary in this example, because grid spacing and indices are used.
+All array elements of <span style="font-family: monospace;">rmask</span>
+(<span style="font-family: monospace;">rmask(:,:,:)</span>) are preset
+by the model with 1.0. In no case this assignment must be
+changed for the total domain (<span style="font-family: monospace;">rmask(:,:,0)</span>)!
+Computations and output for the user-defined subdomains only take place
+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
+assigned
+via the initialization parameter <a href="chapter_4.3.html#region">region</a>.
+Output of the names of the selected user-defined subdomains happens in
+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>.
+<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>
Index: palm/trunk/DOC/app/chapter_3.5.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.4.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.5.4.html	(revision 5)
@@ -0,0 +1,71 @@
+<!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.5</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040802;14050943">
+  <meta name="CHANGED" content="20041117;12180008">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style></head>
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;"><font size="4">3.5.4 User-defined output quantities<br>
+</font></h3>A very typical request of users is the calculation and
+output of
+quantities which are not part of PALM's standard output. The basic user
+interface includes a number of subroutines which allow the calculation
+of user-defined quantities and output of these quantities as 2d cross
+section or 3d volume data. The respective subroutines contain&nbsp;as
+an example code lines (written as comment lines) for calculating and
+output the square of the u-component velocity (note: this quantity
+could of course easily be calculated from the u-component by
+postprocessing the PALM output so that calculation within PALM is not
+necessarily required).<br><br>The
+rest of this chapter explains step-by-step how to modify/extend the
+default file user_interface.f90 in order to generate output of the
+quantity "square of the u-component". If more than one user-defined
+quantity shall be output, these steps have to be carried out in the
+same way for each of the quantities.<br><br><ol><li>The quantity has to be given a unique string identifier, e.g. <span style="font-style: italic;">'u2'</span>.
+This identifier must be different from the identifiers used for the
+PALM standard output (see list in description of parameter <a href="chapter_4.2.html#data_output">data_output</a>). To switch on output of this quantity, the user has to assign the string identifier to the parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>, eg.:<br><br><span style="font-family: monospace;">&nbsp; &nbsp; data_output_user</span> = <span style="font-style: italic;">'u2'</span>, <span style="font-style: italic;">&nbsp;'u2_xy_av'</span><br><br>The pure string <span style="font-style: italic;">'u2'</span>
+switches on the output of instantaneous 3d volume data. Output of cross
+section data and time averaged data is switched on by additionally
+appending the strings <span style="font-style: italic;">'_xy'</span>, <span style="font-style: italic;">'_xz'</span>, <span style="font-style: italic;">'_yz'</span>, and/or <span style="font-style: italic;">'_av'</span> (for a detailed explanation see parameter <a href="chapter_4.2.html#data_output">data_output</a>).<br><br></li><li>In order to store the quantities' grid point data within PALM, a 3d data array has to be declared in module <a href="chapter_3.5.1.html#user"><span style="font-family: monospace;">user</span></a>:<br><br><span style="font-family: monospace;">&nbsp; &nbsp; REAL, DIMENSION(:,:,:), ALLOCATABLE ::&nbsp; u2, u2_av</span><br><br>The second array <span style="font-family: monospace;">u2_av</span>
+is needed in case that output of time averaged data is requested. It is
+used to store the sum of the data of the respective time levels over
+which the average has to be carried out.<br><br><br></li><li>The data array has to be allocated in subroutine <a href="chapter_3.5.1.html#user_init"><span style="font-family: monospace;">user_init</span></a>:<br><br><span style="font-family: monospace;">&nbsp; &nbsp; ALLOCATE( u2(nzb:nzt+1,nys-1:nyn+1,nxl-1:nxr+1) )</span><br><br>In
+case that output of time averaged data is requested, the array
+containing the sum has possibly to be read from the restart file (local
+filename <a href="chapter_3.4.html#BININ">BININ</a>) by executing the following code in <span style="font-family: monospace;">user_init</span>:<br><br><span style="font-family: monospace;">&nbsp;&nbsp; &nbsp;IF ( initializing_actions == 'read_restart_data' )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; READ ( 13 )&nbsp; field_chr</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp; &nbsp;DO&nbsp; WHILE ( TRIM( field_chr ) /= '*** end user ***' )</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; SELECT CASE ( TRIM( field_chr ) )</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; CASE ( 'u2_av' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp; &nbsp; ALLOCATE( u2_av(nzb:nzt+1,nys-1:nyn+1,nxl-1:nxr+1) )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; READ ( 13 )&nbsp; u2_av</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp; &nbsp;&nbsp; CASE DEFAULT</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp; PRINT*, '+++ user_init: unknown
+variable named "', &amp;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+&nbsp; &nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TRIM(
+field_chr ), '" found in'</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; PRINT*,
+'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+data from prior run on PE ', myid</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; CALL local_stop</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; END SELECT<br>&nbsp; &nbsp; &nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp; &nbsp;ENDIF</span><br style="font-family: monospace;"><br><br></li><li>The quantity has to be given a unit (subroutine <a href="chapter_3.5.1.html#user_check_data_output"><span style="font-family: monospace;">user_check_data_output</span></a>):<br><br><span style="font-family: monospace;">&nbsp; &nbsp; CASE ( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; unit = 'm2/s2'</span><br>&nbsp;<br>Otherwise, PALM will abort.<br><br><br></li><li>The
+vertical grid on which the quantity is defined (given by the levels
+'zu' or 'zw', on which the u- or w-component of the velocity are
+defined) has to be specified for the NetCDF output files in subroutine <a href="chapter_3.5.1.html#user_define_netcdf_grid"><span style="font-family: monospace;">user_define_netcdf_grid</span></a>:<br><br><span style="font-family: monospace;">&nbsp;&nbsp; &nbsp;CASE ( 'u2', 'u2_xy', 'u2_xz', 'u2_yz' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp; &nbsp; &nbsp; grid = 'zu'</span><br>&nbsp;<br>As the example shows, this grid has to be defined for the 3d volume data as well as for all of the three cross sections.<br><span style="font-family: monospace;"><br><br></span></li><li>After each timestep, the quantity has to be calculated at all gridpoints and to be stored. This has to be done in subroutine <a href="chapter_3.5.1#user_actions"><span style="font-family: monospace;">user_actions</span></a> at location 'after_integration':<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;CASE ( 'after_integration' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">!</span><br style="font-family: monospace;"><span style="font-family: monospace;">!--&nbsp;&nbsp;&nbsp; Enter actions to be done after every time integration (before</span><br style="font-family: monospace;"><span style="font-family: monospace;">!--&nbsp;&nbsp;&nbsp; data output)</span><br style="font-family: monospace;"><span style="font-family: monospace;">!--&nbsp;&nbsp;&nbsp; Sample for user-defined output:</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nzt+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; u2(k,j,i) = u(k,j,i)**2</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br><br>&nbsp;<br></li><li>In
+case that output of time-averaged data is requested, the sum- and
+average-operations as well as the allocation of the sum-array have to
+be carried out in subroutine <a href="chapter_3.5.1.html#user_3d_data_averaging"><span style="font-family: monospace;">user_3d_data_averaging</span></a>:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; IF ( mode == 'allocate' )&nbsp; THEN<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CASE ( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IF ( .NOT. ALLOCATED( u2_av ) )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALLOCATE( u2_av(nzb:nzt+1,nys-1:nyn+1,nxl-1:nxr+1) )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDIF</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; u2_av = 0.0<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; ELSEIF ( mode == 'sum' )&nbsp; THEN<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CASE ( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nzt+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+u2_av(k,j,i) = u2_av(k,j,i) + u2(k,j,i)</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; ELSEIF ( mode == 'average' )&nbsp; THEN<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CASE ( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nzt+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+u2_av(k,j,i) = u2_av(k,j,i) / REAL( average_count_3d )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br><br>&nbsp;</li><li>For output of 2d cross sections, the gridpoint data of the quantity has to be resorted to array <span style="font-family: monospace;">local_pf</span> in subroutine <a href="chapter_3.5.1.html#user_data_output_2d"><span style="font-family: monospace;">user_data_output_2d</span></a>. Also the vertical grid, on which the quantity is defined, has to be set again:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;CASE ( 'u2_xy', 'u2_xz', 'u2_yz' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IF ( av == 0 )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nzt+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+local_pf(i,j,k) = u2(k,j,i)</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ELSE</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nzt+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+local_pf(i,j,k) = u2_av(k,j,i)</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDIF</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; grid = 'zu'</span><br>&nbsp;<br>The <span style="font-family: monospace;">ELSE</span> case is only needed in case that output of time-averaged data is requested.<br><br><br></li><li>For output of 3d volume data, the gridpoint data of the quantity has to be resorted to array <span style="font-family: monospace;">local_pf</span> in subroutine <a href="chapter_3.5.1.html#user_data_output_3d"><span style="font-family: monospace;">user_data_output_3d</span></a>. Also the vertical grid, on which the quantity is defined, has to be set again:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;CASE ( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IF ( av == 0 )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nz_do</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+local_pf(i,j,k) = u2(k,j,i)</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ELSE</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; i = nxl-1, nxr+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; j = nys-1, nyn+1</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DO&nbsp; k = nzb, nz_do</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+local_pf(i,j,k) = u2_av(k,j,i)</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENDIF</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; grid = 'zu'</span><br><br>The <span style="font-family: monospace;">ELSE</span> case is only needed in case that output of time-averaged data is requested.<br><br><br></li><li>In case of job chains, the sum array has to be written to the (binary) restart file (local filename <a href="chapter_3.4.html#BINOUT">BINOUT</a>) in subroutine <a href="chapter_3.5.1.html#user_last_actions"><span style="font-family: monospace;">user_last_actions</span></a>:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; IF ( ALLOCATED( u2_av ) )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+WRITE ( 14 )&nbsp;
+'u2_av&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+';&nbsp; WRITE ( 14 )&nbsp; u2_av</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; ENDIF</span><br><br>Otherwise, the calculated time-average may be wrong. &nbsp;</li></ol><hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.5.3.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.5.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="right.gif" name="Grafik3"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 24/03/06 (SR)</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.5.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.5.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.5.5.html	(revision 5)
@@ -0,0 +1,126 @@
+<!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.5</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040802;14050943">
+  <meta name="CHANGED" content="20041117;12180008">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;"><font size="4">3.5.5 Compiling and
+linking user-defined code<br>
+</font></h3>
+<p style="line-height: 100%;">The compiling and linking of
+user-defined code into a model run is done via the shellscript
+<a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>.
+The simplest (however not the most comfortable) way is by giving the
+filenames of the files containing the user-defined code as an argument
+of the shellscript option <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-s">-s</a>.
+If the user-defined subroutines are located e.g. on the two files <span
+ style="font-family: monospace;">user1.f90</span> and <span
+ style="font-family: monospace;">user2.f90</span>, then
+the <b>mrun</b> call has to be:<br>
+</p>
+<p style="line-height: 100%; margin-left: 40px;"><span
+ style="font-family: monospace;">mrun... -s "user1.f90 user2.f90" ... .</span><br>
+</p>
+<p style="line-height: 100%;">For this call the user has to be in the
+working directory <tt><tt><font style="font-size: 10pt;" size="2">~/palm/current_version/SOURCE</font></tt></tt>,
+because the file with the source code of the main program is located
+here. The main program is compiled with
+each model run (without the appropriate filename given as argument for
+the
+option -s). </p>
+<p style="line-height: 100%;">The call </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun
+ -s TEST
+,</font></pre>
+</ul>
+<p style="line-height: 100%;">is simpler and causes the compilation
+of all files with suffix <tt><font style="font-size: 10pt;" size="2">.f90</font></tt>
+located in the working
+directory <font face="Thorndale, serif">a</font>nd having
+user write permissions.&nbsp; Unchanged sources of the default model
+have read permission only and therefore are not compiled with that
+call. </p>
+<p style="line-height: 100%;">Typically, users may have different
+versions
+of user-defined code which are to be used for different model runs.
+According to the method just described for starting a certain model
+run,
+the associated user-defined code would have to be copied into the
+working directory and code for other runs may have to be
+removed (otherwise theses files would be compiled as well and the
+routines like <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt>
+would occur twice or several times which would lead to compiling
+errors). This procedure is quite tedious and can lead to errors if
+different
+model runs with restarts are to be carried out at the same time. It is
+better
+to store the different versions of user-defined code in different
+subdirectories
+using the base file name of the respective model run as subdirectory
+name. In this case a line like </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">% </font><a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#add_source_path"><font
+ style="font-size: 10pt;" size="2">add_source_path</font></a><font
+ style="font-size: 10pt;" size="2"> $HOME/palm/current_version/SOURCE/USER_CODE/$fname</font></pre>
+</ul>
+<p style="line-height: 100%;">has to be added to the <b>mrun</b>
+configuration file. If you call <b>mrun</b> now with </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -d run1  -s user1.f90 user2.f90
+,</font></pre>
+</ul>
+<p style="line-height: 100%;">the additional entry in the configuration
+file
+causes that the files given as argument of the option -s are also
+looked
+for in the directory <tt><font style="font-size: 10pt;" size="2">$HOME/palm/current_version/SOURCE/USER_CODE/run1</font></tt><font
+ style="font-size: 10pt;" size="2">,</font>
+in case they are not found in the current working directory. The
+specification of <tt><font style="font-size: 10pt;" size="2">-s</font><font
+ size="2">
+TEST</font></tt> in the <b>mrun</b> call now causes compilation of all
+files with suffix <tt><font style="font-size: 10pt;" size="2">.f90</font></tt>
+and user write permissions which are located in the working
+directory or in the directory indicated by <span
+ style="font-family: monospace;">add_source_path</span>. In
+this case no files with the same name are allowed to be in these two
+directories. </p>
+<p style="line-height: 100%;">Further detailed information for linking
+user-defined code with <b>mrun</b> can be found in <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter7">chapter
+7</a> of the <b>mrun </b>documentation (only in German). </p>
+<p style="line-height: 100%;">While programming user-defined code,
+errors are frequently made. Possible ways of error
+tracing are described in the next chapter. <br>
+&nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.5.3.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="chapter_3.6.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>
Index: palm/trunk/DOC/app/chapter_3.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.5.html	(revision 5)
@@ -0,0 +1,95 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html><head>
+  <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE">
+  
+  <title>PALM chapter 3.5</title><meta content="StarOffice 7  (Win32)" name="GENERATOR">
+  <meta content="Siegfried Raasch" name="AUTHOR">
+  <meta content="20040802;10431831" name="CREATED">
+  <meta content="20041112;14292662" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style></head>
+
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">3.5 Programming of user-defined code
+extensions<br>
+</h3>
+<p style="line-height: 100%;">Programming user-defined code
+extensions usually requires exact knowledge of the internal structure
+of PALM.
+Appropriate explanations in <a href="chapter_2.0.html">chapter
+2.0</a> and the technical documentation are usually not sufficient
+and must be supplemented by the rigorous study of the source code of
+the model. Programming experiences with FORTRAN95 and if necessary
+experiences with the parallelization tool MPI are absolutely
+neccessary! </p>
+<p style="line-height: 100%;">Changes of the standard model code by the
+user
+should be avoided whenever possible and are reserved to the
+developer-group of PALM. The corrections, revisions and extensions of
+the
+model accomplished by this group are published in the
+<a href="../tec/index.html">technical/numerical
+documentation</a> and the accordingly updated source files are
+accessible to the users (see <a href="chapter_5.1.html">chapter
+5.1</a>).</p>
+<p style="line-height: 100%;">However, the user frequently may feel the
+need to make extensions of the model code for his/her own simulations.
+For this purpose, a set
+of interfaces is available, which can be used to add user-defined code
+to the model. This
+chapter describes the programming of such user-defined code extensions.</p><p style="line-height: 100%;">The integration of user-defined code
+occurs in the form of subroutine calls, which are made at a set of
+places in the model code, by default. These subroutines have
+pre-defined names, which must not be changed by the user. Their basic
+versions are a component of the standard model
+code and they are all included in the source code file
+<tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt><font style="font-size: 10pt;" size="2">.</font>
+<font color="#000000">The</font> basic versions accomplish nearly no
+actions, thus they are pure templates, which can be extended by the
+user as required. Actions which are already accomplished in these
+basic versions by default should not be changed. Here is an example
+of such a basic version: </p>
+<p style="line-height: 100%;">&nbsp; </p>
+<pre style="line-height: 100%;"><font color="#000000"><font style="font-size: 10pt;" size="2">SUBROUTINE user_init</font></font><br><br><font color="#000000"><font style="font-size: 10pt;" size="2">!------------------------------------------------------------------------------</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">!</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">!</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">! Description:</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">! -----------</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">! Execution of user-defined initializing actions</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">!------------------------------------------------------------------------------</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">!</font></font><br><br><font color="#000000"> <font style="font-size: 10pt;" size="2">USE control_parameters</font></font><br><font color="#000000"> <font style="font-size: 10pt;" size="2">USE user</font></font><br><br><font color="#000000"> <font style="font-size: 10pt;" size="2">IMPLICIT NONE</font></font><br><br><font color="#000000"><font style="font-size: 10pt;" size="2">!</font></font><br><font color="#000000"><font style="font-size: 10pt;" size="2">!-- Here the user defined initializing actions follow:</font></font><br><br><br><font color="#000000"><font style="font-size: 10pt;" size="2">END SUBROUTINE user_init</font></font></pre>
+<p style="line-height: 100%;">The communication (handling of variables)
+with the model occurs via the
+global variables, which are defined within the individual FORTRAN -
+modules of PALM. The appropriate modules (they are all in the
+source code file <tt><font style="font-size: 10pt;" size="2">modules.f90</font></tt>)
+must be declared by means of <font size="2"><font face="Cumberland, monospace">USE</font></font> statements in the
+user-defined routines in order to be able to work with the variables
+contained in them. As in the example, this is already done with the
+module <tt><font style="font-size: 10pt;" size="2">control_parameters</font></tt>.
+This yields access to most of the existing parameters for steering the
+model. Furthermore, the module <tt><font style="font-size: 11pt;" size="2">user</font></tt> appears in the example
+above. This is a
+user-defined module (it is located at
+the beginning of the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>)
+and can be used for communication between the user-defined routines. In
+this module own variables can be declared as desired. It
+is not used outside of the user code. </p>
+<p style="line-height: 100%;">A very typical request of users is the
+calculation and output of
+quantities which are not part of PALM's standard output. Several
+routines in the basic user interface are already designed and prepared
+for calculating and output of such quantities (see <a href="chapter_3.5.4.html">3.5.4</a>).</p><p style="line-height: 100%;">As already mentioned, the contents of
+the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>
+can be used as a basis for extensions. However the file should not be
+manipulated directly (it is anyway write protected by default), but it
+should be
+copied to another file. User write permits for this new file must be
+declared by means of the unix command <tt><font style="font-size: 10pt;" size="2">chmod</font></tt>.
+</p>
+<p style="line-height: 100%;">The following sections describe, which
+interfaces for user-defined code exist in the
+model, how user parameters can be defined for steering this code
+and how it is translated and linked to the model. &nbsp;</p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.4.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.1.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 15/04/05 (SR)</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.6.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.6.html	(revision 5)
@@ -0,0 +1,137 @@
+<!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.6</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040809;10583400">
+  <meta name="CHANGED" content="20041112;15013624">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">3.6 Interactive mode and debugging</h3>
+<p style="line-height: 100%;">You can use <b>mrun</b> for running PALM
+in batch mode as well as for running it interactively. For interactive
+runs, you must (naturally) be logged in on the respective computer. For
+this computer the subroutines of the model must have
+been precompiled (see <a href="chapter_5.0.html">chapter
+5.0</a>). Furthermore, the working directory
+(<tt><font style="font-size: 10pt;" size="2">~/palm/current_version/SOURCE</font></tt>)
+must contain all default source code files of the model (<span
+ style="font-family: monospace;">*.f90</span>), the <b>mrun</b>
+configuration file (<span style="font-family: monospace;">.mrun.config</span>)
+the Makefile (<span style="font-family: monospace;">Makefile</span>)
+and the files which contain the user-defined code (the default
+user-interface file <span style="font-family: monospace;">user_interface.f90</span>
+have to be removed from the directory). All output-files possibly
+created by the model and requested by the user to be kept after the run
+are copied to
+directories on the local host corresponding to the specifications
+in the configuration file (in this case the file attribute <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tr">tr</a>
+does not cause transfer to another computer). </p>
+<p style="line-height: 100%;">Since model runs usually require large
+amounts of CPU time, interactive runs are usually not feasible, since
+in interactive mode CPU time
+is strongly limited on many hosts and runs will be aborted
+after the time limit has been exceeded. However, an interactive run
+makes sense if a suitable debugger is available,
+which may be used for error tracing in the model (here, error tracing
+in
+the user-defined software is meant). The preparations neccessary for
+debugging are described in the following. This
+description is limited to the IBM Regatta "hanni" and "berni" of the
+HLRN. </p>
+<p style="line-height: 100%;">If certain routines of the model
+are to be debugged for errors, the complete source code of
+the model, including the user-defined code, must be compiled
+with special debug compiler options. For this purpose, at least the
+following three lines must be included in the <span
+ style="font-weight: bold;">mrun </span>configuration file:<br>
+</p>
+<p style="line-height: 100%;"><span style="font-family: monospace;">%compiler_name&nbsp;&nbsp;&nbsp;&nbsp;
+mpxlf95_r&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;&nbsp;&nbsp;&nbsp;&nbsp;
+ibmh parallel debug</span><br style="font-family: monospace;">
+<span style="font-family: monospace;">%fopts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-g:-C:-qinitauto=FF:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-qarch=pwr4:-qnosave:-qnoescape:-qflttrap=overflow::zerodivide:<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+:invalid::enable:-qsigtrap&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ibmh parallel debug</span><br style="font-family: monospace;">
+<span style="font-family: monospace;">%lopts&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-g:-C:-qinitauto=FF:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-qarch=pwr4:-qnosave:-qnoescape:-qflttrap=overflow::zerodivide:<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+:invalid::enable:-qsigtrap:-lesslsmp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ibmh parallel debug</span><br style="font-family: monospace;">
+<br>
+</p>
+<p style="line-height: 100%;">(Attention: in the configuration file,
+the compiler and linker options (<span style="font-family: monospace;">fopts</span>
+and <span style="font-family: monospace;">lopts</span>) must be
+written in one line without any blank space before and after the
+colons!)<br>
+</p>
+<p style="line-height: 100%;">Using the compiler options "<span
+ style="font-family: monospace;">-g</span>" and "<span
+ style="font-family: monospace;">-C</span>", debugable code is created
+and check of array bounds is
+switched on during run time. Option "-qinitauto=FF" initializes all
+automatic variables (unfortunately not the global values of modules) to
+NaN.The "<span style="font-family: monospace;">-qflttrap</span>" and "<span
+ style="font-family: monospace;">-qsigtrap</span>" options are needed
+in order to terminate the run in case of any floating point errors
+(otherwise the run will not terminate and errors can hardly be
+detected).<br>
+</p>
+<p style="line-height: 100%;">The <b>mrun </b>call for debugging
+needs
+an extended argument for the option <tt><font style="font-size: 10pt;"
+ size="2">-K</font></tt><font style="font-size: 10pt;" size="2">:</font>
+</p>
+<ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
+ size="2">mrun ... -K parallel debug -s *.f90" ... .<br>
+  </font></tt></p>
+</ul>
+<p style="line-height: 100%;">The argument of option <tt><font
+ style="font-size: 10pt;" size="2">-s</font></tt>
+must list all source code files of the model. </p>
+<p style="line-height: 100%;">After compiling, the debugger
+<b>TotalView</b> is automatically called by <span
+ style="font-weight: bold;">mrun</span>. With its assistance the user
+has to start
+the program execution manually, to set breakpoints, etc.. User manuals
+of <b>TotalView</b> are available <a
+ href="http://www.hlrn.de/doc/totalview/index.html">online</a>. </p>
+<p style="line-height: 100%;">Program crashes caused by errors in the
+user-defined code should usually be found
+unassisted. If the termination point lies outside the user code (in the
+default model code), the PALM developer group had possibly be asked for
+assistance. It is emphasized again that error tracing and programming
+of
+user-defined code requires more or less precise knowledge of the
+internal structure of PALM (see beginning of <a href="chapter_3.5.html">chapter
+3.5</a>). <br>
+&nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.5.5.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.7.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>
Index: palm/trunk/DOC/app/chapter_3.7.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.7.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_3.7.html	(revision 5)
@@ -0,0 +1,141 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=windows-1252">
+  <title>PALM chapter 3.7</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040809;13460943">
+  <meta name="CHANGED" content="20041112;15085727">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">3.7 Optional software packages</h3>
+<p style="line-height: 100%;">Starting from version 2.1 PALM includes
+so-called software packages which can be used optionally. These
+software packages are part of the model, but they are not compiled with
+the default model
+installation (actually, the routines of the corresponding packages are
+compiled within the installation, but these subroutines are empty,
+i.e. they do not contain any executable statements). Thus the
+compilation time as well as the memory demand of the model is limited
+to the real needs. </p>
+<p style="line-height: 100%;">To use software packages in a model run,
+they must be requested with <b>mrun</b> option <tt><font
+ style="font-size: 10pt;" size="2">-p</font>.</tt>
+Then the subroutines belonging to the respective package are
+additionally compiled for the run (and the respective restart
+runs; the filenames of these subroutines are also displayed on the
+terminal after <b>mrun</b> has been called). If one wants to use e.g.
+the two packages with the names
+<tt>package1</tt> and <tt>package2</tt>, then the <b>mrun</b> call
+has to be: </p>
+<ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
+ size="2">mrun ... -p package1 package2 </font>.</tt></p>
+</ul>
+<p style="line-height: 100%;">Further package names can be added to
+the list, separated by blanks. If the respective packages permit user
+steering, the appropriate parameters must be given at the end of
+the file <a href="chapter_3.4.html#PARIN">PARIN</a>.
+They must be given <b>before</b> possible user-defined parameters!
+Each package requires its own NAMELIST group. The respective NAMELIST
+group name is given in the table below. For the example above one
+would have to add the following lines to PARIN (example): &nbsp; </p>
+<ul>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
+ size="2">&amp;namelist_packagename1 var1 = 1,0, var2 =
+abcd /</font></tt><font style="font-size: 10pt;" size="2"> </font> </p>
+  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
+ size="2">&amp;namelist_packagename2 var3 = .TRUE.,
+var4 = 0 /</font></tt></p>
+</ul>
+<p style="margin-bottom: 0cm; line-height: 100%;">The following
+packages are available: <br>
+&nbsp; <br>
+&nbsp; </p>
+<table border="1" cellpadding="2" cellspacing="2" width="100%">
+  <tbody>
+    <tr>
+      <td>
+      <p><b>Package name:</b></p>
+      </td>
+      <td>
+      <p><b>NAMELIST group name:</b></p>
+      </td>
+      <td>
+      <p><b>Functionality:</b></p>
+      </td>
+      <td>
+      <p><b>Control parameter:</b></p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td>
+      <p>particles</p>
+      </td>
+      <td>
+      <p>particles_par</p>
+      </td>
+      <td>
+      <p>Release and advection of particles. The particle sources can
+additionally be defined by the user in subroutine <tt><font
+ style="font-size: 10pt;" size="2">user_init_particles</font></tt> .</p>
+      </td>
+      <td>
+      <p>see section 4.2</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td>
+      <p>dvrp_graphics</p>
+      </td>
+      <td>
+      <p>dvrp_graphics_par</p>
+      </td>
+      <td>
+      <p>Graphical output with the dvrp software of the RRZN. This is
+only available on the IBM Regatta "hanni" of the HLRN. Possible output
+are iso-surfaces, cross-sections and particles (if the particle package
+is selected). The use of this package is described in section <a
+ href="chapter_4.5.7.html">4.5.7</a>.</p>
+      </td>
+      <td>
+      <p>see section 4.2</p>
+      </td>
+    </tr>
+    <tr valign="top">
+      <td>
+      <p>spectra</p>
+      </td>
+      <td>
+      <p>spectra_par</p>
+      </td>
+      <td>
+      <p>Computation and output of horizontal power spectra of the
+prognostic variables. </p>
+      </td>
+      <td>
+      <p>see section <a href="chapter_4.2.html#spectra_package">4.2</a></p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="chapter_4.0.html"><font
+ color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
+ border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 15/04/05 (SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.0.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.0.html	(revision 5)
@@ -0,0 +1,173 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="CONTENT-TYPE"
+ content="text/html; charset=windows-1252">
+  <title>PALM chapter 4.0</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20040809;14214479">
+  <meta name="CHANGED" content="20041112;15151993">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h2 style="line-height: 100%;"><font size="4">4.0 Steering parameters</font></h2>
+<p style="line-height: 100%;">Before carrying out a model run, the user
+has to /determine/ a data set - the model parameters - e.g. how
+many grid points are to be used, how large the horizontal and
+vertical grid spacing should be, which kind of boundary conditions are
+to be used for the individual variables, which numerical schemes
+implemented in the model are to be used, how long the simulated time
+should be, at which times and points plot output are supposed to be
+made, etc. <br>
+</p>
+<p style="line-height: 100%;">These data are assigned with the help of
+so-called ?NAMELIST-driven input? (FORTRAN - NAMELIST 
+input). The ?gewählten? values of the model parameters are written
+into an ASCII file with fixed format, which is expected by the model as
+an input
+file under the local name <a href="chapter_3.4.html#PARIN">PARIN</a>.
+On this file the parameters are represented by their variable names
+they have in the model. These parameters can be assigned one or more
+values, depending on the type and size the variable has. The following
+example shows the format of the file
+PARIN: <br>
+&nbsp; </p>
+<ul>
+  <p style="line-height: 100%; font-family: monospace;">&amp;inipar nx
+= 79, ny = 79, nz = 40, <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dx = 50.0, dy = 50.0, dz =
+50.0, <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; initializing_actions =
+"set_1d-model_profiles", <br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; prandtl_layer = .TRUE.,/ </p>
+  <p style="line-height: 100%; font-family: monospace;">&amp;d3par&nbsp;
+end_time = 9000.0, section_xy = 1, 10, 20,/ </p>
+  <p style="line-height: 100%; font-family: monospace;">&amp;packagename
+var1 = .TRUE. / </p>
+  <p style="line-height: 100%;"><span style="font-family: monospace;">&amp;userpar
+abcd = 1234,0,/ </span><br>
+&nbsp; <br>
+&nbsp;</p>
+</ul>
+<p style="line-height: 100%;">The parameters are separated into four
+different groups which all start with the so-called NAMELIST group
+names.
+These are <span style="font-family: monospace;">&amp;inipar</span>, <span
+ style="font-family: monospace;">&amp;d3par</span> and <span
+ style="font-family: monospace;">&amp;packagename</span> as well as <span
+ style="font-family: monospace;">&amp;userpar</span>. In each case a
+group is terminated with one backslash ("/"). Between the beginning of
+the line and the group name at least one blank has to be typed. Between
+the
+group names and the "/", the
+values are assigned to the variables. The example shows that in
+principle all FORTRAN data types are allowed. For more details
+concerning the NAMELIST syntax, refer to
+appropriate FORTRAN manuals. <br>
+</p>
+<p style="line-height: 100%;">Parameters belonging to the group <span
+ style="font-family: monospace;">inipar</span> are first read by PALM.
+These are the initialization parameters. Second, the so-called run
+parameters belonging to the group <span style="font-family: monospace;">d3par</span>
+are read in, then the parameters for steering the optional software
+packages (group <span style="font-family: monospace;">packagename,</span>
+the string <span style="font-family: monospace;">"packagename"</span>
+must be replaced by the NAMELIST
+group name of the respective package) as well as user-defined
+parameters
+(group <span style="font-family: monospace;">userpar</span>). The four
+groups must be given in this order, the last groups, <span
+ style="font-family: monospace;">packagename</span> and <span
+ style="font-family: monospace;">userpar</span>, may
+be omitted. If several software packages are selected
+(see chapter <a href="chapter_3.7.html">3.7</a>),
+further NAMELIST groups may be inserted before the group <span
+ style="font-family: monospace;">userpar</span>.
+</p>
+<p style="line-height: 100%;"><b>The initialization, run</b> and
+<b>package parameters</b> differ as follows: </p>
+<ul>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
+parameters </b>are steering the basic settings of the model run. They
+define e.g. the number of the grid points, the numerical schemes to be
+used, initial and boundary conditions to be applied, how the
+three-dimensional fields are initialized at the beginning of a model
+run (constant&nbsp; value profiles or 1D-model-pre-run, the initial
+temperature profile etc.). These parameters apply to the total model
+run and thus can not be changed with restart runs! If one tries to
+change these values within the NAMELIST input file of a restart run,
+then these changes are ignored (sole exception is the parameter <a
+ style="font-family: monospace;"
+ href="chapter_4.1.html#initializing_actions">initializing_actions</a><font
+ style="font-size: 10pt;" size="2">, </font>which must be given the
+value<span style="font-family: thorndale,serif,mon;"> </span><span
+ style="font-family: monospace; font-style: italic;">read_restart_data</span><span
+ style="font-family: thorndale,serif,mon;"> for </span>restart runs). <br>
+&nbsp; </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
+parameters</b> are generally steering actions to be carried out during
+a model run. One can select for example, at which times plot output
+should happen and which variables are to be written. Additionally one
+can (and must) specify the time to be simulated. Run parameters only
+apply to the actual run (job) and with each restart run other values
+may be declared (if runs are restarted automatically, parameters will
+usually keep their values, provided that the NAMELIST input file was
+not changed by the user in the meantime). <br>
+&nbsp; </p>
+  </li>
+  <li>
+    <p style="line-height: 100%;"><b>Package parameters</b> behave like
+    <b>run parameters</b>. Package parameters determine the behavior of
+the additional (not user-defined) software packages . </p>
+  </li>
+</ul>
+<p style="line-height: 100%;">The user-defined parameters are assigned
+by the user within the NAMELIST group name <tt>&amp;userpar</tt> (see <a
+ href="chapter_3.5.2.html">chapter
+3.5.2</a>). They steer actions programmed by the user. By default,
+this group has only one parameter (<a href="chapter_4.3.html#region">region</a>).
+If the
+user don't want to assign any values to the user-defined&nbsp;
+parameters, the group<span style="font-family: monospace;"> userpar
+</span>may be omitted. The group name <span
+ style="font-family: monospace;">&amp;userpar</span>
+can be changed by the user in the user-defined code. In
+addition to this, further NAMELIST groups may also be declared (all
+within routine <span style="font-family: monospace;">user_parin</span>
+in file <span style="font-family: monospace;">user_interface.f90</span>).
+<a href="chapter_4.4.html">Chapter
+4.4</a> shows a simple but complete example of the input file PARIN.
+This example file can be used together with the configuration file
+(described in <a href="chapter_3.2.html">chapter
+3.2</a>) for the execution of a model test run. </p>
+<p style="line-height: 100%;">PALM assigns default
+values to nearly all parameters. They become effective
+if no other assignments are given in the parameter file. These
+default values as well as the parameter name, type and its
+explanation are described in the lists of the following subsections. <br>
+&nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="chapter_4.1.html"><font
+ color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
+ border="2" height="32" width="32"></font></a></font></font><br>
+&nbsp;
+<br>
+&nbsp;<span style="font-style: italic;">Last change:</span> 15/04/05
+(SR)<br>
+</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.1.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.1.html	(revision 5)
@@ -0,0 +1,19273 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+
+
+
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>PALM chapter 4.1</title></head>
+<body>
+
+
+
+
+
+
+
+
+
+
+<h3><a name="chapter4.1"></a>4.1 Initialization parameters</h3>
+
+
+
+
+
+
+
+
+
+
+<br>
+
+
+
+
+
+
+
+
+
+
+<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
+
+
+
+
+
+
+
+
+
+
+  <tbody>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><font size="4"><b>Parameter name</b></font></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><b><font size="4">Default</font></b> <br>
+
+
+
+
+
+
+
+
+
+
+      <b><font size="4">value</font></b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="adjust_mixing_length"></a><b>adjust_mixing_length</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Near-surface adjustment of the
+mixing length to the Prandtl-layer law.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Usually the mixing length in LES models l<sub>LES</sub>
+depends (as in PALM) on the grid size and is possibly restricted
+further in case of stable stratification and near the lower wall (see
+parameter <a href="#wall_adjustment">wall_adjustment</a>).
+With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span>
+the Prandtl' mixing length l<sub>PR</sub> = kappa * z/phi is calculated
+and the mixing length actually used in the model is set l = MIN (l<sub>LES</sub>,
+l<sub>PR</sub>). This usually gives a decrease of the mixing length at
+the bottom boundary and considers the fact that eddy sizes
+decrease in the vicinity of the wall.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;"><b>Warning:</b> So far, there is
+no good experience with <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> !&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> and the Prandtl-layer being
+switched on (see <a href="#prandtl_layer">prandtl_layer</a>) <span style="font-style: italic;">'(u*)** 2+neumann'</span>
+should always be set as the lower boundary condition for the TKE (see <a href="#bc_e_b">bc_e_b</a>),
+otherwise the near-surface value of the TKE is not in agreement with
+the Prandtl-layer law (Prandtl-layer law and Prandtl-Kolmogorov-Ansatz
+should provide the same value for K<sub>m</sub>). A warning is given,
+if this is not the case.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="alpha_surface"></a><b>alpha_surface</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Inclination of the model domain
+with respect to the horizontal (in degrees).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">By means of <b>alpha_surface</b>
+the model domain can be inclined in x-direction with respect to the
+horizontal. In this way flows over inclined surfaces (e.g. drainage
+flows, gravity flows) can be simulated. In case of <b>alpha_surface </b>/=
+      <span style="font-style: italic;">0</span> the buoyancy term
+appears both in
+the equation of motion of the u-component and of the w-component.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">An inclination is only possible in
+case of cyclic horizontal boundary conditions along x AND y (see <a href="#bc_lr">bc_lr</a>
+and <a href="#bc_ns">bc_ns</a>) and <a href="#topography">topography</a> = <span style="font-style: italic;">'flat'</span>. </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Runs with inclined surface still require additional
+user-defined code as well as modifications to the default code. Please
+ask the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">PALM
+developer&nbsp; group</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_e_b"></a><b>bc_e_b</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Bottom boundary condition of the
+TKE.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><b>bc_e_b</b> may be set to&nbsp;<span style="font-style: italic;">'neumann'</span> or <span style="font-style: italic;">'(u*) ** 2+neumann'</span>. <b>bc_e_b</b>
+= <span style="font-style: italic;">'neumann'</span> yields to
+e(k=0)=e(k=1) (Neumann boundary condition), where e(k=1) is calculated
+via the prognostic TKE equation. Choice of <span style="font-style: italic;">'(u*)**2+neumann'</span> also yields to
+e(k=0)=e(k=1), but the TKE at the Prandtl-layer top (k=1) is calculated
+diagnostically by e(k=1)=(us/0.1)**2. However, this is only allowed if
+a Prandtl-layer is used (<a href="#prandtl_layer">prandtl_layer</a>).
+If this is not the case, a warning is given and <b>bc_e_b</b> is reset
+to <span style="font-style: italic;">'neumann'</span>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">At the top boundary a Neumann
+boundary condition is generally used: (e(nz+1) = e(nz)).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_lr"></a><b>bc_lr</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Boundary
+condition along x (for all quantities).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+By default, a cyclic boundary condition is used along x.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-weight: bold;">bc_lr</span> may also be
+assigned the values <span style="font-style: italic;">'dirichlet/neumann'</span>
+(inflow from left, outflow to the right) or <span style="font-style: italic;">'neumann/dirichlet'</span> (inflow from
+right, outflow to the left). This requires the multi-grid method to be
+used for solving the Poisson equation for perturbation pressure (see <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</a>)
+and it also requires cyclic boundary conditions along y (see<br>
+
+
+
+
+
+
+
+
+
+
+      <a href="#bc_ns">bc_ns</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+In case of these non-cyclic lateral boundaries, a Dirichlet condition
+is used at the inflow for all quantities (initial vertical profiles -
+see <a href="#initializing_actions">initializing_actions</a>
+- are fixed during the run) except u, to which a Neumann (zero
+gradient) condition is applied. At the outflow, a Neumann (zero
+gradient) condition is used for all quantities except v, which is set
+to its horizontal average along the outflow (e.g. v(k,:,nx+1) =
+average_along_y( v(k,:,nx)), and except w, which is set to zero
+(Dirichlet condition). These conditions ensure the velocity field to be
+free of divergence at the inflow and at the outflow. For perturbation
+pressure Neumann (zero gradient) conditions are assumed both at the
+inflow and at the outflow.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+When using non-cyclic lateral boundaries, a filter is applied to the
+velocity field in the vicinity of the outflow in order to suppress any
+reflections of outgoing disturbances (see <a href="#km_damp_max">km_damp_max</a>
+and <a href="#outflow_damping_width">outflow_damping_width</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+In order to maintain a turbulent state of the flow, it may be
+neccessary to continuously impose perturbations on the horizontal
+velocity field in the vicinity of the inflow throughout the whole run.
+This can be switched on using <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#create_disturbances">create_disturbances</a>.
+The horizontal range to which these perturbations are applied is
+controlled by the parameters <a href="#inflow_disturbance_begin">inflow_disturbance_begin</a>
+and <a href="#inflow_disturbance_end">inflow_disturbance_end</a>.
+The vertical range and the perturbation amplitude are given by <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_b</a>,
+      <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_t</a>,
+and <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_amplitude</a>.
+The time interval at which perturbations are to be imposed is set by <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#dt_disturb">dt_disturb</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+In case of non-cyclic horizontal boundaries <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#call_psolver_at_all_substeps">call_psolver
+at_all_substeps</a> = .T. should be used.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-weight: bold;">Note:</span><br>
+
+
+
+
+
+
+
+
+
+
+Using non-cyclic lateral boundaries requires very sensitive adjustments
+of the inflow (vertical profiles) and the bottom boundary conditions,
+e.g. a surface heating should not be applied near the inflow boundary
+because this may significantly disturb the inflow. Please check the
+model results very carefully.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_ns"></a><b>bc_ns</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Boundary
+condition along y (for all quantities).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+By default, a cyclic boundary condition is used along y.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-weight: bold;">bc_ns</span> may also be
+assigned the values <span style="font-style: italic;">'dirichlet/neumann'</span>
+(inflow from rear ("north"), outflow to the front ("south")) or <span style="font-style: italic;">'neumann/dirichlet'</span>
+(inflow from front ("south"), outflow to the rear ("north")). This
+requires the multi-grid
+method to be used for solving the Poisson equation for perturbation
+pressure (see <a href="chapter_4.2.html#psolver">psolver</a>)
+and it also requires cyclic boundary conditions along x (see<br>
+
+
+
+
+
+
+
+
+
+
+      <a href="#bc_lr">bc_lr</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+In case of these non-cyclic lateral boundaries, a Dirichlet condition
+is used at the inflow for all quantities (initial vertical profiles -
+see <a href="#initializing_actions">initializing_actions</a>
+- are fixed during the run) except v, to which a Neumann (zero
+gradient) condition is applied. At the outflow, a Neumann (zero
+gradient) condition is used for all quantities except u, which is set
+to its horizontal average along the outflow (e.g. u(k,ny+1,:) =
+average_along_x( u(k,ny,:)), and except w, which is set to zero
+(Dirichlet condition). These conditions ensure the velocity field to be
+free of divergence at the inflow and at the outflow. For perturbation
+pressure Neumann (zero gradient) conditions are assumed both at the
+inflow and at the outflow.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+For further details regarding non-cyclic lateral boundary conditions
+see <a href="#bc_lr">bc_lr</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_p_b"></a><b>bc_p_b</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Bottom boundary condition of the
+perturbation pressure.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>,
+      <span style="font-style: italic;">'neumann'</span> and <span style="font-style: italic;">'neumann+inhomo'</span>.&nbsp; <span style="font-style: italic;">'dirichlet'</span> sets
+p(k=0)=0.0,&nbsp; <span style="font-style: italic;">'neumann'</span>
+sets p(k=0)=p(k=1). <span style="font-style: italic;">'neumann+inhomo'</span>
+corresponds to an extended Neumann boundary condition where heat flux
+or temperature inhomogeneities near the
+surface (pt(k=1))&nbsp; are additionally regarded (see Shen and LeClerc
+(1995, Q.J.R. Meteorol. Soc.,
+1209)). This condition is only permitted with the Prandtl-layer
+switched on (<a href="#prandtl_layer">prandtl_layer</a>),
+otherwise the run is terminated.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Since at the bottom boundary of the model the vertical
+velocity
+disappears (w(k=0) = 0.0), the consistent Neumann condition (<span style="font-style: italic;">'neumann'</span> or <span style="font-style: italic;">'neumann+inhomo'</span>) dp/dz = 0 should
+be used, which leaves the vertical component w unchanged when the
+pressure solver is applied. Simultaneous use of the Neumann boundary
+conditions both at the bottom and at the top boundary (<a href="#bc_p_t">bc_p_t</a>)
+usually yields no consistent solution for the perturbation pressure and
+should be avoided.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_p_t"></a><b>bc_p_t</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Top boundary condition of the
+perturbation pressure.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Allowed values are <span style="font-style: italic;">'dirichlet'</span> (p(k=nz+1)= 0.0) or <span style="font-style: italic;">'neumann'</span>
+(p(k=nz+1)=p(k=nz)).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Simultaneous use of Neumann boundary conditions both at the
+top and bottom boundary (<a href="#bc_p_b">bc_p_b</a>)
+usually yields no consistent solution for the perturbation pressure and
+should be avoided. Since at the bottom boundary the Neumann
+condition&nbsp; is a good choice (see <a href="#bc_p_b">bc_p_b</a>),
+a Dirichlet condition should be set at the top boundary.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_pt_b"></a><b>bc_pt_b</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C*20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Bottom boundary condition of the
+potential temperature.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+(pt(k=0) = const. = <a href="#pt_surface">pt_surface</a>
++ <a href="#pt_surface_initial_change">pt_surface_initial_change</a>;
+the user may change this value during the run using user-defined code)
+and <span style="font-style: italic;">'neumann'</span>
+(pt(k=0)=pt(k=1)).&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+When a constant surface sensible heat flux is used (<a href="#surface_heatflux">surface_heatflux</a>), <b>bc_pt_b</b> = <span style="font-style: italic;">'neumann'</span>
+must be used, because otherwise the resolved scale may contribute to
+the surface flux so that a constant value cannot be guaranteed.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="pc_pt_t"></a><b>bc_pt_t</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Top boundary condition of the
+potential temperature.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed are the values <span style="font-style: italic;">'dirichlet'
+      </span>(pt(k=nz) and pt(k=nz+1)
+do not change during the run) and <span style="font-style: italic;">'neumann'</span>.
+With the Neumann boundary
+condition the value of the temperature gradient at the top is
+calculated from the initial
+temperature profile (see <a href="#pt_surface">pt_surface</a>, <a href="#pt_vertical_gradient">pt_vertical_gradient</a>)
+by bc_pt_t_val = (pt_init(k=nz) -
+pt_init(k=nz-1)) / dzu(nz).<br>
+
+
+
+
+
+
+
+
+
+
+Using this value (assumed constant during the
+run) the temperature boundary values are calculated as&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">pt(k=nz) = pt(k=nz-1) +
+bc_pt_t_val * dzu(nz)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">and&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">pt(k=nz+1) = pt(k=nz) +
+bc_pt_t_val * dzu(nz+1)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">(up to k=nz-1 the prognostic
+equation for the temperature is solved).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_q_b"></a><b>bc_q_b</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Bottom boundary condition of the
+specific humidity / total water content.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+(q(k=0) = const. = <a href="#q_surface">q_surface</a>
++ <a href="#q_surface_initial_change">q_surface_initial_change</a>;
+the user may change this value during the run using user-defined code)
+and <span style="font-style: italic;">'neumann'</span>
+(q(k=0)=q(k=1)).&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+When a constant surface latent heat flux is used (<a href="#surface_waterflux">surface_waterflux</a>), <b>bc_q_b</b> = <span style="font-style: italic;">'neumann'</span>
+must be used, because otherwise the resolved scale may contribute to
+the surface flux so that a constant value cannot be guaranteed.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_q_t"></a><b>bc_q_t</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">C
+* 20</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Top boundary condition of the
+specific humidity / total water content.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed are the values <span style="font-style: italic;">'dirichlet'</span>
+(q(k=nz) and q(k=nz+1) do
+not change during the run) and <span style="font-style: italic;">'neumann'</span>.
+With the Neumann boundary
+condition the value of the humidity gradient at the top is calculated
+from the
+initial humidity profile (see <a href="#q_surface">q_surface</a>, <a href="#q_vertical_gradient">q_vertical_gradient</a>)
+by: bc_q_t_val = ( q_init(k=nz) - q_init(k=nz-1)) / dzu(nz).<br>
+
+
+
+
+
+
+
+
+
+
+Using this value (assumed constant during the run) the humidity
+boundary values
+are calculated as&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">q(k=nz) = q(k=nz-1) +
+bc_q_t_val * dzu(nz)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">and&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">q(k=nz+1) =q(k=nz) +
+bc_q_t_val * dzu(nz+1)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">(up tp k=nz-1 the prognostic
+equation for q is solved). </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_s_b"></a><b>bc_s_b</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Bottom boundary condition of the
+scalar concentration.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+(s(k=0) = const. = <a href="#s_surface">s_surface</a>
++ <a href="#s_surface_initial_change">s_surface_initial_change</a>;
+the user may change this value during the run using user-defined code)
+and <span style="font-style: italic;">'neumann'</span> (s(k=0) =
+s(k=1)).&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+When a constant surface concentration flux is used (<a href="#surface_scalarflux">surface_scalarflux</a>), <b>bc_s_b</b> = <span style="font-style: italic;">'neumann'</span>
+must be used, because otherwise the resolved scale may contribute to
+the surface flux so that a constant value cannot be guaranteed.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_s_t"></a><b>bc_s_t</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Top boundary condition of the
+scalar concentration.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed are the values <span style="font-style: italic;">'dirichlet'</span>
+(s(k=nz) and s(k=nz+1) do
+not change during the run) and <span style="font-style: italic;">'neumann'</span>.
+With the Neumann boundary
+condition the value of the scalar concentration gradient at the top is
+calculated
+from the initial scalar concentration profile (see <a href="#s_surface">s_surface</a>,
+      <a href="#s_vertical_gradient">s_vertical_gradient</a>)
+by: bc_s_t_val = (s_init(k=nz) - s_init(k=nz-1)) / dzu(nz).<br>
+
+
+
+
+
+
+
+
+
+
+Using this value (assumed constant during the run) the concentration
+boundary values
+are calculated as </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">s(k=nz) = s(k=nz-1) +
+bc_s_t_val * dzu(nz)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">and&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">s(k=nz+1) = s(k=nz) +
+bc_s_t_val * dzu(nz+1)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">(up to k=nz-1 the prognostic
+equation for the scalar concentration is
+solved).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_uv_b"></a><b>bc_uv_b</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Bottom boundary condition of the
+horizontal velocity components u and v.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed values are <span style="font-style: italic;">'dirichlet'
+      </span>and <span style="font-style: italic;">'neumann'</span>. <b>bc_uv_b</b>
+= <span style="font-style: italic;">'dirichlet'</span> yields the
+no-slip condition with u=v=0 at the bottom. Due to the staggered grid
+u(k=0) and v(k=0) are located at z = - 0,5 * <a href="#dz">dz</a>
+(below the bottom), while u(k=1) and v(k=1) are located at z = +0,5 *
+dz. u=v=0 at the bottom is guaranteed using mirror boundary
+condition:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p style="font-style: normal;">u(k=0) = - u(k=1) and v(k=0) = -
+v(k=1)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">The Neumann boundary condition
+yields the free-slip condition with u(k=0) = u(k=1) and v(k=0) =
+v(k=1).
+With Prandtl - layer switched on, the free-slip condition is not
+allowed (otherwise the run will be terminated)<font color="#000000">.</font></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="bc_uv_t"></a><b>bc_uv_t</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Top boundary condition of the
+horizontal velocity components u and v.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed values are <span style="font-style: italic;">'dirichlet'</span>
+and <span style="font-style: italic;">'neumann'</span>. The
+Dirichlet condition yields u(k=nz+1) = ug(nz+1) and v(k=nz+1) =
+vg(nz+1),
+Neumann condition yields the free-slip condition with u(k=nz+1) =
+u(k=nz) and v(k=nz+1) = v(k=nz) (up to k=nz the prognostic equations
+for the velocities are solved).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_height"></a>building_height</span></td>
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
+
+
+
+
+
+
+      <td>Height of a single building in m.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+      <span style="font-weight: bold;">building_height</span> must be less than the height of the model domain. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.</td>
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_x"></a>building_length_x</span></td>
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
+
+
+
+
+
+
+      <td><span style="font-style: italic;"></span>Width of a single building in m.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+Currently, <span style="font-weight: bold;">building_length_x</span> must be at least <span style="font-style: italic;">3 *&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#nx">nx</a><span style="font-style: italic;"> - 1 ) </span><span style="font-style: italic;"> * <a href="#dx">dx</a> </span><span style="font-style: italic;">- <a href="#building_wall_left">building_wall_left</a><a href="#dx"></a><a href="#dx"></a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.</td>
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_y"></a>building_length_y</span></td>
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
+
+
+
+
+
+
+      <td>Depth of a single building in m.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+Currently, <span style="font-weight: bold;">building_length_y</span> must be at least <span style="font-style: italic;">3 *&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#ny">ny</a><span style="font-style: italic;"> - 1 )&nbsp;</span><span style="font-style: italic;"> * <a href="#dy">dy</a></span><span style="font-style: italic;"> - <a href="#building_wall_south">building_wall_south</a><a href="#dy"></a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.</td>
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_left"></a>building_wall_left</span></td>
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">building centered in x-direction</span></td>
+
+
+
+
+
+
+      <td>x-coordinate of the left building wall (distance between the left building wall and the left border of the model domain) in m.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+Currently, <span style="font-weight: bold;">building_wall_left</span> must be at least <span style="font-style: italic;">1 *&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and less than <span style="font-style: italic;">( <a href="#nx">nx</a>&nbsp; - 1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+The default value&nbsp;<span style="font-weight: bold;">building_wall_left</span> = <span style="font-style: italic;">( ( <a href="#nx">nx</a>&nbsp;+ 1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a> ) / 2</span> centers the building in x-direction. </td>
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_south"></a>building_wall_south</span></td>
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;"></span><span style="font-style: italic;">building centered in y-direction</span></td>
+
+
+
+
+
+
+      <td>y-coordinate of the South building wall (distance between the
+South building wall and the South border of the model domain) in m.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+Currently, <span style="font-weight: bold;">building_wall_south</span> must be at least <span style="font-style: italic;">1 *&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and less than <span style="font-style: italic;">( <a href="#ny">ny</a>&nbsp; - 1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a></span>. This parameter requires the use of&nbsp;<a href="#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>.<br>
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+The default value&nbsp;<span style="font-weight: bold;">building_wall_south</span> = <span style="font-style: italic;">( ( <a href="#ny">ny</a>&nbsp;+ 1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a> ) / 2</span> centers the building in y-direction. </td>
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="cloud_droplets"></a>cloud_droplets</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Parameter to switch on usage of cloud droplets.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+Cloud droplets require to use the particle package (<span style="font-weight: bold;">mrun</span>-option <span style="font-family: monospace;">-p particles</span>),
+so in this case a particle corresponds to a droplet. The droplet
+features (number of droplets, initial radius, etc.) can be steered with
+the&nbsp; respective particle parameters (see e.g. <a href="#chapter_4.2.html#radius">radius</a>).
+The real number of initial droplets in a grid cell is equal to the
+initial number of droplets (defined by the particle source parameters <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
+      <span lang="en-GB"><font face="Thorndale, serif">and </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>) times the <a href="#initial_weighting_factor">initial_weighting_factor</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+In case of using cloud droplets, the default condensation scheme in PALM cannot be used, i.e. <a href="#cloud_physics">cloud_physics</a> must be set <span style="font-style: italic;">.F.</span>.<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="cloud_physics"></a><b>cloud_physics</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on the condensation scheme.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+For <b>cloud_physics =</b> <span style="font-style: italic;">.TRUE.</span>, equations for the
+liquid water&nbsp;
+content and the liquid water potential temperature are solved instead
+of those for specific humidity and potential temperature. Note
+that a grid volume is assumed to be either completely saturated or
+completely
+unsaturated (0%-or-100%-scheme). A simple precipitation scheme can
+additionally be switched on with parameter <a href="#precipitation">precipitation</a>.
+Also cloud-top cooling by longwave radiation can be utilized (see <a href="#radiation">radiation</a>)<br>
+
+
+
+
+
+
+
+
+
+
+      <b><br>
+
+
+
+
+
+
+
+
+
+
+cloud_physics =</b> <span style="font-style: italic;">.TRUE. </span>requires <a href="#moisture">moisture</a> =<span style="font-style: italic;"> .TRUE.</span> .<br>
+
+
+
+
+
+
+
+
+
+
+Detailed information about the condensation scheme is given in the
+description of the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM-1/Dokumentationen/Cloud_physics/wolken.pdf">cloud
+physics module</a> (pdf-file, only in German).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+This condensation scheme is not allowed if cloud droplets are simulated explicitly (see <a href="#cloud_droplets">cloud_droplets</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="conserve_volume_flow"></a>conserve_volume_flow</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
+
+
+
+
+
+
+
+      <td>Conservation of volume flow in x- and y-direction.<br>
+      <br>
+      <span style="font-weight: bold;">conserve_volume_flow</span> = <span style="font-style: italic;">.TRUE.</span>
+guarantees that the volume flow through the xz- or yz-cross-section of
+the total model domain remains constant (equal to the initial value at
+t=0) throughout the run.<br>
+</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="cut_spline_overshoot"></a><b>cut_spline_overshoot</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Cuts off of so-called overshoots, which can occur with the
+upstream-spline scheme.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><font color="#000000">The cubic splines tend to overshoot in
+case of discontinuous changes of variables between neighbouring grid
+points.</font><font color="#ff0000"> </font><font color="#000000">This
+may lead to errors in calculating the advection tendency.</font> Choice
+of <b>cut_spline_overshoot</b> = <i>.TRUE.</i> (switched on by
+default)
+allows variable values not to exceed an interval defined by the
+respective adjacent grid points. This interval can be adjusted
+seperately for every prognostic variable (see initialization parameters
+      <a href="#overshoot_limit_e">overshoot_limit_e</a>, <a href="#overshoot_limit_pt">overshoot_limit_pt</a>, <a href="#overshoot_limit_u">overshoot_limit_u</a>,
+etc.). This might be necessary in case that the
+default interval has a non-tolerable effect on the model
+results.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Overshoots may also be removed using the parameters <a href="#ups_limit_e">ups_limit_e</a>, <a href="#ups_limit_pt">ups_limit_pt</a>,
+etc. as well as by applying a long-filter (see <a href="#long_filter_factor">long_filter_factor</a>).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="damp_level_1d"></a><b>damp_level_1d</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz+1)</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Height where the damping layer begins in the 1d-model
+(in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This parameter is used to switch on a damping layer for the
+1d-model, which is generally needed for the damping of inertia
+oscillations. Damping is done by gradually increasing the value
+of the eddy diffusivities about 10% per vertical grid level
+(starting with the value at the height given by <b>damp_level_1d</b>,
+or possibly from the next grid pint above), i.e. K<sub>m</sub>(k+1) =
+1.1 * K<sub>m</sub>(k).
+The values of K<sub>m</sub> are limited to 10 m**2/s at maximum.&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+This parameter only comes into effect if the 1d-model is switched on
+for
+the initialization of the 3d-model using <a href="#initializing_actions">initializing_actions</a>
+= <span style="font-style: italic;">'set_1d-model_profiles'</span>. <br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+      <td style="vertical-align: top;"><a name="dissipation_1d"></a><span style="font-weight: bold;">dissipation_1d</span><br>
+      </td>
+      <td style="vertical-align: top;">C*20<br>
+      </td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;">
+      <span style="font-style: italic;">model'</span><br>
+      </td>
+      <td style="vertical-align: top;">Calculation method for the energy dissipation term in the TKE equation of the 1d-model.<br>
+      <br>
+By default the dissipation is calculated as in the 3d-model using diss = (0.19 + 0.74 * l / l_grid) * e**1.5 / l.<br>
+      <br>
+Setting <span style="font-weight: bold;">dissipation_1d</span> = <span style="font-style: italic;">'detering'</span> forces the dissipation to be calculated as diss = 0.064 * e**1.5 / l.<br>
+      </td>
+    </tr>
+<tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dt"></a><b>dt</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">variable</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Time step for the 3d-model (in s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By default, (i.e. if a Runge-Kutta scheme is used, see <a href="#timestep_scheme">timestep_scheme</a>)
+the value of the time step is calculating after each time step
+(following the time step criteria) and
+used for the next step.</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If the user assigns <b>dt</b> a value, then the time step is
+fixed to this value throughout the whole run (whether it fulfills the
+time step
+criteria or not). However, changes are allowed for restart runs,
+because <b>dt</b> can also be used as a <a href="chapter_4.2.html#dt_laufparameter">run
+parameter</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>In case that the calculated time step meets the condition<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p><b>dt</b> &lt; 0.00001 * dt_max (with dt_max = 20.0)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>the simulation will be aborted. Such situations usually arise
+in case of any numerical problem / instability which causes a
+non-realistic increase of the wind speed.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>A small time step due to a large mean horizontal windspeed
+speed may be enlarged by using a coordinate transformation (see <a href="#galilei_transformation">galilei_transformation</a>),
+in order to spare CPU time.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If the leapfrog timestep scheme is used (see <a href="#timestep_scheme">timestep_scheme</a>)
+a temporary time step value dt_new is calculated first, with dt_new = <a href="chapter_4.2.html#fcl_factor">cfl_factor</a>
+* dt_crit where dt_crit is the maximum timestep allowed by the CFL and
+diffusion condition. Next it is examined whether dt_new exceeds or
+falls below the
+value of the previous timestep by at
+least +5 % / -2%. If it is smaller, <span style="font-weight: bold;">dt</span>
+= dt_new is immediately used for the next timestep. If it is larger,
+then <span style="font-weight: bold;">dt </span>= 1.02 * dt_prev
+(previous timestep) is used as the new timestep, however the time
+step is only increased if the last change of the time step is dated
+back at
+least 30 iterations. If dt_new is located in the interval mentioned
+above, then dt
+does not change at all. By doing so, permanent time step changes as
+well as large
+sudden changes (increases) in the time step are avoided.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dt_pr_1d"></a><b>dt_pr_1d</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Temporal interval of vertical profile output of the 1D-model
+(in s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Data are written in ASCII format to file <a href="chapter_3.4.html#LIST_PROFIL_1D">LIST_PROFIL_1D</a>.
+This parameter is only in effect if the 1d-model has been switched on
+for the
+initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
+= <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dt_run_control_1d"></a><b>dt_run_control_1d</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">60.0</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Temporal interval of runtime control output of the 1d-model
+(in s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Data are written in ASCII format to file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
+This parameter is only in effect if the 1d-model is switched on for the
+initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
+= <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dx"></a><b>dx</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Horizontal grid spacing along the x-direction (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Along x-direction only a constant grid spacing is allowed.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dy"></a><b>dy</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Horizontal grid spacing along the x-direction (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Along x-direction only a constant grid spacing is allowed.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dz"></a><b>dz</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Vertical grid spacing (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This parameter must be assigned by the user, because no
+default value is given.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By default, the
+model uses constant grid spacing along z-direction, but it can be
+stretched using the parameters <a href="#dz_stretch_level">dz_stretch_level</a>
+and <a href="#dz_stretch_factor">dz_stretch_factor</a>. In case of stretching, a maximum allowed grid spacing can be given by <a href="#dz_max">dz_max</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Assuming a constant <span style="font-weight: bold;">dz</span>,
+the scalar levels (zu) are calculated directly by:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>zu(0) = - dz * 0.5&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+zu(1) = dz * 0.5</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The w-levels lie
+half between them:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>zw(k) = ( zu(k) + zu(k+1) ) * 0.5</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr><td style="vertical-align: top;"><a name="dz_max"></a><span style="font-weight: bold;">dz_max</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td><td style="vertical-align: top;">Allowed maximum vertical grid spacing (in m).<br><br>If the vertical grid is stretched (see <a href="#dz_stretch_factor">dz_stretch_factor</a> and <a href="#dz_stretch_level">dz_stretch_level</a>), <span style="font-weight: bold;">dz_max</span> can be used to limit the vertical grid spacing.</td></tr><tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dz_stretch_factor"></a><b>dz_stretch_factor</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">1.08</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Stretch factor for a vertically stretched grid (see <a href="#dz_stretch_level">dz_stretch_level</a>).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The stretch factor should not exceed a value of approx. 1.10 -
+1.12, otherwise the discretization errors due to the stretched grid not
+negligible any more. (refer Kalnay de Rivas)</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="dz_stretch_level"></a><b>dz_stretch_level</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">100000.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Height level above which the grid is to be stretched
+vertically (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The vertical grid spacings <a href="#dz">dz</a>
+above this level are calculated as&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p><b>dz</b>(k+1) = <b>dz</b>(k) * <a href="#dz_stretch_factor">dz_stretch_factor</a></p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>and used as spacings for the scalar levels (zu). The
+w-levels are then defined as:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>zw(k) = ( zu(k) + zu(k+1) ) * 0.5</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="e_min"></a>e_min</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
+
+
+
+
+
+
+
+      <td>Minimum subgrid-scale TKE in m<sup>2</sup>s<sup>-2</sup>.<br>
+
+
+
+
+
+
+
+      <br>This
+option&nbsp;adds artificial viscosity to the flow by ensuring that the
+subgrid-scale TKE does not fall below the minimum threshold <span style="font-weight: bold;">e_min</span>.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="end_time_1d"></a><b>end_time_1d</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">864000.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Time to be simulated for the 1d-model (in s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The default value corresponds to a simulated time of 10 days.
+Usually, after such a period the inertia oscillations have completely
+decayed and the solution of the 1d-model can be regarded as stationary
+(see <a href="#damp_level_1d">damp_level_1d</a>).
+This parameter is only in effect if the 1d-model is switched on for the
+initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
+= <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="fft_method"></a><b>fft_method</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'system-</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">specific'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>FFT-method to be used.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><br>
+
+
+
+
+
+
+
+
+
+
+The fast fourier transformation (FFT) is used for solving the
+perturbation pressure equation with a direct method (see <a href="chapter_4.2.html#psolver">psolver</a>)
+and for calculating power spectra (see optional software packages,
+section <a href="chapter_4.2.html#spectra_package">4.2</a>).</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><br>
+
+
+
+
+
+
+
+
+
+
+By default, system-specific, optimized routines from external
+vendor libraries are used. However, these are available only on certain
+computers and there are more or less severe restrictions concerning the
+number of gridpoints to be used with them.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>There are two other PALM internal methods available on every
+machine (their respective source code is part of the PALM source code):</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>1.: The <span style="font-weight: bold;">Temperton</span>-method
+from Clive Temperton (ECWMF) which is computationally very fast and
+switched on with <b>fft_method</b> = <span style="font-style: italic;">'temperton-algorithm'</span>.
+The number of horizontal gridpoints (nx+1, ny+1) to be used with this
+method must be composed of prime factors 2, 3 and 5.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+2.: The <span style="font-weight: bold;">Singleton</span>-method
+which is very slow but has no restrictions concerning the number of
+gridpoints to be used with, switched on with <b>fft_method</b> = <span style="font-style: italic;">'singleton-algorithm'</span>. </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="galilei_transformation"></a><b>galilei_transformation</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.F.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Application of a Galilei-transformation to the
+coordinate
+system of the model.<br><p>With <b>galilei_transformation</b> = <i>.T.,</i> a so-called
+Galilei-transformation is switched on which ensures that the coordinate
+system of the model is moved along with the geostrophical wind.
+Alternatively, the model domain can be moved along with the averaged
+horizontal wind (see <a href="#use_ug_for_galilei_tr">use_ug_for_galilei_tr</a>,
+this can and will naturally change in time). With this method,
+numerical inaccuracies of the Piascek - Williams - scheme (concerns in
+particular the momentum advection) are minimized. Beyond that, in the
+majority of cases the lower relative velocities in the moved system
+permit a larger time step (<a href="#dt">dt</a>).
+Switching the transformation on is only worthwhile if the geostrophical
+wind (ug, vg)
+and the averaged horizontal wind clearly deviate from the value 0. In
+each case, the distance the coordinate system has been moved is written
+to the file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
+and <a href="#bc_ns">bc_ns</a>), the specification of a gestrophic
+wind that is not constant with height
+as well as e.g. stationary inhomogeneities at the bottom boundary do
+not allow the use of this transformation.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="grid_matching"></a><b>grid_matching</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 6</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'match'</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Variable to adjust the subdomain
+sizes in parallel runs.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+For <b>grid_matching</b> = <span style="font-style: italic;">'strict'</span>,
+the subdomains are forced to have an identical
+size on all processors. In this case the processor numbers in the
+respective directions of the virtual processor net must fulfill certain
+divisor conditions concerning the grid point numbers in the three
+directions (see <a href="#nx">nx</a>,
+      <a href="#ny">ny</a>
+and <a href="#nz">nz</a>).
+Advantage of this method is that all PEs bear the same computational
+load.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+There is no such restriction by default, because then smaller
+subdomains are allowed on those processors which
+form the right and/or north boundary of the virtual processor grid. On
+all other processors the subdomains are of same size. Whether smaller
+subdomains are actually used, depends on the number of processors and
+the grid point numbers used. Information about the respective settings
+are given in file <a href="file:///home/raasch/public_html/PALM_group/home/raasch/public_html/PALM_group/doc/app/chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+When using a multi-grid method for solving the Poisson equation (see <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</a>)
+only <b>grid_matching</b> = <span style="font-style: italic;">'strict'</span>
+is allowed.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>Note:</b><br>
+
+
+
+
+
+
+
+
+
+
+In some cases for small processor numbers there may be a very bad load
+balancing among the
+processors which may reduce the performance of the code.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="inflow_disturbance_begin"></a><b>inflow_disturbance_<br>
+
+
+
+
+
+
+
+
+
+
+begin</b></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(10,</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">nx/2 or ny/2)</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Lower
+limit of the horizontal range for which random perturbations are to be
+imposed on the horizontal velocity field (gridpoints).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+If non-cyclic lateral boundary conditions are used (see <a href="#bc_lr">bc_lr</a>
+or <a href="#bc_ns">bc_ns</a>),
+this parameter gives the gridpoint number (counted horizontally from
+the inflow)&nbsp; from which on perturbations are imposed on the
+horizontal velocity field. Perturbations must be switched on with
+parameter <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><a name="inflow_disturbance_end"></a><b>inflow_disturbance_<br>
+
+
+
+
+
+
+
+
+
+
+end</b></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(100,</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">3/4*nx or</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">3/4*ny)</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Upper
+limit of the horizontal range for which random perturbations are
+to be imposed on the horizontal velocity field (gridpoints).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+If non-cyclic lateral boundary conditions are used (see <a href="#bc_lr">bc_lr</a>
+or <a href="#bc_ns">bc_ns</a>),
+this parameter gives the gridpoint number (counted horizontally from
+the inflow)&nbsp; unto which perturbations are imposed on the
+horizontal
+velocity field. Perturbations must be switched on with parameter <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="initializing_actions"></a><b>initializing_actions</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 100</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Initialization actions
+to be carried out.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">This parameter does not have a
+default value and therefore must be assigned with each model run. For
+restart runs <b>initializing_actions</b> = <span style="font-style: italic;">'read_restart_data'</span>
+must be set. For the initial run of a job chain the following values
+are allowed:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;"><span style="font-style: italic;">'set_constant_profiles'</span>
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>A horizontal wind profile consisting of linear sections (see
+        <a href="#ug_surface">ug_surface</a>, <a href="#ug_vertical_gradient">ug_vertical_gradient</a>, <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a> and <a href="#vg_surface">vg_surface</a>, <a href="#vg_vertical_gradient">vg_vertical_gradient</a>,
+        <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
+respectively) as well as a vertical temperature (humidity) profile
+consisting of
+linear sections (see <a href="#pt_surface">pt_surface</a>, <a href="#pt_vertical_gradient">pt_vertical_gradient</a>, <a href="#q_surface">q_surface</a>
+and <a href="#q_vertical_gradient">q_vertical_gradient</a>)
+are assumed as initial profiles. The subgrid-scale TKE is set to 0 but K<sub>m</sub>
+and K<sub>h</sub> are set to very small values because otherwise no TKE
+would be generated.</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: italic;">'set_1d-model_profiles' </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>The arrays of the 3d-model are initialized with the
+(stationary) solution of the 1d-model. These are the variables e, kh,
+km, u, v and with Prandtl layer switched on rif, us, usws, vsws. The
+temperature (humidity) profile consisting of linear sections is set as
+for 'set_constant_profiles' and assumed as constant in time within the
+1d-model. For steering of the 1d-model a set of parameters with suffix
+"_1d" (e.g. <a href="#end_time_1d">end_time_1d</a>, <a href="#damp_level_1d">damp_level_1d</a>)
+is available.</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'initialize_vortex'</span> </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">The initial velocity field of the
+3d-model corresponds to a
+Rankine-vortex with vertical axis. This setting may be used to test
+advection schemes. Free-slip boundary conditions for u and v (see <a href="#bc_uv_b">bc_uv_b</a>, <a href="#bc_uv_t">bc_uv_t</a>)
+are necessary. In order not to distort the vortex, an initial
+horizontal wind profile constant
+with height is necessary (to be set by <b>initializing_actions</b>
+= <span style="font-style: italic;">'set_constant_profiles'</span>)
+and some other conditions have to be met (neutral stratification,
+diffusion must be
+switched off, see <a href="#km_constant">km_constant</a>).
+The center of the vortex is located at jc = (nx+1)/2. It
+extends from k = 0 to k = nz+1. Its radius is 8 * <a href="#dx">dx</a>
+and the exponentially decaying part ranges to 32 * <a href="#dx">dx</a>
+(see init_rankine.f90). </div>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'initialize_ptanom'</span> </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>A 2d-Gauss-like shape disturbance (x,y) is added to the
+initial temperature field with radius 10.0 * <a href="#dx">dx</a>
+and center at jc = (nx+1)/2. This may be used for tests of scalar
+advection schemes
+(see <a href="#scalar_advec">scalar_advec</a>).
+Such tests require a horizontal wind profile constant with hight and
+diffusion
+switched off (see <span style="font-style: italic;">'initialize_vortex'</span>).
+Additionally, the buoyancy term
+must be switched of in the equation of motion&nbsp; for w (this
+requires the user to comment out the call of <span style="font-family: monospace;">buoyancy</span> in the source code of <span style="font-family: monospace;">prognostic_equations.f90</span>).</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Values may be
+combined, e.g. <b>initializing_actions</b> = <span style="font-style: italic;">'set_constant_profiles
+initialize_vortex'</span>, but the values of <span style="font-style: italic;">'set_constant_profiles'</span>
+and <span style="font-style: italic;">'set_1d-model_profiles'</span>
+must not be given at the same time.</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="font-style: italic;"> </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="km_constant"></a><b>km_constant</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>variable<br>
+
+
+
+
+
+
+
+
+
+
+(computed from TKE)</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Constant eddy diffusivities are used (laminar
+simulations).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If this parameter is specified, both in the 1d and in the
+3d-model constant values for the eddy diffusivities are used in
+space and time with K<sub>m</sub> = <b>km_constant</b>
+and K<sub>h</sub> = K<sub>m</sub> / <a href="chapter_4.2.html#prandtl_number">prandtl_number</a>.
+The prognostic equation for the subgrid-scale TKE is switched off.
+Constant eddy diffusivities are only allowed with the Prandtl layer (<a href="#prandtl_layer">prandtl_layer</a>)
+switched off.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="km_damp_max"></a><b>km_damp_max</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.5*(dx
+or dy)</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Maximum
+diffusivity used for filtering the velocity field in the vicinity of
+the outflow (in m<sup>2</sup>/s).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+When using non-cyclic lateral boundaries (see <a href="#bc_lr">bc_lr</a>
+or <a href="#bc_ns">bc_ns</a>),
+a smoothing has to be applied to the
+velocity field in the vicinity of the outflow in order to suppress any
+reflections of outgoing disturbances. Smoothing is done by increasing
+the eddy diffusivity along the horizontal direction which is
+perpendicular to the outflow boundary. Only velocity components
+parallel to the outflow boundary are filtered (e.g. v and w, if the
+outflow is along x). Damping is applied from the bottom to the top of
+the domain.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The horizontal range of the smoothing is controlled by <a href="#outflow_damping_width">outflow_damping_width</a>
+which defines the number of gridpoints (counted from the outflow
+boundary) from where on the smoothing is applied. Starting from that
+point, the eddy diffusivity is linearly increased (from zero to its
+maximum value given by <span style="font-weight: bold;">km_damp_max</span>)
+until half of the damping range width, from where it remains constant
+up to the outflow boundary. If at a certain grid point the eddy
+diffusivity calculated from the flow field is larger than as described
+above, it is used instead.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The default value of <span style="font-weight: bold;">km_damp_max</span>
+has been empirically proven to be sufficient.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="long_filter_factor"></a><b>long_filter_factor</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Filter factor for the so-called Long-filter.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><br>
+
+
+
+
+
+
+
+
+
+
+This filter very efficiently
+eliminates 2-delta-waves sometimes cauesed by the upstream-spline
+scheme (see Mahrer and
+Pielke, 1978: Mon. Wea. Rev., 106, 818-830). It works in all three
+directions in space. A value of <b>long_filter_factor</b> = <i>0.01</i>
+sufficiently removes the small-scale waves without affecting the
+longer waves.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By default, the filter is switched off (= <i>0.0</i>).
+It is exclusively applied to the tendencies calculated by the
+upstream-spline scheme (see <a href="#momentum_advec">momentum_advec</a>
+and <a href="#scalar_advec">scalar_advec</a>),
+not to the prognostic variables themselves. At the bottom and top
+boundary of the model domain the filter effect for vertical
+2-delta-waves is reduced. There, the amplitude of these waves is only
+reduced by approx. 50%, otherwise by nearly 100%.&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+Filter factors with values &gt; <i>0.01</i> also reduce the amplitudes
+of waves with wavelengths longer than 2-delta (see the paper by Mahrer
+and
+Pielke, quoted above). </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+      <td style="vertical-align: top;"><a name="mixing_length_1d"></a><span style="font-weight: bold;">mixing_length_1d</span><br>
+      </td>
+      <td style="vertical-align: top;">C*20<br>
+      </td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;">
+      <span style="font-style: italic;">model'</span><br>
+      </td>
+      <td style="vertical-align: top;">Mixing length used in the 1d-model.<br>
+      <br>
+By default the mixing length is calculated as in the 3d-model (i.e. it depends on the grid spacing).<br>
+      <br>
+By setting <span style="font-weight: bold;">mixing_length_1d</span> = <span style="font-style: italic;">'blackadar'</span>,
+the so-called Blackadar mixing length is used (l = kappa * z / ( 1 +
+kappa * z / lambda ) with the limiting value lambda = 2.7E-4 * u_g / f).<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="moisture"></a><b>moisture</b></p>
+      </td>
+      <td style="vertical-align: top;">L</td>
+      <td style="vertical-align: top;"><i>.F.</i></td>
+      <td style="vertical-align: top;">
+      <p>Parameter to switch on the prognostic equation for specific
+humidity q.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The initial vertical profile of q can be set via parameters <a href="chapter_4.1.html#q_surface">q_surface</a>, <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
+and <a href="chapter_4.1.html#q_vertical_gradient_level">q_vertical_gradient_level</a>.&nbsp;
+Boundary conditions can be set via <a href="chapter_4.1.html#q_surface_initial_change">q_surface_initial_change</a>
+and <a href="chapter_4.1.html#surface_waterflux">surface_waterflux</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+
+If the condensation scheme is switched on (<a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
+= .TRUE.), q becomes the total liquid water content (sum of specific
+humidity and liquid water content).</td>
+    </tr>
+<tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="momentum_advec"></a><b>momentum_advec</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 10</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>'pw-scheme'</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Advection scheme to be used for the momentum equations.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The user can choose between the following schemes:<br>
+
+
+
+
+
+
+
+
+
+
+&nbsp;<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">'pw-scheme'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">The scheme of Piascek and
+Williams (1970, J. Comp. Phys., 6,
+392-405) with central differences in the form C3 is used.<br>
+
+
+
+
+
+
+
+
+
+
+If intermediate Euler-timesteps are carried out in case of <a href="#timestep_scheme">timestep_scheme</a>
+= <span style="font-style: italic;">'leapfrog+euler'</span> the
+advection scheme is - for the Euler-timestep - automatically switched
+to an upstream-scheme.<br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p> </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'ups-scheme'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">The upstream-spline scheme is
+used
+(see Mahrer and Pielke,
+1978: Mon. Wea. Rev., 106, 818-830). In opposite to the
+Piascek-Williams scheme, this is characterized by much better numerical
+features (less numerical diffusion, better preservation of flow
+structures, e.g. vortices), but computationally it is much more
+expensive. In
+addition, the use of the Euler-timestep scheme is mandatory (<a href="#timestep_scheme">timestep_scheme</a>
+= <span style="font-style: italic;">'</span><i>euler'</i>), i.e. the
+timestep accuracy is only of first order.
+For this reason the advection of scalar variables (see <a href="#scalar_advec">scalar_advec</a>)
+should then also be carried out with the upstream-spline scheme,
+because otherwise the scalar variables would
+be subject to large numerical diffusion due to the upstream
+scheme.&nbsp; </div>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="margin-left: 40px;">Since the cubic splines used tend
+to overshoot under
+certain circumstances, this effect must be adjusted by suitable
+filtering and smoothing (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>,
+      <a href="#long_filter_factor">long_filter_factor</a>, <a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>,
+      <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
+This is always neccessary for runs with stable stratification,
+even if this stratification appears only in parts of the model domain.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">With stable stratification the
+upstream-spline scheme also
+produces gravity waves with large amplitude, which must be
+suitably damped (see <a href="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-weight: bold;">Important: </span>The&nbsp;
+upstream-spline scheme is not implemented for humidity and passive
+scalars (see <a href="#moisture">moisture</a>
+and <a href="#passive_scalar">passive_scalar</a>)
+and requires the use of a 2d-domain-decomposition. The last conditions
+severely restricts code optimization on several machines leading to
+very long execution times! The scheme is also not allowed for
+non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
+and <a href="#bc_ns">bc_ns</a>).</div>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+
+
+
+
+    <tr>
+      <td style="vertical-align: top;"><a name="netcdf_precision"></a><span style="font-weight: bold;">netcdf_precision</span><br>
+      </td>
+      <td style="vertical-align: top;">C*20<br>
+(10)<br>
+      </td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">single preci-</span><br style="font-style: italic;">
+      <span style="font-style: italic;">sion for all</span><br style="font-style: italic;">
+      <span style="font-style: italic;">output quan-</span><br style="font-style: italic;">
+      <span style="font-style: italic;">tities</span><br>
+      </td>
+      <td style="vertical-align: top;">Defines the accuracy of the NetCDF output.<br>
+      <br>
+By default, all NetCDF output data (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>) have single precision&nbsp; (4 byte) accuracy. Double precision (8 byte) can be choosen alternatively.<br>
+Accuracy for the different output data (cross sections, 3d-volume data, spectra, etc.) can be set independently.<br>
+      <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL4'</span> (single precision) or <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL8'</span> (double precision) are the two principally allowed values for <span style="font-weight: bold;">netcdf_precision</span>, where the string <span style="font-style: italic;">'&lt;out&gt;' </span>can be chosen out of the following list:<br>
+      <br>
+      <table style="text-align: left; width: 284px; height: 234px;" border="1" cellpadding="2" cellspacing="2">
+        <tbody>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'xy'</span><br>
+            </td>
+            <td style="vertical-align: top;">horizontal cross section<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'xz'</span><br>
+            </td>
+            <td style="vertical-align: top;">vertical (xz) cross section<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'yz'</span><br>
+            </td>
+            <td style="vertical-align: top;">vertical (yz) cross section<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'2d'</span><br>
+            </td>
+            <td style="vertical-align: top;">all cross sections<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'3d'</span><br>
+            </td>
+            <td style="vertical-align: top;">volume data<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'pr'</span><br>
+            </td>
+            <td style="vertical-align: top;">vertical profiles<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'ts'</span><br>
+            </td>
+            <td style="vertical-align: top;">time series, particle time series<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'sp'</span><br>
+            </td>
+            <td style="vertical-align: top;">spectra<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'prt'</span><br>
+            </td>
+            <td style="vertical-align: top;">particles<br>
+            </td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><span style="font-style: italic;">'all'</span><br>
+            </td>
+            <td style="vertical-align: top;">all output quantities<br>
+            </td>
+          </tr>
+        </tbody>
+      </table>
+      <br>
+      <span style="font-weight: bold;">Example:</span><br>
+If all cross section data and the particle data shall be output in
+double precision and all other quantities in single precision, then <span style="font-weight: bold;">netcdf_precision</span> = <span style="font-style: italic;">'2d_NF90_REAL8'</span>, <span style="font-style: italic;">'prt_NF90_REAL8'</span> has to be assigned.<br>
+      </td>
+    </tr>
+<tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="npex"></a><b>npex</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Number of processors along x-direction of the virtual
+processor
+net.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For parallel runs, the total number of processors to be used
+is given by
+the <span style="font-weight: bold;">mrun</span> option <a href="http://www.muk.uni-hannover.de/software/mrun_beschreibung.html#Opt-X">-X</a>.
+By default, depending on the type of the parallel computer, PALM
+generates a 1d processor
+net (domain decomposition along x, <span style="font-weight: bold;">npey</span>
+= <span style="font-style: italic;">1</span>) or a 2d-net (this is
+favored on machines with fast communication network). In case of a
+2d-net, it is tried to make it more or less square-shaped. If, for
+example, 16 processors are assigned (-X 16), a 4 * 4 processor net is
+generated (<span style="font-weight: bold;">npex</span> = <span style="font-style: italic;">4</span>, <span style="font-weight: bold;">npey</span>
+= <span style="font-style: italic;">4</span>).
+This choice is optimal for square total domains (<a href="#nx">nx</a>
+= <a href="#ny">ny</a>),
+since then the number of ghost points at the lateral boundarys of
+the subdomains is minimal. If <span style="font-weight: bold;">nx</span>
+nd <span style="font-weight: bold;">ny</span> differ extremely, the
+processor net should be manually adjusted using adequate values for <span style="font-weight: bold;">npex</span> and <span style="font-weight: bold;">npey</span>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><b>Important:</b> The value of <span style="font-weight: bold;">npex</span> * <span style="font-weight: bold;">npey</span> must exactly correspond to the
+value assigned by the <span style="font-weight: bold;">mrun</span>-option
+      <tt>-X</tt>.
+Otherwise the model run will abort with a corresponding error
+message.&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+Additionally, the specification of <span style="font-weight: bold;">npex</span>
+and <span style="font-weight: bold;">npey</span> may of course
+override the default setting for the domain decomposition (1d or 2d)
+which may have a significant (negative) effect on the code performance.
+      </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="npey"></a><b>npey</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Number of processors along y-direction of the virtual
+processor
+net.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For further information see <a href="#npex">npex</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="nsor_ini"></a><b>nsor_ini</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>100</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Initial number of iterations with the SOR algorithm.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This parameter is only effective if the SOR algorithm was
+selected as the pressure solver scheme (<a href="chapter_4.2.html#psolver">psolver</a>
+= <span style="font-style: italic;">'sor'</span>) and specifies the
+number of initial iterations of the SOR
+scheme (at t = 0). The number of subsequent iterations at the following
+timesteps is determined
+with the parameter <a href="#nsor">nsor</a>.
+Usually <b>nsor</b> &lt; <b>nsor_ini</b>, since in each case
+subsequent calls to <a href="chapter_4.2.html#psolver">psolver</a>
+use the solution of the previous call as initial value. Suitable
+test runs should determine whether sufficient convergence of the
+solution is obtained with the default value and if necessary the value
+of <b>nsor_ini</b> should be changed.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="nx"></a><b>nx</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Number of grid points in x-direction.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>A value for this parameter must be assigned. Since the lower
+array bound in PALM
+starts with i = 0, the actual number of grid points is equal to <b>nx+1</b>.
+In case of cyclic boundary conditions along x, the domain size is (<b>nx+1</b>)*
+      <a href="#dx">dx</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For parallel runs, in case of <a href="#grid_matching">grid_matching</a>
+= <span style="font-style: italic;">'strict'</span>, <b>nx+1</b> must
+be an integral multiple
+of the processor numbers (see <a href="#npex">npex</a>
+and <a href="#npey">npey</a>)
+along x- as well as along y-direction (due to data
+transposition restrictions).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ny"></a><b>ny</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Number of grid points in y-direction.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>A value for this parameter must be assigned. Since the lower
+array bound in PALM starts with i = 0, the actual number of grid points
+is equal to <b>ny+1</b>. In case of cyclic boundary conditions along
+y, the domain size is (<b>ny+1</b>) * <a href="#dy">dy</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For parallel runs, in case of <a href="#grid_matching">grid_matching</a>
+= <span style="font-style: italic;">'strict'</span>, <b>ny+1</b> must
+be an integral multiple
+of the processor numbers (see <a href="#npex">npex</a>
+and <a href="#npey">npey</a>)&nbsp;
+along y- as well as along x-direction (due to data
+transposition restrictions).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="nz"></a><b>nz</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Number of grid points in z-direction.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>A value for this parameter must be assigned. Since the lower
+array bound in PALM
+starts with k = 0 and since one additional grid point is added at the
+top boundary (k = <b>nz+1</b>), the actual number of grid points is <b>nz+2</b>.
+However, the prognostic equations are only solved up to <b>nz</b> (u,
+v)
+or up to <b>nz-1</b> (w, scalar quantities). The top boundary for u
+and v is at k = <b>nz+1</b> (u, v) while at k = <b>nz</b> for all
+other quantities.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For parallel runs,&nbsp; in case of <a href="#grid_matching">grid_matching</a>
+= <span style="font-style: italic;">'strict'</span>, <b>nz</b> must
+be an integral multiple of
+the number of processors in x-direction (due to data transposition
+restrictions).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="omega"></a><b>omega</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>7.29212E-5</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Angular velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The angular velocity of the earth is set by default. The
+values
+of the Coriolis parameters are calculated as:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p>f = 2.0 * <b>omega</b> * sin(<a href="#phi">phi</a>)&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+f* = 2.0 * <b>omega</b> * cos(<a href="#phi">phi</a>)</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="outflow_damping_width"></a><b>outflow_damping_width</b></p>
+      </td>
+      <td style="vertical-align: top;">I</td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(20,
+nx/2</span> or <span style="font-style: italic;">ny/2)</span></td>
+      <td style="vertical-align: top;">Width of
+the damping range in the vicinity of the outflow (gridpoints).<br>
+
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+
+When using non-cyclic lateral boundaries (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
+or <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
+a smoothing has to be applied to the
+velocity field in the vicinity of the outflow in order to suppress any
+reflections of outgoing disturbances. This parameter controlls the
+horizontal range to which the smoothing is applied. The range is given
+in gridpoints counted from the respective outflow boundary. For further
+details about the smoothing see parameter <a href="chapter_4.1.html#km_damp_max">km_damp_max</a>,
+which defines the magnitude of the damping.</td>
+    </tr>
+<tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="overshoot_limit_e"></a><b>overshoot_limit_e</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of subgrid-scale TKE in
+case that the upstream-spline scheme is switched on (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By deafult, if cut-off of overshoots is switched on for the
+upstream-spline scheme (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>),
+no overshoots are permitted at all. If <b>overshoot_limit_e</b>
+is given a non-zero value, overshoots with the respective
+amplitude (both upward and downward) are allowed.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are allowed for <b>overshoot_limit_e</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="overshoot_limit_pt"></a><b>overshoot_limit_pt</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of potential temperature in
+case that the upstream-spline scheme is switched on (in K).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are allowed for <b>overshoot_limit_pt</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="overshoot_limit_u"></a><b>overshoot_limit_u</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Allowed limit for the
+overshooting of
+the u-component of velocity in case that the upstream-spline scheme is
+switched on (in m/s).
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are allowed for <b>overshoot_limit_u</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="overshoot_limit_v"></a><b>overshoot_limit_v</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of the v-component of
+velocity in case that the upstream-spline scheme is switched on
+(in m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are allowed for <b>overshoot_limit_v</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="overshoot_limit_w"></a><b>overshoot_limit_w</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of the w-component of
+velocity in case that the upstream-spline scheme is switched on
+(in m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are permitted for <b>overshoot_limit_w</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="passive_scalar"></a><b>passive_scalar</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.F.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on the prognostic equation for a passive
+scalar. <br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The initial vertical profile of s can be set via parameters <a href="#s_surface">s_surface</a>, <a href="#s_vertical_gradient">s_vertical_gradient</a>
+and&nbsp; <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.
+Boundary conditions can be set via <a href="#s_surface_initial_change">s_surface_initial_change</a>
+and <a href="#surface_scalarflux">surface_scalarflux</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><b>Note:</b> <br>
+
+
+
+
+
+
+
+
+
+
+With <span style="font-weight: bold;">passive_scalar</span> switched
+on, the simultaneous use of humidity (see <a href="#moisture">moisture</a>)
+is impossible.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="phi"></a><b>phi</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>55.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Geographical latitude (in degrees).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The value of this parameter determines the value of the
+Coriolis parameters f and f*, provided that the angular velocity (see <a href="#omega">omega</a>)
+is non-zero.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="prandtl_layer"></a><b>prandtl_layer</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.T.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on a Prandtl layer.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By default, a Prandtl layer is switched on at the bottom
+boundary between z = 0 and z = 0.5 * <a href="#dz">dz</a>
+(the first computational grid point above ground for u, v and the
+scalar quantities).
+In this case, at the bottom boundary, free-slip conditions for u and v
+(see <a href="#bc_uv_b">bc_uv_b</a>)
+are not allowed. Likewise, laminar
+simulations with constant eddy diffusivities (<a href="#km_constant">km_constant</a>)
+are forbidden.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>With Prandtl-layer switched off, the TKE boundary condition <a href="#bc_e_b">bc_e_b</a>
+= '<i>(u*)**2+neumann'</i> must not be used and is automatically
+changed to <i>'neumann'</i> if necessary.&nbsp; Also, the pressure
+boundary condition <a href="#bc_p_b">bc_p_b</a>
+= <i>'neumann+inhomo'</i>&nbsp; is not allowed. </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The roughness length is declared via the parameter <a href="#roughness_length">roughness_length</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="precipitation"></a><b>precipitation</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on the precipitation scheme.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For precipitation processes PALM uses a simplified Kessler
+scheme. This scheme only considers the
+so-called autoconversion, that means the generation of rain water by
+coagulation of cloud drops among themselves. Precipitation begins and
+is immediately removed from the flow as soon as the liquid water
+content exceeds the critical value of 0.5 g/kg.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="pt_surface"></a><b>pt_surface</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>300.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Surface potential temperature (in K).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This parameter assigns the value of the potential temperature
+pt at the surface (k=0)<b>.</b> Starting from this value, the
+initial vertical temperature profile is constructed with <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
+and <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level </a>.
+This profile is also used for the 1d-model as a stationary profile.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="pt_surface_initial_change"></a><b>pt_surface_initial</b>
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>_change</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Change in surface temperature to be made at the beginning of
+the 3d run
+(in K).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If <b>pt_surface_initial_change</b> is set to a non-zero
+value, the near surface sensible heat flux is not allowed to be given
+simultaneously (see <a href="#surface_heatflux">surface_heatflux</a>).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="pt_vertical_gradient"></a><b>pt_vertical_gradient</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R (10)</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>10 * 0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Temperature gradient(s) of the initial temperature profile (in
+K
+/ 100 m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This temperature gradient holds starting from the height&nbsp;
+level defined by <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>
+(precisely: for all uv levels k where zu(k) &gt;
+pt_vertical_gradient_level,
+pt_init(k) is set: pt_init(k) = pt_init(k-1) + dzu(k) * <b>pt_vertical_gradient</b>)
+up to the top boundary or up to the next height level defined
+by <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>.
+A total of 10 different gradients for 11 height intervals (10 intervals
+if <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>(1)
+= <i>0.0</i>) can be assigned. The surface temperature is assigned via
+      <a href="#pt_surface">pt_surface</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Example:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p><b>pt_vertical_gradient</b> = <i>1.0</i>, <i>0.5</i>,&nbsp;
+        <br>
+
+
+
+
+
+
+
+
+
+
+        <b>pt_vertical_gradient_level</b> = <i>500.0</i>, <i>1000.0</i>,</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>That defines the temperature profile to be neutrally
+stratified
+up to z = 500.0 m with a temperature given by <a href="#pt_surface">pt_surface</a>.
+For 500.0 m &lt; z &lt;= 1000.0 m the temperature gradient is 1.0 K /
+100 m and for z &gt; 1000.0 m up to the top boundary it is
+0.5 K / 100 m (it is assumed that the assigned height levels correspond
+with uv levels). </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="pt_vertical_gradient_level"></a><b>pt_vertical_gradient</b>
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>_level</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R (10)</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><i>10 *</i>&nbsp; <span style="font-style: italic;">0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Height level from which on the temperature gradient defined by
+      <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
+is effective (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The height levels are to be assigned in ascending order. The
+default values result in a neutral stratification regardless of the
+values of <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
+(unless the top boundary of the model is higher than 100000.0 m).
+For the piecewise construction of temperature profiles see <a href="#pt_vertical_gradient">pt_vertical_gradient</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="q_surface"></a><b>q_surface</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Surface specific humidity / total water content (kg/kg).&nbsp;
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This parameter assigns the value of the specific humidity q at
+the surface (k=0).&nbsp; Starting from this value, the initial humidity
+profile is constructed with&nbsp; <a href="#q_vertical_gradient">q_vertical_gradient</a>
+and <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>.
+This profile is also used for the 1d-model as a stationary profile.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="q_surface_initial_change"></a><b>q_surface_initial</b>
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>_change</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Change in surface specific humidity / total water content to
+be made at the beginning
+of the 3d run (kg/kg).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If <b>q_surface_initial_change</b><i> </i>is set to a
+non-zero value the
+near surface latent heat flux (water flux) is not allowed to be given
+simultaneously (see <a href="#surface_waterflux">surface_waterflux</a>).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="q_vertical_gradient"></a><b>q_vertical_gradient</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R (10)</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>10 * 0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Humidity gradient(s) of the initial humidity profile
+(in 1/100 m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This humidity gradient holds starting from the height
+level&nbsp; defined by <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>
+(precisely: for all uv levels k, where zu(k) &gt;
+q_vertical_gradient_level,
+q_init(k) is set: q_init(k) = q_init(k-1) + dzu(k) * <b>q_vertical_gradient</b>)
+up to the top boundary or up to the next height level defined
+by <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>.
+A total of 10 different gradients for 11 height intervals (10 intervals
+if <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>(1)
+= <i>0.0</i>) can be asigned. The surface humidity is assigned
+via <a href="#q_surface">q_surface</a>. </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Example:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p><b>q_vertical_gradient</b> = <i>0.001</i>, <i>0.0005</i>,&nbsp;
+        <br>
+
+
+
+
+
+
+
+
+
+
+        <b>q_vertical_gradient_level</b> = <i>500.0</i>, <i>1000.0</i>,</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+That defines the humidity to be constant with height up to z =
+500.0
+m with a
+value given by <a href="#q_surface">q_surface</a>.
+For 500.0 m &lt; z &lt;= 1000.0 m the humidity gradient is 0.001 / 100
+m and for z &gt; 1000.0 m up to the top boundary it is
+0.0005 / 100 m (it is assumed that the assigned height levels
+correspond with uv
+levels). </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="q_vertical_gradient_level"></a><b>q_vertical_gradient</b>
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>_level</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R (10)</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Height level from which on the moisture gradient defined by <a href="#q_vertical_gradient">q_vertical_gradient</a>
+is effective (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The height levels are to be assigned in ascending order. The
+default values result in a humidity constant with height regardless of
+the values of <a href="#q_vertical_gradient">q_vertical_gradient</a>
+(unless the top boundary of the model is higher than 100000.0 m). For
+the piecewise construction of humidity profiles see <a href="#q_vertical_gradient">q_vertical_gradient</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="radiation"></a><b>radiation</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.F.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on longwave radiation cooling at
+cloud-tops.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Long-wave radiation processes are parameterized by the
+effective emissivity, which considers only the absorption and emission
+of long-wave radiation at cloud droplets. The radiation scheme can be
+used only with <a href="#cloud_physics">cloud_physics</a>
+= .TRUE. .</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="random_generator"></a><b>random_generator</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><i>'numerical</i><br>
+
+
+
+
+
+
+
+
+
+
+      <i>recipes'</i></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Random number generator to be used for creating uniformly
+distributed random numbers. <br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>It is used if random perturbations are to be imposed on the
+velocity field or on the surface heat flux field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>
+and <a href="chapter_4.2.html#random_heatflux">random_heatflux</a>).
+By default, the "Numerical Recipes" random number generator is used.
+This one provides exactly the same order of random numbers on all
+different machines and should be used in particular for comparison runs.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+Besides, a system-specific generator is available ( <b>random_generator</b>
+= <i>'system-specific')</i> which should particularly be used for runs
+on vector parallel computers (NEC), because the default generator
+cannot be vectorized and therefore significantly drops down the code
+performance on these machines.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-weight: bold;">Note:</span><br>
+
+
+
+
+
+
+
+
+
+
+Results from two otherwise identical model runs will not be comparable
+one-to-one if they used different random number generators.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="random_heatflux"></a><b>random_heatflux</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.F.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to impose random perturbations on the internal two-dimensional near surface heat flux field <span style="font-style: italic;">shf</span>. <br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+If a near surface heat flux is used as bottom boundary
+condition (see <a href="#surface_heatflux">surface_heatflux</a>),
+it is by default assumed to be horizontally homogeneous. Random
+perturbations can be imposed on the internal two-dimensional&nbsp;heat flux field <span style="font-style: italic;">shf</span> by assigning <b>random_heatflux</b>
+= <i>.T.</i>. The disturbed heat flux field is calculated by
+multiplying the
+values at each mesh point with a normally distributed random number
+with a mean value and standard deviation of 1. This is repeated after
+every timestep.<br>
+
+
+
+      <br>
+
+
+
+
+
+
+In case of a non-flat <a href="#topography">topography</a>,&nbsp;assigning <b>random_heatflux</b>
+= <i>.T.</i> imposes random perturbations on the combined&nbsp;heat
+flux field <span style="font-style: italic;">shf</span> composed of <a href="#surface_heatflux">surface_heatflux</a> at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a> at the topography top face.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="rif_max"></a><b>rif_max</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>1.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Upper limit of the flux-Richardson number.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>With the Prandtl layer switched on (see <a href="#prandtl_layer">prandtl_layer</a>),
+flux-Richardson numbers (rif) are calculated for z=z<sub>p</sub> (k=1)
+in the 3d-model (in the 1d model for all heights). Their values in
+particular determine the
+values of the friction velocity (1d- and 3d-model) and the values of
+the eddy diffusivity (1d-model). With small wind velocities at the
+Prandtl layer top or small vertical wind shears in the 1d-model, rif
+can take up unrealistic large values. They are limited by an upper (<span style="font-weight: bold;">rif_max</span>) and lower limit (see <a href="#rif_min">rif_min</a>)
+for the flux-Richardson number. The condition <b>rif_max</b> &gt; <b>rif_min</b>
+must be met.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="rif_min"></a><b>rif_min</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>- 5.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Lower limit of the flux-Richardson number.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>For further explanations see <a href="#rif_max">rif_max</a>.
+The condition <b>rif_max</b> &gt; <b>rif_min </b>must be met.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="roughness_length"></a><b>roughness_length</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.1</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Roughness length (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This parameter is effective only in case that a Prandtl layer
+is switched
+on (see <a href="#prandtl_layer">prandtl_layer</a>).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="scalar_advec"></a><b>scalar_advec</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 10</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>'pw-scheme'</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Advection scheme to be used for the scalar quantities.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The user can choose between the following schemes:<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'pw-scheme'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">The scheme of Piascek and
+Williams (1970, J. Comp. Phys., 6,
+392-405) with central differences in the form C3 is used.<br>
+
+
+
+
+
+
+
+
+
+
+If intermediate Euler-timesteps are carried out in case of <a href="#timestep_scheme">timestep_scheme</a>
+= <span style="font-style: italic;">'leapfrog+euler'</span> the
+advection scheme is - for the Euler-timestep - automatically switched
+to an upstream-scheme. <br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'bc-scheme'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">The Bott scheme modified by
+Chlond (1994, Mon.
+Wea. Rev., 122, 111-125). This is a conservative monotonous scheme with
+very small numerical diffusion and therefore very good conservation of
+scalar flow features. The scheme however, is computationally very
+expensive both because it is expensive itself and because it does (so
+far) not allow specific code optimizations (e.g. cache optimization).
+Choice of this
+scheme forces the Euler timestep scheme to be used for the scalar
+quantities. For output of horizontally averaged
+profiles of the resolved / total heat flux, <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
+= <i>'w*pt*BC'</i> / <i>'wptBC' </i>should be used, instead of the
+standard profiles (<span style="font-style: italic;">'w*pt*'</span>
+and <span style="font-style: italic;">'wpt'</span>) because these are
+too inaccurate with this scheme. However, for subdomain analysis (see <a href="#statistic_regions">statistic_regions</a>)
+exactly the reverse holds: here <i>'w*pt*BC'</i> and <i>'wptBC'</i>
+show very large errors and should not be used.<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+This scheme is not allowed for non-cyclic lateral boundary conditions
+(see <a href="#bc_lr">bc_lr</a>
+and <a href="#bc_ns">bc_ns</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">'ups-scheme'</span><br>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="margin-left: 40px;">The upstream-spline-scheme is used
+(see Mahrer and Pielke,
+1978: Mon. Wea. Rev., 106, 818-830). In opposite to the Piascek
+Williams scheme, this is characterized by much better numerical
+features (less numerical diffusion, better preservation of flux
+structures, e.g. vortices), but computationally it is much more
+expensive. In
+addition, the use of the Euler-timestep scheme is mandatory (<a href="#timestep_scheme">timestep_scheme</a>
+= <span style="font-style: italic;">'</span><i>euler'</i>), i.e. the
+timestep accuracy is only first order. For this reason the advection of
+momentum (see <a href="#momentum_advec">momentum_advec</a>)
+should then also be carried out with the upstream-spline scheme,
+because otherwise the momentum would
+be subject to large numerical diffusion due to the upstream
+scheme.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="margin-left: 40px;">Since the cubic splines used tend
+to overshoot under
+certain circumstances, this effect must be adjusted by suitable
+filtering and smoothing (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>,
+      <a href="#long_filter_factor">long_filter_factor</a>, <a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>,
+      <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
+This is always neccesssary for runs with stable stratification,
+even if this stratification appears only in parts of the model
+domain.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="margin-left: 40px;">With stable stratification the
+upstream-upline scheme also produces gravity waves with large
+amplitude, which must be
+suitably damped (see <a href="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p style="margin-left: 40px;"><span style="font-weight: bold;">Important:
+      </span>The&nbsp;
+upstream-spline scheme is not implemented for humidity and passive
+scalars (see <a href="#moisture">moisture</a>
+and <a href="#passive_scalar">passive_scalar</a>)
+and requires the use of a 2d-domain-decomposition. The last conditions
+severely restricts code optimization on several machines leading to
+very long execution times! This scheme is also not allowed for
+non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
+and <a href="#bc_ns">bc_ns</a>).</p><br>A differing advection scheme can be choosed for the subgrid-scale TKE using parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="statistic_regions"></a><b>statistic_regions</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Number of additional user-defined subdomains for which
+statistical analysis
+and corresponding output (profiles, time series) shall be made.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By default, vertical profiles and other statistical quantities
+are calculated as horizontal and/or volume average of the total model
+domain. Beyond that, these calculations can also be carried out for
+subdomains which can be defined using the field <a href="chapter_3.5.3.html">rmask </a>within the user-defined software
+(see <a href="chapter_3.5.3.html">chapter
+3.5.3</a>). The number of these subdomains is determined with the
+parameter <b>statistic_regions</b>. Maximum 9 additional subdomains
+are allowed. The parameter <a href="chapter_4.3.html#region">region</a>
+can be used to assigned names (identifier) to these subdomains which
+are then used in the headers
+of the output files and plots.</p><p>If the default NetCDF output format is selected (see parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>), data for the total domain and all defined subdomains are output to the same file(s) (<a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>, <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>). In case of <span style="font-weight: bold;">statistic_regions</span> &gt; <span style="font-style: italic;">0</span>,
+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
+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
+respective file connection statements of the <span style="font-weight: bold;">mrun</span> configuration file).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="surface_heatflux"></a><b>surface_heatflux</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
+heatflux<br>
+      </span></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Kinematic sensible heat flux at the bottom surface (in K m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If a value is assigned to this parameter, the internal two-dimensional surface heat flux field <span style="font-style: italic;">shf</span> is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span>&nbsp;as bottom (horizontally homogeneous) boundary condition for the
+temperature equation. This additionally requires that a Neumann
+condition must be used for the potential temperature (see <a href="#bc_pt_b">bc_pt_b</a>),
+because otherwise the resolved scale may contribute to
+the surface flux so that a constant value cannot be guaranteed. Also,
+changes of the
+surface temperature (see <a href="#pt_surface_initial_change">pt_surface_initial_change</a>)
+are not allowed. The parameter <a href="#random_heatflux">random_heatflux</a>
+can be used to impose random perturbations on the (homogeneous) surface heat
+flux field <span style="font-style: italic;">shf</span>.&nbsp;</p>
+
+
+
+      
+      
+      
+      <p>
+
+
+In case of a non-flat <a href="#topography">topography</a>,&nbsp;the internal two-dimensional&nbsp;surface heat
+flux field <span style="font-style: italic;">shf</span> is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span> at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a> at the topography top face.&nbsp;The parameter<a href="#random_heatflux"> random_heatflux</a>
+can be used to impose random perturbations on this combined surface heat
+flux field <span style="font-style: italic;">shf</span>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If no surface heat flux is assigned, <span style="font-style: italic;">shf</span> is calculated at each timestep by u<sub>*</sub> * theta<sub>*</sub>
+(of course only with <a href="#prandtl_layer">prandtl_layer</a> switched on). Here, u<sub>*</sub>
+and theta<sub>*</sub> are calculated from the Prandtl law assuming
+logarithmic wind and temperature
+profiles between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_pt_b">bc_pt_b</a>)
+must be used as bottom boundary condition for the potential temperature.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="surface_pressure"></a><b>surface_pressure</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>1013.25</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Atmospheric pressure at the surface (in hPa).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+Starting from this surface value, the vertical pressure
+profile is calculated once at the beginning of the run assuming a
+neutrally stratified
+atmosphere. This is needed for
+converting between the liquid water potential temperature and the
+potential temperature (see <a href="#cloud_physics">cloud_physics</a><span style="text-decoration: underline;"></span>).</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="surface_scalarflux"></a><b>surface_scalarflux</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Scalar flux at the surface (in kg/(m<sup>2</sup> s)).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If a non-zero value is assigned to this parameter, the
+respective scalar flux value is used
+as bottom (horizontally homogeneous) boundary condition for the scalar
+concentration equation.&nbsp;This additionally requires that a Neumann
+condition must be used for the scalar concentration&nbsp;(see <a href="#bc_s_b">bc_s_b</a>),
+because otherwise the resolved scale may contribute to
+the surface flux so that a constant value cannot be guaranteed. Also,
+changes of the
+surface scalar concentration (see <a href="#s_surface_initial_change">s_surface_initial_change</a>)
+are not allowed. <br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If no surface scalar flux is assigned (<b>surface_scalarflux</b>
+= <i>0.0</i>),
+it is calculated at each timestep by u<sub>*</sub> * s<sub>*</sub>
+(of course only with Prandtl layer switched on). Here, s<sub>*</sub>
+is calculated from the Prandtl law assuming a logarithmic scalar
+concentration
+profile between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_s_b">bc_s_b</a>)
+must be used as bottom boundary condition for the scalar concentration.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="surface_waterflux"></a><b>surface_waterflux</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Kinematic water flux near the surface (in m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If a non-zero value is assigned to this parameter, the
+respective water flux value is used
+as bottom (horizontally homogeneous) boundary condition for the
+humidity equation. This additionally requires that a Neumann
+condition must be used for the specific humidity / total water content
+(see <a href="#bc_q_b">bc_q_b</a>),
+because otherwise the resolved scale may contribute to
+the surface flux so that a constant value cannot be guaranteed. Also,
+changes of the
+surface humidity (see <a href="#q_surface_initial_change">q_surface_initial_change</a>)
+are not allowed.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If no surface water flux is assigned (<b>surface_waterflux</b>
+= <i>0.0</i>),
+it is calculated at each timestep by u<sub>*</sub> * q<sub>*</sub>
+(of course only with Prandtl layer switched on). Here, q<sub>*</sub>
+is calculated from the Prandtl law assuming a logarithmic temperature
+profile between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_q_b">bc_q_b</a>)
+must be used as the bottom boundary condition for the humidity.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="s_surface"></a><b>s_surface</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Surface value of the passive scalar (in kg/m<sup>3</sup>).&nbsp;<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+This parameter assigns the value of the passive scalar s at
+the surface (k=0)<b>.</b> Starting from this value, the
+initial vertical scalar concentration profile is constructed with<a href="#s_vertical_gradient">
+s_vertical_gradient</a> and <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="s_surface_initial_change"></a><b>s_surface_initial</b>
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>_change</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Change in surface scalar concentration to be made at the
+beginning of the 3d run (in kg/m<sup>3</sup>).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>If <b>s_surface_initial_change</b><i>&nbsp;</i>is set to a
+non-zero
+value, the near surface scalar flux is not allowed to be given
+simultaneously (see <a href="#surface_scalarflux">surface_scalarflux</a>).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="s_vertical_gradient"></a><b>s_vertical_gradient</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R (10)</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>10 * 0</i><i>.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Scalar concentration gradient(s) of the initial scalar
+concentration profile (in kg/m<sup>3 </sup>/
+100 m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The scalar gradient holds starting from the height level
+defined by <a href="#s_vertical_gradient_level">s_vertical_gradient_level
+      </a>(precisely: for all uv levels k, where zu(k) &gt;
+s_vertical_gradient_level, s_init(k) is set: s_init(k) = s_init(k-1) +
+dzu(k) * <b>s_vertical_gradient</b>) up to the top boundary or up to
+the next height level defined by <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.
+A total of 10 different gradients for 11 height intervals (10 intervals
+if <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>(1)
+= <i>0.0</i>) can be assigned. The surface scalar value is assigned
+via <a href="#s_surface">s_surface</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Example:&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <ul>
+
+
+
+
+
+
+
+
+
+
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        
+        <p><b>s_vertical_gradient</b> = <i>0.1</i>, <i>0.05</i>,&nbsp;
+        <br>
+
+
+
+
+
+
+
+
+
+
+        <b>s_vertical_gradient_level</b> = <i>500.0</i>, <i>1000.0</i>,</p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      </ul>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>That defines the scalar concentration to be constant with
+height up to z = 500.0 m with a value given by <a href="#s_surface">s_surface</a>.
+For 500.0 m &lt; z &lt;= 1000.0 m the scalar gradient is 0.1
+kg/m<sup>3 </sup>/ 100 m and for z &gt; 1000.0 m up to the top
+boundary it is 0.05 kg/m<sup>3 </sup>/ 100 m (it is assumed that the
+assigned height levels
+correspond with uv
+levels).</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="s_vertical_gradient_level"></a><b>s_vertical_gradient_</b>
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <b>level</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R (10)</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><i>10 *</i> <i>0.0</i></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Height level from which on the scalar gradient defined by <a href="#s_vertical_gradient">s_vertical_gradient</a>
+is effective (in m).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The height levels are to be assigned in ascending order. The
+default values result in a scalar concentration constant with height
+regardless of the values of <a href="#s_vertical_gradient">s_vertical_gradient</a>
+(unless the top boundary of the model is higher than 100000.0 m). For
+the
+piecewise construction of scalar concentration profiles see <a href="#s_vertical_gradient">s_vertical_gradient</a>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="timestep_scheme"></a><b>timestep_scheme</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 20</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><i>'runge</i><br>
+
+
+
+
+
+
+
+
+
+
+      <i>kutta-3'</i></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Time step scheme to be used for the integration of the prognostic
+variables.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The user can choose between the following schemes:<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'runge-kutta-3'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">Third order Runge-Kutta scheme.<br>
+
+
+
+
+
+
+
+
+
+
+This scheme requires the use of <a href="#momentum_advec">momentum_advec</a>
+= <a href="#scalar_advec">scalar_advec</a>
+= '<i>pw-scheme'</i>. Please refer to the&nbsp;<a href="../tec/numerik.heiko/zeitschrittverfahren.pdf">documentation on PALM's time integration schemes&nbsp;(28p., in German)</a> fur further details.<br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'runge-kutta-2'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">Second order Runge-Kutta scheme.<br>
+
+
+
+
+
+
+
+
+
+
+For special features see <b>timestep_scheme</b> = '<i>runge-kutta-3'</i>.<br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;"><span style="font-style: italic;">'leapfrog'</span><br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      </span>
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">Second order leapfrog scheme.<br>
+
+
+
+
+
+
+
+
+
+
+Although this scheme requires a constant timestep (because it is
+centered in time),&nbsp; is even applied in case of changes in
+timestep. Therefore, only small
+changes of the timestep are allowed (see <a href="#dt">dt</a>).
+However, an Euler timestep is always used as the first timestep of an
+initiali run. When using the Bott-Chlond scheme for scalar advection
+(see <a href="#scalar_advec">scalar_advec</a>),
+the prognostic equation for potential temperature will be calculated
+with the Euler scheme, although the leapfrog scheme is switched
+on.&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+The leapfrog scheme must not be used together with the upstream-spline
+scheme for calculating the advection (see <a href="#scalar_advec">scalar_advec</a>
+= '<i>ups-scheme'</i> and <a href="#momentum_advec">momentum_advec</a>
+= '<i>ups-scheme'</i>).<br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">'</span><span style="font-style: italic;"><span style="font-style: italic;">leapfrog+euler'</span><br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      </span>
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">The leapfrog scheme is used, but
+after each change of a timestep an Euler timestep is carried out.
+Although this method is theoretically correct (because the pure
+leapfrog method does not allow timestep changes), the divergence of the
+velocity field (after applying the pressure solver) may be
+significantly larger than with <span style="font-style: italic;">'leapfrog'</span>.<br>
+
+
+
+
+
+
+
+
+
+
+      </div>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;">'euler'</span><br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">First order Euler scheme.&nbsp; <br>
+
+
+
+
+
+
+
+
+
+
+The Euler scheme must be used when treating the advection terms with
+the upstream-spline scheme (see <a href="#scalar_advec">scalar_advec</a>
+= <span style="font-style: italic;">'ups-scheme'</span> and <a href="#momentum_advec">momentum_advec</a>
+= <span style="font-style: italic;">'ups-scheme'</span>).</div>
+
+
+
+
+
+
+
+
+
+
+      <br><br>A differing timestep scheme can be choosed for the subgrid-scale TKE using parameter <a href="#use_upstream_for_tke">use_upstream_for_tke</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+      <td style="text-align: left; vertical-align: top;"><span style="font-weight: bold;"><a name="topography"></a></span><span style="font-weight: bold;">topography</span></td>
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">C * 40</td>
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">'flat'</span></td>
+
+
+
+
+
+
+
+
+
+      <td>
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Topography mode.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The user can choose between the following modes:<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'flat'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">Flat surface.</div>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'single_building'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">Flow around&nbsp;a single rectangular building mounted on a flat surface.<br>
+The building size and location can be specified with the parameters <a href="#building_height">building_height</a>, <a href="#building_length_x">building_length_x</a>, <a href="#building_length_y">building_length_y</a>, <a href="#building_wall_left">building_wall_left</a> and <a href="#building_wall_south">building_wall_south</a>.</div>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;"></span>
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">'read_from_file'</span><br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <div style="margin-left: 40px;">Flow around arbitrary topography.<br>
+This mode requires the input file <a href="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</a><font color="#000000">. This file contains </font><font color="#000000"><font color="#000000">the&nbsp;</font></font><font color="#000000">arbitrary topography </font><font color="#000000"><font color="#000000">height information</font></font><font color="#000000"> in m. These data&nbsp;<span style="font-style: italic;"></span>must exactly match the horizontal grid.</font>
+
+
+
+
+
+
+
+
+ 
+      </div>
+
+
+
+
+
+
+
+
+
+
+      <span style="font-style: italic;"><br>
+
+
+
+
+
+
+
+
+
+      </span><font color="#000000">
+Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a> to allow further topography modes.<br>
+
+
+
+
+
+
+
+
+      <br>
+All non-flat <span style="font-weight: bold;">topography</span> modes </font>require the use of <a href="#momentum_advec">momentum_advec</a>
+= <a href="#scalar_advec">scalar_advec</a>
+= '<i>pw-scheme'</i>, <a href="chapter_4.2.html#psolver">psolver</a> = <i>'poisfft'</i> or '<i>poisfft_hybrid'</i>, <i>&nbsp;</i><a href="#alpha_surface">alpha_surface</a> = 0.0, <a href="#bc_lr">bc_lr</a> = <a href="#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>,&nbsp;<a style="" href="#galilei_transformation">galilei_transformation</a> = <span style="font-style: italic;">.F.</span>,&nbsp;<a href="#cloud_physics">cloud_physics&nbsp;</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#moisture">moisture</a> = <span style="font-style: italic;">.F.</span>, and <a href="#prandtl_layer">prandtl_layer</a> = .T..<br>
+      <font color="#000000"><br>
+
+
+
+
+
+
+
+
+Note that an inclined model domain requires the use of <span style="font-weight: bold;">topography</span> = <span style="font-style: italic;">'flat'</span> and a nonzero </font><a href="#alpha_surface">alpha_surface</a>.</td>
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ug_surface"></a><span style="font-weight: bold;">ug_surface</span></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">u-component of the geostrophic
+wind at the surface (in m/s).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+This parameter assigns the value of the u-component of the geostrophic
+wind (ug) at the surface (k=0). Starting from this value, the initial
+vertical profile of the <br>
+
+
+
+
+
+
+
+
+
+
+u-component of the geostrophic wind is constructed with <a href="#ug_vertical_gradient">ug_vertical_gradient</a> and <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>. The
+profile constructed in that way is used for creating the initial
+vertical velocity profile of the 3d-model. Either it is applied, as it
+has been specified by the user (<a href="#initializing_actions">initializing_actions</a>
+= 'set_constant_profiles') or it is used for calculating a stationary
+boundary layer wind profile (<a href="#initializing_actions">initializing_actions</a>
+= 'set_1d-model_profiles'). If ug is constant with height (i.e. ug(k)=<span style="font-weight: bold;">ug_surface</span>) and&nbsp; has a large
+value, it is recommended to use a Galilei-transformation of the
+coordinate system, if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
+in order to obtain larger time steps.<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ug_vertical_gradient"></a><span style="font-weight: bold;">ug_vertical_gradient</span></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R(10)<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Gradient(s) of the initial
+profile of the&nbsp; u-component of the geostrophic wind (in 1/100s).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The gradient holds starting from the height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>
+(precisely: for all uv levels k where zu(k) &gt; <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>,
+ug(k) is set: ug(k) = ug(k-1) + dzu(k) * <span style="font-weight: bold;">ug_vertical_gradient</span>) up to the top
+boundary or up to the next height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>. A
+total of 10 different gradients for 11 height intervals (10
+intervals&nbsp; if <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>(1)
+= 0.0) can be assigned. The surface geostrophic wind is assigned by <a href="#ug_surface">ug_surface</a>. <br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ug_vertical_gradient_level"></a><span style="font-weight: bold;">ug_vertical_gradient_level</span></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R(10)<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Height level from which on the
+gradient defined by <a href="#ug_vertical_gradient">ug_vertical_gradient</a>
+is effective (in m).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The height levels are to be assigned in ascending order. For the
+piecewise construction of a profile of the u-component of the
+geostrophic wind component (ug) see <a href="#ug_vertical_gradient">ug_vertical_gradient</a>.<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ups_limit_e"></a><b>ups_limit_e</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Subgrid-scale turbulent kinetic energy difference used as
+criterion for applying the upstream scheme when upstream-spline
+advection is switched on (in m<sup>2</sup>/s<sup>2</sup>).
+&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This variable steers the appropriate treatment of the
+advection of the subgrid-scale turbulent kinetic energy in case that
+the uptream-spline scheme is used . For further information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are allowed for <b>ups_limit_e</b>. </p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ups_limit_pt"></a><b>ups_limit_pt</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Temperature difference used as criterion for applying&nbsp;
+the upstream scheme when upstream-spline advection&nbsp; is switched on
+(in K).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This criterion is used if the upstream-spline scheme is
+switched on (see <a href="#scalar_advec">scalar_advec</a>).<br>
+
+
+
+
+
+
+
+
+
+
+If, for a given gridpoint, the absolute temperature difference with
+respect to the upstream
+grid point is smaller than the value given for <b>ups_limit_pt</b>,
+the upstream scheme is used for this gridpoint (by default, the
+upstream-spline scheme is always used). Reason: in case of a very small
+upstream gradient, the advection should cause only a very small
+tendency. However, in such situations the upstream-spline scheme may
+give wrong tendencies at a
+grid point due to spline overshooting, if simultaneously the downstream
+gradient is very large. In such cases it may be more reasonable to use
+the upstream scheme. The numerical diffusion caused by the upstream
+schme remains small as long as the upstream gradients are small.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The percentage of grid points for which the upstream
+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
+of gridpoints&nbsp; should stay below a certain limit, however, it is
+not possible to give
+a general limit, since it depends on the respective flow.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are permitted for <b>ups_limit_pt</b>.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+A more effective control of
+the &ldquo;overshoots&rdquo; can be achieved with parameter <a href="#cut_spline_overshoot">cut_spline_overshoot</a>. </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ups_limit_u"></a><b>ups_limit_u</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Velocity difference (u-component) used as criterion for
+applying the upstream scheme
+when upstream-spline advection is switched on (in m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This variable steers the appropriate treatment of the
+advection of the u-velocity-component in case that the upstream-spline
+scheme is used. For further
+information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are permitted for <b>ups_limit_u</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ups_limit_v"></a><b>ups_limit_v</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Velocity difference (v-component) used as criterion for
+applying the upstream scheme
+when upstream-spline advection is switched on (in m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This variable steers the appropriate treatment of the
+advection of the v-velocity-component in case that the upstream-spline
+scheme is used. For further
+information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are permitted for <b>ups_limit_v</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="ups_limit_w"></a><b>ups_limit_w</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>0.0</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Velocity difference (w-component) used as criterion for
+applying the upstream scheme
+when upstream-spline advection is switched on (in m/s).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>This variable steers the appropriate treatment of the
+advection of the w-velocity-component in case that the upstream-spline
+scheme is used. For further
+information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Only positive values are permitted for <b>ups_limit_w</b>.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="use_surface_fluxes"></a><b>use_surface_fluxes</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.F.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to steer the treatment of the subgrid-scale vertical
+fluxes within the diffusion terms at k=1 (bottom boundary).<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>By default, the near-surface subgrid-scale fluxes are
+parameterized (like in the remaining model domain) using the gradient
+approach. If <b>use_surface_fluxes</b>
+= <i>.TRUE.</i>, the user-assigned surface fluxes are used instead
+(see <a href="#surface_heatflux">surface_heatflux</a>, <a href="#surface_waterflux">surface_waterflux</a>
+and <a href="#surface_scalarflux">surface_scalarflux</a>) <span style="font-weight: bold;">or</span> the surface fluxes are
+calculated via the Prandtl layer relation (depends on the bottom
+boundary conditions, see <a href="#bc_pt_b">bc_pt_b</a>, <a href="#bc_q_b">bc_q_b</a>
+and <a href="#bc_s_b">bc_s_b</a>).<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><b>use_surface_fluxes</b>
+is automatically set <i>.TRUE.</i>, if a Prandtl layer is used (see <a href="#prandtl_layer">prandtl_layer</a>).&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>The user may prescribe the surface fluxes at the bottom
+boundary without using a Prandtl layer by setting <span style="font-weight: bold;">use_surface_fluxes</span> = <span style="font-style: italic;">.T.</span> and <span style="font-weight: bold;">prandtl_layer</span> = <span style="font-style: italic;">.F.</span>. If , in this case, the
+momentum flux (u<sub>*</sub><sup>2</sup>) should also be prescribed,
+the user must assign an appropriate value within the user-defined code.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="use_ug_for_galilei_tr"></a><b>use_ug_for_galilei_tr</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.T.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Switch to determine the translation velocity in case that a
+Galilean transformation is used.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>In case of a Galilean transformation (see <a href="#galilei_transformation">galilei_transformation</a>), <b>use_ug_for_galilei_tr</b>
+= <i>.T.</i>&nbsp; ensures
+that the coordinate system is translated with the geostrophic windspeed.<br>
+
+
+
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Alternatively, with <b>use_ug_for_galilei_tr</b> = <i>.F</i>.,
+the
+geostrophic wind can be replaced as translation speed by the (volume)
+averaged velocity. However, in this case the user must be aware of fast
+growing gravity waves, so this
+choice is usually not recommended!</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr><td align="left" valign="top"><a name="use_upstream_for_tke"></a><span style="font-weight: bold;">use_upstream_for_tke</span></td><td align="left" valign="top">L</td><td align="left" valign="top"><span style="font-style: italic;">.F.</span></td><td align="left" valign="top">Parameter to choose the advection/timestep scheme to be used for the subgrid-scale TKE.<br><br>By
+default, the advection scheme and the timestep scheme to be used for
+the subgrid-scale TKE are set by the initialization parameters <a href="#scalar_advec">scalar_advec</a> and <a href="#timestep_scheme">timestep_scheme</a>, respectively. <span style="font-weight: bold;">use_upstream_for_tke</span> = <span style="font-style: italic;">.T.</span>
+forces the Euler-scheme and the upstream-scheme to be used as timestep
+scheme and advection scheme, respectively. By these methods, the strong
+(artificial) near-surface vertical gradients of the subgrid-scale TKE
+are significantly reduced. This is required when subgrid-scale
+velocities are used for advection of particles (see particle package
+parameter <a href="chapter_4.2.html#use_sgs_for_particles">use_sgs_for_particles</a>).</td></tr><tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="vg_surface"></a><span style="font-weight: bold;">vg_surface</span></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">v-component of the geostrophic
+wind at the surface (in m/s).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+This parameter assigns the value of the v-component of the geostrophic
+wind (vg) at the surface (k=0). Starting from this value, the initial
+vertical profile of the <br>
+
+
+
+
+
+
+
+
+
+
+v-component of the geostrophic wind is constructed with <a href="#vg_vertical_gradient">vg_vertical_gradient</a> and <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>. The
+profile
+constructed in that way is used for creating the initial vertical
+velocity profile of the 3d-model. Either it is applied, as it has been
+specified by the user (<a href="#initializing_actions">initializing_actions</a>
+= 'set_constant_profiles')
+or it is used for calculating a stationary boundary layer wind profile
+(<a href="#initializing_actions">initializing_actions</a> =
+'set_1d-model_profiles'). If vg is constant
+with height (i.e. vg(k)=<span style="font-weight: bold;">vg_surface</span>)
+and&nbsp; has a large value, it is
+recommended to use a Galilei-transformation of the coordinate system,
+if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
+in order to obtain larger
+time steps.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="vg_vertical_gradient"></a><span style="font-weight: bold;">vg_vertical_gradient</span></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R(10)<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Gradient(s) of the initial
+profile of the&nbsp; v-component of the geostrophic wind (in 1/100s).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The gradient holds starting from the height level defined by <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>
+(precisely: for all uv levels k where zu(k)
+&gt; <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
+vg(k) is set: vg(k) = vg(k-1) + dzu(k)
+* <span style="font-weight: bold;">vg_vertical_gradient</span>) up to
+the top boundary or up to the next height
+level defined by <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>.
+A total of 10 different
+gradients for 11 height intervals (10 intervals&nbsp; if <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>(1) =
+0.0) can be assigned. The surface
+geostrophic wind is assigned by <a href="#vg_surface">vg_surface</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="vg_vertical_gradient_level"></a><span style="font-weight: bold;">vg_vertical_gradient_level</span></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R(10)<br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">10
+* 0.0</span><br>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Height level from which on the
+gradient defined by <a href="#vg_vertical_gradient">vg_vertical_gradient</a>
+is effective (in m).<br>
+
+
+
+
+
+
+
+
+
+
+      <br>
+
+
+
+
+
+
+
+
+
+
+The height levels are to be assigned in ascending order. For the
+piecewise construction of a profile of the v-component of the
+geostrophic wind component (vg) see <a href="#vg_vertical_gradient">vg_vertical_gradient</a>.</td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p><a name="wall_adjustment"></a><b>wall_adjustment</b></p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L</td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><i>.T.</i></td>
+
+
+
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>Parameter to restrict the mixing length in the vicinity of the
+bottom
+boundary.&nbsp; </p>
+
+
+
+
+
+
+
+
+
+
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      <p>With <b>wall_adjustment</b> = <i>.TRUE., </i>the mixing
+length is limited to a maximum of&nbsp; 1.8 * z. This condition
+typically affects only the
+first grid points above the bottom boundary.</p>
+
+
+
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="wall_heatflux"></a>wall_heatflux</span></td>
+
+
+
+
+
+
+      <td style="vertical-align: top;">R(5)</td>
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">5 * 0.0</span></td>
+
+
+
+
+
+
+      <td>Prescribed kinematic sensible heat flux in W m<sup>-2</sup>
+at the five topography faces:<br>
+
+
+
+      <br>
+
+
+
+      
+      
+      
+      <div style="margin-left: 40px;"><span style="font-weight: bold;">wall_heatflux(0)&nbsp;&nbsp; &nbsp;</span>top face<br>
+
+
+
+      <span style="font-weight: bold;">wall_heatflux(1)&nbsp;&nbsp;&nbsp; </span>left face<br>
+
+
+
+      <span style="font-weight: bold;">wall_heatflux(2)&nbsp;&nbsp;&nbsp; </span>right face<br>
+
+
+
+      <span style="font-weight: bold;">wall_heatflux(3)&nbsp;&nbsp;&nbsp; </span>south face<br>
+
+
+
+      <span style="font-weight: bold;">wall_heatflux(4)&nbsp;&nbsp;&nbsp; </span>north face</div>
+
+
+
+      <br>
+
+
+
+This parameter applies only in case of a non-flat <a href="#topography">topography</a>.&nbsp;The parameter <a href="#random_heatflux">random_heatflux</a>
+can be used to impose random perturbations on the internal two-dimensional surface heat
+flux field <span style="font-style: italic;">shf</span> that is composed of <a href="#surface_heatflux">surface_heatflux</a> at the bottom surface and <span style="font-weight: bold;">wall_heatflux(0)</span> at the topography top face.&nbsp;</td>
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  </tbody>
+</table>
+
+
+
+
+
+
+
+
+
+
+<br>
+
+
+
+
+
+
+
+
+
+
+<p style="line-height: 100%;"><br>
+
+
+
+
+
+
+
+
+
+
+<font color="#000080"><font color="#000080"><a href="chapter_4.0.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.2.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+
+
+
+
+
+
+
+
+
+
+<p style="line-height: 100%;"><i>Last change:&nbsp;</i> 22/08/06 (SR) </p>
+
+
+
+
+
+
+
+
+
+
+<br>
+
+
+
+
+
+
+
+
+
+
+<br>
+
+
+
+
+
+
+
+
+
+
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.2.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.2.html	(revision 5)
@@ -0,0 +1,3718 @@
+<!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
+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
+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
+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
+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>
+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
+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
+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
+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>
+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>.
+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>
+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
+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
+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
+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>,
+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>,
+and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>.
+In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
+and <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
+the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a>
+and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>.
+A perturbation is added to each grid point with its individual value
+determined by multiplying the disturbance amplitude with a uniformly
+distributed random number.
+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
+is not necessary and can be omitted (this does not hold for non-cyclic
+lateral boundaries!). This can be steered by assigning
+an upper limit value for the perturbation energy (the perturbation
+energy is defined by the deviation of the velocity from the mean flow)
+using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>.
+As soon as the perturbation energy has exceeded this energy limit, no
+more random perturbations are assigned<br>
+.&nbsp; <br>
+Timesteps where a random perturbation has been imposed are marked in
+the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
+by the character "D" appended to the values of the maximum horizontal
+velocities. </p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
+      </td>
+      <td style="vertical-align: top;">C*10&nbsp; <br>
+&nbsp;&nbsp; (100)</td>
+      <td style="vertical-align: top;"><i>100 * ' '</i></td>
+      <td style="vertical-align: top;">
+      <p>Type of 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>,
+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
+certain quantities (e.g. the near-surface heat flux) in order to ensure
+a better comparability. This type of normalization then applies to all
+profiles of one coordinate system (panel). The normalization quantities
+are re-calculated for each output time of each individual profile. If
+temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>),
+then the normalization quantities are also temporally averaged
+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
+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>).
+Instead of this, they can be calculated from the data of a certain
+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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+(local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
+&nbsp;<br>
+The assigned normalization quantity is noted in the axes labels of the
+respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
+      </td>
+      <td style="vertical-align: top;">C*10&nbsp; <br>
+&nbsp;&nbsp; (100)</td>
+      <td style="vertical-align: top;"><i>100 * ' '</i></td>
+      <td style="vertical-align: top;">
+      <p>Type of 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>,
+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
+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 '
+,</span><br>
+14 * <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>
+determines how many coordinate systems (panels) the plot contains and
+which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
+expects a character string (up to 100 characters long) for each
+coordinate system, which consists of the names of the profiles to be
+drawn into this system (all available profiles and their respective
+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
+(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>)
+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
+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
+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>
+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
+K',&nbsp; </span><br style="font-style: italic;">
+        <span style="font-style: italic;">'heat flux in K
+ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
+        <span style="font-style: italic;">'momentum flux in
+m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;">
+        <span style="font-style: italic;">'eddy diffusivity in
+m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
+        <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
+        <br>
+14 * <span style="font-style: italic;">' '</span></p>
+      </ul>
+      <p>This parameter can be used to assign x-axis 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>
+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
+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
+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
+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
+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
+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
+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
+cross section data, this string must be appended after the cross
+section string). Cross section data can also be (additionally) averaged
+along the direction normal to the respective section (see below).
+Assignments of quantities can be given in arbitrary
+order:<br><br>Example:<br><br><div style="margin-left: 40px;"><span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'pt_xz_av'</span>, <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'u_av'</span>.<br></div><br>This
+example will create the following output: instantaneous 3d volume data
+of u-velocity component (by default on file DATA_3D_NETCDF), temporally
+averaged 3d volume data of u-velocity component (by default on file
+DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of
+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>.
+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;
+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
+&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
+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>.
+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>
+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
+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>
+(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;
+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
+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>.
+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;
+means that the file starts with the pressure data, followed by the
+v-component of the velocity, etc.). Both instantaneous and time
+averaged data are written on this file! Additional to this file, PALM
+creates
+a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>)
+with coordinate information needed by <span style="font-weight: bold;">AVS</span>.
+As third and
+fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
+and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>),
+which describe the contents of the data file and/or coordinate file
+and are used by AVS. However, AVS expects the content description in
+one file. This needs the local file PLOT3D_FLD_COOR to be appended to
+the file
+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
+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
+4.5.5</a>.</p>By assigning <span style="font-weight: bold;">data_output_format </span>= <span style="font-style: italic;">'iso2d'</span>, the cross section data is output to the local files <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>, <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>, and <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
+Output is in FORTRAN binary format&nbsp;readable by
+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;
+means that the file containing the horizontal cross section data starts
+with the instantaneous pressure data, followed by the
+temporally averaged v-component of the velocity, etc.). Both
+instantaneous and time averaged data are written on this
+file!Additional to these binary files, PALM
+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>)
+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
+respective files with suffix _GLOBAL (by
+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
+parameter file. The plot layout is steered via the parameter input
+file.
+The values of these <span style="font-weight: bold;">iso2d</span>
+parameters are determined by a set of mostly internal PALM parameters
+(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
+4.5.4</a>.<br><br><span style="font-weight: bold;">Important:</span><br>There is no guarantee that iso2d- and avs-output will be available in future PALM versions (later than 3.0).
+      
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
+      </td>
+      <td style="vertical-align: top;">C * 10 (10)
+      </td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span>
+      </td>
+      <td style="vertical-align: top;">Format of output data.<br><br>By 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
+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
+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>.
+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,
+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
+(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
+(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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+turbulent transport of pressure
+fluctuations (resolved)</td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
+            <td style="vertical-align: top;">Energy production by
+transport of resolved-scale TKE</td>
+          </tr>
+        </tbody>
+      
+      </table>
+
+      <br>
+
+Beyond that, initial profiles (t=0) of some variables can be also be
+output (this output is only done once
+with the first plot output and not repeated with the profile output at
+later
+times). The names of these profiles result from the ones specified
+above leaded by a hash "#".&nbsp; Allowed values are:<br>
+
+      
+      <ul>
+<p><i>#u</i>, <i>#v</i>, <i>#pt</i>, <i>#km</i>, <i>#kh</i>,
+        <i>#l</i></p>
+      </ul>
+
+      
+      <p>These initial profiles have been either set by 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>.
+Profiles 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 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>,
+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
+4.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
+4.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
+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>
+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
+imposed to the horizontal velocity field (in m/s).&nbsp; </p>
+      <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 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
+random perturbations to the horizontal velocity field. The perturbation
+energy is defined as the volume average (over the total model domain)
+of the squares of the deviations of the velocity components from the
+mean flow (horizontal average). If the perturbation energy exceeds the
+assigned value, random perturbations to the fields of horizontal
+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
+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 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
+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>
+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
+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>)
+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
+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
+(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
+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
+machines. Additional information for
+handling compressed data is given in <a href="chapter_4.5.6.html">chapter
+4.5.6</a>.</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="do3d_precision"></a><b>do3d_precision</b></p>
+      </td>
+      <td style="vertical-align: top;">C * 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
+(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
+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
+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
+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>,
+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>,
+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
+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>,
+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),
+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
+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>,
+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>
+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
+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>,
+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
+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
+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
+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>,
+etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
+profiles can not be calculated for times lying within a time step
+interval, the output times can deviate from these theoretical values.
+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
+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>
+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
+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
+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,
+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
+interval, the output times can deviate from these theoretical values.
+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
+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>
+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
+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
+(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
+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
+&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
+2*<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
+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
+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>,
+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
+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
+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">),
+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
+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
+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
+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">),
+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
+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
+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
+3d-volume data is switched on (see </font></span><font><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>)<span style="font-family: thorndale;">, this parameter can be used 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
+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
+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
+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
+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>,
+2*<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
+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
+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
+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
+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>
+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
+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
+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
+sufficiently reduced by the pressure solver. It should be reduced at
+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
+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>
+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>),
+the value of this parameter defines on which grid level the data are
+gathered on PE0 in order to allow for a further coarsening of the grid.
+The finest grid defines the largest grid level. By default, the
+gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</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
+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><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;">
+      <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>),
+the value of this parameter defines on which grid level the data are
+gathered on PE0 in order to allow for a further coarsening of the grid.
+The finest grid defines the largest grid level. By default, the
+gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</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
+(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>),
+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
+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
+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
+as pressure solver (<a href="#psolver">psolver</a>
+= <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
+runs (the default value will not at all be sufficient for larger grid
+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>
+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>
+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>),
+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
+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>
+determines how many panels are to be
+arranged next to each other in one row (number of columns). The
+respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>.
+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
+panels are drawn on an additional page. If cranz &lt; <b>profile_columns</b>,
+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
+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
+along x and y, solution of a
+tridiagonal matrix along z, and backward
+FFT (see Siano, institute reports, volume 54). The FFT routines to be
+used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
+This solver is specially optimized for 1d domain decompositions.
+Vectorization is optimized for domain decompositions along x only.</td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;">
+            <p><i>poisfft_</i> <br>
+            <i>hybrid</i></p>
+            </td>
+            <td style="vertical-align: top;">Direct method using FFT
+along x and y, solution of a
+tridiagonal matrix along z, and backward
+FFT (see Siano, institute reports, volume 54). The FFT routines to be
+used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
+This solver is specially optimized for 1d domain decompositions.
+Vectorization is optimized for domain decompositions along x only.</td>
+          </tr>
+          <tr>
+            <td style="vertical-align: top;"><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>)
+are implemented. The convergence of the iterative scheme can be
+steered by the number of v-/w-cycles to be carried out for each call of
+the scheme (<a href="#mg_cycles">mg_cycles</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>
+The
+smaller this limit is, the more cycles have to be carried out in this
+case and the number of cycles may vary from timestep to timestep.</p>
+            <br>
+If <a href="#mg_cycles">mg_cycles</a>
+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
+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
+multi-grid scheme can even be faster than the direct solver (although
+its accuracy is several orders of magnitude worse, but this does not
+affect the accuracy of the simulation). Nevertheless, the user should
+always carry out some test runs in order to find out the optimum value
+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
+the
+subdomains (or of the total domain, if only one PE is uesd) along each
+of the directions can at least be devided once by 2 without rest.</p>
+With parallel runs, starting from a certain grid level the
+data of the subdomains are possibly gathered on PE0 in order to allow
+for a further coarsening of the grid. The grid level for gathering can
+be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
+            <p>Using this procedure requires the subdomains to be of
+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
+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
+needs substantially
+more computing time. It should only be used for test runs, e.g. if
+errors in the other pressure solver methods are assumed.</td>
+          </tr>
+        </tbody>
+      </table>
+      <br>
+In order to speed-up 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
+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
+respective basic states (e.g. the geostrophic wind). The intensity of
+damping is controlled by the value the <b>rayleigh_damping_factor</b>
+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
+at
+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
+reflected&nbsp; at the top
+boundary. This particularly happens with the upstream-spline scheme
+switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
+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>
+&lt;= <b>rayleigh_damping_factor</b>
+&lt;= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
+numerical instabilities.</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b> <br>
+      <b>_height</b></p>
+      </td>
+      <td style="vertical-align: top;">R</td>
+      <td style="vertical-align: top;">
+      <p><i>2/3 *</i> <br><span style="font-style: italic;">
+zu</span><i style="font-style: italic;">(nz)</i></p>
+      </td>
+      <td style="vertical-align: top;">
+      <p>Height where the Rayleigh damping starts (in m).&nbsp; </p>
+      <p>With 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
+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 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
+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
+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>
+A successful operation of this parameter requires additional
+modifications in the <span style="font-weight: bold;">mrun</span>-call
+for the respective run (see <a href="chapter_3.3.html">chapter
+3.3</a>).<br>
+      </p>
+      <p>The choice of <b>restart_time</b> 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
+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>
+the
+corresponding vertical grid point index/indices k of the requested
+cross section(s). The exact location (height level) of the cross
+section depends on the variable for which the output is made: zu(k) for
+scalars and horizontal velocities, zw(k) for the vertical velocity.
+Information about the exact location of the cross section is contained
+in the NetCDF output file (if the default NetCDF output is switched on;
+see <a href="#data_output_format">data_output_format</a>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
+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
+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
+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
+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>
+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>),
+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
+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
+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>
+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
+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
+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
+set <i>true</i> (see <a href="chapter_3.3.html">chapter
+3.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
+integration has finished (e.g. writing of binary data for the restart
+run, carrying out output commands, copying of local files to their
+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,
+it depends on
+the number of grid points used. If its value is selected too small,
+then the
+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
+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
+(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
+4.5.2</a>.</p>
+      </td>
+    </tr>
+    
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
+      </td>
+      <td style="vertical-align: top;">R</td>
+      <td style="vertical-align: top;"><i>zu(nzt+1) (model top)</i></td>
+      <td style="vertical-align: top;">
+      <p>Height level up to which horizontally averaged profiles are to
+be
+plotted with <span style="font-weight: bold;">profil</span> (in
+m).&nbsp; </p>
+      <p>This parameter only applies for &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
+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>
+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
+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
+(<a href="#data_output_pr">data_output_pr</a>)
+when plotted with the plot software <span style="font-weight: bold;">profil</span>,
+if a normalization for the vertical axis is selected
+(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 =
+1.5* z<sub>i </sub>are plotted.</p>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">
+      <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
+      </td>
+      <td style="vertical-align: top;">R<br>
+      </td>
+      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br>
+      </td>
+      <td style="vertical-align: top;">
+      <p>Height level up to which 2d cross sections are to be plotted
+with <span style="font-weight: bold;">iso2d</span>
+(in m).&nbsp; </p>
+      <p>This parameter only applies for &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
+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
+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 level up to which the section is visualized can later be changed by
+manually editing the
+file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>
+or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</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
+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;
+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
+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
+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
+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
+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,
+2877-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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+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
+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.
+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.
+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.
+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>
+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.
+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
+particles are weightless and transported passively with the resolved
+scale flow.
+In case of <span style="font-weight: bold;">density_ratio</span> /=
+0.0 particles have a mass and hence inertia so that their velocity
+deviates more or less from the velocity of the surrounding flow.
+Particle velocity is calculated analytically and depends on (besides
+the density ratio and the current velocity difference between particles
+and surrounding fluid) the
+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
+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
+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
+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
+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>),
+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
+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
+4.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>. All
+particles are displayed with this same size.<br>
+      </p>
+      <p>Alternatively, 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
+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>
+
+
+
+
+
+
+
+
+
+
+
+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
+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>
+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>
+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
+of tail
+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
+length of
+these
+tails is determined by the value of <b>maximum_number_of_tailpoints</b>
+and by the minimum distance between each of the adjoining
+tailpoints,&nbsp; which can be set by <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.
+Additionally, it can be determined that the temporal displacement
+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
+particle tail and the current position of the particle becomes larger
+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
+the particle tail do not exceed the value given by <b>maximum_number_of_tailpoints</b>,
+then the length the particle tails is a measure for the distance the
+particle travelled along during the time interval defined via <b>maximum_tailpoint_age</b>,
+i.e. for the
+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
+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
+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>
+A suitable choice of <b>minimum_tailpoint_distance</b>
+&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>
+should be chosen in a way that the visualized particle
+tails still appear as smooth lines. Example: with a model domain of
+1000 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>,
+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
+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>
+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
+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
+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>
+
+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
+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
+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>,
+and<a href="#pdz">
+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
+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
+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
+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
+in a restart run particle transport is switched on for the
+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>
+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
+velocities are calculated from the resolved and subgrid-scale TKE using
+the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
+61,
+2877-2887). When using this method, the timestep for the advancement of
+the particles is limited by the so-called Lagrangian time scale. This
+may be smaller than the current LES timestep so that several particle
+(sub-) timesteps have to be carried out within one LES timestep. In
+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>.
+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>
+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
+informations</span> (e.g. the total number of particles used, the
+number of particles exchanged between the PEs, etc.) which may be used
+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>
+&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
+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
+(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
+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>,
+2*<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
+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
+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).
+Apart from the default, it is only allowed to assign <span style="font-style: italic;">'/dev/null'</span> (which
+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
+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>
+software is transferred using
+a special transmission protocol to a so-called streaming server, which
+is able to continuously transfer visualization data with a
+high transmission rate.&nbsp; <br>
+Additionally, with this output mode a
+set of files is generated automatically
+within a directory on the streaming server (beside the visualization
+data e.g. some html-files) which can be used to
+visualize the data via an internet-browser plugin. Host
+(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>
+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>
+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
+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
+to be created by the <span style="font-weight: bold;">dvrp</span>
+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>
+(cross sections), and <span style="font-style: italic;">'particles'</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>,
+'slicer1',
+'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
+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
+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>,
+'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
+horizontal cross section of u and
+a vertical cross section (xz) of w is created. For locations of the
+cross sections see <a href="#data_output">data_output</a>.
+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
+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
+4.5.7</a>.<br>
+      </p>
+      <b>Note:</b><br>
+The declaration color charts to be
+used still have to be given "manually" in subroutine <span style="font-family: monospace;">user_dvrp_coltab</span> (file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;
+      <br>
+A change of particle colors and/or particle diameters (e.g. 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
+of values to which a color table has to be mapped (units of the
+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
+quantities to which the colortable in use has to be mapped. If e.g. a
+temperature slice shall be displayed, the colortable defines colors
+from blue to red, and <span style="font-weight: bold;">slicer_range_limits_dvrp</span>
+= 290.0, 305.0 then areas with temperature of 290 K are displayed in
+dark blue and those with 305.0 are displayed in dark red. Temperatures
+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>
+Up to ten different ranges can be assigned in case that more than one
+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
+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
+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
+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
+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
+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
+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>
+</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
+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
+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
+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
+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
+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
+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:
+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>),
+the spectral coefficients for the further heighs can be found in the
+subsequent columns. </font>The order
+of the data in the file follows the order used in the assignment for <b>data_output_sp</b>
+(<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
+the data,
+PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a>
+and <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_Y_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>.
+Spectra can be directly plotted with <span style="font-weight: bold;">profil</span>
+using the data and the corresponding parameter file. The
+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
+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
+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
+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
+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
+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
+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
+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>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.3.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.3.html	(revision 5)
@@ -0,0 +1,71 @@
+<!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.3</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041013;13364831">
+  <meta name="CHANGED" content="20041015;15380006">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style></head>
+
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 200%;">4.3 User-defined parameters</h3>
+<table style="width: 100%;" border="1" cellpadding="2" cellspacing="2">
+  <tbody>
+    <tr valign="top">
+      <td>
+      <p><font size="4"><b>Parameter name</b></font></p>
+      </td>
+      <td>
+      <p><font size="4"><b>Type</b></font></p>
+      </td>
+      <td>
+      <p><b><font size="4">Default</font></b>&nbsp; <br>
+      <b><font size="4">value</font></b></p>
+      </td>
+      <td>
+      <p><font size="4"><b>Explanation</b></font></p>
+      </td>
+    </tr>
+    <tr><td style="vertical-align: top;"><a name="data_output_user"></a><span style="font-weight: bold;">data_output_user</span></td><td style="vertical-align: top;">C * 10 (100)</td><td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span></td><td style="vertical-align: top;">User defined quantities for which 2d cross section and/or 3d volume data are to be output.<br><br>Beside the PALM standard output quantities (which can be selected via parameter <a href="chapter_4.2.html#data_output">data_output</a>),
+the user can define (without any restriction) additional output
+quantities (e.g. the temperature variance, etc.). Each of these
+quantities has to be given a unique identifier (string) which must be
+different from the strings defining the standard output quantities (see
+list from the description of <a href="chapter_4.2.html#data_output">data_output</a>). Data output can be switched on by assigning the respective strings to <span style="font-weight: bold;">data_output_user</span>.<br><br>The user has to calculate/provide the respective data array(s) by appropriately extending the user interface (see <a href="chapter_3.5.4.html">3.5.4</a>).<br><br>For
+further steering of the user defined output (output times, cross
+section levels, time averaging, etc.), the steering parameters for <a href="chapter_4.2.html#data_output">data_output</a> apply accordingly.<br><br><span style="font-weight: bold;">Example:</span><br>If the user defined output quantity is the temperature variance and if the user has chosen the string <span style="font-style: italic;">'pt2'</span> as an identifier for this quantity, then output of horizontal cross sections can be selected by assigning <span style="font-weight: bold;">data_output_user</span> = <span style="font-style: italic;">'pt2_xy'</span>.</td></tr><tr valign="top">
+      <td>
+      <p><b><a name="region"></a>region</b></p>
+      </td>
+      <td>
+      <p>C*40 (0:9)</p>
+      </td>
+      <td>
+      <p>&nbsp;</p>
+      </td>
+      <td>
+      <p>Name(s) of the subdomain(s) defined by the user.&nbsp; </p>
+      <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>)
+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>
+(0)).</p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<p style="line-height: 200%;">&nbsp; <br>
+&nbsp; </p>
+<hr>
+<p><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.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.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><span style="font-style: italic;">Last change:</span> 22/03/06
+(SR)&nbsp;</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.4.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.4.html	(revision 5)
@@ -0,0 +1,150 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html><head>
+  <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE">
+  
+  <title>PALM chapter 4.4</title><meta content="StarOffice 7  (Win32)" name="GENERATOR">
+  <meta content="Siegfried Raasch" name="AUTHOR">
+  <meta content="20041013;13430732" name="CREATED">
+  <meta content="20041117;11162734" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style></head>
+
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">4.4 Example of a minimum parameter set</h3>
+<p style="line-height: 100%;">In this chapter a brief, simple and
+complete parameter set is described, which can be used to carry out a
+model run. The presented example is available via <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">example
+file</a> and can be used (together with the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">configuration
+file</a> described in <a href="chapter_3.2.html">chapter
+3.2)</a> for the execution of a simple model run. </p>
+<p style="line-height: 100%;">This run simulates a quasi-stationary,
+convective, atmospheric boundary layer with&nbsp; <font color="#000000">zero
+mean horizontal
+wind.</font> For evaluation purposes, cross sections and horizontally averaged vertical
+profiles of typical boundary layer variables
+are output at the end of the run. The run shall be carried out in
+batch mode on the IBM Regatta "hanni" of the HLRN.</p>
+<p style="line-height: 100%;">The parameter file necessary to carry
+out a run must be provided to the model as an input file under the
+local name <a href="chapter_3.4.html#PARIN">PARIN</a>
+and has the following contents:</p>
+<pre style="line-height: 100%;">&amp;inipar  <a href="chapter_4.1.html#nx">nx</a> = <span style="font-style: italic;">39</span>, <a href="chapter_4.1.html#ny">ny</a> = <span style="font-style: italic;">39</span>, <a href="chapter_4.1.html#nz">nz</a> = <span style="font-style: italic;">40</span>,<br>         <a href="chapter_4.1.html#dx">dx</a> = <span style="font-style: italic;">50.0</span>, <a href="chapter_4.1.html#dy">dy</a> = <span style="font-style: italic;">50.0</span>, <a href="chapter_4.1.html#dz">dz</a> = <span style="font-style: italic;">50.0</span>,<br>         <a href="chapter_4.1.html#dz_stretch_level">dz_stretch_level</a> = <span style="font-style: italic;">1200.0</span>,<br>         <a href="chapter_4.1.html#fft_method">fft_method</a> = <span style="font-style: italic;">'temperton-algorithm'</span>,<br>         <a href="chapter_4.1.html#initializing_actions">initializing_actions</a> = <span style="font-style: italic;">'set_constant_profiles'</span>,<br>         <a href="chapter_4.1.html#ug_surface">ug_surface</a> = <span style="font-style: italic;">0.0</span>, <a href="chapter_4.1.html#vg_surface">vg_surface</a> = <span style="font-style: italic;">0.0</span>,<br>         <a href="chapter_4.1.html#pt_vertical_gradient">pt_vertical_gradient</a> = <span style="font-style: italic;">0.0</span>, <span style="font-style: italic;">1.0</span>,<br>         <a href="chapter_4.1.html#pt_vertical_gradient_level">pt_vertical_gradient_level</a> = <span style="font-style: italic;">0.0</span>, <span style="font-style: italic;">800.0</span>,<br>         <a href="chapter_4.1.html#surface_heatflux">surface_heatflux</a> = <span style="font-style: italic;">0.1</span>, <a href="chapter_4.1.html#bc_pt_b">bc_pt_b</a> = <span style="font-style: italic;">'neumann'</span>,/<br><br>&amp;d3par   <a href="chapter_4.2.html#end_time">end_time</a> = <span style="font-style: italic;">3600.0</span>,<br>         <a href="chapter_4.2.html#create_disturbances">create_disturbances</a> = <span style="font-style: italic;">.T.</span>,<br>         <a href="chapter_4.2.html#dt_disturb">dt_disturb</a> = <span style="font-style: italic;">150.0</span>, <a href="chapter_4.2.html#disturbance_energy_limit">disturbance_energy_limit</a> = <span style="font-style: italic;">0.01</span>,<br>         <a href="chapter_4.2.html#dt_run_control">dt_run_control</a> = <span style="font-style: italic;">0.0</span>,<br>         <a href="chapter_4.2.html#data_output">data_output</a> = <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'w_xz'</span>, <span style="font-style: italic;">'w_xz_av'</span>, <span style="font-style: italic;">'pt_xy'</span>, <span style="font-style: italic;">'pt_xz'</span>,<br>         <a href="chapter_4.2.html#dt_data_output">dt_data_output</a> = <span style="font-style: italic;">900.0</span>,<br>         <a href="chapter_4.2.html#dt_data_output_av">dt_data_output_av</a> = <span style="font-style: italic;">1800.0</span>,<br>         <a href="chapter_4.2.html#averaging_interval">averaging_interval</a> = <span style="font-style: italic;">900.0</span>,<br>         <a href="chapter_4.2.html#dt_averaging_input">dt_averaging_input</a> = <span style="font-style: italic;">10.0</span>,<br>         <a href="chapter_4.2.html#section_xy">section_xy</a> = <span style="font-style: italic;">2</span>, <span style="font-style: italic;">10</span>, <a href="chapter_4.2.html#section_xz">section_xz</a> = <span style="font-style: italic;">20</span>,<br>         <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a> = <span style="font-style: italic;">.F.</span>,<br>         <a href="chapter_4.2.html#dt_dopr">dt_dopr</a> = <span style="font-style: italic;">900.0</span>, <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a> = <span style="font-style: italic;">600.0</span>,<br>         <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a> = <span style="font-style: italic;">10.0</span>,<br>         <a href="chapter_4.2.html#data_output_pr">data_output_pr</a> = <span style="font-style: italic;">'#pt'</span>, <span style="font-style: italic;">'w&rdquo;pt&rdquo;'</span>, <span style="font-style: italic;">'w*pt*'</span>, <span style="font-style: italic;">'wpt'</span>, <span style="font-style: italic;">'w*2'</span>, <span style="font-style: italic;">'pt*2'</span>,<br>         <a href="chapter_4.2.html#cross_profiles">cross_profiles</a> = <span style="font-style: italic;">' pt '</span>, <span style="font-style: italic;">' w"pt" w*pt* wpt '</span>, <span style="font-style: italic;">' w*2 '</span>, <span style="font-style: italic;">' pt*2 '</span>,<br>         <a href="chapter_4.2.html#cross_xtext">cross_xtext</a> = <span style="font-style: italic;">'pot. temperature in K'</span>,<br>                       <span style="font-style: italic;">'heat flux in K ms&gt;-&gt;1'</span>,<br>                       <span style="font-style: italic;">'velocity variance in m&gt;2s&gt;-&gt;2'</span>,<br>                       <span style="font-style: italic;">'temperature variance in K&gt;2'</span>,<br>         <a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a> = <span style="font-style: italic;">1500.0</span>,   /</pre>
+<p style="line-height: 100%;"><br>
+<br>
+</p>
+<p style="line-height: 100%;">The initialization parameters (<tt><font style="font-size: 10pt;" size="2">&amp;inipar</font></tt>)
+are located at the beginning of the file. For analysis of a
+convective boundary layer of approx. 1000 m thickness the horizontal
+size of the model domain should amount to at least 2 km x 2 km. In
+order to resolve the convective structures a grid spacing of <b>dx</b>
+=
+<b>dy</b> = <b>dz</b> = <i>50 m</i> is enough, since the typical
+diameter of convective plumes is more than 100 m. Thereby the
+upper array index in the two horizontal directions needs to be <b>nx</b>
+= <b>ny</b> = <i>39</i>. <font color="#000000">Since in
+each case the lower array index has the value 0, 40 grid points are
+used along both horizontal directions.</font> In the vertical direction
+the domain must be high enough to include the entrainment processes at
+the top of the boundary layer as well as the propagation of gravity
+waves, which were stimulated by
+the convection. However, in the stably stratified region the grid
+resolution has not necessarily to be as high as within the boundary
+layer. This can be obtained by a vertical stretching of the grid
+starting
+from 1200 m via <b>dz_stretch_level</b> = <i>1200.0 m.</i> This saves
+grid points and computing time. <font color="#800000">T</font><font color="#000000">he
+upper boundary of the model is located at (see </font><a href="chapter_4.1.html#dz_stretch_factor"><font color="#000000">dz_stretch_factor</font></a><font color="#000000">)
+&hellip; m (computed by the model)</font>.</p><p style="line-height: 100%;">Fast Fourier transformations are calculated using the Temperton-algorithm, which -on the IBM Regatta- is faster than the default system-specific algorithm (from IBM essl library).</p><p style="line-height: 100%;">The initial profiles for
+wind and temperature can be assigned via <b>initializing_actions</b>
+= <span style="font-style: italic;">'set_constant_profiles'</span>.
+The wind speed, constant with
+height, amounts to <b>ug_surface</b> = <b>vg_surface</b> = <i>0.0 m/s</i>. In order
+to allow for a fast onset of convection, a neutral stratified layer up
+to z
+= 800 m capped by an inversion with dtheta/dz = 1K/100 m is given:
+<b>pt_vertical_gradient</b> = <i>0.0, 1.0</i>,
+<b>pt_vertical_gradient_level</b> = <i>0.0, 800.0.</i> The surface
+temperature, which by default amounts to 300 K, provides the fixed
+point for the temperature profile (see <a href="chapter_4.1.html#pt_surface">pt_surface</a>).
+Convection is driven by a given, near-surface sensible heat flux via <b>surface_heatflux</b>
+= <i>0.1 K m/s.</i> A given surface sensible heta flux requires the
+bottom boundary condition for potential temperature to be <b>bc_pt_b</b>
+=
+<span style="font-style: italic;">'neumann'</span> . Thus
+all initialization parameters are determined. These can not be
+changed during the run (also not for restart runs). </p>
+<p style="line-height: 100%;">Now the run parameters (<tt><font style="font-size: 10pt;" size="2">&amp;d3par</font></tt>)
+must be specified. To produce a quasi stationary boundary layer the
+simulated time should be at least one hour, i.e. <b>end_time</b> = <i>3600
+s.</i> To stimulate convection, the initially homogeneous (zero) wind
+field must be disturbed (<b>create_disturbances</b> = <i>.T.</i>).
+These perturbations should be repeated in a temporal interval of
+<b>dt_disturb</b> = <i>150.0 s</i> until the energy of the
+perturbations exceeds the value <b>disturbance_energy_limit</b> = 0.<i>01
+m<sup>2</sup>/s<sup>2</sup></i>. After each time step run time
+informations (e.g. size of the timestep, maximum velocities, etc.) are
+to be written to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
+(<b>dt_run_control</b> = <i>0.0 s</i>).</p><p style="line-height: 100%;">Instantaneous cross section data of vertical velocity (<span style="font-style: italic;">w</span>) and potential temperature (<span style="font-style: italic;">pt</span>) are to be output for horizontal (<span style="font-style: italic;">xy</span>) and vertical (<span style="font-style: italic;">xz</span>) cross sections, and additionally, time averaged (<span style="font-style: italic;">av</span>) vertical cross section data are to be output for the vertical velocity: <span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'w_xz'</span>, <span style="font-style: italic;">'w_xz_av'</span>, <span style="font-style: italic;">'pt_xy'</span>, <span style="font-style: italic;">'pt_xz'</span>. Output of instantaneous (time averaged) data is done after each 900 (1800)s: <span style="font-weight: bold;">dt_data_output</span> = <span style="font-style: italic;">900.0</span>, <span style="font-weight: bold;">dt_data_output_av</span> = <span style="font-style: italic;">1800.0</span>. The averaged data are time averaged over the last 900.0 s, where the temporal interval of data entering the average is 10 s: <span style="font-weight: bold;">averaging_interval</span> = <span style="font-style: italic;">900.0</span>, <span style="font-weight: bold;">dt_averaging_input</span> = <span style="font-style: italic;">10.0</span>.
+Horizontal cross sections are output for vertical levels with grid
+index k=2 and k=10, vertical cross sections are output for index j=20: <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">2</span>, <span style="font-style: italic;">10</span>, <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">20</span>. For runs on more than one processor, cross section data are collected and output on PE0: <span style="font-weight: bold;">data_output_2d_on_each_pe</span> = <span style="font-style: italic;">.F.</span>.</p><p style="line-height: 100%;">Output
+of vertical profiles is to be done after each 900 s. The profiles shall
+be temporally averaged<font color="#000000"> over the last <font color="#000000">600 </font>seconds, </font>whereby
+the temporal interval of the profiles entering the average has to be
+10 s: <b>dt_dopr</b> = <i>900.0 s</i>, <b>averaging_interval_pr</b> =
+<i>600.0 s</i>, <b>dt_averaging_input_pr</b> = <i>10.0 s.</i> The temperature
+profile including the initial temperature profile (therefore <span style="font-style: italic;">'#pt'</span>),
+the subgrid scale, resolved and total vertical sensible heat flux as
+well as the variances of the vertical velocity and the potential
+temperature are to be output:&nbsp; <b>data_output_pr</b> = <span style="font-style: italic;">'#pt'</span><i>, 'w"pt&rdquo;',
+'w*pt*', 'wpt', 'w*2', 'pt*2'</i>.</p><p style="line-height: 100%;">If the data output format for graphic software <span style="font-weight: bold;">profil</span> is selected (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>), the temperature
+profile and the individual variances are to be drawn into independent
+coordinate systems, and in contrast to this all heat flux profiles are to
+be
+drawn into the same system: <b>cross_profiles</b> = <span style="font-style: italic;">'pt'</span><i>,
+'w"pt"w*pt*wpt', 'w*2', 'pt*2'</i>. The legend of the x
+axes of these systems is set to <b>cross_xtext</b>= <i>'pot.
+temperature in K', 'heat flux in K ms&gt;-&gt;1', 'velocity variance
+in m&gt;2s&gt;-&gt;2', 'temperature variance in K&gt;2'</i>.
+The profiles are to be drawn up to a height level of <b>z_max_do1d</b>
+=
+<i>1500.0 m</i>. </p>
+<p style="line-height: 100%;">Before starting the mo<font color="#000000">del
+on the parallel computer, the number of processing elements must be
+specified.</font> Since relatively few grid points are used for
+this run, choosing of e.g. 8 PEs is sufficient. By default, a 1d domain
+decomposition along x is used on the IBM-Regatta, which means that a
+virtual processor topology (grid) of 8*1 (x*y) is used. (<span style="font-weight: bold;">Note:</span> the user may adjust this
+default domain decomposition with the help of the parameters <a href="chapter_4.1.html#npex">npex</a>
+and <a href="chapter_4.1.html#npey">npey</a>).
+</p>
+<p style="line-height: 100%;">Provided that the parameters
+file described above are set within the file </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/example/INPUT/example_p3d</font></pre>
+</ul>
+<p style="line-height: 100%;">and that the conditions mentioned in the
+first sections of <a href="chapter_3.2.html">chapter
+3.2</a> are met, the model run can be started with the command </p>
+<p style="line-height: 100%;"><font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2">mrun
+-d example -h ibmh -K parallel -X 8 -T 8 -t 1800 -q cdev -r &ldquo;d3# xy# xz# pr#&rdquo;</font></font></p>
+<p style="line-height: 100%;">The output files will appear in the
+directories </p>
+<blockquote style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/example/MONITORING</font></tt><font style="font-size: 10pt;" size="2"><br>
+  </font><tt><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/example/OUTPUT
+,</font></tt></blockquote>
+<p style="line-height: 100%;">while the job protocol will appear in
+directory <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">job_queue</font></font></tt>.
+<br>
+&nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.3.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.5.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+<p style="line-height: 100%;"><i>Last change:&nbsp; 13/04/06</i> (SR)
+<br>
+&nbsp; <br>
+&nbsp; </p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.1.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.1.html	(revision 5)
@@ -0,0 +1,330 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html><head>
+<meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 4.5.1</title> <meta content="StarOffice 7 (Win32)" name="GENERATOR"> <meta content="Siegfried Raasch" name="AUTHOR"> <meta content="20041022;12155949" name="CREATED"> <meta content="20041117;11232134" name="CHANGED"> <meta content="parallel LES model" name="KEYWORDS"> <style>
+<!--
+@page { size: 21cm 29.7cm }
+-->
+</style></head>
+<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.1
+NetCDF data output&nbsp;<span style="color: rgb(255, 0, 0);"></span></font></h4>
+<p style="line-height: 100%;">The standard data output of
+PALM is NetCDF (<span style="font-weight: bold;">Net</span>work
+<span style="font-weight: bold;">C</span>ommon <span style="font-weight: bold;">D</span>ata <span style="font-weight: bold;">F</span>orm). NetCDF is an
+interface to a library of data access functions<br>for
+storing and retrieving data in the form of arrays. NetCDF is an
+abstraction that supports a view of data as a collection of
+self-describing, <span style="font-weight: bold;">portable</span>
+objects that can be accessed through a simple interface (protable means
+that NetCDF data files can be read on any machine regardless of where they
+have been created). Array values may be accessed directly, without
+knowing details of how the data are stored. Auxiliary information about
+the data, such as what units are used, may be stored with the data.
+Generic utilities and application programs can access NetCDF datasets
+(files) and transform, combine, analyze, or display specified fields of
+the data, e.g. the contents of a NetCDF dataset can be viewed using the
+command <span style="font-family: monospace;">ncdump</span>
+(see <a href="#ncdump">further below</a>).
+Many (public domain) graphic software has built in interfaces to read
+NetCDF datasets (e.g. <span style="font-weight: bold;">ferret</span> or <span style="font-weight: bold;">NCL</span>). The complete NetCDF documentation
+is available from the <a href="http://www.unidata.ucar.edu/packages/netcdf/docs.html">NetCDF
+homepage</a>. The NetCDF tutorial for FORTRAN90 can also be found
+on <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/manual/netcdf/netcdf-3_f90_tutorial.pdf">our
+web server</a>.</p><p style="line-height: 100%;">The
+output format of PALM data is determined by the runtime-parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
+(<span style="font-weight: bold;">data_output_format</span>
+= <span style="font-style: italic;">'netcdf'</span>,
+by default). For historical reasons, some alternative formats can be
+selected (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>).
+The accuracy of the NetCDF output data can be set with parameter <a href="chapter_4.1.html#netcdf_precision">netcdf_precision</a>.
+By default, data have single (4 byte) precision. Also by default,
+NetCDF datasets (files) are not allowed to be larger than 2 GByte.
+Larger datasets can be created&nbsp;by setting <a href="chapter_4.2.html#netcdf_64bit">netcdf_64bit</a>
+= <span style="font-style: italic;">.TRUE.</span>.
+These files then have the so-called 64bit-offset format. However,
+currently, many of the existing application programs may not support
+this 64-bit offset format.<br></p>PALM allows the output of
+various
+data (e.g. cross sections, vertical profiles, timeseries, etc.) into
+different files. The following table gives an overview about the
+different kind of NetCDF output data offered by PALM. Beside the local
+names of the files, the table also lists the minimum parameter settings which
+are necessary to switch on the output, as well as the parameters to be
+used to control the output.<br><br><table style="text-align: left; width: 750px; height: 226px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td align="left" valign="top"><span style="font-weight: bold;">kind of data</span></td><td align="left" valign="top"><span style="font-weight: bold;">local filename</span></td><td align="left" valign="top"><span style="font-weight: bold;">parameter settings necessary to
+switch on output</span></td><td align="left" valign="top"><span style="font-weight: bold;">further
+parameters for output control</span></td></tr><tr><td align="left" valign="top">vertical profiles</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output_pr">data_output_pr</a>,
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>)</td><td align="left" valign="top"><a href="chapter_4.2.html#averaging_interval">averaging_interval</a>,
+(or <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>),
+<a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.2.html#dt_averaging_input">dt_averaging_input</a>,
+<a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>,
+<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.2.html#data_output_sp">data_output_sp</a>,
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
+<a href="chapter_4.2.html#spectra_direction">spectra_direction</a></td><td align="left" valign="top"><a href="chapter_4.2.html#averaging_interval">averaging_interval</a>&nbsp;(or
+<a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a>),
+<a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_dosp">skip_time_dosp)</a></td></tr><tr><td align="left" valign="top">2d cross section (xy)</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_xy</a>),
+<a href="chapter_4.2.html#section_xy">section_xy</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#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>,
+<a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_do2d_xy">skip_time_do2d_xy</a>)</td></tr><tr><td align="left" valign="top">2d cross section (xy),
+time-averaged</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_data_output_av">dt_data_output_av</a>&nbsp;or
+<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_xy</a>),
+<a href="chapter_4.2.html#section_xy">section_xy</a></td><td align="left" valign="top"><a href="chapter_4.2.html#averaging_interval">averaging_interval</a>,
+<a href="chapter_4.2.html#dt_averaging_input">dt_averaging_input</a>,
+<a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>,
+<a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_data_output_av">skip_time_data_output_av</a>,
+or <a href="chapter_4.2.html#skip_time_do2d_xy">skip_time_do2d_xy</a>)</td></tr><tr><td align="left" valign="top">2d cross section (xz)</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_do2d_xz">dt_do2d_xz</a>),
+<a href="chapter_4.2.html#section_xz">section_xz</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#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>,
+<a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_do2d_xz">skip_time_do2d_xz</a>)</td></tr><tr><td align="left" valign="top">2d cross section (xz),
+time-averaged</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_data_output_av">dt_data_output_av</a>&nbsp;or
+<a href="chapter_4.2.html#dt_do2d_xz">dt_do2d_xz</a>),
+<a href="chapter_4.2.html#section_xz">section_xz</a></td><td align="left" valign="top"><a href="chapter_4.2.html#averaging_interval">averaging_interval</a>,
+<a href="chapter_4.2.html#dt_averaging_input">dt_averaging_input</a>,
+<a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>,
+<a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_data_output_av">skip_time_data_output_av</a>,
+or <a href="chapter_4.2.html#skip_time_do2d_xz">skip_time_do2d_xz</a>)</td></tr><tr><td align="left" valign="top">2d cross section (yz)</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>),
+<a href="chapter_4.2.html#section_yz">section_yz</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#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>,
+<a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_do2d_yz">skip_time_do2d_yz</a>)</td></tr><tr><td align="left" valign="top">2d cross section (yz),
+time-averaged</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_data_output_av">dt_data_output_av</a>&nbsp;or
+<a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>),
+<a href="chapter_4.2.html#section_yz">section_yz</a></td><td align="left" valign="top"><a href="chapter_4.2.html#averaging_interval">averaging_interval</a>,
+<a href="chapter_4.2.html#dt_averaging_input">dt_averaging_input</a>,
+<a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>,
+<a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>,
+<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_data_output_av">skip_time_data_output_av</a>,
+or <a href="chapter_4.2.html#skip_time_do2d_yz">skip_time_do2d_yz</a>)</td></tr><tr><td align="left" valign="top">3d volume</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_do3d">dt_do3d</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#do3d_at_begin">do3d_at_begin</a>,
+<a href="chapter_4.2.html#nz_do3d">nz_do3d</a>, <a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_do3d">skip_time_do3d</a>)</td></tr><tr><td align="left" valign="top">3d volume, time-averaged</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output">data_output</a>
+(or <a href="chapter_4.3.html#data_output_user">data_output_user</a>),
+<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+(or <a href="chapter_4.2.html#dt_data_output_av">dt_data_output_av</a>&nbsp;or
+<a href="chapter_4.2.html#dt_do3d">dt_do3d</a>)</td><td align="left" valign="top"><a href="chapter_4.2.html#averaging_interval">averaging_interval</a>,
+<a href="chapter_4.2.html#dt_averaging_input">dt_averaging_input</a>,
+<a href="chapter_4.2.html#data_output_format">data_output_format</a>,&nbsp;<a href="chapter_4.2.html#do3d_at_begin">do3d_at_begin</a>,
+<a href="chapter_4.2.html#nz_do3d">nz_do3d</a>, <a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_data_output_av">skip_time_data_output_av</a>,
+or <a href="chapter_4.2.html#skip_time_do3d">skip_time_do3d</a>)</td></tr><tr><td align="undefined" valign="undefined">particle timeseries</td><td style="vertical-align: top;"><a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a></td><td style="vertical-align: top;"><a href="chapter_4.2.html#dt_data_output">dt_data_output</a> (or <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>)</td><td align="undefined" valign="undefined"></td></tr><tr><td align="left" valign="top">particle attributes</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_PRT_NETCDF">DATA_PRT_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a></td><td align="left" valign="top"></td></tr></tbody></table><br><br><span style="font-weight: bold;">Creating, contents and
+post-processing of a PALM NetCDF file</span><br><br>This
+section describes, step-by-step, the creation, storage, and
+post-processing of PALM NetCDF datasets considering the output of 2d
+horizontal (xy) cross sections as example. The parameter settings
+described below are those of the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">example
+parameter file</a> (see <a href="chapter_4.4.html">chapter
+4.4</a>) so this parameter file can be used to retrace the
+following explanations.<br><br><ol><li>Output
+of xy cross
+sections requires to set at least three parameters: first, the temporal
+interval of the output time (run parameter <a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
+or <a href="chapter_4.2.html#dt_do2d_xy"><u>dt_do2d_xy)</u></a><span style="text-decoration: none;">, second<span style="text-decoration: none;"></span>,
+the names of the quantities for which cross section output is wanted</span><span style="text-decoration: none;"><span style="text-decoration: none;"> (<a href="chapter_4.2.html#data_output">data_output</a></span></span>),
+and third, the position (height level given as gridpoint index) of the
+cross sections (<a href="chapter_4.2.html#section_xy">section_xy</a>).
+The string <span style="font-style: italic;">'_xy'</span>
+must be appended to the name strings assigned to <span style="font-weight: bold;">data_output</span> in
+either case. 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 cross sections are
+written at the time t=0; exceptions see <a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>).
+As an exception, the first output time can be set independently with
+parameter <a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
+(or <a href="chapter_4.2.html#skip_time_do2d_xy">skip_time_do2d_xy</a>).<br><br><span style="font-weight: bold;">Very important:</span><br>If
+no values have been assigned to <b>data_output</b> , <span style="font-weight: bold;">dt_data_output</span> (or <span style="font-weight: bold;">dt_do2d_xy</span>), and <b>section_xy</b>,
+or
+if the values given for <span style="font-weight: bold;">dt_data_output</span>
+(or <b>dt_do2d_xy</b>) or <span style="font-weight: bold;">skip_time_data_output</span>
+(or <span style="font-weight: bold;">skip_time_do2d_xy</span>)
+are
+larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>),
+<b>then there will be no output!<br><br></b>For
+output of time-averaged data, the string <span style="font-style: italic;">'_av'</span> has to be
+additionally appended to the respective name string (see <a href="chapter_4.2.html#data_output">data_output</a>).<br><br><br></li><li>
+<p style="line-height: 100%;">Instantaneous data are output in NetCDF
+format
+into the
+local file&nbsp;<a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>.
+This file must be linked with a permanent file by
+using a file connection statement in the <b>mrun</b>
+configuration
+file (see e.g. <a href="chapter_3.2.html">chapter
+3.2</a>). At the end of the run the local file is copied to this
+file. Such a statement can look like this:<br><br><span style="font-family: monospace;">&nbsp;
+&nbsp;DATA_2D_XY_NETCDF out:loc:tr&nbsp;&nbsp;xy#&nbsp;
+~/$fname/OUTPUT/$fname&nbsp; _xy nc &nbsp; .</span><br><br>If
+the respective <b>mrun</b> call is
+like<br><br><span style="font-family: monospace;">&nbsp;
+&nbsp;mrun -d&nbsp; test -r &ldquo;xy#&rdquo; ... </span><br style="font-family: monospace;"><br>then the local
+file <tt><font style="font-size: 10pt;" size="2">DATA_2D_XY_NETCDF</font></tt>
+is copied to the permanent file <tt><font style="font-size: 10pt;" size="2">~/test/OUTPUT/test/test_xy.nc</font>
+</tt>. However, the character string <span style="font-family: mon; font-style: italic;">'</span><tt style="font-style: italic;"><font style="font-size: 10pt;" size="2">xy#</font></tt><span style="font-style: italic;">'</span> activating the
+file connection statement (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> <span style="text-decoration: none;">If
+t</span>his 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.<br><br>The
+last (6th) column of the file connection statement, which defines the
+additional file suffix, should be the string <span style="font-style: italic;">'nc'</span>, because many
+application programs expect NetCDF files to have the file extension <span style="font-style: italic;">'.nc'</span>. (This
+additional suffix given in the 6th column is always put at the very end of the filename, even
+in case of cycle numbers.)<br><br>Time averaged data are output into local file&nbsp;<a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a> which requires an additional file connection statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp; DATA_2D_XY_AV_NETCDF out:loc:tr&nbsp; xy#&nbsp; ~/$fname/OUTPUT/$fname&nbsp; _xy_av nc&nbsp;&nbsp; .</span><br></p></li><li>With
+parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
+= <i>.T.</i>
+each PE outputs the data of its subdomain
+not directly to the NetCDF file but to a separate file with the name
+PLOT2D_XY_&lt;processor-Id&gt;,
+where &lt;processor-Id&gt; is a four digit number (e.g.
+PLOT2D_XY_0000). These files have FORTRAN binary format. After PALM has
+finished, their content is merged into the final local destination file
+DATA_2D_XY_NETCDF by the program <span style="font-family: monospace;">combine_plot_fields</span>.&nbsp;<span style="font-weight: bold;"></span>This is done by adding the following output command to the configuration file:<br><br><span style="font-family: monospace;">&nbsp; &nbsp;OC:[[$
+( echo $localhost | cut -c1-3 ) = imbh ]] &amp;&amp;
+combine_plot_fields.x &nbsp; &nbsp; .</span><br><br>Using
+this call, possibly existing
+files of the other cross sections (xz, yz) and of 3d volume data are
+also merged to their respective NetCDF files.&nbsp;The tool writes
+informative messages about the actions accomplished into the job
+protocol, even if no files were found (i.e. the output command
+may remain in the configuration file, even if no appropriate files
+are created during the simulation).&nbsp;<br><br><br></li><li><a name="ncdump"></a>The contents of a NetCDF dataset can
+be simply analyzed with the tool <span style="font-family: monospace;">ncdump</span>
+(which is part of the NetCDF software). It can be used to display the
+dimension (coordinate) names and lengths; variable names, types, and
+shapes; attribute names and values; and optionally,<br>the values
+of
+data for all variables or selected variables in a netCDF dataset. The
+file content (without displaying the gridpoint data of the quantities)
+can be displayed with the command<br><br><span style="font-family: monospace;">&nbsp; &nbsp;ncdump
+-c &lt;filename&gt; &nbsp; &nbsp; .</span><br><br>Usage
+of the <span style="font-family: monospace;">ncdump</span>
+command requires that the path to the NetCDF software is appropriately
+set. On the IMUK-Linux-cluster this path is set by default, on the
+HLRN-IBM-Regatta, the user has to execute the command<br><br><span style="font-family: monospace;">&nbsp; &nbsp;module
+load netcdf &nbsp; &nbsp; .</span><br><br>Please
+refer to the&nbsp;system documentation or system administrator on
+how
+to setup the correct NetCDF path on the respective host.<br><br>An
+example how to interpret the <span style="font-family: monospace;">ncdump</span>-output
+will be given <a href="#NetCDF_example">further below</a>.<br><br></li><li>There
+are several application programs which can be used for graphical
+display of NetCDF datasets. One of the easiest ways to display the PALM
+data is the <a style="font-family: monospace;" href="http://ferret.wrc.noaa.gov/Ferret/">ferret</a>
+graphical user interface (GUI). On the IMUK-Linux-cluster, this can be called by
+executing the command<br><br><span style="font-family: monospace;">&nbsp; &nbsp;ferret
+-gui &nbsp; &nbsp; .</span><br><br><span style="font-family: monospace;">ferret</span> is also
+available at <a href="http://www.hlrn.de/doc/ferret/index.html">HLRN</a>.
+Another possible tool is <span style="font-family: monospace;">ncview</span>,
+which is also available at HLRN (see the <a href="http://www.hlrn.de/doc/ncview/index.html">HLRN
+documentation</a>). Beside these general tools, the PALM group
+will develop a&nbsp;graphical interface based on <a href="http://www.ncl.ucar.edu/">NCL</a>
+(NCAR Command Language). This interface will be&nbsp;specially
+designed
+to display the PALM Data. A detailed documentation will be linked here
+as soon as available.<br><br><br></li><li><a name="netcdf_example_program"></a>One
+of the most flexible general ways for postprocessing NetCDF data
+is&nbsp;reading these data into a FORTRAN program. The&nbsp;<font color="#000000"></font><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/read_palm_netcdf_data.f90"><font color="#000080">example program</font></a> shows how to read 2d or 3d NetCDF datasets created by PALM. Compiling this program requires that the
+NetCDF library is installed (if neccessary, please ask your system
+administrator). Some compilation instructions are given in the header of the
+example program.<br><br><br></li><li>By
+default, each PALM job creates its own NetCDF files. If permanent files
+with respective filenames are already existing then new files with
+higher cycle numbers will be created. However, in case of a job chain,
+it is possible to extend the NetCDF datasets created by the initial
+run&nbsp;with data from the restart run(s). As a result, data of all
+output times of the complete job chain are contained in one file and
+the number of data files to be handled by the user may be reduced
+significantly.<br>To extend a NetCDF dataset (created by a previous run
+of a job chain) with data from the current run requires that this
+dataset must be provided as an INPUT file. This may be difficult in
+case that PALM is running on a remote host because typically the output
+data files from the previous run have been already transferred by <span style="font-weight: bold;">mrun</span> to the local workstation with a file connection statement like<br><br><span style="font-family: monospace;">&nbsp;
+&nbsp;DATA_2D_XY_NETCDF &nbsp;out:loc:tr&nbsp;&nbsp;xy#:xyf
+&nbsp;~/palm/current_version/JOBS/$fname/OUTPUT &nbsp;_xy&nbsp; nc</span><br><br>and thus they are not available on the remote host any more. <br>A
+workaround for solving this problem is to create an additional copy of
+the output file on the remote machine by adding the file connection
+statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp; DATA_2D_XY_NETCDF&nbsp; out:loc&nbsp; xy#:xyf&nbsp; ~/palm/current_version/JOBS/$fname/OUTPUT&nbsp; _xy&nbsp; nc</span><br><br>This additional copy can then be accessed from a restart job as an input file using the file connection statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp; DATA_2D_XY_NETCDF&nbsp; in:locopt&nbsp;&nbsp;xyf&nbsp; ~/palm/current_version/JOBS/$fname/OUTPUT&nbsp; _xy&nbsp; nc</span><br><br>Here the file attribut <span style="font-family: monospace;">locopt</span>
+(2nd column) guarantees that the job continues if a permanent file does
+not exist (e.g. in case of an initial run). Otherwise, the job would be
+aborted.<br>Although the dataset created by the last run of a job chain
+will contain data from all selected time levels of the complete job
+chain, the main disadvantage of this workaround is that the datasets
+created by the remaining jobs (with lower cycle numbers) still exist
+and may consume large disc space. They have to be deleted "by hand" by
+the user on the local machine as well as on the remote
+machine&nbsp;because they only contain redundant data from the earlier
+time levels which are already contained&nbsp;in the dataset created by
+the last job of the job chain.<br><br><span style="font-weight: bold;">Note:</span><br>Extension of PALM NetCDF datasets of 2d horizontal cross sections requires that parameters <a href="chapter_4.2.html#data-output">data_output</a> and <a href="chapter_4.2.html#section_xy">section_xy</a>&nbsp;
+for the restart runs are set identical to the initial run. In case of a
+value mismatch between initial and restart runs, a warning is issued in
+the job protocol file and the dataset will contain only data from those
+timelevels calculated within the restart run.<br>Similar restrictions apply for all other PALM NetCDF datasets (i.e. profiles, vertical cross sections, volume data, etc.).</li></ol><br>&nbsp;<br><span style="font-weight: bold;"><a name="NetCDF_example"></a>Example of a PALM NetCDF dataset</span><br><br>The
+NetCDF dataset described here contains data of instantaneous horizontal
+cross sections and has been created using the settings of the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">example
+parameter file</a> (see <a href="chapter_4.4.html">chapter
+4.4</a>),
+i.e. it contains section data of the w-velocity-component and of the
+potential temperature for vertical grid levels with index <span style="font-family: monospace;">k = 2</span> and <span style="font-family: monospace;">k = 10</span>, selected by the respective parameter settings <a href="chapter_4.2.html#data_output">data_output</a> = <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'pt_xy'</span>, and <a href="chapter_4.2.html#section_xy">section_xy</a> = <span style="font-style: italic;">2</span>, <span style="font-style: italic;">10</span>. Output has been created after every 900 s (<a href="chapter_4.2.html#dt_data_output">dt_data_output</a> = <span style="font-style: italic;">900.0</span>). Because of <a href="chapter_4.2.html#end_time">end_time</a> = <span style="font-style: italic;">3600.0</span>, the file contains data of 4 time levels (t = 900, 1800, 2700, 3600 s).<br>Supposed that the name of the NetCDF dataset is <span style="font-family: monospace;">example_xy.nc</span>, an analysis of the file contents using the command<br><br><span style="font-family: monospace;">&nbsp; &nbsp;ncdump -c example_xy.nc</span><br><br>will create the following output. The original ncdump output is displayed using <span style="font-family: monospace;">fixed spacing</span>, additional explanations are given in <span style="font-style: italic; font-family: monospace;">italian</span>.<br><br><div style="margin-left: 40px;"><span style="font-family: monospace;">netcdf&nbsp;example_xy { &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! filename</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">dimensions: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! 41 gridpoints along x and y, 4 timelevels</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; time = UNLIMITED ; // (4 currently) &nbsp; &nbsp;<span style="font-style: italic;">! unlimited means that&nbsp;additional time levels can be added (e.g. by</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp;<span style="font-style: italic;">! restart jobs)</span><br>&nbsp;&nbsp;&nbsp; zu_xy = 2 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! vertical dimension (2, because two cross sections are selected);</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; zw_xy = 2 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! there are two different vertical dimensions zu and zw because due</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; zu1_xy = 1 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! to the staggered grid the z-levels of variables are those of the</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+x = 41 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! u- or the w-component of the velocity</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; y = 41 ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">variables: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! precision, dimensions, and units of the variables</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double time(time) ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! the variables containing the time levels and grid point coordinates</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; time:units = "seconds" ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! have the same names as the respective dimensions</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double zu_xy(zu_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; zu_xy:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double zw_xy(zw_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; zw_xy:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double zu1_xy(zu1_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; zu1_xy:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double ind_z_xy(zu_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ind_z_xy:units = "gridpoints" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double x(x) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; x:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; double y(y) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; y:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; float w_xy(time, zw_xy, y, x) ; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! array of the vertical velocity; it has 4 dimensions: x and y,</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; w_xy:long_name = "w_xy" ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! because it is a horizontal cross section, zw_xy, which defines</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; w_xy:units = "m/s" ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! the vertical levels of the sections, and time, for the time levels</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; float pt_xy(time, zu_xy, y, x) ; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! array of the potential temperature, which is defined on the u-grid</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; pt_xy:long_name = "pt_xy" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; pt_xy:units = "K" ;</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">// global attributes:</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :Conventions = "COARDS" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; :title = "PALM&nbsp;&nbsp; 3.0&nbsp; run:
+example.00&nbsp; host: ibmh&nbsp; 13-04-06 15:12:43" ; &nbsp;<span style="font-style: italic;">! PALM run-identifier</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; :VAR_LIST = ";w_xy;pt_xy;" ; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! the list of output quantities contained in this dataset;</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp;<span style="font-style: italic;">! this global attribute can be used by FORTRAN programs to identify</span><br>&nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+&nbsp;<span style="font-style: italic;">! and read the quantities contained in the file</span><br>data:</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;time = 905.3, 1808.98, 2711.98, 3603.59 ; <span style="font-style: italic;">! values of the four time levels</span></span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;zu_xy = 75, 475 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! heights of the two selected cross sections (u-grid)</span></span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;zw_xy = 100, 500 ;</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;zu1_xy = 25 ;</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;x = 0, 50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, &nbsp; <span style="font-style: italic;">! x-coordinates of the gridpoints</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; 750, 800, 850, 900, 950, 1000, 1050, 1100, 1150, 1200, 1250, 1300, 1350, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; 1400, 1450, 1500, 1550, 1600, 1650, 1700, 1750, 1800, 1850, 1900, 1950, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; 2000 ;</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;y = 0, 50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 650, 700, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; 750, 800, 850, 900, 950, 1000, 1050, 1100, 1150, 1200, 1250, 1300, 1350, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; 1400, 1450, 1500, 1550, 1600, 1650, 1700, 1750, 1800, 1850, 1900, 1950, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp; 2000 ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">}</span><br></div><br>If the option <span style="font-family: monospace;">-c</span> is omitted in the <span style="font-family: monospace;">ncdump</span> call, then also the complete grid point data of all quantities are output to the terminal.<br><br>The &nbsp;<a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/read_palm_netcdf_data.f90"><font color="#000080">example program</font></a><span style="font-weight: bold;"></span> shows how to read this 2d
+horizontal cross section dataset from a FORTRAN program (<a href="#netcdf_example_program">see above</a>).<br><hr>
+<p style="line-height: 100%;"><br><font color="#000080"><font color="#000080"><a href="chapter_4.5.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.5.2.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" name="Grafik3" src="right.gif"></font></a></font></font></p>
+<p style="line-height: 100%;"><span style="font-style: italic;">Last
+change:</span> 08/02/07 (SR)&nbsp;</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.2.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.2.html	(revision 5)
@@ -0,0 +1,227 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+  <meta content="text/html; charset=windows-1252"
+ http-equiv="CONTENT-TYPE">
+  <title>PALM chapter 4.5.2</title>
+  <meta content="StarOffice 7  (Win32)" name="GENERATOR">
+  <meta content="Siegfried Raasch" name="AUTHOR">
+  <meta content="20041022;12155949" name="CREATED">
+  <meta content="20041117;11232134" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body lang="en-US" dir="ltr">
+<h4 style="line-height: 100%;"><font size="4">4.5.2 Plots of vertical
+profiles with profil</font></h4>
+<p style="line-height: 100%;">Output of vertical
+profile data is enabled by providing values for the run parameters <a
+ href="chapter_4.2.html#dt_dopr"><u>dt_dopr</u></a><span
+ style="text-decoration: none;">
+and </span><a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
+<span style="text-decoration: none;">which specify the temporal
+interval of the output times (in s) and the quantities for which output
+is to be made.</span> 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 profiles are
+written at the time t=0; exceptions see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
+By default, vertical profiles represent an instantaneous horizontal
+average of the
+total model domain at the respective output time. Temporal averaging
+can be initiated with
+the run parameter <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>.
+Beyond that, an output of profiles for user-defined subdomains is
+possible via the
+initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.</p>
+<p style="line-height: 100%;">Output of desired profiles (temperature,
+velocity, etc.) is steered with the run parameter <a
+ href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
+If this parameter is not set by the user, then, independently of the
+value of <b>dt_dopr</b>, there will be no output! PALM
+creates the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
+which must be linked with a permanent file (see e.g. <a
+ href="chapter_3.2.html">chapter
+3.2</a>) via a file connection statement in the <b>mrun</b>
+configuration file. 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 size="2"
+ style="font-size: 10pt;">PLOT1D_DATA   out:loc:tr   pr   ~/PLOT/$fname   _pr_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 size="2"
+ style="font-size: 10pt;">mrun -d test -r pr 
+</font></pre>
+</ul>
+<p style="line-height: 100%;">then the local f<span
+ style="text-decoration: none;">ile
+</span><tt><span style="text-decoration: none;"><font size="2"
+ style="font-size: 10pt;">PLOT1D_DATA</font></span></tt><span
+ style="text-decoration: none;"><font size="2" style="font-size: 10pt;">
+</font>is copied to the permanent file </span><tt><span
+ style="text-decoration: none;"><font size="2" style="font-size: 10pt;">~/PLOT/test/test_pr_in</font></span></tt><span
+ style="text-decoration: none;">.
+However, the character string <font size="2" style="font-size: 10pt;"></font></span><tt><span
+ style="text-decoration: none;"><font size="2" style="font-size: 10pt;">pr</font></span></tt><span
+ style="text-decoration: none;"><font size="2" style="font-size: 10pt;"></font>
+activating the file connection statement </span><span
+ style="text-decoration: none;">(see third column of the statement) </span><span
+ style="text-decoration: none;">must be given in the <b>mrun</b>
+call as argument of the
+option -r (and/or -o)<b>.</b> If t</span>his 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 created data file can be
+directly used as input file for the plot software <b>profil</b>.
+<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#PLOT1D_PAR">PLOT1D_PAR</a>
+and also needs a file connection statement, e.g.: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
+ style="font-size: 10pt;">PLOT1D_PAR out:loc:tr    pr ~/PLOT/$fname   _pr_par.</font></pre>
+</ul>
+<p style="line-height: 100%;">If you are in the directory
+<tt><font size="2" style="font-size: 10pt;">~/PLOT/test</font>,</tt>the
+data can be plotted by entering </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
+ style="font-size: 10pt;">profil -d test_pr_in -p test_pr_par</font></pre>
+</ul>
+<p style="line-height: 100%;">The default plot layout as
+specified in the parameter file is as follows: the profiles of the
+different quantities are plottet into
+one or more coordinate systems (panels). Every profile is plotted only
+once,
+however several profiles of different quantities can be plottet into
+the same panel. If case of this, the different quantities are
+marked by different styles of lines. Which variables
+are drawn into which coordinate system is specified by the user via
+the run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>.
+It is very important to note that only profiles are plottet, which are
+assigned to
+a coordinate system via <b>cross_profiles</b>. If a certain
+variable is selected by <b>data_output_pr</b> but not assigned to a coordinate
+system via <b>cross_profiles</b>, then the appropriate profile data
+are written to the file PLOT1D_DATA but they are not plotted! All
+panels for which data
+exist are plotted. For example, if only the profiles of the potential
+temperature are
+to be plottet in a panel but output of potential temperature is not set
+via
+<b>data_output_pr</b>, then the respective panel is not drawn
+(thus no 'empty' panels appear in the plot). The
+parameters <a href="chapter_4.2.html#profile_columns">profile_columns</a>
+and <a href="chapter_4.2.html#profile_rows">profile_rows</a>
+determine how the panels are arranged in columns and rows. The panels
+are plotted in the order given by <span style="font-weight: bold;">data_output_pr</span>
+starting in the top row from left to right.
+If the number of panels to be plotted is larger than the
+product <b>profile_columns</b> * <b>profile_rows</b>, then the plot
+is continued on a second page. </p>
+<p style="line-height: 100%;">During a model run output of profiles to
+file PLOT1D_DATA is usually carried out for several times (as
+determined by <span style="font-weight: bold;">dt_dopr</span>)<font
+ size="2" style="font-size: 10pt;">.</font>
+All of these profiles belonging to the same quantity are plotted in the
+same panel. The different output times are marked by different line
+colors. All profiles of a certain output time have the
+same color, even if they are plotted into different panels. Beyond
+that, a legend entry is made for each, containing the name of the
+respective quantity and the output time.
+This legend string is taken from file PLOT1D_DATA
+in which a comment line is placed ahead of each profile data. </p>
+<p style="line-height: 100%;">For 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>). If the profiles are additionally temporally averaged,
+each panel gets an appropriate sub-label (<span
+ style="font-style: italic;">'time
+averaged over
+ s'</span>). The axes labels of the x axes of the
+individual panels are specified with the run parameter
+<a href="chapter_4.2.html#cross_xtext">cross_xtext</a>,
+the y axes always have the label <span style="font-style: italic;">'height
+in m'</span>. For better
+comparison, the profiles can be normalized with respect to different
+quantities
+(see <a href="chapter_4.2.html#cross_normalized_x">cross_normalized_x</a>
+and <a href="chapter_4.2.html#cross_normalized_y">cross_normalized_y</a>).
+The respective normalization is noted in the axes label. </p>
+<p style="line-height: 100%;"><font color="#000000">As already
+mentioned, the profiles of a quantity
+for all output times are plotted into the same panel. This is not
+possible if a simulation needs restart runs, since the restart runs
+write the
+profile data to separate files (with appropriate cycle numbers) and
+create own parameter files. Thus by default profiles can only be drawn
+separately for each respective run. However there is a possibility to
+plot
+all profiles of a quantity in one plot, regardless of the number of
+restart runs. For this
+purpose the configuration file must be changed such that for restart
+runs the profile data are appended to already existing<font
+ color="#000000">
+data</font> (thus all data are output into one file). Then the
+configuration file has two entries for </font><tt><font color="#000000">PLOT1D_DATA</font></tt><font
+ color="#000000">:
+</font></p>
+<ul>
+  <pre style="line-height: 100%;"><font size="2"
+ style="font-size: 10pt;">PLOT1D_DATA out:loc:tr  pr# ~/PLOT/$fname _pr_in</font><br><font
+ size="2" style="font-size: 10pt;">PLOT1D_DATA out:loc:tra prf ~/PLOT/$fname _pr_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 size="2"
+ style="font-size: 10pt;">mrun - D test - r pr#
+</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 profile data.
+The file connection statement for the parameter file
+<font size="3">PLOT1D_PAR</font> has not changed, thus a new cycle of
+the respective permanent file is created for each run. To plot
+the combined data with the parameter file created by the last run of
+the job chain, the run parameter
+<a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
+= <i>.TRUE.</i> must be additionally set for the restart runs. If this
+is
+forgotten, the parameter file is useless and the data cannot
+be plotted. </p>
+<p style="line-height: 100%;">The default layout of the plots of
+vertical profiles 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). <br>
+</p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.html"><font
+ color="#000080"><img width="32" height="32" border="2" align="bottom"
+ name="Grafik1" src="left.gif"></font></a><a href="index.html"><font
+ color="#000080"><img width="32" height="32" border="2" align="bottom"
+ name="Grafik2" src="up.gif"></font></a><a href="chapter_4.5.3.html"><font
+ color="#000080"><img width="32" height="32" border="2" align="bottom"
+ name="Grafik3" src="right.gif"></font></a></font></font></p>
+<p style="line-height: 100%;"><span style="font-style: italic;">Last
+change:</span> 19/04/05 (SR)&nbsp;</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.5.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.3.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.3.html	(revision 5)
@@ -0,0 +1,184 @@
+<!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)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041026;14291096">
+  <meta name="CHANGED" content="20041117;11335481">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</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>.
+</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
+3.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>
Index: palm/trunk/DOC/app/chapter_4.5.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.4.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.4.html	(revision 5)
@@ -0,0 +1,200 @@
+<!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.4</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041027;10130843">
+  <meta name="CHANGED" content="20041117;11420847">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h4 style="line-height: 100%;"><font size="4">4.5.4 Plots of 2d cross
+sections with iso2d</font></h4>
+<p style="line-height: 100%;">PALM permits simultaneous output xy, xz
+and&nbsp;
+yz cross sections. Since the output of all three cross section plots is
+steered in the same way, only the creation of xy plots is described.</p>
+<p style="line-height: 100%;">Output of xy cross
+sections requires to set at least two parameters: first, the temporal
+interval of the output time (run parameter <a
+ href="chapter_4.2.html#dt_do2d_xy"><u>dt_do2d_xy)</u></a><span
+ style="text-decoration: none;">
+and second<span style="text-decoration: none;"></span>
+the names of the quantities for which cross section output is wanted</span><span
+ style="text-decoration: none;"><span style="text-decoration: none;"> (<a
+ href="chapter_4.2.html#data_output">data_output</a></span></span>).
+The string <span style="font-style: italic;">'_xy'</span>
+must be appended to these name strings in either case. 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 cross sections are
+written at the time t=0; exceptions see <a
+ href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>).
+The exact location (height level) of the cross
+section(s) can be defined with run parameter <a
+ href="chapter_4.2.html#section_xy">section_xy</a>.
+If no values have been assigned to <b>data_output</b> and <b>section_xy</b> or
+if the value given for <b>dt_do2d_xy </b>is
+larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>),
+<b>then there will be no output!</b><br>
+</p>
+<p style="line-height: 100%;">Data is output in binary format
+into the
+local file <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>.
+This file must be linked with a permanent file by
+using a file connection statement in the <b>mrun</b> configuration
+file (see e.g. <a href="chapter_3.2.html">chapter
+3.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">PLOT2D_XY out:loc:tr  pxy  ~/PLOT/$fname  _pxy_in.</font></pre>
+</ul>
+<p style="line-height: 100%;">If the respective <b>mrun</b> call is
+like </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -d  test -r pxy
+</font></pre>
+</ul>
+<p style="line-height: 100%;">then the local file <tt><font
+ style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
+is copied to the permanent file <tt><font style="font-size: 10pt;"
+ size="2">~/PLOT/test/test_pxy_in</font>
+</tt>. However, the character string <font style="font-size: 10pt;"
+ size="2"></font><tt><font style="font-size: 10pt;" size="2">pxy</font></tt><font
+ style="font-size: 10pt;" size="2"></font>
+activating the file connection statement (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> <span style="text-decoration: none;">If
+t</span>his 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 created data file can be
+directly used as input file for the plot software <b>iso2d</b>.
+However, this requires the user to assign <a
+ href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
+= <i>.FALSE. </i>(see also at the end of this chapter) . <b>iso2d</b>
+needs another file, the so-called parameter file, which specifies the
+plot
+layout. This file contains a
+so-called global parameter set which applies to all plots as well as
+a local parameter set which is valid for each individual plot. These
+global and
+local parameter sets are also created by PALM and output into two
+different local files named <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
+and <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
+These must be combined to one file via a so-called <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.2">output
+command</a> in the configuration file. The resulting file also needs a
+file connection statement: </p>
+<ul>
+  <pre style="line-height: 100%;"><font style="font-size: 10pt;"
+ size="2">OC: [[ -f PLOT2D_XY_GLOBAL]] &amp;&amp; cat PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</font><br><br><font
+ style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL out:loc:tr  pxy  ~/PLOT/$fname  _pxy_par.</font></pre>
+</ul>
+<p style="line-height: 100%;">The output command (corn shell syntax)
+tests whether the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL</font></tt>
+exists and if so the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY_LOCAL</font></tt>
+is appended via the "cat" command to the file <tt><font
+ style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL</font></tt>
+which then contains all parameters needed by <b>iso2d</b>.&nbsp; This
+relatively pedantic proceeding is due to the fact that PALM
+can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation
+(when the final value of the global <span style="font-weight: bold;">iso2d</span>-parameter
+<a
+ href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
+is known), while the local parameter sets are written continuously
+to the file PLOT2D_XY_LOCAL during the run. A consequence is, that in
+case of aborts of a run the file <tt><font style="font-size: 10pt;"
+ size="2">PLOT2D_XY_GLOBAL</font></tt>
+has possibly not been created and thus a visualization of the data -
+although they may be available - is
+not possible (in such a case, the user may create the parameter file
+manually). </p>
+<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">iso2d -d test  _pxy_in  -p test_pxy_par</font></pre>
+</ul>
+<p style="line-height: 100%;">By default plot layout as specified in
+the parameter file is as follows: for each cross section of each
+individual quantity a seperate plot is created using isolines. Isolines
+with negative values are displayed in
+red color. The axes do not have labels and the units are [m]. For
+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, and the date and time of the
+beginning
+of the run. Furthermore each plot carries a
+caption where the name of the displayed quantity, the output time
+(starting from
+beginning of the 3d simulation, t=0) and the location of the cross
+sections (as height level and grid point number) is noted. </p>
+<p style="line-height: 100%;">The layout of the plots can be
+varied by editing the parameter file (according to the
+various features of <b>iso2d</b>: color shading,
+vector plots, streamlines, etc.). For a detailed description of the <span
+ style="font-weight: bold;">iso2d</span> parameters see the
+<a
+ href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>
+manual (only in German). </p>
+<p style="line-height: 100%;">With parallel runs and choice of <a
+ href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
+= <i>.T.</i> each PE outputs the data of its subdomain
+to a separate file with the name PLOT2D_XY_&lt;processor-Id&gt;,
+whereby &lt;processor-Id&gt; is a four digit number (e.g.
+PLOT2D_XY_0000). These files are not suitable for <span
+ style="font-weight: bold;">iso2d</span>, but after the
+end
+of a run they can be combined to one file readable by <span
+ style="font-weight: bold;">iso2d</span>. This is done via a
+further output command in the configuration file: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">OC:[[$ ( echo $localhost | cut -c1-3 ) = imbh ]] &amp;&amp; combine_plot_fields.x</font></pre>
+</ul>
+<p style="line-height: 100%;">The program <tt><font
+ style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
+collects the data from the individual processor files and outputs it
+into the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
+which can be processed by <span style="font-weight: bold;">iso2d</span>.
+Using this call, possibly existing
+files of the other cross sections (xz, yz) and of 3d volume data are
+also combined.&nbsp;The tool writes
+informative messages about the actions accomplished into the job
+protocol, even if no files were found (i.e. the output command
+may remain in the configuration file, even if no appropriate files
+are created during the simulation). <br>
+<b><br>
+Note:</b> due to internal
+restrictions of <b>iso2d </b>the file <tt><font
+ style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
+may not contain more than 99 cross sections. This restriction does not
+apply
+for the production of video clips via <b>iso2d</b>. &nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.3.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a
+ href="chapter_4.5.5.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;<i>Last change:&nbsp;&nbsp;</i>
+20/04/05 (SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.5.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.5.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.5.html	(revision 5)
@@ -0,0 +1,205 @@
+<!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.5</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041027;13094394">
+  <meta name="CHANGED" content="20041117;11561956">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h4 style="line-height: 100%;"><font size="4">4.5.5 Plots of 3d volume
+data with AVS</font></h4>
+<p style="line-height: 100%;">In contrast to the plot output described
+so far, which can be handled more or less automatically, the creation
+of
+plots with <b>AVS</b> requires programming a so-called network by
+using the <span style="font-weight: bold;">AVS</span> network editor
+to design the plot
+layout. Details are not given here because it is assumed that the user
+is familiar with <b>AVS</b>. </p>
+<p style="line-height: 100%;"><font color="#000000">Output of 3d volume
+data requires to set at least two parameters: </font>first, the
+temporal
+interval of the output time (run parameter <a
+ href="chapter_4.2.html#dt_do3d"><u>dt_do3d)</u></a><span
+ style="text-decoration: none;">
+and second<span style="text-decoration: none;"></span>
+the names of the quantities for which volume data output is wanted</span><span
+ style="text-decoration: none;"><span style="text-decoration: none;"> (<a
+ href="chapter_4.2.html#data_output">data_output</a></span></span>).<font
+ color="#000000"> </font><font color="#000000"><span
+ style="text-decoration: none;"></span></font><font color="#000000"><span
+ style="text-decoration: none;"></span><span
+ style="text-decoration: none;"></span></font><font color="#800000"> </font>The
+parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>
+can be used to limit data output in vertical direction up to a certain
+grid
+point. If no value has been assigned to <b>data_output</b> or
+if the value given for <b>dt_do3d </b>is
+larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>),
+<b>then there will be no output!</b> By default, data is output in
+32-bit real format. Alternatively, for parallel runs, data can also be
+output in compressed format using 32-bit integers. This yields
+a loss of accuracy, but the file size is clearly reduced. The output of
+compressed data is described in more detail in <a
+ href="chapter_4.5.6.html">chapter
+4.5.6</a>. </p>
+<p style="line-height: 100%;">Data, whether compressed or
+uncompressed, is output into the local file <a
+ href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
+This file must be linked with a permanent file by
+using a file connection statement in the <b>mrun</b> configuration
+file (see e.g. <a href="chapter_3.2.html">chapter
+3.2</a>). At the end of the run the local file is copied to this
+file. Additionally, mrun creates a file containing some coordinate
+informations about the 3d data, which also has to be copied. The
+statements can look like this: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">PLOT3D_DATA out:loc:tr avs ~/PLOT/$fname  _avs<br>PLOT3D_COOR out:loc:tr avs ~/PLOT/$fname  _coor .</font></pre>
+</ul>
+<p style="line-height: 100%;">If the respective <b>mrun</b> call is
+like</p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">mrun -d  test -r avs
+</font></pre>
+</ul>
+<p style="line-height: 100%;">then the local file <tt><font
+ style="font-size: 10pt;" size="2">PLOT3D_DATA</font></tt>
+is copied to the permanent file <tt><font style="font-size: 10pt;"
+ size="2">~/PLOT/test/test_avs</font></tt> .
+However, the character string <tt><font style="font-size: 10pt;"
+ size="2">avs</font></tt>
+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). <span style="text-decoration: none;">If t</span>his
+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.<br>
+</p>
+<p style="line-height: 100%;">The created data file can be used as
+input file for the plot software <span style="font-weight: bold;">AVS</span>
+although for parallel runs another step is necessary which is
+described at the end of this chapter. However, after starting <b>AVS</b>
+(by executing the command avs), these data file is not read
+immediately<font color="#000000">. First, the user has to load a
+suitable network (created by the
+network editor). This module usually contains the module</font> read
+field, which requires an input
+file in the so-called "fld-format", which in turn refers to the two
+files
+specified above (containing the volume data and coordinate
+informations) and describes their exact structure. This fld file is
+also generated by PALM by creating two different
+local files with the names <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
+and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
+which must be combined into one file by a so-called <a
+ href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.2">output
+command</a>: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">OC:[[ -f PLOT3D_FLD ]] &amp;&amp; cat PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</font></pre>
+</ul>
+<p style="line-height: 100%;">The new file PLOT3D_FLD also needs a file
+connection statement: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">PLOT3D_FLD out:loc:tr   avs  ~/PLOT/$fname  _fld fld</font></pre>
+</ul>
+<p style="line-height: 100%;">The above <b>mrun </b>call
+then copies the local file <tt><font style="font-size: 10pt;" size="2">PLOT3D_FLD</font></tt>
+to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_fld.fld</font>
+</tt><font face="Thorndale, serif">.</font> In this case the entry
+<tt><font style="font-size: 10pt;" size="2">fld</font></tt>
+in the sixth column of the file connection statement is
+very important because this ensures that the permanent file name gets
+the suffix  <tt><font style="font-size: 10pt;" size="2">.fld</font></tt>
+".&nbsp; The <span style="font-weight: bold;">AVS</span>
+module read field expects all files to have this suffix. (Note: With
+this file
+connection statements files with cycle numbers receive the names <tt><font
+ style="font-size: 10pt;" size="2">
+
+_fld.&lt;number of cycle&gt;.fld</font></tt><font
+ style="font-size: 10pt;" size="2">
+</font>".) </p>
+<p style="line-height: 100%;"><font color="#000000">The file
+connection statements must guarantee that all three permanent files
+(volume
+data, coordinates, fld file) lie in the same directory. The names of
+the volume data file and coordinate file may not be changed after
+creation of the files, since they are registered in the fld file and
+otherwise cannot be found </font>by the "read field" module. Sometimes
+it may happen<font color="#000000">
+that incorrect file names are registered into the fld file. In such
+cases the user must edit and correct the fld file accordingly. </font>
+</p>
+<p style="line-height: 100%;"><font color="#800000"><font
+ color="#000000">After
+<font color="#000000">the <span style="font-weight: bold;">AVS</span>
+module <font color="#000000">read
+fields </font>has </font>read in the data, the content of this
+file is listed in a separate <span style="font-weight: bold;">AVS</span>
+window where each quantity is represented by its name and output time.</font>
+</font></p>
+<p style="line-height: 100%;">With parallel runs each PE outputs the
+volume data of its subdomain to a separate file with the name
+PLOT3D_DATA_&lt;processor-Id&gt;,
+whereby &lt;processor-Id&gt; is a four digit number (e.g.
+PLOT3D_DATA_0000). These files are not suitable for&nbsp; <b>AVS</b>,
+but after the end of a run they can be combined to one file readable by
+<span style="font-weight: bold;">AVS</span>. This is done via a
+further output command in the configuration file: </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">OC:[[$ ( echo $localhost | cut -c1-3 ) = ibmh ]] &amp;&amp; combine_plot_fields.x</font></pre>
+</ul>
+<p style="line-height: 100%;">The program <tt><font
+ style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
+collects the data from the individual processor files and outputs it
+into the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_DATA</font></tt>
+which can be processed by <span style="font-weight: bold;">AVS</span>.
+Using this call, possibly existing
+files of 2d cross sections (xy, xz, yz) are
+also combined.&nbsp;The tool writes
+informative messages about the actions accomplished into the job
+protocol, even if no files were found (i.e. the output command
+may remain in the configuration file, even if no appropriate files
+are created during the simulation). <span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span
+ style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><br>
+</p>
+<p style="line-height: 100%;">&nbsp;<b>Note:</b> <span
+ style="font-weight: bold;">AVS</span> can process 64 arrays at maximum
+in one file (with vector representations even
+only 25). If more arrays should be output, surplus arrays must be
+removed from the fld file (see <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>)
+manually. &nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.4.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.6.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;<i>Last change:&nbsp;</i> 20/04/05
+(SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.5.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.6.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.6.html	(revision 5)
@@ -0,0 +1,109 @@
+<!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.6</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041029;13171001">
+  <meta name="CHANGED" content="20041117;12013945">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h4 style="line-height: 100%;"><font size="4">4.5.6 Plots of compressed
+3d volume data with AVS</font></h4>
+<p style="line-height: 100%;">Files containing 3d volume data usually
+need large amounts of disc space. For parallel runs, the disc space
+requirement can
+be clearly reduced if the data are output in compressed format (note:
+currently a data
+compression is permitted only for parallel runs on Cray-T3E). Data
+compression
+can switched on by setting the initialization parameter <a
+ href="chapter_4.2.html#do3d_compress">do3d_compress</a>
+= <i>.TRUE.</i> and by assigning the desired accuracy (number of
+significant digits) via <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
+A separate accuracy must be assigned for each individual quantity.
+Using uncompressed data, each grid point value is
+represented by a 32-bit real number, in case of compression the grid
+point values are represented by integers whose length depends
+on the desired accuracy (in general clearly smaller than 32 bits).
+The individual grid point values are packed into 32-bit integers and
+output. To plot these compressed data the following output command must
+be inserted into the
+<span style="font-weight: bold;">mrun</span> configuration file<b> </b>(in
+addition to the steps described
+in <a href="chapter_4.5.5.html">chapter
+4.5.5</a>): </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">OC:[[ -f PLOT3D_COMPRESSED ]] &amp;&amp; tar cf PLOT3D_DATA PLOT3D_DATA_*</font></pre>
+</ul>
+<p style="line-height: 100%;">If a file named <tt><font
+ style="font-size: 10pt;" size="2">PLOT3D_COMPRESSED</font></tt>
+exists in the local working directory, <tt><font
+ face="Thorndale, serif">t</font></tt><font face="Thorndale, serif">he
+files produ</font>ced by the individual processors are packed into one
+file (<tt><font style="font-size: 10pt;" size="2">PLOT3D_DATA</font></tt>)
+using the "tar"
+command. The flag file
+<tt><font size="2">PLOT3D_COMPRESSED </font></tt>is created by PALM
+whenever data in compressed form is to be output. For
+uncompressed output, the individual files have to be joined via the
+program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font>
+</tt>. In this case, an additional output command is also necessary
+(see chapter 4.5.5). For compressed output, this output command may
+remain
+unchanged in the configuration file, since <tt><font
+ style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
+recognizes the
+ex<font face="Thorndale, serif">isten</font>ce of <tt><font
+ style="font-size: 10pt;" size="2">PLOT3D_COMPRESSED</font></tt>
+and carries out no actions in such cases. </p>
+<p style="line-height: 100%;">The file connection statements for the
+local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>
+and all further necessary statements to create plots of 3d volume
+data can be found in <a href="chapter_4.5.5.html">chapter
+4.5.5</a>. </p>
+<p style="line-height: 100%;">After been transferred to the local
+computer
+of the user, the tar file with the compressed data cannot be read
+with the usual <span style="font-weight: bold;">AVS</span> module
+read field. Alternatively,
+the module read_compressed_field particularly developed
+for this purpose must be used. This module is located in a module
+library under: </p>
+<pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ style="font-size: 10pt;" size="2">http://www.muk.uni-hannover.de/~raasch/PALM_group/AVS/Libraries/palm</font></pre>
+<p style="line-height: 100%;">This module must be loaded within AVS
+(network editor - &gt; module
+tools - &gt; read module library) and then it can be used like all
+other modules. <a
+ href="http://www.muk.uni-hannover.de/institut/people/raasch/PALM_group/AVS/Doc/read_compressed_field.html">Further
+information</a> about using this module is available (e.g. for
+accelerated treatment of compressed data with <span
+ style="font-weight: bold;">AVS</span> the module
+<a
+ href="http://www.muk.uni-hannover.de/institut/people/raasch/PALM_group/AVS/Doc/write_compressed_field.html">write_compressed_field</a>
+is available). <br>
+&nbsp; <br>
+&nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.5.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.7.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;<i>Last change:&nbsp;</i> 20/04/05
+(SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.5.7.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.7.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.7.html	(revision 5)
@@ -0,0 +1,104 @@
+<!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.7</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041029;14344622">
+  <meta name="CHANGED" content="20050119;9531085">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h4 style="line-height: 100%;"><font size="4">4.5.7 Plots of
+isosurfaces, 2d cross sections and particles with dvrp</font></h4>
+<p style="line-height: 100%;">The <span style="font-weight: bold;">dvrp</span>
+software developed by the RRZN
+(Stephan Olbrich, Carsten Chmielewski) allows a creation of plot
+sequences with PALM,
+which can be animated via a special plugin for internet browsers. With
+suitable graphic hardware even stereoscopic views are
+possible. <br>
+In contrast to the other kinds of visualization output realized
+in PALM (<b>profil</b>, <b>iso2d</b> and <b>AVS</b>), where the data
+is output in a format suitable for the plot software, the creation of
+plots via <span style="font-weight: bold;">dvrp</span> software is
+integrated in PALM, i.e. respective routines are directly called within
+the PALM code. The
+<span style="font-weight: bold;">dvrp</span> routines then output the
+graphic data
+(so-called plot-primitives, e.g. polygones of isosurfaces) in a special
+dvr format. Since the <span style="font-weight: bold;">dvrp</span>
+software is parallelized (i.e. each PE calculates the graphic data for
+its subdomain), the visualization of simulations with very
+large numbers of grid points is possible (which so far failed because
+of
+several problems: volume of the raw data, which rapidly may sum-up to
+several Terabytes; main memory size needed for graphic workstations, on
+which the visualization is to be carried out; the insufficient scalar
+(!)
+computing speed of commercial graphic software in case of such
+large numbers of grid points). </p>
+<p style="line-height: 100%;">The coupling of <span
+ style="font-weight: bold;">dvrp</span> software and PALM
+as well as the visualization of the model results via <span
+ style="font-weight: bold;">dvrp</span> has been
+the main focus of the BMBF project "Application of
+tele-immersion in long-distance networks" (2001-2002),
+which was a joint project of RRZN, ZIB and IMUK. This work is currently
+continued by RRZN in the new DFG-funded project "EVITA - Untersuchung
+effizienter
+<br>
+Methoden zur visuellen und haptischen tele-immersiven Exploration
+<br>
+komplexer Volumen- und Strömungsdaten aus parallelisierten,
+<br>
+dynamischen 3D-Simulationen" (2005-2007). </p>
+<p style="line-height: 100%;">The calls of the <span
+ style="font-weight: bold;">dvrp</span> routines are contained within a
+PALM software package (see chapter <a href="chapter_3.7.html">3.7</a>).
+To use this package, the additional option <tt><font size="2">-p
+dvrp_graphics</font></tt>
+has to be given in the <b>mrun</b> call. This automatically links the
+required libraries.
+Steering of the plot output is done via the package
+parameters (see chapter <a href="chapter_4.2.html">4.2</a>).
+In contrast to all other PALM output, <span style="font-weight: bold;">dvrp</span>
+graphic
+data are not output to local files but directly to a special remote
+computer which is defined via the package parameter <a
+ href="chapter_4.2.html#dvrp_host">dvrp_host</a>.
+The
+default values of the dvrp parameters are cause the output to be
+directed to a so-called streaming server at the
+RRZN. Apart from graphic data an additional html file is created, which
+can be used by an internet browser to view the data (a special <span
+ style="font-weight: bold;">dvrp</span> plugin is needed). </p>
+<p style="line-height: 100%;">Since July 2001, the basic functionality
+of the <span style="font-weight: bold;">dvrp</span> software is
+installed in PALM and steerable via the
+package parameters. However, some code modifications may still need to
+be done by the user (e.g. in
+the subroutine <tt><font style="font-size: 10pt;" size="2">plot_dvrp</font></tt>
+in order to define suitable color tables).
+<br>
+For further detailed information please ask Siegfried Raasch. </p>
+<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.5.6.html"><font
+ color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="index.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="chapter_4.6.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;<i>Last change:&nbsp;</i> 20/04/05
+(SR)</p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_4.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.5.html	(revision 5)
@@ -0,0 +1,74 @@
+<!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</title>
+  
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041015;12234229">
+  <meta name="CHANGED" content="20041022;13412723">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style></head>
+
+<body dir="ltr" lang="en-US">
+<h3 style="line-height: 100%;">4.5 Data analysis and visualization<br>
+</h3>
+<p style="line-height: 100%;">PALM is able to output
+data of different quantities as time series,
+vertical profiles (usually horizontally averaged), two-dimensional
+cross sections or <font color="#000000">3d-volume data.</font>
+Depending on the kind of output (time series, profiles, etc.) and the output format (ASCII&nbsp; or binary) data are written
+to different files (file descriptions can be found in
+<a href="../app/chapter_3.4.html">chapter
+3.4</a>). By default, all data
+output files are in NetCDF format (link to the NetCDF documentations in
+the Internet and on the PALM homepage), which can be processed by many
+public domain and commercial (graphic) software. Data from NetCDF files
+can also be easily read from FORTRAN programs provided that a NetCDF
+library is available. More detailed informations about the
+PALM-NetCDF-output is given in the next subchapter (<a href="../app/chapter_4.5.1.html">4.5.1</a>).</p>
+
+<p style="line-height: 100%;">Due to historical reasons, PALM can also
+output data in other formats suitable for some special graphic
+software. The exact format of these files corresponds to the
+requirements of the respective software. Still available at IMUK are <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>
+(time series, profiles), <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>
+(2d cross sections) and <b>AVS</b> (e.g. iso-surfaces of 3d volume
+data). The special files created by PALM can be directly used
+as input files for these plot programs. Beyond that, <b>profil</b> and
+<b>iso2d</b> need additional information
+about the plot layout (e.g. titles, axes labels, arrangement of the
+coordinate systems, etc.) provided by so-called parameter files<font color="#800000">.
+</font><font color="#000000">Thes</font>e files are also created by
+the PALM, providing a default layout (e.g. plots produced by <b>iso2d</b>
+show. only isolines and no color shading). Within certain
+limits the plot layout can be steered by some PALM parameters.
+Beyond that the user can edit the parameter files created by PALM and
+change, supplement or remove the given default values
+according to his needs. Beside the file with the (binary) data to be
+visualized, <b>AVS</b> additionally needs a file with
+coordinate information (likewise binary) and an ASCII file in the
+so-called FLD format, which describes the structure of the two binary
+files. Coordinate and FLD file are also created by the PALM. However,
+with <b>AVS</b> (differently than with <b>profile</b> or <b>iso2d</b>)
+the plot layout must always be additionally designed by the user
+with the help of the AVS network editor. &nbsp;</p>
+
+
+<p style="line-height: 100%;">In the following subchapters, steering
+of the different data output and how to create plots of the data is
+described by some examples. Not all details of steering
+are mentioned. If necessary, these can be found within the
+description of the respective parameters.<br>
+</p>
+
+&nbsp;For most purposes it should be sufficient to read <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a> which explains the PALM-NetCDF-output.<hr>
+<p style="line-height: 100%;"><br>
+<font color="#000080"><font color="#000080"><a href="chapter_4.4.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.1.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> 05/03/05 (SR)<br>
+</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.6.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_4.6.html	(revision 5)
@@ -0,0 +1,24376 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
+  <title>PALM chapter 4.6</title>
+
+
+
+
+
+
+  
+
+
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  <meta name="GENERATOR" content="StarOffice 7 (Win32)">
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  <meta name="AUTHOR" content="Marcus Oliver Letzel">
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  <meta name="CREATED" content="20041103;9554421">
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  <meta name="CHANGED" content="20041117;12591937">
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  <meta name="KEYWORDS" content="parallel LES model">
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  <style>
+<!--
+@page { size: 21cm 29.7cm }
+-->
+  </style>
+</head>
+
+<body style="direction: ltr;" lang="en-US">
+
+
+
+
+
+
+
+<h3>4.6 Listing of the steering parameters in alphabetical order<br>
+
+
+
+
+
+
+
+</h3>
+
+
+
+
+
+
+
+<p style="margin-bottom: 0cm;">Initialization parameters
+(class = I),
+run parameters (R), package parameters (P) as well as user-defined
+parameters (U) are alphabetically listed in the following table. <br>
+
+
+
+
+
+
+
+&nbsp;
+</p>
+
+
+
+
+
+
+
+<p style="margin-bottom: 0cm;" align="center"><br>
+
+
+
+
+
+
+
+</p>
+
+
+
+
+
+
+
+<table style="width: 100%;" border="1" cellpadding="2" cellspacing="4">
+
+
+
+
+
+
+
+  <col width="38*"> <col width="12*"> <col width="18*"> <col width="42*"> <col width="146*"> <tbody>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <h3><b>Parameter name</b></h3>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <h3>Class</h3>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <h3>Type</h3>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <h3>Default<br>
+
+
+
+
+
+
+
+value</h3>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <h3>Explanation</h3>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#adjust_mixing_length"><b>adjust_mixing_length</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Near-surface adjustment of the
+mixing length to the Prandtl-layer law.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#alpha_surface"><b>alpha_surface</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Inclination of the model domain
+with respect to the horizontal (in degrees).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#averaging_interval"><span style="font-weight: bold;">averaging_interval</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">0.0</span></td>
+      <td>Averaging interval for all&nbsp;output of temporally averaged data (in s).</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#averaging_interval_pr"><b>averaging_interval_pr</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
+
+interval</a></span></td>
+
+
+
+
+
+
+
+      <td style="width: 57%; text-align: left; vertical-align: middle;"> Averaging interval for vertical profiles&nbsp;output to local
+file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a> </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
+(in s).&nbsp;</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#averaging_interval_sp"><b>averaging_interval_sp</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
+
+interval</a></span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">Averaging 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;</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_e_b"><b>bc_e_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'neumann'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition of the
+TKE. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#bc_lr"><b>bc_lr</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">C * 20<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">&acute;cyclic&acute;</span><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Boundary
+condition along x (for all quantities).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#bc_ns"><b>bc_ns</b></a></b></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">C * 20</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">'cyclic'</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Boundary
+condition along y (for all quantities).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_p_b"><b>bc_p_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'neumann'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition of the
+perturbation pressure. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_p_t"><b>bc_p_t</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'dirichlet'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Top boundary condition of the
+perturbation pressure. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_b"><b>bc_par_b</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>&acute;reflect&acute;</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition for particle transport. </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_lr"><b>bc_par_lr</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Lateral boundary
+condition
+(x-direction) for particle
+transport.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_ns"><b>bc_par_ns</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Lateral boundary
+condition
+(y-direction) for particle
+transport.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_t"><b>bc_par_t</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">C*15</td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>&acute;absorb&acute;</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Top boundary
+condition for
+particle transport.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_pt_b"><b>bc_pt_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'dirichlet'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition of the
+potential temperature. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#pc_pt_t"><b>bc_pt_t</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'neumann'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Top boundary condition of the
+potential temperature. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_q_b"><b>bc_q_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'dirichlet'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition of the
+specific humidity / total water content. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_q_t"><b>bc_q_t</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'neumann'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Top boundary condition of the
+specific humidity / total water content. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_s_b"><b>bc_s_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'dirichlet'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition of the
+scalar concentration. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_s_t"><b>bc_s_t</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>&acute;neumann&acute;</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Top boundary condition of the
+scalar concentration. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_uv_b"><b>bc_uv_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'dirichlet'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom boundary condition of the horizontal wind
+components u
+and v.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#bc_uv_t"><b>bc_uv_t</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'dirichlet'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Top boundary condition of the
+horizontal velocity components u and v.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="font-weight: bold;"><a href="chapter_4.1.html#building_height">building_height</a></td>
+
+
+
+
+
+      <td>I</td>
+
+
+
+
+
+      <td>R</td>
+
+
+
+
+
+      <td style="font-style: italic;">50.0</td>
+
+
+
+
+
+      <td>Height of a single building in m.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_x">building_length_x</a></td>
+
+
+
+
+
+      <td>I</td>
+
+
+
+
+
+      <td>R</td>
+
+
+
+
+
+      <td style="font-style: italic;">50.0</td>
+
+
+
+
+
+      <td>Width of a single building in m.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_y">building_length_y</a></td>
+
+
+
+
+
+      <td>I</td>
+
+
+
+
+
+      <td>R</td>
+
+
+
+
+
+      <td style="font-style: italic;">50.0</td>
+
+
+
+
+
+      <td>Depth of a single building in m.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_left">building_wall_left</a></td>
+
+
+
+
+
+      <td style="vertical-align: middle;">I</td>
+
+
+
+
+
+      <td style="vertical-align: middle;">R</td>
+
+
+
+
+
+      <td style="font-style: italic;"><span style="font-style: italic;">building centered in x-direction</span></td>
+
+
+
+
+
+      <td style="vertical-align: middle;">x-coordinate of the left building wall in m.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+      <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_south">building_wall_south</a></td>
+
+
+
+
+
+      <td style="vertical-align: middle;">I</td>
+
+
+
+
+
+      <td style="vertical-align: middle;">R</td>
+
+
+
+
+
+      <td style="font-style: italic;"><span style="font-style: italic;">building centered in y-direction</span></td>
+
+
+
+
+
+      <td style="vertical-align: middle;">y-coordinate of the South building wall&nbsp;in m.</td>
+
+
+
+
+
+    </tr>
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#call_psolver_at_all_substeps"><b>call_psolver_at_all_substeps</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">L<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">.T..</span><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Switch
+to steer the call of the pressure solver.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><b><a href="chapter_4.2.html#fcl_factor"><b>cfl_factor</b></a></b></td>
+      <td>R</td>
+      <td>R</td>
+      <td><i>0.1, 0.8&nbsp;or 0.9 </i>(see parameter description)</td>
+      <td>Time step limiting factor.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><a href="chapter_4.1.html#cloud_droplets"><span style="font-weight: bold;">cloud_droplets</span></a><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">L<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Parameter to switch
+on usage of cloud droplets.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#cloud_physics"><b>cloud_physics</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on the condensation scheme. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#comp_spectra_level"><b>comp_spectra_level</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>no level</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Vertical level for which horizontal spectra are to be
+calculated and output (gridpoints).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+      <td><a href="chapter_4.1.html#conserve_volume_flow"><span style="font-weight: bold;">conserve_volume_flow</span></a></td>
+
+
+
+
+      <td>I</td>
+
+
+
+
+      <td>L</td>
+
+
+
+
+      <td><span style="font-style: italic;">.F.</span></td>
+
+
+
+
+      <td>Conservation of volume flow in x- and y-direction.</td>
+
+
+
+
+    </tr>
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#create_disturbances"><b>create_disturbances</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.T.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Switch to impose random perturbations to the horizontal
+velocity field. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#cross_normalized_x"><b>cross_normalized_x</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 10 (100)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>100 * ' '</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Type of normalization applied to the x-coordinate of
+vertical
+profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#cross_normalized_y"><b>cross_normalized_y</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 10&nbsp; <br>
+
+
+
+
+
+
+
+(100)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>100 * ' '</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Type of normalization applied to the y-coordinate of
+vertical
+profiles to be plotted with <span style="font-weight: bold;">profil</span>.
+      <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#cross_profiles"><b>cross_profiles</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 100 (100)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Determines which vertical profiles are to be presented
+in
+which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is
+used.&nbsp; <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#cross_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>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#cross_xtext"><b>cross_xtext</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 40&nbsp; <br>
+
+
+
+
+
+
+
+&nbsp;(100)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>x-axis labels of vertical profile coordinate systems to
+be
+plotted with <span style="font-weight: bold;">profil</span>.
+      <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#cut_spline_overshoot"><b>cut_spline_overshoot</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.T.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Cut off of so-called overshoots, which can occur with
+the upstream-spline-scheme.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#cycle_mg"><b>cycle_mg</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 1</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'w'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">Type
+of cycle to
+be used with the multi-grid
+method.&nbsp;</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#damp_level_1d"><b>damp_level_1d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>zu(nz+1)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Height where the damping layer begins in the 1d-model
+(in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#data_output"><span style="font-weight: bold;">data_output</span></a></td>
+      <td>R</td>
+      <td>C * 10 (100)</td>
+      <td><span style="font-style: italic;">100 * &acute; &acute;</span></td>
+      <td>Quantities for which 2d cross section and/or 3d volume data are to be output.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#data_output_format"><span style="font-weight: bold;">data_output_format</span></a></td>
+      <td>R</td>
+      <td>C * 10 (10)</td>
+      <td><span style="font-style: italic;">'netcdf'</span></td>
+      <td>Format of output data.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#data_output_pr"><span style="font-weight: bold;">data_output_pr</span></a></td>
+      <td>R</td>
+      <td>C * 10 (100)</td>
+      <td><span style="font-style: italic;">100 * ' '</span></td>
+      <td>Quantities for which vertical profiles (horizontally averaged)
+are to be output.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#data_output_sp"><span style="font-weight: bold;">data_output_sp</span></a></td>
+      <td>P</td>
+      <td>C * 10 (10)</td>
+      <td><span style="font-style: italic;">10 * ' '</span></td>
+      <td>Quantities for which horizontal spectra are to be calculated
+and output.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.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>
+      <td>U</td>
+      <td>C * 10 (100)</td>
+      <td><span style="font-style: italic;">100 * ' '</span></td>
+      <td>User defined quantities for which 2d cross section and/or 3d volume data are to be output.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#data_output_2d_on_each_pe"><span style="font-weight: bold;">data_output_2d_on_each_pe</span></a></td>
+      <td>R</td>
+      <td>L</td>
+      <td><span style="font-style: italic;">.T.</span></td>
+      <td>Output 2d cross section data by one or
+all processors.&nbsp;</td>
+    </tr>
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#density_ratio"><b>density_ratio</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0, 9</i> * <i>9999999.9</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Ratio of the density of the fluid and the density of the
+particles.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.1.html#dissipation_1d"><span style="font-weight: bold;">dissipation_1d</span></a></td>
+      <td>I</td>
+      <td>C * 20</td>
+      <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
+      <td>Calculation method for the energy dissipation term in the TKE equation of the 1d-model.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#disturbance_amplitude"><b>disturbance</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#disturbance_amplitude">&nbsp;<b>_amplitude</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.25</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Maximum perturbation amplitude of the random
+perturbations
+imposed to the horizontal velocity field (in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#disturbance_energy_limit"><b>disturbance_energy</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#disturbance_energy_limit">&nbsp;<b>_limit</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.01</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB">Upper limit value of the
+perturbation energy of
+the velocity field used as a criterion for imposing random
+perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#disturbance_level_b"><b>disturbance_level_b</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>zu(3)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
+limit of the vertical range for which random perturbations are to be
+imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
+      </font></font> </p>
+
+
+
+
+
+
+
+      <span lang="en-GB"></span></td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#disturbance_level_t"><b>disturbance_level_t</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>zu(nz/3)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
+limit of the vertical range for which random perturbations are to be
+imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m). <br>
+
+
+
+
+
+
+
+      </font></font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#do2d_at_begin"><span style="font-weight: bold;">do2d_at_begin</span></a></td>
+      <td>R</td>
+      <td>L</td>
+      <td><span style="font-style: italic;">.F.</span></td>
+      <td>Output 2d cross section data by one or
+all processors.&nbsp;</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#do3d_at_begin"><span style="font-weight: bold;">do3d_at_begin</span></a></td>
+      <td>R</td>
+      <td>L</td>
+      <td><span style="font-style: italic;">.F.</span></td>
+      <td>Output of 3d volume data at the beginning
+of a run.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#do3d_compress"><span style="font-weight: bold;">do3d_compress</span></a></td>
+      <td>R</td>
+      <td>L</td>
+      <td><span style="font-style: italic;">.F.</span></td>
+      <td>Output of data for 3d plots in compressed form.&nbsp;</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#do3d_precision"><span style="font-weight: bold;">do3d_precision</span></a></td>
+      <td>R</td>
+      <td>C * 7 (100)</td>
+      <td>see parameter description</td>
+      <td>Significant digits in case of compressed data output.&nbsp;</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dt"><b>dt</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I/R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>variable</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p><font face="Thorndale, serif"><font size="3">Time
+step for the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s). <br>
+
+
+
+
+
+
+
+      </font></font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#dt_averaging_input"><span style="font-weight: bold;">dt_averaging_input</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">0.0</span></td>
+      <td>Temporal interval of&nbsp;data which are subject to temporal averaging (in s).</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_averaging_input_pr"><b>dt_averaging_input_pr</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#dt_averaging_input">dt_<br>
+averaging_<br>
+input</a></span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">Temporal interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;</font></font></td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#dt_data_output"><span style="font-weight: bold;">dt_data_output</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">9999999.9</span></td>
+      <td>
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
+at which&nbsp;data (3d volume data (instantaneous or time averaged),
+cross sections (instantaneous or time averaged), vertical profiles,
+spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
+      </td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#dt_data_output_av"><span style="font-weight: bold;">dt_data_output_av</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+      <td>
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
+at which time averaged 3d volume data and/or 2d cross section data
+shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
+      </td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_disturb"><b>dt_disturb</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>9999999.9</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which random
+perturbations are to be imposed on the horizontal velocity field
+(</font>in <font face="Thorndale">s). <br>
+
+
+
+
+
+
+
+      </font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#dt_dopr"><span style="font-weight: bold;">dt_dopr</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+      <td><span lang="en-GB"><font face="Thorndale">Temporal interval at
+which data&nbsp;of vertical profiles shall be output (to local
+file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a> or/and </font></span><a href="chapter_3.4.html#PLOT1D_DATA"><span lang="en-GB"><font face="Thorndale">PLOT1D_DATA</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span></td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#dt_dopr_listing"><span style="font-weight: bold;">dt_dopr_listing</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">9999999.9</span></td>
+      <td>
+      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
+interval</font> at which data <font face="Thorndale">of vertical
+profiles shall be output (output for printouts, local file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span> </p>
+      </td>
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_dopts"><span style="font-weight: bold;">dt_dopts</span></a></td>
+      <td align="undefined" valign="undefined">P</td>
+      <td align="undefined" valign="undefined">R</td>
+      <td align="undefined" valign="undefined"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+      <td align="undefined" valign="undefined">
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at which time series data of particle quantities shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
+      </td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_dosp"><b>dt_dosp</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">Temporal interval at which&nbsp;spectra data shall be output
+(in s).&nbsp;</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_dots"><b>dt_dots</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which&nbsp;time series data shall be output (</font>in <font face="Thorndale">s). <br>
+
+
+
+
+
+
+
+      </font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_do2d_xy"><b>dt_do2d_xy</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at which horizontal cross section data shall be output (</font>in <font face="Thorndale">s). <br>
+
+
+
+
+
+
+
+      </font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_do2d_xz"><b>dt_do2d_xz</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which vertical cross section data (xz) shall be output&nbsp;(</font>in <font face="Thorndale">s). <br>
+
+
+
+
+
+
+
+      </font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_do2d_yz"><b>dt_do2d_yz</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which vertical cross section data (yz)&nbsp;shall be output&nbsp;(</font>in s<font face="Thorndale">).</font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_do3d"><b>dt_do3d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
+output</a></i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which 3d volume data shall be output (</font>in <font face="Thorndale">s).
+      <br>
+
+
+
+
+
+
+
+      </font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><b><a href="chapter_4.2.html#dt_dvrp"><b>dt_dvrp</b></a></b></td>
+      <td>P</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">9999999.9</span></td>
+      <td>Temporal interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
+s). </td>
+    </tr>
+    <tr>
+      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_min_part"><span style="font-weight: bold;">dt_min_part</span></a></td>
+      <td align="undefined" valign="undefined">P</td>
+      <td align="undefined" valign="undefined">R</td>
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">0.0002</span></td>
+      <td align="undefined" valign="undefined">Minimum value for the particle timestep when SGS velocities are used (in s).</td>
+    </tr>
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_prel"><b>dt_prel</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>9999999.9</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
+interval at
+which particles are to be released <span lang="en-GB">from
+a particle
+source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;</font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dt_pr_1d"><b>dt_pr_1d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>9999999.9</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Temporal interval of vertical profile output of the
+1D-model
+(in s).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_restart"><b>dt_restart</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">9999999.9<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><font face="Thorndale"><font face="Thorndale, serif">Temporal
+interval</font> at which a new
+restart run is to be carried out (</font>in <font face="Thorndale">s).</font></td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dt_run_control"><b>dt_run_control</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>60.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
+which run control
+output is to be made (</font>in <font face="Thorndale">s).
+      <br>
+
+
+
+
+
+
+
+      </font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dt_run_control_1d"><b>dt_run_control_1d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>60.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Temporal interval of runtime control output of the
+1d-model
+(in s).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_write_particle_data"><b>dt_write_particle_data</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>9999999.9</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Temporal
+interval for output
+of particle data (in s).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_directory"><b>dvrp_directory</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 80</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'default'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Name of the directory into which data created by the <span style="font-weight: bold;">dvrp</span>
+software shall be saved. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_file"><b>dvrp_file</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 80</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'default'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Name of the file into which data created by the <span style="font-weight: bold;">dvrp</span> software shall
+be output.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_host"><b>dvrp_host</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 80</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'origin.rvs. <br>
+
+
+
+
+
+
+
+uni- hanover.de'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Name of the computer to which data created by the <span style="font-weight: bold;">dvrp</span> software shall
+be
+transferred. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_output"><b>dvrp_output</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 10</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'rtsp'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Output mode for the <span style="font-weight: bold;">dvrp</span>
+software. </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_password"><b>dvrp_password</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 80</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'********'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">Password
+for the
+computer to which data created
+by the <span style="font-weight: bold;">dvrp</span>
+software is to be
+transferred.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_psize"><b>dvrp_psize</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.2</i> * <i>dx</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Diameter that the particles is given in visualizations
+with
+the <span style="font-weight: bold;">dvrp</span>
+software (in
+m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#dvrp_username"><b>dvrp_username</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 80</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default value </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>User 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. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dx"><b>dx</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Horizontal grid spacing along the x-direction (in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dy"><b>dy</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Horizontal grid spacing along the x-direction (in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dz"><b>dz</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Vertical grid spacing (in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#dz_max">dz_max</a></td>
+      <td align="undefined" valign="undefined">I</td>
+      <td align="undefined" valign="undefined">R</td>
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
+      <td align="undefined" valign="undefined">Allowed maximum vertical grid spacing (in m).<br>
+      </td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dz_stretch_factor"><b>dz_stretch_factor</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.08</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Stretch factor for a vertically stretched grid (see <a href="chapter_4.1.html#dz_stretch_level">dz_stretch_level</a>).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#dz_stretch_level"><b>dz_stretch_level</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>100000.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Height level above which the grid is to be stretched
+vertically (in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td><a href="chapter_4.1.html#e_min"><b>e_min</b></a></td>
+
+
+
+
+
+
+
+      <td>I</td>
+
+
+
+
+
+
+
+      <td>R</td>
+
+
+
+
+
+
+
+      <td>0.0</td>
+
+
+
+
+
+
+
+      <td>Minimum TKE in m<sup>2</sup>s<sup>-2</sup>.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#end_time"><b>end_time</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p lang="en-GB"><font face="Thorndale">Simulation
+time of the 3D
+model (</font>in <font face="Thorndale">s)</font><font face="Thorndale">.</font></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#end_time_prel"><span style="font-weight: bold;">end_time_prel</span></a></td>
+      <td align="undefined" valign="undefined">P</td>
+      <td align="undefined" valign="undefined">R</td>
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
+      <td align="undefined" valign="undefined">Time of the last release of particles (in s).</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#end_time_1d"><b>end_time_1d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>864000.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Time to be simulated for the 1D-model (in s).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#fft_method"><b>fft_method</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'system specific'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>FFT-method to be used.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#force_print_header"><b>force_print_header</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="width: 57%; vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p>Steering of header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#galilei_transformation"><b>galilei_transformation</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Application of a Galilei-transformation to the
+coordinate
+system of the model.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#grid_matching"><b>grid_matching</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 6</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'match'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Variable to adjust the subdomain sizes in parallel runs.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#inflow_disturbance_begin"><b>inflow_disturbance_begin</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(10,</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+      <span style="font-style: italic;">nx/2 or ny/2)</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Lower
+limit of the horizontal range for which random perturbations are to be
+imposed on the horizontal velocity field (gridpoints).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#inflow_disturbance_end"><b>inflow_disturbance_end</b></a></b></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(100,</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+      <span style="font-style: italic;">3/4*nx or</span><br style="font-style: italic;">
+
+
+
+
+
+
+
+      <span style="font-style: italic;">3/4*ny)</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Upper
+limit of the horizontal range for which random perturbations are
+to be imposed on the horizontal velocity field (gridpoints).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#initializing_actions"><b>initializing_actions</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 100</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p style="font-style: normal;">Initialization
+actions
+to be carried out. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><a href="chapter_4.2.html#initial_weighting_factor"><span style="font-weight: bold;">initial_weighting_factor</span></a><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Factor to define
+the real number of initial droplets in a grid cell.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#km_constant"><b>km_constant</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>variable (computed from TKE)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Constant eddy diffusivities are used (laminar
+simulations).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#km_damp_max"><b>km_damp_max</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">0.5*(dx
+or dy)</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Maximum
+diffusivity used for filtering the velocity field in the vicinity of
+the outflow (in m<sup>2</sup>/s).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#long_filter_factor"><b>long_filter_factor</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Filter factor for the so-called Long-filter.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#maximum_number_of_particles"><b>maximum_number_</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#maximum_number_of_particles"><b>of_particles</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1000</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Maximum number of particles (on a PE). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>maximum_number_</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>of_tailpoints</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>100</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Maximum number of tailpoints that a particle tail can
+have. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#maximum_tailpoint_age"><b>maximum_tailpoint_</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#maximum_tailpoint_age"><b>age</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>100000.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Maximum age that the end point of a particle tail is allowed to have (in s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><b><a href="chapter_4.2.html#mg_cycles"><b>mg_cycles</b></a></b></td>
+      <td>R</td>
+      <td>I</td>
+      <td><i>- 1</i></td>
+      <td>Number of cycles to be used with the multi-grid scheme.</td>
+    </tr>
+    <tr>
+      <td><b><b><a href="chapter_4.2.html#mg_switch_to_pe0_level"><b>mg_switch_to_pe0_level</b></a></b></b></td>
+      <td>R</td>
+      <td>I</td>
+      <td>see parameter description</td>
+      <td>Grid
+level at which data shall be gathered on PE0.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#minimum_tailpoint_distance"><b>minimum_tailpoint_</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#minimum_tailpoint_distance"><b>distance</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Minimum distance allowed between two adjacent points of
+a
+particle tail (in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.1.html#mixing_length_1d"><span style="font-weight: bold;">mixing_length_1d</span></a></td>
+      <td>I</td>
+      <td>C * 20</td>
+      <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
+      <td>Mixing length used in the 1d-model.</td>
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#mode_dvrp"><b>mode_dvrp</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20 (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * ' '</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Graphical objects (isosurfaces, slicers, particles)
+which are
+to be created by the <span style="font-weight: bold;">dvrp</span>
+software. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#moisture"><b>moisture</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on the prognostic equation for
+specific
+humidity q.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#momentum_advec"><b>momentum_advec</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 10</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'pw-scheme</i>'</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Advection scheme to be used for the momentum equations.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.1.html#netcdf_precision"><span style="font-weight: bold;">netcdf_precision</span></a></td>
+      <td>I</td>
+      <td>C * 20 (10)</td>
+      <td><span style="font-style: italic;">single preci</span><span style="font-style: italic;">sion for all</span><br style="font-style: italic;">
+
+      <span style="font-style: italic;">output quan</span><span style="font-style: italic;">tities</span></td>
+      <td>Defines the accuracy of the NetCDF output.<br>
+
+      </td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#netcdf_64bit"><span style="font-weight: bold;">netcdf_64bit</span></a></td>
+      <td>R</td>
+      <td>L</td>
+      <td><span style="font-style: italic;">.F.</span></td>
+      <td>NetCDF files will have 64 bit offset format.</td>
+    </tr>
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#ngsrb"><b>ngsrb</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>2</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Grid
+level at which data shall be gathered on PE0.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#normalizing_region"><b>normalizing_region</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Determines the subdomain from which the normalization
+quantities are calculated. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#npex"><b>npex</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of processors along x-direction of the virtual
+processor
+net. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#npey"><b>npey</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of processors along y-direction of the virtual
+processor
+net. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#nsor"><b>nsor</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>20</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of iterations to be used with the SOR-scheme. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#nsor_ini"><b>nsor_ini</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>100</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Initial number of iterations with the SOR algorithm</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#number_of_particle_groups"><span style="font-weight: bold;">number_of_particle_groups</span></a></td>
+      <td>P</td>
+      <td>I</td>
+      <td><span style="font-style: italic;">1</span></td>
+      <td>Number of particle groups to be used.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#nx"><b>nx</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of grid points in x-direction. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ny"><b>ny</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of grid points in y-direction.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#nz"><b>nz</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>no default, see parameter description</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of grid points in z-direction.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#nz_do3d"><b>nz_do3d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>nz+1</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      Limits the output of 3d volume data along the vertical direction (grid point index k).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#omega"><b>omega</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>7.29212E-5</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Angular velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#omega_sor"><b>omega_sor</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.8</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Convergence factor to be used with the the SOR-scheme. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#outflow_damping_width"><b>outflow_damping_width</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(20,
+nx/2</span> or <span style="font-style: italic;">ny/2)</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Width of
+the damping range in the vicinity of the outflow (gridpoints).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_e"><b>overshoot_limit_e</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of subgrid-scale TKE
+in
+case that the upstream-spline scheme is switched on (in m<sup>2</sup>/s<sup>2</sup>).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_pt"><b>overshoot_limit_pt</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of potential
+temperature in
+case that the upstream-spline scheme is switched on (in K). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_u"><b>overshoot_limit_u</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the
+overshooting of
+the u-component of velocity in case that the upstream-spline scheme is
+switched on (in m/s).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_v"><b>overshoot_limit_v</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of the v-component of
+velocity in case that the upstream-spline scheme is switched on
+(in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#overshoot_limit_w"><b>overshoot_limit_w</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Allowed limit for the overshooting of the w-component of
+velocity in case that the upstream-spline scheme is switched on
+(in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#particles_per_point"><span style="font-weight: bold;">particles_per_point</span></a></td>
+      <td align="undefined" valign="undefined">P</td>
+      <td align="undefined" valign="undefined">I</td>
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">1</span></td>
+      <td align="undefined" valign="undefined">Number of particles to be started per point.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><b><a href="chapter_4.2.html#particle_advection_start"><b>particle_advection_start</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: top;">Time of the first
+release of
+particles (in s).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#particle_maximum_age"><b>particle_maximum_age</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>9999999.9</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Maximum allowed age of particles (in s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#passive_scalar"><b>passive_scalar</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on the prognostic equation for a
+passive
+scalar. </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#pdx"><b>pdx</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * dx</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Distance along x between particles within a particle
+source
+(in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#pdy"><b>pdy</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * dy</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Distance along y between
+particles within a
+particle source (in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#pdz"><b>pdz</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * ( zu(2) - zu(1) )</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Distance along z between
+particles within a particle source
+(in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#phi"><b>phi</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>55.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Geographical latitude (in degrees). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#plot_spectra_level"><b>plot_spectra_level</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>No level</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Vertical level(s) for which horizontal spectra are to be
+plotted (in gridpoints). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#prandtl_layer"><b>prandtl_layer</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.T.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on a Prandtl layer. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#prandtl_number"><b>prandtl_number</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Ratio of the eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).
+      <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#precipitation"><b>precipitation</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">L<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">.F.</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Parameter to
+switch on the
+precipitation scheme.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#profile_columns"><b>profile_columns</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>3</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of coordinate systems to be plotted<span style="font-weight: bold;"></span> in one row by <span style="font-weight: bold;">profil</span>. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#profile_rows"><b>profile_rows</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>2</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of rows of coordinate systems to be plotted on
+one page
+by <span style="font-weight: bold;">profil</span>. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#psb"><b>psb</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * zu(nz/2)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Bottom edge of a particle
+source (in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#psl"><b>psl</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * 0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Left edge of a particle source
+(in m). </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#psn"><b>psn</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * ( ny * dy )</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Rear (&ldquo;north&rdquo;) edge of a particle
+source (in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#psolver"><b>psolver</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 10</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'poisfft'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Scheme to be used to solve the Poisson equation for the
+perturbation pressure. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#psr"><b>psr</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * ( nx * dx )</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Right edge of a particle source (in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#pss"><b>pss</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * 0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Front (&ldquo;south&rdquo;) edge of a particle
+source (in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#pst"><b>pst</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * zu(nz/2)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Top edge of a particle source (in m).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#pt_surface"><b>pt_surface</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>300.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Surface potential temperature (in K). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#pt_surface_initial_change"><b>pt_surface_initial</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.1.html#pt_surface_initial_change">&nbsp;<b>_change</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">Change
+in surface
+temperature to be made at the
+beginning of
+the 3d run
+(in K).&nbsp;</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#pt_vertical_gradient"><b>pt_vertical_gradient</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * 0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Temperature gradient(s) of the initial temperature
+profile (in
+K
+/ 100 m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#pt_vertical_gradient_level"><b>pt_vertical_gradient</b></a>&nbsp;&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.1.html#pt_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Height level from which on the temperature gradient
+defined by <a href="chapter_4.1.html#pt_vertical_gradient">pt_vertical_gradient</a>
+is effective (in m).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#q_surface"><b>q_surface</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Surface specific humidity / total water content (kg/kg).
+      <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#q_surface_initial_change"><b>q_surface_initial</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.1.html#q_surface_initial_change">&nbsp;<b>_change</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Change in surface specific humidity / total water
+content to
+be made at the beginning
+of the 3d run (kg/kg). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#q_vertical_gradient"><b>q_vertical_gradient</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * 0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="width: 57%; vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p>Humidity gradient(s) of the initial humidity profile
+(in 1/100 m). </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#q_vertical_gradient_level"><b>q_vertical_gradient</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.1.html#q_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Height level from which on the moisture gradient defined
+by <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
+is effective (in m).&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#radiation"><b>radiation</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to switch on longwave radiation cooling at
+cloud-tops. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#radius"><span style="font-weight: bold;">radius</span></a></td>
+      <td>P</td>
+      <td>R (10)</td>
+      <td><i>0.0, 9</i>*<br>
+
+
+      <i>9999999.9</i></td>
+      <td>Particle radius (in m).</td>
+    </tr>
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#random_generator"><b>random_generator</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'numerical recipes'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Random number generator to be used for creating
+uniformly
+distributed random numbers. </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#random_heatflux"><b>random_heatflux</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to impose random perturbations on the internal two-dimensional near surface heat flux field <span style="font-style: italic;">shf</span>. </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#random_start_position"><b>random_start_position</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
+particles is
+varied randomly within certain limits.&nbsp;</span></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#rayleigh_damping_factor"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#rayleigh_damping_factor">&nbsp;<b>_factor</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">0.0</span> and/or <span style="font-style: italic;">0.01</span> (see parameter description)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Factor for Rayleigh damping.&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#rayleigh_damping_height"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#rayleigh_damping_height">&nbsp;<b>_height</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle; font-style: italic;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>2/3 * zu(nz)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="width: 57%; text-align: left; vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p>Height where the Rayleigh damping starts (in
+m).&nbsp; </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#read_particles_from_restartfile"><b>read_particles_from_</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#read_particles_from_restartfile"><b>restartfile</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.T.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Read particle data from the previous run. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.3.html#region"><b>region</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>U</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 40 (0:9)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p>&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Name(s) of the subdomain(s) defined by the user.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#residual_limit"><b>residual_limit</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0E-6</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Largest residual permitted for the multi-grid scheme (in
+s<sup>-2</sup>m<sup>-3</sup>). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#restart_time"><b>restart_time</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">9999999.9<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Simulated time
+after which a
+restart run is to be carried out
+(in s).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#rif_max"><b>rif_max</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Upper limit of the flux-Richardson number. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#rif_min"><b>rif_min</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>- 5.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Lower limit of the flux-Richardson number. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#roughness_length"><b>roughness_length</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.1</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Roughness length (in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#scalar_advec"><b>scalar_advec</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 10</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'pw-scheme'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Advection scheme to be used for the scalar quantities. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#section_xy"><span style="font-weight: bold;">section_xy</span></a></td>
+      <td>R</td>
+      <td>I (100)</td>
+      <td><span style="font-style: italic;">no section</span></td>
+      <td><font face="Thorndale">Position of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross sections (grid point index k).&nbsp;</font></td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#section_xz"><span style="font-weight: bold;">section_xz</span></a></td>
+      <td>R</td>
+      <td>I (100)</td>
+      <td><span style="font-style: italic;">no section</span></td>
+      <td><font face="Thorndale">Position of&nbsp;cross section(s) for&nbsp;output of 2d (xz) vertical cross sections (grid point index j).&nbsp;</font></td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#section_yz"><span style="font-weight: bold;">section_yz</span></a></td>
+      <td>R</td>
+      <td>I (100)</td>
+      <td><span style="font-style: italic;">no section</span></td>
+      <td><font face="Thorndale">Position of&nbsp;cross section(s) for&nbsp;output of 2d (yz) vertical cross sections (grid point index i).&nbsp;</font></td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_particles_for_tail"><span style="font-weight: bold;">skip_particles_for_tail</span></a></td>
+      <td>P</td>
+      <td>I</td>
+      <td><span style="font-style: italic;">1</span></td>
+      <td>Limit the number of particle tails.</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_data_output"><span style="font-weight: bold;">skip_time_data_output</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">0.0</span></td>
+      <td>No data output before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_data_output_av"><span style="font-weight: bold;">skip_time_data_output_av</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of temporally averaged 2d/3d data before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_dopr"><span style="font-weight: bold;">skip_time_dopr</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of vertical profile data before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_dosp"><span style="font-weight: bold;">skip_time_dosp</span></a></td>
+      <td>P</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of spectra data before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_do2d_xy"><span style="font-weight: bold;">skip_time_do2d_xy</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of instantaneous horizontal cross section data before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_do2d_xz"><span style="font-weight: bold;">skip_time_do2d_xz</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of instantaneous vertical (xz) cross section data before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_do2d_yz"><span style="font-weight: bold;">skip_time_do2d_yz</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of instantaneous vertical (yz) cross section data before this interval has passed (in s).<br>
+      </td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.2.html#skip_time_do3d"><span style="font-weight: bold;">skip_time_do3d</span></a></td>
+      <td>R</td>
+      <td>R</td>
+      <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
+data_output</a></span></td>
+      <td>No output of instantaneous 3d volume data before this interval has passed (in s).</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="file:///home/raasch/public_html/PALM_group/doc/app/chapter_4.2.html#spectra_direction"><b>slicer_range_limits_dvrp</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R(2,10)<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><span style="font-style: italic;">10
+* (-1,1)</span></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Ranges
+of values to which a color table has to be mapped (units of the
+respective quantity).</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#spectra_direction"><b>spectra_direction</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 2 (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>10 * ' '</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Direction(s) along which spectra are to be calculated. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#statistic_regions"><b>statistic_regions</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Number of additional user-defined subdomains for which
+statistical analysis
+and corresponding output (profiles, time series) shall be made.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#superelevation"><b>superelevation</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Superelevation factor for the vertical coordinate. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#superelevation_x"><b>superelevation_x</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Superelevation factor for the horizontal (x) coordinate.
+      <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#superelevation_y"><b>superelevation_y</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Superelevation factor for the
+horizontal (y) coordinate. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#surface_heatflux"><b>surface_heatflux</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><span style="font-style: italic;">no prescribed heatflux</span></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Kinematic sensible heat flux at the bottom surface (in K m/s).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#surface_pressure"><b>surface_pressure</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>1013.25</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Atmospheric pressure at the surface (in hPa)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#surface_scalarflux"><b>surface_scalarflux</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>0.0</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Scalar flux at
+the surface
+(in kg/(m<sup>2</sup> s)). <br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#surface_waterflux"><b>surface_waterflux</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Kinematic water flux near the surface (in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#s_surface"><b>s_surface</b></a></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>0.0</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Surface value of
+the passive
+scalar (in kg/m<sup>3</sup>). <br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_surface_initial_change"><b>s_surface_initial_change</b></a></b></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>0.0</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Change in
+surface scalar
+concentration to be made at the
+beginning of the 3d run (in kg/m<sup>3</sup>). <br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_vertical_gradient"><b>s_vertical_gradient</b></a></b></b></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">I<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">R(10)<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>10 * 0</i><i>.0</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Scalar
+concentration
+gradient(s) of the initial scalar
+concentration profile (in kg/m<sup>3 </sup>/
+100 m). <br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.1.html#s_vertical_gradient_level"><span style="font-weight: bold;">s_vertical_gradient_level</span></a></td>
+      <td>I</td>
+      <td>R(10)</td>
+      <td><span style="font-style: italic;">10 * 0.0</span></td>
+      <td>Height level from which on the scalar gradient defined by <a href="chapter_4.1.html#s_vertical_gradient">s_vertical_gradient</a>
+is effective (in m).</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#termination_time_needed"><b>termination_time</b></a>&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#termination_time_needed">&nbsp;<b>_needed</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>35.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>CPU time needed for terminal actions at the end of a run
+in
+batch mode (in s).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#threshold"><b>threshold</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>P</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R (10)</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Threshold value for which an isosurface is to be created
+by
+the <span style="font-weight: bold;">dvrp</span>
+software. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#timestep_scheme"><b>timestep_scheme</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>C * 20</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>'runge-kutta-3'</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Time step scheme to be used for integration of the prognostic
+variables. <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td><a href="chapter_4.1.html#topography"><span style="font-weight: bold;">topography</span></a></td>
+
+
+
+
+
+
+
+      <td>I</td>
+
+
+
+
+
+
+
+      <td>C * 40</td>
+
+
+
+
+
+
+
+      <td><span style="font-style: italic;">'flat'</span></td>
+
+
+
+
+
+
+
+      <td>Topography mode.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ug_surface"><b>ug_surface</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>u-component of the geostrophic wind at the surface (in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.1.html#ug_vertical_gradient"><span style="font-weight: bold;">ug_vertical_gradient</span></a></td>
+      <td>I</td>
+      <td>R(10)</td>
+      <td><span style="font-style: italic;">10 * 0.0</span></td>
+      <td>Gradient(s) of the initial
+profile of the&nbsp; u-component of the geostrophic wind (in 1/100s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.1.html#ug_vertical_gradient_level"><span style="font-weight: bold;">ug_vertical_gradient_level</span></a></td>
+      <td>I</td>
+      <td>R(10)</td>
+      <td><span style="font-style: italic;">10 * 0.0</span></td>
+      <td>Height level from which on the
+gradient defined by <a href="chapter_4.1.html#ug_vertical_gradient">ug_vertical_gradient</a>
+is effective (in m).<br>
+
+
+
+
+
+
+
+
+
+
+
+      </td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ups_limit_e"><b>ups_limit_e</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Subgrid-scale turbulent kinetic energy difference used
+as
+criterion for applying the upstream scheme when upstream-spline
+advection is switched on (in m<sup>2</sup>/s<sup>2</sup>).
+&nbsp;</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ups_limit_pt"><b>ups_limit_pt</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Temperature difference used as criterion for
+applying&nbsp;
+the upstream scheme when upstream-spline advection&nbsp; is
+switched on
+(in K). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ups_limit_u"><b>ups_limit_u</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Velocity difference (u-component) used as criterion for
+applying the upstream scheme
+when upstream-spline advection is switched on (in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ups_limit_v"><b>ups_limit_v</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Velocity difference (v-component) used as criterion for
+applying the upstream scheme
+when upstream-spline advection is switched on (in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#ups_limit_w"><b>ups_limit_w</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Velocity difference (w-component) used as criterion for
+applying the upstream scheme
+when upstream-spline advection is switched on (in m/s). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.2.html#use_particle_tails"><span style="font-weight: bold;">use_particle_tails</span></a></td>
+      <td>P</td>
+      <td>L</td>
+      <td>.F.</td>
+      <td>Give particles a tail.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#use_prior_plot1d_parameters"><b>use_prior_plot1d</b></a>&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#use_prior_plot1d_parameters">&nbsp;<b>_parameters</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="width: 57%; text-align: left; vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p>Additional plot of vertical profile data with <span style="font-weight: bold;">profil</span> from
+preceding runs of the
+job chain.&nbsp; </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#use_sgs_for_particles"><span style="font-weight: bold;">use_sgs_for_particles</span></a></td>
+      <td align="undefined" valign="undefined">P</td>
+      <td align="undefined" valign="undefined">L</td>
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
+      <td align="undefined" valign="undefined">Use subgrid-scale velocities for particle advection.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#use_surface_fluxes"><b>use_surface_fluxes</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.F.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to steer the treatment of the subgrid-scale
+vertical
+fluxes within the diffusion terms at k=1 (bottom boundary).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#use_ug_for_galilei_tr"><b>use_ug_for_galilei_tr</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.T.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Switch to determine the translation velocity in case
+that a
+Galilean transformation is used.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#use_upstream_for_tke"><span style="font-weight: bold;">use_upstream_for_tke</span></a></td>
+      <td align="undefined" valign="undefined">I</td>
+      <td align="undefined" valign="undefined">L</td>
+      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
+      <td align="undefined" valign="undefined">Parameter to choose the advection/timestep scheme to be used for the subgrid-scale TKE.</td>
+    </tr>
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#vertical_particle_advection"><b>vertical_particle_advection</b></a><br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">L<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>.T.</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Switch on/off
+vertical
+particle transport.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#vg_surface"><b>vg_surface</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>0.0</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>v-component of the geostrophic wind at the surface (in m/s).</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+      <td><a href="chapter_4.1.html#vg_vertical_gradient"><span style="font-weight: bold;">vg_vertical_gradient</span></a></td>
+      <td>I</td>
+      <td>R(10)</td>
+      <td><span style="font-style: italic;">10 * 0.0</span></td>
+      <td>Gradient(s) of the initial
+profile of the&nbsp; v-component of the geostrophic wind (in 1/100s).</td>
+    </tr>
+    <tr>
+      <td><a href="chapter_4.1.html#vg_vertical_gradient_level"><span style="font-weight: bold;">vg_vertical_gradient_level</span></a></td>
+      <td>I</td>
+      <td>R(10)</td>
+      <td><span style="font-style: italic;">10 * 0.0</span></td>
+      <td>Height level from which on the
+gradient defined by <a href="chapter_4.1.html#vg_vertical_gradient">vg_vertical_gradient</a>
+is effective (in m).</td>
+    </tr>
+    <tr valign="top">
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.1.html#wall_adjustment"><b>wall_adjustment</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>I</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>L</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>.T.</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Parameter to restrict the mixing length in the vicinity
+of the
+bottom
+boundary.</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+      <td><a href="chapter_4.1.html#wall_heatflux"><span style="font-weight: bold;">wall_heatflux</span></a></td>
+
+
+
+
+      <td>I</td>
+
+
+
+
+      <td>R(5)</td>
+
+
+
+
+      <td><span style="font-style: italic;">5 * 0.0</span></td>
+
+
+
+
+      <td>Prescribed kinematic sensible heat flux in W m<sup>-2</sup>&nbsp;at the five topography faces.</td>
+
+
+
+
+    </tr>
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#write_particle_statistics"><b>write_particle_</b></a>
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#write_particle_statistics"><b>statistics</b></a>
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">P<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">L<br>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;"><i>.F.</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;">Switch on/off
+output of
+particle informations.</td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#z_max_do1d"><b>z_max_do1d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%"><i>zu(nzt+1) (model top)</i></td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Height level up to which horizontally averaged profiles
+are to
+be
+plotted with <span style="font-weight: bold;">profil</span>
+(in
+m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#z_max_do1d_normalized"><b>z_max_do1d</b></a>&nbsp;&nbsp;
+      <br>
+
+
+
+
+
+
+
+      <a href="chapter_4.2.html#z_max_do1d_normalized">&nbsp;<b>_normalized</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>determined by plot <br>
+
+
+
+
+
+
+
+data</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Normalized height level up to which horizontally
+averaged
+profiles are to be plotted with <span style="font-weight: bold;">profil</span>.
+      <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+    <tr>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="15%">
+      
+      
+      
+      
+      
+      
+      <p><a href="chapter_4.2.html#z_max_do2d"><b>z_max_do2d</b></a></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="5%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="7%">
+      
+      
+      
+      
+      
+      
+      <p>R</p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="16%">
+      
+      
+      
+      
+      
+      
+      <p><i>zu(nz)</i></p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+      <td style="vertical-align: middle;" width="57%">
+      
+      
+      
+      
+      
+      
+      <p>Height level up to which 2d cross sections are to be
+plotted
+with <span style="font-weight: bold;">iso2d</span>
+(in m). <br>
+
+
+
+
+
+
+
+      </p>
+
+
+
+
+
+
+
+      </td>
+
+
+
+
+
+
+
+    </tr>
+
+
+
+
+
+
+
+  
+  
+  
+  
+  
+  
+  </tbody>
+</table>
+
+
+
+
+
+
+
+<hr>
+<p><br>
+
+
+
+
+
+
+
+<font color="#000080"><a href="chapter_4.5.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_5.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></p>
+
+
+
+
+
+
+
+<p>&nbsp;<i>Last change:&nbsp;&nbsp;</i> 07/11/06 (ML) </p>
+
+
+
+
+
+
+
+<p><br>
+
+
+
+
+
+
+
+<br>
+
+
+
+
+
+
+
+<br>
+
+
+
+
+
+
+
+</p>
+
+
+
+
+
+
+
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_5.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_5.0.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_5.0.html	(revision 5)
@@ -0,0 +1,277 @@
+<!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 5.0</title>
+  <meta name="GENERATOR" content="StarOffice 7  (Win32)">
+  <meta name="AUTHOR" content="Siegfried Raasch">
+  <meta name="CREATED" content="20041103;12380720">
+  <meta name="CHANGED" content="20041123;15532356">
+  <meta name="KEYWORDS" content="parallel LES model">
+  <style>
+	<!--
+		@page { size: 21cm 29.7cm }
+	-->
+	</style>
+</head>
+<body dir="ltr" lang="en-US">
+<h2 style="line-height: 100%;"><font size="4">5.0 Installation of the
+model</font></h2>
+<p style="line-height: 100%;"><font color="#000000">This chapter
+describes the installation of PALM on the Linux workstation
+cluster of IMUK and a suitable remote computer (host), on which the
+model runs are actually carried out. The local cluster is used to
+start the batch job with <b>mrun</b> and to analyze the results
+produced by the model. In batch mode, runs can be carried on the
+IBM-Regatta
+system of the HLRN, on an IBM-Regatta at KISTI, Korea </font><font
+ color="#000000">(via a local
+DEC-Alpha-workstation at the Department of Atmospheric Sciences of the
+Yonsei University, Seoul)</font><font color="#000000">, and on an
+NEC-SX6 at DKRZ. The examples given in this chapter refer to an
+installation of PALM on the IMUK cluster, considering the IBM-Regatta
+system of
+the HLRN as the remote computer. </font>
+</p>
+<p style="line-height: 100%;">The installation process requires a valid
+account on the IMUK cluster and on the remote host as well. In the
+following the IMUK workstation is called the local host. <br>
+&nbsp; </p>
+<ul>
+  <p style="line-height: 100%;">All hosts (local as well as remote) are
+accessed via the secure shell (ssh). The user must establish
+passwordless login using the private/public-key mechanism (see e.g. the
+  <a href="http://www.hlrn.de/doc/ssh/index.html">HLRN documentation</a>).
+  <b>To ensure proper function of mrun, passwordless login must be
+established in both directions, from the local to the remote host as
+well as from the remote to the local host!</b> Test this by carrying
+out e.g. on the local host:</p>
+  <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+ssh&nbsp; &lt;username on remote host&gt;@&lt;remote IP-address&gt;</span><br>
+  </p>
+  <p style="line-height: 100%;">and on the remote host:<br>
+  </p>
+  <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+ssh&nbsp; &lt;username on local host&gt;@&lt;local IP-adddress&gt;</span><br>
+  </p>
+  <p style="line-height: 100%;">In both cases you should nnot be
+prompted for a password. <b>Before continuing the further installation
+process, this must be absolutely guaranteed!</b> This must also be
+guaranteed for <b>all</b> other remote hosts, on which PALM shall run.</p>
+</ul>
+<p style="line-height: 100%;">In the <b>first installation step</b> a
+set of directories must be created both on the local and on the
+remote host. These directories are: </p>
+<ul>
+  <pre style="line-height: 100%;"><font size="2">~/job_queue</font><br><font
+ size="2">~/palm</font><br><font size="2">~/palm/current_version</font><br><font
+ size="2">~/palm/current_version/SOURCE</font><br><font size="2">~/palm/current_version/JOBS</font></pre>
+</ul>
+<p style="line-height: 100%;">The names of these directories are
+freely selectable (except <tt><font size="2">~/job_queue</font></tt>),
+however new users should use them as suggested, since many
+examples in this documentation as well as all example files are
+assuming these settings. </p>
+<p style="line-height: 100%;"><font color="#000000">In the <b>second
+step</b> the PALM source code must be copied into directory </font><tt><font
+ size="2"><font color="#000000">~/palm/current_version/SOURCE</font></font></tt><font
+ color="#000000"> on the local host by carrying out the following
+commands: </font>
+</p>
+<ul>
+  <pre style="line-height: 100%;"><font color="#000000">cd ~/palm/current_version/SOURCE</font><br><font
+ color="#000000">ln -s /home/raasch/public_html/PALM_group/INSTALL/RCS .</font><br><font
+ color="#000000">cp RCS/*,v .</font><br><font color="#000000">co *,v</font><br><font
+ color="#000000">rm -rf *,v</font></pre>
+</ul>
+<p style="line-height: 100%;"><font color="#000000">Afterwards, the
+directory</font><font color="#000000"> </font><tt><font size="2"><font
+ color="#000000">~/palm/current_version/SOURCE</font></font></tt><font
+ color="#000000">
+should contain</font><font color="#000000"> all PALM routines as well
+as a file with the name </font><tt><font size="2"><font color="#000000">Makefile</font></font></tt><font
+ color="#000000">. </font><font color="#000000">All files are
+write-protected, the source code files end on </font><tt><font
+ style="font-size: 11pt;" size="2"><font color="#000000">.f90</font></font></tt><font
+ color="#000000">.
+The user should never modify these files without further knowledge of
+the PALM code. </font>
+</p>
+<p style="line-height: 100%;"><font color="#000000">To avoid the
+re-compilation of the complete source code for each model run, PALM
+willl be pre-compiled once on the remote host. Due to the use of
+FORTRAN modules in the source code, the subroutines must be compiled
+in a certain sequence. Therefore the so-called <i>make</i> mechanism
+is used (see the respective man-page of the Unix operating system),
+requiring the file </font><tt><font color="#000000">Makefile</font></tt><font
+ color="#000000">,
+in which the dependencies are described. The compiled sources (object
+files) are
+stored on the remote computer in the directory
+</font><tt><font color="#000000">~/palm/current_version/SOURCE/MAKE_DEPOSITORY</font></tt><font
+ color="#000000">.<br>
+&nbsp;<br>
+For pre-compilation the user has to</font> call <font color="#000000">the
+command <b>mbuild</b>, which requires some pre-settings. The path
+variable must be extended on <b>both</b> computers, so that the
+commands <b>mbuild</b> and <b>mrun</b> as well as further routines
+needed by <span style="font-weight: bold;">mrun</span> can be found.
+This is achieved on the local computer via:: </font>
+</p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ color="#000000">PATH=$PATH:/home/raasch/pub,</font></pre>
+</ul>
+<p style="line-height: 100%;"><font color="#000000">and on the IBM
+Regatta
+system of the HLRN via</font></p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ color="#000000">PATH=$PATH:/home/h/niksiraa/pub.</font></pre>
+</ul>
+<p style="line-height: 100%;"><font color="#000000">These path
+extensions must be automatically set in the profiles of the local and
+remote host (file "~/.myprofile" at IMUK, file "~/.profile" at HLRN)</font><font
+ color="#000000">.
+</font></p>
+<p style="line-height: 100%;"><font color="#000000">It is now assumed
+that the working directory is
+</font><tt><font color="#000000">~/palm/current_version/SOURCE</font></tt><font
+ color="#000000">
+on the local host. Compilation of the PALM code via <b>mbuild </b>needs
+a </font><a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config"><font
+ color="#000080">configuration
+file</font></a><font color="#000080">,</font><font color="#000000">
+which must be copied to the working directory under name
+</font><tt><font color="#000000">.mrun.config</font></tt><font
+ color="#000000">
+(please click on the link with &lt;SHIFT&gt; + left mouse button)</font><font
+ color="#000000">. This file contains typical installation parameters
+like compiler name, compiler options, etc.
+for a set of different remote hosts. This file is also needed later on
+for starting the model runs. </font>
+</p>
+<p style="line-height: 100%;"><font color="#000000">In the
+configuration file </font><tt><font color="#000000">.mrun.config</font></tt><font
+ color="#000000">
+the user name on the respective remote host must be entered. In lines
+like</font>
+</p>
+<ul>
+  <p style="line-height: 100%;"><tt><font color="#000000">%
+remote_username &lt;username&gt; &lt;remote-computer-shortcut&gt;</font></tt></p>
+</ul>
+the string "<span style="font-family: monospace;">&lt;username&gt;</span>"
+has to be replaced by the actual name of the user on the respective
+remote host (e.g. "nik....." on HLRN).<font color="#000000">
+</font>
+<p style="line-height: 100%;"><font color="#000000">After this, the
+pre-compilation for the IBM-Regatta of HLRN can be started by entering</font><font
+ color="#000000"> </font>
+</p>
+<ul>
+  <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
+ color="#000000">mbuild - h ibmh  .</font></pre>
+</ul>
+<p style="line-height: 100%;"><span style="font-family: monospace;">mbuild</span>
+will prompt some queries<font color="#000000">, which must all be
+answered "y" by the user. The compiling process </font><font
+ color="#000000">will take some time. </font><font color="#000000"><span
+ style="font-family: monospace;">mbuild</span></font><font
+ color="#000000"> transfers the respective compiler calls to the remote
+host where they are carried out interactively. You can follow the
+progress at the terminal window, where also error messages
+are displayed (hopefully not for this standard installation). By just
+entering </font>
+</p>
+<blockquote style="line-height: 100%;"><tt><font color="#000000">mbuild</font></tt></blockquote>
+<p style="line-height: 100%;"><font color="#000000">PALM will
+be (consecutively) pre-compiled for all remote hosts listed in
+the configuration file. </font>
+</p>
+<p style="line-height: 100%;"><font color="#000000">As a last step,
+after the compilation has been finished, the PALM installation has to
+be verified. For this
+purpose a simple test run is carried out. This once again requires the <b>mrun
+</b>configuration file (described in </font><a href="chapter_3.2.html"><font
+ color="#000080">chapter
+3.2</font></a><font color="#000000">), as well as the </font><a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d"><font
+ color="#000080">parameter
+file</font></a><font color="#000000"> (described in </font><a
+ href="chapter_4.4.html"><font color="#000080">chapter
+4.4</font></a>)<font color="#000000">. The parameter file must be&nbsp;
+copied to<br>
+</font></p>
+<p style="line-height: 100%;"><tt><font color="#000000">&nbsp;&nbsp;&nbsp;
+~/palm/current_version/JOBS/example/INPUT/example_p3d</font></tt><font
+ color="#000000">&nbsp;&nbsp; .
+</font></p>
+<p style="line-height: 100%;"><font color="#000000">The test run can
+now be started by entering the command: </font>
+</p>
+<pre
+ style="margin-left: 1cm; margin-right: 1cm; margin-bottom: 0.5cm; line-height: 100%;"><font
+ color="#000000">mrun -d example -h ibmh -K parallel -X 8 -T 8 -t 500 -q cdev -r d3# pr#</font></pre>
+<p style="line-height: 100%;"><font color="#000000">This specific run
+will be carried out on 8 PEs and is allowed to use up to 500 seconds
+CPU time. After pressing &lt;return&gt;, the most important settings of
+the job are displayed at the terminal window
+and the user is prompted for o.k. (</font><tt><font color="#000000">y</font></tt><font
+ color="#000000">).
+Afterwards a message of the queuing system like <i>Request</i> 
+
+<i>Submitted to queue
+ by
+ </i>should be displayed. Now the job is
+queued either started immediately or at a later time, depending on the
+current workload of the remote host. Provided that it is executed
+immediately and that all things work as designed, the job protocol of
+this run will appear under the file name </font><tt><font
+ color="#000000">~/job_queue/ibmh_example</font></tt><font
+ color="#000000"> no more than 3 minutes later. The content of this
+file should be carefully examined for any error messages.</font>
+</p>
+<p style="line-height: 100%;">Beside the job protocol and according to
+the configuration file and arguments given for <b>mrun</b>
+options <tt>-d</tt> and <tt>-r,</tt>further files should be found in
+the
+directories<br>
+</p>
+<p style="line-height: 100%; font-family: monospace;">&nbsp;&nbsp;&nbsp;
+~/palm/current_version/JOBS/example/MONITORING
+<br>
+</p>
+<p style="line-height: 100%;">and</p>
+<p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+~/palm/current_version/JOBS/example/OUTPUT&nbsp; .
+</span><br>
+</p>
+<p style="line-height: 100%;">Please compare the contents of file</p>
+<p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+~/palm/current_version/JOBS/example/MONITORING/ibmh_example_rc</span><br>
+</p>
+<p style="line-height: 100%;">with those of the <a
+ href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_rc">result
+example file</a> (e.g. with the help of the UNIX-command <span
+ style="font-family: monospace;">diff</span>). There should be not a
+single difference between these two files. <font color="#000000">If
+the file contents are identical, the installation is successfully
+completed.</font> </p>
+<p style="line-height: 100%;">If you have any problems with the PALM
+installation, the members of the PALM working group are pleased to
+help you. &nbsp; </p>
+<hr>
+<p style="line-height: 100%;"><font color="#000080"><font
+ color="#000080"><a href="chapter_4.6.html"><font color="#000080"><img
+ src="left.gif" name="Grafik1" align="bottom" border="2" height="32"
+ width="32"></font></a><a href="Inhaltsverzeichnis.html"><font
+ color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
+ border="2" height="32" width="32"></font></a><a href="chapter_5.1.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> 20/04/05 (SR) </p>
+</body>
+</html>
Index: palm/trunk/DOC/app/chapter_5.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_5.1.html	(revision 5)
+++ palm/trunk/DOC/app/chapter_5.1.html	(revision 5)
@@ -0,0 +1,52 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head>
+  <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 5.1</title>
+  
+  <meta content="StarOffice 7  (Win32)" name="GENERATOR">
+  <meta content="Siegfried Raasch" name="AUTHOR">
+  <meta content="20041103;12395815" name="CREATED">
+  <meta content="20041119;12321236" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS"></head>
+
+<body lang="en-US" dir="ltr">
+<h3>5.1 Installation of new versions</h3>
+<p>The PALM developer group announces code revisions within the
+<a href="../tec/technical_documentation.html">technical/numerical
+documentation</a>. Users can carry out version updates by changing into
+the working directory
+<span style="font-family: monospace;">~/palm/current_version/SOURCE</span>
+and entering </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm;">co *.f90.</pre>
+</ul>
+<p>This updates all source code files. </p>
+<p><b>Note:</b> if the user should have changed this source code, then
+these changes are certainly lost! This is one reason why
+modifications of the basic source code should be omitted and
+be restricted to the user-interface only
+(see <a href="chapter_3.5.html">chapter
+3.5</a>). </p>
+<p>After updating the source code the pre-compiled code must be updated
+via </p>
+<ul>
+  <pre style="margin-bottom: 0.5cm;">mbuild -h ibmh</pre>
+</ul>
+<p>on the IBM-Regatta "hanni" of the HLRN or via</p>
+<blockquote style="font-family: monospace;">mbuild</blockquote>
+<p>on all remote hosts listed in the configuration file
+<span style="font-family: monospace;">.mrun.config</span>. </p>
+<p>As a last step, a suitable test run should be carried out. It should
+be carefully examined whether and how the results created by the new
+version differ from those of the old version. Possible discrepancies
+which go beyond the ones announced in the <a href="../tec/technical_documentation.html">technical/numerical
+documentation</a>
+should be communicated as soon as possible to the PALM developer group.
+</p>
+<hr>
+<p><br>
+<font color="#000080"><font color="#000080"><a href="chapter_5.0.html"><font color="#000080"><img width="32" height="32" border="2" align="bottom" name="Grafik1" src="left.gif"></font></a><a href="index.html"><font color="#000080"><img width="32" height="32" border="2" align="bottom" name="Grafik2" src="up.gif"></font></a></font></font><br>
+&nbsp;
+<br>
+&nbsp;<span style="font-style: italic;">Last change:</span> 20/04/05
+(SR)<br>
+</p>
+</body></html>
Index: palm/trunk/DOC/app/index.html
===================================================================
--- palm/trunk/DOC/app/index.html	(revision 5)
+++ palm/trunk/DOC/app/index.html	(revision 5)
@@ -0,0 +1,227 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml"><head>
+  <meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
+  <meta content="Word.Document" name="ProgId">
+  <meta content="Microsoft Word 11" name="Generator">
+  <meta content="Microsoft Word 11" name="Originator">
+  <link href="index-Dateien/filelist.xml" rel="File-List">
+  <link href="index-Dateien/editdata.mso" rel="Edit-Time-Data"><!--[if !mso]>
+<style>
+v\:* {behavior:url(#default#VML);}
+o\:* {behavior:url(#default#VML);}
+w\:* {behavior:url(#default#VML);}
+.shape {behavior:url(#default#VML);}
+</style>
+<![endif]--><title>PALM table of contents</title><!--[if gte mso 9]><xml>
+ <w:WordDocument>
+  <w:SpellingState>Clean</w:SpellingState>
+  <w:GrammarState>Clean</w:GrammarState>
+  <w:HyphenationZone>21</w:HyphenationZone>
+  <w:ValidateAgainstSchemas/>
+  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
+  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
+  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
+  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
+ </w:WordDocument>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
+ </w:LatentStyles>
+</xml><![endif]-->
+
+  
+
+  <style>
+<!--
+ /* Font Definitions */
+ @font-face
+	{font-family:Thorndale;
+	panose-1:2 2 6 3 5 4 5 2 3 4;
+	mso-font-charset:0;
+	mso-generic-font-family:roman;
+	mso-font-pitch:variable;
+	mso-font-signature:647 0 0 0 159 0;}
+ /* Style Definitions */
+ p.MsoNormal, li.MsoNormal, div.MsoNormal
+	{mso-style-parent:"";
+	margin:0cm;
+	margin-bottom:.0001pt;
+	mso-pagination:widow-orphan;
+	font-size:12.0pt;
+	font-family:"Times New Roman";
+	mso-fareast-font-family:"Times New Roman";
+	color:black;}
+a:link, span.MsoHyperlink
+	{color:blue;
+	text-decoration:underline;
+	text-underline:single;}
+a:visited, span.MsoHyperlinkFollowed
+	{color:blue;
+	text-decoration:underline;
+	text-underline:single;}
+p
+	{mso-margin-top-alt:auto;
+	margin-right:0cm;
+	mso-margin-bottom-alt:auto;
+	margin-left:0cm;
+	mso-pagination:widow-orphan;
+	font-size:12.0pt;
+	font-family:"Times New Roman";
+	mso-fareast-font-family:"Times New Roman";
+	color:black;}
+span.SpellE
+	{mso-style-name:"";
+	mso-spl-e:yes;}
+span.GramE
+	{mso-style-name:"";
+	mso-gram-e:yes;}
+@page Section1
+	{size:595.3pt 841.9pt;
+	margin:70.85pt 70.85pt 2.0cm 70.85pt;
+	mso-header-margin:35.4pt;
+	mso-footer-margin:35.4pt;
+	mso-paper-source:0;}
+div.Section1
+	{page:Section1;}
+-->
+  </style><!--[if gte mso 10]>
+<style>
+ /* Style Definitions */
+ table.MsoNormalTable
+	{mso-style-name:"Normale Tabelle";
+	mso-tstyle-rowband-size:0;
+	mso-tstyle-colband-size:0;
+	mso-style-noshow:yes;
+	mso-style-parent:"";
+	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
+	mso-para-margin:0cm;
+	mso-para-margin-bottom:.0001pt;
+	mso-pagination:widow-orphan;
+	font-size:10.0pt;
+	font-family:"Times New Roman";
+	mso-ansi-language:#0400;
+	mso-fareast-language:#0400;
+	mso-bidi-language:#0400;}
+</style>
+<![endif]-->
+  <meta content="Marcus Oliver Letzel" name="AUTHOR">
+  <meta content="20041117;10075861" name="CREATED">
+  <meta content="20041119;12040014" name="CHANGED">
+  <meta content="parallel LES model" name="KEYWORDS"><!--[if gte mso 9]><xml>
+ <u1:DocumentProperties>
+  <u1:Author>pooluser</u1:Author>
+  <u1:LastAuthor>pooluser</u1:LastAuthor>
+  <u1:Revision>2</u1:Revision>
+  <u1:Created>2004-11-19T10:58:00Z</u1:Created>
+  <u1:LastSaved>2004-11-19T10:59:00Z</u1:LastSaved>
+  <u1:Pages>1</u1:Pages>
+  <u1:Words>559</u1:Words>
+  <u1:Characters>3522</u1:Characters>
+  <u1:Company>IMUK</u1:Company>
+  <u1:Lines>29</u1:Lines>
+  <u1:Paragraphs>8</u1:Paragraphs>
+  <u1:CharactersWithSpaces>4073</u1:CharactersWithSpaces>
+  <u1:Version>11.6360</u1:Version>
+ </u1:DocumentProperties>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <u2:WordDocument>
+  <u2:SpellingState>Clean</u2:SpellingState>
+  <u2:GrammarState>Clean</u2:GrammarState>
+  <u2:HyphenationZone>21</u2:HyphenationZone>
+  <u2:ValidateAgainstSchemas/>
+  <u2:SaveIfXMLInvalid>false</u2:SaveIfXMLInvalid>
+  <u2:IgnoreMixedContent>false</u2:IgnoreMixedContent>
+  <u2:AlwaysShowPlaceholderText>false</u2:AlwaysShowPlaceholderText>
+  <u2:BrowserLevel>MicrosoftInternetExplorer4</u2:BrowserLevel>
+ </u2:WordDocument>
+</xml><![endif]--><!--[if gte mso 9]><xml>
+ <u3:LatentStyles DefLockedState="false" LatentStyleCount="156">  </u3:LatentStyles>
+</xml><![endif]--></head>
+<body style="" lang="DE" link="blue" vlink="blue">
+<div class="Section1">
+<p style="margin-bottom: 0.0001pt;"><span style="font-size: 36pt; font-family: Thorndale;">PALM </span><span style="font-family: Thorndale;">a <span class="SpellE"><b>pa</b>rallelized</span>
+<b>L</b>ES <span class="SpellE"><b>m</b>odel</span>
+<o:p></o:p></span></p>
+<div style="text-align: center;" class="MsoNormal" align="center"><span style="font-family: Thorndale;">
+<hr align="center" size="2" width="100%"></span></div>
+<p><span style="font-family: Thorndale;" lang="EN-GB"><br>
+</span><span style="font-size: 18pt; font-family: Thorndale;" lang="EN-GB">Documentation </span><span style="font-family: Thorndale;" lang="EN-GB"><o:p></o:p></span></p>
+<p><span style="font-family: Thorndale;" lang="EN-GB">Current
+model
+version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.1a<br>
+<a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/Aenderungen.html"><span class="GramE">Last</span></a></span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/Aenderungen.html"><span style="" lang="EN-GB"> change of</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> this
+documentation:&nbsp;&nbsp;&nbsp; 15/03/06 <o:p></o:p></span></p>
+<div style="text-align: center;" class="MsoNormal" align="center"><span style="font-family: Thorndale;">
+<hr align="center" size="2" width="100%"></span></div>
+<p><span style="font-size: 18pt; font-family: Thorndale;" lang="EN-GB">Table
+of contents</span><span style="font-family: Thorndale;" lang="EN-GB"> <br>
+&nbsp; <o:p></o:p></span></p>
+<p style="margin-left: 36pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_1.0.html"><span style="" lang="EN-GB">1.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Introduction <o:p></o:p></span></p>
+<p style="margin-left: 36pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_2.0.html"><span style="" lang="EN-GB">2.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Basic
+techniques of the LES model and its parallelization <o:p></o:p></span></p>
+<p style="margin: 5pt 0cm 0.0001pt 36pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.0.html"><span style="" lang="EN-GB">3.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Execution of
+model runs<o:p></o:p></span></p>
+<p style="margin: 0cm 0cm 0.0001pt 72pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.1.html"><span style="" lang="EN-GB">3.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Job control
+with <span class="SpellE"><b>mrun</b></span> <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.2.html"><span style="" lang="EN-GB">3.2</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Example of a
+minimum configuration file <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.3.html"><span style="" lang="EN-GB">3.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB">
+Initialization and restart runs <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.4.html"><span style="" lang="EN-GB">3.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Input and
+output files <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.5.html"><span style="" lang="EN-GB">3.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Programming
+of user-defined code extensions <o:p></o:p></span></p>
+<p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.5.1.html"><span style="" lang="EN-GB">3.5.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Interfaces for
+user-defined&nbsp; code <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.5.2.html"><span style="" lang="EN-GB">3.5.2</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Definition of
+user-defined parameters <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.5.3.html"><span style="" lang="EN-GB">3.5.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Definition of
+<span class="SpellE">user-defined subdomains</span></span></p><p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;" lang="EN-GB"><span class="SpellE"></span> <a href="chapter_3.5.4.html">3.5.4</a> User-defined output quantities<br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.5.5.html"><span style="" lang="EN-GB">3.5.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Compiling and linking
+user-defined code <o:p></o:p></span></p>
+<p style="margin: 0cm 0cm 5pt 72pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.6.html"><span style="" lang="EN-GB">3.6</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Interactive mode and
+debugging <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_3.7.html"><span style="" lang="EN-GB">3.7</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Optional
+software packages<o:p></o:p></span></p>
+<p style="margin: 12pt 0cm 0.0001pt 36pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.0.html"><span style="" lang="EN-GB">4.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Steering
+parameters <o:p></o:p></span></p>
+<p style="margin: 0cm 0cm 0.0001pt 72pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html"><span style="" lang="EN-GB">4.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB">
+Initialization parameters <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html"><span style="" lang="EN-GB">4.2</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Runtime
+parameters and package parameters <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.3.html"><span style="" lang="EN-GB">4.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> User-defined
+parameters <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.4.html"><span style="" lang="EN-GB">4.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Example of a
+minimum parameter set <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.html"><span style="" lang="EN-GB">4.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Data analysis and
+visualization <o:p></o:p></span></p>
+
+<p style="margin: 0cm 0cm 0.0001pt 108pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.1.html"><span style="" lang="EN-GB">4.5.1</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> NetCDF data output<b></b><br>
+<a href="chapter_4.5.2.html">4.5.2</a> </span><span style="font-family: Thorndale;" lang="EN-GB">Plots of
+vertical profiles with <b>profil</b></span><br>
+<span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.3.html"><span style="" lang="EN-GB">4.5.3</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of time
+series with <b>profil</b> <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.4.html"><span style="" lang="EN-GB">4.5.4</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of 2D
+cross sections with <b>iso2d</b> <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.5.html"><span style="" lang="EN-GB">4.5.5</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of 3D
+volume data with <b>AVS</b> <br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.6.html"><span style="" lang="EN-GB">4.5.6</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of
+compressed 3D volume data with <b>AVS</b><br>
+</span><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.5.7.html"><span style="" lang="EN-GB">4.5.7</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Plots of <span class="SpellE">isosurfaces</span>, 2D cross sections and particles
+with <span class="SpellE"><b>dvrp</b></span><o:p></o:p></span></p>
+<p style="margin: 0cm 0cm 5pt 72pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.6.html"><span style="" lang="EN-GB">4.6</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Listing of the steering
+parameters in alphabetical&nbsp; order<o:p></o:p></span></p>
+<p style="margin: 12pt 0cm 0.0001pt 36pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_5.0.html"><span style="" lang="EN-GB">5.0</span></a></span><span style="font-family: Thorndale;" lang="EN-GB"> Installation
+of the model <o:p></o:p></span></p>
+<p style="margin: 0cm 0cm 5.1pt 72pt;"><span style="font-family: Thorndale;"><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_5.1.html">5.1</a>
+Installation of <span class="SpellE">new</span><span class="SpellE"></span>
+<span class="SpellE">versions</span><o:p></o:p></span></p>
+<p style="margin-bottom: 12pt;"><span style="font-family: Thorndale;"><br>
+<br>
+<br>
+<br>
+<br>
+<br style="">
+<!--[if !supportLineBreakNewLine]--><br style="">
+<!--[endif]--><o:p></o:p></span></p>
+</div>
+</body></html>
Index: palm/trunk/DOC/tec/technical_documentation.html
===================================================================
--- palm/trunk/DOC/tec/technical_documentation.html	(revision 5)
+++ palm/trunk/DOC/tec/technical_documentation.html	(revision 5)
@@ -0,0 +1,4533 @@
+<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
+<html><head>
+
+  
+  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
+
+  
+  <meta content="Mozilla/4.73 [en] (X11; U; HP-UX B.10.20 9000/782) [Netscape]" name="GENERATOR">
+
+  
+  <meta content="Siegfried Raasch" name="Author">
+
+  
+  <meta content="parallel LES model" name="Keywords"><title>PALM technical/numerical documentation</title></head>
+<body>
+
+<font size="+4">PALM&nbsp;&nbsp;
+</font>a
+<b>pa</b>rallelized
+<b>L</b>ES <b>m</b>odel
+<br>
+
+<hr width="100%">
+<br>
+
+<font size="+2">technical/numerical documentation</font>
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+<table nosave="" cellpadding="0" cellspacing="0">
+
+  <caption>&nbsp; <br>
+
+  </caption><tbody>
+
+  
+  </tbody><tbody>
+
+  
+  </tbody> <tbody>
+
+    <tr nosave="">
+
+      <td nosave=""><b>Current model version:</b></td>
+
+      <td><span style="font-weight: bold;">3.1b</span></td>
+
+    </tr>
+
+    <tr nosave="">
+
+      <td nosave=""><b>Last change of this document</b>:&nbsp;</td>
+
+      <td nosave=""><b>11/02/07</b></td>
+
+    </tr>
+
+  
+  </tbody>
+</table>
+
+<hr width="100%">
+<p><font size="+2">Table of contents</font>
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+</p>
+
+<ul>
+
+  <a href="#Kapitel1.0">1.0</a>&nbsp; History of changes
+  
+  <p><a href="#Kapitel2.0">2.0</a>&nbsp; How to change the model source
+code </p>
+
+  
+  <p><a href="#Kapitel3.0">3.0</a>&nbsp; Description of selected parts
+of
+the model source code <br>
+
+&nbsp;</p>
+
+</ul>
+
+<b>Please note: Parts of this document are still in German. We
+apologize
+for any inconvenience.</b>
+<br>
+
+&nbsp;
+<h2><a name="Kapitel1.0"></a>1.0&nbsp; History of changes</h2>
+
+The following table documents all changes to the model since July, 7th
+1998. Entries in the fourth column specify the type of the change:
+change&nbsp;
+of existing code (C), new code (N) or bugfix (B). More detailed
+information
+about the changes may be found in the header comment lines of the
+respective
+routines.
+<br>
+
+&nbsp;
+<br>
+
+<table nosave="" style="width: 100%;" border="1">
+
+  <caption>&nbsp; <br>
+
+  </caption><tbody>
+
+  
+  </tbody><tbody>
+
+  
+  </tbody> <tbody>
+
+    <tr>
+
+      <td><b>date</b></td>
+
+      <td><b>author</b></td>
+
+      <td><b>model</b> <br>
+
+      <b>version</b></td>
+
+      <td><b>type</b></td>
+
+      <td><b>description</b></td>
+
+      <td><b>affected routines</b></td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>06/07/98</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>C</td>
+
+      <td nosave="">&Auml;nderung von Default-Werten
+(initializing_actions, end_time,
+fcl_factor, use_prior_plot1d_parameters), zus&auml;tzliche
+&Uuml;berpr&uuml;fung
+von Parametern auf Zul&auml;ssigkeit (prandtl_layer, psolver, nx, ny,
+nz,
+fcl_factor), H&ouml;he der Schnittebenen der Horizontalschnitte wird
+auf
+Plots exakt ausgegeben (uv- bzw. w-Gitter).</td>
+
+      <td>modules, check_parameters, plot_2d</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>N</td>
+
+      <td>Neues Modul test_variables wird in (fast) allen
+Programmteilen benutzt
+(USE). <b>Wichtig</b>: dieses Modul steht in der Datei <tt>module_test.f90.
+D</tt>iese Datei mu&szlig; in der mrun- und add_library -
+Konfigurationsdatei
+bei der Variablen <tt>module_files</tt> aufgef&uuml;hrt werden.</td>
+
+      <td nosave="">(fast) alle&nbsp; <br>
+
+Neu: module_test</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>16/07/98</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>N</td>
+
+      <td nosave="">Anpassung an die T3E-Rechner in Juelich (cpp -
+Direktiven)</td>
+
+      <td>advec_s_bc, check_open, check_parameters, cpu_zeitmessung,
+init_pegrid,
+local_getenv, local_system, local_tremain, local_tremain_ini, poisfft</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>24/07/98</td>
+
+      <td>MS</td>
+
+      <td>1.0</td>
+
+      <td>C</td>
+
+      <td nosave="">Anpassung des Druckloesealgorithmusses an
+Vorgehensweise von
+Schmidt, Schumann und Volkert (DFVLR-Mitteilung 84-15, S. 20-26)&nbsp;</td>
+
+      <td>poisfft</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>27/07/98</td>
+
+      <td>MS</td>
+
+      <td>1.0</td>
+
+      <td>C</td>
+
+      <td nosave="">Berechnung von l in maketri geschieht nun
+ausserhalb der k-Schleife,
+da unabhaengig von k, dadurch Rechenzeitersparnis&nbsp;</td>
+
+      <td>poisfft</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>05/08/98</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>C</td>
+
+      <td>Entfernung der Sonderbehandlung der Advektionsterme
+(Piascek-Williams)
+bei k=1. Terme werden nun &uuml;berall gleich berechnet. Evtl. leichte
+Erh&ouml;hung der Varianzen in Oberfl&auml;chenn&auml;he.</td>
+
+      <td nosave="">advec_u_pw, advec_v_pw, advec_w_pw</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>C</td>
+
+      <td>Mischungsweganpassung (s. adjust_mixing_length) erfolgt nur
+noch bei
+k=1. Unrealistische sekund&auml;re Maxima in den Km-Profilen oberhalb
+der
+Prandtl-Schicht werden damit vermieden. Leichte &Auml;nderungen in den
+oberfl&auml;chennahen Turbulenzgr&ouml;&szlig;en sind die Folge.</td>
+
+      <td>diffusivities</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>B</td>
+
+      <td>Falsche Berechnung der ben&ouml;tigten CPU-Zeit pro Sekunde
+simulierter
+Zeit bei Fortsetzungsl&auml;ufen korrigiert.&nbsp;
+      
+      <p>Berechnung von cross_uxmin(1) und cross_uxmax(1) aus den
+Werten von
+ug und vg entfernt. Lieferte falsche Wertebereiche f&uuml;r Plots von
+Vertikalprofilen,
+wenn im ersten Koordinatenkreuz nicht die Windgeschwindigkeiten
+gezeichnet
+wurden.</p>
+
+      </td>
+
+      <td nosave="">header, check_parameters</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>N</td>
+
+      <td>Das erlaubte Maximum und Minimum der Rif-Zahl ist nun mittels
+der Initialparameter
+rif_max und rif_min einstellbar (Werte waren bisher fest auf -2.0, +1.0
+eingestellt).</td>
+
+      <td>check_parameters, header, init_1d_model, modules, parin,
+prandtl_fluxes,
+read_var_list, write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">23/09/98</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>B</td>
+
+      <td>Initialisierung von Feldern im Fall von initializing_action =
+"<i>set_constant_profiles</i>"
+und "<i>set_1d-model_profiles</i>" korrigiert.&nbsp;
+      
+      <p>2D-Plotausgabe von u* und theta* korrigiert. Hier wurden
+bisher falsche
+Felder herausgeschrieben.&nbsp; </p>
+
+      
+      <p>Bei SOR-Aufrufen war bisher dp nicht initialisiert.
+Entsprechend ge&auml;ndert.</p>
+
+      </td>
+
+      <td>init_3d_model, plot_2d, pres</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>C</td>
+
+      <td nosave="">Ausgabeformate f&uuml;r Statistik-Ausgaben auf
+Datei RUN_CONTROL
+um einige Kommastellen erweitert.&nbsp;
+      
+      <p>Lieferung von ausf&uuml;hrlicheren Informationen bei
+Programmabbruch
+durch Unterschreitung des minimal erlaubten Zeitschritts.</p>
+
+      </td>
+
+      <td>run_control, timestep</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>N</td>
+
+      <td>Rechnungen mit geneigter Ebene zur Simulation von
+Kaltluftabfl&uuml;ssen
+sind erlaubt. Gestartet und gesteuert werden sie mit dem
+Intialisierungsparameter <tt>alpha_surface</tt>.
+Realisiert wird die geneigte Ebene durch entsprechende
+Schr&auml;gstellung
+des Schwerkraftvektors. Dadurch erh&auml;lt auch die u-Komponente der
+Windgeschwindigkeit
+einen Anteil der Auftriebskraft.&nbsp;
+      
+      <p>Diese Implementierung ist noch nicht abgeschlossen. Die
+Simulation von
+Kaltluftabfl&uuml;ssen erfordert bisher noch Eingriffe "von Hand".</p>
+
+      </td>
+
+      <td>buoyancy, check_parameters, header, leap_frog, modules,
+parin, prandtl_fluxes,
+read_var_list, write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>15/12/98</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>N</td>
+
+      <td>Vereinbarung einer Cache-Layer zur schnelleren bin&auml;ren
+I/O auf
+T3E-Rechnern.&nbsp;
+      
+      <p>Ermittelung wahrer I/O-Zeiten f&uuml;r bin&auml;re
+Ein-/Ausgabe auf
+T3E-Rechnern mit TIMEF.</p>
+
+      </td>
+
+      <td nosave="">check_open,&nbsp; <br>
+
+cpu_zeitmessung, init_3d_model, write_3d_model</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">"</td>
+
+      <td>SR</td>
+
+      <td>1.0</td>
+
+      <td>B</td>
+
+      <td>Bekanntgabe von run_description_header an alle PE's.&nbsp;
+      
+      <p>Diese Programm&auml;nderung erfordert auf T3E-Rechnern
+zwingend den
+Einsatz der MPI-Version mpt.1.2.0.1. In dieser neuen Version tritt auch
+der alte Fehler in MPI_ALLREDUCE nicht mehr auf, so da&szlig; ab jetzt
+mpt.1.1.0.1 nicht mehr verwendet werden mu&szlig;.</p>
+
+      </td>
+
+      <td>parles</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">05/02/99</td>
+
+      <td>SR</td>
+
+      <td>1.1</td>
+
+      <td>C/N</td>
+
+      <td>Implementierung des Upstream-Spline- Verfahrens zur Advektion
+von Impuls
+und skalaren Gr&ouml;&szlig;en (neue UP's, s. rechts). Berechnung von
+Variablen
+f&uuml;r spezielle Advektionsverfahren in eigenst&auml;ndiges UP
+ausgelagert
+(<tt>init_advec</tt> + eigenes Modul <tt>advection</tt>). Reines
+Euler-/Upstream-Verfahren
+kann gerechnet werden.&nbsp;
+      
+      <p>Schnelle bin&auml;re I/O (s. 15/12/98) wieder abgeschaltet, da
+Dateien
+nicht wieder einlesbar sind. Druckst&ouml;rung (p) wird zu Beginn auf 0
+gesetzt, damit sie keine Tendenzen im ersten Zeitschritt hervorruft.</p>
+
+      </td>
+
+      <td>advec_s_bc, check_open, check_parameters, flow_statistics,
+header,
+init_3d_model, init_grid, leap_frog, modules, parin, plot_2d, plot_ts,
+read_var_list, timestep, write_3d_binary, write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+advec_s_ups, advec_u_ups, advec_v_ups, advec_w_ups, init_advec,
+long_filter,
+spline_x, spline_y, spline_z</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">24/02/99</td>
+
+      <td>SR</td>
+
+      <td>1.1a</td>
+
+      <td>C/N</td>
+
+      <td>Kleinere Erg&auml;nzungen / &Auml;nderungen f&uuml;r Upstream
+- Spline,&nbsp; <br>
+
+Diverse Verbesserungen bei Berechnung der Diffusionskoeffizienten
+(exaktere
+Formulierung von Scherungen, Dissipation gemaess Original - Deardorff -
+Ansatz, Mischungswegreduktion nur, wenn Schichtung sowohl oberhalb als
+auch unterhalb des entsprechenden Gitterpunktes stabil ist),
+Wertebegrenzung
+bei Spline - Berechnung zur Verhinderung von "&Uuml;berschwingern"</td>
+
+      <td>check_parameters, diffusion_e, diffusion_pt, diffusivities,
+header,
+init_advec, long_filter, modules, production_e, spline_x, spline_y,
+spline_z</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>"</td>
+
+      <td nosave="">SR</td>
+
+      <td>1.1a</td>
+
+      <td>N/B</td>
+
+      <td>Erweiterung des des Bott - Chlond - Schemas auf Advektion der
+TKE,
+Korrektur der Dichteberechnung (war falsch bei Galilei-Transformation)</td>
+
+      <td>advec_s_bc, leap_frog</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">01/03/99</td>
+
+      <td>MS</td>
+
+      <td>1.1b</td>
+
+      <td>N</td>
+
+      <td>Kleinere Erg&auml;nzungen f&uuml;r Upstream - Spline:&nbsp;
+      
+      <ul>
+
+        <li>Gradientenkontrolle f&uuml;r den nicht-parallelen Teil</li>
+
+        <li>statistische Auswertung &uuml;ber den prozentualen Anteil
+des
+Upstream-Verfahrens
+an der Gesamtadvektion fuer nicht-parallelen Teil</li>
+
+      
+      </ul>
+
+      </td>
+
+      <td>modules, spline_x, spline_y, spline_z</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>"</td>
+
+      <td>SR</td>
+
+      <td>1.1b</td>
+
+      <td>N</td>
+
+      <td>Datenkompression f&uuml;r 3D-Plotausgaben</td>
+
+      <td nosave="">check_open, check_parameters, close_files, header,
+modules,
+parin, plot_3d&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+write_compressed</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">03/03/99</td>
+
+      <td>SR</td>
+
+      <td>1.1c</td>
+
+      <td>B/C</td>
+
+      <td>Schnelle bin&auml;re I/O auf T3E-Rechnern funktioniert jetzt.
+Beim
+bin&auml;ren Einlesen d&uuml;rfen Records nicht mit dem Trick "<tt>READ
+(..) idum</tt>" &uuml;berlesen werden. Zeitmessungen auf T3E erfolgen
+jetzt
+grunds&auml;tzlich mit <tt>TIMEF.</tt></td>
+
+      <td>check_open, cpu_zeitmessung, init_3d_model, modules,
+write_3d_binary</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">25/03/99</td>
+
+      <td>SR</td>
+
+      <td>1.1d</td>
+
+      <td>N</td>
+
+      <td>Einbau einer Rayleigh-D&auml;mpfungsschicht sowie flexiblere
+Wahl der
+numerischen Begrenzer f&uuml;r das Upstream - Spline - Verfahren.</td>
+
+      <td>check_parameters, header, init_3d_model, leap_frog, modules,
+parin,
+read_var_list, spline_x, spline_y, spline_z, write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">"</td>
+
+      <td>SR</td>
+
+      <td>1.1d</td>
+
+      <td>B</td>
+
+      <td>Korrektur des Zeitschrittkriteriums bei z=zp im 1D-Modell</td>
+
+      <td>init_1d_model</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>25/11/99</td>
+
+      <td>SR</td>
+
+      <td>1.1e</td>
+
+      <td>N</td>
+
+      <td nosave="">Partikelplots mit vtk-Graphiksoftware sind auf t3eh
+m&ouml;glich.
+Ausgabe erfolgt im dvr-Format. Bisher noch nicht nutzbar, da noch
+Einstellm&ouml;glichkeiten
+f&uuml;r die Partikelquelle(n) fehlen. <b>Wichtig:</b> Die Benutzung
+der
+vtk-Software erfordert die zus&auml;tzliche mrun-Option <tt>-g</tt>.
+Das
+Hauptprogramm <tt>parles</tt> wird in diesem Fall zum Unterprogramm
+und
+von einem c++-Programm aus aufgerufen.</td>
+
+      <td>header, init_3d_model, init_pegrid, leap_frog, modules,
+parin, parles,
+read_var_list, write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+advec_particles, init_particles, plot_particles</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>"</td>
+
+      <td>SR</td>
+
+      <td>1.1e</td>
+
+      <td nosave="">B/C</td>
+
+      <td>TIMEF-Zeitmessungen von Subroutine- auf Function-Aufruf
+umgestellt.
+Laufindexkorrektur in <tt>spline_y</tt>. Fehler trat bei nx /= ny auf.</td>
+
+      <td>cpu_zeitmessung, spline_y</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">28/12/99</td>
+
+      <td>SR</td>
+
+      <td>1.1f</td>
+
+      <td>N</td>
+
+      <td>Plot von Isooberfl&auml;chen mit vtk-Graphiksoftware sind auf
+t3eh
+m&ouml;glich. Ausgabe erfolgt im dvr-Format. Bisher noch nicht
+allgemein
+nutzbar, da noch diverse manuelle Eingriffe n&ouml;tig sind.</td>
+
+      <td>header, leap_frog, modules, parin, plot_particles,
+read_var_list, write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+plot_isosurface</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">10/01/00</td>
+
+      <td>SR</td>
+
+      <td>1.2</td>
+
+      <td>C</td>
+
+      <td>Randbedingungen f&uuml;r w (=0) werden explizit gesetzt, und
+zwar nicht
+nur bei&nbsp; <tt>k = nzb, nzt+1</tt> sondern auch bei&nbsp; <tt>k =
+nzt</tt>,
+wo bislang der vom vorigen Zeitschritt durch den Druckl&ouml;ser
+ermittelte
+Wert stand. Auch jetzt wird der Wert bei k = nzt anschlie&szlig;end
+durch
+den Druckl&ouml;ser modifiziert. Soweit bis jetzt abzusehen, hat diese
+&Auml;nderung nur minimale Auswirkungen auf den Prognoseverlauf. Evtl.
+gibt es st&auml;rkere Auswirkungen bei exzessivem Auftreten von
+Schwerewellen
+am oberen Rand (die dort aber eigentlich sowieso nicht
+hingeh&ouml;ren).&nbsp; <br>
+
+Variablen&uuml;bergabe an <tt>boundary_conds</tt> erfolgt&nbsp; <br>
+
+&uuml;ber Modul und nicht mehr per Parameterliste.&nbsp;
+      
+      <p>Bei Galilei-Transformation wird jetzt defaultm&auml;&szlig;ig
+der geostrophische
+Wind als Translationsgeschwindigkeit verwendet (neuer
+Initialisierungsparameter <tt>use_ug_for_galilei_tr</tt>).
+Dadurch wird das verst&auml;rkte Auftreten von Schwerewellen bei
+h&ouml;heren
+geostrophischen Windgeschwindigkeiten unterdr&uuml;ckt.&nbsp; </p>
+
+      
+      <p>3D-Feldvariablen (u, v, w, pt, e, km, kh) sowie einige
+2D-Variablen
+(usws, vsws, rif, shf) sind nun als Pointer deklariert, denen nach
+jedem
+Zeitschritt neue Targets zugeordnet werden (f&uuml;r die
+ben&ouml;tigten&nbsp;
+3 Zeitebenen existieren die Targets ..._1 (z.B. u_1), ..._2, ..._3).
+Durch
+die jeweilige Neuzuordnung der Targets entf&auml;llt das Umspeichern
+der
+Zeitebenen komplett (Zeitersparung: ca. 5% der Gesamtrechenzeit).&nbsp;
+      <br>
+
+Die Umordnung der Zeitebenen wurde ins neue UP <tt>swap_timelevel</tt>
+ausgelagert.&nbsp; <br>
+
+      <b>Wichtig:</b> Die &Uuml;bersetzungszeiten haben durch die
+Einf&uuml;hrung
+der Pointer t.w. sehr deutlich zugenommen (<tt>leap_frog</tt>
+ben&ouml;tigt
+jetzt z.B. ca. 60 Sekunden). Au&szlig;erdem ben&ouml;tigt der Compiler
+jetzt wesentlich mehr Speicher. Der "memory"-Parameter in den
+Konfigurationsdateien
+(.mrun.config, .al.config) muss nun mindestens den Wert 60 (MB) (t3eh,
+t3ej2) bzw. 45 (t3eb) und 96 (vpp) haben.&nbsp; <br>
+
+      <b>Achtung:</b> bislang wurde diese &Auml;nderung nur f&uuml;r
+das
+reine Leapfrog-Verfahren getestet!&nbsp; </p>
+
+      
+      <p>Neue Laderoption "<tt>-D preset=nan</tt>" empfohlen (s.
+Beispiel-Konfigurationsdatei).
+Ebenso empfehlenswert f&uuml;r Debug-L&auml;ufe: Compileroption "<tt>-ei</tt>".
+Diese bewirkt einen Programmabbruch, falls mit nicht initialisierten
+Variablen
+gearbeitet wird (ist aber zeitaufwendig in der Ausf&uuml;hrung!).</p>
+
+      </td>
+
+      <td>boundary_conds, check_parameters, header, init_3d_model,
+leap_frog,
+modules, parin, read_var_list, timestep, write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+swap_timelevel</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">10/01/00</td>
+
+      <td>SR</td>
+
+      <td>1.2</td>
+
+      <td>B</td>
+
+      <td>Der Asselin-Filter wird vor Umordnung der Zeitebenen
+aufgerufen. Dies
+geschah bisher f&auml;lschlicherweise erst danach, sodass der
+Zeitfilter
+asymmetrisch arbeitete.&nbsp; <br>
+
+      <b>Achtung:</b> diese &Auml;nderung hat Auswirkungen auf den
+Prognoseverlauf.
+Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</td>
+
+      <td>leap_frog</td>
+
+    </tr>
+
+    <tr nosave="">
+
+      <td nosave="" valign="top">14/02/00</td>
+
+      <td nosave="" valign="top">MS</td>
+
+      <td nosave="" valign="top">1.2</td>
+
+      <td nosave="" valign="top">B/C</td>
+
+      <td><b>1D-Modell:</b> <br>
+
+Der Asselin-Filter im 1D-Modell wird nun auch vor der Umordnung der
+Zeitebenen aufgerufen (s.o.).&nbsp;
+      
+      <p><b>3D-Modell:</b> <br>
+
+TKE wurde bisher bei <tt>scalar_advec=bc-scheme</tt> einer zeitlichen
+Filterung unterzogen. Dies wird nun unterbunden.&nbsp; </p>
+
+      
+      <p>Die Divergenz der Impulsfl&uuml;sse an der Prandtl - Schicht -
+Obergrenze
+wird nun &uuml;ber eine ganze Gitterweite gebildet. Die bisherige
+Methode
+lieferte im Vergleich mit Ergebnissen anderer LES-Modelle&nbsp; zu
+gro&szlig;e
+Impulsfl&uuml;sse.&nbsp; </p>
+
+      
+      <p>Bei der Berechnung der Diffusion der Temperatur werden die
+Diffusionskoeffizienten
+nun wieder durch Mittelung f&uuml;r die entsprechenden&nbsp;
+Gitterpunkte
+bereitgestllt. Das Maximumkriterium, das im Zuge der Implementierung
+des
+Upstream-Spline Advektionsverfahrens eingebaut wurde, bewirkte ein zu
+rasches
+Anwachsen der Grenzschicht mit der Zeit.&nbsp; </p>
+
+      
+      <p><b>Achtung:</b> diese &Auml;nderungen haben Auswirkungen auf
+den Prognoseverlauf.
+Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p>
+
+      </td>
+
+      <td nosave="" valign="top">init_1d_model, asselin_filter,
+diffusion_u, diffusion_v,&nbsp; <br>
+
+diffusion_pt</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">17/02/00</td>
+
+      <td>MS</td>
+
+      <td>2.0</td>
+
+      <td>N</td>
+
+      <td><b>Allgemeine Beschreibung der &Auml;nderungen:</b> <br>
+
+vollst&auml;ndige Implementierung des wolkenphysikalischen Moduls&nbsp;
+      
+      <p>Zur Implementierung der Wolkenphysik waren umfangreiche
+&Auml;nderungen
+in zahlreichen Programmteilen notwendig (Beschreibung <a href="#Cloud_physics">siehe
+unten</a> ). Im einzelnen wurden folgende Unprogramme
+ge&auml;ndert:&nbsp; <br>
+
+      <b>modules</b>:&nbsp; <br>
+
+1) Bereitstellung neuer 3D-, 2D- und 1D-Felder f&uuml;r die Prognose
+des Gesamtwassergehaltes&nbsp; <br>
+
+2) "cloud_parameters" als neues Modul mit wolkenphysikalischen
+Variablen&nbsp; <br>
+
+      <b>parin: </b>Initialisierungsparameterliste wurde erweitert
+(s.u.)&nbsp; <br>
+
+      <font color="#000000"><b>read_var_list, write_var_list,
+write_3d_binary: </b>In/Output
+der neuen Initialisierungsparamter und Felder f&uuml;r
+Fortsetzungsl&auml;ufe&nbsp;</font> <br>
+
+      <font color="#000000"><b>check_parameters:</b> Initialisierung
+des
+Feuchteprofils und Ausgabe von neuen Vertikalprofilen:&nbsp;</font> <br>
+
+      <font color="#ff0000">vpt</font><font color="#000000">: virtuelle
+poteniellen
+Temperatur,</font> <br>
+
+      <font color="#ff0000">lpt</font><font color="#000000">:
+potentielle
+Fl&uuml;ssigwassertemperatur,</font> <br>
+
+      <font color="#ff0000">q</font><font color="#000000">:
+Gesamtwassergehalt,</font> <br>
+
+      <font color="#ff0000">qv</font><font color="#000000">:
+spezifische
+Feuchte,</font> <br>
+
+      <font color="#ff0000">ql</font><font color="#000000">:
+Fl&uuml;ssigwassergehalt,</font> <br>
+
+      <font color="#ff0000">w"vpt", w*vpt*, wvpt</font><font color="#000000">:
+Auftriebsfluss (subskalig, aufgel&ouml;st, gesamt),</font> <br>
+
+      <font color="#ff0000">w"q", w*q*, wq</font><font color="#000000">:
+Wasserfluss (subs., aufg., ges.),</font> <br>
+
+      <font color="#ff0000">w"qv", w*qv*, wqv</font><font color="#000000">:
+Feuchtefluss (subs, aufg., ges.)</font> <br>
+
+      <b>init_3d_model</b>: Initialisierung aller
+Feuchte/Wasserfelder&nbsp; <br>
+
+      <b>init_1d_model</b>: Anpassung an Rechnungen mit Feuchte&nbsp; <br>
+
+      <b>header</b>: Headerausgaben f&uuml;r Feuchtebehandlung und
+Wolkenphysik
+eingef&uuml;gt, au&szlig;erdem Formatnummern erweitert um Platz
+f&uuml;r
+weitere Ausgaben zu schaffen&nbsp; <br>
+
+      <b>leap_frog:</b> <br>
+
+1) alle prognostischen Gleichungen wurden in prognostic_equations
+ausgelagert&nbsp; <br>
+
+2) Aufrufe der neuen Unterprogramme (UP) compute_vpt,
+calc_liquid_water_content&nbsp; <br>
+
+3) veraenderter Aufruf von diffusivities&nbsp; <br>
+
+      <b><tt>b</tt>oundary_conds, asselin_filter, swap_timelevel,
+flow_statistics: </b>Anpassung
+an Feuchtebehandlung&nbsp; <br>
+
+      <b>plot2d, plot3d</b>: Ausgabem&ouml;glichkeiten von q und ql <br>
+
+      <b>buoyancy</b>: Anpassung des Autriebstermes an
+Feuchtebehandlung
+durch neue &Uuml;bergabeparameter: Temperatur + Nummer des
+entsprechenden
+mittleren Temperaturprofils&nbsp; <br>
+
+      <b>diffusion_e</b>: Anpassung der Mischungswegberechnung an
+Feuchtebehandlung
+durch Variation der &Uuml;bergabeparameter&nbsp; <br>
+
+      <b>production_e</b>: TKE-Produktion durch Auftriebskr&auml;fte an
+Feuchtebehandlung
+angepasst&nbsp; <br>
+
+      <b>diffusivities</b>: siehe diffusion_e&nbsp; <br>
+
+      <b>prandtl-fluxes</b>: Prandtl-Schicht fuer den
+Gesamtwassergehalt
+eingef&uuml;gt&nbsp; </p>
+
+      
+      <p>Zus&auml;tzlich wurden folgende Unterprogramme NEU
+eingef&uuml;hrt:&nbsp; <br>
+
+      <b>inti_cloud_physics</b>: Initialisierung wolkenphysikalischer
+Parameter&nbsp; <br>
+
+      <b>prognostic_equations</b>: Auslagerung der prognostischen
+Gleichungen
+aus leap_frog, zus&auml;tzliche porgnostische Gleichung f&uuml;r den
+Gesamtwassergehalt&nbsp; <br>
+
+      <b>diffusion_s</b>: Berechnung der Diffusion skalarer
+Gr&ouml;&szlig;en
+(Temperatur und Gesamtwassergehalt), ersetzt diffusion_pt&nbsp; <br>
+
+      <b>calc_liquid_water_content</b>: Berechnung des
+Fl&uuml;ssigwassergehalts&nbsp; <br>
+
+      <b>calc_radiation</b>: Parametrisierung langwelliger
+Strahlungsprozesse
+&uuml;ber des Schema der effektiven Emissivit&auml;t&nbsp; <br>
+
+      <b>calc_precipitation</b>:Parametrisierung von
+Niederschlagsprozessen
+mit Hilfe eines vereinfachten Kesslerschemas&nbsp; <br>
+
+      <b>impact_of_latent_heat</b>: Ber&uuml;cksichtigung der durch
+Niederschlagsprozesse
+zur&uuml;ckbleibenden latenten Waerme innerhalb eines
+Gittervolumens&nbsp; <br>
+
+      <b>compute_vpt</b>: Berechnung der virtuellen potentiellen
+Temperatur&nbsp; </p>
+
+      
+      <p><b>Liste der neuen Initialisierungsparameter:</b> <br>
+
+      
+      <table nosave="" border="1">
+
+        <caption>&nbsp; <br>
+
+        </caption><tbody>
+
+        
+        </tbody><tbody>
+
+        
+        </tbody> <tbody>
+
+          <tr nosave="">
+
+            <td nosave=""><b>Parameter</b></td>
+
+            <td nosave=""><b>Typ</b></td>
+
+            <td nosave="" width="4%"><b>Default</b></td>
+
+            <td nosave=""><b>Beschreibung</b></td>
+
+          </tr>
+
+          <tr nosave="">
+
+            <td nosave=""><tt>moisture</tt></td>
+
+            <td>L</td>
+
+            <td>FALSE</td>
+
+            <td>Ab-/Zuschalten des Gesamtwassergerhaltes als neue
+progn. Variable</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>cloud_physics</tt></td>
+
+            <td>L</td>
+
+            <td>FALSE</td>
+
+            <td>Ab-/Zuschalten des Kondensationsschemas</td>
+
+          </tr>
+
+          <tr nosave="">
+
+            <td><tt>radiation</tt></td>
+
+            <td>L</td>
+
+            <td nosave="">FALSE</td>
+
+            <td>Ab-/Zuschalten des Strahlungsschemas</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>precipitation</tt></td>
+
+            <td>L</td>
+
+            <td>FALSE</td>
+
+            <td>Ab-/Zuschalten der Niderschlagsparametrisierung</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>bc_q_b</tt></td>
+
+            <td>C</td>
+
+            <td>'dirichlet'</td>
+
+            <td>untere Randbedingung f&uuml;r q (siehe auch bc_pt_b)</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>bc_q_t</tt></td>
+
+            <td>C</td>
+
+            <td>'neumann'</td>
+
+            <td>obere RB f&uuml;r q (siehe auch bc_pt_t)</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>q_surface</tt></td>
+
+            <td>R</td>
+
+            <td>0.0</td>
+
+            <td>Feuchtewert an der Erdoberfl&auml;che</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>q_surface_initial_change</tt></td>
+
+            <td>R</td>
+
+            <td>0.0</td>
+
+            <td>vgl. pt_surface_initial_change</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>q_vertical_gradient</tt></td>
+
+            <td>R(10)</td>
+
+            <td>0.0</td>
+
+            <td>vgl. pt_vertical_gradient</td>
+
+          </tr>
+
+          <tr nosave="">
+
+            <td nosave=""><tt>q_vertical_gradient_level</tt></td>
+
+            <td>R(10)</td>
+
+            <td>10000.0</td>
+
+            <td>vgl. pt_vertical_gradient_level</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>surface_pressure</tt></td>
+
+            <td>R</td>
+
+            <td>1013.25</td>
+
+            <td>Luftdruck an der Erdoberfl&auml;che</td>
+
+          </tr>
+
+          <tr>
+
+            <td><tt>surface_waterflux</tt></td>
+
+            <td>R</td>
+
+            <td>0.0</td>
+
+            <td>oberfl&auml;chennaher Wasser/Feuchtefluss</td>
+
+          </tr>
+
+        
+        </tbody>
+      
+      </table>
+
+Fortsetzungsl&auml;ufe mit Daten, die mit Modellversionen kleiner 2.0
+erzeugt
+wurden, sind aufgrund der erweiterten Initialisierungsparameterliste
+INKOMPATIBEL
+zu den Einleseroutinen der Version 2.0. Ein Update auf Version 2.0
+sollte
+deshalb nach Abschluss eines kompletten Modelllaufs erfolgen.&nbsp; </p>
+
+      
+      <p><b>Achtung:</b> diese &Auml;nderungen haben Auswirkungen auf
+den Prognoseverlauf.
+Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p>
+
+      </td>
+
+      <td nosave="" valign="top">modules, parin, read_var_list,
+check_parameters,
+init_3d_model, init_1d_model, header, leap_frog. buoyancy, diffusion_e,
+production_e, diffusivities, prandtl_fluxes, boundary_conds,
+asselin_filter,
+swap_timelevels, flow_statistics, plot_2d, plot_3d, write_var_list,
+write_3d_binary&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+init_cloud_physics, prognostic_equations, diffusion_s,
+calc_liquid_water_content,
+calc_radiation, calc_precipitation, impact_of_latent_heat, comute_vpt</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="">
+
+      <td nosave="" valign="top">18/02/00</td>
+
+      <td nosave="" valign="top">MS</td>
+
+      <td nosave="" valign="top">2.0</td>
+
+      <td nosave="" valign="top">B/N</td>
+
+      <td>Im Zuge der Umstellung auf Modellversion 2.0&nbsp; wurden
+noch kleine
+&Auml;nderungen an den Unterprogrammen diffusion_e, production_e und
+diffusivities
+vorgenommen. In allen genannten&nbsp; <br>
+
+Unterprogrammen wurde bisher ein strengeres Kriterium zur Bestimmung
+der Schichtungsverh&auml;ltnisse verwendet. Ein Modellvergleich zeigte
+jedoch, dass dadurch die Diffusion im Bereich der Inversion zu gross
+wird.&nbsp;
+      
+      <p>Eine weitere Erg&auml;nzung betrifft die
+Advektionsverfahren:&nbsp; <br>
+
+Das Bott-Chlond Advektionsverfahren ist nun auch f&uuml;r Rechnungen
+mit Feuchte/Wolkenphysik verf&uuml;gbar.&nbsp; </p>
+
+      
+      <p><b>Achtung:</b> diese &Auml;nderungen haben Auswirkungen auf
+den Prognoseverlauf.
+Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p>
+
+      </td>
+
+      <td nosave="" valign="top">diffusion_e, production_e,
+diffusivities, check_parameters</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">26/04/00</td>
+
+      <td>SR</td>
+
+      <td>2.0a</td>
+
+      <td>C</td>
+
+      <td>Vollst&auml;ndige Umstellung von vtk-Grafik-Software auf
+dvrp-Software.
+Grafik-Ausgaben im dvr-Format sind mittlerweile begrenzt nutzbar
+(Isooberfl&auml;chen
+sind darstellbar, siehe neue Laufparameter&nbsp; <tt>dt_dvrp, threshold</tt>),
+es wird aber in der Anwendung in naher Zukunft noch diverse
+&Auml;nderungen
+geben. Partikelausgabe vorerst nicht mehr m&ouml;glich (Verlagerung
+schon).</td>
+
+      <td>header, init_particles, init_3d_model, leap_frog, modules,
+parin, parles,
+read_var_list, write_var_list&nbsp; <br>
+
+      <b>Gestrichen:</b> <br>
+
+plot_isosurface, plot_particles&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+init_dvrp, plot_dvrp</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">26/04/00</td>
+
+      <td>SR</td>
+
+      <td>2.0a</td>
+
+      <td>C</td>
+
+      <td>Durch zus&auml;tzlichen zyklischen Rand im Bott-Chlond-Schema
+sehr
+viele SENDRECV-Aufrufe eingespart.&nbsp; <br>
+
+&Auml;nderung des Namens einer eingelesenen Environment-Variablen in <tt>check_open</tt>
+von <tt>remote_addres</tt> nach <tt>return_addres</tt>.&nbsp; <br>
+
+Prozessor-Topologie kann durch Benutzer vorgegeben werden. Dazu neue
+Initialisierungsparameter <tt>npex</tt> und <tt>npey</tt>. Durch
+&Auml;nderungen
+am Header-Format wurde Testergebnis-Datei ge&auml;ndert.</td>
+
+      <td>advec_s_bc, check_open, header, init_pegrid, modules, parin,
+read_var_list,
+write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">26/04/00</td>
+
+      <td>SR</td>
+
+      <td>2.0a</td>
+
+      <td>N</td>
+
+      <td>Rechnungen mit geneigter Oberfl&auml;che erlauben jetzt die
+Vorgabe
+eines stabil geschichteten Temperaturprofils mit konstantem Gradienten.
+Hinzuschalten von Feuchte funktioniert f&uuml;r Hangrechnungen noch
+nicht.</td>
+
+      <td>advec_s_bc, buoyancy, init_3d_model, modules,
+prognostic_equations&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+init_slope</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>13/06/00</td>
+
+      <td>MS</td>
+
+      <td>2.0a</td>
+
+      <td nosave="">B</td>
+
+      <td>Es werden nun auch die seitlichen R&auml;nder f&uuml;r ql
+gesetzt.
+Ein Nichtsetzen der Randbedingungen f&uuml;hrte zu Fehlern bei der
+Ausgabe
+von pt</td>
+
+      <td nosave="">calc_liquid_water_content</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">03/07/00</td>
+
+      <td>SR</td>
+
+      <td>2.0b</td>
+
+      <td>C</td>
+
+      <td>F&uuml;r eine Reihe von&nbsp; Unterprogrammen, die innerhalb
+von <tt>prognostic_equation</tt>
+aufgerufen werden und an die Pointer-Variablen &uuml;bergeben werden,
+sind
+jetzt explizite Interfaces vereinbart (neues Modul <tt>pointer_interfaces</tt>).
+Auch im Vereinbarungsteil der entsprechenden Unterprogramme sind diese
+&Uuml;bergabeparameter jetzt aus Konsistenzgr&uuml;nden (und weil es
+sonst
+Laufzeitfehler gibt) als Pointer-Variablen deklariert. Mit dieser
+&Auml;nderung
+ist der gro&szlig;e Speicher- und CPU-Zeit-Bedarf beim &Uuml;bersetzen
+von prognostic_equations wieder auf ein ertr&auml;gliches Ma&szlig;
+reduziert.&nbsp; <br>
+
+Im Rahmen dieser &Auml;nderungen wurde auch an diffusion_e ein
+Hilfsfeld
+weniger &uuml;bergeben.&nbsp; <br>
+
+Aus nicht vollst&auml;ndig gek&auml;rten Gr&uuml;nden haben sich die
+Zahlen in der Testergebnis-Datei minimal ge&auml;ndert (und zwar die
+Spalte
+mit der Gesamtdivergenz nach Aufruf des Druckl&ouml;sers).</td>
+
+      <td>advec_s_bc, buoyancy, diffusion_e, diffusion_s, diffusion_u,
+diffusion_v,
+diffusion_w, disturb_field, modules, production_e, prognostic_equations</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">04/07/00</td>
+
+      <td>SR</td>
+
+      <td>2.0b</td>
+
+      <td>B</td>
+
+      <td>Diriclet-Randbedingungen f&uuml;r Temperatur und
+Fl&uuml;ssigwassergehalt
+werden gesetzt. Dies w&auml;re bereits nach Einf&uuml;hrung der Pointer
+zwingend notwendig gewesen. Rechnungen mit vorgegebener
+Oberfl&auml;chentemperatur
+schlugen deshalb bislang fehl.</td>
+
+      <td>boundary_conds</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">07/09/00</td>
+
+      <td>MS</td>
+
+      <td>2.0b</td>
+
+      <td>B</td>
+
+      <td>Die virtuelle potenielle Temperatur wird nun auch f&uuml;r
+k=nzb und
+k=nzt+1 berechnet, um die Randwerte auch f&uuml;r Ausgabezwecke
+bereichtzustellen.&nbsp;</td>
+
+      <td>compute_vpt</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">28/12/00</td>
+
+      <td>SR</td>
+
+      <td>2.1</td>
+
+      <td>C/N</td>
+
+      <td>PALM erlaubt jetzt den Einsatz optionaler Software-Pakete,
+die zwar
+zum Modell geh&ouml;ren, standardm&auml;&szlig;ig aber nicht mit
+&uuml;bersetzt
+werden, um so unter anderem Kompilationszeit einzusparen. Siehe neues
+Kapitel
+3.7 in der Modelldokumentation.&nbsp;
+      
+      <p>Einsatz der dvrp-Software wurde vollst&auml;ndig
+&uuml;berarbeitet.
+Sie ist nun als Software-Paket optional im Modell einsetzbar. Siehe
+&uuml;berarbeitetes
+Kapitel 4.5.6 in der Modelldokumentation.&nbsp; </p>
+
+      
+      <p>Die Prognose der Partikelverlagerung ist ebenfalls in ein
+optionales
+Software-Paket ausgelagert.</p>
+
+      </td>
+
+      <td>advec_particles, header, init_3d_model, init_dvrp,
+init_particles,
+init_pegrid, modules, parin, parles, plot_dvrp, prognostic_equations,
+read_var_list,
+write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+package_parin</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">28/12/00</td>
+
+      <td>SR</td>
+
+      <td>2.1</td>
+
+      <td>B</td>
+
+      <td>MPI_FINALIZE ans Ende des Hauptprogramms geschoben (stand
+vorher vor
+cpu_auswertung, wo noch ein Barrier-Aufruf steht). comm2d war zu Beginn
+undefiniert und wird nun erst einmal gleich MPI_COMM_WORLD gesetzt.</td>
+
+      <td>parles</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">02/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1a</td>
+
+      <td>C</td>
+
+      <td>Offene Dateien werden sobald m&ouml;glich geschlossen.
+Wiederer&ouml;ffnung
+bestimmter Dateien mit POSITION='APPEND' m&ouml;glich. In diesem
+Zusammenhang
+wurde das Unterprogramm close_files in close_file umbenannt und hat nun
+1 Argument.&nbsp; <br>
+
+Anpassung der Diffusionsparametrisierung im 1D-Modell an das 3D-Modell.</td>
+
+      <td>advec_particles, check_cpu_time, check_open, cpu_auswertung,
+init_1d_model,
+init_3d_model, init_particles, modules.f90, parin, parles, plot_2d,
+write_3d_binary&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+close_file&nbsp; </p>
+
+      
+      <p><b>Eliminiert:</b> <br>
+
+close_files</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">02/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1a</td>
+
+      <td>B</td>
+
+      <td>Beseitigung kleiner Fehler.</td>
+
+      <td>check_cpu_time, diffusion_e, diffusivities, long_filter,
+production_e</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>05/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1b</td>
+
+      <td>N</td>
+
+      <td nosave="">Neues Software-Paket zur Berechnung von Spektren im
+Ortsraum</td>
+
+      <td>check_open, header, init_3d_model, leap_frog, modules,
+package_parin,
+parles, read_var_list, write_3d_binary, write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+calc_spectra, plot_spectra</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td>25/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1c</td>
+
+      <td>C/N</td>
+
+      <td>Druckl&ouml;ser kann jetzt die Singleton-FFT benutzen. Modul <tt>singleton</tt>
+wurde deshalb von <tt>calc_spectra.f90</tt> nach <tt>modules.f90</tt>
+geschoben
+(neuer Initialisierungsparameter <tt>fft_method</tt>).&nbsp; <br>
+
+Fl&uuml;sse k&ouml;nnen jetzt bei k=1 unabh&auml;ngig von der
+Verwendung
+einer Prandtl-Schicht vorgegeben werden (neuer
+Initialisierungsparameter <tt>use_surface_fluxes</tt>).&nbsp; <br>
+
+Modul <tt>test_variables</tt> wurde aus allen Programmteilen entfernt.
+Hauptprogramm wurde von parles nach <tt>palm</tt> umbenannt.&nbsp; <br>
+
+Modell kann auf DEC-Workstations eingesetzt werden (-D <tt>dec</tt>).&nbsp;
+      <br>
+
+Zus&auml;tzliche Zeitmessungen mit dvrp-Software. Schreiben von
+Partikel-Informationen
+ist optional (neuer Parameter <tt>write_particle_informations</tt>).</td>
+
+      <td>advec_particles, calc_spectra, check_parameters,
+cpu_zeitmessung, diffusion_s,
+header, init_3d_model, init_dvrp, init_particles, leap_frog, modules,
+package_parin,
+parin, poisfft, read_var_list, swap_timelevel, write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+palm&nbsp; </p>
+
+      
+      <p><b>Eliminiert:</b> <br>
+
+parles, module_test</p>
+
+      </td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td>25/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1c</td>
+
+      <td>B</td>
+
+      <td>Fehler beim &ouml;ffnen von Unit 23 beseitigt. Modul <tt>interface</tt>
+fehlte in disturb_field.&nbsp; <br>
+
+Wertebereich von theta* in Prandtl-Fluxes eingeschr&auml;nkt, weil
+sonst auf einigen Rechnern overflow droht, wenn u*=0.</td>
+
+      <td>check_open, disturb_field, prandtl_fluxes</td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td>30/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1d</td>
+
+      <td>N/C</td>
+
+      <td>Prognose eines passiven Skalars ist m&ouml;glich (anstatt
+Feuchte),
+dazu neuer Initialisierungsparameter <tt>passive_scalar</tt>.&nbsp;
+      
+      <p>Falls kein Pfad f&uuml;r ftpcopy existiert, werden in <tt>check_open</tt>
+die Dateinamen f&uuml;r AVS-Koordinaten- und Datendatei auf "unknown"
+gesetzt.</p>
+
+      </td>
+
+      <td>asselin_filter, boundary_conds, check_open, check_parameters,
+flow_statistics,
+header, init_1d_model, init_3d_model, modules, parin, plot_2d,
+plot_dvrp,
+prandtl_fluxes, prognostic_equations, read_var_list, swap_timelevel,
+write_3d_binary,
+write_var_list</td>
+
+    </tr>
+
+    <tr valign="top">
+
+      <td>30/01/01</td>
+
+      <td>SR</td>
+
+      <td>2.1d</td>
+
+      <td>B</td>
+
+      <td>String-Ausgabe f&uuml;r use_surface_fluxes korrigiert.
+Version vom
+25/01/01 brach deswegen bei Fortsetzungsl&auml;ufen ab.&nbsp; <br>
+
+xy-Plotausgabe von q und ql korrigiert.</td>
+
+      <td>plot_2d, write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">30/03/01</td>
+
+      <td>SR</td>
+
+      <td>2.2</td>
+
+      <td>N/C</td>
+
+      <td>S&auml;mtliche 3D-Felder der Zeitebene t+dt wurden entfernt.
+Ebenso
+die Arbeitsfelder work und work1. Hilfsfelder wurden soweit
+m&ouml;glich
+eingespart und werden grunds&auml;tzlich lokal allokiert. Dadurch
+konnten
+eine Reihe von &Uuml;bergabeparametern gestrichen werden (z.B. beim
+Aufruf
+von <tt>pres, advec_s_bc, poisfft, production_e, sor </tt>sowie den
+Spline-Unterprogrammen).
+Der Long-Filter wurde in das Upstream-Spline-Verfahren integriert. Da
+der
+Zeitfilter jetzt direkt in der prognostischen Gleichung angewendet wird
+(bisher geschah dies erst nach Aufruf des Druckl&ouml;sers), haben sich
+die Zahlen in der Testergebnis-Datei ge&auml;ndert. Die mittleren
+Profile
+sind aber unbeeinflusst.&nbsp;
+      
+      <p>Eine weitere kleinere &Auml;nderung der Testergebnis-Daten
+wird dadurch
+verursacht, dass jetzt der Parameter <tt>adjust_mixing_length</tt>
+defaultm&auml;&szlig;ig <tt>.FALSE.</tt>
+ist und der Mischungsweg grunds&auml;tzlich zus&auml;tzlich auf&nbsp; <tt>0.7
+* zu</tt>&nbsp;&nbsp; begrenzt wird. Falls <tt>adjust_mixing_length=T</tt>,
+wird jetzt der Mischungsweg in <tt>diffusivities</tt> analog zu <tt>diffusion_e</tt>
+an allen Gitterpunkten modifiziert. <b>Achtung: </b>Diese
+&Auml;nderungen
+k&ouml;nnen bei anderen Simulationen t.w. erhebliche Auswirkungen auf
+die
+oberfl&auml;chennahen Ergebnisse haben.&nbsp; </p>
+
+      
+      <p><b>Kleinere &Auml;nderungen:</b> In <tt>init_cloud_physics</tt>
+wird
+der Wert der Variablen <tt>surface_pressure</tt> in hPa belassen
+(bisher
+Umwandlung in Pa).&nbsp; <br>
+
+Die Namelist-Namen der Software-Pakete sind&nbsp; t.w.
+ge&auml;ndert.&nbsp; <br>
+
+Unit 14 (bin&auml;re Ausgabe f&uuml;r Fortsetzungsl&auml;ufe) wird
+jetzt im Hauptprogramm geschlossen, damit auf diese Datei noch
+benutzergesteuerte
+Ausgaben erfolgen k&ouml;nnen.&nbsp; <br>
+
+Laufparameter werden in keinem Fall mehr auf Unit 14 ausgegeben bzw.
+von Unit 13 gelesen, d.h. sie gelten jetzt tats&auml;chlich nur
+f&uuml;r
+den jeweils aktuellen Lauf.&nbsp; <br>
+
+Partikeladvektion funktioniert jetzt auch zusammen mit der
+Galilei-Transformation.&nbsp; </p>
+
+      
+      <p>Restliche deutsche Variablen-, Unterprogramm- und Modulnamen
+wurden
+ins Englische &uuml;bersetzt. Davon sind fast alle Programmteile
+betroffen
+(nicht in rechter Spalte aufgef&uuml;hrt).</p>
+
+      </td>
+
+      <td>advec_particles, advec_s_bc, advec_s_ups, advec_u_ups,
+advec_v_ups,
+advec_w_ups, boundary_conds, calc_spectra, check_parameters,
+diffusion_e,
+init_3d_model, init_cloud_physics, init_pegrid, init_rankine,
+leap_frog,
+modules, package_parin, palm, parin, poisfft, pres, production_e,
+prognostic_equations,
+read_var_list, sor, swap_timelevel, transpose_*, write_3d_binary,
+write_var_list&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+cpu_log, cpu_statistics&nbsp; </p>
+
+      
+      <p><b>Eliminiert:</b> <br>
+
+asselin_filter, cpu_auswertung, cpu_zeitmessung, long_filter</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">12/07/01</td>
+
+      <td>SR</td>
+
+      <td>2.2a</td>
+
+      <td>N/C</td>
+
+      <td>Defaultwert der unteren Randbedingung f&uuml;r die TKE ist ab
+sofort <tt>bc_e_b
+= 'neumann'</tt>.&nbsp; <br>
+
+Partikelquelle ist &uuml;ber Paketparameter steuerbar.
+Partikeleigenschaften
+sind mittels benutzereigener Software steuerbar. Der dvrp-Ausgabeweg
+ist
+jetzt ebenfalls &uuml;ber Paketparameter steuerbar.&nbsp; <br>
+
+Allen Modulen (bis auf singleton) wurde eine SAVE-Anweisung
+hinzugef&uuml;gt,
+damit die durch sie vereinbarten Variablen w&auml;hrend der Rechnung in
+keinem Fall undefiniert werden k&ouml;nnen (diese Gefahr besteht z.B.
+auf
+SGI-Origin-Maschinen).</td>
+
+      <td>advec_particles, header, init_dvrp, init_particles,
+modules.f90, package_parin,
+plot_dvrp, user_interface</td>
+
+    </tr>
+
+    <tr>
+
+      <td>12/07/01</td>
+
+      <td>SR</td>
+
+      <td>2.2a</td>
+
+      <td>B</td>
+
+      <td>Verschiebung der OPEN-Anweisung f&uuml;r Unit 33
+(AVS-FLD-Datei).</td>
+
+      <td>check_open</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">20/07/01</td>
+
+      <td>SR</td>
+
+      <td>2.3</td>
+
+      <td>N</td>
+
+      <td>Einbau des Mehrgitterverfahrens zur L&ouml;sung der
+Poisson-Gleichung.</td>
+
+      <td>check_parameters, exchange_horiz, header, init_grid,
+init_pegrid, modules,
+parin, pres, run_control&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+poismg</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">21/08/01</td>
+
+      <td>SR</td>
+
+      <td>2.3a</td>
+
+      <td>N/C</td>
+
+      <td>Erg&auml;nzung der dvrp-Software: Partikel k&ouml;nnen mit
+Schw&auml;nzen
+versehen werden. Die Ausgabe der dvrp-Plotdaten durch einen separaten
+PE
+ist m&ouml;glich (mrun-Option "<tt>-p dvrp_graphics+1PE</tt>"). Der
+Kommunikator <tt>MPI_COMM_WORLD</tt>&nbsp;
+wurde deshalb durch&nbsp; <tt>comm_palm</tt>&nbsp; ersetzt.&nbsp;
+      
+      <p>Reduzierung des Mischungsweges im Wandbereich kann wahlweise
+abgeschaltet
+werden. F&uuml;r km und kh wird jetzt eine Neumann-Randbedingung am
+unteren
+Rand verwendet. Die TKE-Energieproduktionsberechnung durch Scherung des
+Grundstroms am unteren Rand wurde verbessert.&nbsp; </p>
+
+      
+      <p>Generelle Verwendung der bodennahen vertikalen
+Impulsfl&uuml;sse in
+den Diffusionstermen von u und v, immer wenn diese als Randbedingung
+vorgegeben
+sind (gem&auml;&szlig; <tt>use_surface_fluxes</tt>, - bisher wurde
+dies
+nur bei eingeschalteter Prandtl-Schicht gemacht). Schubspannungen
+k&ouml;nnen
+jetzt als Randbedingungen vorgegeben werden (allerdings unter
+zuhilfenahme
+benutzereigener Software).&nbsp; </p>
+
+      
+      <p>Zus&auml;tzliche Schnittstellen f&uuml;r benutzereigene
+Software in
+allen Tendenztermen, in <tt>flow_statistics,</tt> und f&uuml;r
+Partikel-
+bzw. dvrp-Programmteile (Bestimmung von Partikeleigenschaften,
+Festlegung
+von Farbtabellen).&nbsp; </p>
+
+      
+      <p><b>Achtung: </b>Diese &Auml;nderungen k&ouml;nnen bei
+Simulationen mit
+mittlerem Wind durch die &Auml;nderungen im bereich des unteren Randes
+t.w. erhebliche Auswirkungen auf die oberfl&auml;chennahen Ergebnisse
+haben.</p>
+
+      </td>
+
+      <td>advec_particles, diffusion_e, diffusion_u, diffusion_v,
+diffusivities,
+flow_statistics, header, init_dvrp, init_particles, init_pegrid,
+leap_frog,
+modules, package_parin, palm, parin, plot_dvrp, production_e,
+prognostic_equations,
+read_var_list, swap_timelevel, user_interface, write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">21/08/01</td>
+
+      <td>SR</td>
+
+      <td>2.3a</td>
+
+      <td>B</td>
+
+      <td>Falsche Positionierung von MPI_ALLREDUCE in check_cpu_time
+korrigiert.</td>
+
+      <td>check_cpu_time</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">04/09/01</td>
+
+      <td>SR</td>
+
+      <td>2.3b</td>
+
+      <td>N</td>
+
+      <td>Zus&auml;tzliche Profilausgaben f&uuml;r
+Energieproduktionsterme m&ouml;glich.
+St&ouml;rdruck wird bei der FFT-Methode nicht mehr durch Aufsummieren
+der
+Werte zu den einzelnen Zeitschritten ermittelt.</td>
+
+      <td>check_parameters, flow_statistics, modules, pres</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">04/09/01</td>
+
+      <td>SR</td>
+
+      <td>2.3b</td>
+
+      <td>B</td>
+
+      <td>Austausch der Geisterr&auml;nder f&uuml;r die zeitgefilterten
+Felder
+direkt nach Durchf&uuml;hrung der Filterung (war fehlerhaft seit
+Entfernen
+der Zeitebene t+dt (Version 2.2) und f&uuml;hrte zu sehr kleinen
+St&ouml;rungen
+an den seitlichen R&auml;ndern der Teilgebiete).&nbsp;
+      
+      <p><b>Achtung:</b> Der Inhalt der Testergebnis-Datei &auml;ndert
+sich durch
+diese Fehlerkorrektur.</p>
+
+      </td>
+
+      <td>prognostic_equations</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">09/11/01</td>
+
+      <td>SR</td>
+
+      <td>2.3c</td>
+
+      <td>N</td>
+
+      <td>Farbe entlang der Partikelschw&auml;nze kann sich
+&auml;ndern. Einschalten
+der Partikeladvektion bei Fortsetzungsl&auml;ufen m&ouml;glich.</td>
+
+      <td>advec_particles, init_particles, modules, package_parin,
+plot_dvrp</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">16/04/02</td>
+
+      <td>SR</td>
+
+      <td>2.3d</td>
+
+      <td>N</td>
+
+      <td>Vorgabe von Randbedingungen f&uuml;r Partikeladvektion
+m&ouml;glich.
+Partikeldaten k&ouml;nnen f&uuml;r sp&auml;tere Analysen auf Datei
+geschrieben
+werden (Unit 85). <tt>PARTICLE</tt>-Datentyp enth&auml;lt
+Informationen
+&uuml;ber Partikelgeschwindigkeitskomponenten und Startposition.&nbsp;
+      
+      <p>Skalartransport sowie entsprechende Datenausgaben k&ouml;nnen
+durch
+eigene Parameter gesteuert werden (nicht mehr &uuml;ber die
+Feuchteparameter).&nbsp; </p>
+
+      
+      <p>Im Fall von pdims(1)=1 (eindimensionales virtuelles
+Prozessornetz in
+y-Richtung) werden die zyklischen Randbedingungen in x-Richtung durch
+direktes
+Umspeichern anstatt durch&nbsp; <tt>sendrecv </tt>realisiert. Ebenso
+werden
+die Transponierungen xz, yz, zx&nbsp; und zy eingespart (es wird aber
+weiter
+umsortiert).&nbsp; </p>
+
+      
+      <p>Im Fall von 3D-Plotausgaben Aufruf von ftpcopy-Script durch
+batch_scp-Script
+ersetzt (dient der Ermittelung von Dateizyklusnummern als Information
+f&uuml;r
+die AVS-fld-Datei).&nbsp; </p>
+
+      
+      <p>Bei fehlerhafter Er&ouml;ffnung einer CPU_MEASURES-Datei
+werden erneute
+Er&ouml;ffnungsversuche durchgef&uuml;hrt.</p>
+
+      </td>
+
+      <td>advec_particles, check_open, check_parameters,
+exchange_horiz, flow_statistics,
+header, init_particles, modules, package_parin, parin, plot_2d,
+plot_3d,
+prognostic_equations, read_var_list, transpose_xz, transpose_yz,
+transpose_zx,
+transpose_zy, write_var_list</td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">02/05/02</td>
+
+      <td>SR</td>
+
+      <td>2.3e</td>
+
+      <td>B</td>
+
+      <td>Wiedereinf&uuml;hrung der 3D-Felder f&uuml;r die Zeitebene
+t+dt, die
+notwendig ist, damit in den Diffusionstermen bei Leapfrog-Zeitschritten
+mit der korrekten Zeitebene t-dt gearbeitet wird. Seit Version 2.2
+wurde
+f&auml;lschlicherweise die Zeitebene t+dt verwendet. Asselin-Filter ist
+jetzt wieder eigenst&auml;ndiges Unterprogramm. <br>
+
+Die Wiedereinf&uuml;hrung dieser dritten Zeitebene ist auch
+Voraussetzung
+f&uuml;r die in der n&auml;chsten Version geplante skalare
+Optimierung.&nbsp;
+      
+      <p>Fehler bei Berechnung von Ausgabezeitpunkten eliminiert (trat
+auf, wenn
+bei Fortsetzungsl&auml;ufen von Ausgabeabst&auml;nden 0.0 auf von Null
+verschiedene Werte gewechselt werden sollte).&nbsp; </p>
+
+      
+      <p><b>Achtung:</b> Der Inhalt der Testergebnis-Datei &auml;ndert
+sich durch
+diese Fehlerkorrektur.</p>
+
+      </td>
+
+      <td>init_3d_model, leap_frog, modules, prognostic_equations,
+swap_timelevel&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+asselin_filter</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td>02/05/02</td>
+
+      <td>SR</td>
+
+      <td>2.3e</td>
+
+      <td>N/C</td>
+
+      <td>Kleinere Anpassungen an IBM-Regatta-Systeme in
+check_parameters, cpu_log.&nbsp;
+      
+      <p>Modul singleton in eigenst&auml;ndige Datei
+&uuml;berf&uuml;hrt.&nbsp; </p>
+
+      
+      <p>Global_min_max arbeitet mit REAL*4, um Komplikationen auf
+32-bit-Rechnern
+zu vermeiden (Datentyp MPI_2REAL m&uuml;sste dort sonst auf
+MPI_2DOUBLE_PRECISION
+ge&auml;ndert werden). <br>
+
+Horizontale Geschwindigkeitskomponenten f&uuml;r Partikeladvektion
+werden exakt zwischen den jeweils benachbarten horizontalen
+Gitterfl&auml;chen
+interpoliert.</p>
+
+      </td>
+
+      <td nosave="">advec_particles, check_parameters, cpu_log,
+global_min_max,
+modules&nbsp;
+      
+      <p><b>Neu:</b> <br>
+
+singleton</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">11/06/02</td>
+
+      <td>SR</td>
+
+      <td>2.4</td>
+
+      <td>N/C</td>
+
+      <td>Optimierung und Anpassungen f&uuml;r einzelne Knoten der
+IBM-Regatta-Systeme.
+      
+      <p><b>Skalare (Cache) Optimierung:</b> Tendenzterme werden
+innerhalb einer
+gro&szlig;en (i,j)-Schleife berechnet, die nun jeweils die gesamte
+prognostische
+Gleichung umfasst. Schleifenindices i und j werden an die
+Tendenzunterprogramme
+als Argumente &uuml;bergeben. Die Tendenzunterprogramme sind als Module
+geschrieben, die mittels Technik der &uuml;berladenen Funktionen auch
+ohne
+diese Indices i und j aufgerufen werden k&ouml;nnen, und dann wie in
+fr&uuml;heren
+Versionen funktionieren (d.h. in ihnen laufen die Schleifen &uuml;ber
+alle
+3 Dimensionen). Solche Teile der prognostischen Gleichungen, die
+globale
+Kommunikation beinhalten, sind vor die (i,j)-Schleife gezogen. Falls
+ausschlie&szlig;lich
+mit Piascek-Williams-Advektion gearbeitet wird, werden alle
+prognostischen
+Gleichungen in einer einzigen (i,j)-Schleife gerechnet. </p>
+
+      
+      <p><b>Kommunikationsoptimierung:</b> Zus&auml;tzliche
+Implementierung einer
+1D-Gebietszerlegung in x-Richtung. Mit dem neuen direkten
+Druckl&ouml;ser
+(poisfft_hybrid) werden dadurch 4 von 6 notwendigen Transpositionen
+eingespart.
+Die 1D-Zerlegung wird automatisch bei Verwendung dieses neuen
+L&ouml;sers
+aktiviert. Austausch von Geisterr&auml;ndern in y-Richtung wird bei
+dieser
+1D-Zerlegung durch einfache zyklische Randbedingungen ersetzt. </p>
+
+      
+      <p><b>Kleinere Anpassungen:</b> String-Vergleiche erfordern beim
+IBM-Compiler
+in der Regel den Einsatz der TRIM-Funktion, um &uuml;bersch&uuml;ssige
+Blanks am Ende des Strings abzuschneiden (sonst liefert der Vergleich
+.F.). <br>
+
+Lokal allokierte Felder t.w. in sogenannte automatische Felder
+umgewandelt
+(g&uuml;nstiger, um Gefahr von eventuellen Speicherlecks zu vermeiden).
+Einige Feldoperationen wurden wegen schlechter Performance auf der IBM
+entfernt (s. pres). </p>
+
+      
+      <p><b>Achtung: </b>Die &Uuml;bersetzung des Modells erfordert
+aufgrund
+der Vielzahl nunmehr eingesetzter Module die Verwendung des
+make-Mechanismus,
+um die korrekte Reihenfolge bei der &Uuml;bersetzung der Programmteile
+zu gew&auml;hrleisten. Die Beschreibung dieser Abh&auml;ngigkeiten
+erfolgt
+in der Datei<tt> Makefile</tt>, die zusammen mit den Programmdateien
+abgelegt
+ist und ebenfalls unter RCS-Verwaltung steht. </p>
+
+      
+      <p>Im User-Interface ist das Unterprogramm<tt> user_actions </tt>nun
+ebenfalls
+als Modul geschrieben und bedient sich der Methode der &uuml;berladenen
+Funktionen. Existierende benutzereigene Software muss entsprechend
+angepasst
+werden.</p>
+
+      </td>
+
+      <td>advec_s_pw, advec_s_up, advec_u_pw, advec_u_up, advec_v_pw,
+advec_v_up,
+advec_w_pw, advec_w_up, buoyancy, calc_precipitation, calc_radiation,
+calc_spectra,
+check_parameters, coriolis, diffusion_e, diffusion_s, diffusion_u,
+diffusion_v,
+diffusion_w, diffusivities, exchange_horiz, exchange_horiz_2d,
+global_min_max,
+header, impact_of_latent_heat, init_pegrid, leap_frog, modules,
+plot_2d,
+plot_3d, plot_spectra, poisfft, pres, production_e,
+prognostic_equations,
+user_interface,
+      
+      <p><b>Neu:</b> <br>
+
+fft_for_1d_decomp, Makefile, poisfft_hybrid,&nbsp;</p>
+
+      </td>
+
+    </tr>
+
+    <tr nosave="" valign="top">
+
+      <td nosave="">11/06/02</td>
+
+      <td>SR</td>
+
+      <td>2.4</td>
+
+      <td>B</td>
+
+      <td>Fehlende Variablenvereinbarung in <tt>advec_particles</tt>
+erg&auml;nzt.</td>
+
+      <td>advec_particles</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">12/09/02</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.4a</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">Partikel k&ouml;nnen mit Tr&auml;gheit versehen
+werden und
+einen Dichteunterschied zum umgebenden Fluid haben. Zur Steuerung dient
+der neue Paketparameter <tt>density_ratio</tt>.</td>
+
+      <td valign="top">advec_particles, header, init_particles,
+modules, package_parin</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">12/09/02</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.4a</td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Fehler in Berechnung der Anfangsprofile von pt
+und q entfernt
+(obere Feldgrenze von 10 konnte in <tt>pt_vertical_gradient_level_ind</tt>
+&uuml;berschritten werden). Fehler f&uuml;hrte unter Umst&auml;nden zu
+"segmentation fault" bei Verwendung sehr gro&szlig;er Gitterpunktzahlen
+in z-Richtung.
+      
+      <p>Fehler in Berechnung der v-Komponente am unteren Rand
+entfernt, die
+f&uuml;r den Scherungsproduktionsterm der TKE verwendet wird (Variable
+v_0). F&auml;lschlicherweise wurde zur Berechnung u(k=1) statt v(k=1)
+verwendet.</p>
+
+      </td>
+
+      <td valign="top">check_parameters, modules, production_e</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">19/12/02</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.5</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">Restart times can be set by user with new
+runtime (d3par)
+parameters <tt>restart_time</tt> and <tt>dt_restart</tt>. Run
+description
+header is written on file CONTINUE_RUN. Output of cpu statistics
+changed
+(PE results are now collected on PE0 in order to calculate mean cpu
+statistics).
+Output of warnings in the job protocol in case of negative measured
+cpu-times.
+Remaining cpu-time is also evaluated on IBM-Regatta.</td>
+
+      <td valign="top">cpu_log, cpu_statistics,
+check_parameters,header, leap_frog,
+local_tremain, local_tremain_ini, modules,&nbsp; palm,&nbsp;
+      
+      <p><b>new:</b> <br>
+
+check_for_restart </p>
+
+      
+      <p><b>deleted:</b> <br>
+
+check_cpu_time</p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">&nbsp;<br>
+
+      </td>
+
+      <td valign="top">&nbsp;<br>
+
+      </td>
+
+      <td valign="top">&nbsp;<br>
+
+      </td>
+
+      <td valign="top">C</td>
+
+      <td valign="top">Unit 14 (BINOUT) must be opened using a special
+process
+id string, because on IBM, the PE rank differs between communicators
+MPI_COMM_WORLD
+and comm_2d. This leads to a mismatch between filename-PE-number and
+PE-number
+written on file. As the consequence, these files could not be read by
+restart-jobs.
+Reading of array <tt>hom</tt> moved from <tt>init_3d_model </tt>to <tt>read_var_list</tt>
+(binary version number incremented to 2.2).
+      
+      <p><b>Further optimization for IBM-Regatta-systems:</b> <br>
+
+Additional optimization of the hybrid-solver for multinode usage
+(overlapping
+of communication and computation). </p>
+
+      
+      <p>Further cache optimization by using strides and joining loops (<tt>hybrid_solver,
+pres</tt> and <tt>timestep</tt>). Joining of MPI_ALLREDUCE calls in
+timestep. </p>
+
+      
+      <p>In case of 1d-decomposition along x only a part of the
+integral divisor
+conditions is checked, on IBM hosts a 1d-decomposition along x is the
+default,
+a switch from Poisson-FFT-solver to the hybrid-solver is made in case
+of
+1d-decomposition along x, the hybrid-solver does not force a
+1d-decomposition
+any more. </p>
+
+      
+      <p>Array notation changed to do-loop constructs due to better
+performance. </p>
+
+      
+      <p>Cyclic boundary conditions along <tt>y</tt> used instead of
+sendrecv
+in case of a 1d-decomposition along <tt>x</tt>. SENDRECV replaced by
+nonblocking
+routines ISEND and IRECV in <tt>exchange_horiz.f90</tt>. </p>
+
+      
+      <p>Speed optimization by removing MINVAL/MAXVAL calls and by
+handling <br>
+
+the "abs" case in a different way than the min/max cases (routine <tt>global_min_max</tt>).</p>
+
+      </td>
+
+      <td valign="top">asselin_filter, check_open, exchange_horiz,
+global_min_max,
+init_3d_model, init_pegrid, parin, poisfft_hybrid, read_var_list,
+timestep,
+write_3d_binary, write_var_list</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Correction of mixing length term (l(k)/ll(k)).
+The condition
+kh=3*km in the unstable case is now also exactly met in the wall
+adjustment
+region. Factor 0.7 in wall adjustment part replaced by variable <tt>wall_adjustment_factor</tt>,
+which is set to 1.8 in <tt>modules.f90</tt>. The factor 0.7 was the
+possible
+reason for 2-delta-x-waves, which were observed since version 2.1d.
+      
+      <p>Calculation of deformation tensor re-designed (<tt>production_e</tt>).
+      </p>
+
+      
+      <p>STOP statements replaced by call of new subroutine <tt>local_stop,
+      </tt>where
+MPI_FINALIZE is called before STOP in case of a parallel environment. </p>
+
+      
+      <p>ISO2D parameter dp set to true for ibm hosts. </p>
+
+      
+      <p>tend=p added in <tt>pres</tt> after calling sor method.</p>
+
+      </td>
+
+      <td valign="top">advec_s_bc, buoyancy, check_open,
+check_parameters, close_file,
+coriolis, diffusion_e, diffusivities, fft_for_1d_decomp,
+flow_statistics,
+init_3d_model, init_dvrp, init_grid, init_particles, init_pegrid,
+parin,
+plot_2d, poisfft, pres, read_var_list, user_interface,&nbsp;
+      
+      <p><b>new:</b> <br>
+
+local_stop, production_e</p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">03/03/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.5a</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">Particle velocities are also stored in array
+particles in
+case of zero density ratio. Steering of variables by dvrp browser
+included.</td>
+
+      <td valign="top">advec_particles, init_dvrp, modules,</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">C</td>
+
+      <td valign="top">AVS data format changed from float to xdr_float
+(needed
+on linux machines <br>
+
+due to the little/big endian problem). Updates for new version of dvrp
+software (e.g. using module dvrp is now mandatory).</td>
+
+      <td valign="top">close_file, init_dvrp, leap_frog, plot_dvrp</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Error in particle inertia part removed (exp_arg
+must not
+contain the timestep). <br>
+
+Error in calculation of the vertical flux of resolved scale energy
+(profile 57) removed. Displacement for integers in mpi_particle_type
+reduced
+from 16 to 8 on ibm.</td>
+
+      <td valign="top">advec_particles, flow_statistics, init_particles</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">12/03/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.6</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top"><b>Version optimized for NEC-SX6 parallel-vector
+machines.&nbsp;</b>
+      
+      <p>There are two main changes. A new vectorizable routine <tt>prognostic_equations_vec</tt>
+is added, where cache optimizations are undone. The tendency
+subroutines
+called by <tt>prognostic_equations_vec</tt> contain the full 3d-loops
+(compared
+with the cache-optimized versions where only loops over k are carried
+out).
+Additionally, a new pressure solver <tt>poisfft_hybrid_vec</tt> is
+added,
+which requires a 1d-domain-decomposition (like poisfft_hybrid). In this
+solver, a very fast FFT from Clive Temperton (ECMWF) is&nbsp;
+optionally
+available by choosing <tt>fft_method </tt>= <i>'temperton-algorithm'</i>.&nbsp;
+      </p>
+
+      
+      <p>Additional changes in <tt>flow_statistics</tt> to allow
+better vectorization. </p>
+
+      
+      <p>Small changes in routines <tt>diffusivities</tt> and <tt>pres</tt>
+which
+caused run time errors on IBM and NEC due to compiler problems. </p>
+
+      
+      <p>Reading of environment variable <tt>tasks_per_node</tt> moved
+from routine <tt>poisfft_hybrid</tt>
+to routine <tt>parin</tt>. </p>
+
+      
+      <p><b>Changes in makefile:</b> modules and user_interface now
+depend on
+the f90 files, dependency of singleton added, LDFLAGS moved to the end
+of PROG rule, temperton_fft added.</p>
+
+      </td>
+
+      <td valign="top">advec_s_pw, advec_s_up, advec_u_pw, advec_u_up,
+advec_v_pw,
+advec_v_up, advec_w_pw, advec_w_up, buoyancy, calc_precipitation,
+calc_radiation,
+check_parameters, coriolis, cpu_log, diffusion_e, diffusion_s,
+diffusion_u,
+diffusion_v, diffusion_w, diffusivities, fft_for_1d_decomp, header,
+impact_of_latent_heat,
+init_pegrid, leap_frog, local_tremain, modules, parin, poisfft,
+poisfft_hybrid,
+pres, production_e, prognostic_equations, user_interface
+      
+      <p><b>new:</b> <br>
+
+temperton_fft</p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">tend=p added in routine <tt>pres</tt> after
+calling sor
+method.</td>
+
+      <td valign="top">pres</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">14/03/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.6a</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">Additional vector optimization for NEC-SX6.
+      
+      <p>Optional system-specific random number generator available
+(for equal
+distributed numbers). </p>
+
+      
+      <p>Define strings in all relevant subroutines changed from&nbsp; </p>
+
+      
+      <p><tt>&nbsp;&nbsp;&nbsp;&nbsp; #if defined( define_string )</tt>
+      </p>
+
+      
+      <p>to </p>
+
+      
+      <p><tt>&nbsp;&nbsp;&nbsp;&nbsp; #if defined( __define_string )</tt>
+      </p>
+
+      
+      <p><b>Caution: </b>The relevant subroutines are NOT listed in
+the right
+column!</p>
+
+      </td>
+
+      <td valign="top">asselin_filter, check_parameters, diffusion_e,
+diffusivities,
+disturb_field, global_min_max, header, local_tremain, modules, parin,
+poisfft_hybrid,
+pres, read_var_list, write_var_list</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Error in particle boundary condition removed
+(velocity must
+be inverted in case of reflection)</td>
+
+      <td valign="top">advec_particles</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">16/04/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.6b</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">Time series output of Monin Obukhov length.
+      
+      <p>Temperton fft can now be used for all hosts and every domain
+decomposition.
+Abort in case of Temperton fft, if number of gridpoints along x and/or
+y contain illegal factors.&nbsp; </p>
+
+      
+      <p>Index values for the extrema found in global_min_max are
+limited to
+the range 0..nx, 0..ny (on IBM machines -1 and nx+1/ny+1 occured which
+produced different RUN_CONTROL output compared to other machines). </p>
+
+      
+      <p>Output format of iteration count in routine run_control
+enlarged.</p>
+
+      </td>
+
+      <td valign="top">check_parameters, fft_for_1d_decomp,
+global_min_max, init_pegrid,
+modules, plot_ts, poisfft, run_control, temperton_fft</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Additional checks of variables <tt>hybrid_solver</tt>
+and <tt>host</tt>
+(<tt>hybrid_solver</tt> must not be used for a 2d-domain-decomposition,
+      <tt>host</tt>
+should be set by setting environment variable <tt>localhost</tt>).
+      
+      <p>Header output for mixing length limitations revised.</p>
+
+      </td>
+
+      <td valign="top">check_parameters, header</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">09/05/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.7</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top"><b>Version running on Linux Clusters using MPICH
+and Intel
+FORTRAN compiler (ifc)</b>
+      
+      <p>So far, only absolutely neccessary changes have been done
+(possible
+optimizations will follow in a later version): </p>
+
+      
+      <p>New time measurements for Linux (ifc) environment added. </p>
+
+      
+      <p>Some parameters in MPI calls had to be modified (arrays had to
+be replaced
+by the first element of the regarding array) in order to fulfill f90
+type
+and rank requirements, since on the MUK-cluster a FORTRAN90-version of
+MPI is used. This also required to replace "mpif.h" by using a special
+module (named <tt>mpi</tt>).&nbsp; I did not find out how character
+strings
+can be send with MPI. Therefore, these strings are transformed to
+integers,
+before they are send, and transformed back to characters on the
+receiving
+PE. </p>
+
+      
+      <p>On the MUK-cluster, only PE0 is able to read the values of
+environment
+variables. Therefore, these values are communicated via broadcast to
+the
+other PEs. </p>
+
+      
+      <p>1d-decomposition is set as the default on Linux Clusters.
+Character
+strings have to be transformed to integer </p>
+
+      
+      <p>Smaller changes: </p>
+
+      
+      <p>Batch_scp paths for IBM, NEC and Linux added</p>
+
+      </td>
+
+      <td valign="top">check_open, cpu_log, flow_statistics,
+init_pegrid, local_getenv,
+modules, palm, poisfft_hybrid</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Measurements on IBM are now using function <tt>irtc</tt>,
+which allows correct measurements for jobs running over the 24:00
+timeline.</td>
+
+      <td valign="top">cpu_log, local_tremain, local_tremain_ini</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">01/08/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.7a</td>
+
+      <td valign="top">B</td>
+
+      <td valign="top">Check that the number processors is also an
+integral divisor
+of the number&nbsp; of gridpoints along y in case of a 1d-decomposition
+along x.
+      
+      <p>Error concerning the multinode-version of poisfft_hybrid
+removed. It
+was caused by the Linux changes of version 2.7 and led to program abort
+due to MPI errors in <tt>MPI_ALLTOALL</tt>. </p>
+
+      
+      <p>No abort on t3e-systems if system specific routines are used. </p>
+
+      
+      <p>Array<tt> sums </tt>is initialized in<tt> init_3d_model </tt>before
+the first call of<tt> pres</tt>. Call of<tt> init_cloud_physics </tt>moved
+before<tt> init_particles</tt>.</p>
+
+      </td>
+
+      <td valign="top">fft_1dd_init, init_3d_model, init_pegrid,
+poisfft_hybrid</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">Interactive steering of dvrp-graphic features by
+dvrp-browser
+plugin extended (position of slicers, threshold values of isosurfaces)
+. New dvrp_graphics package parameter<tt> slicer_range_limits_dvrp</tt>.</td>
+
+      <td valign="top">init_dvrp, modules, package_parin, plot_dvrp</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top">29/10/03</td>
+
+      <td valign="top">SR</td>
+
+      <td valign="top">2.7b</td>
+
+      <td valign="top">N</td>
+
+      <td valign="top">In the multigrid method, on a defined level,
+data are gathered
+on PE0 and further calculations are carried out only on this PE. New<tt>
+d3par </tt>parameter <tt>mg_switch_to_pe0_level</tt>.
+      
+      <p>Particle groups implemented. New data type<tt>
+particle_groups_type </tt>and data type<tt> particle_type </tt>modified.
+Version
+numbers are
+output on the particle files. New<tt> particles_par </tt>parameter<tt>
+diameter</tt>. Parameter name<tt> uniform_psize</tt> changed to<tt>
+dvrp_psize</tt>.
+Parameters<tt> density_ratio </tt>is now an array.</p>
+
+      </td>
+
+      <td valign="top">advec_particles, check_open, exchange_horiz,
+header, init_particles,
+init_pegrid, modules, package_parin, parin, poismg</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">C</td>
+
+      <td valign="top">Random number generator from numerical recipes
+is now rewritten
+as a module. In restart runs the seed of this generator is set to the
+last
+values of the previous run in order to keep the sequence of the random
+numbers. New binary version 2.2.
+      
+      <p>Buffer is flushed for file RUN_CONTROL immediately after every
+output
+on IBM and Linux cluster.</p>
+
+      </td>
+
+      <td valign="top">advec_particles, disturb_field, init_3d_model,
+init_particles,
+random_function, random_gauss, run_control, write_3d_binary</td>
+
+    </tr>
+
+    <tr>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top"><br>
+
+      </td>
+
+      <td valign="top">E</td>
+
+      <td valign="top">In routine buoyance, horizontal mean temperature
+is now
+taken from array hom instead of array sums (otherwise inconsistence in
+case of using more than one statistical region).
+      
+      <p>Information about the time of the last timestep change added
+to the
+restart file. </p>
+
+      
+      <p>System call of<tt> batch_scp </tt>on IBM corrected.</p>
+
+      </td>
+
+      <td valign="top">buoyancy, check_open, read_var_list,
+write_var_list</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">28/01/04</td>
+
+      <td style="vertical-align: top;">SR</td>
+
+      <td style="vertical-align: top;">2.8</td>
+
+      <td style="vertical-align: top;">N</td>
+
+      <td style="vertical-align: top;">Runge-Kutta schemes (2nd and 3rd
+order)
+for time integration implemented. The third order scheme is the new
+default.
+It allows the timestep to be 0.9*CFL, which is much larger than for the
+former default leapfrog scheme.&nbsp; The intermediate steps, which are
+part of these schemes, are realized by an additional loop within routine<span style="font-family: monospace;">
+time_integration&nbsp;</span>(currently<span style="font-family: monospace;">
+leap_frog</span>, but this routine will be renamed soon). Steering
+variables<span style="font-family: monospace;">
+at&nbsp;</span>and<span style="font-family: monospace;"> bt&nbsp;</span>have
+been replaced by array<span style="font-family: monospace;"> sct</span>.
+, which is particularly used in the prognostic equations. Values of
+this
+steering array are calculated within the new routine<span style="font-family: monospace;">
+timestep_scheme_steering</span>.
+      
+      <p>When using Runge-Kutta schemes,&nbsp; the timestep increment
+is freely
+allowed to adjust after each timestep (the older schemes are using some
+restrictions, see routine<span style="font-family: monospace;"> timestep</span>).
+Also, routine<span style="font-family: monospace;"> run_control&nbsp;</span>is
+not automatically called in case of timestep changes, when Runge-Kutta
+schemes are switched on. </p>
+
+      
+      <p>The old leapfrog scheme is still implemented and should
+produce the
+same results as in the previous version(s)! </p>
+
+      
+      <p>Depending on the user experience, further adjustments to the
+Runge-Kutta
+schemes may be necessary within the next minor versions.&nbsp; </p>
+
+      
+      <p><span style="font-weight: bold;">Attention:</span> <br>
+
+The content of the testresult-file (run control output) has
+significantly
+changed due to the new default timestep scheme!</p>
+
+      </td>
+
+      <td style="vertical-align: top;">check_parameters, header,
+init_3d_model,
+init_rankine, leap_frog, modules, prognostic_equations, read_var_list,
+swap_timelevel, timestep, write_var_list
+      
+      <p><span style="font-weight: bold;">new:</span> <br>
+
+timestep_scheme_steering</p>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">C</td>
+
+      <td style="vertical-align: top;">Output of particle infos in
+subroutine<span style="font-family: monospace;">
+allocate_prt_memory&nbsp;</span>on demand only.
+      
+      <p>Type<span style="font-family: monospace;"> log&nbsp;</span>(used
+for
+cpu time measurements) changed to<span style="font-family: monospace;">
+logpoint&nbsp;</span>due to name conflict with FORTRAN intrinsic<span style="font-family: monospace;">
+log.</span></p>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_particles, cpu_log,&nbsp;</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E</td>
+
+      <td style="vertical-align: top;">In case of opening unit 80, a
+barrier
+is set only for the first call of<span style="font-family: monospace;">
+check_open&nbsp;</span>(from routine<span style="font-family: monospace;">
+init_particles</span>), in order to avoid the possibility of hanging
+jobs,
+which may occur if unit 80 is opened within routine<span style="font-family: monospace;">
+allocate_prt_memory</span>.</td>
+
+      <td style="vertical-align: top;">check_open</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">30/01/04</td>
+
+      <td style="vertical-align: top;">SR</td>
+
+      <td style="vertical-align: top;">2.8a</td>
+
+      <td style="vertical-align: top;">N</td>
+
+      <td style="vertical-align: top;">In order to prepare the code for
+the simulation
+of flow around buildings (to be realized in one of the next major
+versions),
+the lower<span style="font-family: monospace;"> k&nbsp;</span>index<span style="font-family: monospace;">
+nzb&nbsp;</span>has been replaced by a two-dimensional array<span style="font-family: monospace;">
+nzb_2d&nbsp;</span>in many of the three-dimensional loops. So far, all
+elements of this array are set to<span style="font-family: monospace;">
+nzb</span>.
+      
+      <p>This change should not effect simulation results and cpu time
+in any
+way.</p>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_s_pw, advec_s_up,
+advec_u_pw, advec_u_up,
+advec_v_pw, advec_v_up, advec_w_pw, advec_w_up, asselin_filter,
+buoyancy,
+calc_liquid_water_content, calc_precipitation, calc_radiation,
+coriolis,
+diffusion_e, diffusion_s, diffusion_u, diffusion_v, diffusion_w,
+diffusivities,
+impact_of_latent_heat, init_3d_model, modules, production_e,
+prognostic_equations,&nbsp;</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">C</td>
+
+      <td style="vertical-align: top;">Euler step informations are
+removed in
+the run control output in case of Runge-Kutta schemes. Also, the
+timestep
+increment limitation is removed for the Runge-Kutta schemes.
+      
+      <p><span style="font-weight: bold;">Attention:</span> <br>
+
+The content of the testresult-file (run control output) has changed
+due to this modification.</p>
+
+      </td>
+
+      <td style="vertical-align: top;">run_control, timestep</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E</td>
+
+      <td style="vertical-align: top;">Velocity gradients at the
+surface calculated
+in routine production_e are now limited. In case of inhomogeneous
+surface
+heating small diffusivities (<span style="font-family: monospace;">km</span>)
+sometimes caused very small timesteps due to this problem.</td>
+
+      <td style="vertical-align: top;">production_e</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">30/04/04<br>
+
+      </td>
+
+      <td style="vertical-align: top;">SR<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2.8b<br>
+
+      </td>
+
+      <td style="vertical-align: top;">N<br>
+
+      </td>
+
+      <td style="vertical-align: top;">The number of processors along
+the respective directions of the virtual processor grid must not be
+integral divisors of the number of gridpoints along x, y or z any more.
+In case that they are not integral divisors, the subdomains on the
+processors at the upper borders of the virtual grid will contain less
+gridpoints than the other subdomains (which are all of equal size).
+Although this causes a load imbalance, only runs with very small
+numbers of processors will feel a significant decrease of performance.
+In order to be able to carry out the transpositions, array<span style="font-family: monospace;"> d </span>(and also working array<span style="font-family: monospace;"> tend</span>) have the same size on
+all processors. This new feature is switched on by setting the
+inipar-parameter<span style="font-family: monospace;"> grid_matching </span>=
+      <span style="font-style: italic;">'match'</span>, which is the
+default now.<br>
+
+      <br>
+
+Routine<span style="font-family: monospace;"> poisfft </span>is now
+the
+default for solving the Poisson-equation for the case of 2d- as well as
+1d-domain-decompositions and has been changed from a subroutine to a
+module. This routine now includes most of the optimization from the
+(Ketelsen) routine<span style="font-family: monospace;"> poisfft_hybrid
+      </span>and additionally allows 1d-decompositions along y.<br>
+
+      <span style="font-weight: bold;">ATTENTION:</span> Routine<span style="font-family: monospace;"> poisfft_hybrid </span>might still be
+faster when running PALM on more than one node of the IBM-Regatta,
+although the difference is not very big. The <span style="font-family: monospace;">poisfft</span>-code for a
+decomposition along y has still a poor performance and needs further
+optimization.<br>
+
+      <br>
+
+The spectra-package is now able to use all the available FFT-methods
+(selected by inipar-parameter<span style="font-family: monospace;">
+fft_method </span>).
+Performance of the transpositions needed for calculating the spectra
+has been improved by using new direct transpositions from z to y and
+from y to x instead of two subsequent transpositions.<br>
+
+      <br>
+
+Runge-Kutta scheme implemented in the 1d-version (<span style="font-family: monospace;">init_1d_model</span>). Diffusion
+quantity arrays are allocated for previous timelevels only in case of
+leapfrog scheme.<br>
+
+      <br>
+
+This version is adapted for use on COMPAQ-DECALPHA systems (main
+changes: calling of SHAPE function within subroutine arguments (e.g.<span style="font-family: monospace;"> singleton</span>)
+causes compiler errors, particle data type modified for better
+alignment, DATA statements from modules removed because they caused
+internal compiler errors).<br>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_s_ups, advec_u_ups,
+advec_v_ups, advec_w_ups, calc_spectra, check_parameters, fft_xy,
+header, init_1d_model, init_3d_model, init_particles, init_pegrid,
+modules, parin, plot_2d, poisfft, prandtl_fluxes, pres, read_var_list,
+singleton, spline_x, spline_y, spline_z, time_integration, transpose,
+write_3d_binary, write_var_list<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">C<br>
+
+      </td>
+
+      <td style="vertical-align: top;">FFT routines renamed. Module<span style="font-family: monospace;"> fft_for_1d_decomp </span>renamed<span style="font-family: monospace;"> fft_xy</span>. Subroutine<span style="font-family: monospace;"> leap_frog </span>renamed<span style="font-family: monospace;"> time_integration</span>.<br>
+
+      <br>
+
+For all transpositions, MPI_ALLTOALL is used instead of MPI_ALLTOALLV.
+The names of many transposition indices have been changed.<br>
+
+      <br>
+
+Inipar-parameter<span style="font-family: monospace;"> impulse_advec </span>renamed<span style="font-family: monospace;"> momentum_advec</span>.<br>
+
+      <br>
+
+Reading of restart data is moved from<span style="font-family: monospace;"> init_3d_model </span>to new routine <span style="font-family: monospace;">read_3d_binary</span>.<br>
+
+      <br>
+
+All former transpose routines collected into one file.<br>
+
+      </td>
+
+      <td style="vertical-align: top;">check_parameters,
+flow_statistics, header, init_1d_model, init_3d_model, init_advec,
+init_pegrid, palm, parin, poisfft, poisfft_hybrid, production_e,
+prognostic_equations, read_var_list, sline_x, spline_y, write_var_list<span style="font-weight: bold;"><br>
+
+      <br>
+
+new:</span><br>
+
+fft_xy, read_3d_binary, time_integration, transpose<br>
+
+      <br>
+
+      <span style="font-weight: bold;">deleted:</span><br>
+
+fft_for_1d_decomp, leap_frog, transpose_xy, transpose_xz, transpose_yx,
+transpose_yz, transpose_zx, transpose_zy<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Small errors in the
+particle-package removed, which sometimes caused aborts of restart runs
+on IBM.<br>
+
+      <br>
+
+Small error in calculating the time series profiles removed (array
+bounds of some arrays needed for profil-output had to be increased).<br>
+
+      <br>
+
+Function fft (singleton method) replaced by subroutine fftn due to
+problems with 64-bit mode on IBM<br>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_particles,
+check_parameters, <br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">26/03/05<br>
+
+      </td>
+
+      <td style="vertical-align: top;">SR<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2.9<br>
+
+      </td>
+
+      <td style="vertical-align: top;">N<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Non-cyclic lateral boundary
+conditions implemented.<br>
+
+Dirichlet/Neumann conditions at the inflow/outflow can be used either
+along x or along y. Cyclic conditions have to be used along the
+remaining direction. In case of non-cyclic conditions along x (y), the
+upper bound nxl (nyn) of array u (v) is enlarged by one gridpoint on
+the rightmost (northest) processor. These array index informations are
+passed to routine<span style="font-family: monospace;"> exchange_horiz </span>and<span style="font-family: monospace;"> disturb_field </span>by two
+additional arguments. Boundary conditions are set with new
+inipar-parameters<span style="font-family: monospace;"> bc_lr </span>and<span style="font-family: monospace;"> bc_ns</span>. A damping layer is
+needed at the outflow in order to damp reflections (see new parameters<span style="font-family: monospace;"> km_damp_max </span>and<span style="font-family: monospace;"> outflow_damping_width</span>) and an
+additional disturbance is imposed near the inflow (see new parameters<span style="font-family: monospace;">&nbsp; inflow_disturbance_begin </span>and<span style="font-family: monospace;"> inflow_disturbance_end</span>).
+Non-cyclic conditions require the use of the multigrid-method for
+solving the Poisson equation. Argument<span style="font-family: monospace;"> range </span>added to routine<span style="font-family: monospace;"> boundary_conds </span>(where the
+non-cyclic conditions are set). <br>
+
+      <br>
+
+Minor changes:<br>
+
+Output of parameter<span style="font-family: monospace;"> datform </span>on
+&amp;GLOBAL-Namelist (iso2d). This is set to <span style="font-style: italic;">'big_endian'</span> on IBM- and
+NEC-machines.<br>
+
+      <br>
+
+Number of particle groups are additionally calculated in<span style="font-family: monospace;"> header </span>(formerly unknown).<br>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_u_pw,
+advec_u_up, advec_v_pw, advec_v_up, boundary_conds,
+calc_liquid_water_content, check_parameters, close_file, coriolis,
+diffusion_u, diffusion_v, diffusion_w, diffusivities, disturb_field,
+exchange_horiz, header, init_3d_model, init_pegrid, init_pt_anomaly,
+init_rankine, modules, parin, poismg, pres, prognostic_equations,
+read_var_list, sor, time_integration, timestep, write_var_list<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">C<br>
+
+      </td>
+
+      <td style="vertical-align: top;"><span style="font-family: monospace;">pres </span>is called by default only
+at the last Runge-Kutta-substep, which spares a big amount of CPU-time
+(see also new parameter<span style="font-family: monospace;">
+call_psolver_at_all_substeps</span>). No pressure term in the momentum
+equations in case of Runge-Kutta-schemes.<br>
+
+      <span style="font-weight: bold;">Attention:</span> <br>
+
+The content of the testresult-file (run control output) has changed
+due to this modification.<br>
+
+      <br>
+
+Program speedup by removing the exchange of ghost points in routines <span style="font-family: monospace;">calc_liquid_water_content</span>, <span style="font-family: monospace;">diffusivities</span>, .<br>
+
+      <br>
+
+Default value for residual limit increased from 1E-6 to 1E-4. Routine<span style="font-family: monospace;"> prolong </span>in<span style="font-family: monospace;"> poismg </span>simplified (one call of<span style="font-family: monospace;"> exchange_horiz </span>spared).<br>
+
+      </td>
+
+      <td style="vertical-align: top;">calc_liquid_water_content,
+diffusivities, modules, poismg, pres, time_integration,
+timestep_scheme_steering<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Calculation of vertical particle
+velocity (with inertia) corrected, exp_arg had a wrong sign.<br>
+
+      <br>
+
+(e)**1.5 replaced by e*SQRT(e) in init_1d_model because of wrong
+results on NEC machines (as a side effect, the new calculation is much
+faster).<br>
+
+      <br>
+
+Two errors concerning switch to PE0 (multigrid method) removed from<span style="font-family: monospace;"> init_pegrid</span>.<br>
+
+      <br>
+
+Two errors in<span style="font-family: monospace;"> plot_2d </span>removed:
+local_2d is allocated with upper bound<span style="font-family: monospace;"> nzt</span> (former<span style="font-family: monospace;"> nzt+1 </span>was
+wrong), additional barrier in case that PE0 gathers data from the other
+PEs, this barrier had to be set at the end of the gathering because
+otherwise PE0 sometimes received wrong data on tag 0.<br>
+
+      <br>
+
+Use of module indices removed from routine<span style="font-family: monospace;"> split_1dd </span>in<span style="font-family: monospace;"> poisfft </span>since it caused
+errors in case of<span style="font-family: monospace;"> nx /= ny </span>and
+a 1D-decomposition along y.<br>
+
+      <br>
+
+Wrong re-definition of dx2 and dy2 in<span style="font-family: monospace;"> sor </span>removed.<br>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_particles, init_1d_model,
+init_pegrid, plot_2d, poisfft, sor<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">23/04/05<br>
+
+      </td>
+
+      <td style="vertical-align: top;">SR<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2.9a<br>
+
+      </td>
+
+      <td style="vertical-align: top;">C<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Additional check for
+incompatibilities between non-cyclic lateral boundary conditions and
+other schemes.<br>
+
+      <br>
+
+fcl_factor renamed cfl_factor.<br>
+
+      <br>
+
+New local array sums_ll declared in flow_statistics instead of
+temporarily using sums_l.<br>
+
+      <br>
+
+crmax (maximum number of crosses allowed in a plot of vertical
+profiles) increased from 20 to 100.<br>
+
+      </td>
+
+      <td style="vertical-align: top;">calc_spectra, check_parameters,
+flow_statistics, header, modules, parin, timestep<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Revised calculation of output
+time counters regarding a possible decrease of the output time interval
+in case of restart runs.<br>
+
+      <br>
+
+Error removed in Dirichlet bottom boundary conditions for pt and q in
+case of Runge-Kutta schemes.<br>
+
+      <br>
+
+      <span style="font-weight: bold;">batch_scp</span> calls (needed
+for determining correct filenames for AVS-fld-files) is given the
+remote username as an additional argument.<br>
+
+      <br>
+
+Default setting of outflow_damping_width corrected.<br>
+
+      <br>
+
+Initial horizontal velocities at the lowest grid levels in the 1d-model
+are set to a very small value in order to avoid wrong results and the
+resulting too small timesteps.<br>
+
+      <br>
+
+Implicit counters i renamed i9 in modules due to declaration conflicts
+with i in other subroutines (reported by Portland compiler).<br>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_particles, boundary_conds,
+check_open, check_parameters, init_1d_model, modules, time_integration<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">18/05/05<br>
+
+      </td>
+
+      <td style="vertical-align: top;">SR<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2.10<br>
+
+      </td>
+
+      <td style="vertical-align: top;">N<br>
+
+      </td>
+
+      <td style="vertical-align: top;">NetCDF support implemented.<br>
+
+Profiles, time series, spectra, cross-sections, 3d-volume-data and
+particle data can now be output in NetCDF format (file handles
+101-108). This output can be switched on with the new d3par-parameter <span style="font-family: monospace;">data_output_format</span>.
+So far, this support is available on IBM systems at HLRN and on the NEC
+system at DKRZ. Output in format suitable for graphic software <span style="font-weight: bold;">profil</span>, <span style="font-weight: bold;">iso2d</span> and <span style="font-weight: bold;">avs</span> is still possible.<br>
+
+      <br>
+
+Output of cross sections for qv, vpt and lwp (liquid water path).<br>
+
+      </td>
+
+      <td style="vertical-align: top;">advec_particles, check_open,
+check_parameters, close_file, header, modules, parin, plot_1d, plot_2d,
+plot_3d, plot_spectra, plot_ts, read_var_list, write_var_list<br>
+
+      <br>
+
+      <span style="font-weight: bold;">new:</span><br>
+
+netcdf<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">C<br>
+
+      </td>
+
+      <td style="vertical-align: top;">In <span style="font-family: monospace;">calc_spectra</span>, n is assigned the
+number of spectra (formerly, the number of spectra was given by n-1)<br>
+
+      <br>
+
+Abort if <span style="font-family: monospace;">poisfft_hybrid</span>
+is called in a non-parallel environment.<br>
+
+      <br>
+
+Default values of spectra package parameters <span style="font-family: monospace;">pl_spectra</span> and <span style="font-family: monospace;">spectra_direction</span> changed.<br>
+
+      </td>
+
+      <td style="vertical-align: top;">calc_spectra, check_parameters,
+modules, pres, read_3d_binary, write_3d_binary<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Missing argument in ffty
+(non-parallel case) added.<br>
+
+      <br>
+
+Error in output of particle inertia information removed.<br>
+
+      </td>
+
+      <td style="vertical-align: top;">poisfft, header<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">05/07/05<br>
+
+      </td>
+
+      <td style="vertical-align: top;">SR<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2.11<br>
+
+      </td>
+
+      <td style="vertical-align: top;">N/C<br>
+
+      </td>
+
+      <td style="vertical-align: top;">New cloud physics code
+implemented, which explicitly simulates single cloud droplets,
+including droplet growth by condensation and collision. Using this code
+requires to set the new inipar-parameter <span style="font-family: monospace;">cloud_droplets</span> = .TRUE. and to use the particle package (by using the <span style="font-weight: bold;">mrun</span>-option <span style="font-family: monospace;">-p particles</span>). Coupling between droplets and the thermodynamic quantities (potential
+temperature and specific humidity) is regarded in the new subroutine <span style="font-family: monospace;">interaction_droplets_ptq</span>. The real number of droplets in a grid cell can steered by the new inipar-parameter <span style="font-family: monospace;">initial_weighting_factor</span>.<br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">This code will be further extended and probably changed in the near future, so the current status is that of a test version!</span><br>
+
+
+      <br>
+
+
+In connection with this new code implementation, several changes has been made to the existing code:<br>
+
+
+      <br>
+
+
+The particle (droplet) size is now given as radius (previously diameter). E.g., the name of the respective package parameter <span style="font-family: monospace;">diameter</span> has changed to <span style="font-family: monospace;">radius</span>.<br>
+
+
+      <br>
+
+
+The current weighting_factor and radius are stored as additional particle attributes in the type structure <span style="font-family: monospace;">particle_type</span>. The MPI data type <span style="font-family: monospace;">mpi_particle_type</span>, needed for exchanging particles between subdomains, has been changed correspondingly.<br>
+
+
+      <br>
+
+
+      <span style="font-family: monospace;">gas_constant</span> is renamed <span style="font-family: monospace;">r_d</span>, <span style="font-family: monospace;">latent_heat</span> is renamed <span style="font-family: monospace;">r_v</span>, the allowed string length of <span style="font-family: monospace;">pl2d</span> and <span style="font-family: monospace;">pl3d</span> is increased from 6 to 10.<br>
+
+
+      <br>
+
+
+New 3d arrays <span style="font-family: monospace;">ql_1</span>, <span style="font-family: monospace;">ql_2</span>, <span style="font-family: monospace;">ql_v</span> and <span style="font-family: monospace;">ql_vp</span>, <span style="font-family: monospace;">ql</span> is now a pointer, new pointer <span style="font-family: monospace;">ql_c</span>.<br>
+
+
+      <br>
+
+
+Data format for unit 85 (particle data output) is changed.</td>
+
+      <td style="vertical-align: top;">advec_particles.f90
+check_open.f90, header.f90, init_3d_model.f90, init_cloud_physics.f90,
+init_particles.f90, modules.f90, package_parin.f90, parin.f90,
+plot_2d.f90, plot_3d.f90, read_var_list.f90, time_integration.f90,
+write_var_list.f90<br>
+
+
+      <br>
+
+
+      <span style="font-weight: bold;">new:</span><br>
+
+
+interaction_droplets_ptq.f90</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">C<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Default value of <span style="font-family: monospace;">call_psolver_at_all_substeps</span> is <span style="font-style: italic;">.TRUE.</span>, because small scale waves occured with <span style="font-style: italic;">.FALSE.</span></td>
+
+      <td style="vertical-align: top;">modules.f90</td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2d- and 3d-NetCDF-files are not opened if there is no output for them (<span style="font-family: monospace;">pl2d</span> = <span style="font-family: monospace;">pl3d</span> = <span style="font-style: italic;">' '</span>).<br>
+
+
+      <br>
+
+
+No opening of units 101 - 108 in case of missing NetCDF support.</td>
+
+      <td style="vertical-align: top;">check_open.f90, netcdf.f90<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;">30/06/05<br>
+
+      </td>
+
+      <td style="vertical-align: top;">GS<br>
+
+      </td>
+
+      <td style="vertical-align: top;">2.11a<br>
+
+      </td>
+
+      <td style="vertical-align: top;">C<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Scalars ug and vg have been
+changed into
+arrays in order to allow the specification of a geostrophic wind that
+depends on height (baroclinicity). The initial profiles of the the
+u- and v-component of the geostrophic wind are initialized by
+specifying the new initialization parameters <span style="font-family: monospace;">ug_surface</span>,
+      <span style="font-family: monospace;">ug_vertical_gradient</span>, <span style="font-family: monospace;">ug_vertical_gradient_level</span> and <span style="font-family: monospace;">vg_surface</span>,
+      <span style="font-family: monospace;">vg_vertical_gradient</span>, <span style="font-family: monospace;">vg_vertical_gradient_level</span>, respectively. <br>
+
+      <br>
+
+The former initialization parameters <span style="font-family: monospace;">ug</span> and <span style="font-family: monospace;">vg</span> have been removed. <br>
+
+      </td>
+
+      <td style="vertical-align: top;">boundary_conds,
+check_parameters, coriolis, header, init_1d_model, modules, parin,
+prognostic_equations, read_var_list, spline_z, write_var_list<br>
+
+      </td>
+
+    </tr>
+
+    <tr>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;"><br>
+
+      </td>
+
+      <td style="vertical-align: top;">E<br>
+
+      </td>
+
+      <td style="vertical-align: top;">Error in the calculation of u_0
+and
+v_0 in production_e.f90 removed.<br>
+
+      <br>
+
+      <span style="font-weight: bold;">Attention:</span> <br>
+
+The content of the testresult-file (run control output) has changed
+due to this modification.<br>
+
+      </td>
+
+      <td style="vertical-align: top;">production_e<br>
+
+      </td>
+
+    </tr>
+    <tr>
+      <td style="text-align: left; vertical-align: top;">20/10/05</td>
+      <td style="vertical-align: top;">SR</td>
+      <td style="vertical-align: top;">2.11b</td>
+      <td style="vertical-align: top;">N/C</td>
+      <td style="vertical-align: top;">Collision process for droplet growth completed.<br>
+      <br>
+      <span style="font-weight: bold;">The droplet code is still under development and requires further speed optimization!<br>
+      <br>
+      </span>Number of particles really used is additionally output on the netcdf particle data file.<span style="font-weight: bold;"></span></td>
+      <td style="vertical-align: top;">advec_particles, modules, netcdf</td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">&nbsp;</td>
+      <td style="vertical-align: top;">&nbsp;</td>
+      <td style="vertical-align: top;">&nbsp;</td>
+      <td style="vertical-align: top;">E</td>
+      <td style="vertical-align: top;">The
+last PE in a row is not allowed to have more grid points than the other
+PES (only less). Jobs crashed in these cases that the last PE has more
+grid points. Therefore, the number of gridpoints along x (and y) must
+now meet a special condition which is checked in case that <span style="font-family: monospace;">grid_matching</span> = <span style="font-style: italic;">'match'</span> is used.<br>
+      <br>
+Error removed in calculating y axis data for yz cross sections. Error in output of netcdf yz-cross-sections removed.<br>
+      <br>
+2*r replaced by r in the exponential term of the particle momentum equation.<br>
+Error in output of yz-slice information removed.</td>
+      <td style="vertical-align: top;">advec_particles, header, init_pegrid, netcdf, plot_2d</td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">06/12/05</td>
+      <td style="vertical-align: top;">SR</td>
+      <td style="vertical-align: top;">2.11c</td>
+      <td style="vertical-align: top;">N</td>
+      <td style="vertical-align: top;">Output of ql profile is allowed in case of using cloud droplets.</td>
+      <td style="vertical-align: top;">check_parameters, flow_statistics, modules</td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">&nbsp;</td>
+      <td style="vertical-align: top;">&nbsp;</td>
+      <td style="vertical-align: top;">&nbsp;</td>
+      <td style="vertical-align: top;">E</td>
+      <td style="vertical-align: top;">The horizontally averaged pt profile is calculated within<span style="font-family: monospace;"> buoyancy </span>only
+in case of the first respective intermediate timestep. This is done in
+order to spare communication time and to produce identical model
+results with jobs which are calling<span style="font-family: monospace;"> flow_statistics </span>at different time intervals.<br>
+      <br>
+Error in netcdf variable declaration for<span style="font-family: monospace;"> statistic_regions </span>/= <span style="font-style: italic;">0</span> removed.</td>
+      <td style="vertical-align: top;">buoyancy, netcdf</td>
+    </tr><tr><td style="vertical-align: top;">23/02/06</td><td style="vertical-align: top;">SR</td><td style="vertical-align: top;">3.0</td><td style="vertical-align: top;">N</td><td><span style="font-weight: bold;">Version for simulating flows over topography (buildings, mountains, etc.)</span><br style="font-weight: bold;"><br>Besides
+the implementation of topography, this version contains several other
+improvements. The most important ones are listed here:<br><ul><li>The cloud droplet code has been optimized (it now runs about 100 times faster than before).</li><li>Output of time-averaged 2d/3d data (sections / volume data) is possible.</li><li>Output of 2d-section data averaged along the direction normal to this section can be done.</li><li>The user-interface has been extended in order to allow 2d-/3d-output of user-defined quantities.</li></ul>The kind of topography to be used is controlled by the new initialization parameter <span style="font-family: monospace;">topography</span>. Allowed values are <span style="font-style: italic;">'flat'</span>, <span style="font-style: italic;">'single_building'</span>, and <span style="font-style: italic;">'read_from_file'</span>. The user can define his own special topography setting within the new user-interface routine <span style="font-family: monospace;">user_init_grid</span>. For the single building case, the&nbsp;building (rectangular) size and position can be controlled with parameters <span style="font-family: monospace;">building_height</span>, <span style="font-family: monospace;">building_length_x</span>, <span style="font-family: monospace;">building_length_y</span>, <span style="font-family: monospace;">building_wall_left</span>, and <span style="font-family: monospace;">building_wall_south</span>.<br>
+      <br>
+The topography code is already optimized (vectorized) for use on the NEC-SX6.<br><br>Output of time-averaged 2d-/3d-data can be enabled by appending the string <span style="font-style: italic;">'_av'</span> to the respective output quantities given with the new runtime-parameter <span style="font-family: monospace;">data_output</span>
+(see further below for the (name)changes in the parameters for data
+output). Example: if a time-average of the vertical cross-section of
+potential temperature is required, the user has to set <span style="font-family: monospace;">data_output</span> = <span style="font-style: italic;">'pt_xy_av'</span>.
+In case of NetCDF-output, the time-averaged data is output to
+additional files (seperate from the non-averaged output). The length of
+the averaging interval and the temporal distance of the single
+instantaneous sections (volumes) entering into this averaging is
+controlled by the new runtime-parameters <span style="font-family: monospace;">averaging_interval</span>and <span style="font-family: monospace;">dt_averaging_input</span>. <br><br>An average normal to the direction of a cross-section can be output by setting the respective cross section index to <span style="font-style: italic;">-1</span> (example: <span style="font-family: monospace;">section_xz</span> = <span style="font-style: italic;">-1</span>).<br><br>New user-interface routines allowing the output of user-defined quantities are <span style="font-family: monospace;">user_check_data_output</span>, <span style="font-family: monospace;">user_define_netcdf_grid</span>, <span style="font-family: monospace;">user_data_output_2d</span>, <span style="font-family: monospace;">user_data_output_3d</span>, and <span style="font-family: monospace;">user_3d_data_averaging</span>. These quantities can be calculated using the new <span style="font-family: monospace;">CASE</span>-Entry <span style="font-style: italic;">'after integration'</span> in the user-interface routine <span style="font-family: monospace;">user_actions</span>.<br><br>Optimization
+of the cloud droplet code is mainly done by re-sorting all particles
+after every timestep in a way that now all particles which belong to
+the same grid-box (k,j,i) are stored consecutively (wthout any strides)
+in memory.<br>
+      <br>
+Code adaptation for the IBM at the department of atmospheric sciences, Yonsei university (ibmy). Affected subroutines: <span style="font-family: monospace;">fft_xy</span>, <span style="font-family: monospace;">netcdf</span>, <br><br><span style="font-weight: bold;">Further new features:</span><br><ul><li>Use of particle tails now requires setting of the new package-parameter <span style="font-family: monospace;">use_particle_tails</span>. The new parameter skip_particles_for_tail allows only every <span style="font-family: monospace;">skip_particle_for_tail</span>'th parameter having a tail.</li><li>Initialization-parameter <span style="font-family: monospace;">e_min</span> can be used to set a lower limit for the subgrid-scale TKE (i.e. to guarantee a lower limit for the flow's Reynolds-number).</li><li>A
+conservation of the volume flow (through the complete xz- and
+yz-sections &nbsp;of the total domain) can be enforced by the new
+initialization-parameter <span style="font-family: monospace;">conserve_volume_flow</span>.</li><li>Data output can be skipped for a given time interval from simulation start (t=0) using new runtime-parameters <span style="font-family: monospace;">skip_time_dopr</span>, <span style="font-family: monospace;">skip_time_dosp</span>, <span style="font-family: monospace;">skip_time_do2d_xy</span>, <span style="font-family: monospace;">skip_time_do2d_xz</span>, <span style="font-family: monospace;">skip_time_do2d_yz</span>, and <span style="font-family: monospace;">skip_time_do3d</span>.<br>
+</li><li>By default, NetCDF output is now using 64-bit offset format
+(large file support) on most machines. The user can switch to the
+32-bit offset format with the new runtime-parameter <span style="font-family: monospace;">netcdf_64bit</span>. Units 111:113&nbsp; and 116 are opened for NetCDF output of time-averaged 2d-3d data.<br>
+        </li>
+        <li>Data
+logging routines are added (see file data_log.f90), which can be used
+for debugging purposes. Output is done on unit 20 (local file
+name/directory name DATA_LOG).</li>
+        <li>New routine <span style="font-family: monospace;">exchange_horiz_2d_int</span> for&nbsp; ghostpoint exchange of 2d-integer arrays. Routine <span style="font-family: monospace;">exchange_horiz_2d</span> is extended for non-cyclic boundary conditions in the non-parallel case.</li>
+        <li>Two different methods for calculating the mixing length and
+the dissipation can be used in the 1d-model. These are steered by the
+new initializing-parameters <span style="font-family: monospace;">dissipation_1d</span> and <span style="font-family: monospace;">mixing_length_1d</span>.<br>
+        </li>
+</ul></td><td style="vertical-align: top;">advec_particles, advec_s_pw,
+advec_s_up, advec_u_pw, advec_u_up, advec_v_pw, advec_v_up, advec_w_pw,
+advec_w_up, boundary_conds, buoyancy, check_open, check_parameters,
+close_file, coriolis, diffusion_e, diffusion_s, diffusion_u,
+diffusion_v, diffusion_w, diffusivities, disturb_field,
+disturb_heatflux, exchange_horiz_2d, exchange_horiz, flow_statistics,
+header, init_1d_model, init_3d_model, init_grid, init_particles,
+init_pegrid, modules, netcdf, package_parin, parin, poisfft,
+prandtl_fluxes, pres, production_e, prognostic_equations,
+read_3d_binary, read_var_list, run_control, time_integration,
+user_interface, write_3d_binary, write_var_list<br>
+      <br>
+      <span style="font-weight: bold;">new:</span><br>
+average_3d_data, data_log, sum_up_3d_data<br>
+      <br>
+      <span style="font-weight: bold;">renamed:<br>
+      </span>plot_dvrp -&gt; data_output_dvrp<br>
+plot_spectra -&gt; data_output_spectra<br>
+plot_ts -&gt; data_output_tseries<br>
+plot_1d -&gt; data_output_profiles<br>
+      <span style="font-weight: bold;"></span>plot_2d -&gt; data_output_2d<br>
+plot_3d -&gt; data_output_3d<br>
+</td></tr><tr><td style="vertical-align: top;">&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">C</td><td>In parallel mode, all PEs are opening the same copy of the NAMELIST-parameter file <span style="font-family: monospace;">PARIN</span>, i.e. from now on, the file attribute "<span style="font-family: monospace;">npe</span>" must be removed from the corresponding file connection statements in the <span style="font-weight: bold;">mrun</span> configuration file (.mrun.config).<br><br>A
+large number of parameter names and local filenames have been changed
+(see&nbsp;list below). Most of them are parameters concerning data
+output (do). The former denotations "plot" and "pl" have been changed
+to "data_output" and "do", respectively. In addition to these changes,
+the names of many internal PALM parameters and variables have also
+changed.<br><br>Restart runs now require setting of the initialization-parameter <span style="font-family: monospace;">initializing_actions</span> = <span style="font-style: italic;">'read_restart_data'</span>.<br>
+      <br>
+Concerning particles, the parameters <span style="font-family: monospace;">psl</span>, <span style="font-family: monospace;">psr</span>, <span style="font-family: monospace;">pdx</span>,
+etc., which are controlling the position of the particle source and the
+number of particles within this source, are now 1d-arrays. This allows
+to define different particle sources for different particle groups.<br>
+      <br>
+The number of particle groups has to be set by the user (no automatic calculation from the value of parameter <span style="font-family: monospace;">density_ratio</span> any more)<span style="font-style: italic;"></span>. Variable <span style="font-family: monospace;">idum</span> in type <span style="font-family: monospace;">particle_type</span> has been renamed <span style="font-family: monospace;">tail_id</span>.<br><br>Output for units 15 and 17 flushed in <span style="font-family: monospace;">init_1d_model</span>.<br><br>List of changed parameter names:<br><table style="text-align: left; width: 559px; height: 831px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="font-weight: bold;" align="undefined" valign="undefined">Old name</td><td align="undefined" valign="undefined"><span style="font-weight: bold;">New name</span></td><td align="undefined" valign="undefined"><span style="font-weight: bold;">Comments</span></td></tr><tr><td align="undefined" valign="undefined">average_period_pl1d</td><td align="undefined" valign="undefined">averaging_interval_pr</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td style="vertical-align: top;">average_period_pr1d</td><td style="vertical-align: top;">---</td><td style="vertical-align: top;">averaging of printed profiles is not possible any more</td></tr><tr><td align="undefined" valign="undefined">average_period_sp</td><td align="undefined" valign="undefined">averaging_interval_sp</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">dt_average</td><td align="undefined" valign="undefined">dt_averaging_input_pr</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">dt_pl1d</td><td align="undefined" valign="undefined">dt_dopr</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">dt_plsp</td><td align="undefined" valign="undefined">dt_dosp</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td>dt_plts</td><td>dt_dots</td><td></td></tr><tr><td align="undefined" valign="undefined">dt_pr1d</td><td align="undefined" valign="undefined">dt_dopr_listing</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">dt_pl2d_xy</td><td align="undefined" valign="undefined">dt_do2d_xy</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">dt_pl2d_xz</td><td align="undefined" valign="undefined">dt_do2d_xz</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">dt_pl2d_yz</td><td align="undefined" valign="undefined">dt_do2d_yz</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">ebene_xy</td><td align="undefined" valign="undefined">section_xy</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">ebene_xz</td><td align="undefined" valign="undefined">section_xz</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">ebene_yz</td><td align="undefined" valign="undefined">section_yz</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">nz_plot3d</td><td align="undefined" valign="undefined">nz_do3d</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">plts</td><td align="undefined" valign="undefined">data_output_ts</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">pl1d</td><td align="undefined" valign="undefined">data_output_pr</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td style="vertical-align: top;">pl2d</td><td style="vertical-align: top;">data_output</td><td style="vertical-align: top;">old parameters pl2d and pl3d are joined to new parameter data_output</td></tr><tr><td align="undefined" valign="undefined">pl3d</td><td align="undefined" valign="undefined">data_output</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">pl2d_at_begin</td><td align="undefined" valign="undefined">do2d_at_begin</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">pl3d_at_begin</td><td align="undefined" valign="undefined">do3d_at_begin</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">pl3d_compress</td><td align="undefined" valign="undefined">do3d_compress</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">pl3d_precision</td><td align="undefined" valign="undefined">do3d_comp_prec</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td>pl_spectra</td><td>data_output_sp</td><td></td></tr><tr><td align="undefined" valign="undefined">read_fields_from_prior_run</td><td align="undefined" valign="undefined">read_restart_data</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">write_plot2d_on_each_pe</td><td align="undefined" valign="undefined">data_output_2d_on_each_pe</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">z_max_pl1d</td><td align="undefined" valign="undefined">z_max_do1d</td><td align="undefined" valign="undefined"><br>
+</td></tr><tr><td align="undefined" valign="undefined">z_max_pl2d</td><td align="undefined" valign="undefined">z_max_do2d</td><td align="undefined" valign="undefined"><br>
+</td></tr></tbody></table></td><td style="vertical-align: top;">advec_particles,
+advec_s_bc, check_parameters, check_open, close_file,
+data_output_dvrp,&nbsp; data_output_profiles, data_output_tseries,
+data_output_2d, data_output_3d, flow_statistics, header, init_1d_model,
+init_3d_model, init_dvrp, init_particles, init_pegrid, init_slope,
+modules, netcdf, package_parin, palm, parin, print_1d, read_var_list,
+run_control, time_integration, timestep, write_compressed,
+write_var_list<br>
+</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">E</td><td>Error in the particle release (defaults of <span style="font-family: monospace;">psl</span>, <span style="font-family: monospace;">psr</span>, <span style="font-family: monospace;">psn</span>, <span style="font-family: monospace;">pss</span>) at the PE boundary has been fixed.<br>
+      <br>
+Error removed getting the variable ids for <span style="font-family: monospace;">_ext</span> for profiles and time series.<br><br>NetCDF calls in <span style="font-family: monospace;">data_output_tseries</span> only if NetCDF output is switched on.<br><br>Output of the initial geostrophic wind profile corrected.<br><br>Maximum possibel timestep for Runge-Kutta-schemes reduced, error concerning initialization of&nbsp; <span style="font-family: monospace;">l_black</span> removed (both in <span style="font-family: monospace;">init_1d_model</span>).<br>
+</td><td style="vertical-align: top;">advec_particles, data_output_tseries, header, init_particles, init_1d_model, netcdf<br>
+</td></tr><tr><td align="left" valign="top">26/04/06</td><td align="left" valign="top">SR</td><td align="left" valign="top">3.0a</td><td align="left" valign="top">N</td><td align="left" valign="top">OpenMP parallelization for the cache-optimized PALM code.<br><br>OpenMP
+directives have been added where necessary. Still further tuning will
+be necessary to get optimum performance. Other parts of the code than
+the cache-optimized code still need to be (OpenMP-) parallelized. <br><br>So far, threads are activated by setting the <span style="font-weight: bold;">mrun</span>-options <span style="font-family: monospace;">-T</span> <span style="font-style: italic;">&lt;number_of_threads&gt;</span> and <span style="font-family: monospace;">-O</span>, i.e. when the Option <span style="font-family: monospace;">-O</span> is given, the <span style="font-family: monospace;">-T</span> argument is interpreted as the number of threads to be used. When <span style="font-family: monospace;">-O</span> is given, the number of MPI tasks per node is automatically set to <span style="font-style: italic;">1</span>.<br><br>Beside
+the additional compiler directives, the main code change required by
+the OpenMP parallelization is that global sums are now calculated by
+first calculating local sums on each thread. As the next step, local
+sums are calculated from these thread sums for each MPI task before the
+global sum is computed via MPI_ALLREDUCE.&nbsp; For storing the thread
+sums, arrays sums_l and sums_l_l now have three dimensions where the
+number of elements of the third dimension is equal to the number of
+OpenMP threads.</td><td align="left" valign="top">buoyancy,
+cpu_statistics, diffusivities, flow_statistics, header, init_pegrid,
+init_3d_model, modules, prandtl_fluxes, pres, production_e</td></tr><tr><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">ML</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">C</td><td align="left" valign="top">Provisional
+correction for Piacsek &amp; Williams advection scheme: keep u and v
+zero one layer below the topography (in case of set_1d-model_profiles).</td><td align="left" valign="top">init_3d_model</td></tr><tr><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">SR/ML</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">E</td><td align="left" valign="top">In <span style="font-family: monospace;">flow_statistics.f90</span> nzb_s_inner(j,i) replaced by nzb in determination of z_i.<br><br>Errors removed in the computation of the diabatic mixing length (<span style="font-family: monospace;">init_1d_model.f90</span>).<br><br>Error removed in extend mode when checking whether the selected cross sections match those in the already existing NetCDF file (<span style="font-family: monospace;">netcdf.f90</span>).</td><td align="left" valign="top">flow_statistics, init_1d_model, netcdf</td></tr><tr><td align="left" valign="top">02/06/06</td><td align="left" valign="top">SR</td><td align="left" valign="top">3.0b</td><td align="left" valign="top">N</td><td align="left" valign="top">This version is adapted to the Sun Fire X4600 system at TIT (to be used by setting the <span style="font-weight: bold;">mrun</span> option <span style="font-family: monospace;">-h lctit</span>).</td><td align="left" valign="top">cpu_log, init_1d_model, local_tremain, loca&ouml;_tremain_ini, run_control</td></tr><tr><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">C</td><td align="left" valign="top">NetCDF&nbsp;2d-
+and 3d-datasets now contain the exact coordinates of the variables
+along x and y with respect to the positions where they are defined on
+the staggered grid.<br><br>NetCDF datasets of cross sections (e.g. <span style="font-family: monospace;">DATA_2D_XY_NETCDF</span>) are only opened if the respective cross sections are really requested by the settings of parameter <span style="font-family: monospace;">data_output</span>.</td><td align="left" valign="top">check_parameters, data_output_2d, data_output_3d, modules, netcdf, user_interface</td></tr><tr><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">E</td><td align="left" valign="top">p is assigned to <span style="font-family: monospace;">to_be_resorted</span> instead of w</td><td align="left" valign="top">data_output_2d</td></tr><tr><td align="left" valign="top">04/08/06</td><td align="left" valign="top">SR</td><td align="left" valign="top">3.1</td><td align="left" valign="top">N</td><td align="left" valign="top">Subgrid
+scale velocities can (optionally) be included for calculating the
+particle advection, using the method of Weil et al. (2004, JAS, 61,
+2877-2887). This method is switched on by the new particle package
+parameter <span style="font-family: monospace;">use_sgs_for_particles</span>. This also forces the Euler/upstream method to be used for time advancement of the TKE (see new parameter <span style="font-family: monospace;">use_upstream_for_tke</span>). The minimum timestep during the sub-timesteps is controlled by parameter <span style="font-family: monospace;">dt_min_part</span>. The data type <span style="font-family: monospace;">particle_type</span> has additional new attributes <span style="font-family: monospace;">e_m</span>, <span style="font-family: monospace;">dt_sum</span>, and <span style="font-family: monospace;">speed_x/y/z_sgs</span>.<br><br>Other new particle features: output of particle quantities as timeseries in NetCDF format (on local file <span style="font-family: monospace;">DATA_1D_PTS_NETCDF</span>). The output time interval is controlled by parameter <span style="font-family: monospace;">dt_dopts</span>. Particle advection can be switched off after some time using parameter <span style="font-family: monospace;">end_time_prel</span>. More than one particle per point can be started with parameter <span style="font-family: monospace;">particles_per_point</span>.<br><br>Additional parameter in function <span style="font-family: monospace;">random_gauss</span> which limits the range of the created random numbers to five times the standard deviation (=1). Seeds <span style="font-family: monospace;">iran</span> and <span style="font-family: monospace;">iran_part</span> are stored for restart runs.</td><td align="left" valign="top">advec_particles,
+check_open, check_parameters, close_file, diffusion_e,
+disturb_heatflux, header, init_3d_model, init_particles, modules,
+netcdf, package_parin, parin, prognostic_equations, random_gauss,
+read_3d_binary, read_var_list, time_integration, write_3d_binary,
+write_var_list<br><br><span style="font-weight: bold;">new:</span><br>data_output_ptseries</td></tr><tr><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">C</td><td align="left" valign="top">Call of subroutine <span style="font-family: monospace;">header</span> is moved after call of subroutine <span style="font-family: monospace;">init_3d_model</span>. Generation of <span style="font-family: monospace;">run_description_header</span> is moved from routines <span style="font-family: monospace;">palm</span> and <span style="font-family: monospace;">header</span> to <span style="font-family: monospace;">check_parameters</span>. Determination of the number of particle groups is moved from <span style="font-family: monospace;">header</span> to <span style="font-family: monospace;">init_particles</span>.<br><br><span style="font-family: monospace;">izuf</span> renamed <span style="font-family: monospace;">iran</span>.</td><td align="left" valign="top">check_parameters, disturb_field, disturb_heatflux, header, init_particles, modules, palm</td></tr><tr><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">&nbsp;</td><td align="left" valign="top">E</td><td align="left" valign="top">Variables
+do2d_unit and do3d_unit now defined as 2d-arrays. Before, in some
+cases, the units of variables in the 2d- and 3d-NetCDF-files have been
+wrong.<br><br>In routine <span style="font-family: monospace;">poisfft</span> default setting of the thread number tn in case of not using OpenMP.<br><br>Error removed in the non-parallel part of routine <span style="font-family: monospace;">flow_statistics</span> (number of arguments of array <span style="font-family: monospace;">sums_l</span>).<br><br>Error removed which appeared if the user had decreased the value of <span style="font-family: monospace;">dt_dopr</span> within a job chain and if simulataneous time averaging of profiles was switched on.</td><td align="left" valign="top">check_parameters, data_output_profiles, flow_statistics, modules, netcdf, poisfft</td></tr><tr><td style="vertical-align: top;">22/08/06</td><td style="vertical-align: top;">SR</td><td style="vertical-align: top;">3.1a</td><td style="vertical-align: top;">N</td><td style="vertical-align: top;">In case of more than one particle group, seperate output of timeseries for each of the groups.<br><br>New initial parameter <span style="font-family: monospace;">dz_max</span>, which limits the vertical gridspacing in case of a vertically stretched grid.</td><td style="vertical-align: top;">data_output_ptseries, header, init_grid, modules, netcdf, parin, read_var_list, write_var_list</td></tr><tr><td style="vertical-align: top;">&nbsp;</td><td style="vertical-align: top;">&nbsp;</td><td style="vertical-align: top;">&nbsp;</td><td style="vertical-align: top;">C</td><td style="vertical-align: top;">Disturbances are imposed only for the last Runge-Kutta-substep. <br><span style="font-weight: bold;">Attention:</span> <br>
+
+The content of the testresult-file (run control output) has changed
+due to this modification.<br><br>Output of xz and yz cross sections now up to gridpoint nzt+1.<br><br>Default settings of particle start positions changed.</td><td style="vertical-align: top;">check_open, close_file, data_output_2d, init_particles, netcdf, time_integration</td></tr><tr><td style="vertical-align: top;">&nbsp;</td><td style="vertical-align: top;">&nbsp;</td><td style="vertical-align: top;">&nbsp;</td><td style="vertical-align: top;">E</td><td style="vertical-align: top;">Initialisation of all tendency arrays (t.._m) needed for the Runge-Kutta schemes.<br><br>Bugfix in index array initialization for line- or point-like topography structures.<br><br>Bugfix: yv coordinates are now used for yz cross sections, where neccessary.</td><td style="vertical-align: top;">init_3d_model, init_grid, netcdf</td></tr><tr><td style="vertical-align: top;">12/02/07</td><td style="vertical-align: top;">SR</td><td style="vertical-align: top;">3.1b</td><td style="vertical-align: top;">&nbsp;N</td><td style="vertical-align: top;"><span style="font-weight: bold;">Attention:</span><br>This is the last revision before switching to the subversion revison control system!<br><br>Informative output to the job protocoll in case of restarts.</td><td style="vertical-align: top;">check_for_restart</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">C</td><td style="vertical-align: top;">Values of environment variables are now read from local file <span style="font-family: monospace;">ENVPAR</span> instead of getting them by a system call.<br><br>For interpolation in <span style="font-family: monospace;">advec_particles</span>, allways level k is used.</td><td style="vertical-align: top;">advec_particles, local_tremain_ini, parin</td></tr><tr><td></td><td></td><td></td><td style="vertical-align: top;">E</td><td style="vertical-align: top;">Several bugfixes in <span style="font-family: monospace;">advec_particles</span>: new particles are released only if <span style="font-family: monospace;">end_time_prel</span> &gt; <span style="font-family: monospace;">simulated_time</span>,&nbsp;transfer
+of particles when x &lt; -0.5*dx (0.0 before), etc., index i,j used
+instead of cartesian (x,y) coordinate to check for transfer because
+this failed under very rare conditions, calculation of number of
+particles with same radius as the current particle (cloud droplet code).<br><br>Allocation of <span style="font-family: monospace;">tail_mask</span> and <span style="font-family: monospace;">new_tail_id</span> in case of restart-runs. "__" added in a cpp-directive. (both <span style="font-family: monospace;">init_particles</span>)</td><td style="vertical-align: top;">advec_particles, init_particles</td></tr>
+
+  
+  </tbody>
+</table>
+
+&nbsp;<b><blink>Attention:</blink></b> If<tt> make </tt>is not used
+for
+compiling,
+<b>all routines</b> have to be re-compiled after every change
+to <b>modules.f90!</b>
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<h2><a name="Kapitel2.0"></a>2.0&nbsp; How to change the model source
+code</h2>
+
+&Auml;nderungen, Erweiterungen oder Fehlerkorrekturen am Modellcode
+(gemeint
+sind alle Modellteile, die nicht zur benutzereigenen Software
+geh&ouml;ren)
+erfordern vom jeweiligen Benutzer Gruppenzugeh&ouml;rigkeit zur Gruppe
+<tt>"palm"</tt>.
+Zu dieser Gruppe geh&ouml;ren alle Benutzer, die aktiv an der
+Modellentwicklung
+mitwirken (im weiteren "Modellarbeitsgruppe" genannt).
+<p>Die einzelnen Quelltextdateien des Modells werden mit RCS (Revision
+Control System) verwaltet. Grundlegende Kenntnisse &uuml;ber dieses
+System
+werden im weiteren vorausgesetzt.
+</p>
+
+<p>&Auml;nderungen am Modellcode erfordern die Durchf&uuml;hrung
+bestimmter
+Aktionen in einer festgelegten Reihenfolge, die nun beschrieben werden
+sollen.
+</p>
+
+<ol>
+
+  <li>Konzeptplanung.</li>
+
+  <li>Diskussion der geplanten &Auml;nderungen in der
+Modellarbeitsgruppe.</li>
+
+  <li>Auschecken der ben&ouml;tigten Quelltextdateien,
+Durchf&uuml;hrung der
+&Auml;nderungen und Test des Modells. Die Modul-Datei <tt>modules.f90</tt>
+sollte nur dann ausgecheckt werden, wenn dort aufgef&uuml;hrte
+Variablen
+ver&auml;ndert werden. Neu geschaffene Variablen sollten w&auml;hrend
+der
+Testphase in ein ebenfalls tempor&auml;r neu zu schaffendes Modul
+geschrieben
+werden, das von den jeweiligen Programmteilen benutzt werden muss
+(Einf&uuml;gen
+entsprechender USE-Anweisungen). Die in den einzelnen Dateien
+durchgef&uuml;hrten
+Arbeiten m&uuml;ssen in den Kopfzeilen (unter "Aktuelle Aenderungen")
+der
+Dateien vermerkt werden. Dies tut man am besten noch <b>bevor</b> man
+die
+eigentlichen &Auml;nderungen durchf&uuml;hrt (sonst droht das
+Vergessen...).</li>
+
+  <li>Zum Abschlu&szlig; der Tests sollte mit dem Modell eine
+Kontrollrechnung
+durchgef&uuml;hrt und die Ergebnisse mit denen des sogenannten
+Standardlaufes
+verglichen werden. Diese Rechnung ist mit der <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">Konfigurationsdatei</a>
+und der <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">Parameterdatei</a>
+durchzuf&uuml;hren, die auch zum Testen der Modellinstallation
+verwendet
+werden (s. <a href="Anwendung/Kapitel_5.0.html">Kapitel 5.0</a> der
+Anwenderdokumentation).
+Die Ergebnisdatei mit dem lokalen Namen <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM-1/Dokumentationen/Anwendung/Kapitel_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
+ist dann mit der <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_rc">Beispiel-Ergebnisdatei</a>
+zu vergleichen (Hinweis: Kopien der Konfigurationsdatei, Parameterdatei
+und Beispiel-Ergebnisdatei erh&auml;lt man durch anklicken der
+entsprechenden
+Links mit der linken Maustaste bei gleichzeitig gedr&uuml;ckter
+&lt;SHIFT&gt;-Taste).
+Werden Abweichungen zwischen den beiden Ergebnisdateien festgestellt,
+so
+ist unbedingt eine Diskussion in der Modellarbeitsgruppe notwendig.</li>
+
+  <li>Nach Durchf&uuml;hrung der Tests m&uuml;ssen bei Bedarf die
+vorl&auml;ufig
+im tempor&auml;ren Modul eingetragenen Variablen in die eigentlichen
+Module
+des Modells &uuml;bertragen werden. Dazu ist die Modul-Datei <tt>modules.f90</tt>
+auszuchecken. Nach Eintrag der Variablen sollte das Modell noch einmal
+testweise &uuml;bersetzt werden, um Sytaxfehler auszuschlie&szlig;en
+(evtl.
+auch noch einmal einen Probelauf starten). Die Verwendung des
+tempor&auml;ren
+Moduls ist aus allen entsprechenden Programmteilen zu entfernen.</li>
+
+  <li>Vergabe einer neuen Versionsnummer (Variable <tt>version</tt> im
+Modul <tt>steuer</tt>),
+Bsp.: 2.3c. Kleinere &Auml;nderungen werden durch angeh&auml;ngten
+kleinen
+Buchstaben kenntlich gemacht, gr&ouml;&szlig;ere &Auml;nderungen durch
+die Zahl hinter dem Punkt. Eine Inkrementierung der Zahl vor dem Punkt
+geschieht nur bei ganz grunds&auml;tzlichen Revisionen des Modells, die
+weite Teile des Modellcodes betreffen.</li>
+
+  <li>Nun k&ouml;nnen die ausgecheckten Dateien wieder eingecheckt
+werden.
+Vor
+dem Einchecken sind in den Dateien die Vermerke unter "Aktuelle
+Aenderungen"
+zu entfernen und beim check-in - Kommando als Log-Text anzugeben. Sie
+erscheinen
+dann in der jeweiligen Datei unter "Fruehere Aenderungen" zusammen mit
+der vom RCS-System vergebenen Versionsnummer (daf&uuml;r sorgt die
+$Log:
+... $ - Zeile, die in jeder Quelltextdatei steht).</li>
+
+  <li>Eine Zusammenfassung der durchgef&uuml;hrten Arbeiten ist im <a href="#Kapitel1.0">Kapitel
+1.0</a> einzutragen.</li>
+
+  <li>Die Modellarbeitsgruppe ist &uuml;ber den Abschlu&szlig; der
+durchgef&uuml;hrten
+Arbeiten zu informieren.</li>
+
+</ol>
+
+<h2>
+<a name="Kapitel3.0"></a>3.0&nbsp; Description of selected parts of the
+model source code</h2>
+
+<b>This chapter is still under construction (Feb. 04).</b>
+<p>Dieser Abschnitt verweist auf vorhandene Beschreibungen der genauen
+Funktionsweise einzelner, spezieller Modellteile. Dazu geh&ouml;rt z.B.
+die Beschreibung bestimmter numerischer Verfahren (auch ihr
+theoretischer
+Hintergrund), die Erkl&auml;rung besonderer Prinzipien bei der
+Parallelisierung
+oder Erl&auml;uterungen zur Vorgehensweise bei der L&ouml;sung
+bestimmter
+Aufgaben (z.B. der Berechnung horizontal gemittelter
+Gr&ouml;&szlig;en).
+<br>
+
+Die Beschreibungen liegen in jeweils getrennten Dokumenten, in der
+Regel als TeX- und/oder Postscript-Datei vor und sind &uuml;ber die
+folgenden
+Links zug&auml;nglich.
+<br>
+
+&nbsp;
+</p>
+
+<ul>
+
+  <li> <a name="UPS"></a>upstream-spline advection scheme ( <a href="Upstream_Spline/ups.ps">.ps</a>
+)</li>
+
+  <li> <a name="Cloud_physics"></a>cloud physics module ( <a href="Cloud_physics/wolken.pdf">.pdf</a>
+)</li>
+
+  <li> <a name="Bitkompression"></a>Datenkompression mit dem Verfahren
+der <a href="Bitkompression/kompression.html">Bitverschiebung</a></li>
+
+  <li> <a name="Runge-kutta"></a>Runge-Kutta time integration scheme (
+    <a href="numerik.heiko/zeitschrittverfahren.pdf">.pdf</a>
+)</li>
+
+</ul>
+
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+<br>
+
+&nbsp;
+</body></html>
