Index: palm/trunk/DOC/app/chapter_1.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_1.0.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_1.0.html	(revision 62)
@@ -1,73 +1,61 @@
 <!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
+<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 style="direction: ltr;" lang="de-DE"><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>
+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
+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
+<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
+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
+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
+<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;">
+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
+<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>).
+(<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
@@ -75,13 +63,7 @@
 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>
+</p><hr><font color="#000080"><font color="#000080"><br>
+<a href="index.html"><font color="#000080"><img name="Grafik1" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_2.0.html"><font color="#000080"><img name="Grafik2" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font><br><br>
+<span style="font-style: italic;">Last change:</span>
+$Id$<br>
+<br></body></html>
Index: palm/trunk/DOC/app/chapter_2.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_2.0.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_2.0.html	(revision 62)
@@ -1,24 +1,15 @@
 <!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
+<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 style="direction: ltr;" lang="en-US"><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
+</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
@@ -28,10 +19,13 @@
 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
+<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,
+quantities in total &ndash; u,v,w, liquid water potential
+temperature
+<font face="Thorndale, serif">&Theta;</font><sub>l
+</sub>(BETTS,
 1973), total water content q and subgrid-scale turbulent kinetic energy
 e. The
@@ -45,5 +39,5 @@
 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
+processes (M&Uuml;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
@@ -58,5 +52,6 @@
 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
+<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
@@ -66,10 +61,12 @@
 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
+<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
+<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
@@ -90,10 +87,11 @@
 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
+Prandtl-layer&ndash;quantities 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
+<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
@@ -109,9 +107,11 @@
 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
+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
+<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
@@ -126,23 +126,16 @@
 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
+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
+<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>
+<hr><font color="#000080"><font color="#000080"><br><a href="chapter_1.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_3.0.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a><br>
+</font></font><br><p style="line-height: 100%;"><span style="font-style: italic;">Last
+change: </span>$Id$<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 61)
+++ palm/trunk/DOC/app/chapter_3.0.html	(revision 62)
@@ -1,53 +1,32 @@
 <!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
+<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 style="direction: 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,
+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
+<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
+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
+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
+</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
+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
@@ -57,19 +36,19 @@
 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
+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
+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
+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
+<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
+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
@@ -78,11 +57,10 @@
 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
+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
+<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
+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
@@ -91,33 +69,24 @@
 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
+<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
+<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
+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>
+<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>
+$Id$<br>
+</p></body></html>
Index: palm/trunk/DOC/app/chapter_3.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.1.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.1.html	(revision 62)
@@ -1,19 +1,11 @@
 <!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>
+<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 style="direction: 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
@@ -23,8 +15,8 @@
 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
+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
+<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
@@ -32,42 +24,32 @@
 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
+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
+<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
+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
+(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
+lie in the temporary working directory created by <b>mrun.</b>
+The
+&ldquo;local&rdquo; 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
@@ -77,16 +59,20 @@
 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.
+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
+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>
+of further functions &ndash; 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
@@ -94,41 +80,38 @@
 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
+<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
+<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
+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">
+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
+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>
+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>
+<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>$Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.2.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.2.html	(revision 62)
@@ -1,101 +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.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
+<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 style="direction: 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
+<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
+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
+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>
+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
+<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
+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>)
+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>
+<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">)
+so-called environment variables. Such lines begin with a
+&ldquo;%&rdquo;-
+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
+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
+</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
@@ -104,117 +74,95 @@
 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
+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">.
+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
+replaced </font>by colons (&ldquo;:&rdquo;). <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
+other will be interpreted as a colon). Thus in the example above </font><tt><font face="Thorndale, serif">fopts
+has the value </font></tt>&ldquo;<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
+-qnoescape</i></font><tt><i><font face="Thorndale, serif"><font color="#000000">&rdquo;</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">
+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
+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
+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">.
+variable lines after the value of variables.</font></font><font color="#000000">
+In the example above the entry &ldquo;</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">&rdquo;
+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">)
+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">
+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
+</p><p style="line-height: 100%;">After the value
+assignment for the
+variables the so-called error commands follow which have to begin with
+&ldquo;<tt><font style="font-size: 11pt;" size="2">EC:</font></tt>&rdquo;
+in the first column (comment lines begin with &ldquo;<tt>#</tt>&rdquo;).
+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
+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
+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>.
+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
+execution of <b>mrun</b> the &ldquo;<tt>$</tt>&rdquo;
+- prefix
+must be protected by a &ldquo;\&rdquo; 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
+<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
+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
+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
@@ -222,16 +170,18 @@
 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
+<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
+<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
+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
@@ -243,15 +193,13 @@
 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
+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
+<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
@@ -260,22 +208,18 @@
 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>.
+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
+<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
+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
@@ -283,46 +227,41 @@
 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
+<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">
+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>
+</p><ul> <p style="line-height: 100%;">File
+name (inclusive path) = &ldquo;value of
+the 4th column&rdquo; + &ldquo;value of the option <tt><font size="2">-d</font></tt>&rdquo;
++ &ldquo;value of the 5th column&rdquo;.</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
+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
+<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
+<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>
+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
+<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>),
+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>)
@@ -330,8 +269,6 @@
 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>.
+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
@@ -339,60 +276,42 @@
 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
+<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
+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
+<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun - K parallel -X &hellip; -t &hellip; -m &hellip;</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>
+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>
+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">%
+<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>
+<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>
+<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>
+$Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.3.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.3.html	(revision 62)
@@ -1,22 +1,15 @@
 <!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
+<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 style="direction: 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
@@ -35,9 +28,9 @@
 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
+<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>
+<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
@@ -49,11 +42,11 @@
 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>,
+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
+</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
@@ -75,45 +68,32 @@
 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
+<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
+<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
+<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>
+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>
+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
+</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
@@ -122,7 +102,7 @@
 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
+<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
@@ -130,14 +110,16 @@
 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
+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,
+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
+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
@@ -148,20 +130,21 @@
 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
+<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>).
+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>
+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
+&ldquo;<i>read_restart_data&rdquo;</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
@@ -173,53 +156,50 @@
 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>.
+must have the value &ldquo;<i>read_restart_data&rdquo;</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
+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
+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>
+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
+<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
+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
+</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>.
+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">&ldquo;f&rdquo;</font></tt>.
 </p>
-<p style="line-height: 100%;">For example, for the initial run
+<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
+<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>
@@ -230,74 +210,48 @@
 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
+<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>)
+restart job does not overwrite this permanent file (<tt>&hellip;/<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
+a permanent file with the name <tt><font style="font-size: 10pt;" size="2">&hellip;/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>
+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">&hellip;/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">&hellip;/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">
+<tt><font style="font-size: 10pt;" size="2">&hellip;/abcde_d3d</font></tt><font style="font-size: 11pt;" size="2">,</font>
+the first restart run uses this file and creates <tt>&hellip;/<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">&hellip;/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
+<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
+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>
+<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>
+$Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_3.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.4.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.4.html	(revision 62)
@@ -1,33 +1,9 @@
 <!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
+<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
+<p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The
+model works
 with a set of files, which are all located in the temporary working
 directory and which are either expected at the beginning of the run
@@ -35,18 +11,16 @@
 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
+<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.
+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
+</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
@@ -57,14 +31,9 @@
 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
+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
@@ -73,5 +42,6 @@
 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
+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
@@ -82,6 +52,8 @@
 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
+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
@@ -90,349 +62,42 @@
 <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
+</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,
+</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
+<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
+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
+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
+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>),
@@ -441,30 +106,10 @@
 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,
+chain and/or if a job chain is continued.&nbsp; </p> <p>Knowledge
+of the file structure is usually not necessary,
 because the file is produced and also read again by the model, but it
 can be useful for error determination in case of read errors .
 Therefore the file structure is described in the following.&nbsp; </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>The first record of this file contains a version number (ten
+<p>The first record of this file contains a version number (ten
 character string) of the subroutine, which, which output the data that
 follows (write_var_list.f90). This number has to
@@ -472,16 +117,6 @@
 (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
+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
@@ -493,45 +128,16 @@
 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
+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
+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
@@ -541,16 +147,6 @@
 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
+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
@@ -561,126 +157,24 @@
 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>.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
+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
+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
+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
@@ -690,94 +184,19 @@
 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
+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
+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
+</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
@@ -787,30 +206,10 @@
 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
+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
+</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.
@@ -821,395 +220,42 @@
 it can be achieved that this information is also written at the
 beginning of the file RUN_CONTROL at restart runs.&nbsp; </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>The individual columns of the 1D - time step control output
+<p>The individual columns of the 1D - time step control output
 have the following meaning (listed by the respective heading of the
 appropriate
-column in the file):&nbsp; <br>
-
-
-
-
-
-      </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <table style="text-align: left; width: 100%;" cellpadding="2">
-
-
-
-
-
-        <tbody>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">ITER.</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Number of time steps
-accomplished so far</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">HH:MM:SS</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Time (in hours: minutes:
-seconds)</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">DT</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Time step (in s)</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">UMAX</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Maximum absolute wind
+column in the file):&nbsp; <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2">
+<tbody> <tr> <td style="vertical-align: top;">ITER.</td>
+<td style="vertical-align: top;">Number of time steps
+accomplished so far</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (in hours: minutes:
+seconds)</td> </tr> <tr> <td style="vertical-align: top;">DT</td> <td style="vertical-align: top;">Time step (in s)</td> </tr>
+<tr> <td style="vertical-align: top;">UMAX</td>
+<td style="vertical-align: top;">Maximum absolute wind
 velocity
-(u-component) (in m/s)</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">VMAX</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Maximum absolute wind
+(u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind
 velocity
-(v-component) (in m/s)</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">U *</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">ALPHA</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Angle of the wind vector
+(v-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">U *</td> <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td> </tr>
+<tr> <td style="vertical-align: top;">ALPHA</td>
+<td style="vertical-align: top;">Angle of the wind vector
 (to the x-axis) at the top of the
 Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: middle;">ENERG.</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Kinetic energy of the
+</tr> <tr> <td style="vertical-align: middle;">ENERG.</td>
+<td style="vertical-align: top;">Kinetic energy of the
 1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
-averaged over all grid points</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-        
-        
-        
-        
-        
-        </tbody>
-      
-      
-      
-      
-      
-      </table>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>&nbsp;
+averaged over all grid points</td> </tr> </tbody> </table>
+<p>&nbsp;
 The individual columns of the 3D - time step control output
 have the following meaning (listed by the respective heading of the
 appropriate
-column in the file):<br>
-
-
-
-
-
-      </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <table style="text-align: left; width: 100%;" cellpadding="2">
-
-
-
-
-
-        <tbody>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">RUN</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Serial-number of the job
+column in the file):<br> </p> <table style="text-align: left; width: 100%;" cellpadding="2">
+<tbody> <tr> <td style="vertical-align: top;">RUN</td>
+<td style="vertical-align: top;">Serial-number of the job
 in the job chain. The initial
 run has the number 0, restart runs accordingly have larger numbers.</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">ITER.</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Number of time steps
+</tr> <tr> <td style="vertical-align: top;">ITER.</td>
+<td style="vertical-align: top;">Number of time steps
 accomplished since starting time t=0 of
-the initial run.</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">HH:MM:SS</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Time (<font color="#000000">in
-            </font>hours: minutes:
+the initial run.</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (<font color="#000000">in
+</font>hours: minutes:
 seconds) since starting time t=0 of the
-initial run.</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">DT (E)</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
+initial run.</td> </tr> <tr> <td style="vertical-align: top;">DT (E)</td> <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
 following character indicates whether the
 time
@@ -1219,518 +265,90 @@
 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
+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
+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
+</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
+</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
+</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
+</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
+</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
+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,
+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
+</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
+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
+u-component of the wind velocity (sequence: k, j, i).</td> </tr>
+<tr> <td style="vertical-align: top;">VMAX (KJI)</td>
+<td style="vertical-align: top;">Indices of the grid point
 with the maximum absolute
-v-component of the wind velocity (sequence: k, j, i).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">WMAX (KJI)</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Indices of the grid point
+v-component of the wind velocity (sequence: k, j, i).</td> </tr>
+<tr> <td style="vertical-align: top;">WMAX (KJI)</td>
+<td style="vertical-align: top;">Indices of the grid point
 with the maximum absolute
-w-component of the wind velocity (sequence: k, j, i).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">ADVECX</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
+w-component of the wind velocity (sequence: k, j, i).</td> </tr>
+<tr> <td style="vertical-align: top;">ADVECX</td>
+<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
 coordinate system has been moved in
 x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;">ADVECY</td>
-
-
-
-
-
-            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
+</tr> <tr> <td style="vertical-align: top;">ADVECY</td>
+<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
 coordinate system has been moved in
 y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-        
-        
-        
-        
-        
-        </tbody>
-      
-      
-      
-      
-      
-      </table>
-
-
-
-
-
-      </td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">16<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">O<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">This file contains horizontally
+</tr> </tbody> </table> </td> </tr> <tr>
+<td style="vertical-align: top; text-align: center;">16<br>
+</td> <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL </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
@@ -1745,9 +363,4 @@
 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
@@ -1757,779 +370,89 @@
 computer, date, time of the beginning of the run, name of the
 subdomain, output time, kind of averaging). On the u-v-level the
-following columns are written: <br>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <table style="text-align: left; width: 100%;" cellpadding="2">
-
-
-
-
-
-        <tbody>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">k<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Vertical
-grid point index.</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">zu<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Height
+following columns are written: <br> <table style="text-align: left; width: 100%;" cellpadding="2">
+<tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br>
+</td> <td style="text-align: left; vertical-align: middle;">Vertical
+grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br>
+</td> <td style="text-align: left; vertical-align: middle;">Height
 of the grid point
 level (<font color="#000000">in </font>m).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">u<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">u-component
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br>
+</td> <td style="text-align: left; vertical-align: middle;">u-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">du<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Deviation
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">du<br>
+</td> <td style="text-align: left; vertical-align: middle;">Deviation
 of the
 u-component from the initial profile at the
-time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">v<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">v-component
+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
+</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
+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
+</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
+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
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br>
+</td> <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Kh<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Turbulent
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br>
+</td> <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">l<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Mixing
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br>
+</td> <td style="text-align: left; vertical-align: middle;">Mixing
 length (<font color="#000000">in </font>m).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: top;"><br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="vertical-align: top;"><br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-        
-        
-        
-        
-        
-        </tbody>
-      
-      
-      
-      
-      
-      </table>
-
-
-
-
-
-On the w-level the following columns are written:<br>
-
-
-
-
-
-      <br>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <table style="text-align: left; width: 100%;" cellpadding="2">
-
-
-
-
-
-        <tbody>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: middle;">k<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="vertical-align: middle;">Vertical grid point
-index.</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="vertical-align: middle;">zw<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="vertical-align: middle;">Height of the grid
+</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 (
+</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
+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
+</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
+</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
@@ -2543,409 +466,42 @@
 only switched on at initial runs), executing computer, date,
 time of the beginning of the run, output time). Afterwards the
-following columns appear:<br>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <table style="text-align: left; width: 100%;" cellpadding="2">
-
-
-
-
-
-        <tbody>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">k<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Vertical
-grid point index.</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">zu<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Height
+following columns appear:<br> <table style="text-align: left; width: 100%;" cellpadding="2">
+<tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br>
+</td> <td style="text-align: left; vertical-align: middle;">Vertical
+grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br>
+</td> <td style="text-align: left; vertical-align: middle;">Height
 of the grid point
 level (<font color="#000000">in </font>m).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">u<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">u-component
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br>
+</td> <td style="text-align: left; vertical-align: middle;">u-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">v<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">v-component
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br>
+</td> <td style="text-align: left; vertical-align: middle;">v-component
 of the wind
 velocity (<font color="#000000">in </font>m/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">pt<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Potential
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">pt<br>
+</td> <td style="text-align: left; vertical-align: middle;">Potential
 temperature (<font color="#000000">in </font>K).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">e<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Turbulent
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br>
+</td> <td style="text-align: left; vertical-align: middle;">Turbulent
 kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">rif<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Flux
-Richardson number</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Km<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Turbulent
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">rif<br>
+</td> <td style="text-align: left; vertical-align: middle;">Flux
+Richardson number</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br>
+</td> <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Kh<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">Turbulent
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br>
+</td> <td style="text-align: left; vertical-align: middle;">Turbulent
 diffusion
 coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-          <tr>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;">l<br>
-
-
-
-
-
-            </td>
-
-
-
-
-
-            <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
-length (</font><font color="#000000">in </font><font color="#000000">m).</font></td>
-
-
-
-
-
-          </tr>
-
-
-
-
-
-        
-        
-        
-        
-        
-        </tbody>
-      
-      
-      
-      
-      
-      </table>
-
-
-
-
-
-      <br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">18 </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">O </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Time measurements are
+</tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br>
+</td> <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
+length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> </tr> </tbody>
+</table> <br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">18 </td>
+<td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
+</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
@@ -2956,16 +512,13 @@
 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
+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
+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
@@ -2974,65 +527,12 @@
 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
+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
@@ -3054,98 +554,32 @@
 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
+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
+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;
+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;
+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
+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 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
@@ -3153,18 +587,10 @@
 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;,
+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
@@ -3182,258 +608,33 @@
 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
+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
+</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
+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
+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
+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
+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
@@ -3443,259 +644,32 @@
 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;).
+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
+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
+</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
+</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
@@ -3710,19 +684,10 @@
 -) 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
+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
+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
@@ -3736,19 +701,10 @@
 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
+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
+= <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>.
@@ -3758,198 +714,30 @@
 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
+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
+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
+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
+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
+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
@@ -3957,34 +745,15 @@
 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
+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
+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
+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
@@ -3992,98 +761,17 @@
 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
+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
+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
@@ -4097,16 +785,6 @@
 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
+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>)
@@ -4114,148 +792,23 @@
 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>
-
-
-
-
-
+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>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <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
+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>.
+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).
@@ -4265,20 +818,10 @@
 (<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
 means that the file starts with the data of the u-component profile,
-followed by the v-component profile, etc.).&nbsp;</p>
-      <p><br>
+followed by the v-component profile, etc.).&nbsp;</p> <p><br>
 The data can only be visualized with <span style="font-weight: bold;">profil</span>
 using NAMELIST-parameter sets, which are saved by the
-model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp; </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>The profile data written to the file are described with 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
@@ -4304,183 +847,44 @@
 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
+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
+= <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
+must be specified together)!&nbsp; </p> <p>Further
+information about output of
 vertical profile data is given in the description of the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.</p>
-
-
-
-
-
-      </td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">80 </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">O </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii </td>
-
-
-
-
-
-      <td style="vertical-align: top;">This
+</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">80 </td>
+<td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/ </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
+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
+</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
+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>)
+<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
+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
@@ -4488,71 +892,6 @@
 additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
 additional pages will be plotted for each single output time. </p>
-
-
-
-
-
-      </td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">82<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">O<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">This
+</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">82<br>
+</td> <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA </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>)
@@ -4561,30 +900,10 @@
 using NAMELIST parameter sets, which are written by
 the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
-
-
-
-
-
-      <br>
-
-
-
-
-
+<br>
 Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
 for actual plotting, this file contains all data of spectra specified
 by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br>
-
-
-
-
-
-      <br>
-
-
-
-
-
-      <font>Each data point of a spectrum is output in a single line
+<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
@@ -4593,163 +912,21 @@
 subsequent columns. </font>The order
 of the data in the file follows the order used in the assignment for <span style="font-style: italic;"></span><span style="font-style: italic;"></span><a href="chapter_4.2.html#data_output_sp">data_output_sp</a>.<br>
-
-
-
-
-
-      <br>
-
-
-
-
-
+<br>
 For orientation, a header of comment lines (one for each height level)
 is placed in front of the spectral data of each quantity. They indicate
 the respective quantity and the output time. The text of these comment
-lines is used as a legend in the plot. </td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">83<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">O<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">This
+lines is used as a legend in the plot. </td> </tr> <tr>
+<td style="vertical-align: top; text-align: center;">83<br>
+</td> <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR </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
+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>
-
-
-
-
-
+<br>
 For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">84<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td>
-
-
-
-
-
-      <td style="vertical-align: top;">O<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">This
+</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">84<br>
+</td> <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</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>)
@@ -4758,162 +935,31 @@
 using NAMELIST parameter sets, which are written by
 the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
-
-
-
-
-
-      <br>
-
-
-
-
-
+<br>
 For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top; text-align: center;">85<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td>
-
-
-
-
-
-      <td style="vertical-align: top;">O<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Binary<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">This
+</tr> <tr> <td style="vertical-align: top; text-align: center;">85<br>
+</td> <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</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
+package</a>) and contains all particle data for one or several
+output
 times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
-
-
-
-
-
-      <br>
-
-
-
-
-
+<br>
 The first record of this file contains an identification string (PALM
 version number, run identifier, etc., 80 characters long). The second
 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
+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
+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
+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
@@ -4925,23 +971,14 @@
 The
 number of processors which can be used must not be changed during a job
-chain and/or if a job chain is continued. <br>
-
-
-
-
-
-      <br>
-
-
-
-
-
+chain and/or if a job chain is continued. <br> <br>
 The first record of this file contains a version number (four character
-string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>, see end of
+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
+(<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
@@ -4954,77 +991,10 @@
 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
+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
@@ -5032,166 +1002,27 @@
 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="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>and/or&nbsp; <br>
-
-
-
-
-
-possibly&nbsp; </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>PLOT1D_PAR_0&nbsp; <br>
-
-
-
-
-
+package</a>). For a more detailed description of the file
+structure see <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
+</tr> <tr> <td style="vertical-align: top; text-align: center;">90<br>
+</td> <td style="vertical-align: top;"> <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
+<p>and/or&nbsp; <br>
+possibly&nbsp; </p> <p>PLOT1D_PAR_0&nbsp; <br>
 PLOT1D_PAR_1&nbsp; <br>
-
-
-
-
-
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 .&nbsp; <br>
-
-
-
-
-
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 .&nbsp; <br>
-
-
-
-
-
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 .&nbsp; <br>
-
-
-
-
-
-PLOT1D_PAR_9</p>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">O<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
-
-
-
-
-
-      </td>
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      <p>NAMELIST parameter set, with which the layout of a plot
+PLOT1D_PAR_9</p> </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>)
+</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
@@ -5200,47 +1031,19 @@
 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
+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
+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
+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>
@@ -5248,80 +1051,14 @@
 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
+= <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
+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>.
@@ -5333,15 +1070,5 @@
 will be drawn onto a separate page (thus no color shading
 presentation, no vector arrows, streamlines etc.).&nbsp; </p>
-
-
-
-
-
-      
-      
-      
-      
-      
-      <p>Additionally <span style="font-weight: bold;">iso2d</span>
+<p>Additionally <span style="font-weight: bold;">iso2d</span>
 needs the so-called local parameter
 sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
@@ -5350,7 +1077,9 @@
 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
+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;).
+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
@@ -5360,661 +1089,219 @@
 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
+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
+</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
+</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>
-
-
-
-
+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>
+<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>
-
+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
+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>
-
+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>
-
+<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)
+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>
-
+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>
-
+<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
+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>
-
+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>
-
+<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>
-
+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>
-
+<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="chapter_4.2.html#dt_dots">dt_dots</a>)
-in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
-
-      <br>
-
+format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
+contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>)
+in NetCDF format. The data in this file can be visualized by any
+graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br> <br>
 More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter&nbsp; 4.5.1</a>.</font></font></font></td>
-
-      <td style="vertical-align: top;"><br>
-
-      </td>
-
-    </tr>
-
-    <tr>
-
-      <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td>
-
-      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td>
-
-      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
-
-      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
-
+<td style="vertical-align: top;"><br> </td> </tr>
+<tr> <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td> <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</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>
-
+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>
-
+<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>
-
+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>
-
+<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>
-
+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>
+<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>),
+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>
-
+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
+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>
-
+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>
-
+<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)
+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>
-
+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>
-
+<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
+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>
-
+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>
-
+<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>
-
+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>
+<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>
-
-
-
-
-
-<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>
+<span style="font-style: italic;">Last change:</span>
+$Id$<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 61)
+++ palm/trunk/DOC/app/chapter_3.5.1.html	(revision 62)
@@ -1,32 +1,13 @@
 <!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>
+<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
+</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
+</h3><p style="margin-bottom: 0cm; line-height: 100%;">The
 following table
 describes the available interfaces for user-defined code in the model,
@@ -34,47 +15,17 @@
 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
+<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
+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
@@ -85,28 +36,14 @@
 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
+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>
@@ -125,23 +62,8 @@
 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
+</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.
@@ -150,32 +72,21 @@
 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
+<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>) and of additional time series quantities (see comment line example in the file).&nbsp; <br>
-
+3.5.3</a>) and of additional time series quantities (see comment
+line example in the file).&nbsp; <br>
 CPU time for <tt><font style="font-size: 10pt;" size="2">user_init</font></tt>
 is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
-within the category &ldquo;initialisation&rdquo;.</p><p>See also <tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a href="#user_init_3d_model">user_init_3d_model</a>.</font></font></tt></p>
-
-      </td>
-
-    </tr>
-
-    <tr>
-
-      <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2">DEFAULT</font></tt>
+within the category &ldquo;initialisation&rdquo;.</p><p>See
+also <tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a href="#user_init_3d_model">user_init_3d_model</a>.</font></font></tt></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
+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
@@ -184,35 +95,19 @@
 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>
+<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>
+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><td style="vertical-align: top;">In the middle of <tt><font style="font-size: 10pt;" size="2">init_3d_model.f90</font></tt></td><td style="vertical-align: top;"><span style="font-family: monospace;"></span><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_3d_model"></a>user_init_3d_<br>model</font></font></tt></td><td style="vertical-align: top;">Initialization of the 3d-model.<br><br>Allows
+within the category &ldquo;initialisation&rdquo;.</p> </td>
+</tr> <tr><td style="vertical-align: top;">In
+the middle of <tt><font style="font-size: 10pt;" size="2">init_3d_model.f90</font></tt></td><td style="vertical-align: top;"><span style="font-family: monospace;"></span><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init_3d_model"></a>user_init_3d_<br>model</font></font></tt></td><td style="vertical-align: top;">Initialization of the 3d-model.<br><br>Allows
 the complete initialization of the 3d model. The user is responsible to
-set at least all those quantities which are normally set within <tt><font style="font-size: 10pt;" size="2">init_3d_model</font></tt>.</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,
+set at least all those quantities which are normally set within <tt><font style="font-size: 10pt;" size="2">init_3d_model</font></tt>.</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
@@ -220,51 +115,18 @@
 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
+</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
+</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
+</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
@@ -280,41 +142,17 @@
 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
+</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
@@ -328,5 +166,6 @@
 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>
+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>
@@ -335,7 +174,5 @@
 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>
+</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>.
@@ -344,9 +181,6 @@
 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
+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
@@ -362,58 +196,103 @@
 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>
+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<br>( sr )</font></font></tt></p>
-
-      </td>
-
-      <td width="862">
-      <p>Horizontal
+(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<br>(
+sr )</font></font></tt></p> </td> <td width="862"> <p>Horizontal
 averages of vertical profiles of user-defined
 quantities can be computed here. Also, additional time series
 quantities can be calculated. They have to be defined before in routine
-<a href="#user_init"><span style="font-family: Courier New,Courier,monospace;">user_init</span></a>. The routine is called once for each defined statistic region (see <a href="chapter_4.1.html#statistic_region">statistic_region</a>).</p><p></p><p>The routine contains some simple examples (as comment lines) in order to demonstrate how to use it.</p><p><br>Profiles have to be written to
+<a href="#user_init"><span style="font-family: Courier New,Courier,monospace;">user_init</span></a>.
+The routine is called once for each defined statistic region (see <a href="chapter_4.1.html#statistic_region">statistic_region</a>).</p><p></p><p>The
+routine contains some simple examples (as comment lines) in order to
+demonstrate how to use it.</p><p><br>Profiles have to
+be written to
 the array <tt><font style="font-size: 10pt;" size="2">sums</font></tt>.
 Please use profile numbers starting from 70 upward (thus e.g. <tt><font style="font-size: 10pt;" size="2">sums (&hellip;,
 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>.</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
+are temporally averaged in <tt><font style="font-size: 10pt;" size="2">flow_statistics</font></tt>.</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>
@@ -423,24 +302,10 @@
 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>
-
+</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: </i>$Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_3.5.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.2.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.5.2.html	(revision 62)
@@ -1,21 +1,15 @@
 <!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
+<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 style="direction: 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
+<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
@@ -25,7 +19,9 @@
 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
+<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>
+<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
@@ -33,36 +29,38 @@
 </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,
+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
+<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
+<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>
+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
+<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
+<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
+<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
@@ -73,10 +71,7 @@
 is available. <br>
 &nbsp; </p>
-<hr>
-<p style="line-height: 100%;"><br>
+<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>
+</font></font></p><p style="line-height: 100%;"><span style="font-style: italic;">Last
+change:</span> $Id$<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 61)
+++ palm/trunk/DOC/app/chapter_3.5.3.html	(revision 62)
@@ -1,21 +1,15 @@
 <!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
+<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 style="direction: 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 timeseries quantities and the horizontally averaged vertical profiles (saved in local files
+<p style="line-height: 100%;">By default, the values of
+the timeseries quantities and the horizontally averaged vertical
+profiles (saved in local files
 <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
 and <a href="chapter_3.4.html#LIST_PROFIL">LIST_PROFIL</a>)
@@ -25,7 +19,9 @@
 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
+<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
+<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
@@ -36,8 +32,8 @@
 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
+<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">,
@@ -56,5 +52,6 @@
 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
+<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
@@ -66,45 +63,30 @@
 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,
+<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
+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
+(<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>)!
@@ -112,5 +94,6 @@
 if
 the user sets <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>
-&ge; <i>1</i>. Beyond that, names for the user-defined subdomains can be
+&ge; <i>1</i>. Beyond that, names for the user-defined
+subdomains can be
 assigned
 via the initialization parameter <a href="chapter_4.3.html#region">region</a>.
@@ -121,7 +104,6 @@
 <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> 07/03/07 (SR)</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>
+$Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_3.5.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.4.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.5.4.html	(revision 62)
@@ -1,24 +1,20 @@
 <!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
+<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 style="direction: 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
+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
@@ -30,42 +26,173 @@
 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>.
+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>
+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>
+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
+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
+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(
+&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
+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
+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;
+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>
+';&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> $Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_3.5.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.5.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.5.5.html	(revision 62)
@@ -1,31 +1,50 @@
 <!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
+<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 style="direction: 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%;">Users can add their own (modified) user-interface to a PALM-run by carrying out the following steps:</p><ol><li>Copy the default (empty) user-interface (file<span style="font-family: Courier New,Courier,monospace;"> user_interface.f90</span>) to a directory of your choice, e.g.:<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp; &nbsp;cd ~/palm/current_version</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">&nbsp; &nbsp;mkdir -p USER_CODE/example</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">&nbsp; &nbsp;cp trunk/SOURCE/user_interface.f90&nbsp; USER_CODE/example/user_example.f90</span><br></li><li>Set an additional path in the configuration file<span style="font-family: Courier New,Courier,monospace;"> .mrun.config </span>to allow <span style="font-weight: bold;">mrun </span>to find and include this file:<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp; &nbsp;%add_source_path&nbsp;&nbsp; $base_directory/USER_CODE/$fname</span><br><br>The default configuration file (<span style="font-family: Courier New,Courier,monospace;">trunk/SCRIPTS/.mrun.config.default</span>) already includes this setting.</li><li>Modify the interface routines according to your needs.</li><li>Start a PALM run by executing<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp; &nbsp;mrun -d example ...</span><br><br>The file<span style="font-family: Courier New,Courier,monospace;"> user_example.f90 </span>will be automatically compiled within the job and will replace PALM&lsquo;s default user-interface.<br></li></ol>The above method with including<span style="font-family: Courier New,Courier,monospace;"> $fname </span>in
+</font></h3><p style="line-height: 100%;">Users
+can add their own (modified) user-interface to a PALM-run by carrying
+out the following steps:</p><ol><li>Copy the default
+(empty) user-interface (file<span style="font-family: Courier New,Courier,monospace;">
+user_interface.f90</span>) to a directory of your choice, e.g.:<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp;
+&nbsp;cd ~/palm/current_version</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">&nbsp;
+&nbsp;mkdir -p USER_CODE/example</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">&nbsp;
+&nbsp;cp trunk/SOURCE/user_interface.f90&nbsp;
+USER_CODE/example/user_example.f90</span><br></li><li>Set
+an additional path in the configuration file<span style="font-family: Courier New,Courier,monospace;">
+.mrun.config </span>to allow <span style="font-weight: bold;">mrun
+</span>to find and include this file:<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp;
+&nbsp;%add_source_path&nbsp;&nbsp;
+$base_directory/USER_CODE/$fname</span><br><br>The
+default configuration file (<span style="font-family: Courier New,Courier,monospace;">trunk/SCRIPTS/.mrun.config.default</span>)
+already includes this setting.</li><li>Modify the interface
+routines according to your needs.</li><li>Start a PALM run
+by executing<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp;
+&nbsp;mrun -d example ...</span><br><br>The file<span style="font-family: Courier New,Courier,monospace;">
+user_example.f90 </span>will be automatically compiled within
+the job and will replace PALM&lsquo;s default user-interface.<br></li></ol>The
+above method with including<span style="font-family: Courier New,Courier,monospace;"> $fname </span>in
 the additional source path allows to use different user-interfaces for
 different runs at the same time. Just store the respective
-interface-files in subdirectories<span style="font-family: Courier New,Courier,monospace;"> USER_CODE/abcd</span>,<span style="font-family: Courier New,Courier,monospace;"> USER_CODE/cdef</span>, etc. and start <span style="font-weight: bold;">mrun</span> with option &ldquo;<span style="font-family: Courier New,Courier,monospace;">-d abcd</span>&ldquo;, &ldquo;<span style="font-family: Courier New,Courier,monospace;">-d cdef</span>&ldquo;, etc.<br><br><span style="font-weight: bold;">The modified user-interface file cannot be pre-compiled by using mbuild!</span><br><br>While programming user-defined code,
+interface-files in subdirectories<span style="font-family: Courier New,Courier,monospace;">
+USER_CODE/abcd</span>,<span style="font-family: Courier New,Courier,monospace;">
+USER_CODE/cdef</span>, etc. and start <span style="font-weight: bold;">mrun</span> with option
+&ldquo;<span style="font-family: Courier New,Courier,monospace;">-d
+abcd</span>&ldquo;, &ldquo;<span style="font-family: Courier New,Courier,monospace;">-d cdef</span>&ldquo;,
+etc.<br><br><span style="font-weight: bold;">The
+modified user-interface file cannot be pre-compiled by using mbuild!</span><br><br>While
+programming user-defined code,
 errors are frequently made. Possible ways of error
 tracing are described in the next chapter. <br><p style="line-height: 100%;">
 &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>
+<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>
+$Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_3.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.5.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.5.html	(revision 62)
@@ -1,31 +1,25 @@
 <!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
+<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 style="direction: 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
+</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
+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
+<p style="line-height: 100%;">Changes of the standard
+model code by the
 user
 should be avoided whenever possible and are reserved to the
@@ -37,10 +31,12 @@
 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
+<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
+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
@@ -49,5 +45,6 @@
 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
+<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
@@ -55,16 +52,18 @@
 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)
+<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
+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
+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
@@ -73,9 +72,11 @@
 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
+<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
+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
@@ -85,11 +86,11 @@
 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
+<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>
+<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>
+$Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_3.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_3.6.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_3.6.html	(revision 62)
@@ -1,25 +1,22 @@
 <!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
+<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 style="direction: 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>). Files containing user-defined code must be stored in the directory given by the variable<span style="font-family: Courier New,Courier,monospace;"> %add_source_path </span>in the mrun-configuration file<span style="font-family: Courier New,Courier,monospace;"> .mrun.config</span>.<span style="font-family: monospace;"></span> All output-files possibly
+5.0</a>). Files containing user-defined code must be stored in
+the directory given by the variable<span style="font-family: Courier New,Courier,monospace;">
+%add_source_path </span>in the mrun-configuration file<span style="font-family: Courier New,Courier,monospace;">
+.mrun.config</span>.<span style="font-family: monospace;"></span>
+All output-files possibly
 created by the model and requested by the user to be kept after the run
 are copied to
@@ -27,5 +24,6 @@
 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
+<p style="line-height: 100%;">Since model runs usually
+require large
 amounts of CPU time, interactive runs may not be feasible, since
 in interactive mode CPU time
@@ -39,11 +37,12 @@
 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
+<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: Courier New,Courier,monospace;">%compiler_name&nbsp;&nbsp;&nbsp;&nbsp;
+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: Courier New,Courier,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: Courier New,Courier,monospace;">
@@ -62,34 +61,46 @@
 :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,
+<br></p>
+<p style="line-height: 100%;">(Attention: in the
+configuration file,
 the compiler and linker options (<span style="font-family: Courier New,Courier,monospace;">fopts
-</span>and<span style="font-family: Courier New,Courier,monospace;"> lopts</span>) must be
+</span>and<span style="font-family: Courier New,Courier,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: Courier New,Courier,monospace;">-g</span>" and "<span style="font-family: Courier New,Courier,monospace;">-C</span>", debugable code is created
+</p><p style="line-height: 100%;">Using the compiler
+options "<span style="font-family: Courier New,Courier,monospace;">-g</span>"
+and "<span style="font-family: Courier New,Courier,monospace;">-C</span>",
+debugable code is created
 and check of array bounds is
-switched on during run time. Option "<span style="font-family: Courier New,Courier,monospace;">-qinitauto=FF</span>" initializes all
+switched on during run time. Option "<span style="font-family: Courier New,Courier,monospace;">-qinitauto=FF</span>"
+initializes all
 automatic variables (unfortunately not the global values of modules) to
-NaN.The "<span style="font-family: Courier New,Courier,monospace;">-qflttrap</span>" and "<span style="font-family: Courier New,Courier,monospace;">-qsigtrap</span>" options are needed
+NaN.The "<span style="font-family: Courier New,Courier,monospace;">-qflttrap</span>"
+and "<span style="font-family: Courier New,Courier,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
+</p><p style="line-height: 100%;">The <b>mrun
+</b>call for debugging
 needs
-an extended argument for the option<span style="font-family: Courier New,Courier,monospace;"> </span><font style="font-size: 10pt; font-family: Courier New,Courier,monospace;" size="2">-K</font>:</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">mrun ... -K &ldquo;parallel debug&rdquo; -s &rdquo;*.f90" ... .</div><p style="line-height: 100%;">The argument of option<span style="font-family: Courier New,Courier,monospace;"> -s </span><span style="font-family: Courier New,Courier,monospace;"></span>must list all source code files of the default PALM code. </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
+an extended argument for the option<span style="font-family: Courier New,Courier,monospace;"> </span><font style="font-size: 10pt; font-family: Courier New,Courier,monospace;" size="2">-K</font>:</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">mrun
+... -K &ldquo;parallel debug&rdquo; -s &rdquo;*.f90" ... .</div><p style="line-height: 100%;">The argument of option<span style="font-family: Courier New,Courier,monospace;"> -s </span><span style="font-family: Courier New,Courier,monospace;"></span>must
+list all source code files of the default PALM code. </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
+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&nbsp;group can be asked for
-assistance, but please do not expect any quick response. It is emphasized again that error tracing and programming
+assistance, but please do not expect any quick response. It is
+emphasized again that error tracing and programming
 of
 user-defined code requires more or less precise knowledge of the
@@ -97,7 +108,6 @@
 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> 02/03/07 (SR)</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>
+$Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_4.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.0.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.0.html	(revision 62)
@@ -1,22 +1,15 @@
 <!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
+<html><head>
+<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
+chapter 4.0</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040809;14214479"> <meta name="CHANGED" content="20041112;15151993"> <meta name="KEYWORDS" content="parallel LES model"> <style>
+<!--
+@page { size: 21cm 29.7cm }
+-->
+</style></head>
+
+<body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">4.0
+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
@@ -26,8 +19,10 @@
 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
+</p><p style="line-height: 100%;">These data are
+assigned with the help of
+so-called ?&ldquo;NAMELIST-driven input&rdquo;? (FORTRAN -
+NAMELIST &ndash;
+input). The ?gew&auml;hlten? values of the model parameters are
+written
 into an ASCII file with fixed format, which is expected by the model as
 an input
@@ -39,28 +34,29 @@
 PARIN: <br>
 &nbsp; </p>
-<ul>
-  <p style="line-height: 100%; font-family: monospace;">&amp;inipar nx
+<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 =
+&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 =
+&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
+&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
+</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
+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
@@ -71,7 +67,7 @@
 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.
+</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>
@@ -82,19 +78,18 @@
 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
+(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
+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
+<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
@@ -104,16 +99,11 @@
 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
+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
@@ -123,22 +113,20 @@
 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,
+&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>
+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
@@ -146,5 +134,6 @@
 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.
+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
@@ -156,18 +145,8 @@
 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;
+<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>
+&nbsp;<span style="font-style: italic;">Last change:</span>
+$Id$<br>
+</p></body></html>
Index: palm/trunk/DOC/app/chapter_4.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.1.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.1.html	(revision 62)
@@ -1,6 +1,5 @@
 <!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>
+<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>
@@ -874,5 +873,10 @@
 of waves with wavelengths longer than 2-delta (see the paper by Mahrer
 and
-Pielke, quoted above). </p> </td> </tr> <tr>
+Pielke, quoted above). </p> </td> </tr> <tr><td style="vertical-align: top;"><a name="loop_optimization"></a><span style="font-weight: bold;">loop_optimization</span></td><td style="vertical-align: top;">C*16</td><td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td><td>Method used to optimize loops for solving the prognostic equations .<br><br>By
+default, the optimization method depends on the host on which PALM is
+running. On machines with vector-type CPUs, single 3d-loops are used to
+calculate each tendency term of each prognostic equation, while on all
+other machines, all prognostic equations are solved within one big loop
+over the two horizontal indices<span style="font-family: Courier New,Courier,monospace;"> i </span>and<span style="font-family: Courier New,Courier,monospace;"> j </span>(giving a good cache uitilization).<br><br>The default behaviour can be changed by setting either <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'vector'</span> or <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'cache'</span>.</td></tr><tr>
 <td style="vertical-align: top;"><a name="mixing_length_1d"></a><span style="font-weight: bold;">mixing_length_1d</span><br>
 </td> <td style="vertical-align: top;">C*20<br>
Index: palm/trunk/DOC/app/chapter_4.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.3.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.3.html	(revision 62)
@@ -1,70 +1,50 @@
 <!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>),
+<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 style="direction: 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
+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
+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>)
 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>
+(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>
+<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>
+$Id$&nbsp;</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_4.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.4.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.4.html	(revision 62)
@@ -1,20 +1,15 @@
 <!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
+<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 style="direction: 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
@@ -22,20 +17,21 @@
 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,
+<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
+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
+<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>)
+<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
@@ -43,10 +39,12 @@
 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
+<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
+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
@@ -56,57 +54,95 @@
 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
+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
+&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
+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
+<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
+= <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
+<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
+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
+<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>.
+(<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
+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
+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
+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
+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
+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
+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>
@@ -118,33 +154,31 @@
 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
+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
+</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
+<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
+-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
+<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
+<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>
+<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;
+</i>$Id$
+<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 61)
+++ palm/trunk/DOC/app/chapter_4.5.1.html	(revision 62)
@@ -1,5 +1,7 @@
 <!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>
+<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 }
@@ -16,5 +18,6 @@
 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
+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
@@ -26,5 +29,7 @@
 (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
+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
@@ -48,5 +53,6 @@
 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
+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
@@ -61,5 +67,6 @@
 <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#dt_dots">dt_dots</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output_format">data_output_format</a>, <a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">spectra</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>,
+<a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">timeseries</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#dt_dots">dt_dots</a></td><td align="left" valign="top"><a href="chapter_4.2.html#data_output_format">data_output_format</a>,
+<a href="chapter_4.1.html#statistic_regions">statistic_regions</a></td></tr><tr><td align="left" valign="top">spectra</td><td align="left" valign="top"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a></td><td align="left" valign="top"><a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>,
 <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>,
 <a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
@@ -148,5 +155,7 @@
 <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
+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
@@ -184,5 +193,6 @@
 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
+<p style="line-height: 100%;">Instantaneous data are
+output in NetCDF
 format
 into the
@@ -213,6 +223,11 @@
 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
+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>
@@ -223,5 +238,6 @@
 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:[[$
+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
@@ -255,5 +271,6 @@
 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
+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
@@ -268,7 +285,10 @@
 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
+is&nbsp;reading these data into a FORTRAN program. 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> 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
+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
@@ -276,20 +296,34 @@
 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
+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
+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
+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>
+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
+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
@@ -297,11 +331,19 @@
 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;
+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
+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
@@ -309,21 +351,126 @@
 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
+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>
+<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> $Id$&nbsp;</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_4.5.2.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.2.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.2.html	(revision 62)
@@ -1,28 +1,18 @@
 <!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
+<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 style="direction: ltr;" lang="en-US"><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;">
+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
+<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
@@ -38,41 +28,26 @@
 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>.
+<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
+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
+<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">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>
+</p><ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -d test -r &ldquo;pr&rdquo; &hellip;</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 style="font-size: 10pt;" size="2">PLOT1D_DATA</font></span></tt><span style="text-decoration: none;"><font style="font-size: 10pt;" size="2">
+</font>is copied to the permanent file </span><tt><span style="text-decoration: none;"><font style="font-size: 10pt;" size="2">~/PLOT/test/test_pr_in</font></span></tt><span style="text-decoration: none;">.
+However, the character string <font style="font-size: 10pt;" size="2">&ldquo;</font></span><tt><span style="text-decoration: none;"><font style="font-size: 10pt;" size="2">pr</font></span></tt><span style="text-decoration: none;"><font style="font-size: 10pt;" size="2">&rdquo;</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
@@ -83,19 +58,14 @@
 <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
+<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>
+<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">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
+<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 size="2"
- style="font-size: 10pt;">profil -d test_pr_in -p test_pr_par</font></pre>
-</ul>
+<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">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
@@ -110,7 +80,10 @@
 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
+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
@@ -119,5 +92,6 @@
 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
+<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>
@@ -127,10 +101,11 @@
 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
+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
+<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>
+determined by <span style="font-weight: bold;">dt_dopr</span>)<font style="font-size: 10pt;" size="2">.</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
@@ -141,16 +116,16 @@
 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
+<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
+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&hellip; 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>,
@@ -162,5 +137,6 @@
 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
+<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
@@ -174,54 +150,37 @@
 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">
+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>
+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 style="font-size: 10pt;" size="2">PLOT1D_DATA out:loc:tr pr# ~/PLOT/$fname _pr_in</font><br><font style="font-size: 10pt;" size="2">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 style="font-size: 10pt;" size="2">mrun - D test - r &ldquo;pr#&hellip;</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
+<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
+= <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
+<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>
+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><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.3.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%;"><span style="font-style: italic;">Last
-change:</span> 19/04/05 (SR)&nbsp;</p>
-</body>
-</html>
+change:</span> $Id$&nbsp;</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.3.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.3.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.3.html	(revision 62)
@@ -1,25 +1,17 @@
 <!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
+<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 style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.3
+Plots of time
 series
-with profil</font></h4>Sorry, this feature isn't supported any more.<hr>
-<p style="line-height: 100%;"><br>
-<font color="#000080"><font color="#000080"><a href="chapter_4.5.2.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.5.4.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
+with profil</font></h4>Sorry, this feature isn't supported
+any more.<hr>
+<p style="line-height: 100%;"><br><font color="#000080"><font color="#000080"><a href="chapter_4.5.2.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.5.4.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
 <p style="line-height: 100%;">&nbsp;<span style="font-style: italic;">Last
-change:</span> 06/03/07 (SR)<br>
-</p>
-</body></html>
+change:</span> $Id$<br>
+</p></body></html>
Index: palm/trunk/DOC/app/chapter_4.5.4.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.4.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.4.html	(revision 62)
@@ -1,23 +1,16 @@
 <!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
+<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 style="direction: 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
+<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
@@ -25,11 +18,7 @@
 <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;">
+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 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
@@ -37,50 +26,41 @@
 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>).
+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
+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
+</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
+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
+<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>
+<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -d test -r &ldquo;pxy&rdquo;&hellip;</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">&ldquo;</font><tt><font style="font-size: 10pt;" size="2">pxy</font></tt><font style="font-size: 10pt;" size="2">&rdquo;</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
+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
+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>
+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
@@ -93,41 +73,33 @@
 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
+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)
+<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
+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>
+<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>
+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
+<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
+</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
@@ -144,29 +116,25 @@
 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
+<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>
+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>
+<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;,
+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
+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
+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>
+<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>
@@ -179,22 +147,13 @@
 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>
+<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>
+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>
+$Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.5.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.5.html	(revision 62)
@@ -1,62 +1,51 @@
 <!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
+<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 style="direction: 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
+<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
+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
+<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;">
+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
+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
+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
+<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
+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>.
+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
+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
@@ -64,37 +53,34 @@
 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
+<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>
+<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font style="font-size: 10pt;" size="2">mrun -d test -r &ldquo;avs&rdquo;&hellip;</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 &ldquo;<tt><font style="font-size: 10pt;" size="2">avs</font></tt>&rdquo;
 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
+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
+</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
+(by executing the command &ldquo;avs&rdquo;), 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
+network editor). This module usually contains the module</font>
+&ldquo;read
+field&rdquo;, which requires an input
 file in the so-called "fld-format", which in turn refers to the two
 files
@@ -104,35 +90,30 @@
 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
+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
+<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>
+<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>
+</tt><font face="Thorndale, serif">.</font> In
+this case the entry
+&ldquo;<tt><font style="font-size: 10pt;" size="2">fld</font></tt>&rdquo;
 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>
+the suffix &rdquo; <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
+module &ldquo;read field&rdquo; 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">
+connection statements files with cycle numbers receive the names
+&rdquo;<tt><font style="font-size: 10pt;" size="2">&hellip;
+_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
+<p style="line-height: 100%;"><font color="#000000">The
+file
 connection statements must guarantee that all three permanent files
 (volume
@@ -140,18 +121,18 @@
 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
+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
+</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
+module <font color="#000000">&ldquo;read
+fields&rdquo; </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
+</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;,
@@ -159,12 +140,9 @@
 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
+<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>
+<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>
@@ -176,30 +154,14 @@
 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
+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>
+<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> $Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.6.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.6.html	(revision 62)
@@ -1,23 +1,16 @@
 <!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
+<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 style="direction: 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
+<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
@@ -26,7 +19,7 @@
 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
+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.
@@ -38,72 +31,60 @@
 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
+<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
+<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
+<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
+</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>
+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>
+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
+<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
+<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
+with the usual <span style="font-weight: bold;">AVS</span>
+module
+&ldquo;read field&rdquo;. Alternatively,
+the module &ldquo;read_compressed_field&rdquo; 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
+<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
+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>
+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>
+<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> $Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.7.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.7.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.7.html	(revision 62)
@@ -1,21 +1,13 @@
 <!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
+<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 style="direction: 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>
@@ -27,10 +19,13 @@
 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
+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
+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
+<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
@@ -46,8 +41,7 @@
 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
+<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),
@@ -55,16 +49,16 @@
 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
+<br>Methoden zur visuellen und haptischen tele-immersiven
+Exploration
+<br>komplexer Volumen- und Str&ouml;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
+&ldquo;dvrp_graphics&rdquo;</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
@@ -73,14 +67,15 @@
 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>.
+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
+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
@@ -88,17 +83,8 @@
 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>
+<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> $Id$</p>
+</body></html>
Index: palm/trunk/DOC/app/chapter_4.5.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.5.html	(revision 62)
@@ -1,25 +1,19 @@
 <!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
+<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 style="direction: 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
+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
@@ -31,17 +25,20 @@
 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
+<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
+(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
+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
+</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
@@ -54,21 +51,18 @@
 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>)
+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
+<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>&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>
+change:</span> $Id$<br>
+</p></body></html>
Index: palm/trunk/DOC/app/chapter_4.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.6.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_4.6.html	(revision 62)
@@ -1,6 +1,5 @@
 <!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>
+<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 }
@@ -701,5 +700,5 @@
 <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%">
+<tr><td><a style="font-weight: bold;" href="chapter_4.1.html#loop_optimization">loop_optimization</a></td><td>I</td><td>C * 16</td><td>see parameter description</td><td>Method used to optimize loops for solving the prognostic equations .</td></tr><tr> <td style="vertical-align: middle;" width="15%">
 <p><a href="chapter_4.2.html#maximum_number_of_particles"><b>maximum_number_</b></a>
 <br> <a href="chapter_4.2.html#maximum_number_of_particles"><b>of_particles</b></a></p>
Index: palm/trunk/DOC/app/chapter_5.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_5.0.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_5.0.html	(revision 62)
@@ -1,157 +1,275 @@
 <!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
+<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 style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">5.0
+Installation of the
 model</font></h2>
 <font color="#000000">This chapter
-describes the installation of PALM on a Linux workstation (local host) and a suitable remote computer, on which the
+describes the installation of PALM on a Linux workstation (local host)
+and a suitable remote computer, on which the
 model runs are to be carried out. The local host is used to
-start batch jobs with <b>mrun</b> and to analyze the results
-which are produced by the model on the remote host and send back to the local host. Alternatively, <span style="font-weight: bold;">mrun</span> can also be used to start PALM on the local host in interactive mode or as a batch job.</font><p style="line-height: 100%;"><font color="#000000"></font></p><p style="line-height: 100%;"><font color="#000000"><span style="font-weight: bold; text-decoration: underline;">Requirements</span></font></p><p style="line-height: 100%;"><font color="#000000">The installation and operation of PALM requires at mimimum (on both, the local and the remote host, unless stated otherwise):</font></p><ol><li><font color="#000000">The AT&amp;T Korn-shell (ksh) must be available under<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">/bin/ksh</font><font color="#000000">. Most of the current Linux distributions are using the public domain Korn-shell (pdksh). The PALM scripts <span style="font-weight: bold;">mrun</span> and <span style="font-weight: bold;">mbuild</span> do not work with the pdksh! Please replace it by the AT&amp;T ksh. If the AT&amp;T ksh path is different from<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">/bin/ksh</font><font color="#000000">, please modify the first lines in <span style="font-weight: bold;">mrun</span> and <span style="font-weight: bold;">mbuild</span>, respectively.</font></li><li><font color="#000000">The NetCDF-library with version number not earlier than 3.6.0-p1 (for NetCDF, see under <a href="http://www.unidata.ucar.edu/software/netcdf/">www.unidata.ucar.edu</a>).</font></li><li><font color="#000000">A FORTRAN90/95 compiler.</font></li><li><font color="#000000">The Message Passing Interface (MPI), at least on the remote host, if the parallel version of PALM shall be used.</font></li><li><font color="#000000">On the local host, the revision control system <span style="font-weight: bold;">subversion</span> (see <a href="http://subversion.tigris.org/">subversion.tigris.org</a>).
-This is already included in many Linux distributions (e.g. SuSe). <span style="font-weight: bold;">subversion requires port 3690 to be open for tcp/udp.</span> <span style="font-weight: bold;">If there are firewall restrictions concerning this port, the PALM code cannot be accessed.</span> The
+start batch jobs with <b>mrun</b> and to analyze the
+results
+which are produced by the model on the remote host and send back to the
+local host. Alternatively, <span style="font-weight: bold;">mrun</span>
+can also be used to start PALM on the local host in interactive mode or
+as a batch job.</font><p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000"><span style="font-weight: bold; text-decoration: underline;">Requirements</span></font></p><p style="line-height: 100%;"><font color="#000000">The
+installation and operation of PALM requires at mimimum (on both, the
+local and the remote host, unless stated otherwise):</font></p><ol><li><font color="#000000">The AT&amp;T Korn-shell (ksh) must be
+available under<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">/bin/ksh</font><font color="#000000">.
+Most of the current Linux distributions are using the public domain
+Korn-shell (pdksh). The PALM scripts <span style="font-weight: bold;">mrun</span> and <span style="font-weight: bold;">mbuild</span> do not work
+with the pdksh! Please replace it by the AT&amp;T ksh. If the
+AT&amp;T ksh path is different from<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">/bin/ksh</font><font color="#000000">,
+please modify the first lines in <span style="font-weight: bold;">mrun</span>
+and <span style="font-weight: bold;">mbuild</span>,
+respectively.</font></li><li><font color="#000000">The
+NetCDF-library with version number not earlier than 3.6.0-p1 (for
+NetCDF, see under <a href="http://www.unidata.ucar.edu/software/netcdf/">www.unidata.ucar.edu</a>).</font></li><li><font color="#000000">A FORTRAN90/95 compiler.</font></li><li><font color="#000000">The Message Passing Interface (MPI), at
+least on the remote host, if the parallel version of PALM shall be used.</font></li><li><font color="#000000">On the local host, the revision control
+system <span style="font-weight: bold;">subversion</span>
+(see <a href="http://subversion.tigris.org/">subversion.tigris.org</a>).
+This is already included in many Linux distributions (e.g. SuSe). <span style="font-weight: bold;">subversion requires port 3690 to
+be open for tcp/udp.</span> <span style="font-weight: bold;">If
+there are firewall restrictions concerning this port, the PALM code
+cannot be accessed.</span> The
 user needs a permit to access the PALM repository. For getting a permit
 please contact the PALM group (<a href="mailto:raasch@muk.uni-hannover.de">raasch@muk.uni-hannover.de</a>)
 and define a username under which you like to access the repository.
 You will then receive a password which allows the access under this
-name.</font></li><li><font color="#000000">A job queueing system must be available on the remote host. Currently, <span style="font-weight: bold;">mrun</span> can handle LoadLeveler (IBM-AIX) and NQS/PBS (Linux-Clusters, NEC-SX).</font></li><li><font color="#000000">ssh/scp-connections to and from the remote host must not be blocked by a firewall.<br></font></li></ol><font color="#000000"><span style="font-weight: bold;"></span></font><font color="#000000"> Currently, <span style="font-weight: bold;">mrun</span> is configured to be used on a limited number of selected machines. These are IBM-Regatta at computing center HLRN in Hannover (<span style="font-style: italic;">ibmh</span>), Berlin (<span style="font-style: italic;">ibmb</span>), at KISTI, Korea (<span style="font-style: italic;">ibms</span>), at Yonsei University, Seoul (<span style="font-style: italic;">ibms</span>), on NEC-SX6/8 systems at DKRZ, Hamburg (<span style="font-style: italic;">nech</span>) and RIAM, Kyushu University, Fukuoka (<span style="font-style: italic;">neck</span>), as well as on the Linux cluster of IMUK (<span style="font-style: italic;">lcmuk</span>) and Tokyo Institute of Technology (<span style="font-style: italic;">lctit</span>). The strings given in brackets are the systems names under which <span style="font-weight: bold;">mrun</span> indentifies the different hosts. mrun should also work on other systems, but this requires some modifications in the scripts <span style="font-weight: bold;">mrun</span>, <span style="font-weight: bold;">mbuild</span>, and <span style="font-weight: bold;">subjob</span>. Future PALM versions will allow to configure the scripts for different kinds of systems by just using a configuration file.</font><p style="line-height: 100%;"><font color="#000000">The examples given in this chapter refer to an
+name.</font></li><li><font color="#000000">A
+job queueing system must be available on the remote host. Currently, <span style="font-weight: bold;">mrun</span> can handle
+LoadLeveler (IBM-AIX) and NQS/PBS (Linux-Clusters, NEC-SX).</font></li><li><font color="#000000">ssh/scp-connections to and from the remote
+host must not be blocked by a firewall.<br></font></li></ol><font color="#000000"><span style="font-weight: bold;"></span></font><font color="#000000"> Currently, <span style="font-weight: bold;">mrun</span> is configured
+to be used on a limited number of selected machines. These are
+IBM-Regatta at computing center HLRN in Hannover (<span style="font-style: italic;">ibmh</span>), Berlin (<span style="font-style: italic;">ibmb</span>), at KISTI,
+Korea (<span style="font-style: italic;">ibms</span>),
+at Yonsei University, Seoul (<span style="font-style: italic;">ibms</span>),
+on NEC-SX6/8 systems at DKRZ, Hamburg (<span style="font-style: italic;">nech</span>) and RIAM,
+Kyushu University, Fukuoka (<span style="font-style: italic;">neck</span>),
+as well as on the Linux cluster of IMUK (<span style="font-style: italic;">lcmuk</span>) and Tokyo
+Institute of Technology (<span style="font-style: italic;">lctit</span>).
+The strings given in brackets are the systems names under which <span style="font-weight: bold;">mrun</span> indentifies the
+different hosts. mrun should also work on other systems, but this
+requires some modifications in the scripts <span style="font-weight: bold;">mrun</span>, <span style="font-weight: bold;">mbuild</span>, and <span style="font-weight: bold;">subjob</span>. Future PALM
+versions will allow to configure the scripts for different kinds of
+systems by just using a configuration file.</font><p style="line-height: 100%;"><font color="#000000">The
+examples given in this chapter refer to an
 installation of PALM on an IMUK Linux workstation and the IBM-Regatta
 system of
-the HLRN used as&nbsp;remote host. They are just called local and remote host from now on. </font></p><p style="line-height: 100%;">
-</p>
-<p style="line-height: 100%;">The installation process requires a valid
+the HLRN used as&nbsp;remote host. They are just called local and
+remote host from now on. </font></p><p style="line-height: 100%;">
+</p><p style="line-height: 100%;">The installation
+process requires a valid
 account on the local and on the remote host as well.<br>
 &nbsp; </p>
-<ul>
-  All hosts (local as well as remote) are
+<ul> 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
+<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 style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
-</span><span style="font-family: Courier New,Courier,monospace;">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;
-</span><span style="font-family: Courier New,Courier,monospace;">ssh&nbsp; &lt;username on local host&gt;@&lt;local IP-adddress&gt;</span><br>
-  </p>
-  In both cases you should&nbsp;not 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.
-</ul>
-<p style="line-height: 100%;"></p><p style="line-height: 100%;"><span style="font-weight: bold; text-decoration: underline;">Package Installation</span></p><p style="line-height: 100%;">In the <b>first installation step</b> a
+well as from the remote to the local host!</b> Test this by
+carrying
+out e.g. on the local host: <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
+</span><span style="font-family: Courier New,Courier,monospace;">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;
+</span><span style="font-family: Courier New,Courier,monospace;">ssh&nbsp;
+&lt;username on local host&gt;@&lt;local IP-adddress&gt;</span><br>
+</p> In both cases you should&nbsp;not 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.
+</ul><p style="line-height: 100%;"></p><p style="line-height: 100%;"><span style="font-weight: bold; text-decoration: underline;">Package
+Installation</span></p><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><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/job_queue<br></div><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/palm<br></div><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/palm/current_version<br></div><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS</span><br></div><p style="line-height: 100%;">The names of these directories are
+remote host. These directories are:</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/job_queue<br></div><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/palm<br></div><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/palm/current_version<br></div><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS</span><br></div><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. The directory <span style="font-family: monospace;">~/palm/current_version</span> on the local host will be called the working directory from now on. </p>
-<p style="line-height: 100%;"><font color="#000000">In the <b>second
+assuming these settings. The directory <span style="font-family: monospace;">~/palm/current_version</span>
+on the local host will be called the working directory from now on. </p>
+<p style="line-height: 100%;"><font color="#000000">In
+the <b>second
 step</b>
 a working copy of the recent version of the PALM software package,
-including the source code, scripts, documentation, etc.&nbsp; must be
+including the source code, scripts, documentation, etc.&nbsp; must
+be
 copied to the working directory (</font><font color="#000000">local
 host!) by executing the following
-commands. Replace &lt;your username&gt; by the name that you chose to
-access the repository, and &lt;#&gt; by any of the available PALM
-releases, e.g. "<span style="font-style: italic;">3.1c</span>" (new releases will be anounced by email to the PALM mailing list).</font></p><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">cd ~/palm/current_version</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">svn checkout --username &lt;your username&gt; svn://130.75.105.45/palm/tags/release-&lt;#&gt; trunk</span><br></div><p style="line-height: 100%;"><font color="#000000">You will then be prompted for your password. After finishing, the subdirectory</font><font style="font-family: Courier New,Courier,monospace;" color="#000000"> trunk </font><font color="#000000">should
+commands. Replace &lt;your username&gt; by the name that you
+chose to
+access the repository, and &lt;#&gt; by any of the available
+PALM
+releases, e.g. "<span style="font-style: italic;">3.1c</span>"
+(new releases will be anounced by email to the PALM mailing list).</font></p><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">cd
+~/palm/current_version</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">svn
+checkout --username &lt;your username&gt;
+svn://130.75.105.45/palm/tags/release-&lt;#&gt; trunk</span><br></div><p style="line-height: 100%;"><font color="#000000">You
+will then be prompted for your password. After finishing, the
+subdirectory</font><font style="font-family: Courier New,Courier,monospace;" color="#000000"> trunk </font><font color="#000000">should
 appear in your working directory. It contains a number of further
-subdirectories which contain e.g. the PALM source code (</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">SOURCE</font><font color="#000000">) and the scripts for running PALM (</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">SCRIPTS</font><font color="#000000">).</font></p><p style="line-height: 100%;">Alternatively,&nbsp;executing</p><pre style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">svn checkout --username &lt;your username&gt; svn://130.75.105.45/palm/tags/release-&lt;#&gt; abcde</pre><p style="line-height: 100%;">will place your working copy in a directory named<span style="font-family: Courier New,Courier,monospace;"> abcde </span>instead of a directory named<span style="font-family: Courier New,Courier,monospace;"> trunk</span>. But keep in mind that you will have to adjust several paths given below, if you do not use the default directory<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.</p><p style="line-height: 100%;">Please never touch any file in your working copy of PALM, unless you&nbsp;know exactly what you are doing.</p><p style="line-height: 100%; font-weight: bold;"><span style="font-weight: normal;">You can also get a copy of the most recent code by executing</span></p><pre style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">svn checkout --username &lt;your username&gt; svn://130.75.105.45/palm/trunk trunk</pre>However, this version may contain bugs and new features may not be documented. <span style="font-weight: bold;">In future PALM releases, repository access to this most recent&nbsp;version will
-probably be restricted to the PALM developers.</span><p style="line-height: 100%;"><font color="#000000"></font></p><p style="line-height: 100%;"><font color="#000000"><span style="font-weight: bold; text-decoration: underline;">Package Configuration</span></font></p><p style="line-height: 100%;"><font color="#000000">To
+subdirectories which contain e.g. the PALM source code (</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">SOURCE</font><font color="#000000">)
+and the scripts for running PALM (</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">SCRIPTS</font><font color="#000000">).</font></p><p style="line-height: 100%;">Alternatively,&nbsp;executing</p><pre style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">svn checkout --username &lt;your username&gt; svn://130.75.105.45/palm/tags/release-&lt;#&gt; abcde</pre><p style="line-height: 100%;">will place your working copy in a
+directory named<span style="font-family: Courier New,Courier,monospace;"> abcde </span>instead
+of a directory named<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.
+But keep in mind that you will have to adjust several paths given
+below, if you do not use the default directory<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.</p><p style="line-height: 100%;">Please never touch any file in
+your working copy of PALM, unless you&nbsp;know exactly what you
+are doing.</p><p style="line-height: 100%; font-weight: bold;"><span style="font-weight: normal;">You can also get a copy of the
+most recent code by executing</span></p><pre style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">svn checkout --username &lt;your username&gt; svn://130.75.105.45/palm/trunk trunk</pre>However,
+this version may contain bugs and new features may not be documented. <span style="font-weight: bold;">In future PALM releases,
+repository access to this most recent&nbsp;version will
+probably be restricted to the PALM developers.</span><p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000"><span style="font-weight: bold; text-decoration: underline;">Package
+Configuration</span></font></p><p style="line-height: 100%;"><font color="#000000">To
 use the PALM scripts, the PATH variable has to be extended and the
 environment variable PALM_BIN has to be set (on local and remote host)
-in the respective profile of the users default shell (e.g. in<span style="font-family: Courier New,Courier,monospace;"> .profile</span>, if<span style="font-family: Courier New,Courier,monospace;"> ksh </span>is used):</font></p><p style="line-height: 100%; margin-left: 40px;"><font style="font-family: Courier New,Courier,monospace;" color="#000000">export PATH=$HOME/palm/current_version/trunk/SCRIPTS:$PATH</font><font color="#000000"><br><span style="font-family: Courier New,Courier,monospace;">export PALM_BIN=</span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">$HOME/palm/current_version/trunk/SCRIPTS</font></p><p style="line-height: 100%;"><font color="#000000">You may habe to login again in order to activate these settings.</font></p><font color="#000000">On the local and on the remote host, some small helper/utility programs have to be installed, which are e.g. later used by <span style="font-weight: bold;">mrun</span> or for PALM data postprocessing. The installation is done by <span style="font-weight: bold;">mbuild</span>. This script requires a configuration file<span style="font-family: Courier New,Courier,monospace;"> .mrun.config</span>, which will be also used by <span style="font-weight: bold;">mrun</span> in the following. A copy has to be put into the working directory under the name<span style="font-family: Courier New,Courier,monospace;"> .mrun.config </span>by</font><p style="line-height: 100%; margin-left: 40px;"><font color="#000000"><span style="font-family: Courier New,Courier,monospace;">cp trunk/SCRIPTS/.mrun.config.default .mrun.config</span></font></p><font color="#000000">Beside many other things, this file contains typical installation parameters
+in the respective profile of the users default shell (e.g. in<span style="font-family: Courier New,Courier,monospace;"> .profile</span>,
+if<span style="font-family: Courier New,Courier,monospace;">
+ksh </span>is used):</font></p><p style="line-height: 100%; margin-left: 40px;"><font style="font-family: Courier New,Courier,monospace;" color="#000000">export
+PATH=$HOME/palm/current_version/trunk/SCRIPTS:$PATH</font><font color="#000000"><br><span style="font-family: Courier New,Courier,monospace;">export
+PALM_BIN=</span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">$HOME/palm/current_version/trunk/SCRIPTS</font></p><p style="line-height: 100%;"><font color="#000000">You
+may habe to login again in order to activate these settings.</font></p><font color="#000000">On the local and on the remote host, some
+small helper/utility programs have to be installed, which are e.g.
+later used by <span style="font-weight: bold;">mrun</span>
+or for PALM data postprocessing. The installation is done by <span style="font-weight: bold;">mbuild</span>. This script
+requires a configuration file<span style="font-family: Courier New,Courier,monospace;">
+.mrun.config</span>, which will be also used by <span style="font-weight: bold;">mrun</span> in the
+following. A copy has to be put into the working directory under the
+name<span style="font-family: Courier New,Courier,monospace;">
+.mrun.config </span>by</font><p style="line-height: 100%; margin-left: 40px;"><font color="#000000"><span style="font-family: Courier New,Courier,monospace;">cp
+trunk/SCRIPTS/.mrun.config.default .mrun.config</span></font></p><font color="#000000">Beside many other things, this file contains
+typical installation parameters
 like compiler name, compiler options, etc.
-for a set of different remote hosts. Please edit this file, uncomment lines like</font><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">#%remote_username &nbsp;&lt;replace by your ... username&gt; &nbsp; &lt;remote-computer-shortcut&gt;</div><p style="line-height: 100%;"><font color="#000000">by removing the first hash (<span style="font-family: Courier New,Courier,monospace;">#</span>) character and replace the string "<span style="font-family: Courier New,Courier,monospace;">&lt;replace by ...&gt;</span>" by your username on the respective host given in the <span style="font-family: Courier New,Courier,monospace;">&lt;remote-computer-shortcut&gt;</span>. You only have to uncomment lines for those hosts on which you intend to use PALM.</font></p><p style="line-height: 100%;"><font color="#000000">After modifying the configuration file, the respective executables are generated by executing</font></p><p style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;"><font color="#000000">mbuild -u -h lcmuk<br>mbuild -u -h ibmh</font></p><p style="line-height: 100%;"><font color="#000000">The second call also copies the PALM scripts like <span style="font-weight: bold;">mrun</span> and <span style="font-weight: bold;">mbuild</span> to the remote host.</font></p><p style="line-height: 100%;"><font color="#000000"></font></p><p style="line-height: 100%;"><font color="#000000"><span style="font-weight: bold; text-decoration: underline;">Pre-Compilation of PALM Code</span></font></p><font color="#000000">
-</font>
-<br><font color="#000000">To avoid the
+for a set of different remote hosts. Please edit this file, uncomment
+lines like</font><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">#%remote_username
+&nbsp;&lt;replace by your ... username&gt; &nbsp;
+&lt;remote-computer-shortcut&gt;</div><p style="line-height: 100%;"><font color="#000000">by
+removing the first hash (<span style="font-family: Courier New,Courier,monospace;">#</span>)
+character and replace the string "<span style="font-family: Courier New,Courier,monospace;">&lt;replace
+by ...&gt;</span>" by your username on the respective host
+given in the <span style="font-family: Courier New,Courier,monospace;">&lt;remote-computer-shortcut&gt;</span>.
+You only have to uncomment lines for those hosts on which you intend to
+use PALM.</font></p><p style="line-height: 100%;"><font color="#000000">After modifying the configuration file, the
+respective executables are generated by executing</font></p><p style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;"><font color="#000000">mbuild -u -h lcmuk<br>mbuild -u -h ibmh</font></p><p style="line-height: 100%;"><font color="#000000">The
+second call also copies the PALM scripts like <span style="font-weight: bold;">mrun</span> and <span style="font-weight: bold;">mbuild</span> to the remote
+host.</font></p><p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000"><span style="font-weight: bold; text-decoration: underline;">Pre-Compilation
+of PALM Code</span></font></p><font color="#000000">
+</font><br><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 by again using the script <span style="font-weight: bold;">mbuild</span>. Due to the use of
+willl be pre-compiled once on the remote host by again using the script
+<span style="font-weight: bold;">mbuild</span>. Due
+to the use of
 FORTRAN modules in the source code, the subroutines must be compiled
-in a certain order. Therefore the so-called <i>make</i> mechanism
+in a certain order. Therefore the so-called <i>make</i>
+mechanism
 is used (see the respective man-page of the Unix operating system),
-requiring a<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">Makefile</font><font color="#000000">,
-in which the dependencies are described. This file is found in subdirectory <span style="font-family: Courier New,Courier,monospace;">trunk/SOURCE<span style="font-family: Times New Roman,Times,serif;">, where also the PALM code is stored</span></span>. The compiled sources (object
+requiring a<span style="font-family: Courier New,Courier,monospace;">
+</span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">Makefile</font><font color="#000000">,
+in which the dependencies are described. This file is found in
+subdirectory <span style="font-family: Courier New,Courier,monospace;">trunk/SOURCE<span style="font-family: Times New Roman,Times,serif;">, where
+also the PALM code is stored</span></span>. The compiled
+sources (object
 files) are
 stored&nbsp;on the remote computer in the default directory
 </font><font style="font-family: Courier New,Courier,monospace;" color="#000000">~/palm/current_version/MAKE_DEPOSITORY</font>.<font color="#000000"><span style="font-weight: bold;"></span></font><p style="line-height: 100%;"><font color="#000000">The
-pre-compilation for the remote host (here the IBM-Regatta of HLRN) is done by</font><span style="font-family: monospace;"></span></p><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">mbuild -h ibmh&nbsp;&nbsp;</span></div><p style="line-height: 100%;"><span style="font-family: Courier New,Courier,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.<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">mbuild</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"> </span>transfers the respective compiler calls to the remote
+pre-compilation for the remote host (here the IBM-Regatta of HLRN) is
+done by</font><span style="font-family: monospace;"></span></p><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">mbuild
+-h ibmh&nbsp;&nbsp;</span></div><p style="line-height: 100%;"><span style="font-family: Courier New,Courier,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.<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">mbuild</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"> </span>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><p style="line-height: 100%;">
-</p>
-<blockquote style="line-height: 100%; font-family: Courier New,Courier,monospace;"><font color="#000000">mbuild</font></blockquote>
-<p style="line-height: 100%;"><font color="#000000">PALM will
+</p><blockquote style="line-height: 100%; font-family: Courier New,Courier,monospace;"><font color="#000000">mbuild</font></blockquote>
+<p style="line-height: 100%;"><font color="#000000">PALM
+will
 be (consecutively) pre-compiled for all remote hosts listed in
-the configuration file. If you want to compile for the local host only, please enter</font></p><p style="line-height: 100%; margin-left: 40px;"><font color="#000000"><span style="font-family: Courier New,Courier,monospace;">mbuild -h lcmuk</span> </font>
-</p>
-<p style="line-height: 100%;"><font color="#000000"></font></p><p style="line-height: 100%; font-weight: bold; text-decoration: underline;"><font color="#000000">Installation Verification</font></p><font color="#000000">As a last step,
+the configuration file. If you want to compile for the local host only,
+please enter</font></p><p style="line-height: 100%; margin-left: 40px;"><font color="#000000"><span style="font-family: Courier New,Courier,monospace;">mbuild
+-h lcmuk</span> </font>
+</p><p style="line-height: 100%;"></p><p style="line-height: 100%; font-weight: bold; text-decoration: underline;"><font color="#000000">Installation Verification</font></p><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
+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
 copied from the PALM working copy by<br>
-</font>
-<div style="margin-left: 40px;"><span style="font-family: monospace;"></span><font style="font-family: Courier New,Courier,monospace;" color="#000000">mkdir -p JOBS/example/INPUT<br>cp trunk/INSTALL/example_p3d&nbsp;JOBS/example/INPUT/example_p3d</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"></span></font></div>
-<p style="line-height: 100%;"><font color="#000000">The test run can
+</font><div style="margin-left: 40px;"><span style="font-family: monospace;"></span><font style="font-family: Courier New,Courier,monospace;" color="#000000">mkdir -p JOBS/example/INPUT<br>cp
+trunk/INSTALL/example_p3d&nbsp;JOBS/example/INPUT/example_p3d</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"></span></font></div>
+<p style="line-height: 100%;"><font color="#000000">The
+test run can
 now be started by executing the command </font>
-</p>
-<pre style="margin-left: 1cm; margin-right: 1cm; margin-bottom: 0.5cm; line-height: 100%; font-family: Courier New,Courier,monospace;"><font color="#000000">mrun -d example -h ibmh -K parallel -X 8 -T 8 -t 500 -q cdev -r &ldquo;d3# pr#&rdquo;</font></pre>
+</p><pre style="margin-left: 1cm; margin-right: 1cm; margin-bottom: 0.5cm; line-height: 100%; font-family: Courier New,Courier,monospace;"><font color="#000000">mrun -d example -h ibmh -K parallel -X 8 -T 8 -t 500 -q cdev -r &ldquo;d3# pr#&rdquo;</font></pre>
 <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
+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. (&ldquo;</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">y</font><font color="#000000">&rdquo;). Next, a message of the queuing system like &ldquo;<i>Request</i> &hellip;
-<i>Submitted to queue&hellip; by&hellip;&rdquo; </i>should be displayed. Now the job is
-queued and either started immediately or at a later time, depending on the
+and the user is prompted for o.k. (&ldquo;</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">y</font><font color="#000000">&rdquo;).
+Next, a message of the queuing system like &ldquo;<i>Request</i>
+&hellip;
+<i>Submitted to queue&hellip; by&hellip;&rdquo; </i>should
+be displayed. Now the job is
+queued and 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<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">~/job_queue/ibmh_example</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"> </span>no more than a few minutes later. The content of this
+this run will appear under the file name<span style="font-family: Courier New,Courier,monospace;"> </span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">~/job_queue/ibmh_example</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"> </span>no
+more than a few minutes later. The content of this
 file should be carefully examined for any error messages.</font><p style="line-height: 100%;">
-</p>
-
-
-<p style="line-height: 100%;">Beside the job protocol and according to
+</p><p style="line-height: 100%;">Beside the job
+protocol and according to
 the configuration file and arguments given for <b>mrun</b>
-options<span style="font-family: Courier New,Courier,monospace;"> -d </span>and<span style="font-family: Courier New,Courier,monospace;"> -r</span><tt>,</tt>further files should be found in
+options<span style="font-family: Courier New,Courier,monospace;">
+-d </span>and<span style="font-family: Courier New,Courier,monospace;"> -r</span><tt>,</tt>further
+files should be found in
 the
 directories</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS/example/MONITORING</div><p style="line-height: 100%;">and</p>
 <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
 </span><span style="font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS/example/OUTPUT</span><span style="font-family: monospace;"></span><br>
-</p>
-<p style="line-height: 100%;">Please compare the contents of file</p>
+</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;
 </span><span style="font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS/example/MONITORING/ibmh_example_rc</span><br>
-</p>
-<p style="line-height: 100%;">with those of the example result file which can be found under<span style="font-family: Courier New,Courier,monospace;"> trunk/INSTALL/example_rc</span>., e.g. by using the<span style="font-family: Courier New,Courier,monospace;"><span style="font-family: Times New Roman,Times,serif;"> standard</span> diff </span>command:</p><p style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">diff &nbsp;JOBS/example/MONITORING/ibmh_example_rc trunk/INSTALL/example_rc</p><p style="line-height: 100%;">where it is assumed that your working directory is<span style="font-family: Courier New,Courier,monospace;"> ~/palm/current_version</span>.</p><span style="font-weight: bold;">You should not find any difference between these two files</span>, except of the run date and time displayed at the top of the file header. <font color="#000000">If
+</p><p style="line-height: 100%;">with those of the
+example result file which can be found under<span style="font-family: Courier New,Courier,monospace;">
+trunk/INSTALL/example_rc</span>., e.g. by using the<span style="font-family: Courier New,Courier,monospace;"><span style="font-family: Times New Roman,Times,serif;"> standard</span>
+diff </span>command:</p><p style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">diff
+&nbsp;JOBS/example/MONITORING/ibmh_example_rc
+trunk/INSTALL/example_rc</p><p style="line-height: 100%;">where
+it is assumed that your working directory is<span style="font-family: Courier New,Courier,monospace;">
+~/palm/current_version</span>.</p><span style="font-weight: bold;">You should not find any
+difference between these two files</span>, except of the run date
+and time displayed at the top of the file header. <font color="#000000">If
 the file contents are identical, the installation is successfully
 completed.</font>
-<p style="line-height: 100%;">If you have any problems with the PALM
+<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> 02/03/07 (SR) </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> $Id$</p>
 </body></html>
Index: palm/trunk/DOC/app/chapter_5.1.html
===================================================================
--- palm/trunk/DOC/app/chapter_5.1.html	(revision 61)
+++ palm/trunk/DOC/app/chapter_5.1.html	(revision 62)
@@ -1,38 +1,56 @@
 <!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 dir="ltr" lang="en-US">
-<h3>5.1 Installation of new / other versions</h3>
-<p>The PALM&nbsp;group announces code revisions by emails send to the
+<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 style="direction: ltr;" lang="en-US"><h3>5.1
+Installation of new / other versions</h3>
+<p>The PALM&nbsp;group announces code revisions by emails
+send to the
 PALM mailing list. If you like to be put on this list, just send an
-email to <a href="mailto:raasch@muk.uni-hannover.de">raasch@muk.uni-hannover.de</a>. Details about new releases can be found in the
+email to <a href="mailto:raasch@muk.uni-hannover.de">raasch@muk.uni-hannover.de</a>.
+Details about new releases can be found in the
 <a href="../tec/technical_documentation.html">technical/numerical
-documentation</a>. Users can easily make version updates by changing into
+documentation</a>. Users can easily make version updates by
+changing into
 the working directory<span style="font-family: Courier New,Courier,monospace;">
 ~/palm/current_version
-</span>and executing<span style="font-family: Courier New,Courier,monospace;"></span></p><p style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">svn update</span></p><p><span style="font-family: Courier New,Courier,monospace;"></span>This updates all files in the PALM working copy in subdirectory<span style="font-family: Courier New,Courier,monospace;"> trunk</span>. The update may fail due&nbsp;the&nbsp;<span style="font-weight: bold;">subversion</span> rules, if you have modified the contents of<span style="font-family: Courier New,Courier,monospace;"> trunk</span>. In case of any conflicts, please refer to the <span style="font-weight: bold;">subversion</span> documentation on how to remove them.&nbsp;In order to avoid such conflicts, modifications of the default PALM code should be omitted and
+</span>and executing<span style="font-family: Courier New,Courier,monospace;"></span></p><p style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">svn
+update</span></p><p><span style="font-family: Courier New,Courier,monospace;"></span>This
+updates all files in the PALM working copy in subdirectory<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.
+The update may fail due&nbsp;the&nbsp;<span style="font-weight: bold;">subversion</span> rules, if
+you have modified the contents of<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.
+In case of any conflicts, please refer to the <span style="font-weight: bold;">subversion</span>
+documentation on how to remove them.&nbsp;In order to avoid such
+conflicts, modifications of the default PALM code should be omitted and
 be restricted to the user-interface only
 (see <a href="chapter_3.5.html">chapter
 3.5</a>).</p>
-<ul style="font-family: Courier New,Courier,monospace;">
-</ul>
 
-<p>Alternatively, you can install new or other releases in a different directory, eg.</p><p style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">mkdir ~/palm/release-3.1c</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">cd ~/palm/release-3.1c</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">svn checkout --username &lt;your username&gt; svn://130.75.105.45:palm/tags/release-3.1c trunk</span></p>
+<p>Alternatively, you can install new or other releases in a
+different directory, eg.</p><p style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">mkdir
+~/palm/release-3.1c</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">cd
+~/palm/release-3.1c</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">svn
+checkout --username &lt;your username&gt;
+svn://130.75.105.45:palm/tags/release-3.1c trunk</span></p>
 <p>However, this would require to carry out again the complete
 installation process described in chapter 5.0. So far, differet
-versions of PALM cannot be used at the same time.</p><p>After updating the working copy, please check for any differences between your current configuration file (<span style="font-family: Courier New,Courier,monospace;">.mrun.config</span>) and the default configuration file under<span style="font-family: Courier New,Courier,monospace;"> trunk/SCRIPTS/.mrun.config.default </span>and adjust your current file, if neccessary.</p><p>The scripts and the pre-compiled code must then be updated
-via</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">mbuild -u -h lcmuk<br>mbuild -u -h ibmh<br>mbuild -h ibmh</div><p>or via</p>
-<ul style="font-family: Courier New,Courier,monospace;">
-</ul>
+versions of PALM cannot be used at the same time.</p><p>After
+updating the working copy, please check for any differences between
+your current configuration file (<span style="font-family: Courier New,Courier,monospace;">.mrun.config</span>)
+and the default configuration file under<span style="font-family: Courier New,Courier,monospace;">
+trunk/SCRIPTS/.mrun.config.default </span>and adjust your
+current file, if neccessary.</p><p>The scripts and the
+pre-compiled code must then be updated
+via</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">mbuild
+-u -h lcmuk<br>mbuild -u -h ibmh<br>mbuild -h ibmh</div><p>or
+via</p>
 
-<blockquote style="font-family: Courier New,Courier,monospace;">mbuild -u<br>mbuild</blockquote>
+<blockquote style="font-family: Courier New,Courier,monospace;">mbuild
+-u<br>mbuild</blockquote>
 <p>on all remote hosts listed in the configuration file<span style="font-family: Courier New,Courier,monospace;">
 .mrun.config</span>. </p>
-<p>As a last step, a suitable test run should be carried out. It should
+<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
@@ -40,12 +58,8 @@
 documentation</a>
 should be communicated as soon as possible to the PALM group.
-</p>
-<hr>
-<p><br>
-<font color="#000080"><font color="#000080"><a href="chapter_5.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></font></font><br>
+</p><hr>
+<p><br><font color="#000080"><font color="#000080"><a href="chapter_5.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></font></font><br>
 &nbsp;
-<br>
-&nbsp;<span style="font-style: italic;">Last change:</span> 02/03/07
-(SR)<br>
-</p>
-</body></html>
+<br>&nbsp;<span style="font-style: italic;">Last
+change:</span> $Id$<br>
+</p></body></html>
Index: palm/trunk/DOC/app/index.html
===================================================================
--- palm/trunk/DOC/app/index.html	(revision 61)
+++ palm/trunk/DOC/app/index.html	(revision 62)
@@ -148,7 +148,5 @@
 <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.1c<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; 05/03/07 <o:p></o:p></span></p>
+version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.1c<br>For date of last change see bottom line of each page. <o:p></o:p></span></p>
 <div style="text-align: center;" class="MsoNormal" align="center"><span style="font-family: Thorndale;">
 <hr align="center" size="2" width="100%"></span></div>
@@ -215,13 +213,9 @@
 <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>
+<span class="SpellE">versions</span><o:p></o:p></span></p><font color="#000000">&nbsp;
 <br>
-<br>
-<br>
-<br>
-<br style="">
-<!--[if !supportLineBreakNewLine]--><br style="">
-<!--[endif]--><o:p></o:p></span></p>
-</div>
+&nbsp;
+<span style="font-style: italic;">Last change:</span>
+$Id$<br>
+</font></div>
 </body></html>
Index: palm/trunk/DOC/tec/technical_documentation.html
===================================================================
--- palm/trunk/DOC/tec/technical_documentation.html	(revision 61)
+++ palm/trunk/DOC/tec/technical_documentation.html	(revision 62)
@@ -1,102 +1,39 @@
 <!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;
+<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.1c</span></td>
-
-    </tr>
-
-    <tr nosave="">
-
-      <td nosave=""><b>Last change of this document</b>:&nbsp;</td>
-
-      <td nosave=""><b>05/03/07</b></td>
-
-    </tr>
-
-  
-  </tbody>
-</table>
-
-<hr width="100%">
+<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.1c</span></td> </tr>
+<tr nosave=""> <td nosave=""><b>Last
+change of this document</b>:&nbsp;</td> <td nosave=""><b>$Id$</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
+<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
+</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>
-
+<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:
@@ -107,293 +44,110 @@
 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
+<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,
+von Parametern auf Zul&auml;ssigkeit (prandtl_layer, psolver, nx,
+ny,
 nz,
-fcl_factor), H&ouml;he der Schnittebenen der Horizontalschnitte wird
+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
+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,
+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
+</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
+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
+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
+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
+<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
+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
+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
+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
+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
+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,
+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 =
+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
+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
+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
+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
+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
@@ -401,125 +155,65 @@
 Realisiert wird die geneigte Ebene durch entsprechende
 Schr&auml;gstellung
-des Schwerkraftvektors. Dadurch erh&auml;lt auch die u-Komponente der
+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
+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,
+</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
+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
+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
+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
+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
+und skalaren Gr&ouml;&szlig;en (neue UP's, s. rechts).
+Berechnung von
 Variablen
-f&uuml;r spezielle Advektionsverfahren in eigenst&auml;ndiges UP
+f&uuml;r spezielle Advektionsverfahren in eigenst&auml;ndiges
+UP
 ausgelagert
-(<tt>init_advec</tt> + eigenes Modul <tt>advection</tt>). Reines
+(<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
+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
+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,
+</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>
-
+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_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
@@ -529,234 +223,94 @@
 Wertebegrenzung
 bei Spline - Berechnung zur Verhinderung von "&Uuml;berschwingern"</td>
-
-      <td>check_parameters, diffusion_e, diffusion_pt, diffusivities,
+<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
+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
+<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,
+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.
+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
+(..) 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
+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,
+<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
+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
+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
+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,
+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
+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
+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
+<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 =
+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
@@ -764,16 +318,16 @@
 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.
+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
+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
@@ -782,7 +336,5 @@
 h&ouml;heren
 geostrophischen Windgeschwindigkeiten unterdr&uuml;ckt.&nbsp; </p>
-
-      
-      <p>3D-Feldvariablen (u, v, w, pt, e, km, kh) sowie einige
+<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
@@ -792,94 +344,56 @@
 3 Zeitebenen existieren die Targets ..._1 (z.B. u_1), ..._2, ..._3).
 Durch
-die jeweilige Neuzuordnung der Targets entf&auml;llt das Umspeichern
+die jeweilige Neuzuordnung der Targets entf&auml;llt das
+Umspeichern
 der
-Zeitebenen komplett (Zeitersparung: ca. 5% der Gesamtrechenzeit).&nbsp;
-      <br>
-
+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
+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 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
+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.
+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>".
+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,
+</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
+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
+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>
-
+<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 -
+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
@@ -887,8 +401,6 @@
 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
+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;
@@ -898,348 +410,143 @@
 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
+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,
+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
+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
+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,
+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
+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
+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">:
+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">:
+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">:
+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
+<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>
-
+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,
+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
+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
+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
+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
+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
+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
+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
+<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
+<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
+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
+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
@@ -1247,14 +554,11 @@
 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
+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,
+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,
@@ -1262,320 +566,159 @@
 asselin_filter,
 swap_timelevels, flow_statistics, plot_2d, plot_3d, write_var_list,
-write_3d_binary&nbsp;
-      
-      <p><b>Neu:</b> <br>
-
+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
+</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
+&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
+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
+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
+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
+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>),
+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,
+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
+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;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,
+<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
+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
+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 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,
+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
+&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;
+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
+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,
+<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
+</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
+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
+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,
+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
+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
+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
+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,
+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
+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.
+<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
@@ -1583,157 +726,66 @@
 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,
+<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,
+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>
+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
+(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>
-
+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
+<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,
+<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>
+<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
+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,
+<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,
@@ -1741,39 +793,14 @@
 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.
+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.
+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
@@ -1783,60 +810,55 @@
 eine Reihe von &Uuml;bergabeparametern gestrichen werden (z.B. beim
 Aufruf
-von <tt>pres, advec_s_bc, poisfft, production_e, sor </tt>sowie den
+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
+(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
+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
+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>
+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
+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>
+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
+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
+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
+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,
+(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,
@@ -1847,33 +869,13 @@
 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
+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
@@ -1881,91 +883,49 @@
 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.
+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,
+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,
+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
+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
+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
+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
+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
+sind (gem&auml;&szlig; <tt>use_surface_fluxes</tt>,
+- bisher wurde
 dies
 nur bei eingeschalteter Prandtl-Schicht gemacht). Schubspannungen
@@ -1973,25 +933,21 @@
 jetzt als Randbedingungen vorgegeben werden (allerdings unter
 zuhilfenahme
-benutzereigener Software).&nbsp; </p>
-
-      
-      <p>Zus&auml;tzliche Schnittstellen f&uuml;r benutzereigene
+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
+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
+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,
+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,
@@ -2000,55 +956,20 @@
 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
+</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
+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
+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
@@ -2056,84 +977,51 @@
 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
+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
+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
+<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
+Partikeldaten k&ouml;nnen f&uuml;r sp&auml;tere Analysen
+auf Datei
 geschrieben
-werden (Unit 85). <tt>PARTICLE</tt>-Datentyp enth&auml;lt
+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
+&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
+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
+Umspeichern anstatt durch&nbsp; <tt>sendrecv </tt>realisiert.
+Ebenso
 werden
-die Transponierungen xz, yz, zx&nbsp; und zy eingespart (es wird aber
+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
+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
+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,
+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,
@@ -2141,110 +1029,52 @@
 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
+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
+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
+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
+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
+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,
+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
+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
@@ -2252,10 +1082,14 @@
 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
+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
+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
+Versionen funktionieren (d.h. in ihnen laufen die Schleifen
+&uuml;ber
 alle
 3 Dimensionen). Solche Teile der prognostischen Gleichungen, die
@@ -2265,8 +1099,6 @@
 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
+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
@@ -2279,41 +1111,38 @@
 dieser
 1D-Zerlegung durch einfache zyklische Randbedingungen ersetzt. </p>
-
-      
-      <p><b>Kleinere Anpassungen:</b> String-Vergleiche erfordern beim
+<p><b>Kleinere Anpassungen:</b> String-Vergleiche
+erfordern beim
 IBM-Compiler
-in der Regel den Einsatz der TRIM-Funktion, um &uuml;bersch&uuml;ssige
+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).
+(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
+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
+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
+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
+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
+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,
+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,
@@ -2327,93 +1156,40 @@
 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
+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
+<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
+&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
+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
+parameters <tt>restart_time</tt> and <tt>dt_restart</tt>.
+Run
 description
 header is written on file CONTINUE_RUN. Output of cpu statistics
@@ -2423,40 +1199,11 @@
 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,
+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
+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
@@ -2466,20 +1213,16 @@
 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>
-
+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
+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
@@ -2489,75 +1232,40 @@
 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
+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
+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
+<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,
+</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)).
+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
+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
+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,
+<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,
@@ -2565,110 +1273,46 @@
 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
+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
+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
+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>
+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
+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
+Additionally, a new pressure solver <tt>poisfft_hybrid_vec</tt>
+is
 added,
 which requires a 1d-domain-decomposition (like poisfft_hybrid). In this
@@ -2676,29 +1320,18 @@
 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>
+</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
+<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
+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,
+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,
@@ -2710,195 +1343,69 @@
 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
+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
+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
+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,
+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
+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
+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
+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,
+<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>
+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>
+(<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
+<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
+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
+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
@@ -2906,5 +1413,6 @@
 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
+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
@@ -2912,357 +1420,156 @@
 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
+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.
+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,
+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>,
+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
+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
+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
+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,
+<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>
+<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>
+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,
+</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
+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
+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,
+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
+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
+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
+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
+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
+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>.
+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
+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
+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
+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
+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>
-
+<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,
+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
+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
+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
+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
+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
+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
@@ -3270,15 +1577,12 @@
 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
+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
+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,
+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,
@@ -3289,87 +1593,25 @@
 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
+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>
-
+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
+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
+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.
@@ -3379,28 +1621,28 @@
 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
+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
+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
+(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
+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>
-
+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;">
@@ -3408,156 +1650,55 @@
 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
+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>
-
+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,
+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>
-
+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,
+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>
-
+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_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
+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>
-
+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>
-
+<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
+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
@@ -3565,28 +1706,28 @@
 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
+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>).
+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>
-
+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,
+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,
@@ -3595,604 +1736,239 @@
 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
+</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>
-
+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,
+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>
-
+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>
-
+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:
+<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>
-
+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
+</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>
-
+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>
-
+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
+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>
-
+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
+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>
-
+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>
-
+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,
+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>
-
+</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>
-
+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,
+</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
+<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>
-
+<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
+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
+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>
-
-
+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
+<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,
+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
+</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>
-
+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
+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
+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
+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>
+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
@@ -4202,28 +1978,58 @@
 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
+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
+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
+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
+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
+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,
+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,
@@ -4235,17 +2041,18 @@
 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>
+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_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
+</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
@@ -4253,13 +2060,23 @@
 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>
+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>
+<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>
@@ -4275,5 +2092,6 @@
 </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 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>
@@ -4292,17 +2110,33 @@
 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
+</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 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
+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
@@ -4310,90 +2144,174 @@
 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-
+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
+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,
+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
+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>
-
+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;&nbsp;</td><td>&nbsp;&nbsp;</td><td>&nbsp;&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>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</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
+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;&nbsp;</td><td>&nbsp;&nbsp;</td><td>&nbsp;&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>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</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><tr><td style="vertical-align: top;">02/03/07</td><td style="vertical-align: top;">SR</td><td style="vertical-align: top;">3.1c</td><td style="vertical-align: top;">N</td><td style="vertical-align: top;">A heatflux can be prescribed at the top with new inipar parameters <span style="font-family: monospace;">top_heatflux</span> and <span style="font-family: monospace;">use_top_fluxes</span>. New 2d-arrays <span style="font-family: monospace;">qswst</span>, <span style="font-family: monospace;">qswst_m</span>, <span style="font-family: monospace;">tswst</span> and <span style="font-family: monospace;">tswst_m</span> are used to store this flux. Use of fluxes are controlled with new index variable <span style="font-family: monospace;">nzt_diff</span>. A Neumann boundary condition for temperature can be applied under these conditions.<br><br>Additionally, a Dirichlet condition for temperature can be used at the top.<br><br><span style="font-weight: bold;">Attention:</span> <br>
-
+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><tr><td style="vertical-align: top;">02/03/07</td><td style="vertical-align: top;">SR</td><td style="vertical-align: top;">3.1c</td><td style="vertical-align: top;">N</td><td style="vertical-align: top;">A heatflux can be prescribed at
+the top with new inipar parameters <span style="font-family: monospace;">top_heatflux</span>
+and <span style="font-family: monospace;">use_top_fluxes</span>.
+New 2d-arrays <span style="font-family: monospace;">qswst</span>,
+<span style="font-family: monospace;">qswst_m</span>,
+<span style="font-family: monospace;">tswst</span>
+and <span style="font-family: monospace;">tswst_m</span>
+are used to store this flux. Use of fluxes are controlled with new
+index variable <span style="font-family: monospace;">nzt_diff</span>.
+A Neumann boundary condition for temperature can be applied under these
+conditions.<br><br>Additionally, a Dirichlet condition for
+temperature can be used at the top.<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.</td><td style="vertical-align: top;">check_parameters,
 diffusion_s, flow_statistics, header, init_grid, init_3d_model,
 modules, parin, production_e, prognostic_equations, read_var_list,
-read_3d_binary, swap_timelevel, write_var_list, write_3d_binary</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">C</td><td style="vertical-align: top;">Prognostic equations for all scalars are now solved up to gridpoint <span style="font-family: monospace;">nzt</span> (formerly <span style="font-family: monospace;">nzt-1</span>). Boundary conditions for scalars at top adjusted respectively (now applied only at <span style="font-family: monospace;">nzt+1</span>).<br><br>The default top boundary condition for temperature has been renamed to <span style="font-style: italic;">'initial_gradient'</span>.<br><br>Calls of <span style="font-family: monospace;">dvrp_output_local</span>, which were commented out for a long time, are now activated for all streams.</td><td style="vertical-align: top;">advec_s_pw,
+read_3d_binary, swap_timelevel, write_var_list, write_3d_binary</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">C</td><td style="vertical-align: top;">Prognostic equations for all
+scalars are now solved up to gridpoint <span style="font-family: monospace;">nzt</span> (formerly <span style="font-family: monospace;">nzt-1</span>).
+Boundary conditions for scalars at top adjusted respectively (now
+applied only at <span style="font-family: monospace;">nzt+1</span>).<br><br>The
+default top boundary condition for temperature has been renamed to <span style="font-style: italic;">'initial_gradient'</span>.<br><br>Calls
+of <span style="font-family: monospace;">dvrp_output_local</span>,
+which were commented out for a long time, are now activated for all
+streams.</td><td style="vertical-align: top;">advec_s_pw,
 boundary_conds, calc_precipitation, check_parameters, diffusion_e,
 diffusion_s, impact_of_latent_heat, init_dvrp, init_pt_anomaly,
-modules, production_e, prognostic_equations, spline_z</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">E</td><td style="vertical-align: top;">Bugfix: 3d-array <span style="font-family: monospace;">p</span> is not a pointer any more.<br><br>Bugfix in <span style="font-family: monospace;">init_particles</span>: <span style="font-family: monospace;">MPI_REAL</span> argument in <span style="font-family: monospace;">MPI_ALLREDUCE</span> replaced by<br><span style="font-family: monospace;">MPI_INTEGER</span> (caused error on NEC only).<br><br>Bugfix:&nbsp; <span style="font-family: monospace;">ddzw</span> now dimensioned <span style="font-family: monospace;">1:nzt"+1".</span></td><td style="vertical-align: top;">diffusion_e, diffusion_s, diffusion_u, diffusion_v, diffusion_w, init_particles, modules</td></tr>
-
-  
-  </tbody>
-</table>
-
-&nbsp;<b><blink>Attention:</blink></b> If<tt> make </tt>is not used
+modules, production_e, prognostic_equations, spline_z</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">E</td><td style="vertical-align: top;">Bugfix: 3d-array <span style="font-family: monospace;">p</span> is not a
+pointer any more.<br><br>Bugfix in <span style="font-family: monospace;">init_particles</span>:
+<span style="font-family: monospace;">MPI_REAL</span>
+argument in <span style="font-family: monospace;">MPI_ALLREDUCE</span>
+replaced by<br><span style="font-family: monospace;">MPI_INTEGER</span>
+(caused error on NEC only).<br><br>Bugfix:&nbsp; <span style="font-family: monospace;">ddzw</span> now
+dimensioned <span style="font-family: monospace;">1:nzt"+1".</span></td><td style="vertical-align: top;">diffusion_e, diffusion_s,
+diffusion_u, diffusion_v, diffusion_w, init_particles, modules</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
+<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
+<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
+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
+<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
+</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,
+</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
+ver&auml;ndert werden. Neu geschaffene Variablen sollten
+w&auml;hrend
 der
 Testphase in ein ebenfalls tempor&auml;r neu zu schaffendes Modul
@@ -4403,12 +2321,13 @@
 entsprechender USE-Anweisungen). Die in den einzelnen Dateien
 durchgef&uuml;hrten
-Arbeiten m&uuml;ssen in den Kopfzeilen (unter "Aktuelle Aenderungen")
+Arbeiten m&uuml;ssen in den Kopfzeilen (unter "Aktuelle
+Aenderungen")
 der
-Dateien vermerkt werden. Dies tut man am besten noch <b>bevor</b> man
+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
+Vergessen...).</li> <li>Zum Abschlu&szlig; der Tests
+sollte mit dem Modell eine
 Kontrollrechnung
 durchgef&uuml;hrt und die Ergebnisse mit denen des sogenannten
@@ -4418,5 +2337,6 @@
 durchzuf&uuml;hren, die auch zum Testen der Modellinstallation
 verwendet
-werden (s. <a href="Anwendung/Kapitel_5.0.html">Kapitel 5.0</a> der
+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>
@@ -4430,27 +2350,31 @@
 so
 ist unbedingt eine Diskussion in der Modellarbeitsgruppe notwendig.</li>
-
-  <li>Nach Durchf&uuml;hrung der Tests m&uuml;ssen bei Bedarf die
+<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
+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
+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
+<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
+Bsp.: 2.3c. Kleinere &Auml;nderungen werden durch
+angeh&auml;ngten
 kleinen
-Buchstaben kenntlich gemacht, gr&ouml;&szlig;ere &Auml;nderungen durch
+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
+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
@@ -4462,22 +2386,19 @@
 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
+... $ - 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
+</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.
+<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
@@ -4488,55 +2409,28 @@
 Aufgaben (z.B. der Berechnung horizontal gemittelter
 Gr&ouml;&szlig;en).
-<br>
-
-Die Beschreibungen liegen in jeweils getrennten Dokumenten, in der
+<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>
-
+<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;
-</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;
+<br>&nbsp;
+<br>&nbsp;
+<br>&nbsp;
+<br>&nbsp;
+<br>&nbsp;
+<br>&nbsp;
+<br>&nbsp;
 </body></html>
