Home


About us
PALM
PALM-4U
Installation
Release notes
Documentation
Getting Help
Gallery
Developers area

Changeset 62 for palm/trunk/DOC


Ignore:
Timestamp:
Mar 13, 2007 2:52:40 AM (18 years ago)
Author:
raasch
Message:

Id string added to all html files

Location:
palm/trunk/DOC
Files:
31 edited

Legend:

Unmodified
Added
Removed

  • palm/trunk/DOC/app/chapter_1.0.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta content="text/html; charset=windows-1252"
    5  http-equiv="CONTENT-TYPE">
    6   <title>PALM chapter 1.0</title>
    7   <meta content="StarOffice 7  (Win32)" name="GENERATOR">
    8   <meta content="Marcus Oliver Letzel" name="AUTHOR">
    9   <meta content="20040719;13375546" name="CREATED">
    10   <meta content="20041112;13163393" name="CHANGED">
    11   <meta content="parallel LES model" name="KEYWORDS">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body lang="de-DE" dir="ltr">
    19 <h2 style="line-height: 100%;"><font size="4">1.0 Introduction</font></h2>
    20 <p style="line-height: 100%;">This documentation wants to give
     2<html><head>
     3<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>
     4<!--
     5@page { size: 21cm 29.7cm }
     6-->
     7</style></head>
     8
     9<body style="direction: ltr;" lang="de-DE"><h2 style="line-height: 100%;"><font size="4">1.0
     10Introduction</font></h2>
     11<p style="line-height: 100%;">This documentation wants to
     12give
    2113assistance how to carry out runs with the large eddy simulation
    22 model <span
    23  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">PALM.</span>
     14model <span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">PALM.</span>
    2415It contains
    2516<font color="#000000">instructions</font><font color="#800000"> </font>for
    2617the installation of the model (<a href="chapter_5.0.html">chapter
    27 5.0</a>), for the practical execution of application runs (<a
    28  href="chapter_3.0.html">chapter
    29 3.0</a>) and for the steering of the model by parameters (<a
    30  href="chapter_4.0.html">chapter
     185.0</a>), for the practical execution of application runs (<a href="chapter_3.0.html">chapter
     193.0</a>) and for the steering of the model by parameters (<a href="chapter_4.0.html">chapter
    31204.0</a>). New users should first of all read <a href="chapter_2.0.html">chapters
    32212.0</a> and <a href="chapter_3.0.html">3.0</a>
    3322(up to and including <a href="chapter_3.5.html">3.5</a>).
    3423</p>
    35 <p style="line-height: 100%;"><b>This documentation does not explain
    36 the <font color="#000000">mathematical,</font> numerical and physical
     24<p style="line-height: 100%;"><b>This documentation
     25does not explain
     26the <font color="#000000">mathematical,</font>
     27numerical and physical
    3728background of large eddy simulation models and it also does not
    3829provide appropriate meteorological background knowledge. Good
    3930knowledge concerning this is presupposed and is indispensable for a
    4031successful application of the model.</b> In addition to this,
    41 knowledge of the operating system<span
    42  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
    43 Unix, </span>the <span
    44  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">Queueing
    45 System (NQS, PBS, Load Leveler, etc.)</span> to generate batch jobs,
    46 the basic functionality of <font color="#000000">parallel computers
    47 </font>and the programming language <span
    48  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">FORTRAN90
     32knowledge 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;">
     33Unix, </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
     34System (NQS, PBS, Load Leveler, etc.)</span> to generate batch
     35jobs,
     36the basic functionality of <font color="#000000">parallel
     37computers
     38</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
    4939(particularly</span>, if code extensions are to be written by the
    5040user) are presupposed. Programming user-defined software usually
    5141requires exact knowledge of the internal model structure. First insight
    52 herei<span
    53  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">n
     42herei<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">n
    5443<font color="#000000">is
    5544given</font></span> in <a href="chapter_2.0.html">chapter
    56452.0</a> and in the <a href="../tec/index.html">technical/numerical
    5746documentation</a>. The information obtained there is usually not
    58 <font color="#000000">sufficient</font> and has to be accompanied by
    59 detailed study of the source code of the model. A<span
    60  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">dditional
     47<font color="#000000">sufficient</font> and has to
     48be accompanied by
     49detailed 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
    6150</span>experience in parallel programming with the
    62 message passing interface<span
    63  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
     51message passing interface<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">
    6452(MPI)</span> maybe presupposed. </p>
    65 <p style="line-height: 100%;">A documentation lives on criticism and
    66 suggestions by users. T<font color="#000000">hi</font>s is expressly
     53<p style="line-height: 100%;">A documentation lives on
     54criticism and
     55suggestions by users. T<font color="#000000">hi</font>s
     56is expressly
    6757requested. Please contact&nbsp; the PALM group
    68 (<span
    69  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">see
    70 <a
    71  href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">members</a></span>).
     58(<span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">see
     59<a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">members</a></span>).
    7260The model documentation is regularly maintained and brought up-to-date
    7361by the PALM group. The date of the last code
    … …  
    7563documentation. <br>
    7664&nbsp;
    77 </p>
    78 <hr><font color="#000080"><font color="#000080"><br>
    79 <a href="index.html"><font color="#000080"><img width="32" height="32"
    80  border="2" align="bottom" name="Grafik1" src="up.gif"></font></a><a
    81  href="chapter_2.0.html"><font color="#000080"><img width="32"
    82  height="32" border="2" align="bottom" name="Grafik2" src="right.gif"></font></a></font></font><br>
    83 <br>
    84 <span style="font-style: italic;">Last change:</span> 14/04/05 (SR)<br>
    85 <br>
    86 </body>
    87 </html>
     65</p><hr><font color="#000080"><font color="#000080"><br>
     66<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>
     67<span style="font-style: italic;">Last change:</span>
     68$Id$<br>
     69<br></body></html>

  • palm/trunk/DOC/app/chapter_2.0.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta content="text/html; charset=windows-1252"
    5  http-equiv="CONTENT-TYPE">
    6   <title>PALM chapter 2.0</title>
    7   <meta content="StarOffice 7  (Win32)" name="GENERATOR">
    8   <meta content="Marcus Oliver Letzel" name="AUTHOR">
    9   <meta content="20040719;14534028" name="CREATED">
    10   <meta content="20041117;10385730" name="CHANGED">
    11   <meta content="parallel LES model" name="KEYWORDS">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body lang="en-US" dir="ltr">
    19 <h2 style="line-height: 100%;"><font size="4">2.0 Basic techniques of
     2<html><head>
     3<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>
     4<!--
     5@page { size: 21cm 29.7cm }
     6-->
     7</style></head>
     8
     9<body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">2.0
     10Basic techniques of
    2011the LES model and its parallelization </font>
    21 </h2>
    22 <p style="line-height: 100%;">LES models generally permit the
     12</h2><p style="line-height: 100%;">LES models
     13generally permit the
    2314simulation of turbulent flows, whereby those eddies, that carry the
    2415main energy are resolved by the numerical grid. Only the
    … …  
    2819simulated directly (they are explicitly resolved) and their effects are
    2920represented by the advection terms. </p>
    30 <p style="font-style: normal; line-height: 100%;">PALM is based on the
     21<p style="font-style: normal; line-height: 100%;">PALM is
     22based on the
    3123non-hydrostatic incompressible Boussinesq equations. It contains a
    3224water cycle with cloud formation and takes into account infrared
    3325radiative cooling in cloudy conditions. The model has six prognostic
    34 quantities in total – u,v,w, liquid water potential temperature
    35 <font face="Thorndale, serif">&#920;</font><sub>l </sub>(BETTS,
     26quantities in total &ndash; u,v,w, liquid water potential
     27temperature
     28<font face="Thorndale, serif">&Theta;</font><sub>l
     29</sub>(BETTS,
    36301973), total water content q and subgrid-scale turbulent kinetic energy
    3731e. The
    … …  
    45391993). The water cycle is closed by using a simplified version of
    4640KESSLERs scheme (KESSLER, 1965; 1969) to parameterize precipitation
    47 processes (MÜLLER and CHLOND, 1996). Incompressibility is
     41processes (M&Uuml;LLER and CHLOND, 1996). Incompressibility is
    4842applied by means of a Poisson equation for pressure, which is solved
    4943with a direct method (SCHUMANN and SWEET, 1988). The Poisson equation
    … …  
    5852horizontal directions. At the lower surface, either temperature/
    5953humidity or their respective fluxes can be prescribed. </p>
    60 <p style="font-style: normal; line-height: 100%;">The advection terms
     54<p style="font-style: normal; line-height: 100%;">The
     55advection terms
    6156are treated by the scheme proposed by PIACSEK and WILLIAMS (1970),
    6257which conserves the integral of linear and quadratic quantities up to
    … …  
    6661with the third-order Runge-Kutta scheme. A second-order Runge-Kutta
    6762scheme, a leapfrog scheme and an Euler scheme are also implemented.</p>
    68 <p style="line-height: 100%;">By default, the time step is computed
     63<p style="line-height: 100%;">By default, the time step is
     64computed
    6965with respect to the different criteria (CFL, diffusion) and adapted
    7066automatically. In case of a non-zero geostrophic
    7167wind the coordinate system can be moved along with the mean wind in
    7268order to maximize the time step (Galilei-Transformation). </p>
    73 <p style="font-style: normal; line-height: 100%;">In principle a model
     69<p style="font-style: normal; line-height: 100%;">In
     70principle a model
    7471run is carried out in the following way: After reading the control
    7572parameters given by the user, all prognostic variables are
    … …  
    9087corrected with the help of the pressure solver. Following this, all
    9188diagnostic turbulence quantities including possible
    92 Prandtl-layer–quantities are computed. At the end of a time
     89Prandtl-layer&ndash;quantities are computed. At the end of a time
    9390step the data output requested by the user is made
    9491(e.g. statistic of analyses for control purposes or profiles and/or
    9592graphics data). If the given end-time was reached, binary data maybe
    9693be saved for restart. </p>
    97 <p style="font-style: normal; line-height: 100%;">The model is based
     94<p style="font-style: normal; line-height: 100%;">The
     95model is based
    9896on the originally non-parallel LES model which has been operated at the
    9997institute since 1989
    … …  
    109107Users can choose between a two- and a one-dimensional domain
    110108decomposition. A 1D-decomposition is preferred on machines with a
    111 slow&nbsp; network interconnection. In case of a 1D-decomposition, the
     109slow&nbsp; network interconnection. In case of a 1D-decomposition,
     110the
    112111grid points along x direction are
    113112distributed among the individual processors, but in y- and z-direction
    114113all respective grid points belong to the same PE. </p>
    115 <p style="line-height: 100%;">The calculation of central differences or
     114<p style="line-height: 100%;">The calculation of central
     115differences or
    116116non-local arithmetic operations (e.g. global
    117117sums, FFT) demands communication and an appropriate data exchange
    … …  
    126126y-direction, the data which lie distributed on the individual central
    127127processing elements, have to be collected and/or relocated before.
    128 This happens by means of the routine <tt>MPI_ALLTOALLV</tt>. Certain
     128This happens by means of the routine <tt>MPI_ALLTOALLV</tt>.
     129Certain
    129130global operations like e.g. the search for absolute maxima or minima
    130131within the 3D-arrays likewise require the employment of special MPI
    131132routines (<tt>MPI_ALLREDUCE</tt>). </p>
    132 <p style="line-height: 100%;">Further details of the internal model
     133<p style="line-height: 100%;">Further details of the
     134internal model
    133135structure are described in the <a href="../tec/index.html">technical/numerical
    134136documentation</a>. <br>
    135137&nbsp; </p>
    136 <hr><font color="#000080"><font color="#000080"><br>
    137 <a href="chapter_1.0.html"><font color="#000080"><img width="32"
    138  height="32" border="2" align="bottom" name="Grafik1" src="left.gif"></font></a><a
    139  href="index.html"><font color="#000080"><img width="32" height="32"
    140  border="2" align="bottom" name="Grafik2" src="up.gif"></font></a><a
    141  href="chapter_3.0.html"><font color="#000080"><img width="32"
    142  height="32" border="2" align="bottom" name="Grafik3" src="right.gif"></font></a><br>
    143 </font></font><br>
    144 <p style="line-height: 100%;"><span style="font-style: italic;">Last
    145 change: </span>14/04/05 (SR)<font color="#000080"><font color="#000080"><br>
    146 </font></font></p>
    147 </body>
    148 </html>
     138<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>
     139</font></font><br><p style="line-height: 100%;"><span style="font-style: italic;">Last
     140change: </span>$Id$<font color="#000080"><font color="#000080"><br>
     141</font></font></p></body></html>

  • palm/trunk/DOC/app/chapter_3.0.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 3.0</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Marcus Oliver Letzel">
    9   <meta name="CREATED" content="20040723;15213734">
    10   <meta name="CHANGED" content="20041112;13170538">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h2 style="font-style: normal; line-height: 100%;"><font size="4">3.0
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h2 style="font-style: normal; line-height: 100%;"><font size="4">3.0
    2011Execution of model runs</font></h2>
    2112<p style="line-height: 100%;">Given that the model was
    2213installed by the user (look at <a href="chapter_5.0.html">chapter
    23 5.0</a>) and that it is clear, which phenomenon is to be simulated,
     145.0</a>) and that it is clear, which phenomenon is to be
     15simulated,
    2416there is a whole set of questions which must be answered before
    2517executing
    2618the actual application run, e.g.: </p>
    27 <ul>
    28   <li>
    29     <p
    30  style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
     19<ul> <li> <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
    3120large does the model domain have to be and what grid size does
    32 phenomenon to be simulated require? </p>
    33   </li>
    34   <li>
    35     <p
    36  style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
     21phenomenon to be simulated require? </p> </li> <li>
     22<p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">How
    3723long is the time which should be simulated, i.e. which typical time
    38 scale does the phenomenon have? </p>
    39   </li>
    40   <li>
    41     <p
    42  style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">Which
     24scale does the phenomenon have? </p> </li> <li> <p style="margin-bottom: 0cm; font-style: normal; line-height: 100%;">Which
    4325boundary conditions and initial conditions are to be selected? </p>
    44   </li>
    45   <li>
    46     <p style="font-style: normal; line-height: 100%;">Which model
     26</li> <li> <p style="font-style: normal; line-height: 100%;">Which model
    4727output data are necessary at which points in time, in order to be able
    48 to analyze the phenomenon afterwards? </p>
    49   </li>
    50 </ul>
    51 <p style="line-height: 100%;">The answers to these questions
     28to analyze the phenomenon afterwards? </p> </li>
     29</ul><p style="line-height: 100%;">The answers to
     30these questions
    5231substantially determine the choice of values for the most important
    5332model parameters, with which the model run is steered. All possible
    … …  
    5736The basic steering of the model with these parameters is explained in
    5837the introduction to <a href="chapter_4.0.html">chapter
    59 4</a>. The user will rarely use all model parameters, since many are
     384</a>. The user will rarely use all model parameters, since many
     39are
    6040preset with consistent default values and therefore do not have to be
    6141changed by the user. Some of the most important parameters are not
    6242preset with default values and must be adjusted by the user in each
    63 case. Such a typical, minimum parameter set is described in <a
    64  href="chapter_4.4.html">chapter
     43case. Such a typical, minimum parameter set is described in <a href="chapter_4.4.html">chapter
    65444.4</a>. For the subsequent analysis of model runs, graphical
    66 visualization of model data is particularly important. <a
    67  href="chapter_4.5.html">Chapter
     45visualization of model data is particularly important. <a href="chapter_4.5.html">Chapter
    68464.5</a> describes, how such outputs are produced with the model. </p>
    69 <p style="line-height: 100%;">The selected parameters and their values
     47<p style="line-height: 100%;">The selected parameters and
     48their values
    7049have to be supplied to the model as an input file. The
    71 structure of this file is described in the introduction to <a
    72  href="chapter_4.0.html">chapter
    73 4</a>. The data, produced by the model, are located in a number of
     50structure of this file is described in the introduction to <a href="chapter_4.0.html">chapter
     514</a>. The data, produced by the model, are located in a number
     52of
    7453different output files. The model works with relative file names
    7554(i.e. without absolute path information). Thus all input and output
    … …  
    7857executable program created from the FORTRAN source code) is started
    7958(but also see next paragraph).
    80 All user-relevant input and output files are described in <a
    81  href="chapter_3.4.html">chapter
     59All user-relevant input and output files are described in <a href="chapter_3.4.html">chapter
    82603.4</a>. </p>
    83 <p style="line-height: 100%;">The actual model (the executable
     61<p style="line-height: 100%;">The actual model (the
     62executable
    8463program) is not started directly via the user, but with the help of
    85 the shell script <a
    86  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>,which
     64the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>,which
    8765can be called by the user. This script takes over the entire pre- and
    8866postprocessing work, which is necessary for a model run. In addition
    … …  
    9169input and output files to these computers, secures data on existing
    9270archives systems, starts if necessary restart jobs, and much more.
    93 <span style="font-weight: bold;">mrun</span> allows to specify
     71<span style="font-weight: bold;">mrun</span> allows
     72to specify
    9473individual path names for each simulation and
    9574for the different types of input/output files. The start of model runs
    9675with <b>mrun</b> is described in <a href="chapter_3.1.html">chapter
    97763.1</a>. </p>
    98 <p style="line-height: 100%;">The implementation of user code
     77<p style="line-height: 100%;">The implementation of user
     78code
    9979extensions in
    10080the model is made possible by a set of defined interfaces. You will
    101 find references to the programming of such extensions in <a
    102  href="chapter_3.5.html">chapter
    103 3.5</a>. Frequently errors arise during the execution of the model
     81find references to the programming of such extensions in <a href="chapter_3.5.html">chapter
     823.5</a>. Frequently errors arise during the execution of the
     83model
    10484after such changes, which can often be found only by interactive
    10585model steering and error tracing (debugging), which are described in
    10686<a href="chapter_3.6.html">chapter
    107873.6</a>. </p>
    108 <hr>
    109 <p style="font-style: normal; line-height: 100%;"><br>
    110 <font color="#000080"><font color="#000080"><a href="chapter_2.0.html"><font
    111  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    112  border="2" height="32" width="32"></font></a><a href="index.html"><font
    113  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    114  border="2" height="32" width="32"></font></a><a href="chapter_3.1.html"><font
    115  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    116  border="2" height="32" width="32"></font></a></font></font>
    117 <br>
    118 </p>
    119 <p style="font-style: normal; line-height: 100%;"><span
    120  style="font-style: italic;">Last change:</span> 14/04/05 (SR)<br>
    121 </p>
    122 </body>
    123 </html>
     88<hr><p style="font-style: normal; line-height: 100%;"><br>
     89<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>
     90</p><p style="font-style: normal; line-height: 100%;"><span style="font-style: italic;">Last change:</span>
     91$Id$<br>
     92</p></body></html>

  • palm/trunk/DOC/app/chapter_3.1.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 3.1</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Marcus Oliver Letzel">
    9   <meta name="CREATED" content="20040806;13565279">
    10   <meta name="CHANGED" content="20040806;13575492">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12 </head>
    13 <body dir="ltr" lang="de-DE">
    14 <h3 style="line-height: 100%;">3.1 Job control with mrun</h3>
    15 <p style="line-height: 100%;">The start of model runs in principle
    16 takes place via executing the shell script <a
    17  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun.</a>
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5
     6<body style="direction: ltr;" lang="de-DE"><h3 style="line-height: 100%;">3.1 Job control with mrun</h3>
     7<p style="line-height: 100%;">The start of model runs in
     8principle
     9takes place via executing the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun.</a>
    1810With this script it is possible to operate the model both
    1911interactively and in batch mode. Batch operation is possible on the
    … …  
    2315described, because this represents the usual mode of operation due to
    2416the large computing time requirements of the model. The interactive
    25 execution differs only in some points and is described in <a
    26  href="chapter_3.6.html">chapter
     17execution differs only in some points and is described in <a href="chapter_3.6.html">chapter
    27183.6</a>. </p>
    28 <p style="line-height: 100%;">By the call of <b>mrun </b>a complete
     19<p style="line-height: 100%;">By the call of <b>mrun
     20</b>a complete
    2921batch job is produced, transferred to the user determined remote
    3022computer
    … …  
    3224After processing of the job, the so-called job protocol is sent back
    3325to the local computer of the user (the local computer is the
    34 computer, on which the user calls <b>mrun</b>). The following actions
     26computer, on which the user calls <b>mrun</b>). The
     27following actions
    3528are implemented by the job, amongst other: </p>
    36 <ul>
    37   <li>
    38     <p style="margin-bottom: 0cm; line-height: 100%;">Change to a
    39 temporary working directory. </p>
    40   </li>
    41   <li>
    42     <p style="margin-bottom: 0cm; line-height: 100%;">The input files
     29<ul> <li> <p style="margin-bottom: 0cm; line-height: 100%;">Change to a
     30temporary working directory. </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The input
     31files
    4332needed by the model are copied into this directory. These files are
    44 transferred from the local computer. </p>
    45   </li>
    46   <li>
    47     <p style="margin-bottom: 0cm; line-height: 100%;">Execute the
    48 model. </p>
    49   </li>
    50   <li>
    51     <p style="margin-bottom: 0cm; line-height: 100%;">Copy the output
     33transferred from the local computer. </p> </li> <li>
     34<p style="margin-bottom: 0cm; line-height: 100%;">Execute
     35the
     36model. </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">Copy the
     37output
    5238files produced by the model into the directories determined by the user
    5339(these are also allowed to lie on the local computer). Depending on the
    5440choice of the user, the files may also be saved on an archiving system
    55 (if existing). </p>
    56   </li>
    57   <li>
    58     <p style="margin-bottom: 0cm; line-height: 100%;">Delete the
    59 temporary working direction. </p>
    60   </li>
    61   <li>
    62     <p style="line-height: 100%;">Transfer the job protocol to the
    63 local computer. </p>
    64   </li>
    65 </ul>
    66 <p style="line-height: 100%;">From this list it becomes clear that two
    67 of the substantial functions of <b>mrun</b> are the supply of input
     41(if existing). </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">Delete the
     42temporary working direction. </p> </li> <li> <p style="line-height: 100%;">Transfer the job protocol to the
     43local computer. </p> </li>
     44</ul><p style="line-height: 100%;">From this list it
     45becomes clear that two
     46of the substantial functions of <b>mrun</b> are the supply
     47of input
    6848files for the model and the storage of output files produced by the
    6949model. The model exclusively works with so-called local files, which
    70 lie in the temporary working directory created by <b>mrun.</b> The
    71 “local” names of these files are determined by the model
     50lie in the temporary working directory created by <b>mrun.</b>
     51The
     52&ldquo;local&rdquo; names of these files are determined by the
     53model
    7254(in the appropriate OPEN instructions). In <a href="chapter_3.4.html">chapter
    73553.4</a> all possible input and output filenames are specified. In
    … …  
    7759stored there. The directory names are arbitrary. The actual file name
    7860(without path) of these input and output files is specified by an
    79 option of <b>mrun</b>. All input and output files of the model
    80 receive this file name (e.g. <i>abcde</i>), but each individual file
    81 is still provided with an extension (e.g. <i>abcde_par</i>, etc.
    82 <i>abcde_dat</i>) - otherwise the files would not be distinguishable.
     61option of <b>mrun</b>. All input and output files of the
     62model
     63receive this file name (e.g. <i>abcde</i>), but each
     64individual file
     65is still provided with an extension (e.g. <i>abcde_par</i>,
     66etc.
     67<i>abcde_dat</i>) - otherwise the files would not be
     68distinguishable.
    8369The linkage of local file names with the names of the permanent
    8470directories and the file name extensions takes place in a
    85 configuration file, which <b>mrun</b> expects to find in the
     71configuration file, which <b>mrun</b> expects to find in
     72the
    8673respective current working directory of the user. A detailed
    8774description of this configuration file - which still offers a variety
    88 of further functions – is found in the
    89 documentation of the shell script <a
    90  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>
     75of further functions &ndash; is found in the
     76documentation of the shell script <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>
    9177(sorry: this is only available in German, so far. If you think that you
    9278would profit from an English version, please give a message to the PALM
    … …  
    9480In the next chapter a simple example of a minimum configuration file
    9581is described. </p>
    96 <p style="line-height: 100%;">A simple call of <b>mrun</b> could read
     82<p style="line-height: 100%;">A simple call of <b>mrun</b>
     83could read
    9784as follows: </p>
    98 <ul>
    99   <p style="line-height: 100%;"><tt>mrun - h <i>ibmh</i> -d <i>abcde</i></tt></p>
    100 </ul>
    101 <p style="line-height: 100%;">The model is started by option -<tt>h
    102 <i>ibmh</i></tt> on the IBM Regatta hanni at the HLRN, i.e. on the
     85<ul> <p style="line-height: 100%;"><tt>mrun -
     86h <i>ibmh</i> -d <i>abcde</i></tt></p>
     87</ul><p style="line-height: 100%;">The model is
     88started by option -<tt>h
     89<i>ibmh</i></tt> on the IBM Regatta hanni at the
     90HLRN, i.e. on the
    10391local computer a batch job is generated, transferred to the remote
    10492computer (IBM) and submitted to a suitable queue of the queuing system.
    10593With the
    106 option <tt>-d</tt> the so-called basis file name (<i>abcde</i>) is
     94option <tt>-d</tt> the so-called basis file name (<i>abcde</i>)
     95is
    10796specified, from which, together with the path names and file name
    10897extensions, the complete file names (including the path) of the
    109 permanent input and output files are <font color="#000000">formed.</font><font
    110  color="#800000">
     98permanent input and output files are <font color="#000000">formed.</font><font color="#800000">
    11199</font>Usually the specification of a set of further options is
    112100necessary, e.g. the CPU time needed by the model and the memory size
    113101needed as well as, on parallel computers, the number of processing
    114 elements which are to be used (options <tt>-t</tt>, <tt>-m</tt> and
    115 <tt>-X</tt>). A precondition for the call of <b>mrun</b> of course is
     102elements which are to be used (options <tt>-t</tt>, <tt>-m</tt>
     103and
     104<tt>-X</tt>). A precondition for the call of <b>mrun</b>
     105of course is
    116106that the installation of the model on the local computer and the
    117107remote machine is complete (see <a href="chapter_5.0.html">chapter
    1181085.0</a>). </p>
    119109<p>Beyond these options a variety of further options for model
    120 steering can be used in the call of <b>mrun</b>. These are fully
    121 described in the <a
    122  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>
     110steering can be used in the call of <b>mrun</b>. These are
     111fully
     112described in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html">mrun</a>
    123113documentation (in German). <br>
    124114&nbsp; </p>
    125 <hr>
    126 <p><a href="chapter_3.0.html"><font color="#000080"><img src="left.gif"
    127  name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a
    128  href="index.html"><font color="#000080"><img src="up.gif"
    129  name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a
    130  href="chapter_3.2.html"><font color="#000080"><img src="right.gif"
    131  name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></p>
    132 <p><i>Last change:&nbsp;</i> 14/04/05 (SR)</p>
    133 </body>
    134 </html>
     115<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>
     116<p><i>Last change:&nbsp;</i>$Id$</p>
     117</body></html>

  • palm/trunk/DOC/app/chapter_3.2.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 3.2</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Marcus Oliver Letzel">
    9   <meta name="CREATED" content="20040726;13164873">
    10   <meta name="CHANGED" content="20050119;9245042">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h3 style="line-height: 100%;">3.2 Example of a minimum configuration
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.2 Example of a minimum
     11configuration
    2012file</h3>
    21 <p style="line-height: 100%;">In this chapter a sample configuration
     13<p style="line-height: 100%;">In this chapter a sample
     14configuration
    2215file is described. It contains only instructions which are really
    2316necessary for the execution of a simple model run (configuration
    2417files can be much more complex). The example presented here is stored
    25 in an appropriate <a
    26  href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">example
    27 file</a> (containing more than the configuration data presented here)
    28 and can be used, together with the <a
    29  href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">parameter
     18in an appropriate <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/.mrun.config">example
     19file</a> (containing more than the configuration data presented
     20here)
     21and can be used, together with the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">parameter
    3022file</a> presented in <a href="chapter_4.4.html">chapter
    31 4.4</a>, for the execution of a simple model run. In chapter 4.4 the
    32 complete <b>mrun</b> options which are necessary for the appropriate
     234.4</a>, for the execution of a simple model run. In chapter 4.4
     24the
     25complete <b>mrun</b> options which are necessary for the
     26appropriate
    3327parameter file are described. Furthermore not all details of the
    3428configuration file are described here. Therefore you should take a
    35 look at the <a
    36  href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a>
     29look at the <a href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a>
    3730documentation (sorry: this is only available in German, so far. If you
    3831think that you
    3932would profit from an English version, please give a message to the PALM
    4033group). </p>
    41 <p style="line-height: 100%;">The following configuration data
     34<p style="line-height: 100%;">The following configuration
     35data
    4236exclusively applies to model runs on the IBM Regatta hanni of the
    4337HLRN when using several processing elements (i.e. for the parallel
    4438version of the model). The proper installation of the model is
    4539presumed (see <a href="chapter_5.0.html">chapter
    46 5.0</a>). Furthermore it is supposed that the user is located in the
     405.0</a>). Furthermore it is supposed that the user is located in
     41the
    4742directory <tt><font style="font-size: 10pt;" size="2">$HOME/palm/current_version/SOURCE</font></tt>
    4843on its local computer. There are the FORTRAN source codes of the
    4944model (<tt><font style="font-size: 10pt;" size="2">*.f90</font></tt>)
    5045as
    51 well as the configuration file (name: <tt><font
    52  style="font-size: 10pt;" size="2">.mrun.config</font></tt>)
     46well as the configuration file (name: <tt><font style="font-size: 10pt;" size="2">.mrun.config</font></tt>)
    5347and the make file (name: <tt><font style="font-size: 10pt;" size="2">Makefile</font></tt>).
    5448The configuration file has the following contents (among other things):
    55 <br>
    56 &nbsp;
    57 </p>
    58 <pre style="line-height: 100%;"><font style="font-size: 10pt;" size="2">% source_path  <i>$HOME/palm/current_version/SOURCE</i></font><br><font
    59  style="font-size: 10pt;" size="2">% mainprog     <i>palm.f90</i></font><br><font
    60  style="font-size: 10pt;" size="2">% use_makefile <i>true</i></font><br><font
    61  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
    62  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
    63  style="font-size: 10pt;" size="2">% lopts        <span
    64  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
    65  style="font-size: 10pt;" size="2">#</font><br><font
    66  style="font-size: 10pt;" size="2">EC:[[ \$locat = execution]] &amp; &amp; <i>cat </i>RUN_CONTROL </font><br><font
    67  style="font-size: 10pt;" size="2">#</font><br><a
    68  href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font
    69  style="font-size: 10pt;" size="2">        in:job:npe d3#   ~/palm/current_version/JOBS/$fname/INPUT      _p3d</font><br><font
    70  style="font-size: 10pt;" size="2">#</font><br><a
    71  href="chapter_3.4.html#RUN_CONTROL"><font style="font-size: 10pt;"
    72  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
    73  href="chapter_3.4.html#HEADER"><font style="font-size: 10pt;" size="2">HEADER</font></a><font
    74  style="font-size: 10pt;" size="2">       out:loc:tr d3#   ~/palm/current_version/JOBS/$fname/MONITORING _header</font><br><a
    75  href="chapter_3.4.html#PLOT1D_PAR"><font style="font-size: 10pt;"
    76  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
    77  href="chapter_3.4.html#PLOT1D_DATA"><font style="font-size: 10pt;"
    78  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>
     49<br>&nbsp;
     50</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>
    7951<p style="line-height: 100%;"><font face="Thorndale, serif">The first
    8052five lines specify values of
    81 so-called environment variables. Such lines begin with a “%”-
    82 sign. After at least one blank the name of the variable</font> <font
    83  face="Thorndale, serif">(e.g.
    84 </font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font
    85  face="Thorndale, serif">)
     53so-called environment variables. Such lines begin with a
     54&ldquo;%&rdquo;-
     55sign. After at least one blank the name of the variable</font> <font face="Thorndale, serif">(e.g.
     56</font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font face="Thorndale, serif">)
    8657follows and then seperated by at least one blank the value of the
    8758variable. Again separated by blank t<font face="Thorndale, serif">he
    8859so-called validity domain</font> can be indicated (later more).
    89 With the first three variables <b>mrun</b> gets to know in which
    90 directory the source code lies (</font><tt><i><font
    91  face="Thorndale, serif">source_path</font></i></tt><font
    92  face="Thorndale, serif">),
    93 the file name of the main program (</font><tt><i><font
    94  face="Thorndale, serif">mainprog</font></i></tt><font
    95  face="Thorndale, serif">)
    96 and that the <font face="Thorndale, serif">make mechanism should be
     60With the first three variables <b>mrun</b> gets to know in
     61which
     62directory the source code lies (</font><tt><i><font face="Thorndale, serif">source_path</font></i></tt><font face="Thorndale, serif">),
     63the file name of the main program (</font><tt><i><font face="Thorndale, serif">mainprog</font></i></tt><font face="Thorndale, serif">)
     64and that the <font face="Thorndale, serif">make mechanism
     65should be
    9766used </font>for compiling (</font><tt><font face="Thorndale, serif"><i>use_makefile
    9867=</i> <i>true</i></font></tt><font face="Thorndale, serif">). <b>mrun
    99 </b>needs these information, <font color="#000000">because for each
     68</b>needs these information, <font color="#000000">because
     69for each
    10070model run the executable is created by compiling the source files.</font>
    10171Normally, only the main program (palm.f90) will be compiled while all
    … …  
    10474model
    10575(see </font><a href="chapter_5.0.html"><font face="Thorndale, serif">chapter
    106 5.0</font></a><font face="Thorndale, serif">). <b>mrun</b> uses
     765.0</font></a><font face="Thorndale, serif">).
     77<b>mrun</b> uses
    10778certain standard options for the compilation process. Beyond that you
    10879can
    109 declare additional options with the environment variable </font><tt><i><font
    110  face="Thorndale, serif">fopts</font></i></tt><font
    111  face="Thorndale, serif">.
     80declare additional options with the environment variable </font><tt><i><font face="Thorndale, serif">fopts</font></i></tt><font face="Thorndale, serif">.
    11281Within the value assignment of an environment variable in the
    11382configuration file no blanks must be
    11483used. If blanks are necessary they must <font face="Thorndale, serif">be
    115 replaced </font>by colons (“:”). <b>mrun</b> will
     84replaced </font>by colons (&ldquo;:&rdquo;). <b>mrun</b>
     85will
    11686interpret these colons as blanks (2 colons written one behind the
    117 other will be interpreted as a colon). Thus in the example above </font><tt><font
    118  face="Thorndale, serif">fopts
    119 has the value </font></tt>“<font
    120  style="font-size: 10pt; font-family: monospace;" size="2"><i>-O3 -g
     87other will be interpreted as a colon). Thus in the example above </font><tt><font face="Thorndale, serif">fopts
     88has the value </font></tt>&ldquo;<font style="font-size: 10pt; font-family: monospace;" size="2"><i>-O3
     89-g
    12190-qrealsize=8 -Q -q64 -qmaxmem=-1 -qtune=pwr4 -qarch=pwr4 -qnosave
    122 -qnoescape</i></font><tt><i><font face="Thorndale, serif"><font
    123  color="#000000">”</font></font></i></tt><font face="Thorndale, serif"><font
    124  color="#000000">.
    125 Thus a PALM executable is generated using high level optimization (</font></font><font
    126  color="#000000"><span
    127  style="font-style: italic; font-family: monospace;">-O3</span></font><font
    128  face="Thorndale, serif"><font color="#000000">).</font></font><font
    129  color="#000000"><font face="Thorndale, serif"> For all other options
    130 see the compiler manual on the IBM (</font><font size="2"><font
    131  face="Cumberland, monospace">man</font></font></font><tt><font
    132  color="#000000">
    133 <font size="2"><font face="Cumberland, monospace">f90</font></font></font></tt><font
    134  face="Thorndale, serif"><font color="#000000">). Additional libraries
     91-qnoescape</i></font><tt><i><font face="Thorndale, serif"><font color="#000000">&rdquo;</font></font></i></tt><font face="Thorndale, serif"><font color="#000000">.
     92Thus 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">
     93For all other options
     94see the compiler manual on the IBM (</font><font size="2"><font face="Cumberland, monospace">man</font></font></font><tt><font color="#000000">
     95<font size="2"><font face="Cumberland, monospace">f90</font></font></font></tt><font face="Thorndale, serif"><font color="#000000">).
     96Additional libraries
    13597which the compiler should use are described by
    136 the environment variable </font></font><tt><font size="2"><font
    137  face="Cumberland, monospace"><font color="#000000">lopts</font></font></font></tt><font
    138  color="#000000">
    139 <font face="Thorndale, serif">(loader options).</font></font><font
    140  color="#800000">
     98the environment variable </font></font><tt><font size="2"><font face="Cumberland, monospace"><font color="#000000">lopts</font></font></font></tt><font color="#000000">
     99<font face="Thorndale, serif">(loader options).</font></font><font color="#800000">
    141100</font><font face="Thorndale, serif"><font color="#000000">Here you
    142101have to indicate a special IBM library (ESSL, </font></font>Engineering
    143 and Scientific Subroutine Library)<font face="Thorndale, serif"><font
    144  color="#000000">.</font><font color="#800000"> </font>On the
    145 IBM-Regatta, all compiler options have also to be given to the linker.</font><font
    146  color="#000000"><font face="Thorndale, serif"> </font></font>
    147 </p>
    148 <p style="line-height: 100%;"><font color="#000000">Compiler and
     102and Scientific Subroutine Library)<font face="Thorndale, serif"><font color="#000000">.</font><font color="#800000">
     103</font>On the
     104IBM-Regatta, all compiler options have also to be given to the linker.</font><font color="#000000"><font face="Thorndale, serif"> </font></font>
     105</p><p style="line-height: 100%;"><font color="#000000">Compiler and
    149106loader options usually differ from computer to computer. In the
    150107configuration file therefore several value assignments for the
    151 variables </font><tt><font style="font-size: 10pt;" size="2"><font
    152  color="#000000">fopts</font></font></tt><font color="#000000">
    153 and </font><tt><font style="font-size: 10pt;" size="2"><font
    154  color="#000000">lopts</font></font></tt><font color="#000000">
    155 exist which become active for different computers.</font><font
    156  color="#800000">
    157 <font color="#000000">Which value assignment is used is described by
     108variables </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">fopts</font></font></tt><font color="#000000">
     109and </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">lopts</font></font></tt><font color="#000000">
     110exist which become active for different computers.</font><font color="#800000">
     111<font color="#000000">Which value assignment is used is
     112described by
    158113the so-called validity domain which follows in the appropriate
    159 variable lines after the value of variables.</font></font><font
    160  color="#000000">
    161 In the example above the entry “</font><font color="#000000"><font
    162  style="font-size: 11pt; font-style: italic; font-family: monospace;"
    163  size="2">ibmh</font></font><tt><font color="#000000"><span
    164  style="font-style: italic; font-family: monospace;">
    165 </span></font><font color="#000000"><i><font style="font-size: 11pt;"
    166  size="2">parallel</font></i></font></tt><font color="#000000">”
    167 stands for </font><tt><font style="font-size: 10pt;" size="2"><font
    168  color="#000000">fopts</font></font></tt><font color="#000000">
    169 and </font><tt><font style="font-size: 10pt;" size="2"><font
    170  color="#000000">lopts</font></font></tt><font color="#000000">.
     114variable lines after the value of variables.</font></font><font color="#000000">
     115In 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;">
     116</span></font><font color="#000000"><i><font style="font-size: 11pt;" size="2">parallel</font></i></font></tt><font color="#000000">&rdquo;
     117stands for </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">fopts</font></font></tt><font color="#000000">
     118and </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">lopts</font></font></tt><font color="#000000">.
    171119These lines only become active if a run on the parallel computer of
    172 the HLRN (</font><tt><i><font style="font-size: 10pt;" size="2">ibmh</font></i></tt><font
    173  color="#000000">)
    174 on several <font color="#000000">(</font><tt><i><font
    175  style="font-size: 10pt;" size="2"><font color="#000000">parallel</font></font></i></tt><font
    176  color="#000000">)
     120the HLRN (</font><tt><i><font style="font-size: 10pt;" size="2">ibmh</font></i></tt><font color="#000000">)
     121on 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">)
    177122</font>processors is started. The activation takes place when you
    178123appropriately specify the <span style="font-weight: bold;">mrun</span>
    179 options </font><tt><font color="#000000">-h</font></tt><font
    180  color="#000000">
    181 and </font><tt><font color="#000000">-K</font></tt><font
    182  color="#000000">
     124options </font><tt><font color="#000000">-h</font></tt><font color="#000000">
     125and </font><tt><font color="#000000">-K</font></tt><font color="#000000">
    183126(see below). This way, the validity domain can be limited also for all
    184127other environment-variables. If no validity domain
    185128is indicated then the given values of variables are valid on all
    186129computers. </font>
    187 </p>
    188 <p style="line-height: 100%;">After the value assignment for the
    189 variables the so-called error commands follow which have to begin with “<tt><font
    190  style="font-size: 11pt;" size="2">EC:</font></tt>”
    191 in the first column (comment lines begin with “<tt>#</tt>”). Directly
     130</p><p style="line-height: 100%;">After the value
     131assignment for the
     132variables the so-called error commands follow which have to begin with
     133&ldquo;<tt><font style="font-size: 11pt;" size="2">EC:</font></tt>&rdquo;
     134in the first column (comment lines begin with &ldquo;<tt>#</tt>&rdquo;).
     135Directly
    192136after the colon Unix commands follow (korn shell syntax) which are
    193137processed by <b>mrun</b> if errors arise during
    194 the model run. The command described in the example (<tt><font
    195  style="font-size: 10pt;" size="2">cat
     138the model run. The command described in the example (<tt><font style="font-size: 10pt;" size="2">cat
    196139RUN_CONTROL</font></tt>) is executed thereby only on the
    197 condition that errors during the execution of the model (<tt><font
    198  style="font-size: 10pt;" size="2">execution</font></tt>)
    199 arise. An <b>mrun </b>internal environment variable which indicates
     140condition that errors during the execution of the model (<tt><font style="font-size: 10pt;" size="2">execution</font></tt>)
     141arise. An <b>mrun </b>internal environment variable which
     142indicates
    200143the
    201 respective abort place in case of errors is <tt><a
    202  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#locat">locat</a></tt>.
     144respective 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>.
    203145In order to determine the actual value of this variable at the
    204 execution of <b>mrun</b> the “<tt>$</tt>” - prefix
    205 must be protected by a “\” since the configuration file has been
    206 already interpreted once when reading in through <b>mrun</b> and the
     146execution of <b>mrun</b> the &ldquo;<tt>$</tt>&rdquo;
     147- prefix
     148must be protected by a &ldquo;\&rdquo; since the configuration
     149file has been
     150already interpreted once when reading in through <b>mrun</b>
     151and the
    207152value from
    208 <tt>locat</tt> would then supply the empty character string. If
     153<tt>locat</tt> would then supply the empty character
     154string. If
    209155errors arise during the model run this command
    210156copies the data written by the model up to then to the local file
    211157<a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
    212158on the standard output where they can be checked after
    213 job end.<font color="#000000"> RUN_CONTROL is an output file of the
     159job end.<font color="#000000"> RUN_CONTROL is an output
     160file of the
    214161model which has to be copied according to the default configuration
    215162file
    216163(see below) after the end of the model run to a permanent file of the
    217164user but this action would not be performed in case of errors
    218 in the model run, so that the file content would be lost.</font> With
     165in the model run, so that the file content would be lost.</font>
     166With
    219167the help of the error command one can secure it nevertheless. </p>
    220168<p style="line-height: 100%;">Before and/or after
    … …  
    222170and/or output commands which are implemented before and/or after the
    223171model run. </p>
    224 <p style="line-height: 100%;">After the output commands<font
    225  color="#000000">
    226 <font color="#000000">in the example file t</font>he so-called file
    227 connection statements</font> <font color="#000000">follow </font>via
    228 which tell <span style="font-weight: bold;">mrun</span> how to connect
     172<p style="line-height: 100%;">After the output commands<font color="#000000">
     173<font color="#000000">in the example file t</font>he
     174so-called file
     175connection statements</font> <font color="#000000">follow
     176</font>via
     177which tell <span style="font-weight: bold;">mrun</span>
     178how to connect
    229179the local files in the temporary working
    230180directory of the model with the respective permanent files of the user.
    231 <b>mrun</b> copies the input and output files in accordance with the
     181<b>mrun</b> copies the input and output files in accordance
     182with the
    232183data in these connection statements. The file connection statements are
    233184explained in detail in the <b>mrun</b>
    234 description (<a
    235  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.3">chapter
     185description (<a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.3">chapter
    2361866.3</a>, in German) and are described here only as far as being
    237187necessary. A
    … …  
    243193the start of the line. In the second column the so-called file
    244194attributes
    245 are given. These determine whether the file is an input file (<tt><font
    246  style="font-size: 10pt;" size="2">in</font></tt>)
    247 or an output file (<tt><font size="2">out</font></tt>), whether output
    248 files are to be transferred to the local computer of the user (<tt><font
    249  style="font-size: 10pt;" size="2">tr</font></tt>)
    250 or whether they are to be archived (<font size="2"><font
    251  face="Cumberland, monospace">fl</font></font>).
    252 If a file has several attributes then they are separated by a <font
    253  color="#000000">colon
     195are given. These determine whether the file is an input file (<tt><font style="font-size: 10pt;" size="2">in</font></tt>)
     196or an output file (<tt><font size="2">out</font></tt>),
     197whether output
     198files are to be transferred to the local computer of the user (<tt><font style="font-size: 10pt;" size="2">tr</font></tt>)
     199or whether they are to be archived (<font size="2"><font face="Cumberland, monospace">fl</font></font>).
     200If a file has several attributes then they are separated by a <font color="#000000">colon
    254201in each case .</font> </p>
    255 <p style="line-height: 100%;">With the entries in the third column one
     202<p style="line-height: 100%;">With the entries in the
     203third column one
    256204specifies the conditions under which a file connection statement
    257205becomes active i.e. under
    … …  
    260208character strings registered in column 3 (again two or more character
    261209strings have to be separated from each other by a colon) is
    262 indicated within the mrun <b>call</b> by the option <a
    263  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-r">-r</a>.
     210indicated 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>.
    264211Thus a call of the form </p>
    265 <ul>
    266   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    267  style="font-size: 10pt;" size="2">mrun - h ibmh -d abcde -r d3</font></pre>
    268 </ul>
    269 <p style="line-height: 100%;">would lead to the fact that the input
     212<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>
     213<p style="line-height: 100%;">would lead to the fact that
     214the input
    270215file with the local name PARIN is made available and the output files
    271216RUN_CONTROL and HEADER are copied to permanent files. The output
    272217files PLOT1D_PAR and PLOT1D_DATA are not copied so that their
    273218contents are not available to the user after the end of the job. If
    274 these files are to be copied of <b>mrun</b> then the call must be</p>
    275 <ul>
    276   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    277  style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -r "d3 pr"</font></pre>
    278 </ul>
    279 <p style="line-height: 100%;">Instead of the option -r you can
     219these files are to be copied of <b>mrun</b> then the call
     220must be</p>
     221<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>
     222<p style="line-height: 100%;">Instead of the option -r you
     223can
    280224separately address the file connection statements for input and/or
    281225output files with the options -i and -o. If one likes to make sure with
    … …  
    283227file all file connection statements are actually executed then
    284228the call must be: </p>
    285 <ul>
    286   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    287  style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -i d3 -o "d3 pr"</font></pre>
    288 </ul>
    289 <p style="line-height: 100%;"><font color="#000000">The names of the
     229<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>
     230<p style="line-height: 100%;"><font color="#000000">The
     231names of the
    290232local files assigned permanent files are build from the entries in
    291233the 4th and 5th column of the file connection statements and the
    292 value of the <span style="font-weight: bold;">mrun</span> option </font><tt><font
    293  style="font-size: 10pt;" size="2"><font color="#000000">-d</font></font></tt><font
    294  color="#000000">
     234value of the <span style="font-weight: bold;">mrun</span>
     235option </font><tt><font style="font-size: 10pt;" size="2"><font color="#000000">-d</font></font></tt><font color="#000000">
    295236in the following way:</font><font color="#800000"> </font>
    296 </p>
    297 <ul>
    298   <p style="line-height: 100%;">File name (inclusive path) = “value of
    299 the 4th column” + “value of the option <tt><font size="2">-d</font></tt>”
    300 + “value of the 5th column”.</p>
    301 </ul>
    302 <p style="line-height: 100%;">The 4th column contains the path name
    303 whereby <tt><a
    304  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#fname">$fname</a></tt>
     237</p><ul> <p style="line-height: 100%;">File
     238name (inclusive path) = &ldquo;value of
     239the 4th column&rdquo; + &ldquo;value of the option <tt><font size="2">-d</font></tt>&rdquo;
     240+ &ldquo;value of the 5th column&rdquo;.</p>
     241</ul><p style="line-height: 100%;">The 4th column
     242contains the path name
     243whereby <tt><a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#fname">$fname</a></tt>
    305244is replaced by the value indicated for the option <tt><font size="2">-d</font></tt>.
    306245The 5th column contains the so-called file name extension. The name
    307 of the permanent file which was copied by <b>mrun</b> to the local
     246of the permanent file which was copied by <b>mrun</b> to
     247the local
    308248file <tt>PARIN</tt> thereby reads: </p>
    309 <ul>
    310   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    311  style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d.</font></pre>
    312 </ul>
    313 <p style="line-height: 100%;">In the same way the names of the
     249<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>
     250<p style="line-height: 100%;">In the same way the names of
     251the
    314252permanent files of the remaining <font color="#000000">file
    315253connection statements </font>can be formed. </p>
    316 <p style="line-height: 100%;">With this example configuration file
     254<p style="line-height: 100%;">With this example
     255configuration file
    317256exactly one input file is copied into the temporary working directory
    318 of the model. This file has the local name <a
    319  href="chapter_3.4.html#PARIN">PARIN</a>
     257of the model. This file has the local name <a href="chapter_3.4.html#PARIN">PARIN</a>
    320258and contains the steering parameters for the model and has to be
    321259provided by the user for each model run. </p>
    322 <p style="line-height: 100%;">The example configuration file also
    323 instructs <b>mrun</b> to copy four output files of the model to
     260<p style="line-height: 100%;">The example configuration
     261file also
     262instructs <b>mrun</b> to copy four output files of the
     263model to
    324264appropriate permanent files of the user at the end of the run.
    325 There are timestep information (local file name <tt><a
    326  href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a></tt>),
     265There are timestep information (local file name <tt><a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a></tt>),
    327266the so-called header file, in which the values of the most selected
    328267parameters for this run (<tt><a href="chapter_3.4.html#HEADER">HEADER</a></tt>)
    … …  
    330269vertical profiles
    331270(<tt><a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a></tt>)
    332 and an associated parameter file (<tt><a
    333  href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a></tt>),
    334 which can be used as input files for the plot program <a
    335  href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
     271and an associated parameter file (<tt><a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a></tt>),
     272which 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>.
    336273A model run does not presuppose neither the file connection statements
    337274for
    … …  
    339276them usually the data produced by the model
    340277are lost after the end of the model run! </p>
    341 <p style="line-height: 100%;">As already mentioned the configuration
     278<p style="line-height: 100%;">As already mentioned the
     279configuration
    342280file offers a variety of further possibilities to steer the
    343281execution of the model run. Some of them are described in the next
    344282chapter. Same applies to possible other options of the <b>mrun</b>
    345 call. For these please refer to the <a
    346  href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a>
    347 documentation (in German). An <b>mrun </b>call for the execution of a
     283call. For these please refer to the <a href="http://www.muk.uni-hannover.de/%7Eraasch/Software/mrun_beschreibung.html">mrun</a>
     284documentation (in German). An <b>mrun </b>call for the
     285execution of a
    348286model run
    349287on several processors on the IBM Regatta "hanni" of the HLRN must be
    350288supplemented by the following options in each case: </p>
    351 <ul>
    352   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    353  style="font-size: 10pt;" size="2">mrun - K parallel -X
    354  -t
    355  -m
    356 </font></pre>
    357 </ul>
    358 <p style="line-height: 100%;">Only the indication of <tt><font
    359  style="font-size: 11pt;" size="2">-K
    360 parallel</font></tt> causes the parallel execution of the run on
     289<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>
     290<p style="line-height: 100%;">Only the indication of <tt><font style="font-size: 11pt;" size="2">-K
     291parallel</font></tt> causes the parallel execution of the
     292run on
    361293several processors (otherwise a scalar execution on one processor is
    362294accomplished). In addition to this the number of the
    363295processing elements which shall be used has to be pre-scribed with the
    364 option <tt><font style="font-size: 10pt;" size="2">-X</font> </tt><font
    365  size="2">(</font><font style="font-size: 10pt;" size="2">e.g.
    366 </font><tt><font style="font-size: 10pt;" size="2">-X 4</font></tt><font
    367  size="2">).</font>
     296option <tt><font style="font-size: 10pt;" size="2">-X</font>
     297</tt><font size="2">(</font><font style="font-size: 10pt;" size="2">e.g.
     298</font><tt><font style="font-size: 10pt;" size="2">-X
     2994</font></tt><font size="2">).</font>
    368300In each case the permitted CPU time in seconds and the required memory
    369 size in MB must be indicated by the options <tt><font
    370  style="font-size: 11pt;" size="2">-t</font></tt>
     301size in MB must be indicated by the options <tt><font style="font-size: 11pt;" size="2">-t</font></tt>
    371302and <tt><font style="font-size: 11pt;" size="2">-m</font></tt>,
    372303respectively<font face="Thorndale, serif">.</font>
    373304Alternatively, these can be set by the appropriate environment
    374305variables in the configuration file: </p>
    375 <blockquote style="line-height: 100%;"><tt><font
    376  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">%
    377 memory&nbsp; <i>1630</i> ibmh parallel</font></font></tt><font
    378  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
    379   </font></font><tt><font style="font-size: 10pt;" size="2"><font
    380  face="Cumberland, monospace">%
     306<blockquote style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">%
     307memory&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">%
    381308cputime <i>1000</i> ibmh parallel</font></font></tt></blockquote>
    382 <p style="line-height: 100%;">The values indicated there can be
    383 overridden with the values of the options <tt><font
    384  style="font-size: 10pt;" size="2">-t</font></tt>
     309<p style="line-height: 100%;">The values indicated there
     310can be
     311overridden with the values of the options <tt><font style="font-size: 10pt;" size="2">-t</font></tt>
    385312and/or <tt><font style="font-size: 10pt;" size="2">-m</font></tt>,
    386313respectivly. </p>
    387 <hr>
    388 <p style="line-height: 100%;"><br>
    389 <font color="#000080"><font color="#000080"><a href="chapter_3.1.html"><font
    390  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    391  border="2" height="32" width="32"></font></a><a href="index.html"><font
    392  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    393  border="2" height="32" width="32"></font></a><a href="chapter_3.3.html"><font
    394  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    395  border="2" height="32" width="32"></font></a></font></font></p>
    396 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 14/04/05 (SR)</p>
    397 </body>
    398 </html>
     314<hr><p style="line-height: 100%;"><br>
     315<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>
     316$Id$</p>
     317</body></html>

  • palm/trunk/DOC/app/chapter_3.3.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 3.3</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Marcus Oliver Letzel">
    9   <meta name="CREATED" content="20040728;14053490">
    10   <meta name="CHANGED" content="20041112;14150257">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h3 style="line-height: 100%;">3.3 Initialization and restart runs</h3>
    20 <p style="line-height: 100%;">A job started by <b>mrun</b> will
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.3 Initialization and restart
     11runs</h3>
     12<p style="line-height: 100%;">A job started by <b>mrun</b>
     13will
    2114- according to its requested computing time, its memory size
    2215requirement and
    … …  
    3528very fast, jobs with higher requirements must wait longer (sometimes
    3629several days). </p>
    37 <p style="line-height: 100%;">Before the start of a model run the user
     30<p style="line-height: 100%;">Before the start of a model
     31run the user
    3832must estimate how much CPU time the model will need for the simulation.
    3933The necessary time in seconds has to be indicated with the mrun
    40 <b>option</b> <tt><a
    41  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-t">-t</a></tt>
     34<b>option</b> <tt><a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Opt-t">-t</a></tt>
    4235and has an influence on the job class into which the job is queued. Due
    4336to the fact that the model usually uses a variable
    … …  
    4942which normally leads to an abort of the job as soon as the available
    5043CPU time is consumed. In principle one could solve this problem by
    51 setting a very generously estimated value for <u><font
    52  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-t</font></font></u>,
     44setting a very generously estimated value for <u><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-t</font></font></u>,
    5345but this will possibly lead to the disadvantage that the queued job has
    5446to wait longer for execution.<br>
    55 </p>
    56 <p style="line-height: 100%;">To avoid this problem <b>mrun </b>offers
    57 the possibility of so-called <b>restart runs</b>. During the model
     47</p><p style="line-height: 100%;">To avoid this
     48problem <b>mrun </b>offers
     49the possibility of so-called <b>restart runs</b>. During
     50the model
    5851run PALM continuously examines how much time is left for the
    5952execution of the job. If the run is not completed and finished shortly
    … …  
    7568first run of this chain (model start at t=0) is called
    7669<b>initial run</b>. </p>
    77 <p style="line-height: 100%;">Working with restart runs and their
    78 generation through <b>mrun</b> requires certain entries in the
     70<p style="line-height: 100%;">Working with restart runs
     71and their
     72generation through <b>mrun</b> requires certain entries in
     73the
    7974mrun-configuration file and in the parameter file, which are
    8075described and explained in the following. The configuration file must
    8176contain the following entries (example for the IBM Regatta of the
    8277HLRN): </p>
    83 <ul>
    84   <pre style="line-height: 100%;"><font style="font-size: 10pt;"
    85  size="2">%write_binary    true    restart</font><br><font
    86  style="font-size: 10pt;" size="2">#</font><br><a
    87  href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN</font></a><font
    88  style="font-size: 10pt;" size="2">   in:job:npe   d3#   ~/palm/current_version/JOBS/$fname/INPUT    _p3d</font><br><font
    89  style="font-size: 10pt;" size="2">PARIN   in:job:npe   d3f   ~/palm/current_version/JOBS/$fname/INPUT    _p3df</font><br><a
    90  href="chapter_3.4.html#BININ"><font style="font-size: 10pt;" size="2">BININ</font></a><font
    91  style="font-size: 10pt;" size="2">   in:loc       d3f   ~/palm/current_version/JOBS/$fname/OUTPUT   _d3d</font><br><font
    92  style="font-size: 10pt;" size="2">#</font><br><a
    93  href="chapter_3.4.html#BINOUT"><font style="font-size: 10pt;" size="2">BINOUT</font></a><font
    94  style="font-size: 10pt;" size="2">  out:loc   restart  ~/palm/current_version/JOBS/$fname/OUTPUT   _d3d</font></pre>
    95 </ul>
    96 <p style="line-height: 100%;">The <b>mrun</b> call for the
     78<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>
     79<p style="line-height: 100%;">The <b>mrun</b>
     80call for the
    9781initialization run of the job chain must look as follows: </p>
    98 <ul>
    99   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    100  style="font-size: 10pt;" size="2">mrun -h ibmh -d abcde -t 900 -r "d3# restart"</font></pre>
    101 </ul>
    102 <p style="line-height: 100%;">The specification of the environment
    103 variable <tt><tt><font style="font-size: 10pt;" size="2">writ</font></tt></tt><tt><tt><font
    104  style="font-size: 10pt;" size="2">e_binary</font><font
    105  style="font-size: 11pt;" size="2">, </font></tt></tt>which must be
     82<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>
     83<p style="line-height: 100%;">The specification of the
     84environment
     85variable <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
     86must be
    10687assigned the value <tt><tt><font style="font-size: 10pt;" size="2">true</font></tt></tt>,
    10788is essential. Only in this case the model writes
    108 binary-coded data for a possible restart run to the local file <tt><tt><a
    109  href="chapter_3.4.html#BINOUT">BINOUT</a></tt></tt>
     89binary-coded data for a possible restart run to the local file <tt><tt><a href="chapter_3.4.html#BINOUT">BINOUT</a></tt></tt>
    11090at the end of the run. Then of course this output file must be stored
    11191on a permanent file with an appropriate file connection statement
    11292(last line of the example above). As you can see, both instructions
    11393(variable declaration and connection statements) are only carried out
    114 by <b>mrun</b>, if the character string <tt><tt><font
    115  style="font-size: 10pt;" size="2">restart</font></tt></tt>
     94by <b>mrun</b>, if the character string <tt><tt><font style="font-size: 10pt;" size="2">restart</font></tt></tt>
    11695is given for the option <tt><font style="font-size: 10pt;" size="2">-r</font>
    117 </tt>in the <span style="font-weight: bold;">mrun</span> call. Thus
     96</tt>in the <span style="font-weight: bold;">mrun</span>
     97call. Thus
    11898the example above can also be used
    11999if no restart runs are intended. In such cases the character string
    … …  
    122102can simply be omitted. </p>
    123103<p style="line-height: 100%;">Only by the specification of
    124 <tt><font style="font-size: 10pt;" size="2">write_binary=true</font><font
    125  style="font-size: 11pt;" size="2">
    126 </font><font face="Thorndale, serif">the</font></tt> model is
     104<tt><font style="font-size: 10pt;" size="2">write_binary=true</font><font style="font-size: 11pt;" size="2">
     105</font><font face="Thorndale, serif">the</font></tt>
     106model is
    127107instructed to compute the remaining CPU time after each time step and
    128108stop, if the run is not going to be completed and finished briefly
    … …  
    130110this time. Actually the stop takes place when the
    131111difference from the available job time (determined by the <b>mrun</b>
    132 option <tt><font style="font-size: 10pt;" size="2">-t</font></tt>) and
     112option <tt><font style="font-size: 10pt;" size="2">-t</font></tt>)
     113and
    133114the time used so far by the job becomes smaller than the time given
    134 by the model variable <a
    135  href="chapter_4.2.html#termination_time_needed">termination_time_needed</a>.
    136 With the variable <b>termination_time_needed </b>the user determines,
     115by the model variable <a href="chapter_4.2.html#termination_time_needed">termination_time_needed</a>.
     116With the variable <b>termination_time_needed </b>the user
     117determines,
    137118how much time is needed for binary copying of the data for restart
    138119runs, as
    139120well as for the following data archiving and transfer of result data
    140121etc. (as long as this is part of the job). Thus, as soon as the
    141 remaining job time is less than <b>termination_time_needed</b>, the
     122remaining job time is less than <b>termination_time_needed</b>,
     123the
    142124model stops
    143125the time step procedure and copies the data for a restart run to the
    … …  
    148130the fact that a restart run must be started and leads to the
    149131start of an appropriate job. </p>
    150 <p style="line-height: 100%;"><font color="#000000">During the initial
    151 phase of a restart ru</font>n different actions than during the initial
     132<p style="line-height: 100%;"><font color="#000000">During
     133the initial
     134phase of a restart ru</font>n different actions than during the
     135initial
    152136phase of an initial run of the model are neccessary. In this
    153137case the model must read in the binary data written by the preceding
    154138run at the beginning of the run. Beyond that it also reads the
    155139initialization parameters from this file. Therefore these do not need
    156 to be indicated in the parameter file (local name <a
    157  href="chapter_3.4.html#PARIN">PARIN</a>).
     140to be indicated in the parameter file (local name <a href="chapter_3.4.html#PARIN">PARIN</a>).
    158141If they are indicated nevertheless and if their value deviates from
    159142their value of the initial run, then this is ignored. There is
    160143exactly one exception to this rule: with the help of the
    161 initialization parameter <a
    162  href="chapter_4.1.html#initializing_actions">initializing_actions</a>
     144initialization parameter <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>
    163145it is determined whether the job is a restart run or an
    164146initial run. If <b>initializing_actions</b> =
    165 “<i>read_restart_data”</i>, then it is a restart
     147&ldquo;<i>read_restart_data&rdquo;</i>, then it is
     148a restart
    166149run, otherwise an initial run. The previous remarks make it
    167150clear that the model obviously needs two different parameter files
    … …  
    173156parameters with values different from the initial run may appear in
    174157this file, but they will be ignored), which
    175 must have the value “<i>read_restart_data”</i>.
     158must have the value &ldquo;<i>read_restart_data&rdquo;</i>.
    176159Therefore the user must produce two different parameter files if he
    177160wants to operate job chains. Since the model always expects the
    178 parameter file on the local file <tt>PARIN</tt>, two different file
     161parameter file on the local file <tt>PARIN</tt>, two
     162different file
    179163connection statements must be given for this file in the
    180164configuration file. One may be active only at the initial run,
    181 the other one only at restart runs. The <b>mrun </b>call for the
     165the other one only at restart runs. The <b>mrun </b>call
     166for the
    182167initial run shown above activates the first of the two
    183 specified connection statements, because the character string <tt><font
    184  style="font-size: 10pt;" size="2">d3#</font></tt>
     168specified connection statements, because the character string <tt><font style="font-size: 10pt;" size="2">d3#</font></tt>
    185169with the option <tt><font style="font-size: 10pt;" size="2">-r</font></tt>
    186170coincides with the character
    187171string in the third column of the connection statement. Obviously
    188172the next statement must be active</p>
    189 <ul>
    190   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    191  style="font-size: 10pt;" size="2">PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</font></pre>
    192 </ul>
    193 <p style="line-height: 100%;">with the restart runs. Given that t<font
    194  color="#000000">his statement only gets</font> active if the option <tt><font
    195  style="font-size: 10pt;" size="2">-r</font></tt> is given the value
    196 <tt><font style="font-size: 11pt;" size="2">d3f</font></tt> and that
     173<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>
     174<p style="line-height: 100%;">with the restart runs. Given
     175that t<font color="#000000">his statement only gets</font>
     176active if the option <tt><font style="font-size: 10pt;" size="2">-r</font></tt> is given the value
     177<tt><font style="font-size: 11pt;" size="2">d3f</font></tt>
     178and that
    197179the <b>mrun</b> call for this restart run is produced
    198 automatically (thus not by the user), <b>mrun</b> obviously has to
     180automatically (thus not by the user), <b>mrun</b>
     181obviously has to
    199182replace <tt><font style="font-size: 10pt;" size="2">"d3#"</font></tt>
    200183of the initial run with <tt><tt><font style="font-size: 10pt;" size="2">"d3f"</font>
    201 </tt></tt>within the call of this restart run. Actually, with restart
     184</tt></tt>within the call of this restart run. Actually,
     185with restart
    202186runs all <tt><font style="font-size: 10pt;" size="2">"#"</font></tt>
    203 characters within the strings given for the options <tt><font
    204  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-r</font></font></tt><font
    205  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">
    206 , </font></font><tt><font style="font-size: 10pt;" size="2"><font
    207  face="Cumberland, monospace">-i</font></font></tt>
    208 and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> are
    209 replaced by <tt><font style="font-size: 10pt;" size="2">“f”</font></tt>.
     187characters 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">
     188, </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-i</font></font></tt>
     189and <tt><font style="font-size: 10pt;" size="2">-o</font></tt>
     190are
     191replaced by <tt><font style="font-size: 10pt;" size="2">&ldquo;f&rdquo;</font></tt>.
    210192</p>
    211 <p style="line-height: 100%;">For example, for the initial run
     193<p style="line-height: 100%;">For example, for the initial
     194run
    212195the permanent file </p>
    213 <ul>
    214   <pre style="margin-bottom: 0.5cm; line-height: 100%;">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d</pre>
    215 </ul>
    216 <p style="line-height: 100%;">and for restart runs the permanent file<span
    217  style="font-family: monospace;"> </span></p>
    218 <ul style="font-family: monospace;">
    219   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    220  style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3df</font></pre>
    221 </ul>
    222 <p style="line-height: 100%;">is used. Only with restart runs the
    223 local file <tt>BININ</tt> is made available as input file, because
     196<ul> <pre style="margin-bottom: 0.5cm; line-height: 100%;">~/palm/current_version/JOBS/abcde/INPUT/abcde_p3d</pre></ul>
     197<p style="line-height: 100%;">and for restart runs the
     198permanent file<span style="font-family: monospace;"> </span></p>
     199<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>
     200<p style="line-height: 100%;">is used. Only with restart
     201runs the
     202local file <tt>BININ</tt> is made available as input file,
     203because
    224204the appropriate file connection statement also contains the
    225205character string <tt><font style="font-size: 10pt;" size="2">"d3f"</font></tt>
    … …  
    230210the corresponding output file (local name BINOUT) are identical and
    231211read </p>
    232 <ul>
    233   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    234  style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/abcde/OUTPUT/abcde_d3d.</font></pre>
    235 </ul>
    236 <p style="line-height: 100%;">However, after the file produced by the
     212<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>
     213<p style="line-height: 100%;">However, after the file
     214produced by the
    237215previous job was read in by the model and after at the local file
    238216<tt>BINOUT </tt>was produced at the end of the job, the
    239 restart job does not overwrite this permanent file (<tt>
    240 /<font
    241  style="font-size: 10pt;" size="2">abcde_d3d</font></tt>)
     217restart job does not overwrite this permanent file (<tt>&hellip;/<font style="font-size: 10pt;" size="2">abcde_d3d</font></tt>)
    242218with the new data. Instead of that, it is examined whether already
    243 a permanent file with the name <tt><font style="font-size: 10pt;"
    244  size="2">
    245 /abcde_d3d</font>
    246 <font face="Thorndale, serif">exists </font></tt>when copying the
     219a permanent file with the name <tt><font style="font-size: 10pt;" size="2">&hellip;/abcde_d3d</font>
     220<font face="Thorndale, serif">exists </font></tt>when
     221copying the
    247222output file (<tt><font style="font-size: 10pt;" size="2">BINOUT</font></tt>)
    248 of <b>mrun</b>. If this is the case, <tt><font
    249  style="font-size: 10pt;" size="2">BINOUT</font></tt>
    250 is copied to the file<font style="font-size: 10pt;" size="2"><font
    251  face="Cumberland, monospace">
    252 </font></font><tt><font style="font-size: 10pt;" size="2"><font
    253  face="Cumberland, monospace">
    254 /abcde_d3d.1</font></font></tt><font
    255  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">.</font></font>
    256 Even if this file is already present, <tt><font
    257  style="font-size: 10pt;" size="2">
    258 /abcde_d3d.2</font></tt>
     223of <b>mrun</b>. If this is the case, <tt><font style="font-size: 10pt;" size="2">BINOUT</font></tt>
     224is copied to the file<font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">
     225</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>
     226Even if this file is already present, <tt><font style="font-size: 10pt;" size="2">&hellip;/abcde_d3d.2</font></tt>
    259227is tried etc. For an input file the highest existing cycle
    260228of the respective permanent file is copied. In the example above this
    261229means: the initial run creates the permanent file
    262 <tt><font style="font-size: 10pt;" size="2">
    263 /abcde_d3d</font></tt><font
    264  style="font-size: 11pt;" size="2">,</font>
    265 the first restart run uses this file and creates <tt>
    266 /<font
    267  style="font-size: 10pt;" size="2">abcde_d3d.1</font></tt>,
    268 the second restart run creates <tt><font style="font-size: 10pt;"
    269  size="2">
    270 /abcde_d3d.2</font></tt><font style="font-size: 10pt;"
    271  size="2">
     230<tt><font style="font-size: 10pt;" size="2">&hellip;/abcde_d3d</font></tt><font style="font-size: 11pt;" size="2">,</font>
     231the first restart run uses this file and creates <tt>&hellip;/<font style="font-size: 10pt;" size="2">abcde_d3d.1</font></tt>,
     232the 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">
    272233</font>etc. After completion of the job chain the user can still
    273234access all files created by the jobs. This makes it possible for the
    274235user for example to restart the model run of a certain job of the job
    275236chain again. </p>
    276 <p style="line-height: 100%;">Therefore restart jobs can not only be
    277 started automatically through <b>mrun</b>, but also manually by the
     237<p style="line-height: 100%;">Therefore restart jobs can
     238not only be
     239started automatically through <b>mrun</b>, but also
     240manually by the
    278241user. This is necessary e.g. whenever after the end of a job chain
    279242it is decided that the simulation must be continued further, because
    280243the phenomenon which should be examined did not reach the desired
    281 state yet. In such cases the <b>mrun</b> options completely
    282 correspond to those of the initial call; simply the <tt><font
    283  style="font-size: 10pt;" size="2">"#"</font></tt> characters in the
    284 arguments of options <tt><font style="font-size: 10pt;" size="2"><font
    285  face="Cumberland, monospace">-r</font></font></tt><font
    286  style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">,
    287 </font></font><tt><font style="font-size: 10pt;" size="2"><font
    288  face="Cumberland, monospace">-i</font></font></tt>
    289 and <tt><font style="font-size: 10pt;" size="2">-o</font></tt> must be
     244state yet. In such cases the <b>mrun</b> options
     245completely
     246correspond to those of the initial call; simply the <tt><font style="font-size: 10pt;" size="2">"#"</font></tt>
     247characters in the
     248arguments 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">,
     249</font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">-i</font></font></tt>
     250and <tt><font style="font-size: 10pt;" size="2">-o</font></tt>
     251must be
    290252replaced by <tt><font style="font-size: 10pt;" size="2">"f"</font></tt>.
    291253</p>
    292 <hr>
    293 <p style="line-height: 100%;"><br>
    294 <font color="#000080"><font color="#000080"><a href="chapter_3.2.html"><font
    295  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    296  border="2" height="32" width="32"></font></a><a href="index.html"><font
    297  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    298  border="2" height="32" width="32"></font></a><a href="chapter_3.4.html"><font
    299  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    300  border="2" height="32" width="32"></font></a></font></font></p>
    301 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 14/04/05 (SR)</p>
    302 </body>
    303 </html>
     254<hr><p style="line-height: 100%;"><br>
     255<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>
     256$Id$</p>
     257</body></html>

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

    r54 r62  
    11<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    22<html><head>
    3 
    4 
    5 
    6 
    7 
    8  
    9  
    10  
    11  
    12  
    13   <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
    14   <title>chapter_3.4</title></head>
    15 
    16 <body>
    17 
    18 
    19 
    20 
    21 
    22 <h3 style="line-height: 100%;"><font color="#000000">3.4 Input and
     3<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>chapter_3.4</title> </head>
     4<body><h3 style="line-height: 100%;"><font color="#000000">3.4 Input and
    235output files</font></h3>
    24 
    25 
    26 
    27 
    28 
    29 <p style="line-height: 100%;"><font color="#000000"></font></p>
    30 
    31 <p style="line-height: 100%;"><font color="#000000">The model works
     6<p style="line-height: 100%;"></p><p style="line-height: 100%;"><font color="#000000">The
     7model works
    328with a set of files, which are all located in the temporary working
    339directory and which are either expected at the beginning of the run
    … …  
    3511produced during the run and/or at the end of the simulation (output
    3612files).</font><font color="#800000">
    37 <font color="#000000">The following table lists all default files
     13<font color="#000000">The following table lists all
     14default files
    3815addressed by the model. They are arranged according to the
    3916associated FORTRAN unit (unit number).</font> </font><font color="#000000">The
    4017unit 90 is used for different files, which are opened only briefly
    4118and uniquely in the model and closed directly afterwards.
    42 Unit numbers 101 - 109, 111 - 113, and 116&nbsp;refer to data files which have NetCDF format.
     19Unit numbers 101 - 109, 111 - 113, and 116&nbsp;refer to data files
     20which have NetCDF format.
    4321These are not opened by a FORTRAN-OPEN-statement but by a corresponding
    4422NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on
    4523machines where a NetCDF library is available.<br>
    46 
    47 </font></p>
    48 
    49 
    50 <p style="line-height: 100%;"><font color="#000000">The file
     24</font></p><p style="line-height: 100%;"><font color="#000000">The file
    5125names described in the list correspond to the names indicated in the
    5226respective OPEN instruction, i.e. the files are expected and saved
    … …  
    5731If restart jobs shall append data to an existing NetCDF file (created
    5832by a previous job of the job chain), the respective file has to be
    59 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>
    60 
    61 <p style="line-height: 100%;"> </p>
    62 
    63 
    64 
    65 
    66 
    67 
    68 <p style="line-height: 100%;"><font color="#000000">On parallel
     33given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter
     344.5.1</a> which gives more details about the PALM-NetCDF-output).</font>
     35</p>
     36<p style="line-height: 100%;"> </p><p style="line-height: 100%;"><font color="#000000">On
     37parallel
    6938computers many of the files are read and/or written by the central
    7039processing element 0 (PE0) only. These files have processor-independent
    … …  
    7342content. For the binary output of data for restart runs (local file
    7443<a href="#BINOUT">BINOUT</a>),
    75 for example, <font color="#000000">each PE outputs only the data of
     44for example, <font color="#000000">each PE outputs only
     45the data of
    7646its subdomain. So each processing element writes
    7747into its own file with its own file name. These files lie in a
    … …  
    8252Such files, which have processor-dependent content on parallel
    8353computers, are marked in the following list by the fact, that to the
    84 file name a line (&rdquo;/&ldquo;) is attached. If appropriate output
    85 files are to be copied through <b>mrun</b> to permanent files, and/or
     54file name a line (&rdquo;/&ldquo;) is attached. If appropriate
     55output
     56files are to be copied through <b>mrun</b> to permanent
     57files, and/or
    8658files with processor-dependent content are supposed to be copied as
    8759input files into the temporary working directory of the model, you have
    … …  
    9062<a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#flpe">flpe</a>
    9163<font color="#000000">in the <b>mrun </b>description).</font><font color="#800000">
    92 </font><font color="#000000">Then the permanent file name will be
     64</font><font color="#000000">Then the permanent file
     65name will be
    9366interpreted as a directory name, in which the input files are
    9467expected and/or to which output files are written. The file names in
    9568these directories are always named _0000, _0001, _0002 etc. </font>
    96 </font></p>
    97 
    98 
    99 
    100 
    101 
    102 <font color="#000000"><font color="#000000">For internal use,
     69</font></p><font color="#000000"><font color="#000000">For internal use,
    10370the model may open a set of further files, which are not
    10471defined by the user but contain no usable information and
    10572therefore are not included in this list. <br>
    106 
    107 
    108 
    109 
    110 
    111 <br>
    112 
    113 
    114 
    115 
    116 
    117 </font>
    118 <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
    119 
    120 
    121 
    122 
    123 
    124   <tbody>
    125 
    126 
    127 
    128 
    129 
    130     <tr valign="top">
    131 
    132 
    133 
    134 
    135 
    136       <td width="8%">
    137      
    138      
    139      
    140      
    141      
    142       <p><font size="4"><b>Unit</b></font></p>
    143 
    144 
    145 
    146 
    147 
    148       </td>
    149 
    150 
    151 
    152 
    153 
    154       <td width="12%">
    155      
    156      
    157      
    158      
    159      
    160       <p><font size="4"><b>Name</b></font></p>
    161 
    162 
    163 
    164 
    165 
    166       </td>
    167 
    168 
    169 
    170 
    171 
    172       <td width="4%">
    173      
    174      
    175      
    176      
    177      
    178       <p><font size="4"><b>I/O</b></font></p>
    179 
    180 
    181 
    182 
    183 
    184       </td>
    185 
    186 
    187 
    188 
    189 
    190       <td width="9%">
    191      
    192      
    193      
    194      
    195      
    196       <p><font size="4"><b>Format</b></font></p>
    197 
    198 
    199 
    200 
    201 
    202       </td>
    203 
    204 
    205 
    206 
    207 
    208       <td colspan="1" width="67%">
    209      
    210      
    211      
    212      
    213      
    214       <p><font size="4"><b>Description/contents</b></font></p>
    215 
    216 
    217 
    218 
    219 
    220       </td>
    221 
    222 
    223 
    224 
    225 
    226     </tr>
    227 
    228 
    229 
    230 
    231 
    232     <tr valign="top">
    233 
    234 
    235 
    236 
    237 
    238       <td style="text-align: center;" width="8%"> 11<br>
    239 
    240 
    241 
    242 
    243 
    244       </td>
    245 
    246 
    247 
    248 
    249 
    250       <td width="12%">
    251      
    252      
    253      
    254      
    255      
    256       <p><a name="PARIN"></a>PARIN</p>
    257 
    258 
    259 
    260 
    261 
    262       </td>
    263 
    264 
    265 
    266 
    267 
    268       <td width="4%">
    269      
    270      
    271      
    272      
    273      
    274       <p align="center">I</p>
    275 
    276 
    277 
    278 
    279 
    280       </td>
    281 
    282 
    283 
    284 
    285 
    286       <td style="width: 9%;">
    287      
    288      
    289      
    290      
    291      
    292       <p>ASCII/&nbsp; <br>
    293 
    294 
    295 
    296 
    297 
    298 NAMELIST</p>
    299 
    300 
    301 
    302 
    303 
    304       </td>
    305 
    306 
    307 
    308 
    309 
    310       <td colspan="1" width="67%">
    311      
    312      
    313      
    314      
    315      
    316       <p><font color="#000000">Parameter for model steering. This file
     73<br></font>
     74<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>
     75<td width="12%"> <p><font size="4"><b>Name</b></font></p>
     76</td> <td width="4%"> <p><font size="4"><b>I/O</b></font></p>
     77</td> <td width="9%"> <p><font size="4"><b>Format</b></font></p>
     78</td> <td colspan="1" width="67%"> <p><font size="4"><b>Description/contents</b></font></p>
     79</td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> 11<br> </td>
     80<td width="12%"> <p><a name="PARIN"></a>PARIN</p>
     81</td> <td width="4%"> <p align="center">I</p>
     82</td> <td style="width: 9%;"> <p>ASCII/&nbsp;
     83<br>NAMELIST</p> </td> <td colspan="1" width="67%"> <p><font color="#000000">Parameter
     84for model steering. This file
    31785is needed by the model in each case. Its content and structure is
    31886described in detail in</font> <a href="chapter_4.0.html">chapter
    319874.0</a>. <a href="chapter_4.4.html">Chapter
    320 4.4</a> <font color="#000000">shows a simple example. </font> </p>
    321 
    322 
    323 
    324 
    325 
    326      
    327      
    328      
    329      
    330      
    331 
    332 
    333 
    334 
    335       </td>
    336 
    337 
    338 
    339 
    340 
    341     </tr>
    342 
    343 
    344 
    345 
    346 
    347     <tr valign="top">
    348 
    349 
    350 
    351 
    352 
    353       <td style="text-align: center;" width="8%">
    354      
    355      
    356      
    357      
    358      
    359       <p align="center">13</p>
    360 
    361 
    362 
    363 
    364 
    365       </td>
    366 
    367 
    368 
    369 
    370 
    371       <td width="12%">
    372      
    373      
    374      
    375      
    376      
    377       <p><a name="BININ"></a>BININ/</p>
    378 
    379 
    380 
    381 
    382 
    383       </td>
    384 
    385 
    386 
    387 
    388 
    389       <td width="4%">
    390      
    391      
    392      
    393      
    394      
    395       <p align="center">I</p>
    396 
    397 
    398 
    399 
    400 
    401       </td>
    402 
    403 
    404 
    405 
    406 
    407       <td width="9%">
    408      
    409      
    410      
    411      
    412      
    413       <p>Binary</p>
    414 
    415 
    416 
    417 
    418 
    419       </td>
    420 
    421 
    422 
    423 
    424 
    425       <td colspan="1" width="67%">
    426      
    427      
    428      
    429      
    430      
    431       <p>Binary data, which are read in by the model at the beginning
     884.4</a> <font color="#000000">shows a simple
     89example. </font> </p> </td> </tr> <tr valign="top"> <td style="text-align: center;" width="8%"> <p align="center">13</p> </td>
     90<td width="12%"> <p><a name="BININ"></a>BININ/</p>
     91</td> <td width="4%"> <p align="center">I</p>
     92</td> <td width="9%"> <p>Binary</p> </td>
     93<td colspan="1" width="67%"> <p>Binary data,
     94which are read in by the model at the beginning
    43295of a restart run (see <a href="chapter_3.3.html">chapter
    433 3.3</a>). The appropriate file must have been written by the preceding
     963.3</a>). The appropriate file must have been written by the
     97preceding
    43498job of the job chain (see <a href="#BINOUT">BINOUT</a>).
    43599This file contains the initial parameters (see <a href="chapter_4.1.html">chapter
    436 4.1</a>) of the job chain, arrays of the prognostic and diagnostic
     1004.1</a>) of the job chain, arrays of the prognostic and
     101diagnostic
    437102variables as well as those parameters and variables for plots of
    438103horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>),
    … …  
    441106reads its own file and the file content is processor-dependent. The
    442107number of processors which can be used must not be changed during a job
    443 chain and/or if a job chain is continued.&nbsp; </p>
    444 
    445 
    446 
    447 
    448 
    449      
    450      
    451      
    452      
    453      
    454       <p>Knowledge of the file structure is usually not necessary,
     108chain and/or if a job chain is continued.&nbsp; </p> <p>Knowledge
     109of the file structure is usually not necessary,
    455110because the file is produced and also read again by the model, but it
    456111can be useful for error determination in case of read errors .
    457112Therefore the file structure is described in the following.&nbsp; </p>
    458 
    459 
    460 
    461 
    462 
    463      
    464      
    465      
    466      
    467      
    468       <p>The first record of this file contains a version number (ten
     113<p>The first record of this file contains a version number (ten
    469114character string) of the subroutine, which, which output the data that
    470115follows (write_var_list.f90). This number has to
    … …  
    472117(read_var_list.f90) in case of a restart run. Otherwise the model run
    473118is aborted. Version numbers are changed whenever new code revisions
    474 require a change of the file format.&nbsp; </p>
    475 
    476 
    477 
    478 
    479 
    480      
    481      
    482      
    483      
    484      
    485       <p>Starting from the second record, all initial parameters follow
     119require a change of the file format.&nbsp; </p> <p>Starting
     120from the second record, all initial parameters follow
    486121(exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>),
    487122whereby each parameter fills two records. In the first record the name
    … …  
    493128and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
    494129If a variable with unknown name is found the model run is
    495 aborted.&nbsp; </p>
    496 
    497 
    498 
    499 
    500 
    501      
    502      
    503      
    504      
    505      
    506       <p>At the end of the initial parameters a record with the string "<i>***
    507 end ***</i>"follows (filled up with trailing blanks up to a length of
    508 30 characters).&nbsp; </p>
    509 
    510 
    511 
    512 
    513 
    514      
    515      
    516      
    517      
    518      
    519       <p>Afterwards the fields of the prognostic and diagnostic
     130aborted.&nbsp; </p> <p>At the end of the initial
     131parameters a record with the string "<i>***
     132end ***</i>"follows (filled up with trailing blanks up to a
     133length of
     13430 characters).&nbsp; </p> <p>Afterwards the fields
     135of the prognostic and diagnostic
    520136variables follow. This part of the file also begins with a record
    521137consisting of a character string of length 10, which contains the
    522138version number of the subroutine that wrote the arrays that follow
    523139(write_3d_binary.f90). It must agree with the number of the reading
    524 subroutine (read_3d_binary.f90).&nbsp; </p>
    525 
    526 
    527 
    528 
    529 
    530      
    531      
    532      
    533      
    534      
    535       <p>The following record contains the number of processors which
     140subroutine (read_3d_binary.f90).&nbsp; </p> <p>The
     141following record contains the number of processors which
    536142were used in the model run producing this file, the processor ID of the
    537143special processor, which creates the file, as well as the lower and
    … …  
    541147particular on parallel computers, because the jobs of a job chain
    542148always have to use the same number of processors and the same virtual
    543 processor grid.&nbsp; </p>
    544 
    545 
    546 
    547 
    548 
    549      
    550      
    551      
    552      
    553      
    554       <p>After these tests the individual arrays as well as parameters
     149processor grid.&nbsp; </p> <p>After these tests the
     150individual arrays as well as parameters
    555151and variables for plots of horizontally averaged vertical profiles
    556152follow. Like the initialization parameters, they consist of two
    … …  
    561157the plot and the respective variables are only read in if for the run
    562158parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
    563 = <i>.TRUE</i> is selected, otherwise they will be skipped.&nbsp; </p>
    564 
    565 
    566 
    567 
    568 
    569      
    570      
    571      
    572      
    573      
    574       <p>At the end of the file there has to be a record with the
    575 character string "<span style="font-style: italic;"></span><i>*** end
     159= <i>.TRUE</i> is selected, otherwise they will be
     160skipped.&nbsp; </p> <p>At the end of the file there
     161has to be a record with the
     162character string "<span style="font-style: italic;"></span><i>***
     163end
    576164***</i>"(filled up with trailing blanks up to a length of 20
    577 characters).</p>
    578 
    579 
    580 
    581 
    582 
    583       </td>
    584 
    585 
    586 
    587 
    588 
    589     </tr>
    590 
    591 
    592 
    593 
    594 
    595     <tr valign="top">
    596 
    597 
    598 
    599 
    600 
    601       <td style="text-align: center;" width="8%">
    602      
    603      
    604      
    605      
    606      
    607       <p align="center">14</p>
    608 
    609 
    610 
    611 
    612 
    613       </td>
    614 
    615 
    616 
    617 
    618 
    619       <td width="12%">
    620      
    621      
    622      
    623      
    624      
    625       <p><a name="BINOUT"></a>BINOUT/</p>
    626 
    627 
    628 
    629 
    630 
    631       </td>
    632 
    633 
    634 
    635 
    636 
    637       <td width="4%">
    638      
    639      
    640      
    641      
    642      
    643       <p align="center">O</p>
    644 
    645 
    646 
    647 
    648 
    649       </td>
    650 
    651 
    652 
    653 
    654 
    655       <td width="9%">
    656      
    657      
    658      
    659      
    660      
    661       <p>Binary</p>
    662 
    663 
    664 
    665 
    666 
    667       </td>
    668 
    669 
    670 
    671 
    672 
    673       <td colspan="1" width="67%">
    674      
    675      
    676      
    677      
    678      
    679       <p>Binary data, which are written by the model at the end of the
     165characters).</p> </td> </tr> <tr valign="top">
     166<td style="text-align: center;" width="8%"> <p align="center">14</p> </td> <td width="12%">
     167<p><a name="BINOUT"></a>BINOUT/</p> </td>
     168<td width="4%"> <p align="center">O</p>
     169</td> <td width="9%"> <p>Binary</p> </td>
     170<td colspan="1" width="67%"> <p>Binary data,
     171which are written by the model at the end of the
    680172run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
    681 3.3</a>) for the initialization. This output file is then read in as
     1733.3</a>) for the initialization. This output file is then read in
     174as
    682175file <a href="#BININ">BININ</a>.
    683176It contains the initial parameters (see <a href="chapter_4.1.html">chapter
    684 4.1</a>) of the model run, arrays of the prognostic and diagnostic
     1774.1</a>) of the model run, arrays of the prognostic and
     178diagnostic
    685179variables as well as those parameters determined so far during a job
    686180chain and variables for plots of horizontally averaged vertical
    … …  
    690184processor-dependent. A specification of the file format can be found in
    691185the
    692 description of the file <a href="#BININ">BININ</a>.&nbsp; </p>
    693 
    694 
    695 
    696 
    697 
    698      
    699      
    700      
    701      
    702      
    703       <p>The file BINOUT is written by the model only if, with the help
    704 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
     186description of the file <a href="#BININ">BININ</a>.&nbsp;
     187</p> <p>The file BINOUT is written by the model only if,
     188with the help
     189of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is
     190assigned for the
    705191environment
    706192variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span>
    707193(see <a href="chapter_3.3.html">chapter
    708 3.3</a>).&nbsp; </p>
    709 
    710 
    711 
    712 
    713 
    714      
    715      
    716      
    717      
    718      
    719       <p>With large grid point numbers the file BINOUT (or the
     1943.3</a>).&nbsp; </p> <p>With large grid point
     195numbers the file BINOUT (or the
    720196files residing in directory BINOUT/) will be very large and should
    721197be stored (if available) on the archive system of the remote computer.</p>
    722 
    723 
    724 
    725 
    726 
    727       </td>
    728 
    729 
    730 
    731 
    732 
    733     </tr>
    734 
    735 
    736 
    737 
    738 
    739     <tr>
    740 
    741 
    742 
    743 
    744 
    745       <td style="vertical-align: top; text-align: center;">15<br>
    746 
    747 
    748 
    749 
    750 
    751       </td>
    752 
    753 
    754 
    755 
    756 
    757       <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td>
    758 
    759 
    760 
    761 
    762 
    763       <td style="vertical-align: top;">O</td>
    764 
    765 
    766 
    767 
    768 
    769       <td style="vertical-align: top;">Ascii</td>
    770 
    771 
    772 
    773 
    774 
    775       <td colspan="1" width="67%">
    776      
    777      
    778      
    779      
    780      
    781       <p>This file contains the so-called time step control output of
     198</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">15<br>
     199</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
     200the so-called time step control output of
    782201the model. At certain temporal intervals, which are described by the
    783202run
    … …  
    787206file. Additionally, such a control line is always written, whenever the
    788207time step of the model changes. All data and quantities always refer to
    789 the entire model domain.&nbsp; </p>
    790 
    791 
    792 
    793 
    794 
    795      
    796      
    797      
    798      
    799      
    800       <p>If the 1D-model is switched on for the initialization of the
     208the entire model domain.&nbsp; </p> <p>If the
     2091D-model is switched on for the initialization of the
    8012103D-models, then control lines are likewise written into this file at
    802211certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>).&nbsp;
    803       </p>
    804 
    805 
    806 
    807 
    808 
    809      
    810      
    811      
    812      
    813      
    814       <p>By default, the file RUN_CONTROL only lists information
     212</p> <p>By default, the file RUN_CONTROL only lists
     213information
    815214about the selected model parameters at the beginning of the
    816215initial run. These informations are written at the beginnning of a run.
    … …  
    821220it can be achieved that this information is also written at the
    822221beginning of the file RUN_CONTROL at restart runs.&nbsp; </p>
    823 
    824 
    825 
    826 
    827 
    828      
    829      
    830      
    831      
    832      
    833       <p>The individual columns of the 1D - time step control output
     222<p>The individual columns of the 1D - time step control output
    834223have the following meaning (listed by the respective heading of the
    835224appropriate
    836 column in the file):&nbsp; <br>
    837 
    838 
    839 
    840 
    841 
    842       </p>
    843 
    844 
    845 
    846 
    847 
    848      
    849      
    850      
    851      
    852      
    853       <table style="text-align: left; width: 100%;" cellpadding="2">
    854 
    855 
    856 
    857 
    858 
    859         <tbody>
    860 
    861 
    862 
    863 
    864 
    865           <tr>
    866 
    867 
    868 
    869 
    870 
    871             <td style="vertical-align: top;">ITER.</td>
    872 
    873 
    874 
    875 
    876 
    877             <td style="vertical-align: top;">Number of time steps
    878 accomplished so far</td>
    879 
    880 
    881 
    882 
    883 
    884           </tr>
    885 
    886 
    887 
    888 
    889 
    890           <tr>
    891 
    892 
    893 
    894 
    895 
    896             <td style="vertical-align: top;">HH:MM:SS</td>
    897 
    898 
    899 
    900 
    901 
    902             <td style="vertical-align: top;">Time (in hours: minutes:
    903 seconds)</td>
    904 
    905 
    906 
    907 
    908 
    909           </tr>
    910 
    911 
    912 
    913 
    914 
    915           <tr>
    916 
    917 
    918 
    919 
    920 
    921             <td style="vertical-align: top;">DT</td>
    922 
    923 
    924 
    925 
    926 
    927             <td style="vertical-align: top;">Time step (in s)</td>
    928 
    929 
    930 
    931 
    932 
    933           </tr>
    934 
    935 
    936 
    937 
    938 
    939           <tr>
    940 
    941 
    942 
    943 
    944 
    945             <td style="vertical-align: top;">UMAX</td>
    946 
    947 
    948 
    949 
    950 
    951             <td style="vertical-align: top;">Maximum absolute wind
     225column in the file):&nbsp; <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2">
     226<tbody> <tr> <td style="vertical-align: top;">ITER.</td>
     227<td style="vertical-align: top;">Number of time steps
     228accomplished so far</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (in hours: minutes:
     229seconds)</td> </tr> <tr> <td style="vertical-align: top;">DT</td> <td style="vertical-align: top;">Time step (in s)</td> </tr>
     230<tr> <td style="vertical-align: top;">UMAX</td>
     231<td style="vertical-align: top;">Maximum absolute wind
    952232velocity
    953 (u-component) (in m/s)</td>
    954 
    955 
    956 
    957 
    958 
    959           </tr>
    960 
    961 
    962 
    963 
    964 
    965           <tr>
    966 
    967 
    968 
    969 
    970 
    971             <td style="vertical-align: top;">VMAX</td>
    972 
    973 
    974 
    975 
    976 
    977             <td style="vertical-align: top;">Maximum absolute wind
     233(u-component) (in m/s)</td> </tr> <tr> <td style="vertical-align: top;">VMAX</td> <td style="vertical-align: top;">Maximum absolute wind
    978234velocity
    979 (v-component) (in m/s)</td>
    980 
    981 
    982 
    983 
    984 
    985           </tr>
    986 
    987 
    988 
    989 
    990 
    991           <tr>
    992 
    993 
    994 
    995 
    996 
    997             <td style="vertical-align: top;">U *</td>
    998 
    999 
    1000 
    1001 
    1002 
    1003             <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td>
    1004 
    1005 
    1006 
    1007 
    1008 
    1009           </tr>
    1010 
    1011 
    1012 
    1013 
    1014 
    1015           <tr>
    1016 
    1017 
    1018 
    1019 
    1020 
    1021             <td style="vertical-align: top;">ALPHA</td>
    1022 
    1023 
    1024 
    1025 
    1026 
    1027             <td style="vertical-align: top;">Angle of the wind vector
     235(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>
     236<tr> <td style="vertical-align: top;">ALPHA</td>
     237<td style="vertical-align: top;">Angle of the wind vector
    1028238(to the x-axis) at the top of the
    1029239Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td>
    1030 
    1031 
    1032 
    1033 
    1034 
    1035           </tr>
    1036 
    1037 
    1038 
    1039 
    1040 
    1041           <tr>
    1042 
    1043 
    1044 
    1045 
    1046 
    1047             <td style="vertical-align: middle;">ENERG.</td>
    1048 
    1049 
    1050 
    1051 
    1052 
    1053             <td style="vertical-align: top;">Kinetic energy of the
     240</tr> <tr> <td style="vertical-align: middle;">ENERG.</td>
     241<td style="vertical-align: top;">Kinetic energy of the
    10542421D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
    1055 averaged over all grid points</td>
    1056 
    1057 
    1058 
    1059 
    1060 
    1061           </tr>
    1062 
    1063 
    1064 
    1065 
    1066 
    1067        
    1068        
    1069        
    1070        
    1071        
    1072         </tbody>
    1073      
    1074      
    1075      
    1076      
    1077      
    1078       </table>
    1079 
    1080 
    1081 
    1082 
    1083 
    1084      
    1085      
    1086      
    1087      
    1088      
    1089       <p>&nbsp;
     243averaged over all grid points</td> </tr> </tbody> </table>
     244<p>&nbsp;
    1090245The individual columns of the 3D - time step control output
    1091246have the following meaning (listed by the respective heading of the
    1092247appropriate
    1093 column in the file):<br>
    1094 
    1095 
    1096 
    1097 
    1098 
    1099       </p>
    1100 
    1101 
    1102 
    1103 
    1104 
    1105      
    1106      
    1107      
    1108      
    1109      
    1110       <table style="text-align: left; width: 100%;" cellpadding="2">
    1111 
    1112 
    1113 
    1114 
    1115 
    1116         <tbody>
    1117 
    1118 
    1119 
    1120 
    1121 
    1122           <tr>
    1123 
    1124 
    1125 
    1126 
    1127 
    1128             <td style="vertical-align: top;">RUN</td>
    1129 
    1130 
    1131 
    1132 
    1133 
    1134             <td style="vertical-align: top;">Serial-number of the job
     248column in the file):<br> </p> <table style="text-align: left; width: 100%;" cellpadding="2">
     249<tbody> <tr> <td style="vertical-align: top;">RUN</td>
     250<td style="vertical-align: top;">Serial-number of the job
    1135251in the job chain. The initial
    1136252run has the number 0, restart runs accordingly have larger numbers.</td>
    1137 
    1138 
    1139 
    1140 
    1141 
    1142           </tr>
    1143 
    1144 
    1145 
    1146 
    1147 
    1148           <tr>
    1149 
    1150 
    1151 
    1152 
    1153 
    1154             <td style="vertical-align: top;">ITER.</td>
    1155 
    1156 
    1157 
    1158 
    1159 
    1160             <td style="vertical-align: top;">Number of time steps
     253</tr> <tr> <td style="vertical-align: top;">ITER.</td>
     254<td style="vertical-align: top;">Number of time steps
    1161255accomplished since starting time t=0 of
    1162 the initial run.</td>
    1163 
    1164 
    1165 
    1166 
    1167 
    1168           </tr>
    1169 
    1170 
    1171 
    1172 
    1173 
    1174           <tr>
    1175 
    1176 
    1177 
    1178 
    1179 
    1180             <td style="vertical-align: top;">HH:MM:SS</td>
    1181 
    1182 
    1183 
    1184 
    1185 
    1186             <td style="vertical-align: top;">Time (<font color="#000000">in
    1187             </font>hours: minutes:
     256the initial run.</td> </tr> <tr> <td style="vertical-align: top;">HH:MM:SS</td> <td style="vertical-align: top;">Time (<font color="#000000">in
     257</font>hours: minutes:
    1188258seconds) since starting time t=0 of the
    1189 initial run.</td>
    1190 
    1191 
    1192 
    1193 
    1194 
    1195           </tr>
    1196 
    1197 
    1198 
    1199 
    1200 
    1201           <tr>
    1202 
    1203 
    1204 
    1205 
    1206 
    1207             <td style="vertical-align: top;">DT (E)</td>
    1208 
    1209 
    1210 
    1211 
    1212 
    1213             <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
     259initial 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
    1214260following character indicates whether the
    1215261time
    … …  
    1219265which indicates with which time step procedure the changed time step
    1220266was accomplished (<span style="font-family: monospace;">L:</span>
    1221 Leapfrog, <span style="font-family: monospace;">E:</span> Euler). This
     267Leapfrog, <span style="font-family: monospace;">E:</span>
     268Euler). This
    1222269does
    1223 not apply for the default Runge-Kutta timestep scheme.</td>
    1224 
    1225 
    1226 
    1227 
    1228 
    1229           </tr>
    1230 
    1231 
    1232 
    1233 
    1234 
    1235           <tr>
    1236 
    1237 
    1238 
    1239 
    1240 
    1241             <td style="vertical-align: top;">UMAX</td>
    1242 
    1243 
    1244 
    1245 
    1246 
    1247             <td style="vertical-align: top;">Maximum absolute wind
    1248 velocity (u-component) (<font color="#000000">in </font>m/s). If at
     270not apply for the default Runge-Kutta timestep scheme.</td> </tr>
     271<tr> <td style="vertical-align: top;">UMAX</td>
     272<td style="vertical-align: top;">Maximum absolute wind
     273velocity (u-component) (<font color="#000000">in </font>m/s).
     274If at
    1249275the
    1250276appropriate output time a random disturbance was added to the
    1251277horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
    1252278the character D will appear directly after the velocity value.</td>
    1253 
    1254 
    1255 
    1256 
    1257 
    1258           </tr>
    1259 
    1260 
    1261 
    1262 
    1263 
    1264           <tr>
    1265 
    1266 
    1267 
    1268 
    1269 
    1270             <td style="vertical-align: top;">VMAX</td>
    1271 
    1272 
    1273 
    1274 
    1275 
    1276             <td style="vertical-align: top;">Maximum absolute wind
    1277 velocity (v-component) (<font color="#000000">in </font>m/s). If at
     279</tr> <tr> <td style="vertical-align: top;">VMAX</td>
     280<td style="vertical-align: top;">Maximum absolute wind
     281velocity (v-component) (<font color="#000000">in </font>m/s).
     282If at
    1278283the
    1279284appropriate output time a random disturbance was added to the
    1280285horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
    1281286the character D will appear directly after the velocity value.</td>
    1282 
    1283 
    1284 
    1285 
    1286 
    1287           </tr>
    1288 
    1289 
    1290 
    1291 
    1292 
    1293           <tr>
    1294 
    1295 
    1296 
    1297 
    1298 
    1299             <td style="vertical-align: top;">WMAX</td>
    1300 
    1301 
    1302 
    1303 
    1304 
    1305             <td style="vertical-align: top;">Maximum absolute wind
     287</tr> <tr> <td style="vertical-align: top;">WMAX</td>
     288<td style="vertical-align: top;">Maximum absolute wind
    1306289velocity (w-component) (<font color="#000000">in </font>m/s).</td>
    1307 
    1308 
    1309 
    1310 
    1311 
    1312           </tr>
    1313 
    1314 
    1315 
    1316 
    1317 
    1318           <tr>
    1319 
    1320 
    1321 
    1322 
    1323 
    1324             <td style="vertical-align: top;">U *</td>
    1325 
    1326 
    1327 
    1328 
    1329 
    1330             <td style="vertical-align: top;">Horizontal average of the
     290</tr> <tr> <td style="vertical-align: top;">U
     291*</td> <td style="vertical-align: top;">Horizontal
     292average of the
    1331293friction velocity (<font color="#000000">in </font>m/s).</td>
    1332 
    1333 
    1334 
    1335 
    1336 
    1337           </tr>
    1338 
    1339 
    1340 
    1341 
    1342 
    1343           <tr>
    1344 
    1345 
    1346 
    1347 
    1348 
    1349             <td style="vertical-align: top;">W *</td>
    1350 
    1351 
    1352 
    1353 
    1354 
    1355             <td style="vertical-align: top;">Convective velocity scale
    1356 (<font color="#000000">in </font>m/s). The assumed boundary layer
    1357 height is determined via the heat flux minimum criterion.</td>
    1358 
    1359 
    1360 
    1361 
    1362 
    1363           </tr>
    1364 
    1365 
    1366 
    1367 
    1368 
    1369           <tr>
    1370 
    1371 
    1372 
    1373 
    1374 
    1375             <td style="vertical-align: top;">THETA *</td>
    1376 
    1377 
    1378 
    1379 
    1380 
    1381             <td style="vertical-align: top;">Characteristic temperature
     294</tr> <tr> <td style="vertical-align: top;">W
     295*</td> <td style="vertical-align: top;">Convective
     296velocity scale
     297(<font color="#000000">in </font>m/s). The assumed
     298boundary layer
     299height is determined via the heat flux minimum criterion.</td> </tr>
     300<tr> <td style="vertical-align: top;">THETA *</td>
     301<td style="vertical-align: top;">Characteristic
     302temperature
    1382303of the Prandtl - layer (<font color="#000000">in </font>K).</td>
    1383 
    1384 
    1385 
    1386 
    1387 
    1388           </tr>
    1389 
    1390 
    1391 
    1392 
    1393 
    1394           <tr>
    1395 
    1396 
    1397 
    1398 
    1399 
    1400             <td style="vertical-align: top;">Z_I</td>
    1401 
    1402 
    1403 
    1404 
    1405 
    1406             <td style="vertical-align: top;">Height of the convective
    1407 boundary layer (<font color="#000000">in </font>m), determined via
    1408 the criterion of the heat flux minimum.</td>
    1409 
    1410 
    1411 
    1412 
    1413 
    1414           </tr>
    1415 
    1416 
    1417 
    1418 
    1419 
    1420           <tr>
    1421 
    1422 
    1423 
    1424 
    1425 
    1426             <td style="vertical-align: middle;">ENERG.</td>
    1427 
    1428 
    1429 
    1430 
    1431 
    1432             <td style="vertical-align: top;">Average resolved total
     304</tr> <tr> <td style="vertical-align: top;">Z_I</td>
     305<td style="vertical-align: top;">Height of the convective
     306boundary layer (<font color="#000000">in </font>m),
     307determined via
     308the criterion of the heat flux minimum.</td> </tr> <tr>
     309<td style="vertical-align: middle;">ENERG.</td> <td style="vertical-align: top;">Average resolved total
    1433310energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
    1434 normalized with the total number of grid points.</td>
    1435 
    1436 
    1437 
    1438 
    1439 
    1440           </tr>
    1441 
    1442 
    1443 
    1444 
    1445 
    1446           <tr>
    1447 
    1448 
    1449 
    1450 
    1451 
    1452             <td style="vertical-align: middle;">DISTENERG</td>
    1453 
    1454 
    1455 
    1456 
    1457 
    1458             <td style="vertical-align: top;">Average resolved
    1459 disturbance energy of flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
    1460 normalized with the total number of grid points.</td>
    1461 
    1462 
    1463 
    1464 
    1465 
    1466           </tr>
    1467 
    1468 
    1469 
    1470 
    1471 
    1472           <tr>
    1473 
    1474 
    1475 
    1476 
    1477 
    1478             <td style="vertical-align: top;">DIVOLD</td>
    1479 
    1480 
    1481 
    1482 
    1483 
    1484             <td style="vertical-align: top;"><font color="#000000">Divergence
     311normalized with the total number of grid points.</td> </tr>
     312<tr> <td style="vertical-align: middle;">DISTENERG</td>
     313<td style="vertical-align: top;">Average resolved
     314disturbance energy of flow field (<font color="#000000">in
     315</font>m<sup>2</sup>/s<sup>2</sup>),
     316normalized with the total number of grid points.</td> </tr>
     317<tr> <td style="vertical-align: top;">DIVOLD</td>
     318<td style="vertical-align: top;"><font color="#000000">Divergence
    1485319of the velocity field (sum of
    1486 the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) before call of the pressure solver,
     320the absolute values) (</font><font color="#000000">in
     321</font><font color="#000000">1/s) before call of the
     322pressure solver,
    1487323normalized with the total number of grid points.</font></td>
    1488 
    1489 
    1490 
    1491 
    1492 
    1493           </tr>
    1494 
    1495 
    1496 
    1497 
    1498 
    1499           <tr>
    1500 
    1501 
    1502 
    1503 
    1504 
    1505             <td style="vertical-align: top;">DIVNEW</td>
    1506 
    1507 
    1508 
    1509 
    1510 
    1511             <td style="vertical-align: top;"><font color="#000000">Divergence
     324</tr> <tr> <td style="vertical-align: top;">DIVNEW</td>
     325<td style="vertical-align: top;"><font color="#000000">Divergence
    1512326of the velocity field (sum of
    1513 the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) after call of the pressure solver, normalized</font>
    1514 with the total number of grid points.</td>
    1515 
    1516 
    1517 
    1518 
    1519 
    1520           </tr>
    1521 
    1522 
    1523 
    1524 
    1525 
    1526           <tr>
    1527 
    1528 
    1529 
    1530 
    1531 
    1532             <td style="vertical-align: top;">UMAX (KJI)</td>
    1533 
    1534 
    1535 
    1536 
    1537 
    1538             <td style="vertical-align: top;">Indices of the grid point
     327the absolute values) (</font><font color="#000000">in
     328</font><font color="#000000">1/s) after call of the
     329pressure solver, normalized</font>
     330with the total number of grid points.</td> </tr> <tr>
     331<td style="vertical-align: top;">UMAX (KJI)</td> <td style="vertical-align: top;">Indices of the grid point
    1539332with the maximum absolute
    1540 u-component of the wind velocity (sequence: k, j, i).</td>
    1541 
    1542 
    1543 
    1544 
    1545 
    1546           </tr>
    1547 
    1548 
    1549 
    1550 
    1551 
    1552           <tr>
    1553 
    1554 
    1555 
    1556 
    1557 
    1558             <td style="vertical-align: top;">VMAX (KJI)</td>
    1559 
    1560 
    1561 
    1562 
    1563 
    1564             <td style="vertical-align: top;">Indices of the grid point
     333u-component of the wind velocity (sequence: k, j, i).</td> </tr>
     334<tr> <td style="vertical-align: top;">VMAX (KJI)</td>
     335<td style="vertical-align: top;">Indices of the grid point
    1565336with the maximum absolute
    1566 v-component of the wind velocity (sequence: k, j, i).</td>
    1567 
    1568 
    1569 
    1570 
    1571 
    1572           </tr>
    1573 
    1574 
    1575 
    1576 
    1577 
    1578           <tr>
    1579 
    1580 
    1581 
    1582 
    1583 
    1584             <td style="vertical-align: top;">WMAX (KJI)</td>
    1585 
    1586 
    1587 
    1588 
    1589 
    1590             <td style="vertical-align: top;">Indices of the grid point
     337v-component of the wind velocity (sequence: k, j, i).</td> </tr>
     338<tr> <td style="vertical-align: top;">WMAX (KJI)</td>
     339<td style="vertical-align: top;">Indices of the grid point
    1591340with the maximum absolute
    1592 w-component of the wind velocity (sequence: k, j, i).</td>
    1593 
    1594 
    1595 
    1596 
    1597 
    1598           </tr>
    1599 
    1600 
    1601 
    1602 
    1603 
    1604           <tr>
    1605 
    1606 
    1607 
    1608 
    1609 
    1610             <td style="vertical-align: top;">ADVECX</td>
    1611 
    1612 
    1613 
    1614 
    1615 
    1616             <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
     341w-component of the wind velocity (sequence: k, j, i).</td> </tr>
     342<tr> <td style="vertical-align: top;">ADVECX</td>
     343<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
    1617344coordinate system has been moved in
    1618345x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
    1619 
    1620 
    1621 
    1622 
    1623 
    1624           </tr>
    1625 
    1626 
    1627 
    1628 
    1629 
    1630           <tr>
    1631 
    1632 
    1633 
    1634 
    1635 
    1636             <td style="vertical-align: top;">ADVECY</td>
    1637 
    1638 
    1639 
    1640 
    1641 
    1642             <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
     346</tr> <tr> <td style="vertical-align: top;">ADVECY</td>
     347<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
    1643348coordinate system has been moved in
    1644349y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
    1645 
    1646 
    1647 
    1648 
    1649 
    1650           </tr>
    1651 
    1652 
    1653 
    1654 
    1655 
    1656        
    1657        
    1658        
    1659        
    1660        
    1661         </tbody>
    1662      
    1663      
    1664      
    1665      
    1666      
    1667       </table>
    1668 
    1669 
    1670 
    1671 
    1672 
    1673       </td>
    1674 
    1675 
    1676 
    1677 
    1678 
    1679     </tr>
    1680 
    1681 
    1682 
    1683 
    1684 
    1685     <tr>
    1686 
    1687 
    1688 
    1689 
    1690 
    1691       <td style="vertical-align: top; text-align: center;">16<br>
    1692 
    1693 
    1694 
    1695 
    1696 
    1697       </td>
    1698 
    1699 
    1700 
    1701 
    1702 
    1703       <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL
    1704       </td>
    1705 
    1706 
    1707 
    1708 
    1709 
    1710       <td style="vertical-align: top;">O<br>
    1711 
    1712 
    1713 
    1714 
    1715 
    1716       </td>
    1717 
    1718 
    1719 
    1720 
    1721 
    1722       <td style="vertical-align: top;">Ascii<br>
    1723 
    1724 
    1725 
    1726 
    1727 
    1728       </td>
    1729 
    1730 
    1731 
    1732 
    1733 
    1734       <td style="vertical-align: top;">This file contains horizontally
     350</tr> </tbody> </table> </td> </tr> <tr>
     351<td style="vertical-align: top; text-align: center;">16<br>
     352</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
    1735353(and possibly temporally)
    1736354averaged vertical profiles of some model variables. The quantities
    … …  
    1745363the respective subdomain (see <a href="chapter_4.3.html#region">region</a>)
    1746364appears in the header of the respective table. <br>
    1747 
    1748 
    1749 
    1750 
    1751 
    1752365In each case the tables consist of a header, followed by the
    1753366profiles arranged next to each other in columns. The header contains
    … …  
    1757370computer, date, time of the beginning of the run, name of the
    1758371subdomain, output time, kind of averaging). On the u-v-level the
    1759 following columns are written: <br>
    1760 
    1761 
    1762 
    1763 
    1764 
    1765      
    1766      
    1767      
    1768      
    1769      
    1770       <table style="text-align: left; width: 100%;" cellpadding="2">
    1771 
    1772 
    1773 
    1774 
    1775 
    1776         <tbody>
    1777 
    1778 
    1779 
    1780 
    1781 
    1782           <tr>
    1783 
    1784 
    1785 
    1786 
    1787 
    1788             <td style="text-align: left; vertical-align: middle;">k<br>
    1789 
    1790 
    1791 
    1792 
    1793 
    1794             </td>
    1795 
    1796 
    1797 
    1798 
    1799 
    1800             <td style="text-align: left; vertical-align: middle;">Vertical
    1801 grid point index.</td>
    1802 
    1803 
    1804 
    1805 
    1806 
    1807           </tr>
    1808 
    1809 
    1810 
    1811 
    1812 
    1813           <tr>
    1814 
    1815 
    1816 
    1817 
    1818 
    1819             <td style="text-align: left; vertical-align: middle;">zu<br>
    1820 
    1821 
    1822 
    1823 
    1824 
    1825             </td>
    1826 
    1827 
    1828 
    1829 
    1830 
    1831             <td style="text-align: left; vertical-align: middle;">Height
     372following columns are written: <br> <table style="text-align: left; width: 100%;" cellpadding="2">
     373<tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br>
     374</td> <td style="text-align: left; vertical-align: middle;">Vertical
     375grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br>
     376</td> <td style="text-align: left; vertical-align: middle;">Height
    1832377of the grid point
    1833378level (<font color="#000000">in </font>m).</td>
    1834 
    1835 
    1836 
    1837 
    1838 
    1839           </tr>
    1840 
    1841 
    1842 
    1843 
    1844 
    1845           <tr>
    1846 
    1847 
    1848 
    1849 
    1850 
    1851             <td style="text-align: left; vertical-align: middle;">u<br>
    1852 
    1853 
    1854 
    1855 
    1856 
    1857             </td>
    1858 
    1859 
    1860 
    1861 
    1862 
    1863             <td style="text-align: left; vertical-align: middle;">u-component
     379</tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br>
     380</td> <td style="text-align: left; vertical-align: middle;">u-component
    1864381of the wind
    1865382velocity (<font color="#000000">in </font>m/s).</td>
    1866 
    1867 
    1868 
    1869 
    1870 
    1871           </tr>
    1872 
    1873 
    1874 
    1875 
    1876 
    1877           <tr>
    1878 
    1879 
    1880 
    1881 
    1882 
    1883             <td style="text-align: left; vertical-align: middle;">du<br>
    1884 
    1885 
    1886 
    1887 
    1888 
    1889             </td>
    1890 
    1891 
    1892 
    1893 
    1894 
    1895             <td style="text-align: left; vertical-align: middle;">Deviation
     383</tr> <tr> <td style="text-align: left; vertical-align: middle;">du<br>
     384</td> <td style="text-align: left; vertical-align: middle;">Deviation
    1896385of the
    1897386u-component from the initial profile at the
    1898 time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
    1899 
    1900 
    1901 
    1902 
    1903 
    1904           </tr>
    1905 
    1906 
    1907 
    1908 
    1909 
    1910           <tr>
    1911 
    1912 
    1913 
    1914 
    1915 
    1916             <td style="text-align: left; vertical-align: middle;">v<br>
    1917 
    1918 
    1919 
    1920 
    1921 
    1922             </td>
    1923 
    1924 
    1925 
    1926 
    1927 
    1928             <td style="text-align: left; vertical-align: middle;">v-component
     387time t=0 (initialization profile) (<font color="#000000">in
     388</font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br>
     389</td> <td style="text-align: left; vertical-align: middle;">v-component
    1929390of the wind
    1930391velocity (<font color="#000000">in </font>m/s).</td>
    1931 
    1932 
    1933 
    1934 
    1935 
    1936           </tr>
    1937 
    1938 
    1939 
    1940 
    1941 
    1942           <tr>
    1943 
    1944 
    1945 
    1946 
    1947 
    1948             <td style="text-align: left; vertical-align: middle;">dv<br>
    1949 
    1950 
    1951 
    1952 
    1953 
    1954             </td>
    1955 
    1956 
    1957 
    1958 
    1959 
    1960             <td style="text-align: left; vertical-align: middle;">Deviation
     392</tr> <tr> <td style="text-align: left; vertical-align: middle;">dv<br>
     393</td> <td style="text-align: left; vertical-align: middle;">Deviation
    1961394of the
    1962395v-component from the initial profile at the
    1963 time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
    1964 
    1965 
    1966 
    1967 
    1968 
    1969           </tr>
    1970 
    1971 
    1972 
    1973 
    1974 
    1975           <tr>
    1976 
    1977 
    1978 
    1979 
    1980 
    1981             <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    1982             <br>
    1983 
    1984 
    1985 
    1986 
    1987 
    1988             </td>
    1989 
    1990 
    1991 
    1992 
    1993 
    1994             <td style="text-align: left; vertical-align: middle;">Potential
     396time t=0 (initialization profile) (<font color="#000000">in
     397</font>m/s).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     398<br> </td> <td style="text-align: left; vertical-align: middle;">Potential
    1995399temperature (<font color="#000000">in </font>K).</td>
    1996 
    1997 
    1998 
    1999 
    2000 
    2001           </tr>
    2002 
    2003 
    2004 
    2005 
    2006 
    2007           <tr>
    2008 
    2009 
    2010 
    2011 
    2012 
    2013             <td style="text-align: left; vertical-align: middle;">dpt<br>
    2014 
    2015 
    2016 
    2017 
    2018 
    2019             </td>
    2020 
    2021 
    2022 
    2023 
    2024 
    2025             <td style="text-align: left; vertical-align: middle;">Deviation
     400</tr> <tr> <td style="text-align: left; vertical-align: middle;">dpt<br>
     401</td> <td style="text-align: left; vertical-align: middle;">Deviation
    2026402of potential
    2027403temperature from the initial profile at
    2028 the time t=0 (initialization profile) (<font color="#000000">in </font>K).</td>
    2029 
    2030 
    2031 
    2032 
    2033 
    2034           </tr>
    2035 
    2036 
    2037 
    2038 
    2039 
    2040           <tr>
    2041 
    2042 
    2043 
    2044 
    2045 
    2046             <td style="text-align: left; vertical-align: middle;">e<br>
    2047 
    2048 
    2049 
    2050 
    2051 
    2052             </td>
    2053 
    2054 
    2055 
    2056 
    2057 
    2058             <td style="text-align: left; vertical-align: middle;">Turbulent
     404the time t=0 (initialization profile) (<font color="#000000">in
     405</font>K).</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br>
     406</td> <td style="text-align: left; vertical-align: middle;">Turbulent
    2059407kinetic energy
    2060408(subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
    2061 
    2062 
    2063 
    2064 
    2065 
    2066           </tr>
    2067 
    2068 
    2069 
    2070 
    2071 
    2072           <tr>
    2073 
    2074 
    2075 
    2076 
    2077 
    2078             <td style="text-align: left; vertical-align: middle;">Km<br>
    2079 
    2080 
    2081 
    2082 
    2083 
    2084             </td>
    2085 
    2086 
    2087 
    2088 
    2089 
    2090             <td style="text-align: left; vertical-align: middle;">Turbulent
     409</tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br>
     410</td> <td style="text-align: left; vertical-align: middle;">Turbulent
    2091411diffusion
    2092412coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
    2093 
    2094 
    2095 
    2096 
    2097 
    2098           </tr>
    2099 
    2100 
    2101 
    2102 
    2103 
    2104           <tr>
    2105 
    2106 
    2107 
    2108 
    2109 
    2110             <td style="text-align: left; vertical-align: middle;">Kh<br>
    2111 
    2112 
    2113 
    2114 
    2115 
    2116             </td>
    2117 
    2118 
    2119 
    2120 
    2121 
    2122             <td style="text-align: left; vertical-align: middle;">Turbulent
     413</tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br>
     414</td> <td style="text-align: left; vertical-align: middle;">Turbulent
    2123415diffusion
    2124416coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
    2125 
    2126 
    2127 
    2128 
    2129 
    2130           </tr>
    2131 
    2132 
    2133 
    2134 
    2135 
    2136           <tr>
    2137 
    2138 
    2139 
    2140 
    2141 
    2142             <td style="text-align: left; vertical-align: middle;">l<br>
    2143 
    2144 
    2145 
    2146 
    2147 
    2148             </td>
    2149 
    2150 
    2151 
    2152 
    2153 
    2154             <td style="text-align: left; vertical-align: middle;">Mixing
     417</tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br>
     418</td> <td style="text-align: left; vertical-align: middle;">Mixing
    2155419length (<font color="#000000">in </font>m).</td>
    2156 
    2157 
    2158 
    2159 
    2160 
    2161           </tr>
    2162 
    2163 
    2164 
    2165 
    2166 
    2167           <tr>
    2168 
    2169 
    2170 
    2171 
    2172 
    2173             <td style="vertical-align: top;"><br>
    2174 
    2175 
    2176 
    2177 
    2178 
    2179             </td>
    2180 
    2181 
    2182 
    2183 
    2184 
    2185             <td style="vertical-align: top;"><br>
    2186 
    2187 
    2188 
    2189 
    2190 
    2191             </td>
    2192 
    2193 
    2194 
    2195 
    2196 
    2197           </tr>
    2198 
    2199 
    2200 
    2201 
    2202 
    2203        
    2204        
    2205        
    2206        
    2207        
    2208         </tbody>
    2209      
    2210      
    2211      
    2212      
    2213      
    2214       </table>
    2215 
    2216 
    2217 
    2218 
    2219 
    2220 On the w-level the following columns are written:<br>
    2221 
    2222 
    2223 
    2224 
    2225 
    2226       <br>
    2227 
    2228 
    2229 
    2230 
    2231 
    2232      
    2233      
    2234      
    2235      
    2236      
    2237       <table style="text-align: left; width: 100%;" cellpadding="2">
    2238 
    2239 
    2240 
    2241 
    2242 
    2243         <tbody>
    2244 
    2245 
    2246 
    2247 
    2248 
    2249           <tr>
    2250 
    2251 
    2252 
    2253 
    2254 
    2255             <td style="vertical-align: middle;">k<br>
    2256 
    2257 
    2258 
    2259 
    2260 
    2261             </td>
    2262 
    2263 
    2264 
    2265 
    2266 
    2267             <td style="vertical-align: middle;">Vertical grid point
    2268 index.</td>
    2269 
    2270 
    2271 
    2272 
    2273 
    2274           </tr>
    2275 
    2276 
    2277 
    2278 
    2279 
    2280           <tr>
    2281 
    2282 
    2283 
    2284 
    2285 
    2286             <td style="vertical-align: middle;">zw<br>
    2287 
    2288 
    2289 
    2290 
    2291 
    2292             </td>
    2293 
    2294 
    2295 
    2296 
    2297 
    2298             <td style="vertical-align: middle;">Height of the grid
     420</tr> <tr> <td style="vertical-align: top;"><br>
     421</td> <td style="vertical-align: top;"><br> </td>
     422</tr> </tbody> </table>
     423On the w-level the following columns are written:<br> <br>
     424<table style="text-align: left; width: 100%;" cellpadding="2">
     425<tbody> <tr> <td style="vertical-align: middle;">k<br>
     426</td> <td style="vertical-align: middle;">Vertical
     427grid point
     428index.</td> </tr> <tr> <td style="vertical-align: middle;">zw<br> </td> <td style="vertical-align: middle;">Height of the grid
    2299429point
    2300430level (<font color="#000000">in </font>m).</td>
    2301 
    2302 
    2303 
    2304 
    2305 
    2306           </tr>
    2307 
    2308 
    2309 
    2310 
    2311 
    2312           <tr>
    2313 
    2314 
    2315 
    2316 
    2317 
    2318             <td style="vertical-align: middle;">w'pt'</td>
    2319 
    2320 
    2321 
    2322 
    2323 
    2324             <td style="vertical-align: middle;">Vertical subgrid-scale
    2325 kinematic heat flux (<font color="#000000">in </font>K m/s).</td>
    2326 
    2327 
    2328 
    2329 
    2330 
    2331           </tr>
    2332 
    2333 
    2334 
    2335 
    2336 
    2337           <tr>
    2338 
    2339 
    2340 
    2341 
    2342 
    2343             <td style="vertical-align: middle;">wpt</td>
    2344 
    2345 
    2346 
    2347 
    2348 
    2349             <td style="vertical-align: middle;">Vertical total (
     431</tr> <tr> <td style="vertical-align: middle;">w'pt'</td>
     432<td style="vertical-align: middle;">Vertical subgrid-scale
     433kinematic heat flux (<font color="#000000">in </font>K
     434m/s).</td> </tr> <tr> <td style="vertical-align: middle;">wpt</td> <td style="vertical-align: middle;">Vertical total (
    2350435subgrid-scale + resolved)
    2351 kinematic heat flux (<font color="#000000">in </font>K m/s).</td>
    2352 
    2353 
    2354 
    2355 
    2356 
    2357           </tr>
    2358 
    2359 
    2360 
    2361 
    2362 
    2363           <tr>
    2364 
    2365 
    2366 
    2367 
    2368 
    2369             <td style="vertical-align: middle;">w'u'</td>
    2370 
    2371 
    2372 
    2373 
    2374 
    2375             <td style="vertical-align: middle;">u-component of the
    2376 vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
    2377 
    2378 
    2379 
    2380 
    2381 
    2382           </tr>
    2383 
    2384 
    2385 
    2386 
    2387 
    2388           <tr>
    2389 
    2390 
    2391 
    2392 
    2393 
    2394             <td style="vertical-align: middle;">wu</td>
    2395 
    2396 
    2397 
    2398 
    2399 
    2400             <td style="vertical-align: middle;">u-component of the
     436kinematic heat flux (<font color="#000000">in </font>K
     437m/s).</td> </tr> <tr> <td style="vertical-align: middle;">w'u'</td> <td style="vertical-align: middle;">u-component of the
     438vertical subgrid-scale momentum flux (<font color="#000000">in
     439</font>m<sup>2</sup>/s<sup>2</sup>).</td>
     440</tr> <tr> <td style="vertical-align: middle;">wu</td>
     441<td style="vertical-align: middle;">u-component of the
    2401442total
    2402443vertical momentum flux (
    2403444subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
    2404 
    2405 
    2406 
    2407 
    2408 
    2409           </tr>
    2410 
    2411 
    2412 
    2413 
    2414 
    2415           <tr>
    2416 
    2417 
    2418 
    2419 
    2420 
    2421             <td style="vertical-align: middle;">w'v'</td>
    2422 
    2423 
    2424 
    2425 
    2426 
    2427             <td style="vertical-align: middle;">v-component of the
    2428 vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
    2429 
    2430 
    2431 
    2432 
    2433 
    2434           </tr>
    2435 
    2436 
    2437 
    2438 
    2439 
    2440           <tr>
    2441 
    2442 
    2443 
    2444 
    2445 
    2446             <td style="vertical-align: middle;">wv</td>
    2447 
    2448 
    2449 
    2450 
    2451 
    2452             <td style="vertical-align: middle;">v-component of the
     445</tr> <tr> <td style="vertical-align: middle;">w'v'</td>
     446<td style="vertical-align: middle;">v-component of the
     447vertical subgrid-scale momentum flux (<font color="#000000">in
     448</font>m<sup>2</sup>/s<sup>2</sup>).</td>
     449</tr> <tr> <td style="vertical-align: middle;">wv</td>
     450<td style="vertical-align: middle;">v-component of the
    2453451total
    2454452vertical momentum flux (
    2455453subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
    2456 
    2457 
    2458 
    2459 
    2460 
    2461           </tr>
    2462 
    2463 
    2464 
    2465 
    2466 
    2467        
    2468        
    2469        
    2470        
    2471        
    2472         </tbody>
    2473      
    2474      
    2475      
    2476      
    2477      
    2478       </table>
    2479 
    2480 
    2481 
    2482 
    2483 
    2484       <br>
    2485 
    2486 
    2487 
    2488 
    2489 
    2490       </td>
    2491 
    2492 
    2493 
    2494 
    2495 
    2496     </tr>
    2497 
    2498 
    2499 
    2500 
    2501 
    2502     <tr>
    2503 
    2504 
    2505 
    2506 
    2507 
    2508       <td style="vertical-align: top; text-align: center;">17 </td>
    2509 
    2510 
    2511 
    2512 
    2513 
    2514       <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D
    2515       </td>
    2516 
    2517 
    2518 
    2519 
    2520 
    2521       <td style="vertical-align: top;">O </td>
    2522 
    2523 
    2524 
    2525 
    2526 
    2527       <td style="vertical-align: top;">Ascii </td>
    2528 
    2529 
    2530 
    2531 
    2532 
    2533       <td style="vertical-align: top;">This file contains the vertical
     454</tr> </tbody> </table> <br> </td> </tr>
     455<tr> <td style="vertical-align: top; text-align: center;">17
     456</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
    2534457profiles calculated by the
    25354581D-model within initial runs. The quantities saved are set
    … …  
    2543466only switched on at initial runs), executing computer, date,
    2544467time of the beginning of the run, output time). Afterwards the
    2545 following columns appear:<br>
    2546 
    2547 
    2548 
    2549 
    2550 
    2551      
    2552      
    2553      
    2554      
    2555      
    2556       <table style="text-align: left; width: 100%;" cellpadding="2">
    2557 
    2558 
    2559 
    2560 
    2561 
    2562         <tbody>
    2563 
    2564 
    2565 
    2566 
    2567 
    2568           <tr>
    2569 
    2570 
    2571 
    2572 
    2573 
    2574             <td style="text-align: left; vertical-align: middle;">k<br>
    2575 
    2576 
    2577 
    2578 
    2579 
    2580             </td>
    2581 
    2582 
    2583 
    2584 
    2585 
    2586             <td style="text-align: left; vertical-align: middle;">Vertical
    2587 grid point index.</td>
    2588 
    2589 
    2590 
    2591 
    2592 
    2593           </tr>
    2594 
    2595 
    2596 
    2597 
    2598 
    2599           <tr>
    2600 
    2601 
    2602 
    2603 
    2604 
    2605             <td style="text-align: left; vertical-align: middle;">zu<br>
    2606 
    2607 
    2608 
    2609 
    2610 
    2611             </td>
    2612 
    2613 
    2614 
    2615 
    2616 
    2617             <td style="text-align: left; vertical-align: middle;">Height
     468following columns appear:<br> <table style="text-align: left; width: 100%;" cellpadding="2">
     469<tbody> <tr> <td style="text-align: left; vertical-align: middle;">k<br>
     470</td> <td style="text-align: left; vertical-align: middle;">Vertical
     471grid point index.</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">zu<br>
     472</td> <td style="text-align: left; vertical-align: middle;">Height
    2618473of the grid point
    2619474level (<font color="#000000">in </font>m).</td>
    2620 
    2621 
    2622 
    2623 
    2624 
    2625           </tr>
    2626 
    2627 
    2628 
    2629 
    2630 
    2631           <tr>
    2632 
    2633 
    2634 
    2635 
    2636 
    2637             <td style="text-align: left; vertical-align: middle;">u<br>
    2638 
    2639 
    2640 
    2641 
    2642 
    2643             </td>
    2644 
    2645 
    2646 
    2647 
    2648 
    2649             <td style="text-align: left; vertical-align: middle;">u-component
     475</tr> <tr> <td style="text-align: left; vertical-align: middle;">u<br>
     476</td> <td style="text-align: left; vertical-align: middle;">u-component
    2650477of the wind
    2651478velocity (<font color="#000000">in </font>m/s).</td>
    2652 
    2653 
    2654 
    2655 
    2656 
    2657           </tr>
    2658 
    2659 
    2660 
    2661 
    2662 
    2663           <tr>
    2664 
    2665 
    2666 
    2667 
    2668 
    2669             <td style="text-align: left; vertical-align: middle;">v<br>
    2670 
    2671 
    2672 
    2673 
    2674 
    2675             </td>
    2676 
    2677 
    2678 
    2679 
    2680 
    2681             <td style="text-align: left; vertical-align: middle;">v-component
     479</tr> <tr> <td style="text-align: left; vertical-align: middle;">v<br>
     480</td> <td style="text-align: left; vertical-align: middle;">v-component
    2682481of the wind
    2683482velocity (<font color="#000000">in </font>m/s).</td>
    2684 
    2685 
    2686 
    2687 
    2688 
    2689           </tr>
    2690 
    2691 
    2692 
    2693 
    2694 
    2695           <tr>
    2696 
    2697 
    2698 
    2699 
    2700 
    2701             <td style="text-align: left; vertical-align: middle;">pt<br>
    2702 
    2703 
    2704 
    2705 
    2706 
    2707             </td>
    2708 
    2709 
    2710 
    2711 
    2712 
    2713             <td style="text-align: left; vertical-align: middle;">Potential
     483</tr> <tr> <td style="text-align: left; vertical-align: middle;">pt<br>
     484</td> <td style="text-align: left; vertical-align: middle;">Potential
    2714485temperature (<font color="#000000">in </font>K).</td>
    2715 
    2716 
    2717 
    2718 
    2719 
    2720           </tr>
    2721 
    2722 
    2723 
    2724 
    2725 
    2726           <tr>
    2727 
    2728 
    2729 
    2730 
    2731 
    2732             <td style="text-align: left; vertical-align: middle;">e<br>
    2733 
    2734 
    2735 
    2736 
    2737 
    2738             </td>
    2739 
    2740 
    2741 
    2742 
    2743 
    2744             <td style="text-align: left; vertical-align: middle;">Turbulent
     486</tr> <tr> <td style="text-align: left; vertical-align: middle;">e<br>
     487</td> <td style="text-align: left; vertical-align: middle;">Turbulent
    2745488kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
    2746 
    2747 
    2748 
    2749 
    2750 
    2751           </tr>
    2752 
    2753 
    2754 
    2755 
    2756 
    2757           <tr>
    2758 
    2759 
    2760 
    2761 
    2762 
    2763             <td style="text-align: left; vertical-align: middle;">rif<br>
    2764 
    2765 
    2766 
    2767 
    2768 
    2769             </td>
    2770 
    2771 
    2772 
    2773 
    2774 
    2775             <td style="text-align: left; vertical-align: middle;">Flux
    2776 Richardson number</td>
    2777 
    2778 
    2779 
    2780 
    2781 
    2782           </tr>
    2783 
    2784 
    2785 
    2786 
    2787 
    2788           <tr>
    2789 
    2790 
    2791 
    2792 
    2793 
    2794             <td style="text-align: left; vertical-align: middle;">Km<br>
    2795 
    2796 
    2797 
    2798 
    2799 
    2800             </td>
    2801 
    2802 
    2803 
    2804 
    2805 
    2806             <td style="text-align: left; vertical-align: middle;">Turbulent
     489</tr> <tr> <td style="text-align: left; vertical-align: middle;">rif<br>
     490</td> <td style="text-align: left; vertical-align: middle;">Flux
     491Richardson number</td> </tr> <tr> <td style="text-align: left; vertical-align: middle;">Km<br>
     492</td> <td style="text-align: left; vertical-align: middle;">Turbulent
    2807493diffusion
    2808494coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
    2809 
    2810 
    2811 
    2812 
    2813 
    2814           </tr>
    2815 
    2816 
    2817 
    2818 
    2819 
    2820           <tr>
    2821 
    2822 
    2823 
    2824 
    2825 
    2826             <td style="text-align: left; vertical-align: middle;">Kh<br>
    2827 
    2828 
    2829 
    2830 
    2831 
    2832             </td>
    2833 
    2834 
    2835 
    2836 
    2837 
    2838             <td style="text-align: left; vertical-align: middle;">Turbulent
     495</tr> <tr> <td style="text-align: left; vertical-align: middle;">Kh<br>
     496</td> <td style="text-align: left; vertical-align: middle;">Turbulent
    2839497diffusion
    2840498coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
    2841 
    2842 
    2843 
    2844 
    2845 
    2846           </tr>
    2847 
    2848 
    2849 
    2850 
    2851 
    2852           <tr>
    2853 
    2854 
    2855 
    2856 
    2857 
    2858             <td style="text-align: left; vertical-align: middle;">l<br>
    2859 
    2860 
    2861 
    2862 
    2863 
    2864             </td>
    2865 
    2866 
    2867 
    2868 
    2869 
    2870             <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
    2871 length (</font><font color="#000000">in </font><font color="#000000">m).</font></td>
    2872 
    2873 
    2874 
    2875 
    2876 
    2877           </tr>
    2878 
    2879 
    2880 
    2881 
    2882 
    2883        
    2884        
    2885        
    2886        
    2887        
    2888         </tbody>
    2889      
    2890      
    2891      
    2892      
    2893      
    2894       </table>
    2895 
    2896 
    2897 
    2898 
    2899 
    2900       <br>
    2901 
    2902 
    2903 
    2904 
    2905 
    2906       </td>
    2907 
    2908 
    2909 
    2910 
    2911 
    2912     </tr>
    2913 
    2914 
    2915 
    2916 
    2917 
    2918     <tr>
    2919 
    2920 
    2921 
    2922 
    2923 
    2924       <td style="vertical-align: top; text-align: center;">18 </td>
    2925 
    2926 
    2927 
    2928 
    2929 
    2930       <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
    2931       </td>
    2932 
    2933 
    2934 
    2935 
    2936 
    2937       <td style="vertical-align: top;">O </td>
    2938 
    2939 
    2940 
    2941 
    2942 
    2943       <td style="vertical-align: top;">Ascii </td>
    2944 
    2945 
    2946 
    2947 
    2948 
    2949       <td style="vertical-align: top;">Time measurements are
     499</tr> <tr> <td style="text-align: left; vertical-align: middle;">l<br>
     500</td> <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
     501length (</font><font color="#000000">in </font><font color="#000000">m).</font></td> </tr> </tbody>
     502</table> <br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">18 </td>
     503<td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
     504</td> <td style="vertical-align: top;">O </td>
     505<td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">Time measurements are
    2950506accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file
    2951507CPU_MEASURES contains a header with some basic information of the
    … …  
    2956512times which have been consumed by certain model parts. The model parts
    2957513analyzed in the first table do not overlap and the CPU times needed for
    2958 them therefore approximately add up to the &ldquo;total&rdquo; value given in the
     514them therefore approximately add up to the &ldquo;total&rdquo;
     515value given in the
    2959516first line of this table. In the second table (heading: special
    2960517measures) overlaps (in particular with the parts described in the first
    2961518table) are possible.&nbsp; <br>
    2962 
    2963 
    2964 
    2965 
    2966 
    2967519For each model part it is indicated in the following columns how much
    2968520CPU time was needed (absolutely and relative), and how often it was
    2969 called.&nbsp; With runs on several processors the average values of all
     521called.&nbsp; With runs on several processors the average values of
     522all
    2970523processors are indicated. In the case of parallel runs information for
    2971524those processors with the largest and smallest CPU time follow as
    … …  
    2974527parallelization the CPU times on the individual processors should
    2975528differ only little from each other and the standard deviation should be
    2976 small.&nbsp; </td>
    2977 
    2978 
    2979 
    2980 
    2981 
    2982     </tr>
    2983 
    2984 
    2985 
    2986 
    2987 
    2988     <tr>
    2989 
    2990 
    2991 
    2992 
    2993 
    2994       <td style="vertical-align: top; text-align: center;">19 </td>
    2995 
    2996 
    2997 
    2998 
    2999 
    3000       <td style="vertical-align: top;"><a name="HEADER"></a>HEADER </td>
    3001 
    3002 
    3003 
    3004 
    3005 
    3006       <td style="vertical-align: top;">O </td>
    3007 
    3008 
    3009 
    3010 
    3011 
    3012       <td style="vertical-align: top;">Ascii </td>
    3013 
    3014 
    3015 
    3016 
    3017 
    3018       <td style="vertical-align: top;">
    3019      
    3020      
    3021      
    3022      
    3023      
    3024       <p>Information about the selected model parameters (physical and
    3025 numerical values) as well as general information about the run.&nbsp; </p>
    3026 
    3027 
    3028 
    3029 
    3030 
    3031      
    3032      
    3033      
    3034      
    3035      
    3036       <p>This file contains the values of all important steering
     529small.&nbsp; </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">19 </td>
     530<td style="vertical-align: top;"><a name="HEADER"></a>HEADER
     531</td> <td style="vertical-align: top;">O </td>
     532<td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;"> <p>Information about
     533the selected model parameters (physical and
     534numerical values) as well as general information about the
     535run.&nbsp; </p> <p>This file contains the values of
     536all important steering
    3037537parameters
    3038538(numerical procedures, computing grid and model dimensions, boundary
    … …  
    3054554time reached is missing etc.) and then briefly before the normal end of
    3055555the simulation. The second, now complete output overwrites the first
    3056 output.).&nbsp; </p>
    3057 
    3058 
    3059 
    3060 
    3061 
    3062      
    3063      
    3064      
    3065      
    3066      
    3067       <p>At the end of the file, information about the values of user
     556output.).&nbsp; </p> <p>At the end of the file,
     557information about the values of user
    3068558parameters (see <a href="chapter_3.7.html">chapter
    30695593.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter
    3070 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
     5604.3</a>) can be output by the user with the help of the
     561subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt>
     562(located in
    3071563the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>).
    3072 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;
     564If no user parameters were found, the string &ldquo;<tt><font style="font-size: 10pt;" size="2">*** no user-defined
     565variables found</font></tt>&rdquo;
    3073566appears at the end of the file.
    3074 If user parameters were indicated, the string &ldquo;<tt><font style="font-size: 11pt;" size="2">user-defined variables and actions</font></tt>&rdquo;
     567If user parameters were indicated, the string &ldquo;<tt><font style="font-size: 11pt;" size="2">user-defined
     568variables and actions</font></tt>&rdquo;
    3075569is printed, followed by informations about the user-defined subdomains
    3076570for which
    3077571profiles and time series are output. All further information to appear
    3078572here, must be provided by the user (by appropriate
    3079 WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p>
    3080 
    3081 
    3082 
    3083 
    3084 
    3085       </td>
    3086 
    3087 
    3088 
    3089 
    3090 
    3091     </tr>
    3092 
    3093 
    3094 
    3095 
    3096 
    3097     <tr>
    3098 
    3099 
    3100 
    3101 
    3102 
    3103       <td style="vertical-align: top; text-align: center;">21 </td>
    3104 
    3105 
    3106 
    3107 
    3108 
    3109       <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY
    3110       </td>
    3111 
    3112 
    3113 
    3114 
    3115 
    3116       <td style="vertical-align: top;">O<br>
    3117 
    3118 
    3119 
    3120 
    3121 
    3122       </td>
    3123 
    3124 
    3125 
    3126 
    3127 
    3128       <td style="vertical-align: top;">Binary<br>
    3129 
    3130 
    3131 
    3132 
    3133 
    3134       </td>
    3135 
    3136 
    3137 
    3138 
    3139 
    3140       <td style="vertical-align: top;">
    3141      
    3142      
    3143      
    3144      
    3145      
    3146       <p>This file contains data of the two-dimensional horizontal
     573WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p> </td>
     574</tr> <tr> <td style="vertical-align: top; text-align: center;">21 </td>
     575<td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY
     576</td> <td style="vertical-align: top;">O<br> </td>
     577<td style="vertical-align: top;">Binary<br> </td>
     578<td style="vertical-align: top;"> <p>This file
     579contains data of the two-dimensional horizontal
    3147580cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>)
    3148581in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>
    3149 (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
     582(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>,
     583then
    3150584the individual arrays follow). The data are visualized with the help of
    3151585ISO2D using
    … …  
    3153587the
    3154588local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
    3155 and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.&nbsp; </p>
    3156 
    3157 
    3158 
    3159 
    3160 
    3161      
    3162      
    3163      
    3164      
    3165      
    3166       <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>
    3167 = <i>.T.</i> each processing element writes the data of its subdomain
    3168 to a separate file with the name PLOT2D_XY_&lt;processor-Id&gt;,
     589and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.&nbsp;
     590</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>
     591= <i>.T.</i> each processing element writes the data of
     592its subdomain
     593to a separate file with the name
     594PLOT2D_XY_&lt;processor-Id&gt;,
    3169595whereby &lt;processor-Id&gt; is a four digit number (e.g.
    3170596PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the
    … …  
    3182608possibly existing files of the other cross sections (xz and/or yz)
    3183609and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
    3184 are also combined.&nbsp; </p>
    3185 
    3186 
    3187 
    3188 
    3189 
    3190      
    3191      
    3192      
    3193      
    3194      
    3195       <p>Further information about the output of plots of
     610are also combined.&nbsp; </p> <p>Further information
     611about the output of plots of
    3196612two-dimensional cross sections is found in the description of the run
    3197613parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p>
    3198 
    3199 
    3200 
    3201 
    3202 
    3203       </td>
    3204 
    3205 
    3206 
    3207 
    3208 
    3209     </tr>
    3210 
    3211 
    3212 
    3213 
    3214 
    3215     <tr>
    3216 
    3217 
    3218 
    3219 
    3220 
    3221       <td style="vertical-align: top; text-align: center;">22<br>
    3222 
    3223 
    3224 
    3225 
    3226 
    3227       </td>
    3228 
    3229 
    3230 
    3231 
    3232 
    3233       <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ
    3234       </td>
    3235 
    3236 
    3237 
    3238 
    3239 
    3240       <td style="vertical-align: top;">O<br>
    3241 
    3242 
    3243 
    3244 
    3245 
    3246       </td>
    3247 
    3248 
    3249 
    3250 
    3251 
    3252       <td style="vertical-align: top;">Binary<br>
    3253 
    3254 
    3255 
    3256 
    3257 
    3258       </td>
    3259 
    3260 
    3261 
    3262 
    3263 
    3264       <td style="vertical-align: top;">
    3265      
    3266      
    3267      
    3268      
    3269      
    3270       <p>This file contains the data of the xz
     614</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">22<br>
     615</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
     616the data of the xz
    3271617cross sections written by the model.&nbsp; </p>
    3272 
    3273 
    3274 
    3275 
    3276 
    3277618The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
    3278 applies to this file, respectively </td>
    3279 
    3280 
    3281 
    3282 
    3283 
    3284     </tr>
    3285 
    3286 
    3287 
    3288 
    3289 
    3290     <tr>
    3291 
    3292 
    3293 
    3294 
    3295 
    3296       <td style="vertical-align: top; text-align: center;">23<br>
    3297 
    3298 
    3299 
    3300 
    3301 
    3302       </td>
    3303 
    3304 
    3305 
    3306 
    3307 
    3308       <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ
    3309       </td>
    3310 
    3311 
    3312 
    3313 
    3314 
    3315       <td style="vertical-align: top;">O<br>
    3316 
    3317 
    3318 
    3319 
    3320 
    3321       </td>
    3322 
    3323 
    3324 
    3325 
    3326 
    3327       <td style="vertical-align: top;">Binary<br>
    3328 
    3329 
    3330 
    3331 
    3332 
    3333       </td>
    3334 
    3335 
    3336 
    3337 
    3338 
    3339       <td style="vertical-align: top;">
    3340      
    3341      
    3342      
    3343      
    3344      
    3345       <p>This file contains the data of the xz
     619applies to this file, respectively </td> </tr> <tr>
     620<td style="vertical-align: top; text-align: center;">23<br>
     621</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
     622the data of the xz
    3346623cross sections written by the model.&nbsp; </p>
    3347 
    3348 
    3349 
    3350 
    3351 
    3352624The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
    3353 applies to this file, respectively </td>
    3354 
    3355 
    3356 
    3357 
    3358 
    3359     </tr>
    3360 
    3361 
    3362 
    3363 
    3364 
    3365     <tr>
    3366 
    3367 
    3368 
    3369 
    3370 
    3371       <td style="vertical-align: top; text-align: center;">27<br>
    3372 
    3373 
    3374 
    3375 
    3376 
    3377       </td>
    3378 
    3379 
    3380 
    3381 
    3382 
    3383       <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL
    3384       </td>
    3385 
    3386 
    3387 
    3388 
    3389 
    3390       <td style="vertical-align: top;">O<br>
    3391 
    3392 
    3393 
    3394 
    3395 
    3396       </td>
    3397 
    3398 
    3399 
    3400 
    3401 
    3402       <td style="vertical-align: top;">Ascii/ NAMELIST<br>
    3403 
    3404 
    3405 
    3406 
    3407 
    3408       </td>
    3409 
    3410 
    3411 
    3412 
    3413 
    3414       <td style="vertical-align: top;">
    3415      
    3416      
    3417      
    3418      
    3419      
    3420       <p>NAMELIST - parameter sets, with which the plot layout of the
     625applies to this file, respectively </td> </tr> <tr>
     626<td style="vertical-align: top; text-align: center;">27<br>
     627</td> <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL </td>
     628<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td>
     629<td style="vertical-align: top;"> <p>NAMELIST -
     630parameter sets, with which the plot layout of the
    3421631data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
    3422632can 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>.
    3423633This file contains the so-called local parameter set (NAMELIST - group
    3424 name: &amp;LOCAL) required by ISO2D (one parameter set for each field
     634name: &amp;LOCAL) required by ISO2D (one parameter set for each
     635field
    3425636present at the file PLOT2D_XY). After the model run these parameter
    3426 sets can be edited by the user, if neccessary.&nbsp; </p>
    3427 
    3428 
    3429 
    3430 
    3431 
    3432      
    3433      
    3434      
    3435      
    3436      
    3437       <p>Additionally ISO2D still needs another so-called global
     637sets can be edited by the user, if neccessary.&nbsp; </p> <p>Additionally
     638ISO2D still needs another so-called global
    3438639parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>.
    3439640Due to the fact that ISO2D expects global and local parameter sets on
    … …  
    3443644contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
    3444645before the call of ISO2D (e.g. by an OUTPUT-command in the
    3445 MRUN-configuration file: &ldquo;PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL&rdquo;).
     646MRUN-configuration file: &ldquo;PLOT2D_XY_LOCAL &gt;&gt;
     647PLOT2D_XY_GLOBAL&rdquo;).
    3446648This relatively pedantic proceeding is due to the fact that the model
    3447649can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation
    3448650(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>
    3449651is known), while the local parameter sets are written continuously
    3450 to the file PLOT2D_XY_LOCAL during the run.</p>
    3451 
    3452 
    3453 
    3454 
    3455 
    3456       </td>
    3457 
    3458 
    3459 
    3460 
    3461 
    3462     </tr>
    3463 
    3464 
    3465 
    3466 
    3467 
    3468     <tr>
    3469 
    3470 
    3471 
    3472 
    3473 
    3474       <td style="vertical-align: top; text-align: center;">28<br>
    3475 
    3476 
    3477 
    3478 
    3479 
    3480       </td>
    3481 
    3482 
    3483 
    3484 
    3485 
    3486       <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL
    3487       </td>
    3488 
    3489 
    3490 
    3491 
    3492 
    3493       <td style="vertical-align: top;">O<br>
    3494 
    3495 
    3496 
    3497 
    3498 
    3499       </td>
    3500 
    3501 
    3502 
    3503 
    3504 
    3505       <td style="vertical-align: top;">Ascii/ NAMELIST<br>
    3506 
    3507 
    3508 
    3509 
    3510 
    3511       </td>
    3512 
    3513 
    3514 
    3515 
    3516 
    3517       <td style="vertical-align: top;">
    3518      
    3519      
    3520      
    3521      
    3522      
    3523       <p>NAMELIST - parameter sets, with which the plot layout of the
     652to the file PLOT2D_XY_LOCAL during the run.</p> </td> </tr>
     653<tr> <td style="vertical-align: top; text-align: center;">28<br>
     654</td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL </td>
     655<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td>
     656<td style="vertical-align: top;"> <p>NAMELIST -
     657parameter sets, with which the plot layout of the
    3524658data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
    3525659can 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;
    3526       </p>
    3527 
    3528 
    3529 
    3530 
    3531 
    3532      
    3533      
    3534      
    3535      
    3536      
    3537       <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
    3538 applies to this file, respectively. </p>
    3539 
    3540 
    3541 
    3542 
    3543 
    3544       </td>
    3545 
    3546 
    3547 
    3548 
    3549 
    3550     </tr>
    3551 
    3552 
    3553 
    3554 
    3555 
    3556     <tr>
    3557 
    3558 
    3559 
    3560 
    3561 
    3562       <td style="vertical-align: top; text-align: center;">29<br>
    3563 
    3564 
    3565 
    3566 
    3567 
    3568       </td>
    3569 
    3570 
    3571 
    3572 
    3573 
    3574       <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL
    3575       </td>
    3576 
    3577 
    3578 
    3579 
    3580 
    3581       <td style="vertical-align: top;">O<br>
    3582 
    3583 
    3584 
    3585 
    3586 
    3587       </td>
    3588 
    3589 
    3590 
    3591 
    3592 
    3593       <td style="vertical-align: top;">Ascii/ NAMELIST<br>
    3594 
    3595 
    3596 
    3597 
    3598 
    3599       </td>
    3600 
    3601 
    3602 
    3603 
    3604 
    3605       <td style="vertical-align: top;">
    3606      
    3607      
    3608      
    3609      
    3610      
    3611       <p>NAMELIST - parameter sets, with which the plot layout of the
     660</p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
     661applies to this file, respectively. </p> </td> </tr>
     662<tr> <td style="vertical-align: top; text-align: center;">29<br>
     663</td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL </td>
     664<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/ NAMELIST<br> </td>
     665<td style="vertical-align: top;"> <p>NAMELIST -
     666parameter sets, with which the plot layout of the
    3612667data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
    3613668can 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;
    3614       </p>
    3615 
    3616 
    3617 
    3618 
    3619 
    3620      
    3621      
    3622      
    3623      
    3624      
    3625       <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
    3626 applies to this file, respectively. </p>
    3627 
    3628 
    3629 
    3630 
    3631 
    3632       </td>
    3633 
    3634 
    3635 
    3636 
    3637 
    3638     </tr>
    3639 
    3640 
    3641 
    3642 
    3643 
    3644     <tr>
    3645 
    3646 
    3647 
    3648 
    3649 
    3650       <td style="vertical-align: top; text-align: center;">30<br>
    3651 
    3652 
    3653 
    3654 
    3655 
    3656       </td>
    3657 
    3658 
    3659 
    3660 
    3661 
    3662       <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA
    3663       </td>
    3664 
    3665 
    3666 
    3667 
    3668 
    3669       <td style="vertical-align: top;">O<br>
    3670 
    3671 
    3672 
    3673 
    3674 
    3675       </td>
    3676 
    3677 
    3678 
    3679 
    3680 
    3681       <td style="vertical-align: top;">Binary<br>
    3682 
    3683 
    3684 
    3685 
    3686 
    3687       </td>
    3688 
    3689 
    3690 
    3691 
    3692 
    3693       <td style="vertical-align: top;">
    3694      
    3695      
    3696      
    3697      
    3698      
    3699       <p>This file contains the data of the three-dimensional arrays
     669</p> <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
     670applies to this file, respectively. </p> </td> </tr>
     671<tr> <td style="vertical-align: top; text-align: center;">30<br>
     672</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
     673the data of the three-dimensional arrays
    3700674(see <a href="chapter_4.2.html#data_output">data_output</a>)
    3701675written by the model in a format readable for the visualization
    … …  
    3710684-) file, the content of the file PLOT3D_FLD_COOR must be appended to
    3711685the file PLOT3D_FLD by the user after the end of the model run (e.g.
    3712 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;
    3713       </p>
    3714 
    3715 
    3716 
    3717 
    3718 
    3719      
    3720      
    3721      
    3722      
    3723      
    3724       <p>With parallel runs each processing element writes the data of
     686with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR
     687&gt;&gt; PLOT3D_FLD</span>").&nbsp; </p> <p>With
     688parallel runs each processing element writes the data of
    3725689its subdomain to a separate file with the name
    3726 PLOT3D_DATA_&lt;Processor-Id&gt;, where &lt;Processor-Id&gt; is a
     690PLOT3D_DATA_&lt;Processor-Id&gt;, where
     691&lt;Processor-Id&gt; is a
    3727692four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable
    3728693for AVS, but after the end of the model run they can be combined to one
    … …  
    3736701found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
    3737702also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>)
    3738 are combined.&nbsp; </p>
    3739 
    3740 
    3741 
    3742 
    3743 
    3744      
    3745      
    3746      
    3747      
    3748      
    3749       <p>With parallel runs the output of data of large volume is also
     703are combined.&nbsp; </p> <p>With parallel runs the
     704output of data of large volume is also
    3750705possible in compressed form. For this purpose the initialization
    3751706parameter&nbsp; <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>
    3752 = <i>.TRUE.</i> must be set and the desired output accuracy has to be
     707= <i>.TRUE.</i> must be set and the desired output
     708accuracy has to be
    3753709indicated
    3754710with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
    … …  
    3758714and a further entry in the MRUN-configuration file are needed. More
    3759715details can be found in <a href="chapter_4.5.6.html">chapter
    3760 4.5.6</a>.</p>
    3761 
    3762 
    3763 
    3764 
    3765 
    3766       </td>
    3767 
    3768 
    3769 
    3770 
    3771 
    3772     </tr>
    3773 
    3774 
    3775 
    3776 
    3777 
    3778     <tr>
    3779 
    3780 
    3781 
    3782 
    3783 
    3784       <td style="vertical-align: top; text-align: center;">31<br>
    3785 
    3786 
    3787 
    3788 
    3789 
    3790       </td>
    3791 
    3792 
    3793 
    3794 
    3795 
    3796       <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR
    3797       </td>
    3798 
    3799 
    3800 
    3801 
    3802 
    3803       <td style="vertical-align: top;">O<br>
    3804 
    3805 
    3806 
    3807 
    3808 
    3809       </td>
    3810 
    3811 
    3812 
    3813 
    3814 
    3815       <td style="vertical-align: top;">Binary<br>
    3816 
    3817 
    3818 
    3819 
    3820 
    3821       </td>
    3822 
    3823 
    3824 
    3825 
    3826 
    3827       <td style="vertical-align: top;">
    3828      
    3829      
    3830      
    3831      
    3832      
    3833       <p>Coordinate information concerning
     7164.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">31<br>
     717</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
     718information concerning
    3834719the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
    3835 needed by the visualization software AVS.&nbsp; </p>
    3836 
    3837 
    3838 
    3839 
    3840 
    3841      
    3842      
    3843      
    3844      
    3845      
    3846       <p>The file PLOT3D_COOR should be saved by the user into the same
    3847 permanent directory as the file PLOT3D_DATA.&nbsp; </p>
    3848 
    3849 
    3850 
    3851 
    3852 
    3853      
    3854      
    3855      
    3856      
    3857      
    3858       <p>For parallel runs PLOT3D_COOR is written by PE0 only.</p>
    3859 
    3860 
    3861 
    3862 
    3863 
    3864       </td>
    3865 
    3866 
    3867 
    3868 
    3869 
    3870     </tr>
    3871 
    3872 
    3873 
    3874 
    3875 
    3876     <tr>
    3877 
    3878 
    3879 
    3880 
    3881 
    3882       <td style="vertical-align: top; text-align: center;">32<br>
    3883 
    3884 
    3885 
    3886 
    3887 
    3888       </td>
    3889 
    3890 
    3891 
    3892 
    3893 
    3894       <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD
    3895       </td>
    3896 
    3897 
    3898 
    3899 
    3900 
    3901       <td style="vertical-align: top;">O<br>
    3902 
    3903 
    3904 
    3905 
    3906 
    3907       </td>
    3908 
    3909 
    3910 
    3911 
    3912 
    3913       <td style="vertical-align: top;">Ascii/&nbsp; <br>
    3914 
    3915 
    3916 
    3917 
    3918 
    3919 AVS-Fld </td>
    3920 
    3921 
    3922 
    3923 
    3924 
    3925       <td style="vertical-align: top;">
    3926      
    3927      
    3928      
    3929      
    3930      
    3931       <p>AVS-fld-file describing the three-dimensional
     720needed by the visualization software AVS.&nbsp; </p> <p>The
     721file PLOT3D_COOR should be saved by the user into the same
     722permanent directory as the file PLOT3D_DATA.&nbsp; </p> <p>For
     723parallel runs PLOT3D_COOR is written by PE0 only.</p> </td>
     724</tr> <tr> <td style="vertical-align: top; text-align: center;">32<br>
     725</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>
     726AVS-Fld </td> <td style="vertical-align: top;"> <p>AVS-fld-file
     727describing the three-dimensional
    3932728array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>,
    3933 needed by the visualization software AVS.&nbsp; </p>
    3934 
    3935 
    3936 
    3937 
    3938 
    3939      
    3940      
    3941      
    3942      
    3943      
    3944       <p>This file describes the structure of the file PLOT3D_DATA
     729needed by the visualization software AVS.&nbsp; </p> <p>This
     730file describes the structure of the file PLOT3D_DATA
    3945731(e.g. number of arrays, array dimensions, data type etc.). It uses the
    3946732so-called AVS-Fld-format. It also contains the name of the file
    3947733(inclusive cycle number, but without path) under which the local file
    3948734PLOT3D_DATA is saved (this is the file name given in the file
    3949 connection statement of the MRUN &ndash; configuration) in the permanent
     735connection statement of the MRUN &ndash; configuration) in the
     736permanent
    3950737directory of the user (possibly on remote computers). Under this name
    3951738AVS expects the data which are to be visualized. If there is no file
    3952739connection statement for PLOT3D_DATA indicated in the configuration
    3953 file, that file (filename) is registered &ldquo;unknown&rdquo; in the file
     740file, that file (filename) is registered &ldquo;unknown&rdquo;
     741in the file
    3954742PLOT3D_FLD and the
    3955743actual name must be inserted later by hand. The file PLOT3D_FLD should
    … …  
    3957745that AVS can find the file PLOT3D_DATA without any problems. If the two
    3958746files lie in different directories, then the path name of the file
    3959 PLOT3D_DATA must be added.&nbsp; </p>
    3960 
    3961 
    3962 
    3963 
    3964 
    3965      
    3966      
    3967      
    3968      
    3969      
    3970       <p>AVS-fld-files are expected by AVS to have the
     747PLOT3D_DATA must be added.&nbsp; </p> <p>AVS-fld-files
     748are expected by AVS to have the
    3971749suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font>
    3972 Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix. This suffix is
     750Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix.
     751This suffix is
    3973752attached to the permanent file names (still after
    3974753possible cycle numbers) by <span style="font-weight: bold;">mrun</span>
    3975754if&nbsp;"<span style="font-family: monospace;">fld</span>"
    3976755is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column
    3977 6 </a>of the file connection statement.&nbsp; </p>
    3978 
    3979 
    3980 
    3981 
    3982 
    3983      
    3984      
    3985      
    3986      
    3987      
    3988       <p>Likewise, AVS expects information about the coordinate
     7566 </a>of the file connection statement.&nbsp; </p> <p>Likewise,
     757AVS expects information about the coordinate
    3989758system underlying the arrays on this file. This information is output
    3990759by the model
    … …  
    3992761whose content the user has to append to the file PLOT3D_FLD after the
    3993762end of the model run (e.g. with an appropriate OUTPUT-command in the
    3994 MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR &gt;&gt;
    3995 PLOT3D_FLD&rdquo;).&nbsp; </p>
    3996 
    3997 
    3998 
    3999 
    4000 
    4001      
    4002      
    4003      
    4004      
    4005      
    4006       <p>For parallel runs, PLOT3D_FLD is produced by PE0 only.</p>
    4007 
    4008 
    4009 
    4010 
    4011 
    4012       </td>
    4013 
    4014 
    4015 
    4016 
    4017 
    4018     </tr>
    4019 
    4020 
    4021 
    4022 
    4023 
    4024     <tr>
    4025 
    4026 
    4027 
    4028 
    4029 
    4030       <td style="vertical-align: top; text-align: center;">33 </td>
    4031 
    4032 
    4033 
    4034 
    4035 
    4036       <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR
    4037       </td>
    4038 
    4039 
    4040 
    4041 
    4042 
    4043       <td style="vertical-align: top;">O<br>
    4044 
    4045 
    4046 
    4047 
    4048 
    4049       </td>
    4050 
    4051 
    4052 
    4053 
    4054 
    4055       <td style="vertical-align: top;">Ascii/&nbsp; <br>
    4056 
    4057 
    4058 
    4059 
    4060 
    4061 AVS-Fld </td>
    4062 
    4063 
    4064 
    4065 
    4066 
    4067       <td style="vertical-align: top;">
    4068      
    4069      
    4070      
    4071      
    4072      
    4073       <p>File for the description of the coordinate information output
     763MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR
     764&gt;&gt;
     765PLOT3D_FLD&rdquo;).&nbsp; </p> <p>For parallel
     766runs, PLOT3D_FLD is produced by PE0 only.</p> </td> </tr>
     767<tr> <td style="vertical-align: top; text-align: center;">33
     768</td> <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td>
     769<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
     770AVS-Fld </td> <td style="vertical-align: top;"> <p>File
     771for the description of the coordinate information output
    4074772by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
    4075773which is needed for the visualization of three-dimensional array data
    4076 by visualization-software AVS.&nbsp; </p>
    4077 
    4078 
    4079 
    4080 
    4081 
    4082      
    4083      
    4084      
    4085      
    4086      
    4087       <p>This file describes the structure of the file PLOT3D_COOR
     774by visualization-software AVS.&nbsp; </p> <p>This
     775file describes the structure of the file PLOT3D_COOR
    4088776(e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format.
    4089777It also contains the name of the file (inclusive cycle number, but
    … …  
    4097785registered as "unknown" in the file
    4098786PLOT3D_FLD_COOR and the actual name
    4099 must be inserted later by hand.&nbsp; </p>
    4100 
    4101 
    4102 
    4103 
    4104 
    4105      
    4106      
    4107      
    4108      
    4109      
    4110       <p>AVS expects the information contained in the file
     787must be inserted later by hand.&nbsp; </p> <p>AVS
     788expects the information contained in the file
    4111789PLOT3D_FLD_COOR, as well as the remaining information about the
    4112790three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>)
    … …  
    4114792PLOT3D_FLD_COOR after the end of a run are to the
    4115793file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the
    4116 MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR &gt;&gt;
    4117 PLOT3D_FLD&rdquo;).&nbsp; </p>
    4118 
    4119 
    4120 
    4121 
    4122 
    4123      
    4124      
    4125      
    4126      
    4127      
    4128       <p>For parallel runs, PLOT3D_FLD_COOR is written by PE0 only.</p>
    4129 
    4130 
    4131 
    4132 
    4133 
    4134       </td>
    4135 
    4136 
    4137 
    4138 
    4139 
    4140     </tr>
    4141 
    4142 
    4143 
    4144 
    4145 
    4146     <tr>
    4147 
    4148 
    4149 
    4150 
    4151 
    4152       <td style="vertical-align: top; text-align: center;">
    4153      
    4154      
    4155      
    4156      
    4157      
    4158       <p align="center">40&nbsp; </p>
    4159 
    4160 
    4161 
    4162 
    4163 
    4164      
    4165      
    4166      
    4167      
    4168      
    4169       <p align="center">and/or&nbsp; <br>
    4170 
    4171 
    4172 
    4173 
    4174 
     794MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR
     795&gt;&gt;
     796PLOT3D_FLD&rdquo;).&nbsp; </p> <p>For parallel
     797runs, PLOT3D_FLD_COOR is written by PE0 only.</p> </td> </tr>
     798<tr> <td style="vertical-align: top; text-align: center;">
     799<p align="center">40&nbsp; </p> <p align="center">and/or&nbsp; <br>
     800possibly&nbsp; </p> <p align="center">40-49</p>
     801</td> <td style="vertical-align: top;"> <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA&nbsp; </p>
     802<p>and/or&nbsp; <br>
    4175803possibly&nbsp; </p>
    4176 
    4177 
    4178 
    4179 
    4180 
    4181      
    4182      
    4183      
    4184      
    4185      
    4186       <p align="center">40-49</p>
    4187 
    4188 
    4189 
    4190 
    4191 
    4192       </td>
    4193 
    4194 
    4195 
    4196 
    4197 
    4198       <td style="vertical-align: top;">
    4199      
    4200      
    4201      
    4202      
    4203      
    4204       <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA&nbsp; </p>
    4205 
    4206 
    4207 
    4208 
    4209 
    4210      
    4211      
    4212      
    4213      
    4214      
    4215       <p>and/or&nbsp; <br>
    4216 
    4217 
    4218 
    4219 
    4220 
    4221 possibly&nbsp; </p>
    4222 
    4223 
    4224 
    4225 
    4226 
    4227804PLOT1D_DATA_0&nbsp; <br>
    4228 
    4229 
    4230 
    4231 
    4232 
    4233 PLOT1D_DATA_1&nbsp; </td>
    4234 
    4235 
    4236 
    4237 
    4238 
    4239       <td style="vertical-align: top;">O </td>
    4240 
    4241 
    4242 
    4243 
    4244 
    4245       <td style="vertical-align: top;">Ascii </td>
    4246 
    4247 
    4248 
    4249 
    4250 
    4251       <td style="vertical-align: top;">
    4252      
    4253      
    4254      
    4255      
    4256      
    4257       <p>This file contains data (possibly horizontally and/or
     805PLOT1D_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
     806data (possibly horizontally and/or
    4258807temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>)
    4259 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>.
     808written by the model in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
     809It is created only if <a href="chapter_4.2.html#data_output_format">data_output_format</a>
     810= <span style="font-style: italic;">'profil'</span>
     811is assigned. This file's format is suitable to be read by the plot
     812software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
    4260813Each data point of the profiles is output in one single line (1st
    4261814column: height in m, 2nd column: value of the respective quantity).
    … …  
    4265818(<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
    4266819means that the file starts with the data of the u-component profile,
    4267 followed by the v-component profile, etc.).&nbsp;</p>
    4268       <p><br>
     820followed by the v-component profile, etc.).&nbsp;</p> <p><br>
    4269821The data can only be visualized with <span style="font-weight: bold;">profil</span>
    4270822using NAMELIST-parameter sets, which are saved by the
    4271 model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp; </p>
    4272 
    4273 
    4274 
    4275 
    4276 
    4277      
    4278      
    4279      
    4280      
    4281      
    4282       <p>The profile data written to the file are described with the
     823model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp;
     824</p> <p>The profile data written to the file are described
     825with the
    4283826run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
    4284827Plots produced with these data using the parameter file PLOT1D_PAR do
    … …  
    4304847to the file name (e.g. PLOT1D_DATA_1). The name of the file with the
    4305848data of the total
    4306 domain in this case reads PLOT1D_DATA_0.&nbsp; </p>
    4307 
    4308 
    4309 
    4310 
    4311 
    4312      
    4313      
    4314      
    4315      
    4316      
    4317       <p>For presentation in the same plot, profile data of the restart
     849domain in this case reads PLOT1D_DATA_0.&nbsp; </p> <p>For
     850presentation in the same plot, profile data of the restart
    4318851runs can be attached to existing data of preceding runs of a job chain.
    4319852One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
    4320853in the file connection statement. The model produces a parameter file
    4321854(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>
    4322 = <i>.T</i>. If this is omitted, then the parameter file gives
     855= <i>.T</i>. If this is omitted, then the parameter file
     856gives
    4323857wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
    4324858= .T.</span> and "<span style="font-family: monospace;">tra</span>"
    4325 must be specified together)!&nbsp; </p>
    4326 
    4327 
    4328 
    4329 
    4330 
    4331      
    4332      
    4333      
    4334      
    4335      
    4336       <p>Further information about output of
     859must be specified together)!&nbsp; </p> <p>Further
     860information about output of
    4337861vertical 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>
    4338 
    4339 
    4340 
    4341 
    4342 
    4343       </td>
    4344 
    4345 
    4346 
    4347 
    4348 
    4349     </tr>
    4350 
    4351 
    4352 
    4353 
    4354 
    4355    
    4356 
    4357 
    4358 
    4359 
    4360 
    4361     <tr>
    4362 
    4363 
    4364 
    4365 
    4366 
    4367       <td style="vertical-align: top; text-align: center;">80 </td>
    4368 
    4369 
    4370 
    4371 
    4372 
    4373       <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/
    4374       </td>
    4375 
    4376 
    4377 
    4378 
    4379 
    4380       <td style="vertical-align: top;">O </td>
    4381 
    4382 
    4383 
    4384 
    4385 
    4386       <td style="vertical-align: top;">Ascii </td>
    4387 
    4388 
    4389 
    4390 
    4391 
    4392       <td style="vertical-align: top;">This
     862</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">80 </td>
     863<td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/ </td>
     864<td style="vertical-align: top;">O </td> <td style="vertical-align: top;">Ascii </td> <td style="vertical-align: top;">This
    4393865file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles
    4394 package</a>). It contains statistical informations about the number of
     866package</a>). It contains statistical informations about the
     867number of
    4395868particles used and about the number of particles exchanged between each
    4396869single PE. These informations are output after every timestep if
    4397870switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>.
    4398       </td>
    4399 
    4400 
    4401 
    4402 
    4403 
    4404     </tr>
    4405 
    4406 
    4407 
    4408 
    4409 
    4410     <tr>
    4411 
    4412 
    4413 
    4414 
    4415 
    4416       <td style="vertical-align: top; text-align: center;">81 </td>
    4417 
    4418 
    4419 
    4420 
    4421 
    4422       <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR
    4423       </td>
    4424 
    4425 
    4426 
    4427 
    4428 
    4429       <td style="vertical-align: top;">O </td>
    4430 
    4431 
    4432 
    4433 
    4434 
    4435       <td style="vertical-align: top;">Ascii/<br>
    4436 
    4437 
    4438 
    4439 
    4440 
    4441 NAMELIST </td>
    4442 
    4443 
    4444 
    4445 
    4446 
    4447       <td style="vertical-align: top;">This
     871</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">81 </td>
     872<td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR
     873</td> <td style="vertical-align: top;">O </td>
     874<td style="vertical-align: top;">Ascii/<br>
     875NAMELIST </td> <td style="vertical-align: top;">This
    4448876file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
    4449 package</a>). It contains the NAMELIST parameter set, with which the
     877package</a>). It contains the NAMELIST parameter set, with which
     878the
    4450879layout of a plot
    4451880of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
    4452881can 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>
    4453 
    4454 
    4455 
    4456 
    4457 
    4458      
    4459      
    4460      
    4461      
    4462      
    4463       <p>It contains the so-called RAHMEN (frame)- and
    4464 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
     882<p>It contains the so-called RAHMEN (frame)- and
     883CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or
     884&amp;CROSS</span>)
    4465885needed by <span style="font-weight: bold;">profil</span>.
    4466886The user can edit these parameter sets (and thus all details of the
    4467 plot layout) after the run.<br>
    4468 
    4469 
    4470 
    4471 
    4472 
    4473       </p>
    4474 
    4475 
    4476 
    4477 
    4478 
    4479      
    4480      
    4481      
    4482      
    4483      
    4484       <p>By default, for one quantity, all spectra at different heights
     887plot layout) after the run.<br> </p> <p>By default,
     888for one quantity, all spectra at different heights
    4485889are plotted into a single panel. Different colors and line styles are
    4486890used for each height. Panels of up to four quantities are arranged on
    … …  
    4488892additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
    4489893additional pages will be plotted for each single output time. </p>
    4490 
    4491 
    4492 
    4493 
    4494 
    4495       </td>
    4496 
    4497 
    4498 
    4499 
    4500 
    4501     </tr>
    4502 
    4503 
    4504 
    4505 
    4506 
    4507     <tr>
    4508 
    4509 
    4510 
    4511 
    4512 
    4513       <td style="vertical-align: top; text-align: center;">82<br>
    4514 
    4515 
    4516 
    4517 
    4518 
    4519       </td>
    4520 
    4521 
    4522 
    4523 
    4524 
    4525       <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA
    4526       </td>
    4527 
    4528 
    4529 
    4530 
    4531 
    4532       <td style="vertical-align: top;">O<br>
    4533 
    4534 
    4535 
    4536 
    4537 
    4538       </td>
    4539 
    4540 
    4541 
    4542 
    4543 
    4544       <td style="vertical-align: top;">Ascii<br>
    4545 
    4546 
    4547 
    4548 
    4549 
    4550       </td>
    4551 
    4552 
    4553 
    4554 
    4555 
    4556       <td style="vertical-align: top;">This
     894</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">82<br>
     895</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
    4557896file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
    4558897package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
    … …  
    4561900using NAMELIST parameter sets, which are written by
    4562901the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
    4563 
    4564 
    4565 
    4566 
    4567 
    4568       <br>
    4569 
    4570 
    4571 
    4572 
    4573 
     902<br>
    4574903Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
    4575904for actual plotting, this file contains all data of spectra specified
    4576905by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br>
    4577 
    4578 
    4579 
    4580 
    4581 
    4582       <br>
    4583 
    4584 
    4585 
    4586 
    4587 
    4588       <font>Each data point of a spectrum is output in a single line
     906<br> <font>Each data point of a spectrum is output in a
     907single line
    4589908(1st column:
    4590909wavenumber, 2nd column: spectral coefficient). If spectra are to be
    … …  
    4593912subsequent columns. </font>The order
    4594913of 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>
    4595 
    4596 
    4597 
    4598 
    4599 
    4600       <br>
    4601 
    4602 
    4603 
    4604 
    4605 
     914<br>
    4606915For orientation, a header of comment lines (one for each height level)
    4607916is placed in front of the spectral data of each quantity. They indicate
    4608917the respective quantity and the output time. The text of these comment
    4609 lines is used as a legend in the plot. </td>
    4610 
    4611 
    4612 
    4613 
    4614 
    4615     </tr>
    4616 
    4617 
    4618 
    4619 
    4620 
    4621     <tr>
    4622 
    4623 
    4624 
    4625 
    4626 
    4627       <td style="vertical-align: top; text-align: center;">83<br>
    4628 
    4629 
    4630 
    4631 
    4632 
    4633       </td>
    4634 
    4635 
    4636 
    4637 
    4638 
    4639       <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR
    4640       </td>
    4641 
    4642 
    4643 
    4644 
    4645 
    4646       <td style="vertical-align: top;">O<br>
    4647 
    4648 
    4649 
    4650 
    4651 
    4652       </td>
    4653 
    4654 
    4655 
    4656 
    4657 
    4658       <td style="vertical-align: top;">Ascii<br>
    4659 
    4660 
    4661 
    4662 
    4663 
    4664       </td>
    4665 
    4666 
    4667 
    4668 
    4669 
    4670       <td style="vertical-align: top;">This
     918lines is used as a legend in the plot. </td> </tr> <tr>
     919<td style="vertical-align: top; text-align: center;">83<br>
     920</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
    4671921file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
    4672 package</a>). It contains the NAMELIST parameter set, with which the
     922package</a>). It contains the NAMELIST parameter set, with which
     923the
    4673924layout of a plot
    4674925of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
    4675926can 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>
    4676 
    4677 
    4678 
    4679 
    4680 
    4681       <br>
    4682 
    4683 
    4684 
    4685 
    4686 
     927<br>
    4687928For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
    4688 
    4689 
    4690 
    4691 
    4692 
    4693       </td>
    4694 
    4695 
    4696 
    4697 
    4698 
    4699     </tr>
    4700 
    4701 
    4702 
    4703 
    4704 
    4705     <tr>
    4706 
    4707 
    4708 
    4709 
    4710 
    4711       <td style="vertical-align: top; text-align: center;">84<br>
    4712 
    4713 
    4714 
    4715 
    4716 
    4717       </td>
    4718 
    4719 
    4720 
    4721 
    4722 
    4723       <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td>
    4724 
    4725 
    4726 
    4727 
    4728 
    4729       <td style="vertical-align: top;">O<br>
    4730 
    4731 
    4732 
    4733 
    4734 
    4735       </td>
    4736 
    4737 
    4738 
    4739 
    4740 
    4741       <td style="vertical-align: top;">Ascii<br>
    4742 
    4743 
    4744 
    4745 
    4746 
    4747       </td>
    4748 
    4749 
    4750 
    4751 
    4752 
    4753       <td style="vertical-align: top;">This
     929</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">84<br>
     930</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
    4754931file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
    4755932package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
    … …  
    4758935using NAMELIST parameter sets, which are written by
    4759936the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
    4760 
    4761 
    4762 
    4763 
    4764 
    4765       <br>
    4766 
    4767 
    4768 
    4769 
    4770 
     937<br>
    4771938For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td>
    4772 
    4773 
    4774 
    4775 
    4776 
    4777     </tr>
    4778 
    4779 
    4780 
    4781 
    4782 
    4783     <tr>
    4784 
    4785 
    4786 
    4787 
    4788 
    4789       <td style="vertical-align: top; text-align: center;">85<br>
    4790 
    4791 
    4792 
    4793 
    4794 
    4795       </td>
    4796 
    4797 
    4798 
    4799 
    4800 
    4801       <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td>
    4802 
    4803 
    4804 
    4805 
    4806 
    4807       <td style="vertical-align: top;">O<br>
    4808 
    4809 
    4810 
    4811 
    4812 
    4813       </td>
    4814 
    4815 
    4816 
    4817 
    4818 
    4819       <td style="vertical-align: top;">Binary<br>
    4820 
    4821 
    4822 
    4823 
    4824 
    4825       </td>
    4826 
    4827 
    4828 
    4829 
    4830 
    4831       <td style="vertical-align: top;">This
     939</tr> <tr> <td style="vertical-align: top; text-align: center;">85<br>
     940</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
    4832941file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
    4833 package</a>) and contains all particle data for one or several output
     942package</a>) and contains all particle data for one or several
     943output
    4834944times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
    4835 
    4836 
    4837 
    4838 
    4839 
    4840       <br>
    4841 
    4842 
    4843 
    4844 
    4845 
     945<br>
    4846946The first record of this file contains an identification string (PALM
    4847947version number, run identifier, etc., 80 characters long). The second
    4848948record also contains a version string (80 characters long) followed by
    4849 two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>). Then, for each
     949two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>).
     950Then, for each
    4850951output time, two records follow, where the first one gives some general
    4851952information (numbers of particles, etc.) and the second one contains
    4852953the actual particle data. A FORTRAN TYPE structure is used for storing
    4853954the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span>
    4854 for the detailed format.</td>
    4855 
    4856 
    4857 
    4858 
    4859 
    4860     </tr>
    4861 
    4862 
    4863 
    4864 
    4865 
    4866     <tr>
    4867 
    4868 
    4869 
    4870 
    4871 
    4872       <td style="vertical-align: top; text-align: center;">90</td>
    4873 
    4874 
    4875 
    4876 
    4877 
    4878       <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
    4879 
    4880 
    4881 
    4882 
    4883 
    4884 DATA_IN/</td>
    4885 
    4886 
    4887 
    4888 
    4889 
    4890       <td style="vertical-align: top;">I<br>
    4891 
    4892 
    4893 
    4894 
    4895 
    4896       </td>
    4897 
    4898 
    4899 
    4900 
    4901 
    4902       <td style="vertical-align: top;">Binary<br>
    4903 
    4904 
    4905 
    4906 
    4907 
    4908       </td>
    4909 
    4910 
    4911 
    4912 
    4913 
    4914       <td style="vertical-align: top;">Binary
     955for the detailed format.</td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90</td>
     956<td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
     957DATA_IN/</td> <td style="vertical-align: top;">I<br>
     958</td> <td style="vertical-align: top;">Binary<br>
     959</td> <td style="vertical-align: top;">Binary
    4915960data, which are read in by the model at the beginning
    4916961of a restart run (see <a href="chapter_3.3.html">chapter
    4917 3.3</a>). The appropriate file must have been written by the preceding
     9623.3</a>). The appropriate file must have been written by the
     963preceding
    4918964job of the job chain (see <a href="#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>).
    4919965This file is needed if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
    … …  
    4925971The
    4926972number of processors which can be used must not be changed during a job
    4927 chain and/or if a job chain is continued. <br>
    4928 
    4929 
    4930 
    4931 
    4932 
    4933       <br>
    4934 
    4935 
    4936 
    4937 
    4938 
     973chain and/or if a job chain is continued. <br> <br>
    4939974The first record of this file contains a version number (four character
    4940 string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>, see end of
     975string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>,
     976see end of
    4941977file <span style="font-family: monospace;">advec_particles.f90</span>).
    4942978This number has to
    4943979agree with the version number of the subroutine which is reading the
    4944980file
    4945 (<span style="font-family: monospace;">init_parrticles.f90</span>) in
     981(<span style="font-family: monospace;">init_parrticles.f90</span>)
     982in
    4946983case of a restart run. Otherwise the model run
    4947984is aborted. Version numbers are changed whenever new code revisions
    … …  
    4954991informations. A FORTRAN TYPE structure is used for storing the particle
    4955992attributes. For detailed informations about the file format see the
    4956 corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span> .<br>
    4957 
    4958 
    4959 
    4960 
    4961 
    4962       </td>
    4963 
    4964 
    4965 
    4966 
    4967 
    4968     </tr>
    4969 
    4970 
    4971 
    4972 
    4973 
    4974     <tr>
    4975 
    4976 
    4977 
    4978 
    4979 
    4980       <td style="vertical-align: top; text-align: center;">90<br>
    4981 
    4982 
    4983 
    4984 
    4985 
    4986       </td>
    4987 
    4988 
    4989 
    4990 
    4991 
    4992       <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
    4993 
    4994 
    4995 
    4996 
    4997 
    4998 DATA_OUT/</td>
    4999 
    5000 
    5001 
    5002 
    5003 
    5004       <td style="vertical-align: top;">O<br>
    5005 
    5006 
    5007 
    5008 
    5009 
    5010       </td>
    5011 
    5012 
    5013 
    5014 
    5015 
    5016       <td style="vertical-align: top;">Binary<br>
    5017 
    5018 
    5019 
    5020 
    5021 
    5022       </td>
    5023 
    5024 
    5025 
    5026 
    5027 
    5028       <td style="vertical-align: top;">Binary
     993corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span>
     994.<br> </td> </tr> <tr> <td style="vertical-align: top; text-align: center;">90<br>
     995</td> <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
     996DATA_OUT/</td> <td style="vertical-align: top;">O<br>
     997</td> <td style="vertical-align: top;">Binary<br>
     998</td> <td style="vertical-align: top;">Binary
    5029999data, which are output at the end of the
    50301000run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
    … …  
    50321002file <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.
    50331003The file is only written if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
    5034 package</a>). For a more detailed description of the file structure see
    5035       <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
    5036 
    5037 
    5038 
    5039 
    5040 
    5041     </tr>
    5042 
    5043 
    5044 
    5045 
    5046 
    5047    
    5048 
    5049 
    5050 
    5051 
    5052 
    5053     <tr>
    5054 
    5055 
    5056 
    5057 
    5058 
    5059       <td style="vertical-align: top; text-align: center;">90<br>
    5060 
    5061 
    5062 
    5063 
    5064 
    5065       </td>
    5066 
    5067 
    5068 
    5069 
    5070 
    5071       <td style="vertical-align: top;">
    5072      
    5073      
    5074      
    5075      
    5076      
    5077       <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
    5078 
    5079 
    5080 
    5081 
    5082 
    5083      
    5084      
    5085      
    5086      
    5087      
    5088       <p>and/or&nbsp; <br>
    5089 
    5090 
    5091 
    5092 
    5093 
    5094 possibly&nbsp; </p>
    5095 
    5096 
    5097 
    5098 
    5099 
    5100      
    5101      
    5102      
    5103      
    5104      
    5105       <p>PLOT1D_PAR_0&nbsp; <br>
    5106 
    5107 
    5108 
    5109 
    5110 
     1004package</a>). For a more detailed description of the file
     1005structure see <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
     1006</tr> <tr> <td style="vertical-align: top; text-align: center;">90<br>
     1007</td> <td style="vertical-align: top;"> <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
     1008<p>and/or&nbsp; <br>
     1009possibly&nbsp; </p> <p>PLOT1D_PAR_0&nbsp; <br>
    51111010PLOT1D_PAR_1&nbsp; <br>
    5112 
    5113 
    5114 
    5115 
    5116 
    51171011&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    51181012.&nbsp; <br>
    5119 
    5120 
    5121 
    5122 
    5123 
    51241013&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    51251014.&nbsp; <br>
    5126 
    5127 
    5128 
    5129 
    5130 
    51311015&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    51321016.&nbsp; <br>
    5133 
    5134 
    5135 
    5136 
    5137 
    5138 PLOT1D_PAR_9</p>
    5139 
    5140 
    5141 
    5142 
    5143 
    5144       </td>
    5145 
    5146 
    5147 
    5148 
    5149 
    5150       <td style="vertical-align: top;">O<br>
    5151 
    5152 
    5153 
    5154 
    5155 
    5156       </td>
    5157 
    5158 
    5159 
    5160 
    5161 
    5162       <td style="vertical-align: top;">Ascii/ NAMELIST<br>
    5163 
    5164 
    5165 
    5166 
    5167 
    5168       </td>
    5169 
    5170 
    5171 
    5172 
    5173 
    5174       <td style="vertical-align: top;">
    5175      
    5176      
    5177      
    5178      
    5179      
    5180       <p>NAMELIST parameter set, with which the layout of a plot
     1017PLOT1D_PAR_9</p> </td> <td style="vertical-align: top;">O<br>
     1018</td> <td style="vertical-align: top;">Ascii/
     1019NAMELIST<br> </td> <td style="vertical-align: top;">
     1020<p>NAMELIST parameter set, with which the layout of a plot
    51811021of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a>
    51821022can 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;
    5183       </p>
    5184 
    5185 
    5186 
    5187 
    5188 
    5189      
    5190      
    5191      
    5192      
    5193      
    5194       <p>This file contains the so-called RAHMEN (frame)- and
    5195 CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
     1023</p> <p>This file contains the so-called RAHMEN (frame)-
     1024and
     1025CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or
     1026&amp;CROSS</span>)
    51961027needed by <span style="font-weight: bold;">profil</span>.
    51971028These parameter sets (and thus all details of the plot layout) can be
    … …  
    52001031colors are used for each output time. Which profiles are drawn
    52011032into which plane and how these planes are arranged on the
    5202 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>
    5203 and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.&nbsp; </p>
    5204 
    5205 
    5206 
    5207 
    5208 
    5209      
    5210      
    5211      
    5212      
    5213      
    5214       <p>The file PLOT1D_PAR is created by the model briefly before
     1033plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
     1034<a href="chapter_4.2.html#profile_columns">profile_columns</a>
     1035and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.&nbsp;
     1036</p> <p>The file PLOT1D_PAR is created by the model
     1037briefly before
    52151038the end of a run. If a model run crashes uncontrolled (run time
    52161039errors or CPU - time exceeded), this file is usually missing, although
    5217 profile data were saved to the file PLOT1D_DATA.&nbsp; </p>
    5218 
    5219 
    5220 
    5221 
    5222 
    5223      
    5224      
    5225      
    5226      
    5227      
    5228       <p>If the model has to create profiles for different subdomains
     1040profile data were saved to the file PLOT1D_DATA.&nbsp; </p> <p>If
     1041the model has to create profiles for different subdomains
    52291042(see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
    52301043further files are created, whereby the file name includes the number of
    52311044the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of
    52321045the file with NAMELIST parameters of the total domain is
    5233 PLOT1D_PAR_0.&nbsp; </p>
    5234 
    5235 
    5236 
    5237 
    5238 
    5239      
    5240      
    5241      
    5242      
    5243      
    5244       <p>For presentation in the same plot, profile data of the restart
     1046PLOT1D_PAR_0.&nbsp; </p> <p>For presentation in the
     1047same plot, profile data of the restart
    52451048runs can be appended to existing data of preceding runs of a job chain.
    52461049One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
    … …  
    52481051a parameter file PLOT1D_PAR for these combined data, if the run
    52491052parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
    5250 = <i>.T</i>. If this is omitted, then the parameter file gives
     1053= <i>.T</i>. If this is omitted, then the parameter file
     1054gives
    52511055wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
    52521056= .T.</span> and "<span style="font-family: monospace;">tra</span>"
    5253 must be specified together)!</p>
    5254 
    5255 
    5256 
    5257 
    5258 
    5259       </td>
    5260 
    5261 
    5262 
    5263 
    5264 
    5265     </tr>
    5266 
    5267 
    5268 
    5269 
    5270 
    5271     <tr>
    5272 
    5273 
    5274 
    5275 
    5276 
    5277       <td style="vertical-align: top; text-align: center;">90<br>
    5278 
    5279 
    5280 
    5281 
    5282 
    5283       </td>
    5284 
    5285 
    5286 
    5287 
    5288 
    5289       <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td>
    5290 
    5291 
    5292 
    5293 
    5294 
    5295       <td style="vertical-align: top;">O<br>
    5296 
    5297 
    5298 
    5299 
    5300 
    5301       </td>
    5302 
    5303 
    5304 
    5305 
    5306 
    5307       <td style="vertical-align: top;">Ascii/&nbsp; <br>
    5308 
    5309 
    5310 
    5311 
    5312 
    5313 NAMELIST</td>
    5314 
    5315 
    5316 
    5317 
    5318 
    5319       <td style="vertical-align: top;">
    5320      
    5321      
    5322      
    5323      
    5324      
    5325       <p>NAMELIST parameter set, with which the plot layout
     1057must be specified together)!</p> </td> </tr> <tr>
     1058<td style="vertical-align: top; text-align: center;">90<br>
     1059</td> <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td>
     1060<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
     1061NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
     1062parameter set, with which the plot layout
    53261063of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
    53271064can 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>.
    … …  
    53331070will be drawn onto a separate page (thus no color shading
    53341071presentation, no vector arrows, streamlines etc.).&nbsp; </p>
    5335 
    5336 
    5337 
    5338 
    5339 
    5340      
    5341      
    5342      
    5343      
    5344      
    5345       <p>Additionally <span style="font-weight: bold;">iso2d</span>
     1072<p>Additionally <span style="font-weight: bold;">iso2d</span>
    53461073needs the so-called local parameter
    53471074sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
    … …  
    53501077file, in fact the global parameter set first, the user has to append
    53511078the contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
    5352 before call of <span style="font-weight: bold;">iso2d</span> (e.g. by
     1079before call of <span style="font-weight: bold;">iso2d</span>
     1080(e.g. by
    53531081an OUTPUT - command in the MRUN -
    5354 configuration file: &ldquo;cat PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL&rdquo;).
     1082configuration file: &ldquo;cat PLOT2D_XY_LOCAL &gt;&gt;
     1083PLOT2D_XY_GLOBAL&rdquo;).
    53551084This
    53561085relatively pedantic proceedure is due to the fact that the model can
    … …  
    53601089to the file PLOT2D_XY_LOCAL during the run. Since the file
    53611090PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit
    5362 90 is used, which is also used for other files.</p>
    5363 
    5364 
    5365 
    5366 
    5367 
    5368       </td>
    5369 
    5370 
    5371 
    5372 
    5373 
    5374     </tr>
    5375 
    5376 
    5377 
    5378 
    5379 
    5380     <tr>
    5381 
    5382 
    5383 
    5384 
    5385 
    5386       <td style="vertical-align: top; text-align: center;">90<br>
    5387 
    5388 
    5389 
    5390 
    5391 
    5392       </td>
    5393 
    5394 
    5395 
    5396 
    5397 
    5398       <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td>
    5399 
    5400 
    5401 
    5402 
    5403 
    5404       <td style="vertical-align: top;">O<br>
    5405 
    5406 
    5407 
    5408 
    5409 
    5410       </td>
    5411 
    5412 
    5413 
    5414 
    5415 
    5416       <td style="vertical-align: top;">Ascii/&nbsp; <br>
    5417 
    5418 
    5419 
    5420 
    5421 
    5422 NAMELIST</td>
    5423 
    5424 
    5425 
    5426 
    5427 
    5428       <td style="vertical-align: top;">
    5429      
    5430      
    5431      
    5432      
    5433      
    5434       <p>NAMELIST parameter set, with which the plot layout of the data
     109190 is used, which is also used for other files.</p> </td> </tr>
     1092<tr> <td style="vertical-align: top; text-align: center;">90<br>
     1093</td> <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td>
     1094<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
     1095NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
     1096parameter set, with which the plot layout of the data
    54351097in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
    54361098can 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;
    5437       </p>
    5438 
    5439 
    5440 
    5441 
    5442 
    5443      
    5444      
    5445      
    5446      
    5447      
    5448       <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
    5449 applies to this file, respectively.</p>
    5450 
    5451 
    5452 
    5453 
    5454 
    5455       </td>
    5456 
    5457 
    5458 
    5459 
    5460 
    5461     </tr>
    5462 
    5463 
    5464 
    5465 
    5466 
    5467     <tr>
    5468 
    5469 
    5470 
    5471 
    5472 
    5473       <td style="vertical-align: top; text-align: center;">90<br>
    5474 
    5475 
    5476 
    5477 
    5478 
    5479       </td>
    5480 
    5481 
    5482 
    5483 
    5484 
    5485       <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td>
    5486 
    5487 
    5488 
    5489 
    5490 
    5491       <td style="vertical-align: top;">O<br>
    5492 
    5493 
    5494 
    5495 
    5496 
    5497       </td>
    5498 
    5499 
    5500 
    5501 
    5502 
    5503       <td style="vertical-align: top;">Ascii/&nbsp; <br>
    5504 
    5505 
    5506 
    5507 
    5508 
    5509 NAMELIST</td>
    5510 
    5511 
    5512 
    5513 
    5514 
    5515       <td style="vertical-align: top;">
    5516      
    5517      
    5518      
    5519      
    5520      
    5521       <p>NAMELIST parameter set, with which the plot layout of the data
     1099</p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
     1100applies to this file, respectively.</p> </td> </tr>
     1101<tr> <td style="vertical-align: top; text-align: center;">90<br>
     1102</td> <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td>
     1103<td style="vertical-align: top;">O<br> </td> <td style="vertical-align: top;">Ascii/&nbsp; <br>
     1104NAMELIST</td> <td style="vertical-align: top;"> <p>NAMELIST
     1105parameter set, with which the plot layout of the data
    55221106in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
    55231107can 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;
    5524       </p>
    5525 
    5526 
    5527 
    5528 
    5529 
    5530      
    5531      
    5532      
    5533      
    5534      
    5535       <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
    5536 applies to this file, respectively.</p>
    5537 
    5538 
    5539 
    5540 
    5541 
    5542       </td>
    5543 
    5544 
    5545 
    5546 
    5547 
    5548     </tr>
    5549 
    5550 
    5551 
    5552 
    5553     <tr>
    5554 
    5555 
    5556 
    5557 
    5558       <td style="vertical-align: top; text-align: center;">90</td>
    5559 
    5560 
    5561 
    5562 
    5563       <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td>
    5564 
    5565 
    5566 
    5567 
    5568       <td style="vertical-align: top;">I</td>
    5569 
    5570 
    5571 
    5572 
    5573       <td style="vertical-align: top;">Ascii</td>
    5574 
    5575 
    5576 
    5577 
    5578       <td>Two-dimensional&nbsp;<font color="#000000">topography height information</font> in m.<br>
    5579 
    5580 
    5581 
    5582 
    5583 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
     1108</p> <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
     1109applies to this file, respectively.</p> </td> </tr>
     1110<tr> <td style="vertical-align: top; text-align: center;">90</td>
     1111<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>
     1112in m.<br>
     1113In case of &nbsp;<a href="chapter_4.1.html#topography">topography</a>
     1114= <span style="font-style: italic;">'read_from_file'</span>
     1115the&nbsp;subroutine <span style="font-family: Cumberland AMT;">init_grid</span>&nbsp;reads
     1116the topography height information in m for each grid point in
    55841117a free floating point format. The data on file are laid out naturally,
    55851118i.e. in W-E orientation horizontally and in S-N orientation vertically,
    5586 they must thus be organized as follows:<br>
    5587 
    5588 
    5589      
    5590      
    5591       <ul>
    5592 
    5593 
    5594         <li>each line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li>
    5595 
    5596 
    5597         <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>
    5598 
    5599 
    5600         <li>individual data must be separated by at least one blank.</li>
    5601 
    5602 
    5603      
    5604      
    5605       </ul>
    5606 
    5607 
    5608 Layout sketch:<br>
    5609 
    5610 
    5611       <span style="font-family: Cumberland AMT;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;N<br>
    5612 
    5613 
    5614 &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>
    5615 
    5616 
    5617       <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>
    5618 
    5619 
    5620       </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>
    5621 
    5622 
    5623       </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>
    5624 
    5625 
    5626 &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
    5627 
    5628 
    5629       </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>
    5630 
    5631 
    5632       <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>
    5633 
    5634 
    5635       <font style="font-family: Arial;" color="#000000"></font><span style="font-family: Arial;"></span><br>
    5636 
    5637 
    5638 
    5639 
     1119they must thus be organized as follows:<br> <ul> <li>each
     1120line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li>
     1121<li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the
     1122bottom line for <span style="font-style: italic;">j = 0</span>
     1123(South),</li> <li>individual data must be separated by at
     1124least one blank.</li> </ul>
     1125Layout sketch:<br> <span style="font-family: Cumberland AMT;">&nbsp;
     1126&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     1127&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;N<br>
     1128&nbsp; &nbsp; (0,ny) &nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny)
     1129&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) &nbsp;
     1130...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) &nbsp;
     1131&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>
     1132<font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
     1133(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)
     1134...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) &nbsp;<br>
     1135</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;
     1136(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)
     1137...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) &nbsp; E<br>
     1138</span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp;
     1139&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     1140&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
     1141&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp;
     1142&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     1143&nbsp;:<br> </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
     1144(0,0) &nbsp;&nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0)
     1145&nbsp;&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0)
     1146&nbsp; &nbsp;...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0)
     1147&nbsp; &nbsp; &nbsp;&nbsp;</span></font></font></font><font color="#000000">&nbsp;bottom of file</font><br>
     1148<font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;
     1149&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     1150&nbsp; &nbsp; &nbsp;&nbsp; &nbsp;S</span></font><br>
     1151<span style="font-family: Arial;"></span><br>
    56401152These data must exactly match the horizontal grid.<br>
    5641 
    5642 
    5643 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>
    5644 
    5645 
    5646 
    5647 
    5648       <td><br>
    5649 
    5650       </td>
    5651 
    5652 
    5653 
    5654 
    5655     </tr>
    5656     <tr>
    5657 
    5658       <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td>
    5659 
    5660       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF</font></td>
    5661 
    5662       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5663 
    5664       <td style="vertical-align: top;"><font color="#000000">Binary/<br>
    5665 
     1153Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a>
     1154to allow different data formats.</td> <td><br> </td>
     1155</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>
     1156<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1157<td style="vertical-align: top;"><font color="#000000">Binary/<br>
    56661158NetCDF-<br>
    5667 
    5668 format</font></td>
    5669 
    5670       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional horizontal
     1159format</font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file
     1160contains data of the two-dimensional horizontal
    56711161cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
    5672 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>
    5673 
    5674       <br>
    5675 
     1162in NetCDF format. The data in this file can be visualized by any
     1163graphic 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>
    56761164More 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>
    5677 
    5678       <td style="vertical-align: top;"><br>
    5679 
    5680       </td>
    5681 
    5682     </tr>
    5683 
    5684     <tr>
    5685 
    5686       <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td>
    5687 
    5688       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF</font></td>
    5689 
    5690       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5691 
    5692       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5693 
     1165<td style="vertical-align: top;"><br> </td> </tr>
     1166<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>
     1167<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1168<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    56941169NetCDF-<br>
    5695 
    5696 format</font></font></td>
    5697 
    5698       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional vertical (xz)
     1170format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1171contains data of the two-dimensional vertical (xz)
    56991172cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
    5700 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>
    5701 
    5702       <br>
    5703 
     1173in NetCDF format. The data in this file can be visualized by any
     1174graphic 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>
    57041175More 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>
    5705 
    5706       <td style="vertical-align: top;"><br>
    5707 
    5708       </td>
    5709 
    5710     </tr>
    5711 
    5712     <tr>
    5713 
    5714       <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td>
    5715 
    5716       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF</font></td>
    5717 
    5718       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5719 
    5720       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5721 
     1176<td style="vertical-align: top;"><br> </td> </tr>
     1177<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>
     1178<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1179<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    57221180NetCDF-<br>
    5723 
    5724 format</font></font></td>
    5725 
    5726       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional vertical
     1181format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1182contains data of the two-dimensional vertical
    57271183(yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
    5728 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>
    5729 
    5730       <br>
    5731 
     1184in NetCDF format. The data in this file can be visualized by any
     1185graphic 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>
    57321186More 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>
    5733 
    5734       <td style="vertical-align: top;"><br>
    5735 
    5736       </td>
    5737 
    5738     </tr>
    5739 
    5740     <tr>
    5741 
    5742       <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td>
    5743 
    5744       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF</font></td>
    5745 
    5746       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5747 
    5748       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5749 
     1187<td style="vertical-align: top;"><br> </td> </tr>
     1188<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>
     1189<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1190<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    57501191NetCDF-<br>
    5751 
    5752 format</font></font></td>
    5753 
    5754       <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>)
    5755 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>
    5756 
    5757       <br>
    5758 
     1192format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1193contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>)
     1194in NetCDF format. The data in this file can be visualized by any
     1195graphic 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>
    57591196More 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>
    5760 
    5761       <td style="vertical-align: top;"><br>
    5762 
    5763       </td>
    5764 
    5765     </tr>
    5766 
    5767     <tr>
    5768 
    5769       <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td>
    5770 
    5771       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF</font></td>
    5772 
    5773       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5774 
    5775       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5776 
     1197<td style="vertical-align: top;"><br> </td> </tr>
     1198<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>
     1199<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1200<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    57771201NetCDF-<br>
    5778 
    5779 format</font></font></td>
    5780 
    5781       <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>)
    5782 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>
    5783 
    5784       <br>
    5785 
     1202format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1203contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>)
     1204in NetCDF format. The data in this file can be visualized by any
     1205graphic 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>
    57861206More 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>
    5787 
    5788       <td style="vertical-align: top;"><br>
    5789 
    5790       </td>
    5791 
    5792     </tr>
    5793 
    5794     <tr>
    5795 
    5796       <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td>
    5797 
    5798       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td>
    5799 
    5800       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5801 
    5802       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5803 
     1207<td style="vertical-align: top;"><br> </td> </tr>
     1208<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>
     1209<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1210<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    58041211NetCDF-<br>
    5805 
    5806 format</font></font></td>
    5807 
    5808       <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>)
    5809 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>
    5810 
    5811       <br>
    5812 
     1212format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1213contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
     1214in NetCDF format. The data in this file can be visualized by any
     1215graphic 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>
    58131216More 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>
    5814 
    5815       <td style="vertical-align: top;"><br>
    5816 
    5817       </td>
    5818 
    5819     </tr>
    5820 
    5821     <tr>
    5822 
    5823       <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td>
    5824 
    5825       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF</font></td>
    5826 
    5827       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5828 
    5829       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5830 
     1217<td style="vertical-align: top;"><br> </td> </tr>
     1218<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>
     1219<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1220<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    58311221NetCDF-<br>
    5832 
    5833 format</font></font></td>
    5834 
    5835       <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>)
    5836 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>
    5837 
    5838       <br>
    5839 
     1222format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1223contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>)
     1224in NetCDF format. The data in this file can be visualized by any
     1225graphic 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>
    58401226More 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>
    5841 
    5842       <td style="vertical-align: top;"><br>
    5843 
    5844       </td>
    5845 
    5846     </tr>
    5847 
    5848     <tr>
    5849 
    5850       <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td>
    5851 
    5852       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/</font></td>
    5853 
    5854       <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
    5855 
    5856       <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    5857 
     1227<td style="vertical-align: top;"><br> </td> </tr>
     1228<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>
     1229<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
     1230<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
    58581231NetCDF-<br>
    5859 
    5860 format</font></font></td>
    5861 
    5862       <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>)
    5863 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>
    5864 
    5865       <br>
    5866 
     1232format</font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1233contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>)
     1234in NetCDF format. The data in this file can be visualized by any
     1235graphic 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>
    58671236More 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>
    5868 
    5869       <td style="vertical-align: top;"><br>
    5870 
    5871       </td>
    5872 
    5873     </tr>
    5874     <tr>
    5875       <td style="vertical-align: top; text-align: center;">109</td>
    5876       <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td>
    5877       <td align="left" valign="top">I/O</td>
    5878       <td align="left" valign="top">Binary/<br>
     1237<td style="vertical-align: top;"><br> </td> </tr>
     1238<tr> <td style="vertical-align: top; text-align: center;">109</td>
     1239<td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td>
     1240<td align="left" valign="top">I/O</td> <td align="left" valign="top">Binary/<br>
    58791241NetCDF-<br>
    5880 format</td>
    5881       <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>)
    5882 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>
    5883       <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
    5884       </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>),
     1242format</td> <td align="left" valign="top">This
     1243file 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>)
     1244in NetCDF format.&nbsp;</font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data
     1245in this file can be visualized by any graphic software which provides a
     1246NetCDF interface (e.g. <span style="font-weight: bold;">NCL
     1247</span>or<span style="font-weight: bold;"> ferret</span>).
     1248For 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>
     1249<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
     1250</font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of
     1251using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
    58851252seperate time series are output for each of the groups. The long names
    58861253of the variables in the NetCDF file containing the respective
    5887 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>
    5888       <br>
    5889       </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>
    5890       <td align="left" valign="top"></td>
    5891     </tr>
    5892     <tr>
    5893       <td style="text-align: center; vertical-align: top;">111</td>
    5894       <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td>
    5895       <td style="vertical-align: top;">I/O</td>
    5896       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    5897 
     1254timeseries 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
     1255group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
     1256<br> </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the
     1257PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter&nbsp;
     12584.5.1</a>.</font></font></font></font></td>
     1259<td align="left" valign="top"></td> </tr>
     1260<tr> <td style="text-align: center; vertical-align: top;">111</td>
     1261<td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td>
     1262<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    58981263NetCDF-<br>
    5899 
    5900 format</font></font></font></td>
    5901       <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
     1264format</font></font></font></td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
     1265contains data of the temporally averaged two-dimensional horizontal
    59021266cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
    5903 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>
    5904 
    5905       <br>
    5906 
     1267in NetCDF format. The data in this file can be visualized by any
     1268graphic 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>
    59071269More 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>
    5908       <td></td>
    5909     </tr>
    5910     <tr>
    5911       <td style="text-align: center; vertical-align: top;">112</td>
    5912       <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td>
    5913       <td style="vertical-align: top;">I/O</td>
    5914       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    5915 
     1270<td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">112</td>
     1271<td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td>
     1272<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    59161273NetCDF-<br>
    5917 
    5918 format</font></font></font></td>
    5919       <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)
     1274format</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
     1275averaged two-dimensional vertical (xz)
    59201276cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
    5921 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>
    5922 
    5923       <br>
    5924 
     1277in NetCDF format. The data in this file can be visualized by any
     1278graphic 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>
    59251279More 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>
    5926       <td></td>
    5927     </tr>
    5928     <tr>
    5929       <td style="text-align: center; vertical-align: top;">113</td>
    5930       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td>
    5931       <td style="vertical-align: top;">I/O</td>
    5932       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    5933 
     1280<td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">113</td>
     1281<td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td>
     1282<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    59341283NetCDF-<br>
    5935 
    5936 format</font></font></font></td>
    5937       <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
     1284format</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
     1285averaged two-dimensional vertical
    59381286(yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
    5939 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>
    5940 
    5941       <br>
    5942 
     1287in NetCDF format. The data in this file can be visualized by any
     1288graphic 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>
    59431289More 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>
    5944       <td></td>
    5945     </tr>
    5946     <tr>
    5947       <td style="text-align: center; vertical-align: top;">116</td>
    5948       <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td>
    5949       <td style="vertical-align: top;">I/O</td>
    5950       <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    5951 
     1290<td></td> </tr> <tr> <td style="text-align: center; vertical-align: top;">116</td>
     1291<td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td>
     1292<td style="vertical-align: top;">I/O</td> <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
    59521293NetCDF-<br>
    5953 
    5954 format</font></font></font></td>
    5955       <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>)
    5956 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>
    5957 
    5958       <br>
    5959 
     1294format</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
     1295averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
     1296in NetCDF format. The data in this file can be visualized by any
     1297graphic 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>
    59601298More 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>
    5961       <td></td>
    5962     </tr>
    5963 
    5964 
    5965 
    5966 
    5967 
    5968 
    5969  
    5970  
    5971  
    5972  
    5973  
    5974   </tbody>
    5975 </table>
    5976 
    5977 
    5978 
    5979 
    5980 
    5981 <font color="#000000"><br>
    5982 
    5983 
    5984 
    5985 
    5986 
    5987 </font>
     1299<td></td> </tr> </tbody>
     1300</table><font color="#000000"><br>
     1301</font><br>
     1302<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;
    59881303<br>
    5989 
    5990 
    5991 
    5992 
    5993 
    5994 <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>
    5995 
    5996 
    5997 
    5998 
    5999 
    60001304&nbsp;
    6001 <br>
    6002 
    6003 
    6004 
    6005 
    6006 
    6007 &nbsp;
    6008 <span style="font-style: italic;">Last change:</span> 07/11/06 (ML)<br>
    6009 
    6010 
    6011 
    6012 
    6013 
    6014 </font><br>
    6015 
    6016 
    6017 
    6018 
    6019 
    6020 </body></html>
     1305<span style="font-style: italic;">Last change:</span>
     1306$Id$<br>
     1307</font><br></body></html>

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

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3 
    4   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    5  
    6 
    7 
    8   <title>PALM chapter 3.5.1</title><meta name="GENERATOR" content="StarOffice 7 (Win32)">
    9 
    10   <meta name="AUTHOR" content="Siegfried Raasch">
    11 
    12   <meta name="CREATED" content="20040802;11451548">
    13 
    14   <meta name="CHANGED" content="20041112;14401801">
    15 
    16   <meta name="KEYWORDS" content="parallel LES model">
    17 
    18   <style>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
    195<!--
    206@page { size: 21cm 29.7cm }
    217-->
    22   </style></head>
    23 <body style="direction: ltr;" lang="en-US">
    24 
    25 <h3 style="line-height: 100%;">3.5.1 Interfaces for
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.5.1 Interfaces for
    2610user-defined code<br>
    27 
    28 </h3>
    29 
    30 <p style="margin-bottom: 0cm; line-height: 100%;">The
     11</h3><p style="margin-bottom: 0cm; line-height: 100%;">The
    3112following table
    3213describes the available interfaces for user-defined code in the model,
    … …  
    3415names and possible arguments of the subroutines involved as well as
    3516actions which can be accomplished in these subroutines. <br>
    36 
    3717&nbsp; </p>
    38 
    39 <table style="width: 100%;" border="1" cellpadding="2" cellspacing="4">
    40 
    41   <col width="211"> <col width="117"> <col width="862"> <tbody>
    42 
    43     <tr>
    44 
    45       <td width="211">
    46       <p><font size="4"><b>Call location</b></font></p>
    47 
    48       </td>
    49 
    50       <td width="117">
    51       <p><font size="4"><b>Subroutine name and
    52 argument</b></font></p>
    53 
    54       </td>
    55 
    56       <td style="width: 862px;">
    57       <p><font size="4"><b>Possible actions</b></font></p>
    58 
    59       </td>
    60 
    61     </tr>
    62 
    63     <tr><td>---</td><td><span style="font-family: monospace;"><a name="user"></a>MODULE user</span></td><td>All
     18<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
     19location</b></font></p> </td> <td width="117"> <p><font size="4"><b>Subroutine
     20name and
     21argument</b></font></p> </td> <td style="width: 862px;"> <p><font size="4"><b>Possible
     22actions</b></font></p> </td> </tr> <tr><td>---</td><td><span style="font-family: monospace;"><a name="user"></a>MODULE
     23user</span></td><td>All
    6424user-defined variables which are used outside the respective local
    65 scopes of the user-defined subroutines have to be declared here.</td></tr><tr valign="top">
    66 
    67       <td width="211">
    68       <p>End of <tt><font style="font-size: 10pt;" size="2">parin.f90</font></tt></p>
    69 
    70       </td>
    71 
    72       <td width="117">
    73       <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_parin"></a>user_parin</font></font></tt></p>
    74 
    75       </td>
    76 
    77       <td width="862">
    78       <p>Declaration of user-defined parameters in the NAMELIST
     25scopes of the user-defined subroutines have to be declared here.</td></tr><tr valign="top"> <td width="211"> <p>End
     26of <tt><font style="font-size: 10pt;" size="2">parin.f90</font></tt></p>
     27</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>
     28</td> <td width="862"> <p>Declaration of
     29user-defined parameters in the NAMELIST
    7930group <tt><font style="font-size: 10pt;" size="2">&amp;userpar</font></tt>.
    8031These
    … …  
    8536and must not be changed. Additional NAMELIST groups may be declared if
    8637desired.&nbsp; <br>
    87 
    8838The CPU time needed for executing <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt>
    8939is included in the
    9040local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
    91 within the category &ldquo;initialisation&rdquo;.</p>
    92 
    93       </td>
    94 
    95     </tr>
    96 
    97     <tr valign="top">
    98 
    99       <td width="211">
    100       <p>End of <tt><font style="font-size: 10pt;" size="2">header.f90</font></tt></p>
    101 
    102       </td>
    103 
    104       <td width="117">
    105       <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>
    106 
    107       </td>
    108 
    109       <td width="862">
    110       <p>Output of the values of the user-defined parameters to
     41within the category &ldquo;initialisation&rdquo;.</p> </td>
     42</tr> <tr valign="top"> <td width="211"><p>End
     43of <tt><font style="font-size: 10pt;" size="2">header.f90</font></tt></p>
     44</td>
     45<td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_header"></a>user_header(
     46io )</font></font></tt></p> </td> <td width="862"> <p>Output of the values of the
     47user-defined parameters to
    11148the
    11249local files <a href="chapter_3.4.html#HEADER">HEADER</a>
    … …  
    12562user-defined
    12663subdomains are displayed by default (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).</p>
    127 
    128       </td>
    129 
    130     </tr>
    131 
    132     <tr valign="top">
    133 
    134       <td width="211">
    135       <p>End of <tt><font style="font-size: 10pt;" size="2">init_3d_model.f90</font></tt></p>
    136 
    137       </td>
    138 
    139       <td width="117">
    140       <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_init"></a>user_init</font></font></tt></p>
    141 
    142       </td>
    143 
    144       <td width="862">
    145       <p>Here, user-defined initialization actions which should
     64</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>
     65</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>
     66</td> <td width="862"> <p>Here, user-defined
     67initialization actions which should
    14668be
    14769accomplished before the start of the 3D-model can be implemented (e.g.
    … …  
    15072the model (<a href="chapter_4.1.html">chapter
    151734.1</a>) have already been carried out at all.&nbsp; </p>
    152 
    153       <p>One of the most important actions here is the definition
     74<p>One of the most important actions here is the definition
    15475of
    15576user-defined subdomains for statistic analysis and output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>
    15677and <a href="chapter_3.5.3.html">chapter
    157 3.5.3</a>) and of additional time series quantities (see comment line example in the file).&nbsp; <br>
    158 
     783.5.3</a>) and of additional time series quantities (see comment
     79line example in the file).&nbsp; <br>
    15980CPU time for <tt><font style="font-size: 10pt;" size="2">user_init</font></tt>
    16081is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
    161 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>
    162 
    163       </td>
    164 
    165     </tr>
    166 
    167     <tr>
    168 
    169       <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2">DEFAULT</font></tt>
     82within the category &ldquo;initialisation&rdquo;.</p><p>See
     83also <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>
     84</td> </tr> <tr> <td style="vertical-align: top;"><tt><font style="font-size: 10pt;" size="2">DEFAULT</font></tt>
    17085case of <tt><font style="font-size: 10pt;" size="2">SELECT
    17186CASE( TRIM(topography) ) </font></tt>command in the
    172 middle&nbsp;of <tt><font style="font-size: 10pt;" size="2">init_grid.f90</font></tt></td>
    173 
    174       <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>
    175 
    176       <td>
    177       <p>Execution of user-defined grid initializing actions.</p>
    178 
    179       <p>Here, the user can define the two-dimensional index
     87middle&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>
     88<td> <p>Execution of user-defined grid initializing
     89actions.</p> <p>Here, the user can define the
     90two-dimensional index
    18091array&nbsp;<tt><font style="font-size: 10pt;" size="2">nzb_local</font></tt> that is used to
    18192set up a non-flat topography. This requires definition of at least one
    … …  
    18495in&nbsp;<tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt>.
    18596Note that the <a href="chapter_4.1.html#topography">topography</a>&nbsp;modes
    186       <span style="font-style: italic;">'flat'</span>
     97<span style="font-style: italic;">'flat'</span>
    18798and <span style="font-style: italic;">'single_building'</span>
    18899are not allowed here since these are the standard cases used in the
    189 calling routine <tt><font style="font-size: 10pt;" size="2">init_grid</font></tt>. </p>
    190 
    191       <p>CPU time for <tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt>
     100calling routine <tt><font style="font-size: 10pt;" size="2">init_grid</font></tt>. </p> <p>CPU
     101time for <tt><font style="font-size: 10pt;" size="2">user_init_grid</font></tt>
    192102is considered in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
    193 within the category &ldquo;initialisation&rdquo;.</p>
    194 
    195       </td>
    196 
    197     </tr>
    198 
    199     <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
     103within the category &ldquo;initialisation&rdquo;.</p> </td>
     104</tr> <tr><td style="vertical-align: top;">In
     105the 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
    200106the complete initialization of the 3d model. The user is responsible to
    201 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">
    202 
    203       <td width="211">
    204       <p>In the middle of <tt><font style="font-size: 10pt;" size="2">init_particles.f90</font></tt></p>
    205 
    206       </td>
    207 
    208       <td width="117">
    209       <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>
    210 
    211       </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">particles</font></font></tt></p>
    212 
    213       </td>
    214 
    215       <td width="862">
    216       <p>With this routine e.g. size and color of particles,
     107set 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
     108the middle of <tt><font style="font-size: 10pt;" size="2">init_particles.f90</font></tt></p>
     109</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>
     110</td> <td width="862"> <p>With this routine
     111e.g. size and color of particles,
    217112which have
    218113been released initially from a source, can be specified. Like the
    … …  
    220115this routine is only
    221116called if particle advection is switched on (see package parameter <a href="chapter_4.2.html#dt_prel">dt_prel</a>).</p>
    222 
    223       </td>
    224 
    225     </tr>
    226 
    227     <tr valign="top">
    228 
    229       <td width="211">
    230       <p>End of <tt><font style="font-size: 10pt;" size="2">advec_particles.f90</font></tt></p>
    231 
    232       </td>
    233 
    234       <td width="117">
    235       <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>
    236 
    237       </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">attributes</font></font></tt></p>
    238 
    239       </td>
    240 
    241       <td width="862">
    242       <p>Here the particles can be assigned new attributes
     117</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>
     118</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>
     119</td> <td width="862"> <p>Here the particles
     120can be assigned new attributes
    243121(diameter,
    244122color 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
    245123routine is only
    246124called if particle advection is switched on (see package parameter <a href="chapter_4.2.html#dt_prel">dt_prel</a>).</p>
    247 
    248       </td>
    249 
    250     </tr>
    251 
    252     <tr valign="top">
    253 
    254       <td width="211">
    255       <p>Before the plot of particles and cross-sections in <br>
    256 
    257       <tt><font style="font-size: 10pt;" size="2">dvrp_plot.f90</font></tt></p>
    258 
    259       </td>
    260 
    261       <td width="117">
    262       <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_dvrp_coltab"></a>user_dvrp_coltab
     125</td> </tr> <tr valign="top"> <td width="211"> <p>Before the plot of particles and
     126cross-sections in <br> <tt><font style="font-size: 10pt;" size="2">dvrp_plot.f90</font></tt></p>
     127</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
    263128(</font></font></tt><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> mode )</font></font></tt></p>
    264 
    265       </td>
    266 
    267       <td width="862">
    268       <p>With this routine, color tables can be adjusted which
     129</td> <td width="862"> <p>With this routine,
     130color tables can be adjusted which
    269131should
    270132be used for output with the dvrp software. Individuell color tables for
    … …  
    280142can have the values &ldquo;<i>particles&rdquo;</i>
    281143or &ldquo;<i>slicer&rdquo;</i>).&nbsp; <br>
    282 
    283144This routine only becomes active if dvrp-graphics is switched on (see
    284145package parameter <a href="chapter_4.2.html#dt_dvrp">dt_dvrp</a>).</p>
    285 
    286       </td>
    287 
    288     </tr>
    289 
    290     <tr valign="top">
    291 
    292       <td width="211">
    293       <p>Beginning and end of the time integration loop
    294 of&nbsp; <br>
    295 
    296       <tt><font style="font-size: 10pt;" size="2">time_integration.f90</font></tt>
    297 as well as after each prognostic equation in <br>
    298 
    299       <tt><font style="font-size: 10pt;" size="2">prognostic_equations.f90</font></tt></p>
    300 
    301       </td>
    302 
    303       <td width="117">
    304       <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>
    305 
    306       <p>or<br>
    307 
    308       <font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2"> </font></font>
    309       </p>
    310 
    311       <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>
    312 
    313       </td>
    314 
    315       <td width="862">
    316      
    317 
    318       <p>In this routine user actions can be implemented which
     146</td> </tr> <tr valign="top"> <td width="211"> <p>Beginning and end of the time
     147integration loop
     148of&nbsp; <br> <tt><font style="font-size: 10pt;" size="2">time_integration.f90</font></tt>
     149as well as after each prognostic equation in <br> <tt><font style="font-size: 10pt;" size="2">prognostic_equations.f90</font></tt></p>
     150</td> <td width="117"> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><a name="user_actions"></a>user_actions(
     151location )</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> </font></font> </p>
     152<p>or<br> <font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2"> </font></font>
     153</p> <p><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">user_actions(
     154i, 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>
     155</td> <td width="862"> <p>In this routine
     156user actions can be implemented which
    319157are to
    320158be executed either at each time step or at certain times (defined by
    … …  
    328166For example, if called at the beginning of a time step, <tt><font style="font-size: 10pt;" size="2">location</font></tt>
    329167=&nbsp;<i>'before_timestep' </i>and if
    330 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>
     168called 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
     169of 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>
    331170if the
    332171cache-optimized version of <span style="font-family: monospace;">prognostic_equation.f90</span>
    … …  
    335174passed as arguments for
    336175all calls within <span style="font-family: monospace;">prognostic_equations</span>.
    337       </p>
    338 
    339       <p>CPU time for <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt>
     176</p> <p>CPU time for <tt><font style="font-size: 10pt;" size="2">user_actions</font></tt>
    340177appears within the category &ldquo;user_actions&rdquo; in the
    341178local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>.
    … …  
    344181needed outside of the prognostic equations. Time needed for calls
    345182within prognostic_equations is considered within the category "all
    346 prog.equations".<br>
    347 
    348       </p>
    349 
    350       <p><b>Important:</b> this subroutine is written
     183prog.equations".<br> </p> <p><b>Important:</b>
     184this subroutine is written
    351185as a FORTRAN
    352186module, which uses so-called function overloading. It can be called in
    … …  
    362196respective 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
    363197in the CASE
    364 structure of <tt><font style="font-size: 10pt;" size="2">user_actions_ij</font></tt>!</p>
    365 
    366       </td>
    367 
    368     </tr>
    369 
    370     <tr valign="top">
    371 
    372       <td width="211">
    373       <p><tt><font style="font-size: 10pt;" size="2">flow_statistics.f90</font></tt>
     198structure of <tt><font style="font-size: 10pt;" size="2">user_actions_ij</font></tt>!</p> </td>
     199</tr> <tr valign="top"> <td width="211"><p><tt><font style="font-size: 10pt;" size="2">flow_statistics.f90</font></tt>
    374200before the summation of array <span style="font-family: monospace;">hom</span>
    375 (horizontal averages)<br>
    376 
    377       </p>
    378 
    379       </td>
    380 
    381       <td width="117">
    382       <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>
    383 
    384       </td>
    385 
    386       <td width="862">
    387       <p>Horizontal
     201(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>(
     202sr )</font></font></tt></p> </td> <td width="862"> <p>Horizontal
    388203averages of vertical profiles of user-defined
    389204quantities can be computed here. Also, additional time series
    390205quantities can be calculated. They have to be defined before in routine
    391 <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
     206<a href="#user_init"><span style="font-family: Courier New,Courier,monospace;">user_init</span></a>.
     207The 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
     208routine contains some simple examples (as comment lines) in order to
     209demonstrate how to use it.</p><p><br>Profiles have to
     210be written to
    392211the array <tt><font style="font-size: 10pt;" size="2">sums</font></tt>.
    393212Please use profile numbers starting from 70 upward (thus e.g. <tt><font style="font-size: 10pt;" size="2">sums (&hellip;,
    39421360) =</font></tt><font style="font-size: 10pt;" size="2">&hellip;)</font>. These additional
    395214profiles
    396 are temporally averaged in <tt><font style="font-size: 10pt;" size="2">flow_statistics</font></tt>.</p>
    397 
    398       </td>
    399 
    400     </tr>
    401 
    402     <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">
    403 
    404       <td width="211">
    405       <p>End of <tt><font style="font-size: 10pt;" size="2">palm.f90</font></tt></p>
    406 
    407       </td>
    408 
    409       <td width="117">
    410       <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>
    411 
    412       </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">action</font></font></tt></p>
    413 
    414       </td>
    415 
    416       <td width="862">
    417       <p>User-defined actions which are to be executed at the end
     215are temporally averaged in <tt><font style="font-size: 10pt;" size="2">flow_statistics</font></tt>.</p> </td>
     216</tr> <tr><td style="vertical-align: top;">End
     217of <span style="font-family: monospace;">check_parameters.f90</span>
     218where 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(
     219variable, unit )</span></td><td style="vertical-align: top;">Here the <span style="font-family: monospace;">unit</span>(s) of
     220user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>)
     221have to be set. Input parameter <span style="font-family: monospace;">variable</span>
     222contains the string identifier of the respective variable. For those
     223variables not recognized by the user, the parameter <span style="font-family: monospace;">unit</span> is set to
     224"illegal", which tells the calling routine that the output variable is
     225not defined and leads to a program abort.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about
     226creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;"><span style="font-family: monospace;">netcdf.f90</span> (4
     227times) where the vertical grid coordinates for cross sections and
     228volume 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(
     229variable, found, grid_x, grid_y, grid_z )</span></td><td style="vertical-align: top;">Set the grid on which
     230user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>)
     231are defined. Input parameter <span style="font-family: monospace;">variable</span>
     232contains the string identifier of the respective variable. Allowed
     233values are <span style="font-style: italic;">'x'</span>
     234and <span style="font-style: italic;">'xu'</span>
     235for <span style="font-family: monospace;">grid_x</span>,
     236<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
     237output parameter <span style="font-family: monospace;">found</span>
     238has to be set <span style="font-style: italic;">.TRUE.</span>
     239by the user, otherwise an error message will appear in the job protocol
     240for the respective output quantity.<br><br><span style="font-weight: bold;">Example:</span><br>If
     241an output quantity is defined at the center of the grid boxes, the
     242following 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
     243defining an output quantity at the grid points where the
     244u-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
     245<a href="chapter_3.5.4.html">chapter 3.5.4</a> about
     246creating 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(
     247av, variable, found, grid, local_pf )</span></td><td style="vertical-align: top;">Resorts&nbsp;user-defined&nbsp;quantities
     248(to be output as cross-section data;&nbsp;see <a href="chapter_4.3.html#data_output_user">data_output_user</a>)
     249with indices (k,j,i) to a temporary array <span style="font-family: monospace;">local_pf</span> with
     250indices (i,j,k) and sets the <span style="font-family: monospace;">grid</span>
     251on which they are defined. Depending on the value of input parameter <span style="font-family: monospace;">av</span> resorting is
     252done for instantaneous (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">0</span>) or time averaged
     253data (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">1</span>). Input parameter
     254<span style="font-family: monospace;">variable</span>
     255contains the string identifier of the respective variable. Allowed
     256values for <span style="font-family: monospace;">grid</span>
     257are&nbsp;<span style="font-style: italic;">'zu'</span>
     258and&nbsp;<span style="font-style: italic;">'zw'</span>.
     259The output parameter <span style="font-family: monospace;">found</span>
     260has to be set <span style="font-style: italic;">.TRUE.</span>
     261by the user, otherwise an error message will appear in the job protocol
     262for the respective output quantity.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about
     263creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;"><span style="font-family: monospace;">data_output_3d.f90</span>
     264at 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(
     265av, variable, found, local_pf, nz_do )</span></td><td style="vertical-align: top;">Resorts&nbsp;user-defined&nbsp;quantities
     266(to be output as volume data;&nbsp;see <a href="chapter_4.3.html#data_output_user">data_output_user</a>)
     267with indices (k,j,i) to a temporary array <span style="font-family: monospace;">local_pf</span> with
     268indices (i,j,k) and sets the <span style="font-family: monospace;">grid</span>
     269on which they are defined. Depending on the value of input parameter <span style="font-family: monospace;">av</span> resorting is
     270done for instantaneous (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">0</span>) or time averaged
     271data (<span style="font-family: monospace;">av</span>=<span style="font-style: italic;">1</span>). Input parameter
     272<span style="font-family: monospace;">variable</span>
     273contains 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
     274parameter <span style="font-family: monospace;">nz_do</span>
     275defines the upper limit of vertical grid index k of the output array
     276(see <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>).
     277The output parameter <span style="font-family: monospace;">found</span>
     278has to be set <span style="font-style: italic;">.TRUE.</span>
     279by the user, otherwise an error message will appear in the job protocol
     280for the respective output quantity.<br><br>See <a href="chapter_3.5.4.html">chapter 3.5.4</a> about
     281creating user-defined output quantities.</td></tr><tr><td style="vertical-align: top;">End of <span style="font-family: monospace;">average_3d_data.f90</span>,
     282middle 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(
     283mode, variable )</span></td><td style="vertical-align: top;">Sum up and time-average of
     284user-defined output quantities (see <a href="chapter_4.3.html#data_output_user">data_output_user</a>)
     285as well as allocation of the arrays necessary for storing the
     286respective averages. Input parameter <span style="font-family: monospace;">variable</span>
     287contains the string identifier of the respective variable. Depending on
     288the requested action, input parameter <span style="font-family: monospace;">mode</span> has the
     289value <span style="font-style: italic;">'allocate'</span>,
     290<span style="font-style: italic;">'sum'</span>, or <span style="font-style: italic;">'average'</span>.<br><br>See
     291<a href="chapter_3.5.4.html">chapter 3.5.4</a> about
     292creating user-defined output quantities. </td></tr><tr valign="top"> <td width="211"> <p>End
     293of <tt><font style="font-size: 10pt;" size="2">palm.f90</font></tt></p>
     294</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>
     295</td> <td width="862"> <p>User-defined
     296actions which are to be executed at the end
    418297of a
    419298model run. When <tt><font style="font-size: 10pt;" size="2">user_last_actions</font></tt>
    … …  
    423302are also not carried
    424303out yet.&nbsp; <br>
    425 
    426304CPU time for <tt><font style="font-size: 10pt;" size="2">user_last_actions</font></tt>
    427305appears in the local file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a>
    428306within the category &ldquo;last actions&rdquo; (the time
    429307necessary for <tt><font style="font-size: 10pt;" size="2">close_files</font></tt> is included).</p>
    430 
    431       </td>
    432 
    433     </tr>
    434 
    435   </tbody>
    436 </table>
    437 
    438 <hr>
    439 <p style="line-height: 100%;"><br>
    440 
    441 <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>
    442 
    443 <p style="line-height: 100%;"><i>Last
    444 change:&nbsp;</i>&nbsp;23/03/06 (SR)</p>
    445 
     308</td> </tr> </tbody></table><hr>
     309<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
     310change: </i>$Id$</p>
    446311</body></html>

  • palm/trunk/DOC/app/chapter_3.5.2.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 3.5.2</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20040802;13321506">
    8   <meta name="CHANGED" content="20041112;14455666">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;">&nbsp;3.5.2 Definition of user-defined
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">&nbsp;3.5.2 Definition of
     10user-defined
    1811parameters</h3>
    19 <p style="line-height: 100%;">As for the model in general, also the
     12<p style="line-height: 100%;">As for the model in general,
     13also the
    2014user-defined code will have to be steered by parameters. For each
    2115run the model should to be able to read in current values of these
    … …  
    2519This module must be declared in all relevant user-defined routines via
    2620a USE statement, in order to make the parameters available. </p>
    27 <p style="line-height: 100%;">The user can assign values to the
     21<p style="line-height: 100%;">The user can assign values
     22to the
    2823user-defined parameters within the NAMELIST group <tt><font style="font-size: 11pt;" size="2">&amp;userpar
    29 <font size="3"><font face="Thorndale, serif">in the local file</font></font>
     24<font size="3"><font face="Thorndale, serif">in
     25the local file</font></font>
    3026<a href="chapter_3.4.html#PARIN">PARIN</a></font></tt>.
    3127This NAMELIST group must be located after the initialization
    … …  
    3329</font><tt><font style="font-size: 10pt;" size="2">&amp;d3par</font></tt>)
    3430(see <a href="chapter_4.0.html">chapter
    35 4.0</a>). Before values of the user-defined parameters can be assigned,
     314.0</a>). Before values of the user-defined parameters can be
     32assigned,
    3633the parameters must be declared within the appropriate NAMELIST
    3734statement in the user-defined subroutine <tt><font style="font-size: 10pt;" size="2">user_parin</font></tt>.
    3835</p>
    39 <p style="line-height: 100%;">The following example illustrates the
     36<p style="line-height: 100%;">The following example
     37illustrates the
    4038procedure. The example assumes that the user declares a
    4139LOGICAL variable named <tt><font style="font-size: 10pt;" size="2">abcd</font></tt>
    4240for steering the user-defined code. This variable
    4341must be declared in the module <tt>user</tt>: </p>
    44 <ul>
    45   <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">LOGICAL:: abcd = .FALSE.</font></tt></p>
    46 </ul>
    47 <p style="line-height: 100%;">Pay attention that in this example a
     42<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">LOGICAL:: abcd =
     43.FALSE.</font></tt></p>
     44</ul><p style="line-height: 100%;">Pay attention
     45that in this example a
    4846default value (.FALSE.) is assigned to the variable and it will keep
    4947this value if nothing else is assigned within the file <tt>PARIN</tt>.
    50 In <tt><font style="font-size: 10pt;" size="2">user_parin</font> <font face="Thorndale, serif">the</font></tt>
     48In <tt><font style="font-size: 10pt;" size="2">user_parin</font>
     49<font face="Thorndale, serif">the</font></tt>
    5150NAMELIST must be extended by the name of the new variable: </p>
    52 <ul>
    53   <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">NAMELIST /userpar/ &nbsp;abcd, data_output_user, region.</font></tt></p>
    54 </ul>
    55 <p style="line-height: 100%;">In the parameter file PARIN a value can
     51<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">NAMELIST /userpar/
     52&nbsp;abcd, data_output_user, region.</font></tt></p>
     53</ul><p style="line-height: 100%;">In the parameter
     54file PARIN a value can
    5655be assigned: </p>
    57 <ul>
    58   <p style="line-height: 100%;">. <br>
    59 . <br>
    60   <tt><font style="font-size: 10pt;" size="2">&amp;userpar abcd = .T.,</font></tt><font style="font-size: 10pt;" size="2"> ...</font></p>
    61 </ul>
    62 <p style="line-height: 100%;">User defined parameters in the file PARIN
     56<ul> <p style="line-height: 100%;">. <br>
     57. <br> <tt><font style="font-size: 10pt;" size="2">&amp;userpar abcd = .T.,</font></tt><font style="font-size: 10pt;" size="2"> ...</font></p>
     58</ul><p style="line-height: 100%;">User defined
     59parameters in the file PARIN
    6360are
    6461considered as run parameters, i.e. they must be specified again for
    6562each restart run.</p>
    66 <p style="line-height: 100%;">In each case the user should carry out
     63<p style="line-height: 100%;">In each case the user should
     64carry out
    6765a control output of the parameter values, so
    6866that their values during the respective model run are really known. For
    … …  
    7371is available. <br>
    7472&nbsp; </p>
    75 <hr>
    76 <p style="line-height: 100%;"><br>
     73<hr><p style="line-height: 100%;"><br>
    7774&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>
    78 </font></font></p>
    79 <p style="line-height: 100%;"><span style="font-style: italic;">Last
    80 change:</span> 24/03/06 (SR)<font color="#000080"><font color="#000080"><br>
    81 </font></font></p>
    82 </body></html>
     75</font></font></p><p style="line-height: 100%;"><span style="font-style: italic;">Last
     76change:</span> $Id$<font color="#000080"><font color="#000080"><br>
     77</font></font></p></body></html>

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

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 3.5.3</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20040802;14001660">
    8   <meta name="CHANGED" content="20041112;14483720">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;">3.5.3 Definition of user-defined
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.5.3 Definition of user-defined
    1810subdomains</h3>
    19 <p style="line-height: 100%;">By default, the values of the timeseries quantities and the horizontally averaged vertical profiles (saved in local files
     11<p style="line-height: 100%;">By default, the values of
     12the timeseries quantities and the horizontally averaged vertical
     13profiles (saved in local files
    2014<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
    2115and <a href="chapter_3.4.html#LIST_PROFIL">LIST_PROFIL</a>)
    … …  
    2519via the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
    2620</p>
    27 <p style="line-height: 100%;">The exact definition of these subdomains
     21<p style="line-height: 100%;">The exact definition of
     22these subdomains
    2823has to be made by the user within the user-defined subroutine
    29 <tt><font style="font-size: 10pt;" size="2">init_user</font></tt>. The
     24<tt><font style="font-size: 10pt;" size="2">init_user</font></tt>.
     25The
    3026subdomains are defined with a mask array named <tt><font style="font-size: 10pt;" size="2">rmask</font></tt>,
    3127which has to be given the value 1.0 for all horizontal grid points
    … …  
    3632is
    3733declared as: </p>
    38 <ul>
    39   <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>
    40 </ul>
    41 <p style="line-height: 100%;">The first two indices are the grid point
     34<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">REAL :: rmask
     35(nys-1:nyn+1,nxl-1,nxr+1,0:9) .</font></tt></p>
     36</ul><p style="line-height: 100%;">The first two
     37indices are the grid point
    4238indices 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">,
    4339</font><tt><font style="font-size: 10pt;" size="2">nxr</font></tt><font style="font-size: 10pt;" size="2">,
    … …  
    5652carries the index 0, the user-defined subdomains have the values 1 to
    57539. </p>
    58 <p style="line-height: 100%;">The following example should illustrate
     54<p style="line-height: 100%;">The following example should
     55illustrate
    5956this. Two subdomains are defined by the user. The first is determined
    6057by all grid
    … …  
    6663domain. This may be obtained by the following lines of code in <tt><font style="font-size: 10pt;" size="2">user_init</font></tt>:
    6764</p>
    68 <ul>
    69   <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">USE
    70 grid_variables</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
    71   </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>
    72   </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>
    73   </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>
    74   </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>
    75   </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>
    76   </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>
    77   </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>
    78   </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>
    79   </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>
    80   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp; x = i * dx</font></font></tt><br>
    81   <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>
    82   </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>
    83   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    84 radial_distance = SQRT( ( x - disc_center_x )**2 + &amp;</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
    85   </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;
    86 ( y - disc_center_y )**2 )</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"> <br>
    87   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp; &nbsp; &nbsp; IF ( radial_distance
    88 &gt; disc_radius )&nbsp; THEN</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
    89   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    90 rmask(j,i,1) = 0.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
    91   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    92 rmask(j,i,2) = 1.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
    93   </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>
    94   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    95 rmask(j,i,1) = 1.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
    96   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    97 rmask(j,i,2) = 0.0</font></font></tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace"><br>
    98   </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>
    99   </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>
    100   </font></font><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">ENDDO</font></font></tt></p>
    101 </ul>
    102 <p style="line-height: 100%;">The module <span style="font-family: monospace;">statistics</span> must be used,
     65<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">USE
     66grid_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 *
     67disc_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>
     68<tt><font style="font-size: 10pt;" size="2"><font face="Cumberland, monospace">&nbsp;&nbsp;
     69DO&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;
     70y = 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;
     71radial_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;
     72( 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;
     73&nbsp; IF ( radial_distance
     74&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;
     75rmask(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;
     76rmask(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;
     77ELSE</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;
     78rmask(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;
     79rmask(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;
     80ENDIF</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>
     81</ul><p style="line-height: 100%;">The module <span style="font-family: monospace;">statistics</span> must
     82be used,
    10383because it contains <span style="font-family: monospace;">rmask</span>
    10484and the modules <span style="font-family: monospace;">grid_variables</span>
    105 and <span style="font-family: monospace;">indices</span> are
     85and <span style="font-family: monospace;">indices</span>
     86are
    10687necessary in this example, because grid spacing and indices are used.
    10788All array elements of <span style="font-family: monospace;">rmask</span>
    108 (<span style="font-family: monospace;">rmask(:,:,:)</span>) are preset
     89(<span style="font-family: monospace;">rmask(:,:,:)</span>)
     90are preset
    10991by the model with 1.0. In no case this assignment must be
    11092changed for the total domain (<span style="font-family: monospace;">rmask(:,:,0)</span>)!
    … …  
    11294if
    11395the user sets <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>
    114 &ge; <i>1</i>. Beyond that, names for the user-defined subdomains can be
     96&ge; <i>1</i>. Beyond that, names for the user-defined
     97subdomains can be
    11598assigned
    11699via the initialization parameter <a href="chapter_4.3.html#region">region</a>.
    … …  
    121104<br>
    122105&nbsp; </p>
    123 <hr>
    124 <p style="line-height: 100%;"><br>
    125 <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>
    126 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 07/03/07 (SR)</p>
     106<hr><p style="line-height: 100%;"><br>
     107<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>
     108$Id$</p>
    127109</body></html>

  • palm/trunk/DOC/app/chapter_3.5.4.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 3.5.5</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20040802;14050943">
    8   <meta name="CHANGED" content="20041117;12180008">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 <body dir="ltr" lang="en-US">
    16 <h3 style="line-height: 100%;"><font size="4">3.5.4 User-defined output quantities<br>
    17 </font></h3>A very typical request of users is the calculation and
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;"><font size="4">3.5.4
     10User-defined output quantities<br>
     11</font></h3>A very typical request of users is the
     12calculation and
    1813output of
    1914quantities which are not part of PALM's standard output. The basic user
    2015interface includes a number of subroutines which allow the calculation
    2116of user-defined quantities and output of these quantities as 2d cross
    22 section or 3d volume data. The respective subroutines contain&nbsp;as
     17section or 3d volume data. The respective subroutines
     18contain&nbsp;as
    2319an example code lines (written as comment lines) for calculating and
    2420output the square of the u-component velocity (note: this quantity
    … …  
    3026quantity "square of the u-component". If more than one user-defined
    3127quantity shall be output, these steps have to be carried out in the
    32 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>.
     28same way for each of the quantities.<br><br><ol><li>The
     29quantity has to be given a unique string identifier, e.g. <span style="font-style: italic;">'u2'</span>.
    3330This identifier must be different from the identifiers used for the
    34 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>
     31PALM standard output (see list in description of parameter <a href="chapter_4.2.html#data_output">data_output</a>).
     32To switch on output of this quantity, the user has to assign the string
     33identifier to the parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>,
     34eg.:<br><br><span style="font-family: monospace;">&nbsp;
     35&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
     36pure string <span style="font-style: italic;">'u2'</span>
    3537switches on the output of instantaneous 3d volume data. Output of cross
    3638section data and time averaged data is switched on by additionally
    37 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>
     39appending the strings <span style="font-style: italic;">'_xy'</span>,
     40<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
     41detailed explanation see parameter <a href="chapter_4.2.html#data_output">data_output</a>).<br><br></li><li>In
     42order to store the quantities' grid point data within PALM, a 3d data
     43array 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,
     44DIMENSION(:,:,:), ALLOCATABLE ::&nbsp; u2, u2_av</span><br><br>The
     45second array <span style="font-family: monospace;">u2_av</span>
    3846is needed in case that output of time averaged data is requested. It is
    3947used to store the sum of the data of the respective time levels over
    40 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
     48which the average has to be carried out.<br><br><br></li><li>The
     49data 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;
     50ALLOCATE( u2(nzb:nzt+1,nys-1:nyn+1,nxl-1:nxr+1) )</span><br><br>In
    4151case that output of time averaged data is requested, the array
    4252containing the sum has possibly to be read from the restart file (local
    43 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;
    44 &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;
    45 &nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp; PRINT*, '+++ user_init: unknown
     53filename <a href="chapter_3.4.html#BININ">BININ</a>)
     54by executing the following code in <span style="font-family: monospace;">user_init</span>:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;
     55&nbsp;IF ( initializing_actions == 'read_restart_data' )&nbsp;
     56THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;
     57&nbsp; READ ( 13 )&nbsp; field_chr</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     58&nbsp; &nbsp;DO&nbsp; WHILE ( TRIM( field_chr ) /= '*** end
     59user ***' )</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     60&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;
     61&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;
     62&nbsp;&nbsp; &nbsp; ALLOCATE(
     63u2_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;
     64&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;
     65&nbsp;&nbsp; &nbsp; &nbsp;&nbsp; CASE DEFAULT</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     66&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp; PRINT*,
     67'+++ user_init: unknown
    4668variable named "', &amp;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    4769&nbsp; &nbsp;&nbsp;
    48 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TRIM(
     70&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     71TRIM(
    4972field_chr ), '" found in'</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    5073&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; PRINT*,
    5174'&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    52 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
     75data from prior run on PE ', myid</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     76&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     77&nbsp; CALL local_stop</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;
     78&nbsp; &nbsp; &nbsp;&nbsp; END SELECT<br>&nbsp;
     79&nbsp; &nbsp;&nbsp; ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;
     80&nbsp;ENDIF</span><br style="font-family: monospace;"><br><br></li><li>The
     81quantity 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 (
     82'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     83&nbsp;&nbsp; unit = 'm2/s2'</span><br>&nbsp;<br>Otherwise,
     84PALM will abort.<br><br><br></li><li>The
    5385vertical grid on which the quantity is defined (given by the levels
    5486'zu' or 'zw', on which the u- or w-component of the velocity are
    55 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
     87defined) 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;
     88&nbsp;CASE ( 'u2', 'u2_xy', 'u2_xz', 'u2_yz' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;
     89&nbsp; &nbsp; grid = 'zu'</span><br>&nbsp;<br>As
     90the example shows, this grid has to be defined for the 3d volume data
     91as well as for all of the three cross sections.<br><span style="font-family: monospace;"><br><br></span></li><li>After
     92each timestep, the quantity has to be calculated at all gridpoints and
     93to 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>
     94at location 'after_integration':<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;CASE
     95( '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;
     96Enter actions to be done after every time integration (before</span><br style="font-family: monospace;"><span style="font-family: monospace;">!--&nbsp;&nbsp;&nbsp;
     97data output)</span><br style="font-family: monospace;"><span style="font-family: monospace;">!--&nbsp;&nbsp;&nbsp;
     98Sample for user-defined output:</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     99DO&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;
     100DO&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;
     101DO&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;
     102u2(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;
     103ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     104ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     105ENDDO</span><br><br>&nbsp;<br></li><li>In
    56106case that output of time-averaged data is requested, the sum- and
    57107average-operations as well as the allocation of the sum-array have to
    58 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;
    59 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;
    60 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;
    61 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;
    62 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;
    63 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;
    64 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;
     108be 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;
     109IF ( mode == 'allocate' )&nbsp; THEN<br>&nbsp; &nbsp;
     110...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     111CASE ( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     112IF ( .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;
     113ALLOCATE( 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;
     114ENDIF</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     115u2_av = 0.0<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     116ELSEIF ( mode == 'sum' )&nbsp; THEN<br>&nbsp; &nbsp;
     117...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CASE
     118( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     119DO&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;
     120DO&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;
     121DO&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;
     122u2_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;
     123ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     124ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     125ENDDO<br>&nbsp; &nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     126ELSEIF ( mode == 'average' )&nbsp; THEN<br>&nbsp;
     127&nbsp; ...</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CASE
     128( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     129DO&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;
     130DO&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;
     131DO&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;
     132u2_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;
     133ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     134ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     135ENDDO</span><br><br>&nbsp;</li><li>For
     136output of 2d cross sections, the gridpoint data of the quantity has to
     137be resorted to array <span style="font-family: monospace;">local_pf</span>
     138in subroutine <a href="chapter_3.5.1.html#user_data_output_2d"><span style="font-family: monospace;">user_data_output_2d</span></a>.
     139Also the vertical grid, on which the quantity is defined, has to be set
     140again:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;CASE
     141( 'u2_xy', 'u2_xz', 'u2_yz' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     142IF ( av == 0 )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     143DO&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;
     144DO&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;
     145DO&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;
     146local_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;
     147ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     148ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     149ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     150ELSE</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     151DO&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;
     152DO&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;
     153DO&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;
     154local_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;
     155ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     156ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     157ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     158ENDIF</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     159grid = 'zu'</span><br>&nbsp;<br>The <span style="font-family: monospace;">ELSE</span> case is
     160only needed in case that output of time-averaged data is requested.<br><br><br></li><li>For
     161output of 3d volume data, the gridpoint data of the quantity has to be
     162resorted to array <span style="font-family: monospace;">local_pf</span>
     163in subroutine <a href="chapter_3.5.1.html#user_data_output_3d"><span style="font-family: monospace;">user_data_output_3d</span></a>.
     164Also the vertical grid, on which the quantity is defined, has to be set
     165again:<br><br><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;CASE
     166( 'u2' )</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     167IF ( av == 0 )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     168DO&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;
     169DO&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;
     170DO&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;
     171local_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;
     172ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     173ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     174ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     175ELSE</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     176DO&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;
     177DO&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;
     178DO&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;
     179local_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;
     180ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     181ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     182ENDDO</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     183ENDIF</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     184grid = 'zu'</span><br><br>The <span style="font-family: monospace;">ELSE</span> case is
     185only needed in case that output of time-averaged data is requested.<br><br><br></li><li>In
     186case of job chains, the sum array has to be written to the (binary)
     187restart file (local filename <a href="chapter_3.4.html#BINOUT">BINOUT</a>)
     188in 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;
     189IF ( ALLOCATED( u2_av ) )&nbsp; THEN</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    65190WRITE ( 14 )&nbsp;
    66191'u2_av&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    67 ';&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>
    68 <p style="line-height: 100%;"><br>
    69 <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>
    70 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 24/03/06 (SR)</p>
     192';&nbsp; WRITE ( 14 )&nbsp; u2_av</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     193ENDIF</span><br><br>Otherwise, the calculated
     194time-average may be wrong. &nbsp;</li></ol><hr>
     195<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>
     196<p style="line-height: 100%;"><i>Last
     197change:&nbsp;</i> $Id$</p>
    71198</body></html>

  • palm/trunk/DOC/app/chapter_3.5.5.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 3.5.5</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20040802;14050943">
    8   <meta name="CHANGED" content="20041117;12180008">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;"><font size="4">3.5.5 Compiling and
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;"><font size="4">3.5.5
     10Compiling and
    1811linking user-defined code<br>
    19 </font></h3>
    20 <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
     12</font></h3><p style="line-height: 100%;">Users
     13can add their own (modified) user-interface to a PALM-run by carrying
     14out the following steps:</p><ol><li>Copy the default
     15(empty) user-interface (file<span style="font-family: Courier New,Courier,monospace;">
     16user_interface.f90</span>) to a directory of your choice, e.g.:<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp;
     17&nbsp;cd ~/palm/current_version</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">&nbsp;
     18&nbsp;mkdir -p USER_CODE/example</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">&nbsp;
     19&nbsp;cp trunk/SOURCE/user_interface.f90&nbsp;
     20USER_CODE/example/user_example.f90</span><br></li><li>Set
     21an additional path in the configuration file<span style="font-family: Courier New,Courier,monospace;">
     22.mrun.config </span>to allow <span style="font-weight: bold;">mrun
     23</span>to find and include this file:<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp;
     24&nbsp;%add_source_path&nbsp;&nbsp;
     25$base_directory/USER_CODE/$fname</span><br><br>The
     26default configuration file (<span style="font-family: Courier New,Courier,monospace;">trunk/SCRIPTS/.mrun.config.default</span>)
     27already includes this setting.</li><li>Modify the interface
     28routines according to your needs.</li><li>Start a PALM run
     29by executing<br><br><span style="font-family: Courier New,Courier,monospace;">&nbsp;
     30&nbsp;mrun -d example ...</span><br><br>The file<span style="font-family: Courier New,Courier,monospace;">
     31user_example.f90 </span>will be automatically compiled within
     32the job and will replace PALM&lsquo;s default user-interface.<br></li></ol>The
     33above method with including<span style="font-family: Courier New,Courier,monospace;"> $fname </span>in
    2134the additional source path allows to use different user-interfaces for
    2235different runs at the same time. Just store the respective
    23 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,
     36interface-files in subdirectories<span style="font-family: Courier New,Courier,monospace;">
     37USER_CODE/abcd</span>,<span style="font-family: Courier New,Courier,monospace;">
     38USER_CODE/cdef</span>, etc. and start <span style="font-weight: bold;">mrun</span> with option
     39&ldquo;<span style="font-family: Courier New,Courier,monospace;">-d
     40abcd</span>&ldquo;, &ldquo;<span style="font-family: Courier New,Courier,monospace;">-d cdef</span>&ldquo;,
     41etc.<br><br><span style="font-weight: bold;">The
     42modified user-interface file cannot be pre-compiled by using mbuild!</span><br><br>While
     43programming user-defined code,
    2444errors are frequently made. Possible ways of error
    2545tracing are described in the next chapter. <br><p style="line-height: 100%;">
    2646&nbsp; </p>
    27 <hr>
    28 <p style="line-height: 100%;"><br>
    29 <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>
    30 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 15/04/05 (SR)</p>
     47<hr><p style="line-height: 100%;"><br>
     48<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>
     49$Id$</p>
    3150</body></html>

  • palm/trunk/DOC/app/chapter_3.5.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE">
    4  
    5   <title>PALM chapter 3.5</title><meta content="StarOffice 7  (Win32)" name="GENERATOR">
    6   <meta content="Siegfried Raasch" name="AUTHOR">
    7   <meta content="20040802;10431831" name="CREATED">
    8   <meta content="20041112;14292662" name="CHANGED">
    9   <meta content="parallel LES model" name="KEYWORDS">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;">3.5 Programming of user-defined code
     3<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>
     4<!--
     5@page { size: 21cm 29.7cm }
     6-->
     7</style></head>
     8<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.5 Programming of user-defined
     9code
    1810extensions<br>
    19 </h3>
    20 <p style="line-height: 100%;">Programming user-defined code
     11</h3><p style="line-height: 100%;">Programming
     12user-defined code
    2113extensions usually requires exact knowledge of the internal structure
    2214of PALM.
    2315Appropriate explanations in <a href="chapter_2.0.html">chapter
    24 2.0</a> and the technical documentation are usually not sufficient
     162.0</a> and the technical documentation are usually not
     17sufficient
    2518and must be supplemented by the rigorous study of the source code of
    2619the model. Programming experiences with FORTRAN95 and if necessary
    2720experiences with the parallelization tool MPI are absolutely
    2821neccessary! </p>
    29 <p style="line-height: 100%;">Changes of the standard model code by the
     22<p style="line-height: 100%;">Changes of the standard
     23model code by the
    3024user
    3125should be avoided whenever possible and are reserved to the
    … …  
    3731accessible to the users (see <a href="chapter_5.1.html">chapter
    38325.1</a>).</p>
    39 <p style="line-height: 100%;">However, the user frequently may feel the
     33<p style="line-height: 100%;">However, the user frequently
     34may feel the
    4035need to make extensions of the model code for his/her own simulations.
    4136For this purpose, a set
    4237of interfaces is available, which can be used to add user-defined code
    4338to the model. This
    44 chapter describes the programming of such user-defined code extensions.</p><p style="line-height: 100%;">The integration of user-defined code
     39chapter describes the programming of such user-defined code extensions.</p><p style="line-height: 100%;">The integration of user-defined
     40code
    4541occurs in the form of subroutine calls, which are made at a set of
    4642places in the model code, by default. These subroutines have
    … …  
    4945code and they are all included in the source code file
    5046<tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt><font style="font-size: 10pt;" size="2">.</font>
    51 <font color="#000000">The</font> basic versions accomplish nearly no
     47<font color="#000000">The</font> basic versions
     48accomplish nearly no
    5249actions, thus they are pure templates, which can be extended by the
    5350user as required. Actions which are already accomplished in these
    … …  
    5552of such a basic version: </p>
    5653<p style="line-height: 100%;">&nbsp; </p>
    57 <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>
    58 <p style="line-height: 100%;">The communication (handling of variables)
     54<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
     55variables)
    5956with the model occurs via the
    6057global variables, which are defined within the individual FORTRAN -
    6158modules of PALM. The appropriate modules (they are all in the
    6259source code file <tt><font style="font-size: 10pt;" size="2">modules.f90</font></tt>)
    63 must be declared by means of <font size="2"><font face="Cumberland, monospace">USE</font></font> statements in the
     60must be declared by means of <font size="2"><font face="Cumberland, monospace">USE</font></font>
     61statements in the
    6462user-defined routines in order to be able to work with the variables
    6563contained in them. As in the example, this is already done with the
    6664module <tt><font style="font-size: 10pt;" size="2">control_parameters</font></tt>.
    6765This yields access to most of the existing parameters for steering the
    68 model. Furthermore, the module <tt><font style="font-size: 11pt;" size="2">user</font></tt> appears in the example
     66model. Furthermore, the module <tt><font style="font-size: 11pt;" size="2">user</font></tt>
     67appears in the example
    6968above. This is a
    7069user-defined module (it is located at
    … …  
    7372this module own variables can be declared as desired. It
    7473is not used outside of the user code. </p>
    75 <p style="line-height: 100%;">A very typical request of users is the
     74<p style="line-height: 100%;">A very typical request of
     75users is the
    7676calculation and output of
    7777quantities which are not part of PALM's standard output. Several
    7878routines in the basic user interface are already designed and prepared
    79 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
     79for 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
     80contents of
    8081the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>
    8182can be used as a basis for extensions. However the file should not be
    … …  
    8586declared by means of the unix command <tt><font style="font-size: 10pt;" size="2">chmod</font></tt>.
    8687</p>
    87 <p style="line-height: 100%;">The following sections describe, which
     88<p style="line-height: 100%;">The following sections
     89describe, which
    8890interfaces for user-defined code exist in the
    8991model, how user parameters can be defined for steering this code
    9092and how it is translated and linked to the model. &nbsp;</p>
    91 <hr>
    92 <p style="line-height: 100%;"><br>
    93 <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>
    94 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 15/04/05 (SR)</p>
     93<hr><p style="line-height: 100%;"><br>
     94<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>
     95$Id$</p>
    9596</body></html>

  • palm/trunk/DOC/app/chapter_3.6.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 3.6</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20040809;10583400">
    8   <meta name="CHANGED" content="20041112;15013624">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;">3.6 Interactive mode and debugging</h3>
    18 <p style="line-height: 100%;">You can use <b>mrun</b> for running PALM
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.6 Interactive mode and debugging</h3>
     10<p style="line-height: 100%;">You can use <b>mrun</b>
     11for running PALM
    1912in batch mode as well as for running it interactively. For interactive
    2013runs, you must (naturally) be logged in on the respective computer. For
    2114this computer the subroutines of the model must have
    2215been precompiled (see <a href="chapter_5.0.html">chapter
    23 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
     165.0</a>). Files containing user-defined code must be stored in
     17the directory given by the variable<span style="font-family: Courier New,Courier,monospace;">
     18%add_source_path </span>in the mrun-configuration file<span style="font-family: Courier New,Courier,monospace;">
     19.mrun.config</span>.<span style="font-family: monospace;"></span>
     20All output-files possibly
    2421created by the model and requested by the user to be kept after the run
    2522are copied to
    … …  
    2724in 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>
    2825does not cause transfer to another computer). </p>
    29 <p style="line-height: 100%;">Since model runs usually require large
     26<p style="line-height: 100%;">Since model runs usually
     27require large
    3028amounts of CPU time, interactive runs may not be feasible, since
    3129in interactive mode CPU time
    … …  
    3937description is limited to the IBM Regatta "hanni" and "berni" of the
    4038HLRN. </p>
    41 <p style="line-height: 100%;">If certain routines of the model
     39<p style="line-height: 100%;">If certain routines of the
     40model
    4241are to be debugged for errors, the complete source code of
    4342the model, including the user-defined code, must be compiled
    4443with special debug compiler options. For this purpose, at least the
    45 following three lines must be included in the <span style="font-weight: bold;">mrun </span>configuration file:<br>
    46 </p>
    47 <p style="line-height: 100%;"><span style="font-family: Courier New,Courier,monospace;">%compiler_name&nbsp;&nbsp;&nbsp;&nbsp;
     44following three lines must be included in the <span style="font-weight: bold;">mrun </span>configuration
     45file:<br>
     46</p><p style="line-height: 100%;"><span style="font-family: Courier New,Courier,monospace;">%compiler_name&nbsp;&nbsp;&nbsp;&nbsp;
    4847mpxlf95_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;
    4948ibmh parallel debug</span><br style="font-family: Courier New,Courier,monospace;">
    … …  
    6261:invalid::enable:-qsigtrap:-lesslsmp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    6362ibmh parallel debug</span><br style="font-family: monospace;">
    64 <br>
    65 </p>
    66 <p style="line-height: 100%;">(Attention: in the configuration file,
     63<br></p>
     64<p style="line-height: 100%;">(Attention: in the
     65configuration file,
    6766the compiler and linker options (<span style="font-family: Courier New,Courier,monospace;">fopts
    68 </span>and<span style="font-family: Courier New,Courier,monospace;"> lopts</span>) must be
     67</span>and<span style="font-family: Courier New,Courier,monospace;"> lopts</span>)
     68must be
    6969written in one line without any blank space before and after the
    7070colons!)<br>
    71 </p>
    72 <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
     71</p><p style="line-height: 100%;">Using the compiler
     72options "<span style="font-family: Courier New,Courier,monospace;">-g</span>"
     73and "<span style="font-family: Courier New,Courier,monospace;">-C</span>",
     74debugable code is created
    7375and check of array bounds is
    74 switched on during run time. Option "<span style="font-family: Courier New,Courier,monospace;">-qinitauto=FF</span>" initializes all
     76switched on during run time. Option "<span style="font-family: Courier New,Courier,monospace;">-qinitauto=FF</span>"
     77initializes all
    7578automatic variables (unfortunately not the global values of modules) to
    76 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
     79NaN.The "<span style="font-family: Courier New,Courier,monospace;">-qflttrap</span>"
     80and "<span style="font-family: Courier New,Courier,monospace;">-qsigtrap</span>"
     81options are needed
    7782in order to terminate the run in case of any floating point errors
    7883(otherwise the run will not terminate and errors can hardly be
    7984detected).<br>
    80 </p>
    81 <p style="line-height: 100%;">The <b>mrun </b>call for debugging
     85</p><p style="line-height: 100%;">The <b>mrun
     86</b>call for debugging
    8287needs
    83 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>
    84 <p style="line-height: 100%;">After compiling, the debugger
    85 <b>TotalView</b> is automatically called by <span style="font-weight: bold;">mrun</span>. With its assistance the user
     88an 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
     89... -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
     90list all source code files of the default PALM code. </p>
     91<p style="line-height: 100%;">After compiling, the
     92debugger
     93<b>TotalView</b> is automatically called by <span style="font-weight: bold;">mrun</span>. With its
     94assistance the user
    8695has to start
    8796the program execution manually, to set breakpoints, etc.. User manuals
    88 of <b>TotalView</b> are available <a href="http://www.hlrn.de/doc/totalview/index.html">online</a>. </p>
    89 <p style="line-height: 100%;">Program crashes caused by errors in the
     97of <b>TotalView</b> are available <a href="http://www.hlrn.de/doc/totalview/index.html">online</a>.
     98</p><p style="line-height: 100%;">Program crashes
     99caused by errors in the
    90100user-defined code should usually be found
    91101unassisted. If the termination point lies outside the user code (in the
    92102default model code), the PALM&nbsp;group can be asked for
    93 assistance, but please do not expect any quick response. It is emphasized again that error tracing and programming
     103assistance, but please do not expect any quick response. It is
     104emphasized again that error tracing and programming
    94105of
    95106user-defined code requires more or less precise knowledge of the
    … …  
    971083.5</a>). <br>
    98109&nbsp; </p>
    99 <hr>
    100 <p style="line-height: 100%;"><br>
    101 <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>
    102 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 02/03/07 (SR)</p>
     110<hr><p style="line-height: 100%;"><br>
     111<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>
     112$Id$</p>
    103113</body></html>

  • palm/trunk/DOC/app/chapter_4.0.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 4.0</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20040809;14214479">
    10   <meta name="CHANGED" content="20041112;15151993">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h2 style="line-height: 100%;"><font size="4">4.0 Steering parameters</font></h2>
    20 <p style="line-height: 100%;">Before carrying out a model run, the user
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">4.0
     11Steering parameters</font></h2>
     12<p style="line-height: 100%;">Before carrying out a model
     13run, the user
    2114has to /determine/ a data set - the model parameters - e.g. how
    2215many grid points are to be used, how large the horizontal and
    … …  
    2619should be, at which times and points plot output are supposed to be
    2720made, etc. <br>
    28 </p>
    29 <p style="line-height: 100%;">These data are assigned with the help of
    30 so-called ?“NAMELIST-driven input”? (FORTRAN - NAMELIST –
    31 input). The ?gewählten? values of the model parameters are written
     21</p><p style="line-height: 100%;">These data are
     22assigned with the help of
     23so-called ?&ldquo;NAMELIST-driven input&rdquo;? (FORTRAN -
     24NAMELIST &ndash;
     25input). The ?gew&auml;hlten? values of the model parameters are
     26written
    3227into an ASCII file with fixed format, which is expected by the model as
    3328an input
    … …  
    3934PARIN: <br>
    4035&nbsp; </p>
    41 <ul>
    42   <p style="line-height: 100%; font-family: monospace;">&amp;inipar nx
     36<ul> <p style="line-height: 100%; font-family: monospace;">&amp;inipar
     37nx
    4338= 79, ny = 79, nz = 40, <br>
    44 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dx = 50.0, dy = 50.0, dz =
     39&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     40dx = 50.0, dy = 50.0, dz =
    454150.0, <br>
    46 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; initializing_actions =
     42&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     43initializing_actions =
    4744"set_1d-model_profiles", <br>
    48 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; prandtl_layer = .TRUE.,/ </p>
    49   <p style="line-height: 100%; font-family: monospace;">&amp;d3par&nbsp;
    50 end_time = 9000.0, section_xy = 1, 10, 20,/ </p>
    51   <p style="line-height: 100%; font-family: monospace;">&amp;packagename
    52 var1 = .TRUE. / </p>
    53   <p style="line-height: 100%;"><span style="font-family: monospace;">&amp;userpar
     45&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     46prandtl_layer = .TRUE.,/ </p> <p style="line-height: 100%; font-family: monospace;">&amp;d3par&nbsp;
     47end_time = 9000.0, section_xy = 1, 10, 20,/ </p> <p style="line-height: 100%; font-family: monospace;">&amp;packagename
     48var1 = .TRUE. / </p> <p style="line-height: 100%;"><span style="font-family: monospace;">&amp;userpar
    5449abcd = 1234,0,/ </span><br>
    5550&nbsp; <br>
    5651&nbsp;</p>
    57 </ul>
    58 <p style="line-height: 100%;">The parameters are separated into four
     52</ul><p style="line-height: 100%;">The parameters
     53are separated into four
    5954different groups which all start with the so-called NAMELIST group
    6055names.
    61 These are <span style="font-family: monospace;">&amp;inipar</span>, <span
    62  style="font-family: monospace;">&amp;d3par</span> and <span
    63  style="font-family: monospace;">&amp;packagename</span> as well as <span
    64  style="font-family: monospace;">&amp;userpar</span>. In each case a
     56These are <span style="font-family: monospace;">&amp;inipar</span>,
     57<span style="font-family: monospace;">&amp;d3par</span>
     58and <span style="font-family: monospace;">&amp;packagename</span>
     59as well as <span style="font-family: monospace;">&amp;userpar</span>.
     60In each case a
    6561group is terminated with one backslash ("/"). Between the beginning of
    6662the line and the group name at least one blank has to be typed. Between
    … …  
    7167concerning the NAMELIST syntax, refer to
    7268appropriate FORTRAN manuals. <br>
    73 </p>
    74 <p style="line-height: 100%;">Parameters belonging to the group <span
    75  style="font-family: monospace;">inipar</span> are first read by PALM.
     69</p><p style="line-height: 100%;">Parameters
     70belonging to the group <span style="font-family: monospace;">inipar</span>
     71are first read by PALM.
    7672These are the initialization parameters. Second, the so-called run
    7773parameters belonging to the group <span style="font-family: monospace;">d3par</span>
    … …  
    8278group name of the respective package) as well as user-defined
    8379parameters
    84 (group <span style="font-family: monospace;">userpar</span>). The four
    85 groups must be given in this order, the last groups, <span
    86  style="font-family: monospace;">packagename</span> and <span
    87  style="font-family: monospace;">userpar</span>, may
     80(group <span style="font-family: monospace;">userpar</span>).
     81The four
     82groups must be given in this order, the last groups, <span style="font-family: monospace;">packagename</span> and
     83<span style="font-family: monospace;">userpar</span>,
     84may
    8885be omitted. If several software packages are selected
    8986(see chapter <a href="chapter_3.7.html">3.7</a>),
    90 further NAMELIST groups may be inserted before the group <span
    91  style="font-family: monospace;">userpar</span>.
    92 </p>
    93 <p style="line-height: 100%;"><b>The initialization, run</b> and
     87further NAMELIST groups may be inserted before the group <span style="font-family: monospace;">userpar</span>.
     88</p><p style="line-height: 100%;"><b>The
     89initialization, run</b> and
    9490<b>package parameters</b> differ as follows: </p>
    95 <ul>
    96   <li>
    97     <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
    98 parameters </b>are steering the basic settings of the model run. They
     91<ul> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
     92parameters </b>are steering the basic settings of the model run.
     93They
    9994define e.g. the number of the grid points, the numerical schemes to be
    10095used, initial and boundary conditions to be applied, how the
    … …  
    10499run and thus can not be changed with restart runs! If one tries to
    105100change these values within the NAMELIST input file of a restart run,
    106 then these changes are ignored (sole exception is the parameter <a
    107  style="font-family: monospace;"
    108  href="chapter_4.1.html#initializing_actions">initializing_actions</a><font
    109  style="font-size: 10pt;" size="2">, </font>which must be given the
    110 value<span style="font-family: thorndale,serif,mon;"> </span><span
    111  style="font-family: monospace; font-style: italic;">read_restart_data</span><span
    112  style="font-family: thorndale,serif,mon;"> for </span>restart runs). <br>
    113 &nbsp; </p>
    114   </li>
    115   <li>
    116     <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
    117 parameters</b> are generally steering actions to be carried out during
     101then 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
     102must be given the
     103value<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
     104runs). <br>
     105&nbsp; </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
     106parameters</b> are generally steering actions to be carried out
     107during
    118108a model run. One can select for example, at which times plot output
    119109should happen and which variables are to be written. Additionally one
    … …  
    123113usually keep their values, provided that the NAMELIST input file was
    124114not changed by the user in the meantime). <br>
    125 &nbsp; </p>
    126   </li>
    127   <li>
    128     <p style="line-height: 100%;"><b>Package parameters</b> behave like
    129     <b>run parameters</b>. Package parameters determine the behavior of
    130 the additional (not user-defined) software packages . </p>
    131   </li>
    132 </ul>
    133 <p style="line-height: 100%;">The user-defined parameters are assigned
    134 by the user within the NAMELIST group name <tt>&amp;userpar</tt> (see <a
    135  href="chapter_3.5.2.html">chapter
    136 3.5.2</a>). They steer actions programmed by the user. By default,
     115&nbsp; </p> </li> <li> <p style="line-height: 100%;"><b>Package parameters</b>
     116behave like <b>run parameters</b>. Package parameters
     117determine the behavior of
     118the additional (not user-defined) software packages . </p> </li>
     119</ul><p style="line-height: 100%;">The user-defined
     120parameters are assigned
     121by the user within the NAMELIST group name <tt>&amp;userpar</tt>
     122(see <a href="chapter_3.5.2.html">chapter
     1233.5.2</a>). They steer actions programmed by the user. By
     124default,
    137125this group has only one parameter (<a href="chapter_4.3.html#region">region</a>).
    138126If the
    139127user don't want to assign any values to the user-defined&nbsp;
    140 parameters, the group<span style="font-family: monospace;"> userpar
    141 </span>may be omitted. The group name <span
    142  style="font-family: monospace;">&amp;userpar</span>
     128parameters, the group<span style="font-family: monospace;">
     129userpar
     130</span>may be omitted. The group name <span style="font-family: monospace;">&amp;userpar</span>
    143131can be changed by the user in the user-defined code. In
    144132addition to this, further NAMELIST groups may also be declared (all
    … …  
    146134in file <span style="font-family: monospace;">user_interface.f90</span>).
    147135<a href="chapter_4.4.html">Chapter
    148 4.4</a> shows a simple but complete example of the input file PARIN.
     1364.4</a> shows a simple but complete example of the input file
     137PARIN.
    149138This example file can be used together with the configuration file
    150139(described in <a href="chapter_3.2.html">chapter
    … …  
    156145explanation are described in the lists of the following subsections. <br>
    157146&nbsp; </p>
    158 <hr>
    159 <p style="line-height: 100%;"><br>
    160 <font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font
    161  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    162  border="2" height="32" width="32"></font></a><a href="index.html"><font
    163  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    164  border="2" height="32" width="32"></font></a><a href="chapter_4.1.html"><font
    165  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    166  border="2" height="32" width="32"></font></a></font></font><br>
    167 &nbsp;
     147<hr><p style="line-height: 100%;"><br>
     148<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;
    168149<br>
    169 &nbsp;<span style="font-style: italic;">Last change:</span> 15/04/05
    170 (SR)<br>
    171 </p>
    172 </body>
    173 </html>
     150&nbsp;<span style="font-style: italic;">Last change:</span>
     151$Id$<br>
     152</p></body></html>

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

    r61 r62  
    11<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    22<html><head>
    3 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>PALM
    4 chapter 4.1</title></head>
     3<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>PALM chapter 4.1</title></head>
    54<body><h3><a name="chapter4.1"></a>4.1
    65Initialization parameters</h3>
    … …  
    874873of waves with wavelengths longer than 2-delta (see the paper by Mahrer
    875874and
    876 Pielke, quoted above). </p> </td> </tr> <tr>
     875Pielke, 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
     876default, the optimization method depends on the host on which PALM is
     877running. On machines with vector-type CPUs, single 3d-loops are used to
     878calculate each tendency term of each prognostic equation, while on all
     879other machines, all prognostic equations are solved within one big loop
     880over 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>
    877881<td style="vertical-align: top;"><a name="mixing_length_1d"></a><span style="font-weight: bold;">mixing_length_1d</span><br>
    878882</td> <td style="vertical-align: top;">C*20<br>

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

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 4.3</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20041013;13364831">
    8   <meta name="CHANGED" content="20041015;15380006">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 <body dir="ltr" lang="en-US">
    16 <h3 style="line-height: 200%;">4.3 User-defined parameters</h3>
    17 <table style="width: 100%;" border="1" cellpadding="2" cellspacing="2">
    18   <tbody>
    19     <tr valign="top">
    20       <td>
    21       <p><font size="4"><b>Parameter name</b></font></p>
    22       </td>
    23       <td>
    24       <p><font size="4"><b>Type</b></font></p>
    25       </td>
    26       <td>
    27       <p><b><font size="4">Default</font></b>&nbsp; <br>
    28       <b><font size="4">value</font></b></p>
    29       </td>
    30       <td>
    31       <p><font size="4"><b>Explanation</b></font></p>
    32       </td>
    33     </tr>
    34     <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>),
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 200%;">4.3 User-defined parameters</h3>
     10<table style="width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr valign="top">
     11<td> <p><font size="4"><b>Parameter name</b></font></p>
     12</td> <td> <p><font size="4"><b>Type</b></font></p>
     13</td> <td> <p><b><font size="4">Default</font></b>&nbsp;
     14<br> <b><font size="4">value</font></b></p>
     15</td> <td> <p><font size="4"><b>Explanation</b></font></p>
     16</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
     17which 2d cross section and/or 3d volume data are to be output.<br><br>Beside
     18the PALM standard output quantities (which can be selected via
     19parameter <a href="chapter_4.2.html#data_output">data_output</a>),
    3520the user can define (without any restriction) additional output
    3621quantities (e.g. the temperature variance, etc.). Each of these
    3722quantities has to be given a unique identifier (string) which must be
    3823different from the strings defining the standard output quantities (see
    39 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
     24list from the description of <a href="chapter_4.2.html#data_output">data_output</a>).
     25Data output can be switched on by assigning the respective strings to <span style="font-weight: bold;">data_output_user</span>.<br><br>The
     26user has to calculate/provide the respective data array(s) by
     27appropriately extending the user interface (see <a href="chapter_3.5.4.html">3.5.4</a>).<br><br>For
    4028further steering of the user defined output (output times, cross
    41 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">
    42       <td>
    43       <p><b><a name="region"></a>region</b></p>
    44       </td>
    45       <td>
    46       <p>C*40 (0:9)</p>
    47       </td>
    48       <td>
    49       <p>&nbsp;</p>
    50       </td>
    51       <td>
    52       <p>Name(s) of the subdomain(s) defined by the user.&nbsp; </p>
    53       <p>With this variable, names can be assigned to the subsections
     29section levels, time averaging, etc.), the steering parameters for <a href="chapter_4.2.html#data_output">data_output</a>
     30apply accordingly.<br><br><span style="font-weight: bold;">Example:</span><br>If
     31the user defined output quantity is the temperature variance and if the
     32user has chosen the string <span style="font-style: italic;">'pt2'</span>
     33as an identifier for this quantity, then output of horizontal cross
     34sections 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>
     35<td> <p>C*40 (0:9)</p> </td> <td> <p>&nbsp;</p>
     36</td> <td> <p>Name(s) of the subdomain(s) defined
     37by the user.&nbsp; </p> <p>With this variable, names
     38can be assigned to the subsections
    5439defined by the user (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>)
    5540which afterwards appear in the headers of the respective files (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
    5641and within the respective plots. Up to 9 subdomains are allowed (<b>region</b>
    57 (1) to <b>region</b> (9)), the total domain has the index 0 (<b>region</b>
    58 (0)).</p>
    59       </td>
    60     </tr>
    61   </tbody>
    62 </table>
    63 <p style="line-height: 200%;">&nbsp; <br>
     42(1) to <b>region</b> (9)), the total domain has the index
     430 (<b>region</b>
     44(0)).</p> </td> </tr> </tbody>
     45</table><p style="line-height: 200%;">&nbsp; <br>
    6446&nbsp; </p>
    65 <hr>
    66 <p><br>
    67 <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>
    68 <p><span style="font-style: italic;">Last change:</span> 22/03/06
    69 (SR)&nbsp;</p>
     47<hr><p><br>
     48<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>
     49$Id$&nbsp;</p>
    7050</body></html>

  • palm/trunk/DOC/app/chapter_4.4.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE">
    4  
    5   <title>PALM chapter 4.4</title><meta content="StarOffice 7  (Win32)" name="GENERATOR">
    6   <meta content="Siegfried Raasch" name="AUTHOR">
    7   <meta content="20041013;13430732" name="CREATED">
    8   <meta content="20041117;11162734" name="CHANGED">
    9   <meta content="parallel LES model" name="KEYWORDS">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;">4.4 Example of a minimum parameter set</h3>
    18 <p style="line-height: 100%;">In this chapter a brief, simple and
     3<meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 4.4</title>
     4<meta content="StarOffice 7 (Win32)" name="GENERATOR">
     5<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>
     6<!--
     7@page { size: 21cm 29.7cm }
     8-->
     9</style></head>
     10<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">4.4 Example of a minimum
     11parameter set</h3>
     12<p style="line-height: 100%;">In this chapter a brief,
     13simple and
    1914complete parameter set is described, which can be used to carry out a
    2015model run. The presented example is available via <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d">example
    … …  
    2217file</a> described in <a href="chapter_3.2.html">chapter
    23183.2)</a> for the execution of a simple model run. </p>
    24 <p style="line-height: 100%;">This run simulates a quasi-stationary,
     19<p style="line-height: 100%;">This run simulates a
     20quasi-stationary,
    2521convective, atmospheric boundary layer with&nbsp; <font color="#000000">zero
    2622mean horizontal
    27 wind.</font> For evaluation purposes, cross sections and horizontally averaged vertical
     23wind.</font> For evaluation purposes, cross sections and
     24horizontally averaged vertical
    2825profiles of typical boundary layer variables
    2926are output at the end of the run. The run shall be carried out in
    3027batch mode on the IBM Regatta "hanni" of the HLRN.</p>
    31 <p style="line-height: 100%;">The parameter file necessary to carry
     28<p style="line-height: 100%;">The parameter file necessary
     29to carry
    3230out a run must be provided to the model as an input file under the
    3331local name <a href="chapter_3.4.html#PARIN">PARIN</a>
    3432and has the following contents:</p>
    35 <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>
    36 <p style="line-height: 100%;"><br>
    37 <br>
    38 </p>
    39 <p style="line-height: 100%;">The initialization parameters (<tt><font style="font-size: 10pt;" size="2">&amp;inipar</font></tt>)
     33<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>
     34<p style="line-height: 100%;">The initialization
     35parameters (<tt><font style="font-size: 10pt;" size="2">&amp;inipar</font></tt>)
    4036are located at the beginning of the file. For analysis of a
    4137convective boundary layer of approx. 1000 m thickness the horizontal
    … …  
    4339order to resolve the convective structures a grid spacing of <b>dx</b>
    4440=
    45 <b>dy</b> = <b>dz</b> = <i>50 m</i> is enough, since the typical
     41<b>dy</b> = <b>dz</b> = <i>50 m</i>
     42is enough, since the typical
    4643diameter of convective plumes is more than 100 m. Thereby the
    4744upper array index in the two horizontal directions needs to be <b>nx</b>
    4845= <b>ny</b> = <i>39</i>. <font color="#000000">Since in
    4946each case the lower array index has the value 0, 40 grid points are
    50 used along both horizontal directions.</font> In the vertical direction
     47used along both horizontal directions.</font> In the vertical
     48direction
    5149the domain must be high enough to include the entrainment processes at
    5250the top of the boundary layer as well as the propagation of gravity
    … …  
    5654layer. This can be obtained by a vertical stretching of the grid
    5755starting
    58 from 1200 m via <b>dz_stretch_level</b> = <i>1200.0 m.</i> This saves
     56from 1200 m via <b>dz_stretch_level</b> = <i>1200.0
     57m.</i> This saves
    5958grid points and computing time. <font color="#800000">T</font><font color="#000000">he
    6059upper 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">)
    61 &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
     60&hellip; m (computed by the model)</font>.</p><p style="line-height: 100%;">Fast Fourier transformations are
     61calculated using the Temperton-algorithm, which -on the IBM Regatta- is
     62faster than the default system-specific algorithm (from IBM essl
     63library).</p><p style="line-height: 100%;">The
     64initial profiles for
    6265wind and temperature can be assigned via <b>initializing_actions</b>
    6366= <span style="font-style: italic;">'set_constant_profiles'</span>.
    6467The wind speed, constant with
    65 height, amounts to <b>ug_surface</b> = <b>vg_surface</b> = <i>0.0 m/s</i>. In order
     68height, amounts to <b>ug_surface</b> = <b>vg_surface</b>
     69= <i>0.0 m/s</i>. In order
    6670to allow for a fast onset of convection, a neutral stratified layer up
    6771to z
    6872= 800 m capped by an inversion with dtheta/dz = 1K/100 m is given:
    6973<b>pt_vertical_gradient</b> = <i>0.0, 1.0</i>,
    70 <b>pt_vertical_gradient_level</b> = <i>0.0, 800.0.</i> The surface
     74<b>pt_vertical_gradient_level</b> = <i>0.0, 800.0.</i>
     75The surface
    7176temperature, which by default amounts to 300 K, provides the fixed
    7277point for the temperature profile (see <a href="chapter_4.1.html#pt_surface">pt_surface</a>).
    7378Convection is driven by a given, near-surface sensible heat flux via <b>surface_heatflux</b>
    74 = <i>0.1 K m/s.</i> A given surface sensible heta flux requires the
     79= <i>0.1 K m/s.</i> A given surface sensible heta flux
     80requires the
    7581bottom boundary condition for potential temperature to be <b>bc_pt_b</b>
    7682=
    77 <span style="font-style: italic;">'neumann'</span> . Thus
     83<span style="font-style: italic;">'neumann'</span> .
     84Thus
    7885all initialization parameters are determined. These can not be
    7986changed during the run (also not for restart runs). </p>
    8087<p style="line-height: 100%;">Now the run parameters (<tt><font style="font-size: 10pt;" size="2">&amp;d3par</font></tt>)
    8188must be specified. To produce a quasi stationary boundary layer the
    82 simulated time should be at least one hour, i.e. <b>end_time</b> = <i>3600
    83 s.</i> To stimulate convection, the initially homogeneous (zero) wind
     89simulated time should be at least one hour, i.e. <b>end_time</b>
     90= <i>3600
     91s.</i> To stimulate convection, the initially homogeneous (zero)
     92wind
    8493field must be disturbed (<b>create_disturbances</b> = <i>.T.</i>).
    8594These perturbations should be repeated in a temporal interval of
    86 <b>dt_disturb</b> = <i>150.0 s</i> until the energy of the
    87 perturbations exceeds the value <b>disturbance_energy_limit</b> = 0.<i>01
    88 m<sup>2</sup>/s<sup>2</sup></i>. After each time step run time
     95<b>dt_disturb</b> = <i>150.0 s</i> until the
     96energy of the
     97perturbations exceeds the value <b>disturbance_energy_limit</b>
     98= 0.<i>01
     99m<sup>2</sup>/s<sup>2</sup></i>. After
     100each time step run time
    89101informations (e.g. size of the timestep, maximum velocities, etc.) are
    90102to be written to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
    91 (<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>.
     103(<b>dt_run_control</b> = <i>0.0 s</i>).</p><p style="line-height: 100%;">Instantaneous cross section data
     104of vertical velocity (<span style="font-style: italic;">w</span>)
     105and potential temperature (<span style="font-style: italic;">pt</span>)
     106are to be output for horizontal (<span style="font-style: italic;">xy</span>)
     107and vertical (<span style="font-style: italic;">xz</span>)
     108cross sections, and additionally, time averaged (<span style="font-style: italic;">av</span>) vertical cross
     109section 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
     110instantaneous (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
     111averaged data are time averaged over the last 900.0 s, where the
     112temporal interval of data entering the average is 10 s: <span style="font-weight: bold;">averaging_interval</span> =
     113<span style="font-style: italic;">900.0</span>, <span style="font-weight: bold;">dt_averaging_input</span> =
     114<span style="font-style: italic;">10.0</span>.
    92115Horizontal cross sections are output for vertical levels with grid
    93 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
     116index 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
     117more than one processor, cross section data are collected and output on
     118PE0: <span style="font-weight: bold;">data_output_2d_on_each_pe</span>
     119= <span style="font-style: italic;">.F.</span>.</p><p style="line-height: 100%;">Output
    94120of vertical profiles is to be done after each 900 s. The profiles shall
    95 be temporally averaged<font color="#000000"> over the last <font color="#000000">600 </font>seconds, </font>whereby
     121be temporally averaged<font color="#000000"> over the last
     122<font color="#000000">600 </font>seconds, </font>whereby
    96123the temporal interval of the profiles entering the average has to be
    97 10 s: <b>dt_dopr</b> = <i>900.0 s</i>, <b>averaging_interval_pr</b> =
    98 <i>600.0 s</i>, <b>dt_averaging_input_pr</b> = <i>10.0 s.</i> The temperature
     12410 s: <b>dt_dopr</b> = <i>900.0 s</i>, <b>averaging_interval_pr</b>
     125=
     126<i>600.0 s</i>, <b>dt_averaging_input_pr</b> =
     127<i>10.0 s.</i> The temperature
    99128profile including the initial temperature profile (therefore <span style="font-style: italic;">'#pt'</span>),
    100129the subgrid scale, resolved and total vertical sensible heat flux as
    101130well as the variances of the vertical velocity and the potential
    102 temperature are to be output:&nbsp; <b>data_output_pr</b> = <span style="font-style: italic;">'#pt'</span><i>, 'w"pt&rdquo;',
    103 '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
     131temperature are to be output:&nbsp; <b>data_output_pr</b>
     132= <span style="font-style: italic;">'#pt'</span><i>,
     133'w"pt&rdquo;',
     134'w*pt*', 'wpt', 'w*2', 'pt*2'</i>.</p><p style="line-height: 100%;">If the data output format for
     135graphic software <span style="font-weight: bold;">profil</span>
     136is selected (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>),
     137the temperature
    104138profile and the individual variances are to be drawn into independent
    105 coordinate systems, and in contrast to this all heat flux profiles are to
     139coordinate systems, and in contrast to this all heat flux profiles are
     140to
    106141be
    107142drawn into the same system: <b>cross_profiles</b> = <span style="font-style: italic;">'pt'</span><i>,
    108143'w"pt"w*pt*wpt', 'w*2', 'pt*2'</i>. The legend of the x
    109144axes of these systems is set to <b>cross_xtext</b>= <i>'pot.
    110 temperature in K', 'heat flux in K ms&gt;-&gt;1', 'velocity variance
     145temperature in K', 'heat flux in K ms&gt;-&gt;1', 'velocity
     146variance
    111147in m&gt;2s&gt;-&gt;2', 'temperature variance in K&gt;2'</i>.
    112148The profiles are to be drawn up to a height level of <b>z_max_do1d</b>
    … …  
    118154this run, choosing of e.g. 8 PEs is sufficient. By default, a 1d domain
    119155decomposition along x is used on the IBM-Regatta, which means that a
    120 virtual processor topology (grid) of 8*1 (x*y) is used. (<span style="font-weight: bold;">Note:</span> the user may adjust this
     156virtual processor topology (grid) of 8*1 (x*y) is used. (<span style="font-weight: bold;">Note:</span> the user may
     157adjust this
    121158default domain decomposition with the help of the parameters <a href="chapter_4.1.html#npex">npex</a>
    122159and <a href="chapter_4.1.html#npey">npey</a>).
    123 </p>
    124 <p style="line-height: 100%;">Provided that the parameters
     160</p><p style="line-height: 100%;">Provided that the
     161parameters
    125162file described above are set within the file </p>
    126 <ul>
    127   <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>
    128 </ul>
    129 <p style="line-height: 100%;">and that the conditions mentioned in the
     163<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
     164mentioned in the
    130165first sections of <a href="chapter_3.2.html">chapter
    1311663.2</a> are met, the model run can be started with the command </p>
    132167<p style="line-height: 100%;"><font face="Cumberland, monospace"><font style="font-size: 10pt;" size="2">mrun
    133 -d example -h ibmh -K parallel -X 8 -T 8 -t 1800 -q cdev -r &ldquo;d3# xy# xz# pr#&rdquo;</font></font></p>
    134 <p style="line-height: 100%;">The output files will appear in the
     168-d example -h ibmh -K parallel -X 8 -T 8 -t 1800 -q cdev -r
     169&ldquo;d3# xy# xz# pr#&rdquo;</font></font></p>
     170<p style="line-height: 100%;">The output files will appear
     171in the
    135172directories </p>
    136 <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>
    137   </font><tt><font style="font-size: 10pt;" size="2">~/palm/current_version/JOBS/example/OUTPUT
     173<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
    138174,</font></tt></blockquote>
    139 <p style="line-height: 100%;">while the job protocol will appear in
     175<p style="line-height: 100%;">while the job protocol will
     176appear in
    140177directory <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>.
    141178<br>
    142179&nbsp; </p>
    143 <hr>
    144 <p style="line-height: 100%;"><br>
    145 <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>
    146 <p style="line-height: 100%;"><i>Last change:&nbsp; 13/04/06</i> (SR)
    147 <br>
    148 &nbsp; <br>
     180<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;
     181</i>$Id$
     182<br>&nbsp; <br>
    149183&nbsp; </p>
    150184</body></html>

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

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3 <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>
     3<meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 4.5.1</title>
     4<meta content="StarOffice 7 (Win32)" name="GENERATOR">
     5<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>
    46<!--
    57@page { size: 21cm 29.7cm }
    … …  
    1618self-describing, <span style="font-weight: bold;">portable</span>
    1719objects that can be accessed through a simple interface (protable means
    18 that NetCDF data files can be read on any machine regardless of where they
     20that NetCDF data files can be read on any machine regardless of where
     21they
    1922have been created). Array values may be accessed directly, without
    2023knowing details of how the data are stored. Auxiliary information about
    … …  
    2629(see <a href="#ncdump">further below</a>).
    2730Many (public domain) graphic software has built in interfaces to read
    28 NetCDF datasets (e.g. <span style="font-weight: bold;">ferret</span> or <span style="font-weight: bold;">NCL</span>). The complete NetCDF documentation
     31NetCDF datasets (e.g. <span style="font-weight: bold;">ferret</span>
     32or <span style="font-weight: bold;">NCL</span>).
     33The complete NetCDF documentation
    2934is available from the <a href="http://www.unidata.ucar.edu/packages/netcdf/docs.html">NetCDF
    3035homepage</a>. The NetCDF tutorial for FORTRAN90 can also be found
    … …  
    4853different files. The following table gives an overview about the
    4954different kind of NetCDF output data offered by PALM. Beside the local
    50 names of the files, the table also lists the minimum parameter settings which
     55names of the files, the table also lists the minimum parameter settings
     56which
    5157are necessary to switch on the output, as well as the parameters to be
    5258used 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
    … …  
    6167<a href="chapter_4.2.html#skip_time_data_output">skip_time_data_output</a>
    6268(or <a href="chapter_4.2.html#skip_time_dopr">skip_time_dopr</a>),
    63 <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>,
     69<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>,
     70<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>,
    6471<a href="chapter_4.2.html#data_output_sp">data_output_sp</a>,
    6572<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
    … …  
    148155<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>
    149156(or <a href="chapter_4.2.html#skip_time_data_output_av">skip_time_data_output_av</a>,
    150 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
     157or <a href="chapter_4.2.html#skip_time_do3d">skip_time_do3d</a>)</td></tr><tr><td align="undefined" valign="undefined">particle
     158timeseries</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>
     159(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
    151160post-processing of a PALM NetCDF file</span><br><br>This
    152161section describes, step-by-step, the creation, storage, and
    … …  
    184193output of time-averaged data, the string <span style="font-style: italic;">'_av'</span> has to be
    185194additionally appended to the respective name string (see <a href="chapter_4.2.html#data_output">data_output</a>).<br><br><br></li><li>
    186 <p style="line-height: 100%;">Instantaneous data are output in NetCDF
     195<p style="line-height: 100%;">Instantaneous data are
     196output in NetCDF
    187197format
    188198into the
    … …  
    213223additional file suffix, should be the string <span style="font-style: italic;">'nc'</span>, because many
    214224application programs expect NetCDF files to have the file extension <span style="font-style: italic;">'.nc'</span>. (This
    215 additional suffix given in the 6th column is always put at the very end of the filename, even
    216 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
     225additional suffix given in the 6th column is always put at the very end
     226of the filename, even
     227in case of cycle numbers.)<br><br>Time averaged data are
     228output into local file&nbsp;<a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>
     229which requires an additional file connection statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp;
     230DATA_2D_XY_AV_NETCDF out:loc:tr&nbsp; xy#&nbsp;
     231~/$fname/OUTPUT/$fname&nbsp; _xy_av nc&nbsp;&nbsp; .</span><br></p></li><li>With
    217232parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
    218233= <i>.T.</i>
    … …  
    223238PLOT2D_XY_0000). These files have FORTRAN binary format. After PALM has
    224239finished, their content is merged into the final local destination file
    225 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:[[$
     240DATA_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
     241adding the following output command to the configuration file:<br><br><span style="font-family: monospace;">&nbsp; &nbsp;OC:[[$
    226242( echo $localhost | cut -c1-3 ) = imbh ]] &amp;&amp;
    227243combine_plot_fields.x &nbsp; &nbsp; .</span><br><br>Using
    … …  
    255271display of NetCDF datasets. One of the easiest ways to display the PALM
    256272data is the <a style="font-family: monospace;" href="http://ferret.wrc.noaa.gov/Ferret/">ferret</a>
    257 graphical user interface (GUI). On the IMUK-Linux-cluster, this can be called by
     273graphical user interface (GUI). On the IMUK-Linux-cluster, this can be
     274called by
    258275executing the command<br><br><span style="font-family: monospace;">&nbsp; &nbsp;ferret
    259276-gui &nbsp; &nbsp; .</span><br><br><span style="font-family: monospace;">ferret</span> is also
    … …  
    268285as soon as available.<br><br><br></li><li><a name="netcdf_example_program"></a>One
    269286of the most flexible general ways for postprocessing NetCDF data
    270 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
     287is&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
     288how to read 2d or 3d NetCDF datasets created by PALM. Compiling this
     289program requires that the
    271290NetCDF library is installed (if neccessary, please ask your system
    272 administrator). Some compilation instructions are given in the header of the
     291administrator). Some compilation instructions are given in the header
     292of the
    273293example program.<br><br><br></li><li>By
    274294default, each PALM job creates its own NetCDF files. If permanent files
    … …  
    276296higher cycle numbers will be created. However, in case of a job chain,
    277297it is possible to extend the NetCDF datasets created by the initial
    278 run&nbsp;with data from the restart run(s). As a result, data of all
     298run&nbsp;with data from the restart run(s). As a result, data of
     299all
    279300output times of the complete job chain are contained in one file and
    280301the number of data files to be handled by the user may be reduced
    281 significantly.<br>To extend a NetCDF dataset (created by a previous run
     302significantly.<br>To extend a NetCDF dataset (created by a
     303previous run
    282304of a job chain) with data from the current run requires that this
    283305dataset must be provided as an INPUT file. This may be difficult in
    284306case that PALM is running on a remote host because typically the output
    285 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;
    286 &nbsp;DATA_2D_XY_NETCDF &nbsp;out:loc:tr&nbsp;&nbsp;xy#:xyf
    287 &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
     307data files from the previous run have been already transferred by <span style="font-weight: bold;">mrun</span> to the local
     308workstation with a file connection statement like<br><br><span style="font-family: monospace;">&nbsp;
     309&nbsp;DATA_2D_XY_NETCDF
     310&nbsp;out:loc:tr&nbsp;&nbsp;xy#:xyf
     311&nbsp;~/palm/current_version/JOBS/$fname/OUTPUT
     312&nbsp;_xy&nbsp; nc</span><br><br>and thus
     313they are not available on the remote host any more. <br>A
    288314workaround for solving this problem is to create an additional copy of
    289315the output file on the remote machine by adding the file connection
    290 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>
     316statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp;
     317DATA_2D_XY_NETCDF&nbsp; out:loc&nbsp; xy#:xyf&nbsp;
     318~/palm/current_version/JOBS/$fname/OUTPUT&nbsp; _xy&nbsp; nc</span><br><br>This
     319additional copy can then be accessed from a restart job as an input
     320file using the file connection statement<br><br><span style="font-family: monospace;">&nbsp;&nbsp;
     321DATA_2D_XY_NETCDF&nbsp; in:locopt&nbsp;&nbsp;xyf&nbsp;
     322~/palm/current_version/JOBS/$fname/OUTPUT&nbsp; _xy&nbsp; nc</span><br><br>Here
     323the file attribut <span style="font-family: monospace;">locopt</span>
    291324(2nd column) guarantees that the job continues if a permanent file does
    292325not exist (e.g. in case of an initial run). Otherwise, the job would be
    293 aborted.<br>Although the dataset created by the last run of a job chain
     326aborted.<br>Although the dataset created by the last run of a job
     327chain
    294328will contain data from all selected time levels of the complete job
    295329chain, the main disadvantage of this workaround is that the datasets
    … …  
    297331and may consume large disc space. They have to be deleted "by hand" by
    298332the user on the local machine as well as on the remote
    299 machine&nbsp;because they only contain redundant data from the earlier
    300 time levels which are already contained&nbsp;in the dataset created by
    301 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;
     333machine&nbsp;because they only contain redundant data from the
     334earlier
     335time levels which are already contained&nbsp;in the dataset created
     336by
     337the last job of the job chain.<br><br><span style="font-weight: bold;">Note:</span><br>Extension
     338of PALM NetCDF datasets of 2d horizontal cross sections requires that
     339parameters <a href="chapter_4.2.html#data-output">data_output</a>
     340and <a href="chapter_4.2.html#section_xy">section_xy</a>&nbsp;
    302341for the restart runs are set identical to the initial run. In case of a
    303342value mismatch between initial and restart runs, a warning is issued in
    304343the job protocol file and the dataset will contain only data from those
    305 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
     344timelevels calculated within the restart run.<br>Similar
     345restrictions apply for all other PALM NetCDF datasets (i.e. profiles,
     346vertical cross sections, volume data, etc.).</li></ol><br>&nbsp;<br><span style="font-weight: bold;"><a name="NetCDF_example"></a>Example
     347of a PALM NetCDF dataset</span><br><br>The
    306348NetCDF dataset described here contains data of instantaneous horizontal
    307349cross 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
    … …  
    3093514.4</a>),
    310352i.e. it contains section data of the w-velocity-component and of the
    311 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;
    312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    313 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    314 &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;
    315 x = 41 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    316 &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;
    317 &nbsp;&nbsp;&nbsp; :title = "PALM&nbsp;&nbsp; 3.0&nbsp; run:
    318 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;
    319 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    320 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    321 &nbsp;<span style="font-style: italic;">! this global attribute can be used by FORTRAN programs to identify</span><br>&nbsp;
    322 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    323 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
    324 &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
     353potential temperature for vertical grid levels with index <span style="font-family: monospace;">k = 2</span> and <span style="font-family: monospace;">k = 10</span>,
     354selected 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
     355created after every 900 s (<a href="chapter_4.2.html#dt_data_output">dt_data_output</a>
     356= <span style="font-style: italic;">900.0</span>).
     357Because of <a href="chapter_4.2.html#end_time">end_time</a>
     358= <span style="font-style: italic;">3600.0</span>,
     359the file contains data of 4 time levels (t = 900, 1800, 2700, 3600 s).<br>Supposed
     360that the name of the NetCDF dataset is <span style="font-family: monospace;">example_xy.nc</span>,
     361an analysis of the file contents using the command<br><br><span style="font-family: monospace;">&nbsp; &nbsp;ncdump
     362-c example_xy.nc</span><br><br>will create the
     363following output. The original ncdump output is displayed using <span style="font-family: monospace;">fixed spacing</span>,
     364additional 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 {
     365&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     366&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;
     367&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     368&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     369&nbsp; &nbsp; &nbsp;<span style="font-style: italic;">!
     37041 gridpoints along x and y, 4 timelevels</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     371time = UNLIMITED ; // (4 currently) &nbsp; &nbsp;<span style="font-style: italic;">! unlimited means
     372that&nbsp;additional time levels can be added (e.g. by</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;
     373&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     374&nbsp; &nbsp; &nbsp; &nbsp;
     375&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     376&nbsp; &nbsp; &nbsp; &nbsp;
     377&nbsp;<span style="font-style: italic;">! restart jobs)</span><br>&nbsp;&nbsp;&nbsp;
     378zu_xy = 2 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     379&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     380&nbsp; &nbsp; &nbsp;<span style="font-style: italic;">!
     381vertical dimension (2, because two cross sections are selected);</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     382zw_xy = 2 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     383&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     384&nbsp; &nbsp; &nbsp;<span style="font-style: italic;">!
     385there 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;
     386zu1_xy = 1 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     387&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     388&nbsp; &nbsp; <span style="font-style: italic;">!
     389to 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;
     390x = 41 ; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     391&nbsp; &nbsp; &nbsp; &nbsp;
     392&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! u- or the w-component of the
     393velocity</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     394y = 41 ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">variables: &nbsp;
     395&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     396&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     397&nbsp; &nbsp; &nbsp; <span style="font-style: italic;">!
     398precision, dimensions, and units of the variables</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     399double time(time) ; &nbsp; &nbsp; &nbsp; &nbsp;
     400&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! the variables containing the
     401time levels and grid point coordinates</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     402&nbsp;&nbsp;&nbsp; time:units = "seconds" ; &nbsp;
     403&nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! have the same names as the
     404respective dimensions</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     405double zu_xy(zu_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     406&nbsp;&nbsp;&nbsp; zu_xy:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     407double zw_xy(zw_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     408&nbsp;&nbsp;&nbsp; zw_xy:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     409double zu1_xy(zu1_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     410&nbsp;&nbsp;&nbsp; zu1_xy:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     411double ind_z_xy(zu_xy) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     412&nbsp;&nbsp;&nbsp; ind_z_xy:units = "gridpoints" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     413double x(x) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     414&nbsp;&nbsp;&nbsp; x:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     415double y(y) ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     416&nbsp;&nbsp;&nbsp; y:units = "meters" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     417float w_xy(time, zw_xy, y, x) ; &nbsp; &nbsp; &nbsp;
     418&nbsp;<span style="font-style: italic;">! array of the
     419vertical velocity; it has 4 dimensions: x and y,</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     420&nbsp;&nbsp;&nbsp; w_xy:long_name = "w_xy" ; &nbsp;
     421&nbsp; &nbsp; &nbsp; &nbsp;<span style="font-style: italic;">! because it is a horizontal
     422cross section, zw_xy, which defines</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     423&nbsp;&nbsp;&nbsp; w_xy:units = "m/s" ; &nbsp;
     424&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! the vertical levels of the
     425sections, and time, for the time levels</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     426float pt_xy(time, zu_xy, y, x) ; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! array of the potential
     427temperature, which is defined on the u-grid</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     428&nbsp;&nbsp;&nbsp; pt_xy:long_name = "pt_xy" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     429&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;
     430&nbsp;&nbsp;&nbsp; :Conventions = "COARDS" ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     431&nbsp;&nbsp;&nbsp; :title = "PALM&nbsp;&nbsp;
     4323.0&nbsp; run:
     433example.00&nbsp; host: ibmh&nbsp; 13-04-06 15:12:43" ;
     434&nbsp;<span style="font-style: italic;">! PALM
     435run-identifier</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     436&nbsp;&nbsp;&nbsp; :VAR_LIST = ";w_xy;pt_xy;" ; &nbsp;
     437&nbsp; &nbsp; <span style="font-style: italic;">!
     438the list of output quantities contained in this dataset;</span></span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;
     439&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     440&nbsp; &nbsp; &nbsp; &nbsp;
     441&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     442&nbsp; &nbsp; &nbsp; &nbsp;
     443&nbsp;<span style="font-style: italic;">! this global
     444attribute can be used by FORTRAN programs to identify</span><br>&nbsp;
     445&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     446&nbsp; &nbsp; &nbsp; &nbsp;
     447&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     448&nbsp; &nbsp; &nbsp; &nbsp;
     449&nbsp;<span style="font-style: italic;">! and read the
     450quantities 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,
     4511808.98, 2711.98, 3603.59 ; <span style="font-style: italic;">!
     452values 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 ;
     453&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
     454&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span style="font-style: italic;">! heights of the two selected
     455cross 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,
     456150, 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;
     457750, 800, 850, 900, 950, 1000, 1050, 1100, 1150, 1200, 1250, 1300,
     4581350, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     4591400, 1450, 1500, 1550, 1600, 1650, 1700, 1750, 1800, 1850, 1900, 1950,
     460</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     4612000 ;</span><br style="font-family: monospace;"><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;y = 0, 50, 100,
     462150, 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;
     463750, 800, 850, 900, 950, 1000, 1050, 1100, 1150, 1200, 1250, 1300,
     4641350, </span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     4651400, 1450, 1500, 1550, 1600, 1650, 1700, 1750, 1800, 1850, 1900, 1950,
     466</span><br style="font-family: monospace;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     4672000 ;</span><br style="font-family: monospace;"><span style="font-family: monospace;">}</span><br></div><br>If
     468the option <span style="font-family: monospace;">-c</span>
     469is omitted in the <span style="font-family: monospace;">ncdump</span>
     470call, then also the complete grid point data of all quantities are
     471output 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
     472this 2d
    325473horizontal cross section dataset from a FORTRAN program (<a href="#netcdf_example_program">see above</a>).<br><hr>
    326 <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>
    327 <p style="line-height: 100%;"><span style="font-style: italic;">Last
    328 change:</span> 08/02/07 (SR)&nbsp;</p>
     474<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
     475change:</span> $Id$&nbsp;</p>
    329476</body></html>

  • palm/trunk/DOC/app/chapter_4.5.2.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta content="text/html; charset=windows-1252"
    5  http-equiv="CONTENT-TYPE">
    6   <title>PALM chapter 4.5.2</title>
    7   <meta content="StarOffice 7  (Win32)" name="GENERATOR">
    8   <meta content="Siegfried Raasch" name="AUTHOR">
    9   <meta content="20041022;12155949" name="CREATED">
    10   <meta content="20041117;11232134" name="CHANGED">
    11   <meta content="parallel LES model" name="KEYWORDS">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body lang="en-US" dir="ltr">
    19 <h4 style="line-height: 100%;"><font size="4">4.5.2 Plots of vertical
     2<html><head>
     3<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>
     4<!--
     5@page { size: 21cm 29.7cm }
     6-->
     7</style></head>
     8
     9<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.2
     10Plots of vertical
    2011profiles with profil</font></h4>
    2112<p style="line-height: 100%;">Output of vertical
    22 profile data is enabled by providing values for the run parameters <a
    23  href="chapter_4.2.html#dt_dopr"><u>dt_dopr</u></a><span
    24  style="text-decoration: none;">
     13profile 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;">
    2514and </span><a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
    26 <span style="text-decoration: none;">which specify the temporal
     15<span style="text-decoration: none;">which specify the
     16temporal
    2717interval of the output times (in s) and the quantities for which output
    2818is to be made.</span> Output times cannot be defined
    … …  
    3828possible via the
    3929initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.</p>
    40 <p style="line-height: 100%;">Output of desired profiles (temperature,
    41 velocity, etc.) is steered with the run parameter <a
    42  href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
     30<p style="line-height: 100%;">Output of desired profiles
     31(temperature,
     32velocity, etc.) is steered with the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
    4333If this parameter is not set by the user, then, independently of the
    4434value of <b>dt_dopr</b>, there will be no output! PALM
    4535creates the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
    46 which must be linked with a permanent file (see e.g. <a
    47  href="chapter_3.2.html">chapter
     36which must be linked with a permanent file (see e.g. <a href="chapter_3.2.html">chapter
    48373.2</a>) via a file connection statement in the <b>mrun</b>
    4938configuration file. At the end of the run the local file is copied
    5039to this file. Such a statement can look like this: </p>
    51 <ul>
    52   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
    53  style="font-size: 10pt;">PLOT1D_DATA   out:loc:tr   pr   ~/PLOT/$fname   _pr_in.</font></pre>
    54 </ul>
    55 <p style="line-height: 100%;">If the respective <b>mrun</b> call is
     40<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>
     41<p style="line-height: 100%;">If the respective <b>mrun</b>
     42call is
    5643like<br>
    57 </p>
    58 <ul>
    59   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
    60  style="font-size: 10pt;">mrun -d test -r “pr”
    61 </font></pre>
    62 </ul>
    63 <p style="line-height: 100%;">then the local f<span
    64  style="text-decoration: none;">ile
    65 </span><tt><span style="text-decoration: none;"><font size="2"
    66  style="font-size: 10pt;">PLOT1D_DATA</font></span></tt><span
    67  style="text-decoration: none;"><font size="2" style="font-size: 10pt;">
    68 </font>is copied to the permanent file </span><tt><span
    69  style="text-decoration: none;"><font size="2" style="font-size: 10pt;">~/PLOT/test/test_pr_in</font></span></tt><span
    70  style="text-decoration: none;">.
    71 However, the character string <font size="2" style="font-size: 10pt;">“</font></span><tt><span
    72  style="text-decoration: none;"><font size="2" style="font-size: 10pt;">pr</font></span></tt><span
    73  style="text-decoration: none;"><font size="2" style="font-size: 10pt;">”</font>
    74 activating the file connection statement </span><span
    75  style="text-decoration: none;">(see third column of the statement) </span><span
    76  style="text-decoration: none;">must be given in the <b>mrun</b>
     44</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>
     45</ul><p style="line-height: 100%;">then the local f<span style="text-decoration: none;">ile
     46</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">
     47</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;">.
     48However, 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>
     49activating the file connection statement </span><span style="text-decoration: none;">(see third column of the
     50statement) </span><span style="text-decoration: none;">must
     51be given in the <b>mrun</b>
    7752call as argument of the
    7853option -r (and/or -o)<b>.</b> If t</span>his is
    … …  
    8358<p style="line-height: 100%;">The created data file can be
    8459directly used as input file for the plot software <b>profil</b>.
    85 <b>profil</b> needs another file, the so-called parameter file, which
     60<b>profil</b> needs another file, the so-called parameter
     61file, which
    8662specifies the plot layout. This file is created by PALM under the local
    8763name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>
    8864and also needs a file connection statement, e.g.: </p>
    89 <ul>
    90   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
    91  style="font-size: 10pt;">PLOT1D_PAR out:loc:tr    pr ~/PLOT/$fname   _pr_par.</font></pre>
    92 </ul>
     65<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>
    9366<p style="line-height: 100%;">If you are in the directory
    94 <tt><font size="2" style="font-size: 10pt;">~/PLOT/test</font>,</tt>the
     67<tt><font style="font-size: 10pt;" size="2">~/PLOT/test</font>,</tt>the
    9568data can be plotted by entering </p>
    96 <ul>
    97   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
    98  style="font-size: 10pt;">profil -d test_pr_in -p test_pr_par</font></pre>
    99 </ul>
     69<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>
    10070<p style="line-height: 100%;">The default plot layout as
    10171specified in the parameter file is as follows: the profiles of the
    … …  
    11080It is very important to note that only profiles are plottet, which are
    11181assigned to
    112 a coordinate system via <b>cross_profiles</b>. If a certain
    113 variable is selected by <b>data_output_pr</b> but not assigned to a coordinate
    114 system via <b>cross_profiles</b>, then the appropriate profile data
     82a coordinate system via <b>cross_profiles</b>. If a
     83certain
     84variable is selected by <b>data_output_pr</b> but not
     85assigned to a coordinate
     86system via <b>cross_profiles</b>, then the appropriate
     87profile data
    11588are written to the file PLOT1D_DATA but they are not plotted! All
    11689panels for which data
    … …  
    11992to be plottet in a panel but output of potential temperature is not set
    12093via
    121 <b>data_output_pr</b>, then the respective panel is not drawn
     94<b>data_output_pr</b>, then the respective panel is not
     95drawn
    12296(thus no 'empty' panels appear in the plot). The
    12397parameters <a href="chapter_4.2.html#profile_columns">profile_columns</a>
    … …  
    127101starting in the top row from left to right.
    128102If the number of panels to be plotted is larger than the
    129 product <b>profile_columns</b> * <b>profile_rows</b>, then the plot
     103product <b>profile_columns</b> * <b>profile_rows</b>,
     104then the plot
    130105is continued on a second page. </p>
    131 <p style="line-height: 100%;">During a model run output of profiles to
     106<p style="line-height: 100%;">During a model run output of
     107profiles to
    132108file PLOT1D_DATA is usually carried out for several times (as
    133 determined by <span style="font-weight: bold;">dt_dopr</span>)<font
    134  size="2" style="font-size: 10pt;">.</font>
     109determined by <span style="font-weight: bold;">dt_dopr</span>)<font style="font-size: 10pt;" size="2">.</font>
    135110All of these profiles belonging to the same quantity are plotted in the
    136111same panel. The different output times are marked by different line
    … …  
    141116This legend string is taken from file PLOT1D_DATA
    142117in which a comment line is placed ahead of each profile data. </p>
    143 <p style="line-height: 100%;">For identification, each plot is
     118<p style="line-height: 100%;">For identification, each
     119plot is
    144120provided with a title, which contains the model version number, the
    145121run identifier (base file name + number of the restart run), the name
    146122of the host where the run was executed, the date and time of the
    147123beginning
    148 of the run as well as the averaging domain (by default: <span
    149  style="font-style: italic;">'total
    150 domain'</span>). If the profiles are additionally temporally averaged,
    151 each panel gets an appropriate sub-label (<span
    152  style="font-style: italic;">'time
    153 averaged over
    154  s'</span>). The axes labels of the x axes of the
     124of the run as well as the averaging domain (by default: <span style="font-style: italic;">'total
     125domain'</span>). If the profiles are additionally temporally
     126averaged,
     127each panel gets an appropriate sub-label (<span style="font-style: italic;">'time
     128averaged over&hellip; s'</span>). The axes labels of the x
     129axes of the
    155130individual panels are specified with the run parameter
    156131<a href="chapter_4.2.html#cross_xtext">cross_xtext</a>,
    … …  
    162137and <a href="chapter_4.2.html#cross_normalized_y">cross_normalized_y</a>).
    163138The respective normalization is noted in the axes label. </p>
    164 <p style="line-height: 100%;"><font color="#000000">As already
     139<p style="line-height: 100%;"><font color="#000000">As
     140already
    165141mentioned, the profiles of a quantity
    166142for all output times are plotted into the same panel. This is not
    … …  
    174150restart runs. For this
    175151purpose the configuration file must be changed such that for restart
    176 runs the profile data are appended to already existing<font
    177  color="#000000">
     152runs the profile data are appended to already existing<font color="#000000">
    178153data</font> (thus all data are output into one file). Then the
    179 configuration file has two entries for </font><tt><font color="#000000">PLOT1D_DATA</font></tt><font
    180  color="#000000">:
    181 </font></p>
    182 <ul>
    183   <pre style="line-height: 100%;"><font size="2"
    184  style="font-size: 10pt;">PLOT1D_DATA out:loc:tr  pr# ~/PLOT/$fname _pr_in</font><br><font
    185  size="2" style="font-size: 10pt;">PLOT1D_DATA out:loc:tra prf ~/PLOT/$fname _pr_in.</font></pre>
    186 </ul>
    187 <p style="line-height: 100%;">The first run of the job chain is now </p>
    188 <ul>
    189   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font size="2"
    190  style="font-size: 10pt;">mrun - D test - r “pr#
    191 </font></pre>
    192 </ul>
    193 <p style="line-height: 100%;">For the restart runs, the "#" in the <span
    194  style="font-weight: bold;">mrun</span>
     154configuration file has two entries for </font><tt><font color="#000000">PLOT1D_DATA</font></tt><font color="#000000">:
     155</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>
     156</ul><p style="line-height: 100%;">The first run of
     157the job chain is now </p>
     158<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>
     159<p style="line-height: 100%;">For the restart runs, the
     160"#" in the <span style="font-weight: bold;">mrun</span>
    195161call is automatically replaced by an "f". At the end of the job chain
    196162there will only be one data file containing the complete profile data.
    197163The file connection statement for the parameter file
    198 <font size="3">PLOT1D_PAR</font> has not changed, thus a new cycle of
     164<font size="3">PLOT1D_PAR</font> has not changed,
     165thus a new cycle of
    199166the respective permanent file is created for each run. To plot
    200167the combined data with the parameter file created by the last run of
    201168the job chain, the run parameter
    202169<a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
    203 = <i>.TRUE.</i> must be additionally set for the restart runs. If this
     170= <i>.TRUE.</i> must be additionally set for the restart
     171runs. If this
    204172is
    205173forgotten, the parameter file is useless and the data cannot
    206174be plotted. </p>
    207 <p style="line-height: 100%;">The default layout of the plots of
     175<p style="line-height: 100%;">The default layout of the
     176plots of
    208177vertical profiles can be changed by editing the
    209 parameter file. For a detailed description of the <span
    210  style="font-weight: bold;">profil</span> parameters see the
    211 <a
    212  href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>
     178parameter file. For a detailed description of the <span style="font-weight: bold;">profil</span> parameters
     179see the
     180<a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>
    213181manual (only in German). <br>
    214 </p>
    215 <hr>
    216 <p style="line-height: 100%;"><br>
    217 <font color="#000080"><font color="#000080"><a href="chapter_4.5.html"><font
    218  color="#000080"><img width="32" height="32" border="2" align="bottom"
    219  name="Grafik1" src="left.gif"></font></a><a href="index.html"><font
    220  color="#000080"><img width="32" height="32" border="2" align="bottom"
    221  name="Grafik2" src="up.gif"></font></a><a href="chapter_4.5.3.html"><font
    222  color="#000080"><img width="32" height="32" border="2" align="bottom"
    223  name="Grafik3" src="right.gif"></font></a></font></font></p>
     182</p><hr>
     183<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>
    224184<p style="line-height: 100%;"><span style="font-style: italic;">Last
    225 change:</span> 19/04/05 (SR)&nbsp;</p>
    226 </body>
    227 </html>
     185change:</span> $Id$&nbsp;</p>
     186</body></html>

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

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 4.5.3</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20041026;14291096">
    8   <meta name="CHANGED" content="20041117;11335481">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h4 style="line-height: 100%;"><font size="4">4.5.3 Plots of time
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.3
     10Plots of time
    1811series
    19 with profil</font></h4>Sorry, this feature isn't supported any more.<hr>
    20 <p style="line-height: 100%;"><br>
    21 <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>
     12with profil</font></h4>Sorry, this feature isn't supported
     13any more.<hr>
     14<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>
    2215<p style="line-height: 100%;">&nbsp;<span style="font-style: italic;">Last
    23 change:</span> 06/03/07 (SR)<br>
    24 </p>
    25 </body></html>
     16change:</span> $Id$<br>
     17</p></body></html>

  • palm/trunk/DOC/app/chapter_4.5.4.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 4.5.4</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20041027;10130843">
    10   <meta name="CHANGED" content="20041117;11420847">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h4 style="line-height: 100%;"><font size="4">4.5.4 Plots of 2d cross
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.4
     11Plots of 2d cross
    2012sections with iso2d</font></h4>
    21 <p style="line-height: 100%;">PALM permits simultaneous output xy, xz
     13<p style="line-height: 100%;">PALM permits simultaneous
     14output xy, xz
    2215and&nbsp;
    2316yz cross sections. Since the output of all three cross section plots is
    … …  
    2518<p style="line-height: 100%;">Output of xy cross
    2619sections requires to set at least two parameters: first, the temporal
    27 interval of the output time (run parameter <a
    28  href="chapter_4.2.html#dt_do2d_xy"><u>dt_do2d_xy)</u></a><span
    29  style="text-decoration: none;">
     20interval 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;">
    3021and second<span style="text-decoration: none;"></span>
    31 the names of the quantities for which cross section output is wanted</span><span
    32  style="text-decoration: none;"><span style="text-decoration: none;"> (<a
    33  href="chapter_4.2.html#data_output">data_output</a></span></span>).
     22the 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>).
    3423The string <span style="font-style: italic;">'_xy'</span>
    3524must be appended to these name strings in either case. Output times
    … …  
    3726directly but only via the output time interval, starting from the
    3827beginning of the initial 3d run (t=0, but no cross sections are
    39 written at the time t=0; exceptions see <a
    40  href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>).
     28written at the time t=0; exceptions see <a href="chapter_4.2.html#do2d_at_begin">do2d_at_begin</a>).
    4129The exact location (height level) of the cross
    42 section(s) can be defined with run parameter <a
    43  href="chapter_4.2.html#section_xy">section_xy</a>.
    44 If no values have been assigned to <b>data_output</b> and <b>section_xy</b> or
     30section(s) can be defined with run parameter <a href="chapter_4.2.html#section_xy">section_xy</a>.
     31If no values have been assigned to <b>data_output</b> and <b>section_xy</b>
     32or
    4533if the value given for <b>dt_do2d_xy </b>is
    4634larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>),
    4735<b>then there will be no output!</b><br>
    48 </p>
    49 <p style="line-height: 100%;">Data is output in binary format
     36</p><p style="line-height: 100%;">Data is output in
     37binary format
    5038into the
    5139local file <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>.
    5240This file must be linked with a permanent file by
    53 using a file connection statement in the <b>mrun</b> configuration
     41using a file connection statement in the <b>mrun</b>
     42configuration
    5443file (see e.g. <a href="chapter_3.2.html">chapter
    55443.2</a>). At the end of the run the local file is copied to this
    5645file. Such a statement can look like this: </p>
    57 <ul>
    58   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    59  style="font-size: 10pt;" size="2">PLOT2D_XY out:loc:tr  pxy  ~/PLOT/$fname  _pxy_in.</font></pre>
    60 </ul>
    61 <p style="line-height: 100%;">If the respective <b>mrun</b> call is
     46<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>
     47<p style="line-height: 100%;">If the respective <b>mrun</b>
     48call is
    6249like </p>
    63 <ul>
    64   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    65  style="font-size: 10pt;" size="2">mrun -d  test -r “pxy”
    66 </font></pre>
    67 </ul>
    68 <p style="line-height: 100%;">then the local file <tt><font
    69  style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
    70 is copied to the permanent file <tt><font style="font-size: 10pt;"
    71  size="2">~/PLOT/test/test_pxy_in</font>
    72 </tt>. However, the character string <font style="font-size: 10pt;"
    73  size="2">“</font><tt><font style="font-size: 10pt;" size="2">pxy</font></tt><font
    74  style="font-size: 10pt;" size="2">”</font>
     50<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>
     51<p style="line-height: 100%;">then the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
     52is copied to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_pxy_in</font>
     53</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>
    7554activating the file connection statement (see third column of the
    76 statement) must be given in the <b>mrun</b> call as argument of the
     55statement) must be given in the <b>mrun</b> call as
     56argument of the
    7757option -r (and/or -o)<b>.</b> <span style="text-decoration: none;">If
    78 t</span>his is forgotten by mistake, the model outputs the data to
     58t</span>his is forgotten by mistake, the model outputs the data
     59to
    7960the local file, but this is not copied to the permanent file and thus
    8061the data are not available for the user after the run has finished.</p>
    8162<p style="line-height: 100%;">The created data file can be
    8263directly used as input file for the plot software <b>iso2d</b>.
    83 However, this requires the user to assign <a
    84  href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
     64However, 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>
    8565= <i>.FALSE. </i>(see also at the end of this chapter) . <b>iso2d</b>
    8666needs another file, the so-called parameter file, which specifies the
    … …  
    9373different local files named <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
    9474and <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
    95 These must be combined to one file via a so-called <a
    96  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.2">output
    97 command</a> in the configuration file. The resulting file also needs a
     75These 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
     76command</a> in the configuration file. The resulting file also
     77needs a
    9878file connection statement: </p>
    99 <ul>
    100   <pre style="line-height: 100%;"><font style="font-size: 10pt;"
    101  size="2">OC: [[ -f PLOT2D_XY_GLOBAL]] &amp;&amp; cat PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</font><br><br><font
    102  style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL out:loc:tr  pxy  ~/PLOT/$fname  _pxy_par.</font></pre>
    103 </ul>
    104 <p style="line-height: 100%;">The output command (corn shell syntax)
     79<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>
     80<p style="line-height: 100%;">The output command (corn
     81shell syntax)
    10582tests whether the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL</font></tt>
    10683exists and if so the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY_LOCAL</font></tt>
    107 is appended via the "cat" command to the file <tt><font
    108  style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL</font></tt>
    109 which then contains all parameters needed by <b>iso2d</b>.&nbsp; This
     84is appended via the "cat" command to the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL</font></tt>
     85which then contains all parameters needed by <b>iso2d</b>.&nbsp;
     86This
    11087relatively pedantic proceeding is due to the fact that PALM
    11188can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation
    11289(when the final value of the global <span style="font-weight: bold;">iso2d</span>-parameter
    113 <a
    114  href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
     90<a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
    11591is known), while the local parameter sets are written continuously
    11692to the file PLOT2D_XY_LOCAL during the run. A consequence is, that in
    117 case of aborts of a run the file <tt><font style="font-size: 10pt;"
    118  size="2">PLOT2D_XY_GLOBAL</font></tt>
     93case of aborts of a run the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY_GLOBAL</font></tt>
    11994has possibly not been created and thus a visualization of the data -
    12095although they may be available - is
    12196not possible (in such a case, the user may create the parameter file
    12297manually). </p>
    123 <p style="line-height: 100%;">If you are in the directory <tt><font
    124  style="font-size: 10pt;" size="2">~/PLOT/test</font></tt>, the data
     98<p style="line-height: 100%;">If you are in the directory <tt><font style="font-size: 10pt;" size="2">~/PLOT/test</font></tt>,
     99the data
    125100can be plotted by entering
    126 </p>
    127 <ul>
    128   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    129  style="font-size: 10pt;" size="2">iso2d -d test  _pxy_in  -p test_pxy_par</font></pre>
    130 </ul>
    131 <p style="line-height: 100%;">By default plot layout as specified in
     101</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>
     102</ul><p style="line-height: 100%;">By default plot
     103layout as specified in
    132104the parameter file is as follows: for each cross section of each
    133105individual quantity a seperate plot is created using isolines. Isolines
    … …  
    144116beginning of the 3d simulation, t=0) and the location of the cross
    145117sections (as height level and grid point number) is noted. </p>
    146 <p style="line-height: 100%;">The layout of the plots can be
     118<p style="line-height: 100%;">The layout of the plots can
     119be
    147120varied by editing the parameter file (according to the
    148121various features of <b>iso2d</b>: color shading,
    149 vector plots, streamlines, etc.). For a detailed description of the <span
    150  style="font-weight: bold;">iso2d</span> parameters see the
    151 <a
    152  href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>
     122vector plots, streamlines, etc.). For a detailed description of the <span style="font-weight: bold;">iso2d</span> parameters see
     123the
     124<a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>
    153125manual (only in German). </p>
    154 <p style="line-height: 100%;">With parallel runs and choice of <a
    155  href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
     126<p style="line-height: 100%;">With parallel runs and
     127choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
    156128= <i>.T.</i> each PE outputs the data of its subdomain
    157 to a separate file with the name PLOT2D_XY_&lt;processor-Id&gt;,
     129to a separate file with the name
     130PLOT2D_XY_&lt;processor-Id&gt;,
    158131whereby &lt;processor-Id&gt; is a four digit number (e.g.
    159 PLOT2D_XY_0000). These files are not suitable for <span
    160  style="font-weight: bold;">iso2d</span>, but after the
     132PLOT2D_XY_0000). These files are not suitable for <span style="font-weight: bold;">iso2d</span>, but after the
    161133end
    162 of a run they can be combined to one file readable by <span
    163  style="font-weight: bold;">iso2d</span>. This is done via a
     134of a run they can be combined to one file readable by <span style="font-weight: bold;">iso2d</span>. This is done
     135via a
    164136further output command in the configuration file: </p>
    165 <ul>
    166   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    167  style="font-size: 10pt;" size="2">OC:[[$ ( echo $localhost | cut -c1-3 ) = imbh ]] &amp;&amp; combine_plot_fields.x</font></pre>
    168 </ul>
    169 <p style="line-height: 100%;">The program <tt><font
    170  style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
     137<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>
     138<p style="line-height: 100%;">The program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
    171139collects the data from the individual processor files and outputs it
    172140into the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
    … …  
    179147may remain in the configuration file, even if no appropriate files
    180148are created during the simulation). <br>
    181 <b><br>
    182 Note:</b> due to internal
    183 restrictions of <b>iso2d </b>the file <tt><font
    184  style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
     149<b><br>Note:</b> due to internal
     150restrictions of <b>iso2d </b>the file <tt><font style="font-size: 10pt;" size="2">PLOT2D_XY</font></tt>
    185151may not contain more than 99 cross sections. This restriction does not
    186152apply
    187 for the production of video clips via <b>iso2d</b>. &nbsp; </p>
    188 <hr>
    189 <p style="line-height: 100%;"><br>
    190 <font color="#000080"><font color="#000080"><a href="chapter_4.5.3.html"><font
    191  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    192  border="2" height="32" width="32"></font></a><a href="index.html"><font
    193  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    194  border="2" height="32" width="32"></font></a><a
    195  href="chapter_4.5.5.html"><font color="#000080"><img src="right.gif"
    196  name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
    197 <p style="line-height: 100%;">&nbsp;<i>Last change:&nbsp;&nbsp;</i>
    198 20/04/05 (SR)</p>
    199 </body>
    200 </html>
     153for the production of video clips via <b>iso2d</b>.
     154&nbsp; </p>
     155<hr><p style="line-height: 100%;"><br>
     156<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
     157change:&nbsp;&nbsp;</i>
     158$Id$</p>
     159</body></html>

  • palm/trunk/DOC/app/chapter_4.5.5.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 4.5.5</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20041027;13094394">
    10   <meta name="CHANGED" content="20041117;11561956">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h4 style="line-height: 100%;"><font size="4">4.5.5 Plots of 3d volume
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.5
     11Plots of 3d volume
    2012data with AVS</font></h4>
    21 <p style="line-height: 100%;">In contrast to the plot output described
     13<p style="line-height: 100%;">In contrast to the plot
     14output described
    2215so far, which can be handled more or less automatically, the creation
    2316of
    24 plots with <b>AVS</b> requires programming a so-called network by
    25 using the <span style="font-weight: bold;">AVS</span> network editor
     17plots with <b>AVS</b> requires programming a so-called
     18network by
     19using the <span style="font-weight: bold;">AVS</span>
     20network editor
    2621to design the plot
    2722layout. Details are not given here because it is assumed that the user
    2823is familiar with <b>AVS</b>. </p>
    29 <p style="line-height: 100%;"><font color="#000000">Output of 3d volume
     24<p style="line-height: 100%;"><font color="#000000">Output
     25of 3d volume
    3026data requires to set at least two parameters: </font>first, the
    3127temporal
    32 interval of the output time (run parameter <a
    33  href="chapter_4.2.html#dt_do3d"><u>dt_do3d)</u></a><span
    34  style="text-decoration: none;">
     28interval of the output time (run parameter <a href="chapter_4.2.html#dt_do3d"><u>dt_do3d)</u></a><span style="text-decoration: none;">
    3529and second<span style="text-decoration: none;"></span>
    36 the names of the quantities for which volume data output is wanted</span><span
    37  style="text-decoration: none;"><span style="text-decoration: none;"> (<a
    38  href="chapter_4.2.html#data_output">data_output</a></span></span>).<font
    39  color="#000000"> </font><font color="#000000"><span
    40  style="text-decoration: none;"></span></font><font color="#000000"><span
    41  style="text-decoration: none;"></span><span
    42  style="text-decoration: none;"></span></font><font color="#800000"> </font>The
     30the 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
    4331parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>
    4432can be used to limit data output in vertical direction up to a certain
    4533grid
    46 point. If no value has been assigned to <b>data_output</b> or
     34point. If no value has been assigned to <b>data_output</b>
     35or
    4736if the value given for <b>dt_do3d </b>is
    4837larger than the simulated time (see <a href="chapter_4.1.html#end_time">end_time</a>),
    49 <b>then there will be no output!</b> By default, data is output in
     38<b>then there will be no output!</b> By default, data is
     39output in
    504032-bit real format. Alternatively, for parallel runs, data can also be
    5141output in compressed format using 32-bit integers. This yields
    5242a loss of accuracy, but the file size is clearly reduced. The output of
    53 compressed data is described in more detail in <a
    54  href="chapter_4.5.6.html">chapter
     43compressed data is described in more detail in <a href="chapter_4.5.6.html">chapter
    55444.5.6</a>. </p>
    5645<p style="line-height: 100%;">Data, whether compressed or
    57 uncompressed, is output into the local file <a
    58  href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
     46uncompressed, is output into the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
    5947This file must be linked with a permanent file by
    60 using a file connection statement in the <b>mrun</b> configuration
     48using a file connection statement in the <b>mrun</b>
     49configuration
    6150file (see e.g. <a href="chapter_3.2.html">chapter
    62513.2</a>). At the end of the run the local file is copied to this
    … …  
    6453informations about the 3d data, which also has to be copied. The
    6554statements can look like this: </p>
    66 <ul>
    67   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    68  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>
    69 </ul>
    70 <p style="line-height: 100%;">If the respective <b>mrun</b> call is
     55<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>
     56<p style="line-height: 100%;">If the respective <b>mrun</b>
     57call is
    7158like</p>
    72 <ul>
    73   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    74  style="font-size: 10pt;" size="2">mrun -d  test -r “avs”
    75 </font></pre>
    76 </ul>
    77 <p style="line-height: 100%;">then the local file <tt><font
    78  style="font-size: 10pt;" size="2">PLOT3D_DATA</font></tt>
    79 is copied to the permanent file <tt><font style="font-size: 10pt;"
    80  size="2">~/PLOT/test/test_avs</font></tt> .
    81 However, the character string “<tt><font style="font-size: 10pt;"
    82  size="2">avs</font></tt>”
     59<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>
     60<p style="line-height: 100%;">then the local file <tt><font style="font-size: 10pt;" size="2">PLOT3D_DATA</font></tt>
     61is copied to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_avs</font></tt>
     62.
     63However, the character string &ldquo;<tt><font style="font-size: 10pt;" size="2">avs</font></tt>&rdquo;
    8364activating the file connection staement (see third column of the
    84 statement) must be given in the <b>mrun</b> call as argument of the
    85 option -r (and/or -o). <span style="text-decoration: none;">If t</span>his
     65statement) must be given in the <b>mrun</b> call as
     66argument of the
     67option -r (and/or -o). <span style="text-decoration: none;">If
     68t</span>his
    8669is forgotten by mistake, the model outputs the data to the local
    8770file, but this is not copied to the permanent file and thus the data
    8871are not available for the user after the run has finished.<br>
    89 </p>
    90 <p style="line-height: 100%;">The created data file can be used as
     72</p><p style="line-height: 100%;">The created data
     73file can be used as
    9174input file for the plot software <span style="font-weight: bold;">AVS</span>
    9275although for parallel runs another step is necessary which is
    9376described at the end of this chapter. However, after starting <b>AVS</b>
    94 (by executing the command “avs”), these data file is not read
    95 immediately<font color="#000000">. First, the user has to load a
     77(by executing the command &ldquo;avs&rdquo;), these data file
     78is not read
     79immediately<font color="#000000">. First, the user has to
     80load a
    9681suitable network (created by the
    97 network editor). This module usually contains the module</font> “read
    98 field”, which requires an input
     82network editor). This module usually contains the module</font>
     83&ldquo;read
     84field&rdquo;, which requires an input
    9985file in the so-called "fld-format", which in turn refers to the two
    10086files
    … …  
    10490local files with the names <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
    10591and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
    106 which must be combined into one file by a so-called <a
    107  href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#chapter6.2">output
     92which 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
    10893command</a>: </p>
    109 <ul>
    110   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    111  style="font-size: 10pt;" size="2">OC:[[ -f PLOT3D_FLD ]] &amp;&amp; cat PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</font></pre>
    112 </ul>
    113 <p style="line-height: 100%;">The new file PLOT3D_FLD also needs a file
     94<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>
     95<p style="line-height: 100%;">The new file PLOT3D_FLD also
     96needs a file
    11497connection statement: </p>
    115 <ul>
    116   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    117  style="font-size: 10pt;" size="2">PLOT3D_FLD out:loc:tr   avs  ~/PLOT/$fname  _fld fld</font></pre>
    118 </ul>
     98<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>
    11999<p style="line-height: 100%;">The above <b>mrun </b>call
    120100then copies the local file <tt><font style="font-size: 10pt;" size="2">PLOT3D_FLD</font></tt>
    121101to the permanent file <tt><font style="font-size: 10pt;" size="2">~/PLOT/test/test_fld.fld</font>
    122 </tt><font face="Thorndale, serif">.</font> In this case the entry
    123 “<tt><font style="font-size: 10pt;" size="2">fld</font></tt>”
     102</tt><font face="Thorndale, serif">.</font> In
     103this case the entry
     104&ldquo;<tt><font style="font-size: 10pt;" size="2">fld</font></tt>&rdquo;
    124105in the sixth column of the file connection statement is
    125106very important because this ensures that the permanent file name gets
    126 the suffix ” <tt><font style="font-size: 10pt;" size="2">.fld</font></tt>
     107the suffix &rdquo; <tt><font style="font-size: 10pt;" size="2">.fld</font></tt>
    127108".&nbsp; The <span style="font-weight: bold;">AVS</span>
    128 module “read field” expects all files to have this suffix. (Note: With
     109module &ldquo;read field&rdquo; expects all files to have this
     110suffix. (Note: With
    129111this file
    130 connection statements files with cycle numbers receive the names ”<tt><font
    131  style="font-size: 10pt;" size="2">
    132 
    133 _fld.&lt;number of cycle&gt;.fld</font></tt><font
    134  style="font-size: 10pt;" size="2">
     112connection statements files with cycle numbers receive the names
     113&rdquo;<tt><font style="font-size: 10pt;" size="2">&hellip;
     114_fld.&lt;number of cycle&gt;.fld</font></tt><font style="font-size: 10pt;" size="2">
    135115</font>".) </p>
    136 <p style="line-height: 100%;"><font color="#000000">The file
     116<p style="line-height: 100%;"><font color="#000000">The
     117file
    137118connection statements must guarantee that all three permanent files
    138119(volume
    … …  
    140121the volume data file and coordinate file may not be changed after
    141122creation of the files, since they are registered in the fld file and
    142 otherwise cannot be found </font>by the "read field" module. Sometimes
     123otherwise cannot be found </font>by the "read field" module.
     124Sometimes
    143125it may happen<font color="#000000">
    144126that incorrect file names are registered into the fld file. In such
    145127cases the user must edit and correct the fld file accordingly. </font>
    146 </p>
    147 <p style="line-height: 100%;"><font color="#800000"><font
    148  color="#000000">After
     128</p><p style="line-height: 100%;"><font color="#800000"><font color="#000000">After
    149129<font color="#000000">the <span style="font-weight: bold;">AVS</span>
    150 module <font color="#000000">“read
    151 fields” </font>has </font>read in the data, the content of this
     130module <font color="#000000">&ldquo;read
     131fields&rdquo; </font>has </font>read in the data, the
     132content of this
    152133file is listed in a separate <span style="font-weight: bold;">AVS</span>
    153134window where each quantity is represented by its name and output time.</font>
    154 </font></p>
    155 <p style="line-height: 100%;">With parallel runs each PE outputs the
     135</font></p><p style="line-height: 100%;">With
     136parallel runs each PE outputs the
    156137volume data of its subdomain to a separate file with the name
    157138PLOT3D_DATA_&lt;processor-Id&gt;,
    … …  
    159140PLOT3D_DATA_0000). These files are not suitable for&nbsp; <b>AVS</b>,
    160141but after the end of a run they can be combined to one file readable by
    161 <span style="font-weight: bold;">AVS</span>. This is done via a
     142<span style="font-weight: bold;">AVS</span>. This is
     143done via a
    162144further output command in the configuration file: </p>
    163 <ul>
    164   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    165  style="font-size: 10pt;" size="2">OC:[[$ ( echo $localhost | cut -c1-3 ) = ibmh ]] &amp;&amp; combine_plot_fields.x</font></pre>
    166 </ul>
    167 <p style="line-height: 100%;">The program <tt><font
    168  style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
     145<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>
     146<p style="line-height: 100%;">The program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
    169147collects the data from the individual processor files and outputs it
    170148into the local file <tt><font style="font-size: 10pt;" size="2">PLOT2D_DATA</font></tt>
    … …  
    176154protocol, even if no files were found (i.e. the output command
    177155may remain in the configuration file, even if no appropriate files
    178 are created during the simulation). <span
    179  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span
    180  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span
    181  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span
    182  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span
    183  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><tt><span
    184  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span></tt><span
    185  style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"></span><br>
    186 </p>
    187 <p style="line-height: 100%;">&nbsp;<b>Note:</b> <span
    188  style="font-weight: bold;">AVS</span> can process 64 arrays at maximum
     156are 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>
     157</p><p style="line-height: 100%;">&nbsp;<b>Note:</b>
     158<span style="font-weight: bold;">AVS</span> can
     159process 64 arrays at maximum
    189160in one file (with vector representations even
    190161only 25). If more arrays should be output, surplus arrays must be
    191162removed from the fld file (see <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>)
    192163manually. &nbsp; </p>
    193 <hr>
    194 <p style="line-height: 100%;"><br>
    195 <font color="#000080"><font color="#000080"><a href="chapter_4.5.4.html"><font
    196  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    197  border="2" height="32" width="32"></font></a><a href="index.html"><font
    198  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    199  border="2" height="32" width="32"></font></a><a
    200  href="chapter_4.5.6.html"><font color="#000080"><img src="right.gif"
    201  name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
    202 <p style="line-height: 100%;">&nbsp;<i>Last change:&nbsp;</i> 20/04/05
    203 (SR)</p>
    204 </body>
    205 </html>
     164<hr><p style="line-height: 100%;"><br>
     165<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
     166change:&nbsp;</i> $Id$</p>
     167</body></html>

  • palm/trunk/DOC/app/chapter_4.5.6.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 4.5.6</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20041029;13171001">
    10   <meta name="CHANGED" content="20041117;12013945">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h4 style="line-height: 100%;"><font size="4">4.5.6 Plots of compressed
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.6
     11Plots of compressed
    20123d volume data with AVS</font></h4>
    21 <p style="line-height: 100%;">Files containing 3d volume data usually
     13<p style="line-height: 100%;">Files containing 3d volume
     14data usually
    2215need large amounts of disc space. For parallel runs, the disc space
    2316requirement can
    … …  
    2619compression is permitted only for parallel runs on Cray-T3E). Data
    2720compression
    28 can switched on by setting the initialization parameter <a
    29  href="chapter_4.2.html#do3d_compress">do3d_compress</a>
    30 = <i>.TRUE.</i> and by assigning the desired accuracy (number of
     21can switched on by setting the initialization parameter <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>
     22= <i>.TRUE.</i> and by assigning the desired accuracy
     23(number of
    3124significant digits) via <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
    3225A separate accuracy must be assigned for each individual quantity.
    … …  
    3831output. To plot these compressed data the following output command must
    3932be inserted into the
    40 <span style="font-weight: bold;">mrun</span> configuration file<b> </b>(in
     33<span style="font-weight: bold;">mrun</span>
     34configuration file<b> </b>(in
    4135addition to the steps described
    4236in <a href="chapter_4.5.5.html">chapter
    43374.5.5</a>): </p>
    44 <ul>
    45   <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    46  style="font-size: 10pt;" size="2">OC:[[ -f PLOT3D_COMPRESSED ]] &amp;&amp; tar cf PLOT3D_DATA PLOT3D_DATA_*</font></pre>
    47 </ul>
    48 <p style="line-height: 100%;">If a file named <tt><font
    49  style="font-size: 10pt;" size="2">PLOT3D_COMPRESSED</font></tt>
    50 exists in the local working directory, <tt><font
    51  face="Thorndale, serif">t</font></tt><font face="Thorndale, serif">he
    52 files produ</font>ced by the individual processors are packed into one
     38<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>
     39<p style="line-height: 100%;">If a file named <tt><font style="font-size: 10pt;" size="2">PLOT3D_COMPRESSED</font></tt>
     40exists in the local working directory, <tt><font face="Thorndale, serif">t</font></tt><font face="Thorndale, serif">he
     41files produ</font>ced by the individual processors are packed
     42into one
    5343file (<tt><font style="font-size: 10pt;" size="2">PLOT3D_DATA</font></tt>)
    5444using the "tar"
    5545command. The flag file
    56 <tt><font size="2">PLOT3D_COMPRESSED </font></tt>is created by PALM
     46<tt><font size="2">PLOT3D_COMPRESSED </font></tt>is
     47created by PALM
    5748whenever data in compressed form is to be output. For
    5849uncompressed output, the individual files have to be joined via the
    5950program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font>
    60 </tt>. In this case, an additional output command is also necessary
     51</tt>. In this case, an additional output command is also
     52necessary
    6153(see chapter 4.5.5). For compressed output, this output command may
    6254remain
    63 unchanged in the configuration file, since <tt><font
    64  style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
     55unchanged in the configuration file, since <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
    6556recognizes the
    66 ex<font face="Thorndale, serif">isten</font>ce of <tt><font
    67  style="font-size: 10pt;" size="2">PLOT3D_COMPRESSED</font></tt>
     57ex<font face="Thorndale, serif">isten</font>ce of <tt><font style="font-size: 10pt;" size="2">PLOT3D_COMPRESSED</font></tt>
    6858and carries out no actions in such cases. </p>
    69 <p style="line-height: 100%;">The file connection statements for the
     59<p style="line-height: 100%;">The file connection
     60statements for the
    7061local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>
    7162and all further necessary statements to create plots of 3d volume
    7263data can be found in <a href="chapter_4.5.5.html">chapter
    73644.5.5</a>. </p>
    74 <p style="line-height: 100%;">After been transferred to the local
     65<p style="line-height: 100%;">After been transferred to
     66the local
    7567computer
    7668of the user, the tar file with the compressed data cannot be read
    77 with the usual <span style="font-weight: bold;">AVS</span> module
    78 “read field”. Alternatively,
    79 the module “read_compressed_field” particularly developed
     69with the usual <span style="font-weight: bold;">AVS</span>
     70module
     71&ldquo;read field&rdquo;. Alternatively,
     72the module &ldquo;read_compressed_field&rdquo; particularly
     73developed
    8074for this purpose must be used. This module is located in a module
    8175library under: </p>
    82 <pre style="margin-bottom: 0.5cm; line-height: 100%;"><font
    83  style="font-size: 10pt;" size="2">http://www.muk.uni-hannover.de/~raasch/PALM_group/AVS/Libraries/palm</font></pre>
    84 <p style="line-height: 100%;">This module must be loaded within AVS
     76<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
     77AVS
    8578(network editor - &gt; module
    8679tools - &gt; read module library) and then it can be used like all
    87 other modules. <a
    88  href="http://www.muk.uni-hannover.de/institut/people/raasch/PALM_group/AVS/Doc/read_compressed_field.html">Further
     80other modules. <a href="http://www.muk.uni-hannover.de/institut/people/raasch/PALM_group/AVS/Doc/read_compressed_field.html">Further
    8981information</a> about using this module is available (e.g. for
    90 accelerated treatment of compressed data with <span
    91  style="font-weight: bold;">AVS</span> the module
    92 <a
    93  href="http://www.muk.uni-hannover.de/institut/people/raasch/PALM_group/AVS/Doc/write_compressed_field.html">write_compressed_field</a>
     82accelerated treatment of compressed data with <span style="font-weight: bold;">AVS</span> the module
     83<a href="http://www.muk.uni-hannover.de/institut/people/raasch/PALM_group/AVS/Doc/write_compressed_field.html">write_compressed_field</a>
    9484is available). <br>
    9585&nbsp; <br>
    9686&nbsp; </p>
    97 <hr>
    98 <p style="line-height: 100%;"><br>
    99 <font color="#000080"><font color="#000080"><a href="chapter_4.5.5.html"><font
    100  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    101  border="2" height="32" width="32"></font></a><a href="index.html"><font
    102  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    103  border="2" height="32" width="32"></font></a><a
    104  href="chapter_4.5.7.html"><font color="#000080"><img src="right.gif"
    105  name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
    106 <p style="line-height: 100%;">&nbsp;<i>Last change:&nbsp;</i> 20/04/05
    107 (SR)</p>
    108 </body>
    109 </html>
     87<hr><p style="line-height: 100%;"><br>
     88<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
     89change:&nbsp;</i> $Id$</p>
     90</body></html>

  • palm/trunk/DOC/app/chapter_4.5.7.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 4.5.7</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20041029;14344622">
    10   <meta name="CHANGED" content="20050119;9531085">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h4 style="line-height: 100%;"><font size="4">4.5.7 Plots of
     2<html><head>
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9
     10<body style="direction: ltr;" lang="en-US"><h4 style="line-height: 100%;"><font size="4">4.5.7
     11Plots of
    2012isosurfaces, 2d cross sections and particles with dvrp</font></h4>
    2113<p style="line-height: 100%;">The <span style="font-weight: bold;">dvrp</span>
    … …  
    2719possible. <br>
    2820In contrast to the other kinds of visualization output realized
    29 in PALM (<b>profil</b>, <b>iso2d</b> and <b>AVS</b>), where the data
     21in PALM (<b>profil</b>, <b>iso2d</b> and <b>AVS</b>),
     22where the data
    3023is output in a format suitable for the plot software, the creation of
    31 plots via <span style="font-weight: bold;">dvrp</span> software is
     24plots via <span style="font-weight: bold;">dvrp</span>
     25software is
    3226integrated in PALM, i.e. respective routines are directly called within
    3327the PALM code. The
    34 <span style="font-weight: bold;">dvrp</span> routines then output the
     28<span style="font-weight: bold;">dvrp</span>
     29routines then output the
    3530graphic data
    3631(so-called plot-primitives, e.g. polygones of isosurfaces) in a special
    … …  
    4641computing speed of commercial graphic software in case of such
    4742large numbers of grid points). </p>
    48 <p style="line-height: 100%;">The coupling of <span
    49  style="font-weight: bold;">dvrp</span> software and PALM
    50 as well as the visualization of the model results via <span
    51  style="font-weight: bold;">dvrp</span> has been
     43<p style="line-height: 100%;">The coupling of <span style="font-weight: bold;">dvrp</span> software and
     44PALM
     45as well as the visualization of the model results via <span style="font-weight: bold;">dvrp</span> has been
    5246the main focus of the BMBF project "Application of
    5347tele-immersion in long-distance networks" (2001-2002),
    … …  
    5549continued by RRZN in the new DFG-funded project "EVITA - Untersuchung
    5650effizienter
    57 <br>
    58 Methoden zur visuellen und haptischen tele-immersiven Exploration
    59 <br>
    60 komplexer Volumen- und Strömungsdaten aus parallelisierten,
    61 <br>
    62 dynamischen 3D-Simulationen" (2005-2007). </p>
    63 <p style="line-height: 100%;">The calls of the <span
    64  style="font-weight: bold;">dvrp</span> routines are contained within a
     51<br>Methoden zur visuellen und haptischen tele-immersiven
     52Exploration
     53<br>komplexer Volumen- und Str&ouml;mungsdaten aus
     54parallelisierten,
     55<br>dynamischen 3D-Simulationen" (2005-2007). </p>
     56<p style="line-height: 100%;">The calls of the <span style="font-weight: bold;">dvrp</span> routines are
     57contained within a
    6558PALM software package (see chapter <a href="chapter_3.7.html">3.7</a>).
    6659To use this package, the additional option <tt><font size="2">-p
    67 “dvrp_graphics”</font></tt>
    68 has to be given in the <b>mrun</b> call. This automatically links the
     60&ldquo;dvrp_graphics&rdquo;</font></tt>
     61has to be given in the <b>mrun</b> call. This
     62automatically links the
    6963required libraries.
    7064Steering of the plot output is done via the package
    … …  
    7367graphic
    7468data are not output to local files but directly to a special remote
    75 computer which is defined via the package parameter <a
    76  href="chapter_4.2.html#dvrp_host">dvrp_host</a>.
     69computer which is defined via the package parameter <a href="chapter_4.2.html#dvrp_host">dvrp_host</a>.
    7770The
    7871default values of the dvrp parameters are cause the output to be
    7972directed to a so-called streaming server at the
    8073RRZN. Apart from graphic data an additional html file is created, which
    81 can be used by an internet browser to view the data (a special <span
    82  style="font-weight: bold;">dvrp</span> plugin is needed). </p>
    83 <p style="line-height: 100%;">Since July 2001, the basic functionality
    84 of the <span style="font-weight: bold;">dvrp</span> software is
     74can be used by an internet browser to view the data (a special <span style="font-weight: bold;">dvrp</span> plugin is
     75needed). </p>
     76<p style="line-height: 100%;">Since July 2001, the basic
     77functionality
     78of the <span style="font-weight: bold;">dvrp</span>
     79software is
    8580installed in PALM and steerable via the
    8681package parameters. However, some code modifications may still need to
    … …  
    8883the subroutine <tt><font style="font-size: 10pt;" size="2">plot_dvrp</font></tt>
    8984in order to define suitable color tables).
    90 <br>
    91 For further detailed information please ask Siegfried Raasch. </p>
    92 <hr>
    93 <p style="line-height: 100%;"><br>
    94 <font color="#000080"><font color="#000080"><a href="chapter_4.5.6.html"><font
    95  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    96  border="2" height="32" width="32"></font></a><a href="index.html"><font
    97  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    98  border="2" height="32" width="32"></font></a><a href="chapter_4.6.html"><font
    99  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    100  border="2" height="32" width="32"></font></a></font></font></p>
    101 <p style="line-height: 100%;">&nbsp;<i>Last change:&nbsp;</i> 20/04/05
    102 (SR)</p>
    103 </body>
    104 </html>
     85<br>For further detailed information please ask Siegfried Raasch.
     86</p>
     87<hr><p style="line-height: 100%;"><br>
     88<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
     89change:&nbsp;</i> $Id$</p>
     90</body></html>

  • palm/trunk/DOC/app/chapter_4.5.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 4.5</title>
    4  
    5   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20041015;12234229">
    8   <meta name="CHANGED" content="20041022;13412723">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 
    16 <body dir="ltr" lang="en-US">
    17 <h3 style="line-height: 100%;">4.5 Data analysis and visualization<br>
    18 </h3>
    19 <p style="line-height: 100%;">PALM is able to output
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">4.5 Data analysis and
     10visualization<br>
     11</h3><p style="line-height: 100%;">PALM is able to
     12output
    2013data of different quantities as time series,
    2114vertical profiles (usually horizontally averaged), two-dimensional
    2215cross sections or <font color="#000000">3d-volume data.</font>
    23 Depending on the kind of output (time series, profiles, etc.) and the output format (ASCII&nbsp; or binary) data are written
     16Depending on the kind of output (time series, profiles, etc.) and the
     17output format (ASCII&nbsp; or binary) data are written
    2418to different files (file descriptions can be found in
    2519<a href="../app/chapter_3.4.html">chapter
    … …  
    3125library is available. More detailed informations about the
    3226PALM-NetCDF-output is given in the next subchapter (<a href="../app/chapter_4.5.1.html">4.5.1</a>).</p>
    33 
    34 <p style="line-height: 100%;">Due to historical reasons, PALM can also
     27<p style="line-height: 100%;">Due to historical reasons,
     28PALM can also
    3529output data in other formats suitable for some special graphic
    3630software. The exact format of these files corresponds to the
    3731requirements of the respective software. Still available at IMUK are <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>
    3832(time series, profiles), <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>
    39 (2d cross sections) and <b>AVS</b> (e.g. iso-surfaces of 3d volume
     33(2d cross sections) and <b>AVS</b> (e.g. iso-surfaces of
     343d volume
    4035data). The special files created by PALM can be directly used
    41 as input files for these plot programs. Beyond that, <b>profil</b> and
     36as input files for these plot programs. Beyond that, <b>profil</b>
     37and
    4238<b>iso2d</b> need additional information
    4339about the plot layout (e.g. titles, axes labels, arrangement of the
    4440coordinate systems, etc.) provided by so-called parameter files<font color="#800000">.
    45 </font><font color="#000000">Thes</font>e files are also created by
     41</font><font color="#000000">Thes</font>e
     42files are also created by
    4643the PALM, providing a default layout (e.g. plots produced by <b>iso2d</b>
    4744show. only isolines and no color shading). Within certain
    … …  
    5451so-called FLD format, which describes the structure of the two binary
    5552files. Coordinate and FLD file are also created by the PALM. However,
    56 with <b>AVS</b> (differently than with <b>profile</b> or <b>iso2d</b>)
     53with <b>AVS</b> (differently than with <b>profile</b>
     54or <b>iso2d</b>)
    5755the plot layout must always be additionally designed by the user
    5856with the help of the AVS network editor. &nbsp;</p>
    59 
    60 
    61 <p style="line-height: 100%;">In the following subchapters, steering
     57<p style="line-height: 100%;">In the following
     58subchapters, steering
    6259of the different data output and how to create plots of the data is
    6360described by some examples. Not all details of steering
    6461are mentioned. If necessary, these can be found within the
    6562description of the respective parameters.<br>
    66 </p>
    67 
    68 &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>
    69 <p style="line-height: 100%;"><br>
    70 <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>
     63</p>&nbsp;For most purposes it should be sufficient to read <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a>
     64which explains the PALM-NetCDF-output.<hr>
     65<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>
    7166<p style="line-height: 100%;">&nbsp;<span style="font-style: italic;">Last
    72 change:</span> 05/03/05 (SR)<br>
    73 </p>
    74 </body></html>
     67change:</span> $Id$<br>
     68</p></body></html>

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

    r61 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
    4 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>
     3<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>
    54<!--
    65@page { size: 21cm 29.7cm }
    … …  
    701700<p><i>0.0</i></p> </td> <td style="vertical-align: middle;" width="57%"> <p>Filter
    702701factor for the so-called Long-filter.</p> </td> </tr>
    703 <tr> <td style="vertical-align: middle;" width="15%">
     702<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%">
    704703<p><a href="chapter_4.2.html#maximum_number_of_particles"><b>maximum_number_</b></a>
    705704<br> <a href="chapter_4.2.html#maximum_number_of_particles"><b>of_particles</b></a></p>

  • palm/trunk/DOC/app/chapter_5.0.html

    r61 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
    4  
    5   <title>PALM chapter 5.0</title><meta name="GENERATOR" content="StarOffice 7  (Win32)">
    6   <meta name="AUTHOR" content="Siegfried Raasch">
    7   <meta name="CREATED" content="20041103;12380720">
    8   <meta name="CHANGED" content="20041123;15532356">
    9   <meta name="KEYWORDS" content="parallel LES model">
    10   <style>
    11         <!--
    12                 @page { size: 21cm 29.7cm }
    13         -->
    14         </style></head>
    15 <body dir="ltr" lang="en-US">
    16 <h2 style="line-height: 100%;"><font size="4">5.0 Installation of the
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 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>
     5<!--
     6@page { size: 21cm 29.7cm }
     7-->
     8</style></head>
     9<body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">5.0
     10Installation of the
    1711model</font></h2>
    1812<font color="#000000">This chapter
    19 describes the installation of PALM on a Linux workstation (local host) and a suitable remote computer, on which the
     13describes the installation of PALM on a Linux workstation (local host)
     14and a suitable remote computer, on which the
    2015model runs are to be carried out. The local host is used to
    21 start batch jobs with <b>mrun</b> and to analyze the results
    22 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>).
    23 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
     16start batch jobs with <b>mrun</b> and to analyze the
     17results
     18which are produced by the model on the remote host and send back to the
     19local host. Alternatively, <span style="font-weight: bold;">mrun</span>
     20can also be used to start PALM on the local host in interactive mode or
     21as 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
     22installation and operation of PALM requires at mimimum (on both, the
     23local and the remote host, unless stated otherwise):</font></p><ol><li><font color="#000000">The AT&amp;T Korn-shell (ksh) must be
     24available 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">.
     25Most of the current Linux distributions are using the public domain
     26Korn-shell (pdksh). The PALM scripts <span style="font-weight: bold;">mrun</span> and <span style="font-weight: bold;">mbuild</span> do not work
     27with the pdksh! Please replace it by the AT&amp;T ksh. If the
     28AT&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">,
     29please modify the first lines in <span style="font-weight: bold;">mrun</span>
     30and <span style="font-weight: bold;">mbuild</span>,
     31respectively.</font></li><li><font color="#000000">The
     32NetCDF-library with version number not earlier than 3.6.0-p1 (for
     33NetCDF, 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
     34least 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
     35system <span style="font-weight: bold;">subversion</span>
     36(see <a href="http://subversion.tigris.org/">subversion.tigris.org</a>).
     37This is already included in many Linux distributions (e.g. SuSe). <span style="font-weight: bold;">subversion requires port 3690 to
     38be open for tcp/udp.</span> <span style="font-weight: bold;">If
     39there are firewall restrictions concerning this port, the PALM code
     40cannot be accessed.</span> The
    2441user needs a permit to access the PALM repository. For getting a permit
    2542please contact the PALM group (<a href="mailto:raasch@muk.uni-hannover.de">raasch@muk.uni-hannover.de</a>)
    2643and define a username under which you like to access the repository.
    2744You will then receive a password which allows the access under this
    28 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
     45name.</font></li><li><font color="#000000">A
     46job queueing system must be available on the remote host. Currently, <span style="font-weight: bold;">mrun</span> can handle
     47LoadLeveler (IBM-AIX) and NQS/PBS (Linux-Clusters, NEC-SX).</font></li><li><font color="#000000">ssh/scp-connections to and from the remote
     48host 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
     49to be used on a limited number of selected machines. These are
     50IBM-Regatta at computing center HLRN in Hannover (<span style="font-style: italic;">ibmh</span>), Berlin (<span style="font-style: italic;">ibmb</span>), at KISTI,
     51Korea (<span style="font-style: italic;">ibms</span>),
     52at Yonsei University, Seoul (<span style="font-style: italic;">ibms</span>),
     53on NEC-SX6/8 systems at DKRZ, Hamburg (<span style="font-style: italic;">nech</span>) and RIAM,
     54Kyushu University, Fukuoka (<span style="font-style: italic;">neck</span>),
     55as well as on the Linux cluster of IMUK (<span style="font-style: italic;">lcmuk</span>) and Tokyo
     56Institute of Technology (<span style="font-style: italic;">lctit</span>).
     57The strings given in brackets are the systems names under which <span style="font-weight: bold;">mrun</span> indentifies the
     58different hosts. mrun should also work on other systems, but this
     59requires 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
     60versions will allow to configure the scripts for different kinds of
     61systems by just using a configuration file.</font><p style="line-height: 100%;"><font color="#000000">The
     62examples given in this chapter refer to an
    2963installation of PALM on an IMUK Linux workstation and the IBM-Regatta
    3064system of
    31 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%;">
    32 </p>
    33 <p style="line-height: 100%;">The installation process requires a valid
     65the HLRN used as&nbsp;remote host. They are just called local and
     66remote host from now on. </font></p><p style="line-height: 100%;">
     67</p><p style="line-height: 100%;">The installation
     68process requires a valid
    3469account on the local and on the remote host as well.<br>
    3570&nbsp; </p>
    36 <ul>
    37   All hosts (local as well as remote) are
     71<ul> All hosts (local as well as remote) are
    3872accessed via the secure shell (ssh). The user must establish
    3973passwordless login using the private/public-key mechanism (see e.g. the
    40   <a href="http://www.hlrn.de/doc/ssh/index.html">HLRN documentation</a>).
    41   <b>To ensure proper function of mrun, passwordless login must be
     74<a href="http://www.hlrn.de/doc/ssh/index.html">HLRN
     75documentation</a>). <b>To ensure proper function of mrun,
     76passwordless login must be
    4277established in both directions, from the local to the remote host as
    43 well as from the remote to the local host!</b> Test this by carrying
    44 out e.g. on the local host:
    45   <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
    46 </span><span style="font-family: Courier New,Courier,monospace;">ssh&nbsp; &lt;username on remote host&gt;@&lt;remote IP-address&gt;</span><br>
    47   </p>
    48   <p style="line-height: 100%;">and on the remote host:<br>
    49   </p>
    50   <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
    51 </span><span style="font-family: Courier New,Courier,monospace;">ssh&nbsp; &lt;username on local host&gt;@&lt;local IP-adddress&gt;</span><br>
    52   </p>
    53   In both cases you should&nbsp;not be
    54 prompted for a password. <b>Before continuing the further installation
    55 process, this must be absolutely guaranteed!</b> This must also be
    56 guaranteed for <b>all</b> other remote hosts, on which PALM shall run.
    57 </ul>
    58 <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
     78well as from the remote to the local host!</b> Test this by
     79carrying
     80out e.g. on the local host: <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     81</span><span style="font-family: Courier New,Courier,monospace;">ssh&nbsp;
     82&lt;username on remote host&gt;@&lt;remote
     83IP-address&gt;</span><br> </p> <p style="line-height: 100%;">and on the remote host:<br>
     84</p> <p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
     85</span><span style="font-family: Courier New,Courier,monospace;">ssh&nbsp;
     86&lt;username on local host&gt;@&lt;local IP-adddress&gt;</span><br>
     87</p> In both cases you should&nbsp;not be
     88prompted for a password. <b>Before continuing the further
     89installation
     90process, this must be absolutely guaranteed!</b> This must also
     91be
     92guaranteed for <b>all</b> other remote hosts, on which
     93PALM shall run.
     94</ul><p style="line-height: 100%;"></p><p style="line-height: 100%;"><span style="font-weight: bold; text-decoration: underline;">Package
     95Installation</span></p><p style="line-height: 100%;">In
     96the <b>first installation step</b> a
    5997set of directories must be created both on the local and on the
    60 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
     98remote 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
     99are
    61100freely selectable (except <tt><font size="2">~/job_queue</font></tt>),
    62101however new users should use them as suggested, since many
    63102examples in this documentation as well as all example files are
    64 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>
    65 <p style="line-height: 100%;"><font color="#000000">In the <b>second
     103assuming these settings. The directory <span style="font-family: monospace;">~/palm/current_version</span>
     104on the local host will be called the working directory from now on. </p>
     105<p style="line-height: 100%;"><font color="#000000">In
     106the <b>second
    66107step</b>
    67108a working copy of the recent version of the PALM software package,
    68 including the source code, scripts, documentation, etc.&nbsp; must be
     109including the source code, scripts, documentation, etc.&nbsp; must
     110be
    69111copied to the working directory (</font><font color="#000000">local
    70112host!) by executing the following
    71 commands. Replace &lt;your username&gt; by the name that you chose to
    72 access the repository, and &lt;#&gt; by any of the available PALM
    73 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
     113commands. Replace &lt;your username&gt; by the name that you
     114chose to
     115access the repository, and &lt;#&gt; by any of the available
     116PALM
     117releases, e.g. "<span style="font-style: italic;">3.1c</span>"
     118(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
     119~/palm/current_version</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">svn
     120checkout --username &lt;your username&gt;
     121svn://130.75.105.45/palm/tags/release-&lt;#&gt; trunk</span><br></div><p style="line-height: 100%;"><font color="#000000">You
     122will then be prompted for your password. After finishing, the
     123subdirectory</font><font style="font-family: Courier New,Courier,monospace;" color="#000000"> trunk </font><font color="#000000">should
    74124appear in your working directory. It contains a number of further
    75 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
    76 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
     125subdirectories which contain e.g. the PALM source code (</font><font style="font-family: Courier New,Courier,monospace;" color="#000000">SOURCE</font><font color="#000000">)
     126and 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
     127directory named<span style="font-family: Courier New,Courier,monospace;"> abcde </span>instead
     128of a directory named<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.
     129But keep in mind that you will have to adjust several paths given
     130below, 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
     131your working copy of PALM, unless you&nbsp;know exactly what you
     132are doing.</p><p style="line-height: 100%; font-weight: bold;"><span style="font-weight: normal;">You can also get a copy of the
     133most 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,
     134this version may contain bugs and new features may not be documented. <span style="font-weight: bold;">In future PALM releases,
     135repository access to this most recent&nbsp;version will
     136probably 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
     137Configuration</span></font></p><p style="line-height: 100%;"><font color="#000000">To
    77138use the PALM scripts, the PATH variable has to be extended and the
    78139environment variable PALM_BIN has to be set (on local and remote host)
    79 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
     140in the respective profile of the users default shell (e.g. in<span style="font-family: Courier New,Courier,monospace;"> .profile</span>,
     141if<span style="font-family: Courier New,Courier,monospace;">
     142ksh </span>is used):</font></p><p style="line-height: 100%; margin-left: 40px;"><font style="font-family: Courier New,Courier,monospace;" color="#000000">export
     143PATH=$HOME/palm/current_version/trunk/SCRIPTS:$PATH</font><font color="#000000"><br><span style="font-family: Courier New,Courier,monospace;">export
     144PALM_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
     145may habe to login again in order to activate these settings.</font></p><font color="#000000">On the local and on the remote host, some
     146small helper/utility programs have to be installed, which are e.g.
     147later used by <span style="font-weight: bold;">mrun</span>
     148or for PALM data postprocessing. The installation is done by <span style="font-weight: bold;">mbuild</span>. This script
     149requires a configuration file<span style="font-family: Courier New,Courier,monospace;">
     150.mrun.config</span>, which will be also used by <span style="font-weight: bold;">mrun</span> in the
     151following. A copy has to be put into the working directory under the
     152name<span style="font-family: Courier New,Courier,monospace;">
     153.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
     154trunk/SCRIPTS/.mrun.config.default .mrun.config</span></font></p><font color="#000000">Beside many other things, this file contains
     155typical installation parameters
    80156like compiler name, compiler options, etc.
    81 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">
    82 </font>
    83 <br><font color="#000000">To avoid the
     157for a set of different remote hosts. Please edit this file, uncomment
     158lines like</font><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">#%remote_username
     159&nbsp;&lt;replace by your ... username&gt; &nbsp;
     160&lt;remote-computer-shortcut&gt;</div><p style="line-height: 100%;"><font color="#000000">by
     161removing the first hash (<span style="font-family: Courier New,Courier,monospace;">#</span>)
     162character and replace the string "<span style="font-family: Courier New,Courier,monospace;">&lt;replace
     163by ...&gt;</span>" by your username on the respective host
     164given in the <span style="font-family: Courier New,Courier,monospace;">&lt;remote-computer-shortcut&gt;</span>.
     165You only have to uncomment lines for those hosts on which you intend to
     166use PALM.</font></p><p style="line-height: 100%;"><font color="#000000">After modifying the configuration file, the
     167respective 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
     168second 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
     169host.</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
     170of PALM Code</span></font></p><font color="#000000">
     171</font><br><font color="#000000">To avoid the
    84172re-compilation of the complete source code for each model run, PALM
    85 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
     173willl be pre-compiled once on the remote host by again using the script
     174<span style="font-weight: bold;">mbuild</span>. Due
     175to the use of
    86176FORTRAN modules in the source code, the subroutines must be compiled
    87 in a certain order. Therefore the so-called <i>make</i> mechanism
     177in a certain order. Therefore the so-called <i>make</i>
     178mechanism
    88179is used (see the respective man-page of the Unix operating system),
    89 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">,
    90 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
     180requiring a<span style="font-family: Courier New,Courier,monospace;">
     181</span></font><font style="font-family: Courier New,Courier,monospace;" color="#000000">Makefile</font><font color="#000000">,
     182in which the dependencies are described. This file is found in
     183subdirectory <span style="font-family: Courier New,Courier,monospace;">trunk/SOURCE<span style="font-family: Times New Roman,Times,serif;">, where
     184also the PALM code is stored</span></span>. The compiled
     185sources (object
    91186files) are
    92187stored&nbsp;on the remote computer in the default directory
    93188</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
    94 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
    95 </span>will prompt some queries<font color="#000000">, which must all be
    96 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
     189pre-compilation for the remote host (here the IBM-Regatta of HLRN) is
     190done by</font><span style="font-family: monospace;"></span></p><div style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">mbuild
     191-h ibmh&nbsp;&nbsp;</span></div><p style="line-height: 100%;"><span style="font-family: Courier New,Courier,monospace;">mbuild
     192</span>will prompt some queries<font color="#000000">,
     193which must all be
     194answered "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
     195the respective compiler calls to the remote
    97196host where they are carried out interactively. You can follow the
    98197progress at the terminal window, where also error messages
    99198are displayed (hopefully not for this standard installation). By just
    100199entering </font></p><p style="line-height: 100%;">
    101 </p>
    102 <blockquote style="line-height: 100%; font-family: Courier New,Courier,monospace;"><font color="#000000">mbuild</font></blockquote>
    103 <p style="line-height: 100%;"><font color="#000000">PALM will
     200</p><blockquote style="line-height: 100%; font-family: Courier New,Courier,monospace;"><font color="#000000">mbuild</font></blockquote>
     201<p style="line-height: 100%;"><font color="#000000">PALM
     202will
    104203be (consecutively) pre-compiled for all remote hosts listed in
    105 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>
    106 </p>
    107 <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,
     204the configuration file. If you want to compile for the local host only,
     205please enter</font></p><p style="line-height: 100%; margin-left: 40px;"><font color="#000000"><span style="font-family: Courier New,Courier,monospace;">mbuild
     206-h lcmuk</span> </font>
     207</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,
    108208after the compilation has been finished, the PALM installation has to
    109209be verified. For this
    110210purpose a simple test run is carried out. This once again requires the <b>mrun
    111211</b>configuration file (described in </font><a href="chapter_3.2.html"><font color="#000080">chapter
    112 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
    113 file</font></a><font color="#000000"> (described in </font><a href="chapter_4.4.html"><font color="#000080">chapter
    114 4.4</font></a>)<font color="#000000">. The parameter file must be
     2123.2</font></a><font color="#000000">), as well
     213as the </font><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/INSTALL/example_p3d"><font color="#000080">parameter
     214file</font></a><font color="#000000">
     215(described in </font><a href="chapter_4.4.html"><font color="#000080">chapter
     2164.4</font></a>)<font color="#000000">. The
     217parameter file must be
    115218copied from the PALM working copy by<br>
    116 </font>
    117 <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>
    118 <p style="line-height: 100%;"><font color="#000000">The test run can
     219</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
     220trunk/INSTALL/example_p3d&nbsp;JOBS/example/INPUT/example_p3d</font><font color="#000000"><span style="font-family: Courier New,Courier,monospace;"></span></font></div>
     221<p style="line-height: 100%;"><font color="#000000">The
     222test run can
    119223now be started by executing the command </font>
    120 </p>
    121 <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>
     224</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>
    122225<font color="#000000">This specific run
    123226will be carried out on 8 PEs and is allowed to use up to 500 seconds
    124 CPU time. After pressing &lt;return&gt;, the most important settings of
     227CPU time. After pressing &lt;return&gt;, the most important
     228settings of
    125229the job are displayed at the terminal window
    126 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;
    127 <i>Submitted to queue&hellip; by&hellip;&rdquo; </i>should be displayed. Now the job is
    128 queued and either started immediately or at a later time, depending on the
     230and 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;).
     231Next, a message of the queuing system like &ldquo;<i>Request</i>
     232&hellip;
     233<i>Submitted to queue&hellip; by&hellip;&rdquo; </i>should
     234be displayed. Now the job is
     235queued and either started immediately or at a later time, depending on
     236the
    129237current workload of the remote host. Provided that it is executed
    130238immediately and that all things work as designed, the job protocol of
    131 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
     239this 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
     240more than a few minutes later. The content of this
    132241file should be carefully examined for any error messages.</font><p style="line-height: 100%;">
    133 </p>
    134 
    135 
    136 <p style="line-height: 100%;">Beside the job protocol and according to
     242</p><p style="line-height: 100%;">Beside the job
     243protocol and according to
    137244the configuration file and arguments given for <b>mrun</b>
    138 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
     245options<span style="font-family: Courier New,Courier,monospace;">
     246-d </span>and<span style="font-family: Courier New,Courier,monospace;"> -r</span><tt>,</tt>further
     247files should be found in
    139248the
    140249directories</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>
    141250<p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
    142251</span><span style="font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS/example/OUTPUT</span><span style="font-family: monospace;"></span><br>
    143 </p>
    144 <p style="line-height: 100%;">Please compare the contents of file</p>
     252</p><p style="line-height: 100%;">Please compare the
     253contents of file</p>
    145254<p style="line-height: 100%;"><span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;
    146255</span><span style="font-family: Courier New,Courier,monospace;">~/palm/current_version/JOBS/example/MONITORING/ibmh_example_rc</span><br>
    147 </p>
    148 <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
     256</p><p style="line-height: 100%;">with those of the
     257example result file which can be found under<span style="font-family: Courier New,Courier,monospace;">
     258trunk/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>
     259diff </span>command:</p><p style="line-height: 100%; margin-left: 40px; font-family: Courier New,Courier,monospace;">diff
     260&nbsp;JOBS/example/MONITORING/ibmh_example_rc
     261trunk/INSTALL/example_rc</p><p style="line-height: 100%;">where
     262it is assumed that your working directory is<span style="font-family: Courier New,Courier,monospace;">
     263~/palm/current_version</span>.</p><span style="font-weight: bold;">You should not find any
     264difference between these two files</span>, except of the run date
     265and time displayed at the top of the file header. <font color="#000000">If
    149266the file contents are identical, the installation is successfully
    150267completed.</font>
    151 <p style="line-height: 100%;">If you have any problems with the PALM
     268<p style="line-height: 100%;">If you have any problems
     269with the PALM
    152270installation, the members of the PALM working group are pleased to
    153271help you. &nbsp; </p>
    154 <hr>
    155 <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>
    156 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 02/03/07 (SR) </p>
     272<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>
     273<p style="line-height: 100%;"><i>Last
     274change:&nbsp;</i> $Id$</p>
    157275</body></html>

  • palm/trunk/DOC/app/chapter_5.1.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    22<html><head>
    3   <meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 5.1</title>
    4  
    5   <meta content="StarOffice 7  (Win32)" name="GENERATOR">
    6   <meta content="Siegfried Raasch" name="AUTHOR">
    7   <meta content="20041103;12395815" name="CREATED">
    8   <meta content="20041119;12321236" name="CHANGED">
    9   <meta content="parallel LES model" name="KEYWORDS"></head><body dir="ltr" lang="en-US">
    10 <h3>5.1 Installation of new / other versions</h3>
    11 <p>The PALM&nbsp;group announces code revisions by emails send to the
     3<meta content="text/html; charset=windows-1252" http-equiv="CONTENT-TYPE"><title>PALM chapter 5.1</title>
     4<meta content="StarOffice 7 (Win32)" name="GENERATOR">
     5<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>
     6<body style="direction: ltr;" lang="en-US"><h3>5.1
     7Installation of new / other versions</h3>
     8<p>The PALM&nbsp;group announces code revisions by emails
     9send to the
    1210PALM mailing list. If you like to be put on this list, just send an
    13 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
     11email to <a href="mailto:raasch@muk.uni-hannover.de">raasch@muk.uni-hannover.de</a>.
     12Details about new releases can be found in the
    1413<a href="../tec/technical_documentation.html">technical/numerical
    15 documentation</a>. Users can easily make version updates by changing into
     14documentation</a>. Users can easily make version updates by
     15changing into
    1616the working directory<span style="font-family: Courier New,Courier,monospace;">
    1717~/palm/current_version
    18 </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
     18</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
     19update</span></p><p><span style="font-family: Courier New,Courier,monospace;"></span>This
     20updates all files in the PALM working copy in subdirectory<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.
     21The update may fail due&nbsp;the&nbsp;<span style="font-weight: bold;">subversion</span> rules, if
     22you have modified the contents of<span style="font-family: Courier New,Courier,monospace;"> trunk</span>.
     23In case of any conflicts, please refer to the <span style="font-weight: bold;">subversion</span>
     24documentation on how to remove them.&nbsp;In order to avoid such
     25conflicts, modifications of the default PALM code should be omitted and
    1926be restricted to the user-interface only
    2027(see <a href="chapter_3.5.html">chapter
    21283.5</a>).</p>
    22 <ul style="font-family: Courier New,Courier,monospace;">
    23 </ul>
    2429
    25 <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>
     30<p>Alternatively, you can install new or other releases in a
     31different directory, eg.</p><p style="margin-left: 40px;"><span style="font-family: Courier New,Courier,monospace;">mkdir
     32~/palm/release-3.1c</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">cd
     33~/palm/release-3.1c</span><br style="font-family: Courier New,Courier,monospace;"><span style="font-family: Courier New,Courier,monospace;">svn
     34checkout --username &lt;your username&gt;
     35svn://130.75.105.45:palm/tags/release-3.1c trunk</span></p>
    2636<p>However, this would require to carry out again the complete
    2737installation process described in chapter 5.0. So far, differet
    28 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
    29 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>
    30 <ul style="font-family: Courier New,Courier,monospace;">
    31 </ul>
     38versions of PALM cannot be used at the same time.</p><p>After
     39updating the working copy, please check for any differences between
     40your current configuration file (<span style="font-family: Courier New,Courier,monospace;">.mrun.config</span>)
     41and the default configuration file under<span style="font-family: Courier New,Courier,monospace;">
     42trunk/SCRIPTS/.mrun.config.default </span>and adjust your
     43current file, if neccessary.</p><p>The scripts and the
     44pre-compiled code must then be updated
     45via</p><div style="margin-left: 40px; font-family: Courier New,Courier,monospace;">mbuild
     46-u -h lcmuk<br>mbuild -u -h ibmh<br>mbuild -h ibmh</div><p>or
     47via</p>
    3248
    33 <blockquote style="font-family: Courier New,Courier,monospace;">mbuild -u<br>mbuild</blockquote>
     49<blockquote style="font-family: Courier New,Courier,monospace;">mbuild
     50-u<br>mbuild</blockquote>
    3451<p>on all remote hosts listed in the configuration file<span style="font-family: Courier New,Courier,monospace;">
    3552.mrun.config</span>. </p>
    36 <p>As a last step, a suitable test run should be carried out. It should
     53<p>As a last step, a suitable test run should be carried out. It
     54should
    3755be carefully examined whether and how the results created by the new
    3856version differ from those of the old version. Possible discrepancies
    … …  
    4058documentation</a>
    4159should be communicated as soon as possible to the PALM group.
    42 </p>
    43 <hr>
    44 <p><br>
    45 <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>
     60</p><hr>
     61<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>
    4662&nbsp;
    47 <br>
    48 &nbsp;<span style="font-style: italic;">Last change:</span> 02/03/07
    49 (SR)<br>
    50 </p>
    51 </body></html>
     63<br>&nbsp;<span style="font-style: italic;">Last
     64change:</span> $Id$<br>
     65</p></body></html>

  • palm/trunk/DOC/app/index.html

    r54 r62  
    148148<p><span style="font-family: Thorndale;" lang="EN-GB">Current
    149149model
    150 version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.1c<br>
    151 <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
    152 documentation:&nbsp;&nbsp;&nbsp; 05/03/07 <o:p></o:p></span></p>
     150version:&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>
    153151<div style="text-align: center;" class="MsoNormal" align="center"><span style="font-family: Thorndale;">
    154152<hr align="center" size="2" width="100%"></span></div>
    … …  
    215213<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>
    216214Installation of <span class="SpellE">new</span><span class="SpellE"></span>
    217 <span class="SpellE">versions</span><o:p></o:p></span></p>
    218 <p style="margin-bottom: 12pt;"><span style="font-family: Thorndale;"><br>
     215<span class="SpellE">versions</span><o:p></o:p></span></p><font color="#000000">&nbsp;
    219216<br>
    220 <br>
    221 <br>
    222 <br>
    223 <br style="">
    224 <!--[if !supportLineBreakNewLine]--><br style="">
    225 <!--[endif]--><o:p></o:p></span></p>
    226 </div>
     217&nbsp;
     218<span style="font-style: italic;">Last change:</span>
     219$Id$<br>
     220</font></div>
    227221</body></html>

  • palm/trunk/DOC/tec/technical_documentation.html

    r54 r62  
    11<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
    22<html><head>
    3 
    4  
    5   <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
    6 
    7  
    8   <meta content="Mozilla/4.73 [en] (X11; U; HP-UX B.10.20 9000/782) [Netscape]" name="GENERATOR">
    9 
    10  
    11   <meta content="Siegfried Raasch" name="Author">
    12 
    13  
    14   <meta content="parallel LES model" name="Keywords"><title>PALM technical/numerical documentation</title></head>
    15 <body>
    16 
    17 <font size="+4">PALM&nbsp;&nbsp;
     3<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
     4documentation</title></head>
     5<body><font size="+4">PALM&nbsp;&nbsp;
    186</font>a
    197<b>pa</b>rallelized
    208<b>L</b>ES <b>m</b>odel
    21 <br>
    22 
    23 <hr width="100%">
    24 <br>
    25 
    26 <font size="+2">technical/numerical documentation</font>
    27 <br>
    28 
    29 &nbsp;
    30 <br>
    31 
    32 &nbsp;
    33 <br>
    34 
    35 <table nosave="" cellpadding="0" cellspacing="0">
    36 
    37   <caption>&nbsp; <br>
    38 
    39   </caption><tbody>
    40 
    41  
    42   </tbody><tbody>
    43 
    44  
    45   </tbody> <tbody>
    46 
    47     <tr nosave="">
    48 
    49       <td nosave=""><b>Current model version:</b></td>
    50 
    51       <td><span style="font-weight: bold;">3.1c</span></td>
    52 
    53     </tr>
    54 
    55     <tr nosave="">
    56 
    57       <td nosave=""><b>Last change of this document</b>:&nbsp;</td>
    58 
    59       <td nosave=""><b>05/03/07</b></td>
    60 
    61     </tr>
    62 
    63  
    64   </tbody>
    65 </table>
    66 
    67 <hr width="100%">
     9<br><hr width="100%">
     10<br><font size="+2">technical/numerical documentation</font>
     11<br>&nbsp;
     12<br>&nbsp;
     13<br><table nosave="" cellpadding="0" cellspacing="0"> <caption>&nbsp; <br> </caption><tbody>
     14</tbody><tbody> </tbody> <tbody> <tr nosave=""> <td nosave=""><b>Current
     15model version:</b></td> <td><span style="font-weight: bold;">3.1c</span></td> </tr>
     16<tr nosave=""> <td nosave=""><b>Last
     17change of this document</b>:&nbsp;</td> <td nosave=""><b>$Id$</b></td> </tr>
     18</tbody>
     19</table><hr width="100%">
    6820<p><font size="+2">Table of contents</font>
    69 <br>
    70 
    71 &nbsp;
    72 <br>
    73 
    74 &nbsp;
    75 </p>
    76 
    77 <ul>
    78 
    79   <a href="#Kapitel1.0">1.0</a>&nbsp; History of changes
    80  
    81   <p><a href="#Kapitel2.0">2.0</a>&nbsp; How to change the model source
    82 code </p>
    83 
    84  
    85   <p><a href="#Kapitel3.0">3.0</a>&nbsp; Description of selected parts
     21<br>&nbsp;
     22<br>&nbsp;
     23</p><ul> <a href="#Kapitel1.0">1.0</a>&nbsp;
     24History of changes <p><a href="#Kapitel2.0">2.0</a>&nbsp;
     25How to change the model source
     26code </p> <p><a href="#Kapitel3.0">3.0</a>&nbsp;
     27Description of selected parts
    8628of
    8729the model source code <br>
    88 
    8930&nbsp;</p>
    90 
    91 </ul>
    92 
    93 <b>Please note: Parts of this document are still in German. We
     31</ul><b>Please note: Parts of this document are still in
     32German. We
    9433apologize
    9534for any inconvenience.</b>
    96 <br>
    97 
    98 &nbsp;
    99 <h2><a name="Kapitel1.0"></a>1.0&nbsp; History of changes</h2>
    100 
     35<br>&nbsp;
     36<h2><a name="Kapitel1.0"></a>1.0&nbsp;
     37History of changes</h2>
    10138The following table documents all changes to the model since July, 7th
    102391998. Entries in the fourth column specify the type of the change:
    … …  
    10744respective
    10845routines.
    109 <br>
    110 
    111 &nbsp;
    112 <br>
    113 
    114 <table nosave="" style="width: 100%;" border="1">
    115 
    116   <caption>&nbsp; <br>
    117 
    118   </caption><tbody>
    119 
    120  
    121   </tbody><tbody>
    122 
    123  
    124   </tbody> <tbody>
    125 
    126     <tr>
    127 
    128       <td><b>date</b></td>
    129 
    130       <td><b>author</b></td>
    131 
    132       <td><b>model</b> <br>
    133 
    134       <b>version</b></td>
    135 
    136       <td><b>type</b></td>
    137 
    138       <td><b>description</b></td>
    139 
    140       <td><b>affected routines</b></td>
    141 
    142     </tr>
    143 
    144     <tr nosave="" valign="top">
    145 
    146       <td>06/07/98</td>
    147 
    148       <td>SR</td>
    149 
    150       <td>1.0</td>
    151 
    152       <td>C</td>
    153 
    154       <td nosave="">&Auml;nderung von Default-Werten
     46<br>&nbsp;
     47<br><table nosave="" style="width: 100%;" border="1"> <caption>&nbsp; <br> </caption><tbody>
     48</tbody><tbody> </tbody> <tbody> <tr> <td><b>date</b></td>
     49<td><b>author</b></td> <td><b>model</b>
     50<br> <b>version</b></td> <td><b>type</b></td>
     51<td><b>description</b></td> <td><b>affected
     52routines</b></td> </tr> <tr nosave="" valign="top"> <td>06/07/98</td> <td>SR</td>
     53<td>1.0</td> <td>C</td> <td nosave="">&Auml;nderung
     54von Default-Werten
    15555(initializing_actions, end_time,
    15656fcl_factor, use_prior_plot1d_parameters), zus&auml;tzliche
    15757&Uuml;berpr&uuml;fung
    158 von Parametern auf Zul&auml;ssigkeit (prandtl_layer, psolver, nx, ny,
     58von Parametern auf Zul&auml;ssigkeit (prandtl_layer, psolver, nx,
     59ny,
    15960nz,
    160 fcl_factor), H&ouml;he der Schnittebenen der Horizontalschnitte wird
     61fcl_factor), H&ouml;he der Schnittebenen der Horizontalschnitte
     62wird
    16163auf
    162 Plots exakt ausgegeben (uv- bzw. w-Gitter).</td>
    163 
    164       <td>modules, check_parameters, plot_2d</td>
    165 
    166     </tr>
    167 
    168     <tr nosave="" valign="top">
    169 
    170       <td>"</td>
    171 
    172       <td>SR</td>
    173 
    174       <td>1.0</td>
    175 
    176       <td>N</td>
    177 
    178       <td>Neues Modul test_variables wird in (fast) allen
     64Plots exakt ausgegeben (uv- bzw. w-Gitter).</td> <td>modules,
     65check_parameters, plot_2d</td> </tr> <tr nosave="" valign="top"> <td>"</td> <td>SR</td>
     66<td>1.0</td> <td>N</td> <td>Neues Modul
     67test_variables wird in (fast) allen
    17968Programmteilen benutzt
    18069(USE). <b>Wichtig</b>: dieses Modul steht in der Datei <tt>module_test.f90.
    18170D</tt>iese Datei mu&szlig; in der mrun- und add_library -
    18271Konfigurationsdatei
    183 bei der Variablen <tt>module_files</tt> aufgef&uuml;hrt werden.</td>
    184 
    185       <td nosave="">(fast) alle&nbsp; <br>
    186 
    187 Neu: module_test</td>
    188 
    189     </tr>
    190 
    191     <tr nosave="" valign="top">
    192 
    193       <td>16/07/98</td>
    194 
    195       <td>SR</td>
    196 
    197       <td>1.0</td>
    198 
    199       <td>N</td>
    200 
    201       <td nosave="">Anpassung an die T3E-Rechner in Juelich (cpp -
    202 Direktiven)</td>
    203 
    204       <td>advec_s_bc, check_open, check_parameters, cpu_zeitmessung,
     72bei der Variablen <tt>module_files</tt>
     73aufgef&uuml;hrt werden.</td> <td nosave="">(fast)
     74alle&nbsp; <br>
     75Neu: module_test</td> </tr> <tr nosave="" valign="top"> <td>16/07/98</td> <td>SR</td>
     76<td>1.0</td> <td>N</td> <td nosave="">Anpassung
     77an die T3E-Rechner in Juelich (cpp -
     78Direktiven)</td> <td>advec_s_bc, check_open,
     79check_parameters, cpu_zeitmessung,
    20580init_pegrid,
    20681local_getenv, local_system, local_tremain, local_tremain_ini, poisfft</td>
    207 
    208     </tr>
    209 
    210     <tr nosave="" valign="top">
    211 
    212       <td>24/07/98</td>
    213 
    214       <td>MS</td>
    215 
    216       <td>1.0</td>
    217 
    218       <td>C</td>
    219 
    220       <td nosave="">Anpassung des Druckloesealgorithmusses an
     82</tr> <tr nosave="" valign="top"> <td>24/07/98</td>
     83<td>MS</td> <td>1.0</td> <td>C</td>
     84<td nosave="">Anpassung des Druckloesealgorithmusses an
    22185Vorgehensweise von
    222 Schmidt, Schumann und Volkert (DFVLR-Mitteilung 84-15, S. 20-26)&nbsp;</td>
    223 
    224       <td>poisfft</td>
    225 
    226     </tr>
    227 
    228     <tr nosave="" valign="top">
    229 
    230       <td>27/07/98</td>
    231 
    232       <td>MS</td>
    233 
    234       <td>1.0</td>
    235 
    236       <td>C</td>
    237 
    238       <td nosave="">Berechnung von l in maketri geschieht nun
     86Schmidt, Schumann und Volkert (DFVLR-Mitteilung 84-15, S.
     8720-26)&nbsp;</td> <td>poisfft</td> </tr> <tr nosave="" valign="top"> <td>27/07/98</td>
     88<td>MS</td> <td>1.0</td> <td>C</td>
     89<td nosave="">Berechnung von l in maketri geschieht nun
    23990ausserhalb der k-Schleife,
    240 da unabhaengig von k, dadurch Rechenzeitersparnis&nbsp;</td>
    241 
    242       <td>poisfft</td>
    243 
    244     </tr>
    245 
    246     <tr nosave="" valign="top">
    247 
    248       <td>05/08/98</td>
    249 
    250       <td>SR</td>
    251 
    252       <td>1.0</td>
    253 
    254       <td>C</td>
    255 
    256       <td>Entfernung der Sonderbehandlung der Advektionsterme
     91da unabhaengig von k, dadurch Rechenzeitersparnis&nbsp;</td> <td>poisfft</td>
     92</tr> <tr nosave="" valign="top"> <td>05/08/98</td>
     93<td>SR</td> <td>1.0</td> <td>C</td>
     94<td>Entfernung der Sonderbehandlung der Advektionsterme
    25795(Piascek-Williams)
    258 bei k=1. Terme werden nun &uuml;berall gleich berechnet. Evtl. leichte
     96bei k=1. Terme werden nun &uuml;berall gleich berechnet. Evtl.
     97leichte
    25998Erh&ouml;hung der Varianzen in Oberfl&auml;chenn&auml;he.</td>
    260 
    261       <td nosave="">advec_u_pw, advec_v_pw, advec_w_pw</td>
    262 
    263     </tr>
    264 
    265     <tr nosave="" valign="top">
    266 
    267       <td nosave="">"</td>
    268 
    269       <td>SR</td>
    270 
    271       <td>1.0</td>
    272 
    273       <td>C</td>
    274 
    275       <td>Mischungsweganpassung (s. adjust_mixing_length) erfolgt nur
     99<td nosave="">advec_u_pw, advec_v_pw, advec_w_pw</td>
     100</tr> <tr nosave="" valign="top"> <td nosave="">"</td> <td>SR</td> <td>1.0</td>
     101<td>C</td> <td>Mischungsweganpassung (s.
     102adjust_mixing_length) erfolgt nur
    276103noch bei
    277 k=1. Unrealistische sekund&auml;re Maxima in den Km-Profilen oberhalb
     104k=1. Unrealistische sekund&auml;re Maxima in den Km-Profilen
     105oberhalb
    278106der
    279 Prandtl-Schicht werden damit vermieden. Leichte &Auml;nderungen in den
    280 oberfl&auml;chennahen Turbulenzgr&ouml;&szlig;en sind die Folge.</td>
    281 
    282       <td>diffusivities</td>
    283 
    284     </tr>
    285 
    286     <tr nosave="" valign="top">
    287 
    288       <td>"</td>
    289 
    290       <td>SR</td>
    291 
    292       <td>1.0</td>
    293 
    294       <td>B</td>
    295 
    296       <td>Falsche Berechnung der ben&ouml;tigten CPU-Zeit pro Sekunde
     107Prandtl-Schicht werden damit vermieden. Leichte &Auml;nderungen in
     108den
     109oberfl&auml;chennahen Turbulenzgr&ouml;&szlig;en sind die
     110Folge.</td> <td>diffusivities</td> </tr> <tr nosave="" valign="top"> <td>"</td> <td>SR</td>
     111<td>1.0</td> <td>B</td> <td>Falsche
     112Berechnung der ben&ouml;tigten CPU-Zeit pro Sekunde
    297113simulierter
    298 Zeit bei Fortsetzungsl&auml;ufen korrigiert.&nbsp;
    299      
    300       <p>Berechnung von cross_uxmin(1) und cross_uxmax(1) aus den
     114Zeit bei Fortsetzungsl&auml;ufen korrigiert.&nbsp; <p>Berechnung
     115von cross_uxmin(1) und cross_uxmax(1) aus den
    301116Werten von
    302 ug und vg entfernt. Lieferte falsche Wertebereiche f&uuml;r Plots von
     117ug und vg entfernt. Lieferte falsche Wertebereiche f&uuml;r Plots
     118von
    303119Vertikalprofilen,
    304120wenn im ersten Koordinatenkreuz nicht die Windgeschwindigkeiten
    305121gezeichnet
    306 wurden.</p>
    307 
    308       </td>
    309 
    310       <td nosave="">header, check_parameters</td>
    311 
    312     </tr>
    313 
    314     <tr nosave="" valign="top">
    315 
    316       <td nosave="">"</td>
    317 
    318       <td>SR</td>
    319 
    320       <td>1.0</td>
    321 
    322       <td>N</td>
    323 
    324       <td>Das erlaubte Maximum und Minimum der Rif-Zahl ist nun mittels
     122wurden.</p> </td> <td nosave="">header,
     123check_parameters</td> </tr> <tr nosave="" valign="top"> <td nosave="">"</td> <td>SR</td>
     124<td>1.0</td> <td>N</td> <td>Das
     125erlaubte Maximum und Minimum der Rif-Zahl ist nun mittels
    325126der Initialparameter
    326127rif_max und rif_min einstellbar (Werte waren bisher fest auf -2.0, +1.0
    327 eingestellt).</td>
    328 
    329       <td>check_parameters, header, init_1d_model, modules, parin,
     128eingestellt).</td> <td>check_parameters, header,
     129init_1d_model, modules, parin,
    330130prandtl_fluxes,
    331 read_var_list, write_var_list</td>
    332 
    333     </tr>
    334 
    335     <tr nosave="" valign="top">
    336 
    337       <td nosave="">23/09/98</td>
    338 
    339       <td>SR</td>
    340 
    341       <td>1.0</td>
    342 
    343       <td>B</td>
    344 
    345       <td>Initialisierung von Feldern im Fall von initializing_action =
     131read_var_list, write_var_list</td> </tr> <tr nosave="" valign="top"> <td nosave="">23/09/98</td>
     132<td>SR</td> <td>1.0</td> <td>B</td>
     133<td>Initialisierung von Feldern im Fall von initializing_action =
    346134"<i>set_constant_profiles</i>"
    347 und "<i>set_1d-model_profiles</i>" korrigiert.&nbsp;
    348      
    349       <p>2D-Plotausgabe von u* und theta* korrigiert. Hier wurden
     135und "<i>set_1d-model_profiles</i>" korrigiert.&nbsp; <p>2D-Plotausgabe
     136von u* und theta* korrigiert. Hier wurden
    350137bisher falsche
    351 Felder herausgeschrieben.&nbsp; </p>
    352 
    353      
    354       <p>Bei SOR-Aufrufen war bisher dp nicht initialisiert.
    355 Entsprechend ge&auml;ndert.</p>
    356 
    357       </td>
    358 
    359       <td>init_3d_model, plot_2d, pres</td>
    360 
    361     </tr>
    362 
    363     <tr nosave="" valign="top">
    364 
    365       <td>"</td>
    366 
    367       <td>SR</td>
    368 
    369       <td>1.0</td>
    370 
    371       <td>C</td>
    372 
    373       <td nosave="">Ausgabeformate f&uuml;r Statistik-Ausgaben auf
     138Felder herausgeschrieben.&nbsp; </p> <p>Bei
     139SOR-Aufrufen war bisher dp nicht initialisiert.
     140Entsprechend ge&auml;ndert.</p> </td> <td>init_3d_model,
     141plot_2d, pres</td> </tr> <tr nosave="" valign="top"> <td>"</td> <td>SR</td>
     142<td>1.0</td> <td>C</td> <td nosave="">Ausgabeformate
     143f&uuml;r Statistik-Ausgaben auf
    374144Datei RUN_CONTROL
    375 um einige Kommastellen erweitert.&nbsp;
    376      
    377       <p>Lieferung von ausf&uuml;hrlicheren Informationen bei
     145um einige Kommastellen erweitert.&nbsp; <p>Lieferung von
     146ausf&uuml;hrlicheren Informationen bei
    378147Programmabbruch
    379 durch Unterschreitung des minimal erlaubten Zeitschritts.</p>
    380 
    381       </td>
    382 
    383       <td>run_control, timestep</td>
    384 
    385     </tr>
    386 
    387     <tr nosave="" valign="top">
    388 
    389       <td nosave="">"</td>
    390 
    391       <td>SR</td>
    392 
    393       <td>1.0</td>
    394 
    395       <td>N</td>
    396 
    397       <td>Rechnungen mit geneigter Ebene zur Simulation von
     148durch Unterschreitung des minimal erlaubten Zeitschritts.</p> </td>
     149<td>run_control, timestep</td> </tr> <tr nosave="" valign="top"> <td nosave="">"</td>
     150<td>SR</td> <td>1.0</td> <td>N</td>
     151<td>Rechnungen mit geneigter Ebene zur Simulation von
    398152Kaltluftabfl&uuml;ssen
    399153sind erlaubt. Gestartet und gesteuert werden sie mit dem
    … …  
    401155Realisiert wird die geneigte Ebene durch entsprechende
    402156Schr&auml;gstellung
    403 des Schwerkraftvektors. Dadurch erh&auml;lt auch die u-Komponente der
     157des Schwerkraftvektors. Dadurch erh&auml;lt auch die u-Komponente
     158der
    404159Windgeschwindigkeit
    405 einen Anteil der Auftriebskraft.&nbsp;
    406      
    407       <p>Diese Implementierung ist noch nicht abgeschlossen. Die
     160einen Anteil der Auftriebskraft.&nbsp; <p>Diese
     161Implementierung ist noch nicht abgeschlossen. Die
    408162Simulation von
    409163Kaltluftabfl&uuml;ssen erfordert bisher noch Eingriffe "von Hand".</p>
    410 
    411       </td>
    412 
    413       <td>buoyancy, check_parameters, header, leap_frog, modules,
     164</td> <td>buoyancy, check_parameters, header, leap_frog,
     165modules,
    414166parin, prandtl_fluxes,
    415 read_var_list, write_var_list</td>
    416 
    417     </tr>
    418 
    419     <tr nosave="" valign="top">
    420 
    421       <td>15/12/98</td>
    422 
    423       <td>SR</td>
    424 
    425       <td>1.0</td>
    426 
    427       <td>N</td>
    428 
    429       <td>Vereinbarung einer Cache-Layer zur schnelleren bin&auml;ren
     167read_var_list, write_var_list</td> </tr> <tr nosave="" valign="top"> <td>15/12/98</td> <td>SR</td>
     168<td>1.0</td> <td>N</td> <td>Vereinbarung
     169einer Cache-Layer zur schnelleren bin&auml;ren
    430170I/O auf
    431 T3E-Rechnern.&nbsp;
    432      
    433       <p>Ermittelung wahrer I/O-Zeiten f&uuml;r bin&auml;re
     171T3E-Rechnern.&nbsp; <p>Ermittelung wahrer I/O-Zeiten
     172f&uuml;r bin&auml;re
    434173Ein-/Ausgabe auf
    435 T3E-Rechnern mit TIMEF.</p>
    436 
    437       </td>
    438 
    439       <td nosave="">check_open,&nbsp; <br>
    440 
    441 cpu_zeitmessung, init_3d_model, write_3d_model</td>
    442 
    443     </tr>
    444 
    445     <tr nosave="" valign="top">
    446 
    447       <td nosave="">"</td>
    448 
    449       <td>SR</td>
    450 
    451       <td>1.0</td>
    452 
    453       <td>B</td>
    454 
    455       <td>Bekanntgabe von run_description_header an alle PE's.&nbsp;
    456      
    457       <p>Diese Programm&auml;nderung erfordert auf T3E-Rechnern
     174T3E-Rechnern mit TIMEF.</p> </td> <td nosave="">check_open,&nbsp;
     175<br>cpu_zeitmessung, init_3d_model, write_3d_model</td> </tr>
     176<tr nosave="" valign="top"> <td nosave="">"</td>
     177<td>SR</td> <td>1.0</td> <td>B</td>
     178<td>Bekanntgabe von run_description_header an alle
     179PE's.&nbsp; <p>Diese Programm&auml;nderung erfordert auf
     180T3E-Rechnern
    458181zwingend den
    459182Einsatz der MPI-Version mpt.1.2.0.1. In dieser neuen Version tritt auch
    460 der alte Fehler in MPI_ALLREDUCE nicht mehr auf, so da&szlig; ab jetzt
    461 mpt.1.1.0.1 nicht mehr verwendet werden mu&szlig;.</p>
    462 
    463       </td>
    464 
    465       <td>parles</td>
    466 
    467     </tr>
    468 
    469     <tr nosave="" valign="top">
    470 
    471       <td nosave="">05/02/99</td>
    472 
    473       <td>SR</td>
    474 
    475       <td>1.1</td>
    476 
    477       <td>C/N</td>
    478 
    479       <td>Implementierung des Upstream-Spline- Verfahrens zur Advektion
     183der alte Fehler in MPI_ALLREDUCE nicht mehr auf, so da&szlig; ab
     184jetzt
     185mpt.1.1.0.1 nicht mehr verwendet werden mu&szlig;.</p> </td>
     186<td>parles</td> </tr> <tr nosave="" valign="top"> <td nosave="">05/02/99</td>
     187<td>SR</td> <td>1.1</td> <td>C/N</td>
     188<td>Implementierung des Upstream-Spline- Verfahrens zur Advektion
    480189von Impuls
    481 und skalaren Gr&ouml;&szlig;en (neue UP's, s. rechts). Berechnung von
     190und skalaren Gr&ouml;&szlig;en (neue UP's, s. rechts).
     191Berechnung von
    482192Variablen
    483 f&uuml;r spezielle Advektionsverfahren in eigenst&auml;ndiges UP
     193f&uuml;r spezielle Advektionsverfahren in eigenst&auml;ndiges
     194UP
    484195ausgelagert
    485 (<tt>init_advec</tt> + eigenes Modul <tt>advection</tt>). Reines
     196(<tt>init_advec</tt> + eigenes Modul <tt>advection</tt>).
     197Reines
    486198Euler-/Upstream-Verfahren
    487 kann gerechnet werden.&nbsp;
    488      
    489       <p>Schnelle bin&auml;re I/O (s. 15/12/98) wieder abgeschaltet, da
     199kann gerechnet werden.&nbsp; <p>Schnelle bin&auml;re I/O
     200(s. 15/12/98) wieder abgeschaltet, da
    490201Dateien
    491 nicht wieder einlesbar sind. Druckst&ouml;rung (p) wird zu Beginn auf 0
     202nicht wieder einlesbar sind. Druckst&ouml;rung (p) wird zu Beginn
     203auf 0
    492204gesetzt, damit sie keine Tendenzen im ersten Zeitschritt hervorruft.</p>
    493 
    494       </td>
    495 
    496       <td>advec_s_bc, check_open, check_parameters, flow_statistics,
     205</td> <td>advec_s_bc, check_open, check_parameters,
     206flow_statistics,
    497207header,
    498208init_3d_model, init_grid, leap_frog, modules, parin, plot_2d, plot_ts,
    499 read_var_list, timestep, write_3d_binary, write_var_list&nbsp;
    500      
    501       <p><b>Neu:</b> <br>
    502 
     209read_var_list, timestep, write_3d_binary, write_var_list&nbsp; <p><b>Neu:</b>
     210<br>
    503211advec_s_ups, advec_u_ups, advec_v_ups, advec_w_ups, init_advec,
    504212long_filter,
    505 spline_x, spline_y, spline_z</p>
    506 
    507       </td>
    508 
    509     </tr>
    510 
    511     <tr nosave="" valign="top">
    512 
    513       <td nosave="">24/02/99</td>
    514 
    515       <td>SR</td>
    516 
    517       <td>1.1a</td>
    518 
    519       <td>C/N</td>
    520 
    521       <td>Kleinere Erg&auml;nzungen / &Auml;nderungen f&uuml;r Upstream
     213spline_x, spline_y, spline_z</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">24/02/99</td>
     214<td>SR</td> <td>1.1a</td> <td>C/N</td>
     215<td>Kleinere Erg&auml;nzungen / &Auml;nderungen
     216f&uuml;r Upstream
    522217- Spline,&nbsp; <br>
    523 
    524218Diverse Verbesserungen bei Berechnung der Diffusionskoeffizienten
    525219(exaktere
    … …  
    529223Wertebegrenzung
    530224bei Spline - Berechnung zur Verhinderung von "&Uuml;berschwingern"</td>
    531 
    532       <td>check_parameters, diffusion_e, diffusion_pt, diffusivities,
     225<td>check_parameters, diffusion_e, diffusion_pt, diffusivities,
    533226header,
    534227init_advec, long_filter, modules, production_e, spline_x, spline_y,
    535 spline_z</td>
    536 
    537     </tr>
    538 
    539     <tr nosave="" valign="top">
    540 
    541       <td>"</td>
    542 
    543       <td nosave="">SR</td>
    544 
    545       <td>1.1a</td>
    546 
    547       <td>N/B</td>
    548 
    549       <td>Erweiterung des des Bott - Chlond - Schemas auf Advektion der
     228spline_z</td> </tr> <tr nosave="" valign="top">
     229<td>"</td> <td nosave="">SR</td> <td>1.1a</td>
     230<td>N/B</td> <td>Erweiterung des des Bott - Chlond -
     231Schemas auf Advektion der
    550232TKE,
    551233Korrektur der Dichteberechnung (war falsch bei Galilei-Transformation)</td>
    552 
    553       <td>advec_s_bc, leap_frog</td>
    554 
    555     </tr>
    556 
    557     <tr nosave="" valign="top">
    558 
    559       <td nosave="">01/03/99</td>
    560 
    561       <td>MS</td>
    562 
    563       <td>1.1b</td>
    564 
    565       <td>N</td>
    566 
    567       <td>Kleinere Erg&auml;nzungen f&uuml;r Upstream - Spline:&nbsp;
    568      
    569       <ul>
    570 
    571         <li>Gradientenkontrolle f&uuml;r den nicht-parallelen Teil</li>
    572 
    573         <li>statistische Auswertung &uuml;ber den prozentualen Anteil
     234<td>advec_s_bc, leap_frog</td> </tr> <tr nosave="" valign="top"> <td nosave="">01/03/99</td>
     235<td>MS</td> <td>1.1b</td> <td>N</td>
     236<td>Kleinere Erg&auml;nzungen f&uuml;r Upstream -
     237Spline:&nbsp; <ul> <li>Gradientenkontrolle
     238f&uuml;r den nicht-parallelen Teil</li> <li>statistische
     239Auswertung &uuml;ber den prozentualen Anteil
    574240des
    575241Upstream-Verfahrens
    576 an der Gesamtadvektion fuer nicht-parallelen Teil</li>
    577 
    578      
    579       </ul>
    580 
    581       </td>
    582 
    583       <td>modules, spline_x, spline_y, spline_z</td>
    584 
    585     </tr>
    586 
    587     <tr nosave="" valign="top">
    588 
    589       <td>"</td>
    590 
    591       <td>SR</td>
    592 
    593       <td>1.1b</td>
    594 
    595       <td>N</td>
    596 
    597       <td>Datenkompression f&uuml;r 3D-Plotausgaben</td>
    598 
    599       <td nosave="">check_open, check_parameters, close_files, header,
     242an der Gesamtadvektion fuer nicht-parallelen Teil</li> </ul>
     243</td> <td>modules, spline_x, spline_y, spline_z</td>
     244</tr> <tr nosave="" valign="top"> <td>"</td>
     245<td>SR</td> <td>1.1b</td> <td>N</td>
     246<td>Datenkompression f&uuml;r 3D-Plotausgaben</td> <td nosave="">check_open, check_parameters, close_files, header,
    600247modules,
    601 parin, plot_3d&nbsp;
    602      
    603       <p><b>Neu:</b> <br>
    604 
    605 write_compressed</p>
    606 
    607       </td>
    608 
    609     </tr>
    610 
    611     <tr nosave="" valign="top">
    612 
    613       <td nosave="">03/03/99</td>
    614 
    615       <td>SR</td>
    616 
    617       <td>1.1c</td>
    618 
    619       <td>B/C</td>
    620 
    621       <td>Schnelle bin&auml;re I/O auf T3E-Rechnern funktioniert jetzt.
     248parin, plot_3d&nbsp; <p><b>Neu:</b> <br>
     249write_compressed</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">03/03/99</td>
     250<td>SR</td> <td>1.1c</td> <td>B/C</td>
     251<td>Schnelle bin&auml;re I/O auf T3E-Rechnern funktioniert
     252jetzt.
    622253Beim
    623254bin&auml;ren Einlesen d&uuml;rfen Records nicht mit dem Trick "<tt>READ
    624 (..) idum</tt>" &uuml;berlesen werden. Zeitmessungen auf T3E erfolgen
     255(..) idum</tt>" &uuml;berlesen werden. Zeitmessungen auf T3E
     256erfolgen
    625257jetzt
    626 grunds&auml;tzlich mit <tt>TIMEF.</tt></td>
    627 
    628       <td>check_open, cpu_zeitmessung, init_3d_model, modules,
    629 write_3d_binary</td>
    630 
    631     </tr>
    632 
    633     <tr nosave="" valign="top">
    634 
    635       <td nosave="">25/03/99</td>
    636 
    637       <td>SR</td>
    638 
    639       <td>1.1d</td>
    640 
    641       <td>N</td>
    642 
    643       <td>Einbau einer Rayleigh-D&auml;mpfungsschicht sowie flexiblere
     258grunds&auml;tzlich mit <tt>TIMEF.</tt></td> <td>check_open,
     259cpu_zeitmessung, init_3d_model, modules,
     260write_3d_binary</td> </tr> <tr nosave="" valign="top"> <td nosave="">25/03/99</td>
     261<td>SR</td> <td>1.1d</td> <td>N</td>
     262<td>Einbau einer Rayleigh-D&auml;mpfungsschicht sowie
     263flexiblere
    644264Wahl der
    645265numerischen Begrenzer f&uuml;r das Upstream - Spline - Verfahren.</td>
    646 
    647       <td>check_parameters, header, init_3d_model, leap_frog, modules,
     266<td>check_parameters, header, init_3d_model, leap_frog, modules,
    648267parin,
    649 read_var_list, spline_x, spline_y, spline_z, write_var_list</td>
    650 
    651     </tr>
    652 
    653     <tr nosave="" valign="top">
    654 
    655       <td nosave="">"</td>
    656 
    657       <td>SR</td>
    658 
    659       <td>1.1d</td>
    660 
    661       <td>B</td>
    662 
    663       <td>Korrektur des Zeitschrittkriteriums bei z=zp im 1D-Modell</td>
    664 
    665       <td>init_1d_model</td>
    666 
    667     </tr>
    668 
    669     <tr nosave="" valign="top">
    670 
    671       <td>25/11/99</td>
    672 
    673       <td>SR</td>
    674 
    675       <td>1.1e</td>
    676 
    677       <td>N</td>
    678 
    679       <td nosave="">Partikelplots mit vtk-Graphiksoftware sind auf t3eh
     268read_var_list, spline_x, spline_y, spline_z, write_var_list</td> </tr>
     269<tr nosave="" valign="top"> <td nosave="">"</td>
     270<td>SR</td> <td>1.1d</td> <td>B</td>
     271<td>Korrektur des Zeitschrittkriteriums bei z=zp im 1D-Modell</td>
     272<td>init_1d_model</td> </tr> <tr nosave="" valign="top"> <td>25/11/99</td> <td>SR</td>
     273<td>1.1e</td> <td>N</td> <td nosave="">Partikelplots
     274mit vtk-Graphiksoftware sind auf t3eh
    680275m&ouml;glich.
    681276Ausgabe erfolgt im dvr-Format. Bisher noch nicht nutzbar, da noch
    682277Einstellm&ouml;glichkeiten
    683 f&uuml;r die Partikelquelle(n) fehlen. <b>Wichtig:</b> Die Benutzung
     278f&uuml;r die Partikelquelle(n) fehlen. <b>Wichtig:</b>
     279Die Benutzung
    684280der
    685281vtk-Software erfordert die zus&auml;tzliche mrun-Option <tt>-g</tt>.
    686282Das
    687 Hauptprogramm <tt>parles</tt> wird in diesem Fall zum Unterprogramm
     283Hauptprogramm <tt>parles</tt> wird in diesem Fall zum
     284Unterprogramm
    688285und
    689 von einem c++-Programm aus aufgerufen.</td>
    690 
    691       <td>header, init_3d_model, init_pegrid, leap_frog, modules,
     286von einem c++-Programm aus aufgerufen.</td> <td>header,
     287init_3d_model, init_pegrid, leap_frog, modules,
    692288parin, parles,
    693 read_var_list, write_var_list&nbsp;
    694      
    695       <p><b>Neu:</b> <br>
    696 
    697 advec_particles, init_particles, plot_particles</p>
    698 
    699       </td>
    700 
    701     </tr>
    702 
    703     <tr nosave="" valign="top">
    704 
    705       <td>"</td>
    706 
    707       <td>SR</td>
    708 
    709       <td>1.1e</td>
    710 
    711       <td nosave="">B/C</td>
    712 
    713       <td>TIMEF-Zeitmessungen von Subroutine- auf Function-Aufruf
     289read_var_list, write_var_list&nbsp; <p><b>Neu:</b>
     290<br>
     291advec_particles, init_particles, plot_particles</p> </td> </tr>
     292<tr nosave="" valign="top"> <td>"</td>
     293<td>SR</td> <td>1.1e</td> <td nosave="">B/C</td>
     294<td>TIMEF-Zeitmessungen von Subroutine- auf Function-Aufruf
    714295umgestellt.
    715 Laufindexkorrektur in <tt>spline_y</tt>. Fehler trat bei nx /= ny auf.</td>
    716 
    717       <td>cpu_zeitmessung, spline_y</td>
    718 
    719     </tr>
    720 
    721     <tr nosave="" valign="top">
    722 
    723       <td nosave="">28/12/99</td>
    724 
    725       <td>SR</td>
    726 
    727       <td>1.1f</td>
    728 
    729       <td>N</td>
    730 
    731       <td>Plot von Isooberfl&auml;chen mit vtk-Graphiksoftware sind auf
     296Laufindexkorrektur in <tt>spline_y</tt>. Fehler trat bei
     297nx /= ny auf.</td> <td>cpu_zeitmessung, spline_y</td>
     298</tr> <tr nosave="" valign="top"> <td nosave="">28/12/99</td> <td>SR</td> <td>1.1f</td>
     299<td>N</td> <td>Plot von Isooberfl&auml;chen mit
     300vtk-Graphiksoftware sind auf
    732301t3eh
    733302m&ouml;glich. Ausgabe erfolgt im dvr-Format. Bisher noch nicht
    734303allgemein
    735304nutzbar, da noch diverse manuelle Eingriffe n&ouml;tig sind.</td>
    736 
    737       <td>header, leap_frog, modules, parin, plot_particles,
    738 read_var_list, write_var_list&nbsp;
    739      
    740       <p><b>Neu:</b> <br>
    741 
    742 plot_isosurface</p>
    743 
    744       </td>
    745 
    746     </tr>
    747 
    748     <tr nosave="" valign="top">
    749 
    750       <td nosave="">10/01/00</td>
    751 
    752       <td>SR</td>
    753 
    754       <td>1.2</td>
    755 
    756       <td>C</td>
    757 
    758       <td>Randbedingungen f&uuml;r w (=0) werden explizit gesetzt, und
     305<td>header, leap_frog, modules, parin, plot_particles,
     306read_var_list, write_var_list&nbsp; <p><b>Neu:</b>
     307<br>
     308plot_isosurface</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">10/01/00</td>
     309<td>SR</td> <td>1.2</td> <td>C</td>
     310<td>Randbedingungen f&uuml;r w (=0) werden explizit gesetzt,
     311und
    759312zwar nicht
    760 nur bei&nbsp; <tt>k = nzb, nzt+1</tt> sondern auch bei&nbsp; <tt>k =
     313nur bei&nbsp; <tt>k = nzb, nzt+1</tt> sondern auch
     314bei&nbsp; <tt>k =
    761315nzt</tt>,
    762316wo bislang der vom vorigen Zeitschritt durch den Druckl&ouml;ser
    … …  
    764318Wert stand. Auch jetzt wird der Wert bei k = nzt anschlie&szlig;end
    765319durch
    766 den Druckl&ouml;ser modifiziert. Soweit bis jetzt abzusehen, hat diese
    767 &Auml;nderung nur minimale Auswirkungen auf den Prognoseverlauf. Evtl.
     320den Druckl&ouml;ser modifiziert. Soweit bis jetzt abzusehen, hat
     321diese
     322&Auml;nderung nur minimale Auswirkungen auf den Prognoseverlauf.
     323Evtl.
    768324gibt es st&auml;rkere Auswirkungen bei exzessivem Auftreten von
    769325Schwerewellen
    770326am oberen Rand (die dort aber eigentlich sowieso nicht
    771327hingeh&ouml;ren).&nbsp; <br>
    772 
    773 Variablen&uuml;bergabe an <tt>boundary_conds</tt> erfolgt&nbsp; <br>
    774 
    775 &uuml;ber Modul und nicht mehr per Parameterliste.&nbsp;
    776      
    777       <p>Bei Galilei-Transformation wird jetzt defaultm&auml;&szlig;ig
     328Variablen&uuml;bergabe an <tt>boundary_conds</tt>
     329erfolgt&nbsp; <br>
     330&uuml;ber Modul und nicht mehr per Parameterliste.&nbsp; <p>Bei
     331Galilei-Transformation wird jetzt defaultm&auml;&szlig;ig
    778332der geostrophische
    779333Wind als Translationsgeschwindigkeit verwendet (neuer
    … …  
    782336h&ouml;heren
    783337geostrophischen Windgeschwindigkeiten unterdr&uuml;ckt.&nbsp; </p>
    784 
    785      
    786       <p>3D-Feldvariablen (u, v, w, pt, e, km, kh) sowie einige
     338<p>3D-Feldvariablen (u, v, w, pt, e, km, kh) sowie einige
    7873392D-Variablen
    788340(usws, vsws, rif, shf) sind nun als Pointer deklariert, denen nach
    … …  
    7923443 Zeitebenen existieren die Targets ..._1 (z.B. u_1), ..._2, ..._3).
    793345Durch
    794 die jeweilige Neuzuordnung der Targets entf&auml;llt das Umspeichern
     346die jeweilige Neuzuordnung der Targets entf&auml;llt das
     347Umspeichern
    795348der
    796 Zeitebenen komplett (Zeitersparung: ca. 5% der Gesamtrechenzeit).&nbsp;
    797       <br>
    798 
     349Zeitebenen komplett (Zeitersparung: ca. 5% der
     350Gesamtrechenzeit).&nbsp; <br>
    799351Die Umordnung der Zeitebenen wurde ins neue UP <tt>swap_timelevel</tt>
    800 ausgelagert.&nbsp; <br>
    801 
    802       <b>Wichtig:</b> Die &Uuml;bersetzungszeiten haben durch die
     352ausgelagert.&nbsp; <br> <b>Wichtig:</b> Die
     353&Uuml;bersetzungszeiten haben durch die
    803354Einf&uuml;hrung
    804355der Pointer t.w. sehr deutlich zugenommen (<tt>leap_frog</tt>
    805356ben&ouml;tigt
    806 jetzt z.B. ca. 60 Sekunden). Au&szlig;erdem ben&ouml;tigt der Compiler
     357jetzt z.B. ca. 60 Sekunden). Au&szlig;erdem ben&ouml;tigt der
     358Compiler
    807359jetzt wesentlich mehr Speicher. Der "memory"-Parameter in den
    808360Konfigurationsdateien
    809361(.mrun.config, .al.config) muss nun mindestens den Wert 60 (MB) (t3eh,
    810 t3ej2) bzw. 45 (t3eb) und 96 (vpp) haben.&nbsp; <br>
    811 
    812       <b>Achtung:</b> bislang wurde diese &Auml;nderung nur f&uuml;r
     362t3ej2) bzw. 45 (t3eb) und 96 (vpp) haben.&nbsp; <br> <b>Achtung:</b>
     363bislang wurde diese &Auml;nderung nur f&uuml;r
    813364das
    814 reine Leapfrog-Verfahren getestet!&nbsp; </p>
    815 
    816      
    817       <p>Neue Laderoption "<tt>-D preset=nan</tt>" empfohlen (s.
     365reine Leapfrog-Verfahren getestet!&nbsp; </p> <p>Neue
     366Laderoption "<tt>-D preset=nan</tt>" empfohlen (s.
    818367Beispiel-Konfigurationsdatei).
    819 Ebenso empfehlenswert f&uuml;r Debug-L&auml;ufe: Compileroption "<tt>-ei</tt>".
     368Ebenso empfehlenswert f&uuml;r Debug-L&auml;ufe: Compileroption
     369"<tt>-ei</tt>".
    820370Diese bewirkt einen Programmabbruch, falls mit nicht initialisierten
    821371Variablen
    822372gearbeitet wird (ist aber zeitaufwendig in der Ausf&uuml;hrung!).</p>
    823 
    824       </td>
    825 
    826       <td>boundary_conds, check_parameters, header, init_3d_model,
     373</td> <td>boundary_conds, check_parameters, header,
     374init_3d_model,
    827375leap_frog,
    828 modules, parin, read_var_list, timestep, write_var_list&nbsp;
    829      
    830       <p><b>Neu:</b> <br>
    831 
    832 swap_timelevel</p>
    833 
    834       </td>
    835 
    836     </tr>
    837 
    838     <tr nosave="" valign="top">
    839 
    840       <td nosave="">10/01/00</td>
    841 
    842       <td>SR</td>
    843 
    844       <td>1.2</td>
    845 
    846       <td>B</td>
    847 
    848       <td>Der Asselin-Filter wird vor Umordnung der Zeitebenen
     376modules, parin, read_var_list, timestep, write_var_list&nbsp; <p><b>Neu:</b>
     377<br>
     378swap_timelevel</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">10/01/00</td>
     379<td>SR</td> <td>1.2</td> <td>B</td>
     380<td>Der Asselin-Filter wird vor Umordnung der Zeitebenen
    849381aufgerufen. Dies
    850382geschah bisher f&auml;lschlicherweise erst danach, sodass der
    851383Zeitfilter
    852 asymmetrisch arbeitete.&nbsp; <br>
    853 
    854       <b>Achtung:</b> diese &Auml;nderung hat Auswirkungen auf den
     384asymmetrisch arbeitete.&nbsp; <br> <b>Achtung:</b>
     385diese &Auml;nderung hat Auswirkungen auf den
    855386Prognoseverlauf.
    856387Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</td>
    857 
    858       <td>leap_frog</td>
    859 
    860     </tr>
    861 
    862     <tr nosave="">
    863 
    864       <td nosave="" valign="top">14/02/00</td>
    865 
    866       <td nosave="" valign="top">MS</td>
    867 
    868       <td nosave="" valign="top">1.2</td>
    869 
    870       <td nosave="" valign="top">B/C</td>
    871 
    872       <td><b>1D-Modell:</b> <br>
    873 
     388<td>leap_frog</td> </tr> <tr nosave="">
     389<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>
     390<br>
    874391Der Asselin-Filter im 1D-Modell wird nun auch vor der Umordnung der
    875 Zeitebenen aufgerufen (s.o.).&nbsp;
    876      
    877       <p><b>3D-Modell:</b> <br>
    878 
    879 TKE wurde bisher bei <tt>scalar_advec=bc-scheme</tt> einer zeitlichen
    880 Filterung unterzogen. Dies wird nun unterbunden.&nbsp; </p>
    881 
    882      
    883       <p>Die Divergenz der Impulsfl&uuml;sse an der Prandtl - Schicht -
     392Zeitebenen aufgerufen (s.o.).&nbsp; <p><b>3D-Modell:</b>
     393<br>
     394TKE wurde bisher bei <tt>scalar_advec=bc-scheme</tt> einer
     395zeitlichen
     396Filterung unterzogen. Dies wird nun unterbunden.&nbsp; </p> <p>Die
     397Divergenz der Impulsfl&uuml;sse an der Prandtl - Schicht -
    884398Obergrenze
    885399wird nun &uuml;ber eine ganze Gitterweite gebildet. Die bisherige
    … …  
    887401lieferte im Vergleich mit Ergebnissen anderer LES-Modelle&nbsp; zu
    888402gro&szlig;e
    889 Impulsfl&uuml;sse.&nbsp; </p>
    890 
    891      
    892       <p>Bei der Berechnung der Diffusion der Temperatur werden die
     403Impulsfl&uuml;sse.&nbsp; </p> <p>Bei der
     404Berechnung der Diffusion der Temperatur werden die
    893405Diffusionskoeffizienten
    894406nun wieder durch Mittelung f&uuml;r die entsprechenden&nbsp;
    … …  
    898410Upstream-Spline Advektionsverfahrens eingebaut wurde, bewirkte ein zu
    899411rasches
    900 Anwachsen der Grenzschicht mit der Zeit.&nbsp; </p>
    901 
    902      
    903       <p><b>Achtung:</b> diese &Auml;nderungen haben Auswirkungen auf
     412Anwachsen der Grenzschicht mit der Zeit.&nbsp; </p> <p><b>Achtung:</b>
     413diese &Auml;nderungen haben Auswirkungen auf
    904414den Prognoseverlauf.
    905 Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p>
    906 
    907       </td>
    908 
    909       <td nosave="" valign="top">init_1d_model, asselin_filter,
     415Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p> </td>
     416<td nosave="" valign="top">init_1d_model,
     417asselin_filter,
    910418diffusion_u, diffusion_v,&nbsp; <br>
    911 
    912 diffusion_pt</td>
    913 
    914     </tr>
    915 
    916     <tr nosave="" valign="top">
    917 
    918       <td nosave="">17/02/00</td>
    919 
    920       <td>MS</td>
    921 
    922       <td>2.0</td>
    923 
    924       <td>N</td>
    925 
    926       <td><b>Allgemeine Beschreibung der &Auml;nderungen:</b> <br>
    927 
    928 vollst&auml;ndige Implementierung des wolkenphysikalischen Moduls&nbsp;
    929      
    930       <p>Zur Implementierung der Wolkenphysik waren umfangreiche
     419diffusion_pt</td> </tr> <tr nosave="" valign="top"> <td nosave="">17/02/00</td>
     420<td>MS</td> <td>2.0</td> <td>N</td>
     421<td><b>Allgemeine Beschreibung der &Auml;nderungen:</b>
     422<br>
     423vollst&auml;ndige Implementierung des wolkenphysikalischen
     424Moduls&nbsp; <p>Zur Implementierung der Wolkenphysik waren
     425umfangreiche
    931426&Auml;nderungen
    932427in zahlreichen Programmteilen notwendig (Beschreibung <a href="#Cloud_physics">siehe
    933428unten</a> ). Im einzelnen wurden folgende Unprogramme
    934 ge&auml;ndert:&nbsp; <br>
    935 
    936       <b>modules</b>:&nbsp; <br>
    937 
    938 1) Bereitstellung neuer 3D-, 2D- und 1D-Felder f&uuml;r die Prognose
     429ge&auml;ndert:&nbsp; <br> <b>modules</b>:&nbsp;
     430<br>1) Bereitstellung neuer 3D-, 2D- und 1D-Felder f&uuml;r
     431die Prognose
    939432des Gesamtwassergehaltes&nbsp; <br>
    940 
    9414332) "cloud_parameters" als neues Modul mit wolkenphysikalischen
    942 Variablen&nbsp; <br>
    943 
    944       <b>parin: </b>Initialisierungsparameterliste wurde erweitert
    945 (s.u.)&nbsp; <br>
    946 
    947       <font color="#000000"><b>read_var_list, write_var_list,
     434Variablen&nbsp; <br> <b>parin: </b>Initialisierungsparameterliste
     435wurde erweitert
     436(s.u.)&nbsp; <br> <font color="#000000"><b>read_var_list,
     437write_var_list,
    948438write_3d_binary: </b>In/Output
    949439der neuen Initialisierungsparamter und Felder f&uuml;r
    950 Fortsetzungsl&auml;ufe&nbsp;</font> <br>
    951 
    952       <font color="#000000"><b>check_parameters:</b> Initialisierung
     440Fortsetzungsl&auml;ufe&nbsp;</font> <br> <font color="#000000"><b>check_parameters:</b>
     441Initialisierung
    953442des
    954 Feuchteprofils und Ausgabe von neuen Vertikalprofilen:&nbsp;</font> <br>
    955 
    956       <font color="#ff0000">vpt</font><font color="#000000">: virtuelle
     443Feuchteprofils und Ausgabe von neuen Vertikalprofilen:&nbsp;</font>
     444<br> <font color="#ff0000">vpt</font><font color="#000000">: virtuelle
    957445poteniellen
    958 Temperatur,</font> <br>
    959 
    960       <font color="#ff0000">lpt</font><font color="#000000">:
     446Temperatur,</font> <br> <font color="#ff0000">lpt</font><font color="#000000">:
    961447potentielle
    962 Fl&uuml;ssigwassertemperatur,</font> <br>
    963 
    964       <font color="#ff0000">q</font><font color="#000000">:
    965 Gesamtwassergehalt,</font> <br>
    966 
    967       <font color="#ff0000">qv</font><font color="#000000">:
     448Fl&uuml;ssigwassertemperatur,</font> <br> <font color="#ff0000">q</font><font color="#000000">:
     449Gesamtwassergehalt,</font> <br> <font color="#ff0000">qv</font><font color="#000000">:
    968450spezifische
    969 Feuchte,</font> <br>
    970 
    971       <font color="#ff0000">ql</font><font color="#000000">:
    972 Fl&uuml;ssigwassergehalt,</font> <br>
    973 
    974       <font color="#ff0000">w"vpt", w*vpt*, wvpt</font><font color="#000000">:
     451Feuchte,</font> <br> <font color="#ff0000">ql</font><font color="#000000">:
     452Fl&uuml;ssigwassergehalt,</font> <br> <font color="#ff0000">w"vpt", w*vpt*, wvpt</font><font color="#000000">:
    975453Auftriebsfluss (subskalig, aufgel&ouml;st, gesamt),</font> <br>
    976 
    977       <font color="#ff0000">w"q", w*q*, wq</font><font color="#000000">:
    978 Wasserfluss (subs., aufg., ges.),</font> <br>
    979 
    980       <font color="#ff0000">w"qv", w*qv*, wqv</font><font color="#000000">:
    981 Feuchtefluss (subs, aufg., ges.)</font> <br>
    982 
    983       <b>init_3d_model</b>: Initialisierung aller
    984 Feuchte/Wasserfelder&nbsp; <br>
    985 
    986       <b>init_1d_model</b>: Anpassung an Rechnungen mit Feuchte&nbsp; <br>
    987 
    988       <b>header</b>: Headerausgaben f&uuml;r Feuchtebehandlung und
     454<font color="#ff0000">w"q", w*q*, wq</font><font color="#000000">:
     455Wasserfluss (subs., aufg., ges.),</font> <br> <font color="#ff0000">w"qv", w*qv*, wqv</font><font color="#000000">:
     456Feuchtefluss (subs, aufg., ges.)</font> <br> <b>init_3d_model</b>:
     457Initialisierung aller
     458Feuchte/Wasserfelder&nbsp; <br> <b>init_1d_model</b>:
     459Anpassung an Rechnungen mit Feuchte&nbsp; <br> <b>header</b>:
     460Headerausgaben f&uuml;r Feuchtebehandlung und
    989461Wolkenphysik
    990462eingef&uuml;gt, au&szlig;erdem Formatnummern erweitert um Platz
    991463f&uuml;r
    992 weitere Ausgaben zu schaffen&nbsp; <br>
    993 
    994       <b>leap_frog:</b> <br>
    995 
     464weitere Ausgaben zu schaffen&nbsp; <br> <b>leap_frog:</b>
     465<br>
    9964661) alle prognostischen Gleichungen wurden in prognostic_equations
    997467ausgelagert&nbsp; <br>
    998 
    9994682) Aufrufe der neuen Unterprogramme (UP) compute_vpt,
    1000469calc_liquid_water_content&nbsp; <br>
    1001 
    1002 3) veraenderter Aufruf von diffusivities&nbsp; <br>
    1003 
    1004       <b><tt>b</tt>oundary_conds, asselin_filter, swap_timelevel,
     4703) veraenderter Aufruf von diffusivities&nbsp; <br> <b><tt>b</tt>oundary_conds,
     471asselin_filter, swap_timelevel,
    1005472flow_statistics: </b>Anpassung
    1006 an Feuchtebehandlung&nbsp; <br>
    1007 
    1008       <b>plot2d, plot3d</b>: Ausgabem&ouml;glichkeiten von q und ql <br>
    1009 
    1010       <b>buoyancy</b>: Anpassung des Autriebstermes an
     473an Feuchtebehandlung&nbsp; <br> <b>plot2d, plot3d</b>:
     474Ausgabem&ouml;glichkeiten von q und ql <br> <b>buoyancy</b>:
     475Anpassung des Autriebstermes an
    1011476Feuchtebehandlung
    1012477durch neue &Uuml;bergabeparameter: Temperatur + Nummer des
    1013478entsprechenden
    1014 mittleren Temperaturprofils&nbsp; <br>
    1015 
    1016       <b>diffusion_e</b>: Anpassung der Mischungswegberechnung an
     479mittleren Temperaturprofils&nbsp; <br> <b>diffusion_e</b>:
     480Anpassung der Mischungswegberechnung an
    1017481Feuchtebehandlung
    1018 durch Variation der &Uuml;bergabeparameter&nbsp; <br>
    1019 
    1020       <b>production_e</b>: TKE-Produktion durch Auftriebskr&auml;fte an
     482durch Variation der &Uuml;bergabeparameter&nbsp; <br> <b>production_e</b>:
     483TKE-Produktion durch Auftriebskr&auml;fte an
    1021484Feuchtebehandlung
    1022 angepasst&nbsp; <br>
    1023 
    1024       <b>diffusivities</b>: siehe diffusion_e&nbsp; <br>
    1025 
    1026       <b>prandtl-fluxes</b>: Prandtl-Schicht fuer den
     485angepasst&nbsp; <br> <b>diffusivities</b>:
     486siehe diffusion_e&nbsp; <br> <b>prandtl-fluxes</b>:
     487Prandtl-Schicht fuer den
    1027488Gesamtwassergehalt
    1028 eingef&uuml;gt&nbsp; </p>
    1029 
    1030      
    1031       <p>Zus&auml;tzlich wurden folgende Unterprogramme NEU
    1032 eingef&uuml;hrt:&nbsp; <br>
    1033 
    1034       <b>inti_cloud_physics</b>: Initialisierung wolkenphysikalischer
    1035 Parameter&nbsp; <br>
    1036 
    1037       <b>prognostic_equations</b>: Auslagerung der prognostischen
     489eingef&uuml;gt&nbsp; </p> <p>Zus&auml;tzlich
     490wurden folgende Unterprogramme NEU
     491eingef&uuml;hrt:&nbsp; <br> <b>inti_cloud_physics</b>:
     492Initialisierung wolkenphysikalischer
     493Parameter&nbsp; <br> <b>prognostic_equations</b>:
     494Auslagerung der prognostischen
    1038495Gleichungen
    1039 aus leap_frog, zus&auml;tzliche porgnostische Gleichung f&uuml;r den
    1040 Gesamtwassergehalt&nbsp; <br>
    1041 
    1042       <b>diffusion_s</b>: Berechnung der Diffusion skalarer
     496aus leap_frog, zus&auml;tzliche porgnostische Gleichung
     497f&uuml;r den
     498Gesamtwassergehalt&nbsp; <br> <b>diffusion_s</b>:
     499Berechnung der Diffusion skalarer
    1043500Gr&ouml;&szlig;en
    1044501(Temperatur und Gesamtwassergehalt), ersetzt diffusion_pt&nbsp; <br>
    1045 
    1046       <b>calc_liquid_water_content</b>: Berechnung des
    1047 Fl&uuml;ssigwassergehalts&nbsp; <br>
    1048 
    1049       <b>calc_radiation</b>: Parametrisierung langwelliger
     502<b>calc_liquid_water_content</b>: Berechnung des
     503Fl&uuml;ssigwassergehalts&nbsp; <br> <b>calc_radiation</b>:
     504Parametrisierung langwelliger
    1050505Strahlungsprozesse
    1051506&uuml;ber des Schema der effektiven Emissivit&auml;t&nbsp; <br>
    1052 
    1053       <b>calc_precipitation</b>:Parametrisierung von
     507<b>calc_precipitation</b>:Parametrisierung von
    1054508Niederschlagsprozessen
    1055 mit Hilfe eines vereinfachten Kesslerschemas&nbsp; <br>
    1056 
    1057       <b>impact_of_latent_heat</b>: Ber&uuml;cksichtigung der durch
     509mit Hilfe eines vereinfachten Kesslerschemas&nbsp; <br> <b>impact_of_latent_heat</b>:
     510Ber&uuml;cksichtigung der durch
    1058511Niederschlagsprozesse
    1059512zur&uuml;ckbleibenden latenten Waerme innerhalb eines
    1060 Gittervolumens&nbsp; <br>
    1061 
    1062       <b>compute_vpt</b>: Berechnung der virtuellen potentiellen
    1063 Temperatur&nbsp; </p>
    1064 
    1065      
    1066       <p><b>Liste der neuen Initialisierungsparameter:</b> <br>
    1067 
    1068      
    1069       <table nosave="" border="1">
    1070 
    1071         <caption>&nbsp; <br>
    1072 
    1073         </caption><tbody>
    1074 
    1075        
    1076         </tbody><tbody>
    1077 
    1078        
    1079         </tbody> <tbody>
    1080 
    1081           <tr nosave="">
    1082 
    1083             <td nosave=""><b>Parameter</b></td>
    1084 
    1085             <td nosave=""><b>Typ</b></td>
    1086 
    1087             <td nosave="" width="4%"><b>Default</b></td>
    1088 
    1089             <td nosave=""><b>Beschreibung</b></td>
    1090 
    1091           </tr>
    1092 
    1093           <tr nosave="">
    1094 
    1095             <td nosave=""><tt>moisture</tt></td>
    1096 
    1097             <td>L</td>
    1098 
    1099             <td>FALSE</td>
    1100 
    1101             <td>Ab-/Zuschalten des Gesamtwassergerhaltes als neue
    1102 progn. Variable</td>
    1103 
    1104           </tr>
    1105 
    1106           <tr>
    1107 
    1108             <td><tt>cloud_physics</tt></td>
    1109 
    1110             <td>L</td>
    1111 
    1112             <td>FALSE</td>
    1113 
    1114             <td>Ab-/Zuschalten des Kondensationsschemas</td>
    1115 
    1116           </tr>
    1117 
    1118           <tr nosave="">
    1119 
    1120             <td><tt>radiation</tt></td>
    1121 
    1122             <td>L</td>
    1123 
    1124             <td nosave="">FALSE</td>
    1125 
    1126             <td>Ab-/Zuschalten des Strahlungsschemas</td>
    1127 
    1128           </tr>
    1129 
    1130           <tr>
    1131 
    1132             <td><tt>precipitation</tt></td>
    1133 
    1134             <td>L</td>
    1135 
    1136             <td>FALSE</td>
    1137 
    1138             <td>Ab-/Zuschalten der Niderschlagsparametrisierung</td>
    1139 
    1140           </tr>
    1141 
    1142           <tr>
    1143 
    1144             <td><tt>bc_q_b</tt></td>
    1145 
    1146             <td>C</td>
    1147 
    1148             <td>'dirichlet'</td>
    1149 
    1150             <td>untere Randbedingung f&uuml;r q (siehe auch bc_pt_b)</td>
    1151 
    1152           </tr>
    1153 
    1154           <tr>
    1155 
    1156             <td><tt>bc_q_t</tt></td>
    1157 
    1158             <td>C</td>
    1159 
    1160             <td>'neumann'</td>
    1161 
    1162             <td>obere RB f&uuml;r q (siehe auch bc_pt_t)</td>
    1163 
    1164           </tr>
    1165 
    1166           <tr>
    1167 
    1168             <td><tt>q_surface</tt></td>
    1169 
    1170             <td>R</td>
    1171 
    1172             <td>0.0</td>
    1173 
    1174             <td>Feuchtewert an der Erdoberfl&auml;che</td>
    1175 
    1176           </tr>
    1177 
    1178           <tr>
    1179 
    1180             <td><tt>q_surface_initial_change</tt></td>
    1181 
    1182             <td>R</td>
    1183 
    1184             <td>0.0</td>
    1185 
    1186             <td>vgl. pt_surface_initial_change</td>
    1187 
    1188           </tr>
    1189 
    1190           <tr>
    1191 
    1192             <td><tt>q_vertical_gradient</tt></td>
    1193 
    1194             <td>R(10)</td>
    1195 
    1196             <td>0.0</td>
    1197 
    1198             <td>vgl. pt_vertical_gradient</td>
    1199 
    1200           </tr>
    1201 
    1202           <tr nosave="">
    1203 
    1204             <td nosave=""><tt>q_vertical_gradient_level</tt></td>
    1205 
    1206             <td>R(10)</td>
    1207 
    1208             <td>10000.0</td>
    1209 
    1210             <td>vgl. pt_vertical_gradient_level</td>
    1211 
    1212           </tr>
    1213 
    1214           <tr>
    1215 
    1216             <td><tt>surface_pressure</tt></td>
    1217 
    1218             <td>R</td>
    1219 
    1220             <td>1013.25</td>
    1221 
    1222             <td>Luftdruck an der Erdoberfl&auml;che</td>
    1223 
    1224           </tr>
    1225 
    1226           <tr>
    1227 
    1228             <td><tt>surface_waterflux</tt></td>
    1229 
    1230             <td>R</td>
    1231 
    1232             <td>0.0</td>
    1233 
    1234             <td>oberfl&auml;chennaher Wasser/Feuchtefluss</td>
    1235 
    1236           </tr>
    1237 
    1238        
    1239         </tbody>
    1240      
    1241       </table>
    1242 
    1243 Fortsetzungsl&auml;ufe mit Daten, die mit Modellversionen kleiner 2.0
     513Gittervolumens&nbsp; <br> <b>compute_vpt</b>:
     514Berechnung der virtuellen potentiellen
     515Temperatur&nbsp; </p> <p><b>Liste der neuen
     516Initialisierungsparameter:</b> <br> <table nosave="" border="1"> <caption>&nbsp; <br> </caption><tbody>
     517</tbody><tbody> </tbody> <tbody> <tr nosave=""> <td nosave=""><b>Parameter</b></td>
     518<td nosave=""><b>Typ</b></td> <td nosave="" width="4%"><b>Default</b></td>
     519<td nosave=""><b>Beschreibung</b></td> </tr>
     520<tr nosave=""> <td nosave=""><tt>moisture</tt></td>
     521<td>L</td> <td>FALSE</td> <td>Ab-/Zuschalten
     522des Gesamtwassergerhaltes als neue
     523progn. Variable</td> </tr> <tr> <td><tt>cloud_physics</tt></td>
     524<td>L</td> <td>FALSE</td> <td>Ab-/Zuschalten
     525des Kondensationsschemas</td> </tr> <tr nosave="">
     526<td><tt>radiation</tt></td> <td>L</td>
     527<td nosave="">FALSE</td> <td>Ab-/Zuschalten
     528des Strahlungsschemas</td> </tr> <tr> <td><tt>precipitation</tt></td>
     529<td>L</td> <td>FALSE</td> <td>Ab-/Zuschalten
     530der Niderschlagsparametrisierung</td> </tr> <tr> <td><tt>bc_q_b</tt></td>
     531<td>C</td> <td>'dirichlet'</td> <td>untere
     532Randbedingung f&uuml;r q (siehe auch bc_pt_b)</td> </tr>
     533<tr> <td><tt>bc_q_t</tt></td> <td>C</td>
     534<td>'neumann'</td> <td>obere RB f&uuml;r q
     535(siehe auch bc_pt_t)</td> </tr> <tr> <td><tt>q_surface</tt></td>
     536<td>R</td> <td>0.0</td> <td>Feuchtewert
     537an der Erdoberfl&auml;che</td> </tr> <tr> <td><tt>q_surface_initial_change</tt></td>
     538<td>R</td> <td>0.0</td> <td>vgl.
     539pt_surface_initial_change</td> </tr> <tr> <td><tt>q_vertical_gradient</tt></td>
     540<td>R(10)</td> <td>0.0</td> <td>vgl.
     541pt_vertical_gradient</td> </tr> <tr nosave="">
     542<td nosave=""><tt>q_vertical_gradient_level</tt></td>
     543<td>R(10)</td> <td>10000.0</td> <td>vgl.
     544pt_vertical_gradient_level</td> </tr> <tr> <td><tt>surface_pressure</tt></td>
     545<td>R</td> <td>1013.25</td> <td>Luftdruck
     546an der Erdoberfl&auml;che</td> </tr> <tr> <td><tt>surface_waterflux</tt></td>
     547<td>R</td> <td>0.0</td> <td>oberfl&auml;chennaher
     548Wasser/Feuchtefluss</td> </tr> </tbody> </table>
     549Fortsetzungsl&auml;ufe mit Daten, die mit Modellversionen kleiner
     5502.0
    1244551erzeugt
    1245552wurden, sind aufgrund der erweiterten Initialisierungsparameterliste
    … …  
    1247554zu den Einleseroutinen der Version 2.0. Ein Update auf Version 2.0
    1248555sollte
    1249 deshalb nach Abschluss eines kompletten Modelllaufs erfolgen.&nbsp; </p>
    1250 
    1251      
    1252       <p><b>Achtung:</b> diese &Auml;nderungen haben Auswirkungen auf
     556deshalb nach Abschluss eines kompletten Modelllaufs erfolgen.&nbsp;
     557</p> <p><b>Achtung:</b> diese
     558&Auml;nderungen haben Auswirkungen auf
    1253559den Prognoseverlauf.
    1254 Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p>
    1255 
    1256       </td>
    1257 
    1258       <td nosave="" valign="top">modules, parin, read_var_list,
     560Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p> </td>
     561<td nosave="" valign="top">modules, parin,
     562read_var_list,
    1259563check_parameters,
    1260564init_3d_model, init_1d_model, header, leap_frog. buoyancy, diffusion_e,
    … …  
    1262566asselin_filter,
    1263567swap_timelevels, flow_statistics, plot_2d, plot_3d, write_var_list,
    1264 write_3d_binary&nbsp;
    1265      
    1266       <p><b>Neu:</b> <br>
    1267 
     568write_3d_binary&nbsp; <p><b>Neu:</b> <br>
    1268569init_cloud_physics, prognostic_equations, diffusion_s,
    1269570calc_liquid_water_content,
    1270571calc_radiation, calc_precipitation, impact_of_latent_heat, comute_vpt</p>
    1271 
    1272       </td>
    1273 
    1274     </tr>
    1275 
    1276     <tr nosave="">
    1277 
    1278       <td nosave="" valign="top">18/02/00</td>
    1279 
    1280       <td nosave="" valign="top">MS</td>
    1281 
    1282       <td nosave="" valign="top">2.0</td>
    1283 
    1284       <td nosave="" valign="top">B/N</td>
    1285 
    1286       <td>Im Zuge der Umstellung auf Modellversion 2.0&nbsp; wurden
     572</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
     573Umstellung auf Modellversion 2.0&nbsp; wurden
    1287574noch kleine
    1288 &Auml;nderungen an den Unterprogrammen diffusion_e, production_e und
     575&Auml;nderungen an den Unterprogrammen diffusion_e, production_e
     576und
    1289577diffusivities
    1290578vorgenommen. In allen genannten&nbsp; <br>
    1291 
    1292579Unterprogrammen wurde bisher ein strengeres Kriterium zur Bestimmung
    1293 der Schichtungsverh&auml;ltnisse verwendet. Ein Modellvergleich zeigte
     580der Schichtungsverh&auml;ltnisse verwendet. Ein Modellvergleich
     581zeigte
    1294582jedoch, dass dadurch die Diffusion im Bereich der Inversion zu gross
    1295 wird.&nbsp;
    1296      
    1297       <p>Eine weitere Erg&auml;nzung betrifft die
     583wird.&nbsp; <p>Eine weitere Erg&auml;nzung betrifft die
    1298584Advektionsverfahren:&nbsp; <br>
    1299 
    1300 Das Bott-Chlond Advektionsverfahren ist nun auch f&uuml;r Rechnungen
    1301 mit Feuchte/Wolkenphysik verf&uuml;gbar.&nbsp; </p>
    1302 
    1303      
    1304       <p><b>Achtung:</b> diese &Auml;nderungen haben Auswirkungen auf
     585Das Bott-Chlond Advektionsverfahren ist nun auch f&uuml;r
     586Rechnungen
     587mit Feuchte/Wolkenphysik verf&uuml;gbar.&nbsp; </p> <p><b>Achtung:</b>
     588diese &Auml;nderungen haben Auswirkungen auf
    1305589den Prognoseverlauf.
    1306 Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p>
    1307 
    1308       </td>
    1309 
    1310       <td nosave="" valign="top">diffusion_e, production_e,
    1311 diffusivities, check_parameters</td>
    1312 
    1313     </tr>
    1314 
    1315     <tr nosave="" valign="top">
    1316 
    1317       <td nosave="">26/04/00</td>
    1318 
    1319       <td>SR</td>
    1320 
    1321       <td>2.0a</td>
    1322 
    1323       <td>C</td>
    1324 
    1325       <td>Vollst&auml;ndige Umstellung von vtk-Grafik-Software auf
     590Die Testergebnis-Datei wurde entsprechend ge&auml;ndert.</p> </td>
     591<td nosave="" valign="top">diffusion_e,
     592production_e,
     593diffusivities, check_parameters</td> </tr> <tr nosave="" valign="top"> <td nosave="">26/04/00</td>
     594<td>SR</td> <td>2.0a</td> <td>C</td>
     595<td>Vollst&auml;ndige Umstellung von vtk-Grafik-Software auf
    1326596dvrp-Software.
    1327597Grafik-Ausgaben im dvr-Format sind mittlerweile begrenzt nutzbar
    1328598(Isooberfl&auml;chen
    1329 sind darstellbar, siehe neue Laufparameter&nbsp; <tt>dt_dvrp, threshold</tt>),
     599sind darstellbar, siehe neue Laufparameter&nbsp; <tt>dt_dvrp,
     600threshold</tt>),
    1330601es wird aber in der Anwendung in naher Zukunft noch diverse
    1331602&Auml;nderungen
    1332603geben. Partikelausgabe vorerst nicht mehr m&ouml;glich (Verlagerung
    1333 schon).</td>
    1334 
    1335       <td>header, init_particles, init_3d_model, leap_frog, modules,
     604schon).</td> <td>header, init_particles, init_3d_model,
     605leap_frog, modules,
    1336606parin, parles,
    1337 read_var_list, write_var_list&nbsp; <br>
    1338 
    1339       <b>Gestrichen:</b> <br>
    1340 
    1341 plot_isosurface, plot_particles&nbsp;
    1342      
    1343       <p><b>Neu:</b> <br>
    1344 
    1345 init_dvrp, plot_dvrp</p>
    1346 
    1347       </td>
    1348 
    1349     </tr>
    1350 
    1351     <tr nosave="" valign="top">
    1352 
    1353       <td nosave="">26/04/00</td>
    1354 
    1355       <td>SR</td>
    1356 
    1357       <td>2.0a</td>
    1358 
    1359       <td>C</td>
    1360 
    1361       <td>Durch zus&auml;tzlichen zyklischen Rand im Bott-Chlond-Schema
     607read_var_list, write_var_list&nbsp; <br> <b>Gestrichen:</b>
     608<br>
     609plot_isosurface, plot_particles&nbsp; <p><b>Neu:</b>
     610<br>
     611init_dvrp, plot_dvrp</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">26/04/00</td>
     612<td>SR</td> <td>2.0a</td> <td>C</td>
     613<td>Durch zus&auml;tzlichen zyklischen Rand im
     614Bott-Chlond-Schema
    1362615sehr
    1363616viele SENDRECV-Aufrufe eingespart.&nbsp; <br>
    1364 
    1365 &Auml;nderung des Namens einer eingelesenen Environment-Variablen in <tt>check_open</tt>
    1366 von <tt>remote_addres</tt> nach <tt>return_addres</tt>.&nbsp; <br>
    1367 
    1368 Prozessor-Topologie kann durch Benutzer vorgegeben werden. Dazu neue
    1369 Initialisierungsparameter <tt>npex</tt> und <tt>npey</tt>. Durch
     617&Auml;nderung des Namens einer eingelesenen Environment-Variablen
     618in <tt>check_open</tt>
     619von <tt>remote_addres</tt> nach <tt>return_addres</tt>.&nbsp;
     620<br>Prozessor-Topologie kann durch Benutzer vorgegeben werden.
     621Dazu neue
     622Initialisierungsparameter <tt>npex</tt> und <tt>npey</tt>.
     623Durch
    1370624&Auml;nderungen
    1371625am Header-Format wurde Testergebnis-Datei ge&auml;ndert.</td>
    1372 
    1373       <td>advec_s_bc, check_open, header, init_pegrid, modules, parin,
     626<td>advec_s_bc, check_open, header, init_pegrid, modules, parin,
    1374627read_var_list,
    1375 write_var_list</td>
    1376 
    1377     </tr>
    1378 
    1379     <tr nosave="" valign="top">
    1380 
    1381       <td nosave="">26/04/00</td>
    1382 
    1383       <td>SR</td>
    1384 
    1385       <td>2.0a</td>
    1386 
    1387       <td>N</td>
    1388 
    1389       <td>Rechnungen mit geneigter Oberfl&auml;che erlauben jetzt die
     628write_var_list</td> </tr> <tr nosave="" valign="top"> <td nosave="">26/04/00</td>
     629<td>SR</td> <td>2.0a</td> <td>N</td>
     630<td>Rechnungen mit geneigter Oberfl&auml;che erlauben jetzt
     631die
    1390632Vorgabe
    1391633eines stabil geschichteten Temperaturprofils mit konstantem Gradienten.
    1392634Hinzuschalten von Feuchte funktioniert f&uuml;r Hangrechnungen noch
    1393 nicht.</td>
    1394 
    1395       <td>advec_s_bc, buoyancy, init_3d_model, modules,
    1396 prognostic_equations&nbsp;
    1397      
    1398       <p><b>Neu:</b> <br>
    1399 
    1400 init_slope</p>
    1401 
    1402       </td>
    1403 
    1404     </tr>
    1405 
    1406     <tr nosave="" valign="top">
    1407 
    1408       <td>13/06/00</td>
    1409 
    1410       <td>MS</td>
    1411 
    1412       <td>2.0a</td>
    1413 
    1414       <td nosave="">B</td>
    1415 
    1416       <td>Es werden nun auch die seitlichen R&auml;nder f&uuml;r ql
     635nicht.</td> <td>advec_s_bc, buoyancy, init_3d_model,
     636modules,
     637prognostic_equations&nbsp; <p><b>Neu:</b> <br>
     638init_slope</p> </td> </tr> <tr nosave="" valign="top"> <td>13/06/00</td> <td>MS</td>
     639<td>2.0a</td> <td nosave="">B</td> <td>Es
     640werden nun auch die seitlichen R&auml;nder f&uuml;r ql
    1417641gesetzt.
    1418642Ein Nichtsetzen der Randbedingungen f&uuml;hrte zu Fehlern bei der
    1419643Ausgabe
    1420 von pt</td>
    1421 
    1422       <td nosave="">calc_liquid_water_content</td>
    1423 
    1424     </tr>
    1425 
    1426     <tr nosave="" valign="top">
    1427 
    1428       <td nosave="">03/07/00</td>
    1429 
    1430       <td>SR</td>
    1431 
    1432       <td>2.0b</td>
    1433 
    1434       <td>C</td>
    1435 
    1436       <td>F&uuml;r eine Reihe von&nbsp; Unterprogrammen, die innerhalb
     644von pt</td> <td nosave="">calc_liquid_water_content</td>
     645</tr> <tr nosave="" valign="top"> <td nosave="">03/07/00</td> <td>SR</td> <td>2.0b</td>
     646<td>C</td> <td>F&uuml;r eine Reihe von&nbsp;
     647Unterprogrammen, die innerhalb
    1437648von <tt>prognostic_equation</tt>
    1438 aufgerufen werden und an die Pointer-Variablen &uuml;bergeben werden,
     649aufgerufen werden und an die Pointer-Variablen &uuml;bergeben
     650werden,
    1439651sind
    1440652jetzt explizite Interfaces vereinbart (neues Modul <tt>pointer_interfaces</tt>).
    1441653Auch im Vereinbarungsteil der entsprechenden Unterprogramme sind diese
    1442 &Uuml;bergabeparameter jetzt aus Konsistenzgr&uuml;nden (und weil es
     654&Uuml;bergabeparameter jetzt aus Konsistenzgr&uuml;nden (und
     655weil es
    1443656sonst
    1444657Laufzeitfehler gibt) als Pointer-Variablen deklariert. Mit dieser
    1445658&Auml;nderung
    1446 ist der gro&szlig;e Speicher- und CPU-Zeit-Bedarf beim &Uuml;bersetzen
    1447 von prognostic_equations wieder auf ein ertr&auml;gliches Ma&szlig;
     659ist der gro&szlig;e Speicher- und CPU-Zeit-Bedarf beim
     660&Uuml;bersetzen
     661von prognostic_equations wieder auf ein ertr&auml;gliches
     662Ma&szlig;
    1448663reduziert.&nbsp; <br>
    1449 
    1450664Im Rahmen dieser &Auml;nderungen wurde auch an diffusion_e ein
    1451665Hilfsfeld
    1452666weniger &uuml;bergeben.&nbsp; <br>
    1453 
    1454 Aus nicht vollst&auml;ndig gek&auml;rten Gr&uuml;nden haben sich die
    1455 Zahlen in der Testergebnis-Datei minimal ge&auml;ndert (und zwar die
     667Aus nicht vollst&auml;ndig gek&auml;rten Gr&uuml;nden haben
     668sich die
     669Zahlen in der Testergebnis-Datei minimal ge&auml;ndert (und zwar
     670die
    1456671Spalte
    1457672mit der Gesamtdivergenz nach Aufruf des Druckl&ouml;sers).</td>
    1458 
    1459       <td>advec_s_bc, buoyancy, diffusion_e, diffusion_s, diffusion_u,
     673<td>advec_s_bc, buoyancy, diffusion_e, diffusion_s, diffusion_u,
    1460674diffusion_v,
    1461675diffusion_w, disturb_field, modules, production_e, prognostic_equations</td>
    1462 
    1463     </tr>
    1464 
    1465     <tr nosave="" valign="top">
    1466 
    1467       <td nosave="">04/07/00</td>
    1468 
    1469       <td>SR</td>
    1470 
    1471       <td>2.0b</td>
    1472 
    1473       <td>B</td>
    1474 
    1475       <td>Diriclet-Randbedingungen f&uuml;r Temperatur und
     676</tr> <tr nosave="" valign="top"> <td nosave="">04/07/00</td> <td>SR</td> <td>2.0b</td>
     677<td>B</td> <td>Diriclet-Randbedingungen f&uuml;r
     678Temperatur und
    1476679Fl&uuml;ssigwassergehalt
    1477 werden gesetzt. Dies w&auml;re bereits nach Einf&uuml;hrung der Pointer
     680werden gesetzt. Dies w&auml;re bereits nach Einf&uuml;hrung der
     681Pointer
    1478682zwingend notwendig gewesen. Rechnungen mit vorgegebener
    1479683Oberfl&auml;chentemperatur
    1480 schlugen deshalb bislang fehl.</td>
    1481 
    1482       <td>boundary_conds</td>
    1483 
    1484     </tr>
    1485 
    1486     <tr nosave="" valign="top">
    1487 
    1488       <td nosave="">07/09/00</td>
    1489 
    1490       <td>MS</td>
    1491 
    1492       <td>2.0b</td>
    1493 
    1494       <td>B</td>
    1495 
    1496       <td>Die virtuelle potenielle Temperatur wird nun auch f&uuml;r
     684schlugen deshalb bislang fehl.</td> <td>boundary_conds</td>
     685</tr> <tr nosave="" valign="top"> <td nosave="">07/09/00</td> <td>MS</td> <td>2.0b</td>
     686<td>B</td> <td>Die virtuelle potenielle Temperatur
     687wird nun auch f&uuml;r
    1497688k=nzb und
    1498689k=nzt+1 berechnet, um die Randwerte auch f&uuml;r Ausgabezwecke
    1499 bereichtzustellen.&nbsp;</td>
    1500 
    1501       <td>compute_vpt</td>
    1502 
    1503     </tr>
    1504 
    1505     <tr nosave="" valign="top">
    1506 
    1507       <td nosave="">28/12/00</td>
    1508 
    1509       <td>SR</td>
    1510 
    1511       <td>2.1</td>
    1512 
    1513       <td>C/N</td>
    1514 
    1515       <td>PALM erlaubt jetzt den Einsatz optionaler Software-Pakete,
     690bereichtzustellen.&nbsp;</td> <td>compute_vpt</td>
     691</tr> <tr nosave="" valign="top"> <td nosave="">28/12/00</td> <td>SR</td> <td>2.1</td>
     692<td>C/N</td> <td>PALM erlaubt jetzt den Einsatz
     693optionaler Software-Pakete,
    1516694die zwar
    1517 zum Modell geh&ouml;ren, standardm&auml;&szlig;ig aber nicht mit
     695zum Modell geh&ouml;ren, standardm&auml;&szlig;ig aber
     696nicht mit
    1518697&uuml;bersetzt
    1519698werden, um so unter anderem Kompilationszeit einzusparen. Siehe neues
    1520699Kapitel
    1521 3.7 in der Modelldokumentation.&nbsp;
    1522      
    1523       <p>Einsatz der dvrp-Software wurde vollst&auml;ndig
     7003.7 in der Modelldokumentation.&nbsp; <p>Einsatz der
     701dvrp-Software wurde vollst&auml;ndig
    1524702&uuml;berarbeitet.
    1525703Sie ist nun als Software-Paket optional im Modell einsetzbar. Siehe
    1526704&uuml;berarbeitetes
    1527 Kapitel 4.5.6 in der Modelldokumentation.&nbsp; </p>
    1528 
    1529      
    1530       <p>Die Prognose der Partikelverlagerung ist ebenfalls in ein
     705Kapitel 4.5.6 in der Modelldokumentation.&nbsp; </p> <p>Die
     706Prognose der Partikelverlagerung ist ebenfalls in ein
    1531707optionales
    1532 Software-Paket ausgelagert.</p>
    1533 
    1534       </td>
    1535 
    1536       <td>advec_particles, header, init_3d_model, init_dvrp,
     708Software-Paket ausgelagert.</p> </td> <td>advec_particles,
     709header, init_3d_model, init_dvrp,
    1537710init_particles,
    1538711init_pegrid, modules, parin, parles, plot_dvrp, prognostic_equations,
    1539712read_var_list,
    1540 write_var_list&nbsp;
    1541      
    1542       <p><b>Neu:</b> <br>
    1543 
    1544 package_parin</p>
    1545 
    1546       </td>
    1547 
    1548     </tr>
    1549 
    1550     <tr nosave="" valign="top">
    1551 
    1552       <td nosave="">28/12/00</td>
    1553 
    1554       <td>SR</td>
    1555 
    1556       <td>2.1</td>
    1557 
    1558       <td>B</td>
    1559 
    1560       <td>MPI_FINALIZE ans Ende des Hauptprogramms geschoben (stand
     713write_var_list&nbsp; <p><b>Neu:</b> <br>
     714package_parin</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">28/12/00</td>
     715<td>SR</td> <td>2.1</td> <td>B</td>
     716<td>MPI_FINALIZE ans Ende des Hauptprogramms geschoben (stand
    1561717vorher vor
    1562718cpu_auswertung, wo noch ein Barrier-Aufruf steht). comm2d war zu Beginn
    1563719undefiniert und wird nun erst einmal gleich MPI_COMM_WORLD gesetzt.</td>
    1564 
    1565       <td>parles</td>
    1566 
    1567     </tr>
    1568 
    1569     <tr nosave="" valign="top">
    1570 
    1571       <td nosave="">02/01/01</td>
    1572 
    1573       <td>SR</td>
    1574 
    1575       <td>2.1a</td>
    1576 
    1577       <td>C</td>
    1578 
    1579       <td>Offene Dateien werden sobald m&ouml;glich geschlossen.
     720<td>parles</td> </tr> <tr nosave="" valign="top"> <td nosave="">02/01/01</td>
     721<td>SR</td> <td>2.1a</td> <td>C</td>
     722<td>Offene Dateien werden sobald m&ouml;glich geschlossen.
    1580723Wiederer&ouml;ffnung
    1581724bestimmter Dateien mit POSITION='APPEND' m&ouml;glich. In diesem
    … …  
    1583726wurde das Unterprogramm close_files in close_file umbenannt und hat nun
    15847271 Argument.&nbsp; <br>
    1585 
    1586728Anpassung der Diffusionsparametrisierung im 1D-Modell an das 3D-Modell.</td>
    1587 
    1588       <td>advec_particles, check_cpu_time, check_open, cpu_auswertung,
     729<td>advec_particles, check_cpu_time, check_open, cpu_auswertung,
    1589730init_1d_model,
    1590731init_3d_model, init_particles, modules.f90, parin, parles, plot_2d,
    1591 write_3d_binary&nbsp;
    1592      
    1593       <p><b>Neu:</b> <br>
    1594 
    1595 close_file&nbsp; </p>
    1596 
    1597      
    1598       <p><b>Eliminiert:</b> <br>
    1599 
    1600 close_files</p>
    1601 
    1602       </td>
    1603 
    1604     </tr>
    1605 
    1606     <tr nosave="" valign="top">
    1607 
    1608       <td nosave="">02/01/01</td>
    1609 
    1610       <td>SR</td>
    1611 
    1612       <td>2.1a</td>
    1613 
    1614       <td>B</td>
    1615 
    1616       <td>Beseitigung kleiner Fehler.</td>
    1617 
    1618       <td>check_cpu_time, diffusion_e, diffusivities, long_filter,
    1619 production_e</td>
    1620 
    1621     </tr>
    1622 
    1623     <tr nosave="" valign="top">
    1624 
    1625       <td>05/01/01</td>
    1626 
    1627       <td>SR</td>
    1628 
    1629       <td>2.1b</td>
    1630 
    1631       <td>N</td>
    1632 
    1633       <td nosave="">Neues Software-Paket zur Berechnung von Spektren im
    1634 Ortsraum</td>
    1635 
    1636       <td>check_open, header, init_3d_model, leap_frog, modules,
     732write_3d_binary&nbsp; <p><b>Neu:</b> <br>
     733close_file&nbsp; </p> <p><b>Eliminiert:</b>
     734<br>
     735close_files</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">02/01/01</td>
     736<td>SR</td> <td>2.1a</td> <td>B</td>
     737<td>Beseitigung kleiner Fehler.</td> <td>check_cpu_time,
     738diffusion_e, diffusivities, long_filter,
     739production_e</td> </tr> <tr nosave="" valign="top"> <td>05/01/01</td> <td>SR</td>
     740<td>2.1b</td> <td>N</td> <td nosave="">Neues
     741Software-Paket zur Berechnung von Spektren im
     742Ortsraum</td> <td>check_open, header, init_3d_model,
     743leap_frog, modules,
    1637744package_parin,
    1638 parles, read_var_list, write_3d_binary, write_var_list&nbsp;
    1639      
    1640       <p><b>Neu:</b> <br>
    1641 
    1642 calc_spectra, plot_spectra</p>
    1643 
    1644       </td>
    1645 
    1646     </tr>
    1647 
    1648     <tr valign="top">
    1649 
    1650       <td>25/01/01</td>
    1651 
    1652       <td>SR</td>
    1653 
    1654       <td>2.1c</td>
    1655 
    1656       <td>C/N</td>
    1657 
    1658       <td>Druckl&ouml;ser kann jetzt die Singleton-FFT benutzen. Modul <tt>singleton</tt>
     745parles, read_var_list, write_3d_binary, write_var_list&nbsp; <p><b>Neu:</b>
     746<br>
     747calc_spectra, plot_spectra</p> </td> </tr> <tr valign="top"> <td>25/01/01</td> <td>SR</td>
     748<td>2.1c</td> <td>C/N</td> <td>Druckl&ouml;ser
     749kann jetzt die Singleton-FFT benutzen. Modul <tt>singleton</tt>
    1659750wurde deshalb von <tt>calc_spectra.f90</tt> nach <tt>modules.f90</tt>
    1660751geschoben
    1661 (neuer Initialisierungsparameter <tt>fft_method</tt>).&nbsp; <br>
    1662 
    1663 Fl&uuml;sse k&ouml;nnen jetzt bei k=1 unabh&auml;ngig von der
     752(neuer Initialisierungsparameter <tt>fft_method</tt>).&nbsp;
     753<br>Fl&uuml;sse k&ouml;nnen jetzt bei k=1
     754unabh&auml;ngig von der
    1664755Verwendung
    1665756einer Prandtl-Schicht vorgegeben werden (neuer
    1666 Initialisierungsparameter <tt>use_surface_fluxes</tt>).&nbsp; <br>
    1667 
    1668 Modul <tt>test_variables</tt> wurde aus allen Programmteilen entfernt.
    1669 Hauptprogramm wurde von parles nach <tt>palm</tt> umbenannt.&nbsp; <br>
    1670 
     757Initialisierungsparameter <tt>use_surface_fluxes</tt>).&nbsp;
     758<br>Modul <tt>test_variables</tt> wurde aus allen
     759Programmteilen entfernt.
     760Hauptprogramm wurde von parles nach <tt>palm</tt>
     761umbenannt.&nbsp; <br>
    1671762Modell kann auf DEC-Workstations eingesetzt werden (-D <tt>dec</tt>).&nbsp;
    1672       <br>
    1673 
    1674 Zus&auml;tzliche Zeitmessungen mit dvrp-Software. Schreiben von
     763<br>Zus&auml;tzliche Zeitmessungen mit dvrp-Software.
     764Schreiben von
    1675765Partikel-Informationen
    1676766ist optional (neuer Parameter <tt>write_particle_informations</tt>).</td>
    1677 
    1678       <td>advec_particles, calc_spectra, check_parameters,
     767<td>advec_particles, calc_spectra, check_parameters,
    1679768cpu_zeitmessung, diffusion_s,
    1680769header, init_3d_model, init_dvrp, init_particles, leap_frog, modules,
    1681770package_parin,
    1682771parin, poisfft, read_var_list, swap_timelevel, write_var_list&nbsp;
    1683      
    1684       <p><b>Neu:</b> <br>
    1685 
    1686 palm&nbsp; </p>
    1687 
    1688      
    1689       <p><b>Eliminiert:</b> <br>
    1690 
    1691 parles, module_test</p>
    1692 
    1693       </td>
    1694 
    1695     </tr>
    1696 
    1697     <tr valign="top">
    1698 
    1699       <td>25/01/01</td>
    1700 
    1701       <td>SR</td>
    1702 
    1703       <td>2.1c</td>
    1704 
    1705       <td>B</td>
    1706 
    1707       <td>Fehler beim &ouml;ffnen von Unit 23 beseitigt. Modul <tt>interface</tt>
     772<p><b>Neu:</b> <br>
     773palm&nbsp; </p> <p><b>Eliminiert:</b> <br>
     774parles, module_test</p> </td> </tr> <tr valign="top"> <td>25/01/01</td> <td>SR</td>
     775<td>2.1c</td> <td>B</td> <td>Fehler
     776beim &ouml;ffnen von Unit 23 beseitigt. Modul <tt>interface</tt>
    1708777fehlte in disturb_field.&nbsp; <br>
    1709 
    1710778Wertebereich von theta* in Prandtl-Fluxes eingeschr&auml;nkt, weil
    1711 sonst auf einigen Rechnern overflow droht, wenn u*=0.</td>
    1712 
    1713       <td>check_open, disturb_field, prandtl_fluxes</td>
    1714 
    1715     </tr>
    1716 
    1717     <tr valign="top">
    1718 
    1719       <td>30/01/01</td>
    1720 
    1721       <td>SR</td>
    1722 
    1723       <td>2.1d</td>
    1724 
    1725       <td>N/C</td>
    1726 
    1727       <td>Prognose eines passiven Skalars ist m&ouml;glich (anstatt
     779sonst auf einigen Rechnern overflow droht, wenn u*=0.</td> <td>check_open,
     780disturb_field, prandtl_fluxes</td> </tr> <tr valign="top"> <td>30/01/01</td> <td>SR</td>
     781<td>2.1d</td> <td>N/C</td> <td>Prognose
     782eines passiven Skalars ist m&ouml;glich (anstatt
    1728783Feuchte),
    1729784dazu neuer Initialisierungsparameter <tt>passive_scalar</tt>.&nbsp;
    1730      
    1731       <p>Falls kein Pfad f&uuml;r ftpcopy existiert, werden in <tt>check_open</tt>
    1732 die Dateinamen f&uuml;r AVS-Koordinaten- und Datendatei auf "unknown"
    1733 gesetzt.</p>
    1734 
    1735       </td>
    1736 
    1737       <td>asselin_filter, boundary_conds, check_open, check_parameters,
     785<p>Falls kein Pfad f&uuml;r ftpcopy existiert, werden in <tt>check_open</tt>
     786die Dateinamen f&uuml;r AVS-Koordinaten- und Datendatei auf
     787"unknown"
     788gesetzt.</p> </td> <td>asselin_filter,
     789boundary_conds, check_open, check_parameters,
    1738790flow_statistics,
    1739791header, init_1d_model, init_3d_model, modules, parin, plot_2d,
    … …  
    1741793prandtl_fluxes, prognostic_equations, read_var_list, swap_timelevel,
    1742794write_3d_binary,
    1743 write_var_list</td>
    1744 
    1745     </tr>
    1746 
    1747     <tr valign="top">
    1748 
    1749       <td>30/01/01</td>
    1750 
    1751       <td>SR</td>
    1752 
    1753       <td>2.1d</td>
    1754 
    1755       <td>B</td>
    1756 
    1757       <td>String-Ausgabe f&uuml;r use_surface_fluxes korrigiert.
     795write_var_list</td> </tr> <tr valign="top"> <td>30/01/01</td>
     796<td>SR</td> <td>2.1d</td> <td>B</td>
     797<td>String-Ausgabe f&uuml;r use_surface_fluxes korrigiert.
    1758798Version vom
    175979925/01/01 brach deswegen bei Fortsetzungsl&auml;ufen ab.&nbsp; <br>
    1760 
    1761 xy-Plotausgabe von q und ql korrigiert.</td>
    1762 
    1763       <td>plot_2d, write_var_list</td>
    1764 
    1765     </tr>
    1766 
    1767     <tr nosave="" valign="top">
    1768 
    1769       <td nosave="">30/03/01</td>
    1770 
    1771       <td>SR</td>
    1772 
    1773       <td>2.2</td>
    1774 
    1775       <td>N/C</td>
    1776 
    1777       <td>S&auml;mtliche 3D-Felder der Zeitebene t+dt wurden entfernt.
     800xy-Plotausgabe von q und ql korrigiert.</td> <td>plot_2d,
     801write_var_list</td> </tr> <tr nosave="" valign="top"> <td nosave="">30/03/01</td>
     802<td>SR</td> <td>2.2</td> <td>N/C</td>
     803<td>S&auml;mtliche 3D-Felder der Zeitebene t+dt wurden
     804entfernt.
    1778805Ebenso
    1779806die Arbeitsfelder work und work1. Hilfsfelder wurden soweit
    … …  
    1783810eine Reihe von &Uuml;bergabeparametern gestrichen werden (z.B. beim
    1784811Aufruf
    1785 von <tt>pres, advec_s_bc, poisfft, production_e, sor </tt>sowie den
     812von <tt>pres, advec_s_bc, poisfft, production_e, sor </tt>sowie
     813den
    1786814Spline-Unterprogrammen).
    1787815Der Long-Filter wurde in das Upstream-Spline-Verfahren integriert. Da
    1788816der
    1789817Zeitfilter jetzt direkt in der prognostischen Gleichung angewendet wird
    1790 (bisher geschah dies erst nach Aufruf des Druckl&ouml;sers), haben sich
     818(bisher geschah dies erst nach Aufruf des Druckl&ouml;sers), haben
     819sich
    1791820die Zahlen in der Testergebnis-Datei ge&auml;ndert. Die mittleren
    1792821Profile
    1793 sind aber unbeeinflusst.&nbsp;
    1794      
    1795       <p>Eine weitere kleinere &Auml;nderung der Testergebnis-Daten
     822sind aber unbeeinflusst.&nbsp; <p>Eine weitere kleinere
     823&Auml;nderung der Testergebnis-Daten
    1796824wird dadurch
    1797825verursacht, dass jetzt der Parameter <tt>adjust_mixing_length</tt>
    1798826defaultm&auml;&szlig;ig <tt>.FALSE.</tt>
    1799 ist und der Mischungsweg grunds&auml;tzlich zus&auml;tzlich auf&nbsp; <tt>0.7
     827ist und der Mischungsweg grunds&auml;tzlich zus&auml;tzlich
     828auf&nbsp; <tt>0.7
    1800829* zu</tt>&nbsp;&nbsp; begrenzt wird. Falls <tt>adjust_mixing_length=T</tt>,
    1801 wird jetzt der Mischungsweg in <tt>diffusivities</tt> analog zu <tt>diffusion_e</tt>
     830wird jetzt der Mischungsweg in <tt>diffusivities</tt>
     831analog zu <tt>diffusion_e</tt>
    1802832an allen Gitterpunkten modifiziert. <b>Achtung: </b>Diese
    1803833&Auml;nderungen
    1804 k&ouml;nnen bei anderen Simulationen t.w. erhebliche Auswirkungen auf
     834k&ouml;nnen bei anderen Simulationen t.w. erhebliche Auswirkungen
     835auf
    1805836die
    1806 oberfl&auml;chennahen Ergebnisse haben.&nbsp; </p>
    1807 
    1808      
    1809       <p><b>Kleinere &Auml;nderungen:</b> In <tt>init_cloud_physics</tt>
     837oberfl&auml;chennahen Ergebnisse haben.&nbsp; </p> <p><b>Kleinere
     838&Auml;nderungen:</b> In <tt>init_cloud_physics</tt>
    1810839wird
    1811 der Wert der Variablen <tt>surface_pressure</tt> in hPa belassen
     840der Wert der Variablen <tt>surface_pressure</tt> in hPa
     841belassen
    1812842(bisher
    1813843Umwandlung in Pa).&nbsp; <br>
    1814 
    1815844Die Namelist-Namen der Software-Pakete sind&nbsp; t.w.
    1816845ge&auml;ndert.&nbsp; <br>
    1817 
    1818 Unit 14 (bin&auml;re Ausgabe f&uuml;r Fortsetzungsl&auml;ufe) wird
     846Unit 14 (bin&auml;re Ausgabe f&uuml;r
     847Fortsetzungsl&auml;ufe) wird
    1819848jetzt im Hauptprogramm geschlossen, damit auf diese Datei noch
    1820849benutzergesteuerte
    1821850Ausgaben erfolgen k&ouml;nnen.&nbsp; <br>
    1822 
    1823851Laufparameter werden in keinem Fall mehr auf Unit 14 ausgegeben bzw.
    1824852von Unit 13 gelesen, d.h. sie gelten jetzt tats&auml;chlich nur
    1825853f&uuml;r
    1826854den jeweils aktuellen Lauf.&nbsp; <br>
    1827 
    1828855Partikeladvektion funktioniert jetzt auch zusammen mit der
    1829 Galilei-Transformation.&nbsp; </p>
    1830 
    1831      
    1832       <p>Restliche deutsche Variablen-, Unterprogramm- und Modulnamen
     856Galilei-Transformation.&nbsp; </p> <p>Restliche
     857deutsche Variablen-, Unterprogramm- und Modulnamen
    1833858wurden
    1834859ins Englische &uuml;bersetzt. Davon sind fast alle Programmteile
    1835860betroffen
    1836 (nicht in rechter Spalte aufgef&uuml;hrt).</p>
    1837 
    1838       </td>
    1839 
    1840       <td>advec_particles, advec_s_bc, advec_s_ups, advec_u_ups,
     861(nicht in rechter Spalte aufgef&uuml;hrt).</p> </td> <td>advec_particles,
     862advec_s_bc, advec_s_ups, advec_u_ups,
    1841863advec_v_ups,
    1842864advec_w_ups, boundary_conds, calc_spectra, check_parameters,
    … …  
    1847869prognostic_equations,
    1848870read_var_list, sor, swap_timelevel, transpose_*, write_3d_binary,
    1849 write_var_list&nbsp;
    1850      
    1851       <p><b>Neu:</b> <br>
    1852 
    1853 cpu_log, cpu_statistics&nbsp; </p>
    1854 
    1855      
    1856       <p><b>Eliminiert:</b> <br>
    1857 
    1858 asselin_filter, cpu_auswertung, cpu_zeitmessung, long_filter</p>
    1859 
    1860       </td>
    1861 
    1862     </tr>
    1863 
    1864     <tr nosave="" valign="top">
    1865 
    1866       <td nosave="">12/07/01</td>
    1867 
    1868       <td>SR</td>
    1869 
    1870       <td>2.2a</td>
    1871 
    1872       <td>N/C</td>
    1873 
    1874       <td>Defaultwert der unteren Randbedingung f&uuml;r die TKE ist ab
     871write_var_list&nbsp; <p><b>Neu:</b> <br>
     872cpu_log, cpu_statistics&nbsp; </p> <p><b>Eliminiert:</b>
     873<br>
     874asselin_filter, cpu_auswertung, cpu_zeitmessung, long_filter</p> </td>
     875</tr> <tr nosave="" valign="top"> <td nosave="">12/07/01</td> <td>SR</td> <td>2.2a</td>
     876<td>N/C</td> <td>Defaultwert der unteren
     877Randbedingung f&uuml;r die TKE ist ab
    1875878sofort <tt>bc_e_b
    1876879= 'neumann'</tt>.&nbsp; <br>
    1877 
    1878880Partikelquelle ist &uuml;ber Paketparameter steuerbar.
    1879881Partikeleigenschaften
    … …  
    1881883ist
    1882884jetzt ebenfalls &uuml;ber Paketparameter steuerbar.&nbsp; <br>
    1883 
    1884885Allen Modulen (bis auf singleton) wurde eine SAVE-Anweisung
    1885886hinzugef&uuml;gt,
    1886 damit die durch sie vereinbarten Variablen w&auml;hrend der Rechnung in
    1887 keinem Fall undefiniert werden k&ouml;nnen (diese Gefahr besteht z.B.
     887damit die durch sie vereinbarten Variablen w&auml;hrend der
     888Rechnung in
     889keinem Fall undefiniert werden k&ouml;nnen (diese Gefahr besteht
     890z.B.
    1888891auf
    1889 SGI-Origin-Maschinen).</td>
    1890 
    1891       <td>advec_particles, header, init_dvrp, init_particles,
     892SGI-Origin-Maschinen).</td> <td>advec_particles, header,
     893init_dvrp, init_particles,
    1892894modules.f90, package_parin,
    1893 plot_dvrp, user_interface</td>
    1894 
    1895     </tr>
    1896 
    1897     <tr>
    1898 
    1899       <td>12/07/01</td>
    1900 
    1901       <td>SR</td>
    1902 
    1903       <td>2.2a</td>
    1904 
    1905       <td>B</td>
    1906 
    1907       <td>Verschiebung der OPEN-Anweisung f&uuml;r Unit 33
    1908 (AVS-FLD-Datei).</td>
    1909 
    1910       <td>check_open</td>
    1911 
    1912     </tr>
    1913 
    1914     <tr nosave="" valign="top">
    1915 
    1916       <td nosave="">20/07/01</td>
    1917 
    1918       <td>SR</td>
    1919 
    1920       <td>2.3</td>
    1921 
    1922       <td>N</td>
    1923 
    1924       <td>Einbau des Mehrgitterverfahrens zur L&ouml;sung der
    1925 Poisson-Gleichung.</td>
    1926 
    1927       <td>check_parameters, exchange_horiz, header, init_grid,
     895plot_dvrp, user_interface</td> </tr> <tr> <td>12/07/01</td>
     896<td>SR</td> <td>2.2a</td> <td>B</td>
     897<td>Verschiebung der OPEN-Anweisung f&uuml;r Unit 33
     898(AVS-FLD-Datei).</td> <td>check_open</td> </tr>
     899<tr nosave="" valign="top"> <td nosave="">20/07/01</td>
     900<td>SR</td> <td>2.3</td> <td>N</td>
     901<td>Einbau des Mehrgitterverfahrens zur L&ouml;sung der
     902Poisson-Gleichung.</td> <td>check_parameters,
     903exchange_horiz, header, init_grid,
    1928904init_pegrid, modules,
    1929 parin, pres, run_control&nbsp;
    1930      
    1931       <p><b>Neu:</b> <br>
    1932 
    1933 poismg</p>
    1934 
    1935       </td>
    1936 
    1937     </tr>
    1938 
    1939     <tr nosave="" valign="top">
    1940 
    1941       <td nosave="">21/08/01</td>
    1942 
    1943       <td>SR</td>
    1944 
    1945       <td>2.3a</td>
    1946 
    1947       <td>N/C</td>
    1948 
    1949       <td>Erg&auml;nzung der dvrp-Software: Partikel k&ouml;nnen mit
     905parin, pres, run_control&nbsp; <p><b>Neu:</b> <br>
     906poismg</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">21/08/01</td>
     907<td>SR</td> <td>2.3a</td> <td>N/C</td>
     908<td>Erg&auml;nzung der dvrp-Software: Partikel
     909k&ouml;nnen mit
    1950910Schw&auml;nzen
    1951911versehen werden. Die Ausgabe der dvrp-Plotdaten durch einen separaten
    1952912PE
    1953 ist m&ouml;glich (mrun-Option "<tt>-p dvrp_graphics+1PE</tt>"). Der
     913ist m&ouml;glich (mrun-Option "<tt>-p dvrp_graphics+1PE</tt>").
     914Der
    1954915Kommunikator <tt>MPI_COMM_WORLD</tt>&nbsp;
    1955 wurde deshalb durch&nbsp; <tt>comm_palm</tt>&nbsp; ersetzt.&nbsp;
    1956      
    1957       <p>Reduzierung des Mischungsweges im Wandbereich kann wahlweise
     916wurde deshalb durch&nbsp; <tt>comm_palm</tt>&nbsp;
     917ersetzt.&nbsp; <p>Reduzierung des Mischungsweges im
     918Wandbereich kann wahlweise
    1958919abgeschaltet
    1959920werden. F&uuml;r km und kh wird jetzt eine Neumann-Randbedingung am
    1960921unteren
    1961922Rand verwendet. Die TKE-Energieproduktionsberechnung durch Scherung des
    1962 Grundstroms am unteren Rand wurde verbessert.&nbsp; </p>
    1963 
    1964      
    1965       <p>Generelle Verwendung der bodennahen vertikalen
     923Grundstroms am unteren Rand wurde verbessert.&nbsp; </p> <p>Generelle
     924Verwendung der bodennahen vertikalen
    1966925Impulsfl&uuml;sse in
    1967926den Diffusionstermen von u und v, immer wenn diese als Randbedingung
    1968927vorgegeben
    1969 sind (gem&auml;&szlig; <tt>use_surface_fluxes</tt>, - bisher wurde
     928sind (gem&auml;&szlig; <tt>use_surface_fluxes</tt>,
     929- bisher wurde
    1970930dies
    1971931nur bei eingeschalteter Prandtl-Schicht gemacht). Schubspannungen
    … …  
    1973933jetzt als Randbedingungen vorgegeben werden (allerdings unter
    1974934zuhilfenahme
    1975 benutzereigener Software).&nbsp; </p>
    1976 
    1977      
    1978       <p>Zus&auml;tzliche Schnittstellen f&uuml;r benutzereigene
     935benutzereigener Software).&nbsp; </p> <p>Zus&auml;tzliche
     936Schnittstellen f&uuml;r benutzereigene
    1979937Software in
    1980 allen Tendenztermen, in <tt>flow_statistics,</tt> und f&uuml;r
     938allen Tendenztermen, in <tt>flow_statistics,</tt> und
     939f&uuml;r
    1981940Partikel-
    1982941bzw. dvrp-Programmteile (Bestimmung von Partikeleigenschaften,
    1983942Festlegung
    1984 von Farbtabellen).&nbsp; </p>
    1985 
    1986      
    1987       <p><b>Achtung: </b>Diese &Auml;nderungen k&ouml;nnen bei
     943von Farbtabellen).&nbsp; </p> <p><b>Achtung: </b>Diese
     944&Auml;nderungen k&ouml;nnen bei
    1988945Simulationen mit
    1989 mittlerem Wind durch die &Auml;nderungen im bereich des unteren Randes
    1990 t.w. erhebliche Auswirkungen auf die oberfl&auml;chennahen Ergebnisse
    1991 haben.</p>
    1992 
    1993       </td>
    1994 
    1995       <td>advec_particles, diffusion_e, diffusion_u, diffusion_v,
     946mittlerem Wind durch die &Auml;nderungen im bereich des unteren
     947Randes
     948t.w. erhebliche Auswirkungen auf die oberfl&auml;chennahen
     949Ergebnisse
     950haben.</p> </td> <td>advec_particles, diffusion_e,
     951diffusion_u, diffusion_v,
    1996952diffusivities,
    1997953flow_statistics, header, init_dvrp, init_particles, init_pegrid,
    … …  
    2000956prognostic_equations,
    2001957read_var_list, swap_timelevel, user_interface, write_var_list</td>
    2002 
    2003     </tr>
    2004 
    2005     <tr nosave="" valign="top">
    2006 
    2007       <td nosave="">21/08/01</td>
    2008 
    2009       <td>SR</td>
    2010 
    2011       <td>2.3a</td>
    2012 
    2013       <td>B</td>
    2014 
    2015       <td>Falsche Positionierung von MPI_ALLREDUCE in check_cpu_time
    2016 korrigiert.</td>
    2017 
    2018       <td>check_cpu_time</td>
    2019 
    2020     </tr>
    2021 
    2022     <tr nosave="" valign="top">
    2023 
    2024       <td nosave="">04/09/01</td>
    2025 
    2026       <td>SR</td>
    2027 
    2028       <td>2.3b</td>
    2029 
    2030       <td>N</td>
    2031 
    2032       <td>Zus&auml;tzliche Profilausgaben f&uuml;r
     958</tr> <tr nosave="" valign="top"> <td nosave="">21/08/01</td> <td>SR</td> <td>2.3a</td>
     959<td>B</td> <td>Falsche Positionierung von
     960MPI_ALLREDUCE in check_cpu_time
     961korrigiert.</td> <td>check_cpu_time</td> </tr>
     962<tr nosave="" valign="top"> <td nosave="">04/09/01</td>
     963<td>SR</td> <td>2.3b</td> <td>N</td>
     964<td>Zus&auml;tzliche Profilausgaben f&uuml;r
    2033965Energieproduktionsterme m&ouml;glich.
    2034 St&ouml;rdruck wird bei der FFT-Methode nicht mehr durch Aufsummieren
     966St&ouml;rdruck wird bei der FFT-Methode nicht mehr durch
     967Aufsummieren
    2035968der
    2036 Werte zu den einzelnen Zeitschritten ermittelt.</td>
    2037 
    2038       <td>check_parameters, flow_statistics, modules, pres</td>
    2039 
    2040     </tr>
    2041 
    2042     <tr nosave="" valign="top">
    2043 
    2044       <td nosave="">04/09/01</td>
    2045 
    2046       <td>SR</td>
    2047 
    2048       <td>2.3b</td>
    2049 
    2050       <td>B</td>
    2051 
    2052       <td>Austausch der Geisterr&auml;nder f&uuml;r die zeitgefilterten
     969Werte zu den einzelnen Zeitschritten ermittelt.</td> <td>check_parameters,
     970flow_statistics, modules, pres</td> </tr> <tr nosave="" valign="top"> <td nosave="">04/09/01</td>
     971<td>SR</td> <td>2.3b</td> <td>B</td>
     972<td>Austausch der Geisterr&auml;nder f&uuml;r die
     973zeitgefilterten
    2053974Felder
    2054975direkt nach Durchf&uuml;hrung der Filterung (war fehlerhaft seit
    … …  
    2056977der Zeitebene t+dt (Version 2.2) und f&uuml;hrte zu sehr kleinen
    2057978St&ouml;rungen
    2058 an den seitlichen R&auml;ndern der Teilgebiete).&nbsp;
    2059      
    2060       <p><b>Achtung:</b> Der Inhalt der Testergebnis-Datei &auml;ndert
     979an den seitlichen R&auml;ndern der Teilgebiete).&nbsp; <p><b>Achtung:</b>
     980Der Inhalt der Testergebnis-Datei &auml;ndert
    2061981sich durch
    2062 diese Fehlerkorrektur.</p>
    2063 
    2064       </td>
    2065 
    2066       <td>prognostic_equations</td>
    2067 
    2068     </tr>
    2069 
    2070     <tr nosave="" valign="top">
    2071 
    2072       <td nosave="">09/11/01</td>
    2073 
    2074       <td>SR</td>
    2075 
    2076       <td>2.3c</td>
    2077 
    2078       <td>N</td>
    2079 
    2080       <td>Farbe entlang der Partikelschw&auml;nze kann sich
     982diese Fehlerkorrektur.</p> </td> <td>prognostic_equations</td>
     983</tr> <tr nosave="" valign="top"> <td nosave="">09/11/01</td> <td>SR</td> <td>2.3c</td>
     984<td>N</td> <td>Farbe entlang der
     985Partikelschw&auml;nze kann sich
    2081986&auml;ndern. Einschalten
    2082987der Partikeladvektion bei Fortsetzungsl&auml;ufen m&ouml;glich.</td>
    2083 
    2084       <td>advec_particles, init_particles, modules, package_parin,
    2085 plot_dvrp</td>
    2086 
    2087     </tr>
    2088 
    2089     <tr nosave="" valign="top">
    2090 
    2091       <td nosave="">16/04/02</td>
    2092 
    2093       <td>SR</td>
    2094 
    2095       <td>2.3d</td>
    2096 
    2097       <td>N</td>
    2098 
    2099       <td>Vorgabe von Randbedingungen f&uuml;r Partikeladvektion
     988<td>advec_particles, init_particles, modules, package_parin,
     989plot_dvrp</td> </tr> <tr nosave="" valign="top">
     990<td nosave="">16/04/02</td> <td>SR</td>
     991<td>2.3d</td> <td>N</td> <td>Vorgabe
     992von Randbedingungen f&uuml;r Partikeladvektion
    2100993m&ouml;glich.
    2101 Partikeldaten k&ouml;nnen f&uuml;r sp&auml;tere Analysen auf Datei
     994Partikeldaten k&ouml;nnen f&uuml;r sp&auml;tere Analysen
     995auf Datei
    2102996geschrieben
    2103 werden (Unit 85). <tt>PARTICLE</tt>-Datentyp enth&auml;lt
     997werden (Unit 85). <tt>PARTICLE</tt>-Datentyp
     998enth&auml;lt
    2104999Informationen
    2105 &uuml;ber Partikelgeschwindigkeitskomponenten und Startposition.&nbsp;
    2106      
    2107       <p>Skalartransport sowie entsprechende Datenausgaben k&ouml;nnen
     1000&uuml;ber Partikelgeschwindigkeitskomponenten und
     1001Startposition.&nbsp; <p>Skalartransport sowie entsprechende
     1002Datenausgaben k&ouml;nnen
    21081003durch
    21091004eigene Parameter gesteuert werden (nicht mehr &uuml;ber die
    2110 Feuchteparameter).&nbsp; </p>
    2111 
    2112      
    2113       <p>Im Fall von pdims(1)=1 (eindimensionales virtuelles
     1005Feuchteparameter).&nbsp; </p> <p>Im Fall von
     1006pdims(1)=1 (eindimensionales virtuelles
    21141007Prozessornetz in
    21151008y-Richtung) werden die zyklischen Randbedingungen in x-Richtung durch
    21161009direktes
    2117 Umspeichern anstatt durch&nbsp; <tt>sendrecv </tt>realisiert. Ebenso
     1010Umspeichern anstatt durch&nbsp; <tt>sendrecv </tt>realisiert.
     1011Ebenso
    21181012werden
    2119 die Transponierungen xz, yz, zx&nbsp; und zy eingespart (es wird aber
     1013die Transponierungen xz, yz, zx&nbsp; und zy eingespart (es wird
     1014aber
    21201015weiter
    2121 umsortiert).&nbsp; </p>
    2122 
    2123      
    2124       <p>Im Fall von 3D-Plotausgaben Aufruf von ftpcopy-Script durch
     1016umsortiert).&nbsp; </p> <p>Im Fall von
     10173D-Plotausgaben Aufruf von ftpcopy-Script durch
    21251018batch_scp-Script
    21261019ersetzt (dient der Ermittelung von Dateizyklusnummern als Information
    21271020f&uuml;r
    2128 die AVS-fld-Datei).&nbsp; </p>
    2129 
    2130      
    2131       <p>Bei fehlerhafter Er&ouml;ffnung einer CPU_MEASURES-Datei
     1021die AVS-fld-Datei).&nbsp; </p> <p>Bei fehlerhafter
     1022Er&ouml;ffnung einer CPU_MEASURES-Datei
    21321023werden erneute
    2133 Er&ouml;ffnungsversuche durchgef&uuml;hrt.</p>
    2134 
    2135       </td>
    2136 
    2137       <td>advec_particles, check_open, check_parameters,
     1024Er&ouml;ffnungsversuche durchgef&uuml;hrt.</p> </td>
     1025<td>advec_particles, check_open, check_parameters,
    21381026exchange_horiz, flow_statistics,
    21391027header, init_particles, modules, package_parin, parin, plot_2d,
    … …  
    21411029prognostic_equations, read_var_list, transpose_xz, transpose_yz,
    21421030transpose_zx,
    2143 transpose_zy, write_var_list</td>
    2144 
    2145     </tr>
    2146 
    2147     <tr nosave="" valign="top">
    2148 
    2149       <td nosave="">02/05/02</td>
    2150 
    2151       <td>SR</td>
    2152 
    2153       <td>2.3e</td>
    2154 
    2155       <td>B</td>
    2156 
    2157       <td>Wiedereinf&uuml;hrung der 3D-Felder f&uuml;r die Zeitebene
     1031transpose_zy, write_var_list</td> </tr> <tr nosave="" valign="top"> <td nosave="">02/05/02</td>
     1032<td>SR</td> <td>2.3e</td> <td>B</td>
     1033<td>Wiedereinf&uuml;hrung der 3D-Felder f&uuml;r die
     1034Zeitebene
    21581035t+dt, die
    21591036notwendig ist, damit in den Diffusionstermen bei Leapfrog-Zeitschritten
    21601037mit der korrekten Zeitebene t-dt gearbeitet wird. Seit Version 2.2
    21611038wurde
    2162 f&auml;lschlicherweise die Zeitebene t+dt verwendet. Asselin-Filter ist
     1039f&auml;lschlicherweise die Zeitebene t+dt verwendet. Asselin-Filter
     1040ist
    21631041jetzt wieder eigenst&auml;ndiges Unterprogramm. <br>
    2164 
    21651042Die Wiedereinf&uuml;hrung dieser dritten Zeitebene ist auch
    21661043Voraussetzung
    21671044f&uuml;r die in der n&auml;chsten Version geplante skalare
    2168 Optimierung.&nbsp;
    2169      
    2170       <p>Fehler bei Berechnung von Ausgabezeitpunkten eliminiert (trat
     1045Optimierung.&nbsp; <p>Fehler bei Berechnung von
     1046Ausgabezeitpunkten eliminiert (trat
    21711047auf, wenn
    2172 bei Fortsetzungsl&auml;ufen von Ausgabeabst&auml;nden 0.0 auf von Null
    2173 verschiedene Werte gewechselt werden sollte).&nbsp; </p>
    2174 
    2175      
    2176       <p><b>Achtung:</b> Der Inhalt der Testergebnis-Datei &auml;ndert
     1048bei Fortsetzungsl&auml;ufen von Ausgabeabst&auml;nden 0.0 auf
     1049von Null
     1050verschiedene Werte gewechselt werden sollte).&nbsp; </p> <p><b>Achtung:</b>
     1051Der Inhalt der Testergebnis-Datei &auml;ndert
    21771052sich durch
    2178 diese Fehlerkorrektur.</p>
    2179 
    2180       </td>
    2181 
    2182       <td>init_3d_model, leap_frog, modules, prognostic_equations,
    2183 swap_timelevel&nbsp;
    2184      
    2185       <p><b>Neu:</b> <br>
    2186 
    2187 asselin_filter</p>
    2188 
    2189       </td>
    2190 
    2191     </tr>
    2192 
    2193     <tr nosave="" valign="top">
    2194 
    2195       <td>02/05/02</td>
    2196 
    2197       <td>SR</td>
    2198 
    2199       <td>2.3e</td>
    2200 
    2201       <td>N/C</td>
    2202 
    2203       <td>Kleinere Anpassungen an IBM-Regatta-Systeme in
    2204 check_parameters, cpu_log.&nbsp;
    2205      
    2206       <p>Modul singleton in eigenst&auml;ndige Datei
    2207 &uuml;berf&uuml;hrt.&nbsp; </p>
    2208 
    2209      
    2210       <p>Global_min_max arbeitet mit REAL*4, um Komplikationen auf
     1053diese Fehlerkorrektur.</p> </td> <td>init_3d_model,
     1054leap_frog, modules, prognostic_equations,
     1055swap_timelevel&nbsp; <p><b>Neu:</b> <br>
     1056asselin_filter</p> </td> </tr> <tr nosave="" valign="top"> <td>02/05/02</td> <td>SR</td>
     1057<td>2.3e</td> <td>N/C</td> <td>Kleinere
     1058Anpassungen an IBM-Regatta-Systeme in
     1059check_parameters, cpu_log.&nbsp; <p>Modul singleton in
     1060eigenst&auml;ndige Datei
     1061&uuml;berf&uuml;hrt.&nbsp; </p> <p>Global_min_max
     1062arbeitet mit REAL*4, um Komplikationen auf
    2211106332-bit-Rechnern
    22121064zu vermeiden (Datentyp MPI_2REAL m&uuml;sste dort sonst auf
    22131065MPI_2DOUBLE_PRECISION
    22141066ge&auml;ndert werden). <br>
    2215 
    22161067Horizontale Geschwindigkeitskomponenten f&uuml;r Partikeladvektion
    22171068werden exakt zwischen den jeweils benachbarten horizontalen
    22181069Gitterfl&auml;chen
    2219 interpoliert.</p>
    2220 
    2221       </td>
    2222 
    2223       <td nosave="">advec_particles, check_parameters, cpu_log,
     1070interpoliert.</p> </td> <td nosave="">advec_particles,
     1071check_parameters, cpu_log,
    22241072global_min_max,
    2225 modules&nbsp;
    2226      
    2227       <p><b>Neu:</b> <br>
    2228 
    2229 singleton</p>
    2230 
    2231       </td>
    2232 
    2233     </tr>
    2234 
    2235     <tr nosave="" valign="top">
    2236 
    2237       <td nosave="">11/06/02</td>
    2238 
    2239       <td>SR</td>
    2240 
    2241       <td>2.4</td>
    2242 
    2243       <td>N/C</td>
    2244 
    2245       <td>Optimierung und Anpassungen f&uuml;r einzelne Knoten der
    2246 IBM-Regatta-Systeme.
    2247      
    2248       <p><b>Skalare (Cache) Optimierung:</b> Tendenzterme werden
     1073modules&nbsp; <p><b>Neu:</b> <br>
     1074singleton</p> </td> </tr> <tr nosave="" valign="top"> <td nosave="">11/06/02</td>
     1075<td>SR</td> <td>2.4</td> <td>N/C</td>
     1076<td>Optimierung und Anpassungen f&uuml;r einzelne Knoten der
     1077IBM-Regatta-Systeme. <p><b>Skalare (Cache) Optimierung:</b>
     1078Tendenzterme werden
    22491079innerhalb einer
    22501080gro&szlig;en (i,j)-Schleife berechnet, die nun jeweils die gesamte
    … …  
    22521082Gleichung umfasst. Schleifenindices i und j werden an die
    22531083Tendenzunterprogramme
    2254 als Argumente &uuml;bergeben. Die Tendenzunterprogramme sind als Module
    2255 geschrieben, die mittels Technik der &uuml;berladenen Funktionen auch
     1084als Argumente &uuml;bergeben. Die Tendenzunterprogramme sind als
     1085Module
     1086geschrieben, die mittels Technik der &uuml;berladenen Funktionen
     1087auch
    22561088ohne
    2257 diese Indices i und j aufgerufen werden k&ouml;nnen, und dann wie in
     1089diese Indices i und j aufgerufen werden k&ouml;nnen, und dann wie
     1090in
    22581091fr&uuml;heren
    2259 Versionen funktionieren (d.h. in ihnen laufen die Schleifen &uuml;ber
     1092Versionen funktionieren (d.h. in ihnen laufen die Schleifen
     1093&uuml;ber
    22601094alle
    226110953 Dimensionen). Solche Teile der prognostischen Gleichungen, die
    … …  
    22651099mit Piascek-Williams-Advektion gearbeitet wird, werden alle
    22661100prognostischen
    2267 Gleichungen in einer einzigen (i,j)-Schleife gerechnet. </p>
    2268 
    2269      
    2270       <p><b>Kommunikationsoptimierung:</b> Zus&auml;tzliche
     1101Gleichungen in einer einzigen (i,j)-Schleife gerechnet. </p> <p><b>Kommunikationsoptimierung:</b>
     1102Zus&auml;tzliche
    22711103Implementierung einer
    227211041D-Gebietszerlegung in x-Richtung. Mit dem neuen direkten
    … …  
    22791111dieser
    228011121D-Zerlegung durch einfache zyklische Randbedingungen ersetzt. </p>
    2281 
    2282      
    2283       <p><b>Kleinere Anpassungen:</b> String-Vergleiche erfordern beim
     1113<p><b>Kleinere Anpassungen:</b> String-Vergleiche
     1114erfordern beim
    22841115IBM-Compiler
    2285 in der Regel den Einsatz der TRIM-Funktion, um &uuml;bersch&uuml;ssige
     1116in der Regel den Einsatz der TRIM-Funktion, um
     1117&uuml;bersch&uuml;ssige
    22861118Blanks am Ende des Strings abzuschneiden (sonst liefert der Vergleich
    22871119.F.). <br>
    2288 
    22891120Lokal allokierte Felder t.w. in sogenannte automatische Felder
    22901121umgewandelt
    2291 (g&uuml;nstiger, um Gefahr von eventuellen Speicherlecks zu vermeiden).
     1122(g&uuml;nstiger, um Gefahr von eventuellen Speicherlecks zu
     1123vermeiden).
    22921124Einige Feldoperationen wurden wegen schlechter Performance auf der IBM
    2293 entfernt (s. pres). </p>
    2294 
    2295      
    2296       <p><b>Achtung: </b>Die &Uuml;bersetzung des Modells erfordert
     1125entfernt (s. pres). </p> <p><b>Achtung: </b>Die
     1126&Uuml;bersetzung des Modells erfordert
    22971127aufgrund
    22981128der Vielzahl nunmehr eingesetzter Module die Verwendung des
    22991129make-Mechanismus,
    2300 um die korrekte Reihenfolge bei der &Uuml;bersetzung der Programmteile
    2301 zu gew&auml;hrleisten. Die Beschreibung dieser Abh&auml;ngigkeiten
     1130um die korrekte Reihenfolge bei der &Uuml;bersetzung der
     1131Programmteile
     1132zu gew&auml;hrleisten. Die Beschreibung dieser
     1133Abh&auml;ngigkeiten
    23021134erfolgt
    2303 in der Datei<tt> Makefile</tt>, die zusammen mit den Programmdateien
     1135in der Datei<tt> Makefile</tt>, die zusammen mit den
     1136Programmdateien
    23041137abgelegt
    2305 ist und ebenfalls unter RCS-Verwaltung steht. </p>
    2306 
    2307      
    2308       <p>Im User-Interface ist das Unterprogramm<tt> user_actions </tt>nun
     1138ist und ebenfalls unter RCS-Verwaltung steht. </p> <p>Im
     1139User-Interface ist das Unterprogramm<tt> user_actions </tt>nun
    23091140ebenfalls
    2310 als Modul geschrieben und bedient sich der Methode der &uuml;berladenen
     1141als Modul geschrieben und bedient sich der Methode der
     1142&uuml;berladenen
    23111143Funktionen. Existierende benutzereigene Software muss entsprechend
    23121144angepasst
    2313 werden.</p>
    2314 
    2315       </td>
    2316 
    2317       <td>advec_s_pw, advec_s_up, advec_u_pw, advec_u_up, advec_v_pw,
     1145werden.</p> </td> <td>advec_s_pw, advec_s_up,
     1146advec_u_pw, advec_u_up, advec_v_pw,
    23181147advec_v_up,
    23191148advec_w_pw, advec_w_up, buoyancy, calc_precipitation, calc_radiation,
    … …  
    23271156plot_3d, plot_spectra, poisfft, pres, production_e,
    23281157prognostic_equations,
    2329 user_interface,
    2330      
    2331       <p><b>Neu:</b> <br>
    2332 
    2333 fft_for_1d_decomp, Makefile, poisfft_hybrid,&nbsp;</p>
    2334 
    2335       </td>
    2336 
    2337     </tr>
    2338 
    2339     <tr nosave="" valign="top">
    2340 
    2341       <td nosave="">11/06/02</td>
    2342 
    2343       <td>SR</td>
    2344 
    2345       <td>2.4</td>
    2346 
    2347       <td>B</td>
    2348 
    2349       <td>Fehlende Variablenvereinbarung in <tt>advec_particles</tt>
    2350 erg&auml;nzt.</td>
    2351 
    2352       <td>advec_particles</td>
    2353 
    2354     </tr>
    2355 
    2356     <tr>
    2357 
    2358       <td valign="top">12/09/02</td>
    2359 
    2360       <td valign="top">SR</td>
    2361 
    2362       <td valign="top">2.4a</td>
    2363 
    2364       <td valign="top">N</td>
    2365 
    2366       <td valign="top">Partikel k&ouml;nnen mit Tr&auml;gheit versehen
     1158user_interface, <p><b>Neu:</b> <br>
     1159fft_for_1d_decomp, Makefile, poisfft_hybrid,&nbsp;</p> </td>
     1160</tr> <tr nosave="" valign="top"> <td nosave="">11/06/02</td> <td>SR</td> <td>2.4</td>
     1161<td>B</td> <td>Fehlende Variablenvereinbarung in <tt>advec_particles</tt>
     1162erg&auml;nzt.</td> <td>advec_particles</td> </tr>
     1163<tr> <td valign="top">12/09/02</td> <td valign="top">SR</td> <td valign="top">2.4a</td>
     1164<td valign="top">N</td> <td valign="top">Partikel
     1165k&ouml;nnen mit Tr&auml;gheit versehen
    23671166werden und
    23681167einen Dichteunterschied zum umgebenden Fluid haben. Zur Steuerung dient
    23691168der neue Paketparameter <tt>density_ratio</tt>.</td>
    2370 
    2371       <td valign="top">advec_particles, header, init_particles,
    2372 modules, package_parin</td>
    2373 
    2374     </tr>
    2375 
    2376     <tr>
    2377 
    2378       <td valign="top">12/09/02</td>
    2379 
    2380       <td valign="top">SR</td>
    2381 
    2382       <td valign="top">2.4a</td>
    2383 
    2384       <td valign="top">B</td>
    2385 
    2386       <td valign="top">Fehler in Berechnung der Anfangsprofile von pt
     1169<td valign="top">advec_particles, header, init_particles,
     1170modules, package_parin</td> </tr> <tr> <td valign="top">12/09/02</td> <td valign="top">SR</td>
     1171<td valign="top">2.4a</td> <td valign="top">B</td>
     1172<td valign="top">Fehler in Berechnung der Anfangsprofile
     1173von pt
    23871174und q entfernt
    23881175(obere Feldgrenze von 10 konnte in <tt>pt_vertical_gradient_level_ind</tt>
    2389 &uuml;berschritten werden). Fehler f&uuml;hrte unter Umst&auml;nden zu
    2390 "segmentation fault" bei Verwendung sehr gro&szlig;er Gitterpunktzahlen
    2391 in z-Richtung.
    2392      
    2393       <p>Fehler in Berechnung der v-Komponente am unteren Rand
     1176&uuml;berschritten werden). Fehler f&uuml;hrte unter
     1177Umst&auml;nden zu
     1178"segmentation fault" bei Verwendung sehr gro&szlig;er
     1179Gitterpunktzahlen
     1180in z-Richtung. <p>Fehler in Berechnung der v-Komponente am
     1181unteren Rand
    23941182entfernt, die
    2395 f&uuml;r den Scherungsproduktionsterm der TKE verwendet wird (Variable
    2396 v_0). F&auml;lschlicherweise wurde zur Berechnung u(k=1) statt v(k=1)
    2397 verwendet.</p>
    2398 
    2399       </td>
    2400 
    2401       <td valign="top">check_parameters, modules, production_e</td>
    2402 
    2403     </tr>
    2404 
    2405     <tr>
    2406 
    2407       <td valign="top">19/12/02</td>
    2408 
    2409       <td valign="top">SR</td>
    2410 
    2411       <td valign="top">2.5</td>
    2412 
    2413       <td valign="top">N</td>
    2414 
    2415       <td valign="top">Restart times can be set by user with new
     1183f&uuml;r den Scherungsproduktionsterm der TKE verwendet wird
     1184(Variable
     1185v_0). F&auml;lschlicherweise wurde zur Berechnung u(k=1) statt
     1186v(k=1)
     1187verwendet.</p> </td> <td valign="top">check_parameters,
     1188modules, production_e</td> </tr> <tr> <td valign="top">19/12/02</td> <td valign="top">SR</td>
     1189<td valign="top">2.5</td> <td valign="top">N</td>
     1190<td valign="top">Restart times can be set by user with new
    24161191runtime (d3par)
    2417 parameters <tt>restart_time</tt> and <tt>dt_restart</tt>. Run
     1192parameters <tt>restart_time</tt> and <tt>dt_restart</tt>.
     1193Run
    24181194description
    24191195header is written on file CONTINUE_RUN. Output of cpu statistics
    … …  
    24231199Output of warnings in the job protocol in case of negative measured
    24241200cpu-times.
    2425 Remaining cpu-time is also evaluated on IBM-Regatta.</td>
    2426 
    2427       <td valign="top">cpu_log, cpu_statistics,
     1201Remaining cpu-time is also evaluated on IBM-Regatta.</td> <td valign="top">cpu_log, cpu_statistics,
    24281202check_parameters,header, leap_frog,
    2429 local_tremain, local_tremain_ini, modules,&nbsp; palm,&nbsp;
    2430      
    2431       <p><b>new:</b> <br>
    2432 
    2433 check_for_restart </p>
    2434 
    2435      
    2436       <p><b>deleted:</b> <br>
    2437 
    2438 check_cpu_time</p>
    2439 
    2440       </td>
    2441 
    2442     </tr>
    2443 
    2444     <tr>
    2445 
    2446       <td valign="top">&nbsp;<br>
    2447 
    2448       </td>
    2449 
    2450       <td valign="top">&nbsp;<br>
    2451 
    2452       </td>
    2453 
    2454       <td valign="top">&nbsp;<br>
    2455 
    2456       </td>
    2457 
    2458       <td valign="top">C</td>
    2459 
    2460       <td valign="top">Unit 14 (BINOUT) must be opened using a special
     1203local_tremain, local_tremain_ini, modules,&nbsp; palm,&nbsp; <p><b>new:</b>
     1204<br>
     1205check_for_restart </p> <p><b>deleted:</b> <br>
     1206check_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
     120714 (BINOUT) must be opened using a special
    24611208process
    24621209id string, because on IBM, the PE rank differs between communicators
    … …  
    24661213written on file. As the consequence, these files could not be read by
    24671214restart-jobs.
    2468 Reading of array <tt>hom</tt> moved from <tt>init_3d_model </tt>to <tt>read_var_list</tt>
    2469 (binary version number incremented to 2.2).
    2470      
    2471       <p><b>Further optimization for IBM-Regatta-systems:</b> <br>
    2472 
     1215Reading of array <tt>hom</tt> moved from <tt>init_3d_model
     1216</tt>to <tt>read_var_list</tt>
     1217(binary version number incremented to 2.2). <p><b>Further
     1218optimization for IBM-Regatta-systems:</b> <br>
    24731219Additional optimization of the hybrid-solver for multinode usage
    24741220(overlapping
    2475 of communication and computation). </p>
    2476 
    2477      
    2478       <p>Further cache optimization by using strides and joining loops (<tt>hybrid_solver,
    2479 pres</tt> and <tt>timestep</tt>). Joining of MPI_ALLREDUCE calls in
    2480 timestep. </p>
    2481 
    2482      
    2483       <p>In case of 1d-decomposition along x only a part of the
     1221of communication and computation). </p> <p>Further cache
     1222optimization by using strides and joining loops (<tt>hybrid_solver,
     1223pres</tt> and <tt>timestep</tt>). Joining of
     1224MPI_ALLREDUCE calls in
     1225timestep. </p> <p>In case of 1d-decomposition along x
     1226only a part of the
    24841227integral divisor
    24851228conditions is checked, on IBM hosts a 1d-decomposition along x is the
    … …  
    248912321d-decomposition along x, the hybrid-solver does not force a
    249012331d-decomposition
    2491 any more. </p>
    2492 
    2493      
    2494       <p>Array notation changed to do-loop constructs due to better
    2495 performance. </p>
    2496 
    2497      
    2498       <p>Cyclic boundary conditions along <tt>y</tt> used instead of
     1234any more. </p> <p>Array notation changed to do-loop
     1235constructs due to better
     1236performance. </p> <p>Cyclic boundary conditions along <tt>y</tt>
     1237used instead of
    24991238sendrecv
    2500 in case of a 1d-decomposition along <tt>x</tt>. SENDRECV replaced by
     1239in case of a 1d-decomposition along <tt>x</tt>. SENDRECV
     1240replaced by
    25011241nonblocking
    25021242routines ISEND and IRECV in <tt>exchange_horiz.f90</tt>. </p>
    2503 
    2504      
    2505       <p>Speed optimization by removing MINVAL/MAXVAL calls and by
     1243<p>Speed optimization by removing MINVAL/MAXVAL calls and by
    25061244handling <br>
    2507 
    25081245the "abs" case in a different way than the min/max cases (routine <tt>global_min_max</tt>).</p>
    2509 
    2510       </td>
    2511 
    2512       <td valign="top">asselin_filter, check_open, exchange_horiz,
     1246</td> <td valign="top">asselin_filter, check_open,
     1247exchange_horiz,
    25131248global_min_max,
    25141249init_3d_model, init_pegrid, parin, poisfft_hybrid, read_var_list,
    25151250timestep,
    2516 write_3d_binary, write_var_list</td>
    2517 
    2518     </tr>
    2519 
    2520     <tr>
    2521 
    2522       <td valign="top"><br>
    2523 
    2524       </td>
    2525 
    2526       <td valign="top"><br>
    2527 
    2528       </td>
    2529 
    2530       <td valign="top"><br>
    2531 
    2532       </td>
    2533 
    2534       <td valign="top">B</td>
    2535 
    2536       <td valign="top">Correction of mixing length term (l(k)/ll(k)).
     1251write_3d_binary, write_var_list</td> </tr> <tr> <td valign="top"><br> </td> <td valign="top"><br>
     1252</td> <td valign="top"><br> </td> <td valign="top">B</td> <td valign="top">Correction
     1253of mixing length term (l(k)/ll(k)).
    25371254The condition
    25381255kh=3*km in the unstable case is now also exactly met in the wall
    25391256adjustment
    25401257region. Factor 0.7 in wall adjustment part replaced by variable <tt>wall_adjustment_factor</tt>,
    2541 which is set to 1.8 in <tt>modules.f90</tt>. The factor 0.7 was the
     1258which is set to 1.8 in <tt>modules.f90</tt>. The factor
     12590.7 was the
    25421260possible
    2543 reason for 2-delta-x-waves, which were observed since version 2.1d.
    2544      
    2545       <p>Calculation of deformation tensor re-designed (<tt>production_e</tt>).
    2546       </p>
    2547 
    2548      
    2549       <p>STOP statements replaced by call of new subroutine <tt>local_stop,
    2550       </tt>where
     1261reason for 2-delta-x-waves, which were observed since version 2.1d. <p>Calculation
     1262of deformation tensor re-designed (<tt>production_e</tt>). </p>
     1263<p>STOP statements replaced by call of new subroutine <tt>local_stop,
     1264</tt>where
    25511265MPI_FINALIZE is called before STOP in case of a parallel environment. </p>
    2552 
    2553      
    2554       <p>ISO2D parameter dp set to true for ibm hosts. </p>
    2555 
    2556      
    2557       <p>tend=p added in <tt>pres</tt> after calling sor method.</p>
    2558 
    2559       </td>
    2560 
    2561       <td valign="top">advec_s_bc, buoyancy, check_open,
     1266<p>ISO2D parameter dp set to true for ibm hosts. </p> <p>tend=p
     1267added in <tt>pres</tt> after calling sor method.</p>
     1268</td> <td valign="top">advec_s_bc, buoyancy,
     1269check_open,
    25621270check_parameters, close_file,
    25631271coriolis, diffusion_e, diffusivities, fft_for_1d_decomp,
    … …  
    25651273init_3d_model, init_dvrp, init_grid, init_particles, init_pegrid,
    25661274parin,
    2567 plot_2d, poisfft, pres, read_var_list, user_interface,&nbsp;
    2568      
    2569       <p><b>new:</b> <br>
    2570 
    2571 local_stop, production_e</p>
    2572 
    2573       </td>
    2574 
    2575     </tr>
    2576 
    2577     <tr>
    2578 
    2579       <td valign="top">03/03/03</td>
    2580 
    2581       <td valign="top">SR</td>
    2582 
    2583       <td valign="top">2.5a</td>
    2584 
    2585       <td valign="top">N</td>
    2586 
    2587       <td valign="top">Particle velocities are also stored in array
     1275plot_2d, poisfft, pres, read_var_list, user_interface,&nbsp; <p><b>new:</b>
     1276<br>
     1277local_stop, production_e</p> </td> </tr> <tr>
     1278<td valign="top">03/03/03</td> <td valign="top">SR</td>
     1279<td valign="top">2.5a</td> <td valign="top">N</td>
     1280<td valign="top">Particle velocities are also stored in
     1281array
    25881282particles in
    25891283case of zero density ratio. Steering of variables by dvrp browser
    2590 included.</td>
    2591 
    2592       <td valign="top">advec_particles, init_dvrp, modules,</td>
    2593 
    2594     </tr>
    2595 
    2596     <tr>
    2597 
    2598       <td valign="top"><br>
    2599 
    2600       </td>
    2601 
    2602       <td valign="top"><br>
    2603 
    2604       </td>
    2605 
    2606       <td valign="top"><br>
    2607 
    2608       </td>
    2609 
    2610       <td valign="top">C</td>
    2611 
    2612       <td valign="top">AVS data format changed from float to xdr_float
     1284included.</td> <td valign="top">advec_particles,
     1285init_dvrp, modules,</td> </tr> <tr> <td valign="top"><br> </td> <td valign="top"><br>
     1286</td> <td valign="top"><br> </td> <td valign="top">C</td> <td valign="top">AVS
     1287data format changed from float to xdr_float
    26131288(needed
    26141289on linux machines <br>
    2615 
    26161290due to the little/big endian problem). Updates for new version of dvrp
    2617 software (e.g. using module dvrp is now mandatory).</td>
    2618 
    2619       <td valign="top">close_file, init_dvrp, leap_frog, plot_dvrp</td>
    2620 
    2621     </tr>
    2622 
    2623     <tr>
    2624 
    2625       <td valign="top"><br>
    2626 
    2627       </td>
    2628 
    2629       <td valign="top"><br>
    2630 
    2631       </td>
    2632 
    2633       <td valign="top"><br>
    2634 
    2635       </td>
    2636 
    2637       <td valign="top">B</td>
    2638 
    2639       <td valign="top">Error in particle inertia part removed (exp_arg
     1291software (e.g. using module dvrp is now mandatory).</td> <td valign="top">close_file, init_dvrp, leap_frog, plot_dvrp</td>
     1292</tr> <tr> <td valign="top"><br> </td>
     1293<td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top">B</td>
     1294<td valign="top">Error in particle inertia part removed
     1295(exp_arg
    26401296must not
    26411297contain the timestep). <br>
    2642 
    26431298Error in calculation of the vertical flux of resolved scale energy
    26441299(profile 57) removed. Displacement for integers in mpi_particle_type
    26451300reduced
    2646 from 16 to 8 on ibm.</td>
    2647 
    2648       <td valign="top">advec_particles, flow_statistics, init_particles</td>
    2649 
    2650     </tr>
    2651 
    2652     <tr>
    2653 
    2654       <td valign="top">12/03/03</td>
    2655 
    2656       <td valign="top">SR</td>
    2657 
    2658       <td valign="top">2.6</td>
    2659 
    2660       <td valign="top">N</td>
    2661 
    2662       <td valign="top"><b>Version optimized for NEC-SX6 parallel-vector
    2663 machines.&nbsp;</b>
    2664      
    2665       <p>There are two main changes. A new vectorizable routine <tt>prognostic_equations_vec</tt>
     1301from 16 to 8 on ibm.</td> <td valign="top">advec_particles,
     1302flow_statistics, init_particles</td> </tr> <tr> <td valign="top">12/03/03</td> <td valign="top">SR</td>
     1303<td valign="top">2.6</td> <td valign="top">N</td>
     1304<td valign="top"><b>Version optimized for NEC-SX6
     1305parallel-vector
     1306machines.&nbsp;</b> <p>There are two main changes. A
     1307new vectorizable routine <tt>prognostic_equations_vec</tt>
    26661308is added, where cache optimizations are undone. The tendency
    26671309subroutines
    2668 called by <tt>prognostic_equations_vec</tt> contain the full 3d-loops
     1310called by <tt>prognostic_equations_vec</tt> contain the
     1311full 3d-loops
    26691312(compared
    26701313with the cache-optimized versions where only loops over k are carried
    26711314out).
    2672 Additionally, a new pressure solver <tt>poisfft_hybrid_vec</tt> is
     1315Additionally, a new pressure solver <tt>poisfft_hybrid_vec</tt>
     1316is
    26731317added,
    26741318which requires a 1d-domain-decomposition (like poisfft_hybrid). In this
    … …  
    26761320optionally
    26771321available by choosing <tt>fft_method </tt>= <i>'temperton-algorithm'</i>.&nbsp;
    2678       </p>
    2679 
    2680      
    2681       <p>Additional changes in <tt>flow_statistics</tt> to allow
    2682 better vectorization. </p>
    2683 
    2684      
    2685       <p>Small changes in routines <tt>diffusivities</tt> and <tt>pres</tt>
     1322</p> <p>Additional changes in <tt>flow_statistics</tt>
     1323to allow
     1324better vectorization. </p> <p>Small changes in routines <tt>diffusivities</tt>
     1325and <tt>pres</tt>
    26861326which
    26871327caused run time errors on IBM and NEC due to compiler problems. </p>
    2688 
    2689      
    2690       <p>Reading of environment variable <tt>tasks_per_node</tt> moved
     1328<p>Reading of environment variable <tt>tasks_per_node</tt>
     1329moved
    26911330from routine <tt>poisfft_hybrid</tt>
    2692 to routine <tt>parin</tt>. </p>
    2693 
    2694      
    2695       <p><b>Changes in makefile:</b> modules and user_interface now
     1331to routine <tt>parin</tt>. </p> <p><b>Changes
     1332in makefile:</b> modules and user_interface now
    26961333depend on
    26971334the f90 files, dependency of singleton added, LDFLAGS moved to the end
    2698 of PROG rule, temperton_fft added.</p>
    2699 
    2700       </td>
    2701 
    2702       <td valign="top">advec_s_pw, advec_s_up, advec_u_pw, advec_u_up,
     1335of PROG rule, temperton_fft added.</p> </td> <td valign="top">advec_s_pw, advec_s_up, advec_u_pw, advec_u_up,
    27031336advec_v_pw,
    27041337advec_v_up, advec_w_pw, advec_w_up, buoyancy, calc_precipitation,
    … …  
    27101343init_pegrid, leap_frog, local_tremain, modules, parin, poisfft,
    27111344poisfft_hybrid,
    2712 pres, production_e, prognostic_equations, user_interface
    2713      
    2714       <p><b>new:</b> <br>
    2715 
    2716 temperton_fft</p>
    2717 
    2718       </td>
    2719 
    2720     </tr>
    2721 
    2722     <tr>
    2723 
    2724       <td valign="top"><br>
    2725 
    2726       </td>
    2727 
    2728       <td valign="top"><br>
    2729 
    2730       </td>
    2731 
    2732       <td valign="top"><br>
    2733 
    2734       </td>
    2735 
    2736       <td valign="top">B</td>
    2737 
    2738       <td valign="top">tend=p added in routine <tt>pres</tt> after
     1345pres, production_e, prognostic_equations, user_interface <p><b>new:</b>
     1346<br>
     1347temperton_fft</p> </td> </tr> <tr> <td valign="top"><br> </td> <td valign="top"><br>
     1348</td> <td valign="top"><br> </td> <td valign="top">B</td> <td valign="top">tend=p
     1349added in routine <tt>pres</tt> after
    27391350calling sor
    2740 method.</td>
    2741 
    2742       <td valign="top">pres</td>
    2743 
    2744     </tr>
    2745 
    2746     <tr>
    2747 
    2748       <td valign="top">14/03/03</td>
    2749 
    2750       <td valign="top">SR</td>
    2751 
    2752       <td valign="top">2.6a</td>
    2753 
    2754       <td valign="top">N</td>
    2755 
    2756       <td valign="top">Additional vector optimization for NEC-SX6.
    2757      
    2758       <p>Optional system-specific random number generator available
     1351method.</td> <td valign="top">pres</td> </tr>
     1352<tr> <td valign="top">14/03/03</td> <td valign="top">SR</td> <td valign="top">2.6a</td>
     1353<td valign="top">N</td> <td valign="top">Additional
     1354vector optimization for NEC-SX6. <p>Optional system-specific
     1355random number generator available
    27591356(for equal
    2760 distributed numbers). </p>
    2761 
    2762      
    2763       <p>Define strings in all relevant subroutines changed from&nbsp; </p>
    2764 
    2765      
    2766       <p><tt>&nbsp;&nbsp;&nbsp;&nbsp; #if defined( define_string )</tt>
    2767       </p>
    2768 
    2769      
    2770       <p>to </p>
    2771 
    2772      
    2773       <p><tt>&nbsp;&nbsp;&nbsp;&nbsp; #if defined( __define_string )</tt>
    2774       </p>
    2775 
    2776      
    2777       <p><b>Caution: </b>The relevant subroutines are NOT listed in
     1357distributed numbers). </p> <p>Define strings in all
     1358relevant subroutines changed from&nbsp; </p> <p><tt>&nbsp;&nbsp;&nbsp;&nbsp;
     1359#if defined( define_string )</tt> </p> <p>to </p>
     1360<p><tt>&nbsp;&nbsp;&nbsp;&nbsp; #if
     1361defined( __define_string )</tt> </p> <p><b>Caution:
     1362</b>The relevant subroutines are NOT listed in
    27781363the right
    2779 column!</p>
    2780 
    2781       </td>
    2782 
    2783       <td valign="top">asselin_filter, check_parameters, diffusion_e,
     1364column!</p> </td> <td valign="top">asselin_filter,
     1365check_parameters, diffusion_e,
    27841366diffusivities,
    27851367disturb_field, global_min_max, header, local_tremain, modules, parin,
    27861368poisfft_hybrid,
    2787 pres, read_var_list, write_var_list</td>
    2788 
    2789     </tr>
    2790 
    2791     <tr>
    2792 
    2793       <td valign="top"><br>
    2794 
    2795       </td>
    2796 
    2797       <td valign="top"><br>
    2798 
    2799       </td>
    2800 
    2801       <td valign="top"><br>
    2802 
    2803       </td>
    2804 
    2805       <td valign="top">B</td>
    2806 
    2807       <td valign="top">Error in particle boundary condition removed
     1369pres, read_var_list, write_var_list</td> </tr> <tr>
     1370<td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br>
     1371</td> <td valign="top">B</td> <td valign="top">Error in particle boundary condition removed
    28081372(velocity must
    2809 be inverted in case of reflection)</td>
    2810 
    2811       <td valign="top">advec_particles</td>
    2812 
    2813     </tr>
    2814 
    2815     <tr>
    2816 
    2817       <td valign="top">16/04/03</td>
    2818 
    2819       <td valign="top">SR</td>
    2820 
    2821       <td valign="top">2.6b</td>
    2822 
    2823       <td valign="top">N</td>
    2824 
    2825       <td valign="top">Time series output of Monin Obukhov length.
    2826      
    2827       <p>Temperton fft can now be used for all hosts and every domain
     1373be inverted in case of reflection)</td> <td valign="top">advec_particles</td>
     1374</tr> <tr> <td valign="top">16/04/03</td>
     1375<td valign="top">SR</td> <td valign="top">2.6b</td>
     1376<td valign="top">N</td> <td valign="top">Time
     1377series output of Monin Obukhov length. <p>Temperton fft can now
     1378be used for all hosts and every domain
    28281379decomposition.
    28291380Abort in case of Temperton fft, if number of gridpoints along x and/or
    2830 y contain illegal factors.&nbsp; </p>
    2831 
    2832      
    2833       <p>Index values for the extrema found in global_min_max are
     1381y contain illegal factors.&nbsp; </p> <p>Index values
     1382for the extrema found in global_min_max are
    28341383limited to
    28351384the range 0..nx, 0..ny (on IBM machines -1 and nx+1/ny+1 occured which
    28361385produced different RUN_CONTROL output compared to other machines). </p>
    2837 
    2838      
    2839       <p>Output format of iteration count in routine run_control
    2840 enlarged.</p>
    2841 
    2842       </td>
    2843 
    2844       <td valign="top">check_parameters, fft_for_1d_decomp,
     1386<p>Output format of iteration count in routine run_control
     1387enlarged.</p> </td> <td valign="top">check_parameters,
     1388fft_for_1d_decomp,
    28451389global_min_max, init_pegrid,
    2846 modules, plot_ts, poisfft, run_control, temperton_fft</td>
    2847 
    2848     </tr>
    2849 
    2850     <tr>
    2851 
    2852       <td valign="top"><br>
    2853 
    2854       </td>
    2855 
    2856       <td valign="top"><br>
    2857 
    2858       </td>
    2859 
    2860       <td valign="top"><br>
    2861 
    2862       </td>
    2863 
    2864       <td valign="top">B</td>
    2865 
    2866       <td valign="top">Additional checks of variables <tt>hybrid_solver</tt>
     1390modules, plot_ts, poisfft, run_control, temperton_fft</td> </tr>
     1391<tr> <td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br>
     1392</td> <td valign="top">B</td> <td valign="top">Additional checks of variables <tt>hybrid_solver</tt>
    28671393and <tt>host</tt>
    2868 (<tt>hybrid_solver</tt> must not be used for a 2d-domain-decomposition,
    2869       <tt>host</tt>
     1394(<tt>hybrid_solver</tt> must not be used for a
     13952d-domain-decomposition, <tt>host</tt>
    28701396should be set by setting environment variable <tt>localhost</tt>).
    2871      
    2872       <p>Header output for mixing length limitations revised.</p>
    2873 
    2874       </td>
    2875 
    2876       <td valign="top">check_parameters, header</td>
    2877 
    2878     </tr>
    2879 
    2880     <tr>
    2881 
    2882       <td valign="top">09/05/03</td>
    2883 
    2884       <td valign="top">SR</td>
    2885 
    2886       <td valign="top">2.7</td>
    2887 
    2888       <td valign="top">N</td>
    2889 
    2890       <td valign="top"><b>Version running on Linux Clusters using MPICH
     1397<p>Header output for mixing length limitations revised.</p>
     1398</td> <td valign="top">check_parameters, header</td>
     1399</tr> <tr> <td valign="top">09/05/03</td>
     1400<td valign="top">SR</td> <td valign="top">2.7</td>
     1401<td valign="top">N</td> <td valign="top"><b>Version
     1402running on Linux Clusters using MPICH
    28911403and Intel
    2892 FORTRAN compiler (ifc)</b>
    2893      
    2894       <p>So far, only absolutely neccessary changes have been done
     1404FORTRAN compiler (ifc)</b> <p>So far, only absolutely
     1405neccessary changes have been done
    28951406(possible
    2896 optimizations will follow in a later version): </p>
    2897 
    2898      
    2899       <p>New time measurements for Linux (ifc) environment added. </p>
    2900 
    2901      
    2902       <p>Some parameters in MPI calls had to be modified (arrays had to
     1407optimizations will follow in a later version): </p> <p>New
     1408time measurements for Linux (ifc) environment added. </p> <p>Some
     1409parameters in MPI calls had to be modified (arrays had to
    29031410be replaced
    29041411by the first element of the regarding array) in order to fulfill f90
    … …  
    29061413and rank requirements, since on the MUK-cluster a FORTRAN90-version of
    29071414MPI is used. This also required to replace "mpif.h" by using a special
    2908 module (named <tt>mpi</tt>).&nbsp; I did not find out how character
     1415module (named <tt>mpi</tt>).&nbsp; I did not find out
     1416how character
    29091417strings
    29101418can be send with MPI. Therefore, these strings are transformed to
    … …  
    29121420before they are send, and transformed back to characters on the
    29131421receiving
    2914 PE. </p>
    2915 
    2916      
    2917       <p>On the MUK-cluster, only PE0 is able to read the values of
     1422PE. </p> <p>On the MUK-cluster, only PE0 is able to read
     1423the values of
    29181424environment
    29191425variables. Therefore, these values are communicated via broadcast to
    29201426the
    2921 other PEs. </p>
    2922 
    2923      
    2924       <p>1d-decomposition is set as the default on Linux Clusters.
     1427other PEs. </p> <p>1d-decomposition is set as the default
     1428on Linux Clusters.
    29251429Character
    2926 strings have to be transformed to integer </p>
    2927 
    2928      
    2929       <p>Smaller changes: </p>
    2930 
    2931      
    2932       <p>Batch_scp paths for IBM, NEC and Linux added</p>
    2933 
    2934       </td>
    2935 
    2936       <td valign="top">check_open, cpu_log, flow_statistics,
     1430strings have to be transformed to integer </p> <p>Smaller
     1431changes: </p> <p>Batch_scp paths for IBM, NEC and Linux
     1432added</p> </td> <td valign="top">check_open,
     1433cpu_log, flow_statistics,
    29371434init_pegrid, local_getenv,
    2938 modules, palm, poisfft_hybrid</td>
    2939 
    2940     </tr>
    2941 
    2942     <tr>
    2943 
    2944       <td valign="top"><br>
    2945 
    2946       </td>
    2947 
    2948       <td valign="top"><br>
    2949 
    2950       </td>
    2951 
    2952       <td valign="top"><br>
    2953 
    2954       </td>
    2955 
    2956       <td valign="top">B</td>
    2957 
    2958       <td valign="top">Measurements on IBM are now using function <tt>irtc</tt>,
     1435modules, palm, poisfft_hybrid</td> </tr> <tr> <td valign="top"><br> </td> <td valign="top"><br>
     1436</td> <td valign="top"><br> </td> <td valign="top">B</td> <td valign="top">Measurements
     1437on IBM are now using function <tt>irtc</tt>,
    29591438which allows correct measurements for jobs running over the 24:00
    2960 timeline.</td>
    2961 
    2962       <td valign="top">cpu_log, local_tremain, local_tremain_ini</td>
    2963 
    2964     </tr>
    2965 
    2966     <tr>
    2967 
    2968       <td valign="top">01/08/03</td>
    2969 
    2970       <td valign="top">SR</td>
    2971 
    2972       <td valign="top">2.7a</td>
    2973 
    2974       <td valign="top">B</td>
    2975 
    2976       <td valign="top">Check that the number processors is also an
     1439timeline.</td> <td valign="top">cpu_log,
     1440local_tremain, local_tremain_ini</td> </tr> <tr> <td valign="top">01/08/03</td> <td valign="top">SR</td>
     1441<td valign="top">2.7a</td> <td valign="top">B</td>
     1442<td valign="top">Check that the number processors is also
     1443an
    29771444integral divisor
    2978 of the number&nbsp; of gridpoints along y in case of a 1d-decomposition
    2979 along x.
    2980      
    2981       <p>Error concerning the multinode-version of poisfft_hybrid
     1445of the number&nbsp; of gridpoints along y in case of a
     14461d-decomposition
     1447along x. <p>Error concerning the multinode-version of
     1448poisfft_hybrid
    29821449removed. It
    29831450was caused by the Linux changes of version 2.7 and led to program abort
    2984 due to MPI errors in <tt>MPI_ALLTOALL</tt>. </p>
    2985 
    2986      
    2987       <p>No abort on t3e-systems if system specific routines are used. </p>
    2988 
    2989      
    2990       <p>Array<tt> sums </tt>is initialized in<tt> init_3d_model </tt>before
    2991 the first call of<tt> pres</tt>. Call of<tt> init_cloud_physics </tt>moved
    2992 before<tt> init_particles</tt>.</p>
    2993 
    2994       </td>
    2995 
    2996       <td valign="top">fft_1dd_init, init_3d_model, init_pegrid,
    2997 poisfft_hybrid</td>
    2998 
    2999     </tr>
    3000 
    3001     <tr>
    3002 
    3003       <td valign="top"><br>
    3004 
    3005       </td>
    3006 
    3007       <td valign="top"><br>
    3008 
    3009       </td>
    3010 
    3011       <td valign="top"><br>
    3012 
    3013       </td>
    3014 
    3015       <td valign="top">N</td>
    3016 
    3017       <td valign="top">Interactive steering of dvrp-graphic features by
     1451due to MPI errors in <tt>MPI_ALLTOALL</tt>. </p> <p>No
     1452abort on t3e-systems if system specific routines are used. </p> <p>Array<tt>
     1453sums </tt>is initialized in<tt> init_3d_model </tt>before
     1454the first call of<tt> pres</tt>. Call of<tt>
     1455init_cloud_physics </tt>moved
     1456before<tt> init_particles</tt>.</p> </td> <td valign="top">fft_1dd_init, init_3d_model, init_pegrid,
     1457poisfft_hybrid</td> </tr> <tr> <td valign="top"><br>
     1458</td> <td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top">N</td>
     1459<td valign="top">Interactive steering of dvrp-graphic
     1460features by
    30181461dvrp-browser
    30191462plugin extended (position of slicers, threshold values of isosurfaces)
    30201463. New dvrp_graphics package parameter<tt> slicer_range_limits_dvrp</tt>.</td>
    3021 
    3022       <td valign="top">init_dvrp, modules, package_parin, plot_dvrp</td>
    3023 
    3024     </tr>
    3025 
    3026     <tr>
    3027 
    3028       <td valign="top">29/10/03</td>
    3029 
    3030       <td valign="top">SR</td>
    3031 
    3032       <td valign="top">2.7b</td>
    3033 
    3034       <td valign="top">N</td>
    3035 
    3036       <td valign="top">In the multigrid method, on a defined level,
     1464<td valign="top">init_dvrp, modules, package_parin,
     1465plot_dvrp</td> </tr> <tr> <td valign="top">29/10/03</td>
     1466<td valign="top">SR</td> <td valign="top">2.7b</td>
     1467<td valign="top">N</td> <td valign="top">In
     1468the multigrid method, on a defined level,
    30371469data are gathered
    30381470on PE0 and further calculations are carried out only on this PE. New<tt>
    30391471d3par </tt>parameter <tt>mg_switch_to_pe0_level</tt>.
    3040      
    3041       <p>Particle groups implemented. New data type<tt>
     1472<p>Particle groups implemented. New data type<tt>
    30421473particle_groups_type </tt>and data type<tt> particle_type </tt>modified.
    30431474Version
    30441475numbers are
    30451476output on the particle files. New<tt> particles_par </tt>parameter<tt>
    3046 diameter</tt>. Parameter name<tt> uniform_psize</tt> changed to<tt>
     1477diameter</tt>. Parameter name<tt> uniform_psize</tt>
     1478changed to<tt>
    30471479dvrp_psize</tt>.
    30481480Parameters<tt> density_ratio </tt>is now an array.</p>
    3049 
    3050       </td>
    3051 
    3052       <td valign="top">advec_particles, check_open, exchange_horiz,
     1481</td> <td valign="top">advec_particles, check_open,
     1482exchange_horiz,
    30531483header, init_particles,
    3054 init_pegrid, modules, package_parin, parin, poismg</td>
    3055 
    3056     </tr>
    3057 
    3058     <tr>
    3059 
    3060       <td valign="top"><br>
    3061 
    3062       </td>
    3063 
    3064       <td valign="top"><br>
    3065 
    3066       </td>
    3067 
    3068       <td valign="top"><br>
    3069 
    3070       </td>
    3071 
    3072       <td valign="top">C</td>
    3073 
    3074       <td valign="top">Random number generator from numerical recipes
     1484init_pegrid, modules, package_parin, parin, poismg</td> </tr>
     1485<tr> <td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br>
     1486</td> <td valign="top">C</td> <td valign="top">Random number generator from numerical recipes
    30751487is now rewritten
    30761488as a module. In restart runs the seed of this generator is set to the
    30771489last
    30781490values of the previous run in order to keep the sequence of the random
    3079 numbers. New binary version 2.2.
    3080      
    3081       <p>Buffer is flushed for file RUN_CONTROL immediately after every
     1491numbers. New binary version 2.2. <p>Buffer is flushed for file
     1492RUN_CONTROL immediately after every
    30821493output
    3083 on IBM and Linux cluster.</p>
    3084 
    3085       </td>
    3086 
    3087       <td valign="top">advec_particles, disturb_field, init_3d_model,
     1494on IBM and Linux cluster.</p> </td> <td valign="top">advec_particles,
     1495disturb_field, init_3d_model,
    30881496init_particles,
    3089 random_function, random_gauss, run_control, write_3d_binary</td>
    3090 
    3091     </tr>
    3092 
    3093     <tr>
    3094 
    3095       <td valign="top"><br>
    3096 
    3097       </td>
    3098 
    3099       <td valign="top"><br>
    3100 
    3101       </td>
    3102 
    3103       <td valign="top"><br>
    3104 
    3105       </td>
    3106 
    3107       <td valign="top">E</td>
    3108 
    3109       <td valign="top">In routine buoyance, horizontal mean temperature
     1497random_function, random_gauss, run_control, write_3d_binary</td> </tr>
     1498<tr> <td valign="top"><br> </td> <td valign="top"><br> </td> <td valign="top"><br>
     1499</td> <td valign="top">E</td> <td valign="top">In routine buoyance, horizontal mean
     1500temperature
    31101501is now
    31111502taken from array hom instead of array sums (otherwise inconsistence in
    3112 case of using more than one statistical region).
    3113      
    3114       <p>Information about the time of the last timestep change added
     1503case of using more than one statistical region). <p>Information
     1504about the time of the last timestep change added
    31151505to the
    3116 restart file. </p>
    3117 
    3118      
    3119       <p>System call of<tt> batch_scp </tt>on IBM corrected.</p>
    3120 
    3121       </td>
    3122 
    3123       <td valign="top">buoyancy, check_open, read_var_list,
    3124 write_var_list</td>
    3125 
    3126     </tr>
    3127 
    3128     <tr>
    3129 
    3130       <td style="vertical-align: top;">28/01/04</td>
    3131 
    3132       <td style="vertical-align: top;">SR</td>
    3133 
    3134       <td style="vertical-align: top;">2.8</td>
    3135 
    3136       <td style="vertical-align: top;">N</td>
    3137 
    3138       <td style="vertical-align: top;">Runge-Kutta schemes (2nd and 3rd
     1506restart file. </p> <p>System call of<tt> batch_scp </tt>on
     1507IBM corrected.</p> </td> <td valign="top">buoyancy,
     1508check_open, read_var_list,
     1509write_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
     15103rd
    31391511order)
    31401512for time integration implemented. The third order scheme is the new
    31411513default.
    31421514It allows the timestep to be 0.9*CFL, which is much larger than for the
    3143 former default leapfrog scheme.&nbsp; The intermediate steps, which are
     1515former default leapfrog scheme.&nbsp; The intermediate steps, which
     1516are
    31441517part of these schemes, are realized by an additional loop within routine<span style="font-family: monospace;">
    31451518time_integration&nbsp;</span>(currently<span style="font-family: monospace;">
    3146 leap_frog</span>, but this routine will be renamed soon). Steering
     1519leap_frog</span>, but this routine will be renamed soon).
     1520Steering
    31471521variables<span style="font-family: monospace;">
    3148 at&nbsp;</span>and<span style="font-family: monospace;"> bt&nbsp;</span>have
    3149 been replaced by array<span style="font-family: monospace;"> sct</span>.
     1522at&nbsp;</span>and<span style="font-family: monospace;">
     1523bt&nbsp;</span>have
     1524been replaced by array<span style="font-family: monospace;">
     1525sct</span>.
    31501526, which is particularly used in the prognostic equations. Values of
    31511527this
    31521528steering array are calculated within the new routine<span style="font-family: monospace;">
    3153 timestep_scheme_steering</span>.
    3154      
    3155       <p>When using Runge-Kutta schemes,&nbsp; the timestep increment
     1529timestep_scheme_steering</span>. <p>When using Runge-Kutta
     1530schemes,&nbsp; the timestep increment
    31561531is freely
    31571532allowed to adjust after each timestep (the older schemes are using some
    3158 restrictions, see routine<span style="font-family: monospace;"> timestep</span>).
    3159 Also, routine<span style="font-family: monospace;"> run_control&nbsp;</span>is
     1533restrictions, see routine<span style="font-family: monospace;">
     1534timestep</span>).
     1535Also, routine<span style="font-family: monospace;">
     1536run_control&nbsp;</span>is
    31601537not automatically called in case of timestep changes, when Runge-Kutta
    3161 schemes are switched on. </p>
    3162 
    3163      
    3164       <p>The old leapfrog scheme is still implemented and should
     1538schemes are switched on. </p> <p>The old leapfrog scheme
     1539is still implemented and should
    31651540produce the
    3166 same results as in the previous version(s)! </p>
    3167 
    3168      
    3169       <p>Depending on the user experience, further adjustments to the
     1541same results as in the previous version(s)! </p> <p>Depending
     1542on the user experience, further adjustments to the
    31701543Runge-Kutta
    31711544schemes may be necessary within the next minor versions.&nbsp; </p>
    3172 
    3173      
    3174       <p><span style="font-weight: bold;">Attention:</span> <br>
    3175 
     1545<p><span style="font-weight: bold;">Attention:</span>
     1546<br>
    31761547The content of the testresult-file (run control output) has
    31771548significantly
    3178 changed due to the new default timestep scheme!</p>
    3179 
    3180       </td>
    3181 
    3182       <td style="vertical-align: top;">check_parameters, header,
     1549changed due to the new default timestep scheme!</p> </td> <td style="vertical-align: top;">check_parameters, header,
    31831550init_3d_model,
    31841551init_rankine, leap_frog, modules, prognostic_equations, read_var_list,
    3185 swap_timelevel, timestep, write_var_list
    3186      
    3187       <p><span style="font-weight: bold;">new:</span> <br>
    3188 
    3189 timestep_scheme_steering</p>
    3190 
    3191       </td>
    3192 
    3193     </tr>
    3194 
    3195     <tr>
    3196 
    3197       <td style="vertical-align: top;"><br>
    3198 
    3199       </td>
    3200 
    3201       <td style="vertical-align: top;"><br>
    3202 
    3203       </td>
    3204 
    3205       <td style="vertical-align: top;"><br>
    3206 
    3207       </td>
    3208 
    3209       <td style="vertical-align: top;">C</td>
    3210 
    3211       <td style="vertical-align: top;">Output of particle infos in
     1552swap_timelevel, timestep, write_var_list <p><span style="font-weight: bold;">new:</span> <br>
     1553timestep_scheme_steering</p> </td> </tr> <tr>
     1554<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
    32121555subroutine<span style="font-family: monospace;">
    3213 allocate_prt_memory&nbsp;</span>on demand only.
    3214      
    3215       <p>Type<span style="font-family: monospace;"> log&nbsp;</span>(used
     1556allocate_prt_memory&nbsp;</span>on demand only. <p>Type<span style="font-family: monospace;"> log&nbsp;</span>(used
    32161557for
    32171558cpu time measurements) changed to<span style="font-family: monospace;">
    3218 logpoint&nbsp;</span>due to name conflict with FORTRAN intrinsic<span style="font-family: monospace;">
    3219 log.</span></p>
    3220 
    3221       </td>
    3222 
    3223       <td style="vertical-align: top;">advec_particles, cpu_log,&nbsp;</td>
    3224 
    3225     </tr>
    3226 
    3227     <tr>
    3228 
    3229       <td style="vertical-align: top;"><br>
    3230 
    3231       </td>
    3232 
    3233       <td style="vertical-align: top;"><br>
    3234 
    3235       </td>
    3236 
    3237       <td style="vertical-align: top;"><br>
    3238 
    3239       </td>
    3240 
    3241       <td style="vertical-align: top;">E</td>
    3242 
    3243       <td style="vertical-align: top;">In case of opening unit 80, a
     1559logpoint&nbsp;</span>due to name conflict with FORTRAN
     1560intrinsic<span style="font-family: monospace;">
     1561log.</span></p> </td> <td style="vertical-align: top;">advec_particles,
     1562cpu_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
    32441563barrier
    32451564is set only for the first call of<span style="font-family: monospace;">
    32461565check_open&nbsp;</span>(from routine<span style="font-family: monospace;">
    3247 init_particles</span>), in order to avoid the possibility of hanging
     1566init_particles</span>), in order to avoid the possibility of
     1567hanging
    32481568jobs,
    32491569which may occur if unit 80 is opened within routine<span style="font-family: monospace;">
    3250 allocate_prt_memory</span>.</td>
    3251 
    3252       <td style="vertical-align: top;">check_open</td>
    3253 
    3254     </tr>
    3255 
    3256     <tr>
    3257 
    3258       <td style="vertical-align: top;">30/01/04</td>
    3259 
    3260       <td style="vertical-align: top;">SR</td>
    3261 
    3262       <td style="vertical-align: top;">2.8a</td>
    3263 
    3264       <td style="vertical-align: top;">N</td>
    3265 
    3266       <td style="vertical-align: top;">In order to prepare the code for
     1570allocate_prt_memory</span>.</td> <td style="vertical-align: top;">check_open</td> </tr>
     1571<tr> <td style="vertical-align: top;">30/01/04</td>
     1572<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
     1573for
    32671574the simulation
    32681575of flow around buildings (to be realized in one of the next major
    … …  
    32701577the lower<span style="font-family: monospace;"> k&nbsp;</span>index<span style="font-family: monospace;">
    32711578nzb&nbsp;</span>has been replaced by a two-dimensional array<span style="font-family: monospace;">
    3272 nzb_2d&nbsp;</span>in many of the three-dimensional loops. So far, all
     1579nzb_2d&nbsp;</span>in many of the three-dimensional loops. So
     1580far, all
    32731581elements of this array are set to<span style="font-family: monospace;">
    3274 nzb</span>.
    3275      
    3276       <p>This change should not effect simulation results and cpu time
     1582nzb</span>. <p>This change should not effect simulation
     1583results and cpu time
    32771584in any
    3278 way.</p>
    3279 
    3280       </td>
    3281 
    3282       <td style="vertical-align: top;">advec_s_pw, advec_s_up,
     1585way.</p> </td> <td style="vertical-align: top;">advec_s_pw,
     1586advec_s_up,
    32831587advec_u_pw, advec_u_up,
    32841588advec_v_pw, advec_v_up, advec_w_pw, advec_w_up, asselin_filter,
    … …  
    32891593diffusivities,
    32901594impact_of_latent_heat, init_3d_model, modules, production_e,
    3291 prognostic_equations,&nbsp;</td>
    3292 
    3293     </tr>
    3294 
    3295     <tr>
    3296 
    3297       <td style="vertical-align: top;"><br>
    3298 
    3299       </td>
    3300 
    3301       <td style="vertical-align: top;"><br>
    3302 
    3303       </td>
    3304 
    3305       <td style="vertical-align: top;"><br>
    3306 
    3307       </td>
    3308 
    3309       <td style="vertical-align: top;">C</td>
    3310 
    3311       <td style="vertical-align: top;">Euler step informations are
     1595prognostic_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
    33121596removed in
    33131597the run control output in case of Runge-Kutta schemes. Also, the
    33141598timestep
    3315 increment limitation is removed for the Runge-Kutta schemes.
    3316      
    3317       <p><span style="font-weight: bold;">Attention:</span> <br>
    3318 
     1599increment limitation is removed for the Runge-Kutta schemes. <p><span style="font-weight: bold;">Attention:</span> <br>
    33191600The content of the testresult-file (run control output) has changed
    3320 due to this modification.</p>
    3321 
    3322       </td>
    3323 
    3324       <td style="vertical-align: top;">run_control, timestep</td>
    3325 
    3326     </tr>
    3327 
    3328     <tr>
    3329 
    3330       <td style="vertical-align: top;"><br>
    3331 
    3332       </td>
    3333 
    3334       <td style="vertical-align: top;"><br>
    3335 
    3336       </td>
    3337 
    3338       <td style="vertical-align: top;"><br>
    3339 
    3340       </td>
    3341 
    3342       <td style="vertical-align: top;">E</td>
    3343 
    3344       <td style="vertical-align: top;">Velocity gradients at the
     1601due to this modification.</p> </td> <td style="vertical-align: top;">run_control, timestep</td>
     1602</tr> <tr> <td style="vertical-align: top;"><br>
     1603</td> <td style="vertical-align: top;"><br> </td>
     1604<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;">E</td> <td style="vertical-align: top;">Velocity gradients at the
    33451605surface calculated
    33461606in routine production_e are now limited. In case of inhomogeneous
    33471607surface
    33481608heating small diffusivities (<span style="font-family: monospace;">km</span>)
    3349 sometimes caused very small timesteps due to this problem.</td>
    3350 
    3351       <td style="vertical-align: top;">production_e</td>
    3352 
    3353     </tr>
    3354 
    3355     <tr>
    3356 
    3357       <td style="vertical-align: top;">30/04/04<br>
    3358 
    3359       </td>
    3360 
    3361       <td style="vertical-align: top;">SR<br>
    3362 
    3363       </td>
    3364 
    3365       <td style="vertical-align: top;">2.8b<br>
    3366 
    3367       </td>
    3368 
    3369       <td style="vertical-align: top;">N<br>
    3370 
    3371       </td>
    3372 
    3373       <td style="vertical-align: top;">The number of processors along
     1609sometimes caused very small timesteps due to this problem.</td> <td style="vertical-align: top;">production_e</td> </tr>
     1610<tr> <td style="vertical-align: top;">30/04/04<br>
     1611</td> <td style="vertical-align: top;">SR<br>
     1612</td> <td style="vertical-align: top;">2.8b<br>
     1613</td> <td style="vertical-align: top;">N<br> </td>
     1614<td style="vertical-align: top;">The number of processors
     1615along
    33741616the respective directions of the virtual processor grid must not be
    33751617integral divisors of the number of gridpoints along x, y or z any more.
    … …  
    33791621Although this causes a load imbalance, only runs with very small
    33801622numbers of processors will feel a significant decrease of performance.
    3381 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
     1623In order to be able to carry out the transpositions, array<span style="font-family: monospace;"> d </span>(and also
     1624working array<span style="font-family: monospace;"> tend</span>)
     1625have the same size on
    33821626all processors. This new feature is switched on by setting the
    3383 inipar-parameter<span style="font-family: monospace;"> grid_matching </span>=
    3384       <span style="font-style: italic;">'match'</span>, which is the
    3385 default now.<br>
    3386 
    3387       <br>
    3388 
    3389 Routine<span style="font-family: monospace;"> poisfft </span>is now
     1627inipar-parameter<span style="font-family: monospace;">
     1628grid_matching </span>= <span style="font-style: italic;">'match'</span>,
     1629which is the
     1630default now.<br> <br>
     1631Routine<span style="font-family: monospace;"> poisfft </span>is
     1632now
    33901633the
    33911634default for solving the Poisson-equation for the case of 2d- as well as
    339216351d-domain-decompositions and has been changed from a subroutine to a
    33931636module. This routine now includes most of the optimization from the
    3394 (Ketelsen) routine<span style="font-family: monospace;"> poisfft_hybrid
    3395       </span>and additionally allows 1d-decompositions along y.<br>
    3396 
    3397       <span style="font-weight: bold;">ATTENTION:</span> Routine<span style="font-family: monospace;"> poisfft_hybrid </span>might still be
     1637(Ketelsen) routine<span style="font-family: monospace;">
     1638poisfft_hybrid </span>and additionally allows 1d-decompositions
     1639along y.<br> <span style="font-weight: bold;">ATTENTION:</span>
     1640Routine<span style="font-family: monospace;">
     1641poisfft_hybrid </span>might still be
    33981642faster when running PALM on more than one node of the IBM-Regatta,
    3399 although the difference is not very big. The <span style="font-family: monospace;">poisfft</span>-code for a
     1643although the difference is not very big. The <span style="font-family: monospace;">poisfft</span>-code
     1644for a
    34001645decomposition along y has still a poor performance and needs further
    3401 optimization.<br>
    3402 
    3403       <br>
    3404 
     1646optimization.<br> <br>
    34051647The spectra-package is now able to use all the available FFT-methods
    34061648(selected by inipar-parameter<span style="font-family: monospace;">
    … …  
    34081650Performance of the transpositions needed for calculating the spectra
    34091651has been improved by using new direct transpositions from z to y and
    3410 from y to x instead of two subsequent transpositions.<br>
    3411 
    3412       <br>
    3413 
    3414 Runge-Kutta scheme implemented in the 1d-version (<span style="font-family: monospace;">init_1d_model</span>). Diffusion
     1652from y to x instead of two subsequent transpositions.<br> <br>
     1653Runge-Kutta scheme implemented in the 1d-version (<span style="font-family: monospace;">init_1d_model</span>).
     1654Diffusion
    34151655quantity arrays are allocated for previous timelevels only in case of
    3416 leapfrog scheme.<br>
    3417 
    3418       <br>
    3419 
     1656leapfrog scheme.<br> <br>
    34201657This version is adapted for use on COMPAQ-DECALPHA systems (main
    34211658changes: calling of SHAPE function within subroutine arguments (e.g.<span style="font-family: monospace;"> singleton</span>)
    34221659causes compiler errors, particle data type modified for better
    34231660alignment, DATA statements from modules removed because they caused
    3424 internal compiler errors).<br>
    3425 
    3426       </td>
    3427 
    3428       <td style="vertical-align: top;">advec_s_ups, advec_u_ups,
     1661internal compiler errors).<br> </td> <td style="vertical-align: top;">advec_s_ups, advec_u_ups,
    34291662advec_v_ups, advec_w_ups, calc_spectra, check_parameters, fft_xy,
    34301663header, init_1d_model, init_3d_model, init_particles, init_pegrid,
    34311664modules, parin, plot_2d, poisfft, prandtl_fluxes, pres, read_var_list,
    34321665singleton, spline_x, spline_y, spline_z, time_integration, transpose,
    3433 write_3d_binary, write_var_list<br>
    3434 
    3435       </td>
    3436 
    3437     </tr>
    3438 
    3439     <tr>
    3440 
    3441       <td style="vertical-align: top;"><br>
    3442 
    3443       </td>
    3444 
    3445       <td style="vertical-align: top;"><br>
    3446 
    3447       </td>
    3448 
    3449       <td style="vertical-align: top;"><br>
    3450 
    3451       </td>
    3452 
    3453       <td style="vertical-align: top;">C<br>
    3454 
    3455       </td>
    3456 
    3457       <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>
    3458 
    3459       <br>
    3460 
     1666write_3d_binary, write_var_list<br> </td> </tr> <tr>
     1667<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>.
     1668Subroutine<span style="font-family: monospace;"> leap_frog
     1669</span>renamed<span style="font-family: monospace;">
     1670time_integration</span>.<br> <br>
    34611671For all transpositions, MPI_ALLTOALL is used instead of MPI_ALLTOALLV.
    3462 The names of many transposition indices have been changed.<br>
    3463 
    3464       <br>
    3465 
    3466 Inipar-parameter<span style="font-family: monospace;"> impulse_advec </span>renamed<span style="font-family: monospace;"> momentum_advec</span>.<br>
    3467 
    3468       <br>
    3469 
    3470 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>
    3471 
    3472       <br>
    3473 
    3474 All former transpose routines collected into one file.<br>
    3475 
    3476       </td>
    3477 
    3478       <td style="vertical-align: top;">check_parameters,
     1672The names of many transposition indices have been changed.<br> <br>
     1673Inipar-parameter<span style="font-family: monospace;">
     1674impulse_advec </span>renamed<span style="font-family: monospace;"> momentum_advec</span>.<br>
     1675<br>
     1676Reading of restart data is moved from<span style="font-family: monospace;"> init_3d_model </span>to
     1677new routine <span style="font-family: monospace;">read_3d_binary</span>.<br>
     1678<br>
     1679All former transpose routines collected into one file.<br> </td>
     1680<td style="vertical-align: top;">check_parameters,
    34791681flow_statistics, header, init_1d_model, init_3d_model, init_advec,
    34801682init_pegrid, palm, parin, poisfft, poisfft_hybrid, production_e,
    3481 prognostic_equations, read_var_list, sline_x, spline_y, write_var_list<span style="font-weight: bold;"><br>
    3482 
    3483       <br>
    3484 
     1683prognostic_equations, read_var_list, sline_x, spline_y, write_var_list<span style="font-weight: bold;"><br> <br>
    34851684new:</span><br>
    3486 
    3487 fft_xy, read_3d_binary, time_integration, transpose<br>
    3488 
    3489       <br>
    3490 
    3491       <span style="font-weight: bold;">deleted:</span><br>
    3492 
     1685fft_xy, read_3d_binary, time_integration, transpose<br> <br>
     1686<span style="font-weight: bold;">deleted:</span><br>
    34931687fft_for_1d_decomp, leap_frog, transpose_xy, transpose_xz, transpose_yx,
    3494 transpose_yz, transpose_zx, transpose_zy<br>
    3495 
    3496       </td>
    3497 
    3498     </tr>
    3499 
    3500     <tr>
    3501 
    3502       <td style="vertical-align: top;"><br>
    3503 
    3504       </td>
    3505 
    3506       <td style="vertical-align: top;"><br>
    3507 
    3508       </td>
    3509 
    3510       <td style="vertical-align: top;"><br>
    3511 
    3512       </td>
    3513 
    3514       <td style="vertical-align: top;">E<br>
    3515 
    3516       </td>
    3517 
    3518       <td style="vertical-align: top;">Small errors in the
     1688transpose_yz, transpose_zx, transpose_zy<br> </td> </tr>
     1689<tr> <td style="vertical-align: top;"><br> </td>
     1690<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
    35191691particle-package removed, which sometimes caused aborts of restart runs
    3520 on IBM.<br>
    3521 
    3522       <br>
    3523 
     1692on IBM.<br> <br>
    35241693Small error in calculating the time series profiles removed (array
    35251694bounds of some arrays needed for profil-output had to be increased).<br>
    3526 
    3527       <br>
    3528 
     1695<br>
    35291696Function fft (singleton method) replaced by subroutine fftn due to
    3530 problems with 64-bit mode on IBM<br>
    3531 
    3532       </td>
    3533 
    3534       <td style="vertical-align: top;">advec_particles,
    3535 check_parameters, <br>
    3536 
    3537       </td>
    3538 
    3539     </tr>
    3540 
    3541     <tr>
    3542 
    3543       <td style="vertical-align: top;">26/03/05<br>
    3544 
    3545       </td>
    3546 
    3547       <td style="vertical-align: top;">SR<br>
    3548 
    3549       </td>
    3550 
    3551       <td style="vertical-align: top;">2.9<br>
    3552 
    3553       </td>
    3554 
    3555       <td style="vertical-align: top;">N<br>
    3556 
    3557       </td>
    3558 
    3559       <td style="vertical-align: top;">Non-cyclic lateral boundary
     1697problems with 64-bit mode on IBM<br> </td> <td style="vertical-align: top;">advec_particles,
     1698check_parameters, <br> </td> </tr> <tr> <td style="vertical-align: top;">26/03/05<br> </td>
     1699<td style="vertical-align: top;">SR<br> </td>
     1700<td style="vertical-align: top;">2.9<br> </td>
     1701<td style="vertical-align: top;">N<br> </td> <td style="vertical-align: top;">Non-cyclic lateral boundary
    35601702conditions implemented.<br>
    3561 
    35621703Dirichlet/Neumann conditions at the inflow/outflow can be used either
    35631704along x or along y. Cyclic conditions have to be used along the
    … …  
    35651706upper bound nxl (nyn) of array u (v) is enlarged by one gridpoint on
    35661707the rightmost (northest) processor. These array index informations are
    3567 passed to routine<span style="font-family: monospace;"> exchange_horiz </span>and<span style="font-family: monospace;"> disturb_field </span>by two
     1708passed to routine<span style="font-family: monospace;">
     1709exchange_horiz </span>and<span style="font-family: monospace;">
     1710disturb_field </span>by two
    35681711additional arguments. Boundary conditions are set with new
    3569 inipar-parameters<span style="font-family: monospace;"> bc_lr </span>and<span style="font-family: monospace;"> bc_ns</span>. A damping layer is
    3570 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
    3571 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>).
     1712inipar-parameters<span style="font-family: monospace;">
     1713bc_lr </span>and<span style="font-family: monospace;">
     1714bc_ns</span>. A damping layer is
     1715needed 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>)
     1716and an
     1717additional disturbance is imposed near the inflow (see new parameters<span style="font-family: monospace;">&nbsp;
     1718inflow_disturbance_begin </span>and<span style="font-family: monospace;"> inflow_disturbance_end</span>).
    35721719Non-cyclic conditions require the use of the multigrid-method for
    3573 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
    3574 non-cyclic conditions are set). <br>
    3575 
    3576       <br>
    3577 
     1720solving the Poisson equation. Argument<span style="font-family: monospace;"> range </span>added
     1721to routine<span style="font-family: monospace;">
     1722boundary_conds </span>(where the
     1723non-cyclic conditions are set). <br> <br>
    35781724Minor changes:<br>
    3579 
    3580 Output of parameter<span style="font-family: monospace;"> datform </span>on
    3581 &amp;GLOBAL-Namelist (iso2d). This is set to <span style="font-style: italic;">'big_endian'</span> on IBM- and
    3582 NEC-machines.<br>
    3583 
    3584       <br>
    3585 
    3586 Number of particle groups are additionally calculated in<span style="font-family: monospace;"> header </span>(formerly unknown).<br>
    3587 
    3588       </td>
    3589 
    3590       <td style="vertical-align: top;">advec_u_pw,
     1725Output of parameter<span style="font-family: monospace;">
     1726datform </span>on
     1727&amp;GLOBAL-Namelist (iso2d). This is set to <span style="font-style: italic;">'big_endian'</span> on
     1728IBM- and
     1729NEC-machines.<br> <br>
     1730Number of particle groups are additionally calculated in<span style="font-family: monospace;"> header </span>(formerly
     1731unknown).<br> </td> <td style="vertical-align: top;">advec_u_pw,
    35911732advec_u_up, advec_v_pw, advec_v_up, boundary_conds,
    35921733calc_liquid_water_content, check_parameters, close_file, coriolis,
    … …  
    35951736init_rankine, modules, parin, poismg, pres, prognostic_equations,
    35961737read_var_list, sor, time_integration, timestep, write_var_list<br>
    3597 
    3598       </td>
    3599 
    3600     </tr>
    3601 
    3602     <tr>
    3603 
    3604       <td style="vertical-align: top;"><br>
    3605 
    3606       </td>
    3607 
    3608       <td style="vertical-align: top;"><br>
    3609 
    3610       </td>
    3611 
    3612       <td style="vertical-align: top;"><br>
    3613 
    3614       </td>
    3615 
    3616       <td style="vertical-align: top;">C<br>
    3617 
    3618       </td>
    3619 
    3620       <td style="vertical-align: top;"><span style="font-family: monospace;">pres </span>is called by default only
     1738</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
     1739by default only
    36211740at the last Runge-Kutta-substep, which spares a big amount of CPU-time
    36221741(see also new parameter<span style="font-family: monospace;">
    3623 call_psolver_at_all_substeps</span>). No pressure term in the momentum
    3624 equations in case of Runge-Kutta-schemes.<br>
    3625 
    3626       <span style="font-weight: bold;">Attention:</span> <br>
    3627 
     1742call_psolver_at_all_substeps</span>). No pressure term in the
     1743momentum
     1744equations in case of Runge-Kutta-schemes.<br> <span style="font-weight: bold;">Attention:</span> <br>
    36281745The content of the testresult-file (run control output) has changed
    3629 due to this modification.<br>
    3630 
    3631       <br>
    3632 
    3633 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>
    3634 
    3635       <br>
    3636 
    3637 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>
    3638 
    3639       </td>
    3640 
    3641       <td style="vertical-align: top;">calc_liquid_water_content,
     1746due to this modification.<br> <br>
     1747Program speedup by removing the exchange of ghost points in routines <span style="font-family: monospace;">calc_liquid_water_content</span>,
     1748<span style="font-family: monospace;">diffusivities</span>,
     1749.<br> <br>
     1750Default 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
     1751(one call of<span style="font-family: monospace;">
     1752exchange_horiz </span>spared).<br> </td> <td style="vertical-align: top;">calc_liquid_water_content,
    36421753diffusivities, modules, poismg, pres, time_integration,
    3643 timestep_scheme_steering<br>
    3644 
    3645       </td>
    3646 
    3647     </tr>
    3648 
    3649     <tr>
    3650 
    3651       <td style="vertical-align: top;"><br>
    3652 
    3653       </td>
    3654 
    3655       <td style="vertical-align: top;"><br>
    3656 
    3657       </td>
    3658 
    3659       <td style="vertical-align: top;"><br>
    3660 
    3661       </td>
    3662 
    3663       <td style="vertical-align: top;">E<br>
    3664 
    3665       </td>
    3666 
    3667       <td style="vertical-align: top;">Calculation of vertical particle
    3668 velocity (with inertia) corrected, exp_arg had a wrong sign.<br>
    3669 
    3670       <br>
    3671 
     1754timestep_scheme_steering<br> </td> </tr> <tr>
     1755<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
     1756particle
     1757velocity (with inertia) corrected, exp_arg had a wrong sign.<br> <br>
    36721758(e)**1.5 replaced by e*SQRT(e) in init_1d_model because of wrong
    36731759results on NEC machines (as a side effect, the new calculation is much
    3674 faster).<br>
    3675 
    3676       <br>
    3677 
     1760faster).<br> <br>
    36781761Two errors concerning switch to PE0 (multigrid method) removed from<span style="font-family: monospace;"> init_pegrid</span>.<br>
    3679 
    3680       <br>
    3681 
    3682 Two errors in<span style="font-family: monospace;"> plot_2d </span>removed:
     1762<br>
     1763Two errors in<span style="font-family: monospace;">
     1764plot_2d </span>removed:
    36831765local_2d is allocated with upper bound<span style="font-family: monospace;"> nzt</span> (former<span style="font-family: monospace;"> nzt+1 </span>was
    36841766wrong), additional barrier in case that PE0 gathers data from the other
    36851767PEs, this barrier had to be set at the end of the gathering because
    3686 otherwise PE0 sometimes received wrong data on tag 0.<br>
    3687 
    3688       <br>
    3689 
    3690 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
    3691 errors in case of<span style="font-family: monospace;"> nx /= ny </span>and
    3692 a 1D-decomposition along y.<br>
    3693 
    3694       <br>
    3695 
     1768otherwise PE0 sometimes received wrong data on tag 0.<br> <br>
     1769Use of module indices removed from routine<span style="font-family: monospace;"> split_1dd </span>in<span style="font-family: monospace;"> poisfft </span>since
     1770it caused
     1771errors in case of<span style="font-family: monospace;"> nx
     1772/= ny </span>and
     1773a 1D-decomposition along y.<br> <br>
    36961774Wrong re-definition of dx2 and dy2 in<span style="font-family: monospace;"> sor </span>removed.<br>
    3697 
    3698       </td>
    3699 
    3700       <td style="vertical-align: top;">advec_particles, init_1d_model,
    3701 init_pegrid, plot_2d, poisfft, sor<br>
    3702 
    3703       </td>
    3704 
    3705     </tr>
    3706 
    3707     <tr>
    3708 
    3709       <td style="vertical-align: top;">23/04/05<br>
    3710 
    3711       </td>
    3712 
    3713       <td style="vertical-align: top;">SR<br>
    3714 
    3715       </td>
    3716 
    3717       <td style="vertical-align: top;">2.9a<br>
    3718 
    3719       </td>
    3720 
    3721       <td style="vertical-align: top;">C<br>
    3722 
    3723       </td>
    3724 
    3725       <td style="vertical-align: top;">Additional check for
     1775</td> <td style="vertical-align: top;">advec_particles,
     1776init_1d_model,
     1777init_pegrid, plot_2d, poisfft, sor<br> </td> </tr> <tr>
     1778<td style="vertical-align: top;">23/04/05<br> </td>
     1779<td style="vertical-align: top;">SR<br> </td>
     1780<td style="vertical-align: top;">2.9a<br> </td>
     1781<td style="vertical-align: top;">C<br> </td> <td style="vertical-align: top;">Additional check for
    37261782incompatibilities between non-cyclic lateral boundary conditions and
    3727 other schemes.<br>
    3728 
    3729       <br>
    3730 
    3731 fcl_factor renamed cfl_factor.<br>
    3732 
    3733       <br>
    3734 
     1783other schemes.<br> <br>
     1784fcl_factor renamed cfl_factor.<br> <br>
    37351785New local array sums_ll declared in flow_statistics instead of
    3736 temporarily using sums_l.<br>
    3737 
    3738       <br>
    3739 
     1786temporarily using sums_l.<br> <br>
    37401787crmax (maximum number of crosses allowed in a plot of vertical
    3741 profiles) increased from 20 to 100.<br>
    3742 
    3743       </td>
    3744 
    3745       <td style="vertical-align: top;">calc_spectra, check_parameters,
    3746 flow_statistics, header, modules, parin, timestep<br>
    3747 
    3748       </td>
    3749 
    3750     </tr>
    3751 
    3752     <tr>
    3753 
    3754       <td style="vertical-align: top;"><br>
    3755 
    3756       </td>
    3757 
    3758       <td style="vertical-align: top;"><br>
    3759 
    3760       </td>
    3761 
    3762       <td style="vertical-align: top;"><br>
    3763 
    3764       </td>
    3765 
    3766       <td style="vertical-align: top;">E<br>
    3767 
    3768       </td>
    3769 
    3770       <td style="vertical-align: top;">Revised calculation of output
     1788profiles) increased from 20 to 100.<br> </td> <td style="vertical-align: top;">calc_spectra, check_parameters,
     1789flow_statistics, header, modules, parin, timestep<br> </td>
     1790</tr> <tr> <td style="vertical-align: top;"><br>
     1791</td> <td style="vertical-align: top;"><br> </td>
     1792<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;">E<br> </td> <td style="vertical-align: top;">Revised calculation of output
    37711793time counters regarding a possible decrease of the output time interval
    3772 in case of restart runs.<br>
    3773 
    3774       <br>
    3775 
     1794in case of restart runs.<br> <br>
    37761795Error removed in Dirichlet bottom boundary conditions for pt and q in
    3777 case of Runge-Kutta schemes.<br>
    3778 
    3779       <br>
    3780 
    3781       <span style="font-weight: bold;">batch_scp</span> calls (needed
     1796case of Runge-Kutta schemes.<br> <br> <span style="font-weight: bold;">batch_scp</span> calls
     1797(needed
    37821798for determining correct filenames for AVS-fld-files) is given the
    3783 remote username as an additional argument.<br>
    3784 
    3785       <br>
    3786 
    3787 Default setting of outflow_damping_width corrected.<br>
    3788 
    3789       <br>
    3790 
     1799remote username as an additional argument.<br> <br>
     1800Default setting of outflow_damping_width corrected.<br> <br>
    37911801Initial horizontal velocities at the lowest grid levels in the 1d-model
    37921802are set to a very small value in order to avoid wrong results and the
    3793 resulting too small timesteps.<br>
    3794 
    3795       <br>
    3796 
     1803resulting too small timesteps.<br> <br>
    37971804Implicit counters i renamed i9 in modules due to declaration conflicts
    3798 with i in other subroutines (reported by Portland compiler).<br>
    3799 
    3800       </td>
    3801 
    3802       <td style="vertical-align: top;">advec_particles, boundary_conds,
     1805with i in other subroutines (reported by Portland compiler).<br> </td>
     1806<td style="vertical-align: top;">advec_particles,
     1807boundary_conds,
    38031808check_open, check_parameters, init_1d_model, modules, time_integration<br>
    3804 
    3805       </td>
    3806 
    3807     </tr>
    3808 
    3809     <tr>
    3810 
    3811       <td style="vertical-align: top;">18/05/05<br>
    3812 
    3813       </td>
    3814 
    3815       <td style="vertical-align: top;">SR<br>
    3816 
    3817       </td>
    3818 
    3819       <td style="vertical-align: top;">2.10<br>
    3820 
    3821       </td>
    3822 
    3823       <td style="vertical-align: top;">N<br>
    3824 
    3825       </td>
    3826 
    3827       <td style="vertical-align: top;">NetCDF support implemented.<br>
    3828 
     1809</td> </tr> <tr> <td style="vertical-align: top;">18/05/05<br> </td>
     1810<td style="vertical-align: top;">SR<br> </td>
     1811<td style="vertical-align: top;">2.10<br> </td>
     1812<td style="vertical-align: top;">N<br> </td> <td style="vertical-align: top;">NetCDF support implemented.<br>
    38291813Profiles, time series, spectra, cross-sections, 3d-volume-data and
    38301814particle data can now be output in NetCDF format (file handles
    38311815101-108). This output can be switched on with the new d3par-parameter <span style="font-family: monospace;">data_output_format</span>.
    38321816So far, this support is available on IBM systems at HLRN and on the NEC
    3833 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>
    3834 
    3835       <br>
    3836 
     1817system 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
     1818possible.<br> <br>
    38371819Output of cross sections for qv, vpt and lwp (liquid water path).<br>
    3838 
    3839       </td>
    3840 
    3841       <td style="vertical-align: top;">advec_particles, check_open,
     1820</td> <td style="vertical-align: top;">advec_particles,
     1821check_open,
    38421822check_parameters, close_file, header, modules, parin, plot_1d, plot_2d,
    38431823plot_3d, plot_spectra, plot_ts, read_var_list, write_var_list<br>
    3844 
    3845       <br>
    3846 
    3847       <span style="font-weight: bold;">new:</span><br>
    3848 
    3849 netcdf<br>
    3850 
    3851       </td>
    3852 
    3853     </tr>
    3854 
    3855     <tr>
    3856 
    3857       <td style="vertical-align: top;"><br>
    3858 
    3859       </td>
    3860 
    3861       <td style="vertical-align: top;"><br>
    3862 
    3863       </td>
    3864 
    3865       <td style="vertical-align: top;"><br>
    3866 
    3867       </td>
    3868 
    3869       <td style="vertical-align: top;">C<br>
    3870 
    3871       </td>
    3872 
    3873       <td style="vertical-align: top;">In <span style="font-family: monospace;">calc_spectra</span>, n is assigned the
     1824<br> <span style="font-weight: bold;">new:</span><br>
     1825netcdf<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
     1826is assigned the
    38741827number of spectra (formerly, the number of spectra was given by n-1)<br>
    3875 
    3876       <br>
    3877 
     1828<br>
    38781829Abort if <span style="font-family: monospace;">poisfft_hybrid</span>
    3879 is called in a non-parallel environment.<br>
    3880 
    3881       <br>
    3882 
    3883 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>
    3884 
    3885       </td>
    3886 
    3887       <td style="vertical-align: top;">calc_spectra, check_parameters,
    3888 modules, pres, read_3d_binary, write_3d_binary<br>
    3889 
    3890       </td>
    3891 
    3892     </tr>
    3893 
    3894     <tr>
    3895 
    3896       <td style="vertical-align: top;"><br>
    3897 
    3898       </td>
    3899 
    3900       <td style="vertical-align: top;"><br>
    3901 
    3902       </td>
    3903 
    3904       <td style="vertical-align: top;"><br>
    3905 
    3906       </td>
    3907 
    3908       <td style="vertical-align: top;">E<br>
    3909 
    3910       </td>
    3911 
    3912       <td style="vertical-align: top;">Missing argument in ffty
    3913 (non-parallel case) added.<br>
    3914 
    3915       <br>
    3916 
    3917 Error in output of particle inertia information removed.<br>
    3918 
    3919       </td>
    3920 
    3921       <td style="vertical-align: top;">poisfft, header<br>
    3922 
    3923       </td>
    3924 
    3925     </tr>
    3926 
    3927     <tr>
    3928 
    3929       <td style="vertical-align: top;">05/07/05<br>
    3930 
    3931       </td>
    3932 
    3933       <td style="vertical-align: top;">SR<br>
    3934 
    3935       </td>
    3936 
    3937       <td style="vertical-align: top;">2.11<br>
    3938 
    3939       </td>
    3940 
    3941       <td style="vertical-align: top;">N/C<br>
    3942 
    3943       </td>
    3944 
    3945       <td style="vertical-align: top;">New cloud physics code
     1830is called in a non-parallel environment.<br> <br>
     1831Default values of spectra package parameters <span style="font-family: monospace;">pl_spectra</span> and <span style="font-family: monospace;">spectra_direction</span>
     1832changed.<br> </td> <td style="vertical-align: top;">calc_spectra,
     1833check_parameters,
     1834modules, pres, read_3d_binary, write_3d_binary<br> </td> </tr>
     1835<tr> <td style="vertical-align: top;"><br> </td>
     1836<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
     1837(non-parallel case) added.<br> <br>
     1838Error in output of particle inertia information removed.<br> </td>
     1839<td style="vertical-align: top;">poisfft, header<br>
     1840</td> </tr> <tr> <td style="vertical-align: top;">05/07/05<br> </td>
     1841<td style="vertical-align: top;">SR<br> </td>
     1842<td style="vertical-align: top;">2.11<br> </td>
     1843<td style="vertical-align: top;">N/C<br> </td>
     1844<td style="vertical-align: top;">New cloud physics code
    39461845implemented, which explicitly simulates single cloud droplets,
    39471846including droplet growth by condensation and collision. Using this code
    3948 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
    3949 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>
    3950 
    3951 
    3952       <br>
    3953 
    3954 
    3955       <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>
    3956 
    3957 
    3958       <br>
    3959 
    3960 
    3961 In connection with this new code implementation, several changes has been made to the existing code:<br>
    3962 
    3963 
    3964       <br>
    3965 
    3966 
    3967 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>
    3968 
    3969 
    3970       <br>
    3971 
    3972 
    3973 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>
    3974 
    3975 
    3976       <br>
    3977 
    3978 
    3979       <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>
    3980 
    3981 
    3982       <br>
    3983 
    3984 
    3985 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>
    3986 
    3987 
    3988       <br>
    3989 
    3990 
    3991 Data format for unit 85 (particle data output) is changed.</td>
    3992 
    3993       <td style="vertical-align: top;">advec_particles.f90
     1847requires to set the new inipar-parameter <span style="font-family: monospace;">cloud_droplets</span>
     1848= .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>).
     1849Coupling between droplets and the thermodynamic quantities (potential
     1850temperature and specific humidity) is regarded in the new subroutine <span style="font-family: monospace;">interaction_droplets_ptq</span>.
     1851The real number of droplets in a grid cell can steered by the new
     1852inipar-parameter <span style="font-family: monospace;">initial_weighting_factor</span>.<br>
     1853<br> <span style="font-weight: bold;">This code
     1854will be further extended and probably changed in the near future, so
     1855the current status is that of a test version!</span><br> <br>
     1856In connection with this new code implementation, several changes has
     1857been made to the existing code:<br> <br>
     1858The particle (droplet) size is now given as radius (previously
     1859diameter). E.g., the name of the respective package parameter <span style="font-family: monospace;">diameter</span> has
     1860changed to <span style="font-family: monospace;">radius</span>.<br>
     1861<br>
     1862The current weighting_factor and radius are stored as additional
     1863particle attributes in the type structure <span style="font-family: monospace;">particle_type</span>.
     1864The MPI data type <span style="font-family: monospace;">mpi_particle_type</span>,
     1865needed for exchanging particles between subdomains, has been changed
     1866correspondingly.<br> <br> <span style="font-family: monospace;">gas_constant</span> is
     1867renamed <span style="font-family: monospace;">r_d</span>,
     1868<span style="font-family: monospace;">latent_heat</span>
     1869is renamed <span style="font-family: monospace;">r_v</span>,
     1870the allowed string length of <span style="font-family: monospace;">pl2d</span>
     1871and <span style="font-family: monospace;">pl3d</span>
     1872is increased from 6 to 10.<br> <br>
     1873New 3d arrays <span style="font-family: monospace;">ql_1</span>,
     1874<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
     1875pointer, new pointer <span style="font-family: monospace;">ql_c</span>.<br>
     1876<br>
     1877Data format for unit 85 (particle data output) is changed.</td> <td style="vertical-align: top;">advec_particles.f90
    39941878check_open.f90, header.f90, init_3d_model.f90, init_cloud_physics.f90,
    39951879init_particles.f90, modules.f90, package_parin.f90, parin.f90,
    39961880plot_2d.f90, plot_3d.f90, read_var_list.f90, time_integration.f90,
    3997 write_var_list.f90<br>
    3998 
    3999 
    4000       <br>
    4001 
    4002 
    4003       <span style="font-weight: bold;">new:</span><br>
    4004 
    4005 
    4006 interaction_droplets_ptq.f90</td>
    4007 
    4008     </tr>
    4009 
    4010     <tr>
    4011 
    4012       <td style="vertical-align: top;"><br>
    4013 
    4014       </td>
    4015 
    4016       <td style="vertical-align: top;"><br>
    4017 
    4018       </td>
    4019 
    4020       <td style="vertical-align: top;"><br>
    4021 
    4022       </td>
    4023 
    4024       <td style="vertical-align: top;">C<br>
    4025 
    4026       </td>
    4027 
    4028       <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>
    4029 
    4030       <td style="vertical-align: top;">modules.f90</td>
    4031 
    4032     </tr>
    4033 
    4034     <tr>
    4035 
    4036       <td style="vertical-align: top;"><br>
    4037 
    4038       </td>
    4039 
    4040       <td style="vertical-align: top;"><br>
    4041 
    4042       </td>
    4043 
    4044       <td style="vertical-align: top;"><br>
    4045 
    4046       </td>
    4047 
    4048       <td style="vertical-align: top;">E<br>
    4049 
    4050       </td>
    4051 
    4052       <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>
    4053 
    4054 
    4055       <br>
    4056 
    4057 
     1881write_var_list.f90<br> <br> <span style="font-weight: bold;">new:</span><br>
     1882interaction_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>
     1883is <span style="font-style: italic;">.TRUE.</span>,
     1884because small scale waves occured with <span style="font-style: italic;">.FALSE.</span></td> <td style="vertical-align: top;">modules.f90</td> </tr>
     1885<tr> <td style="vertical-align: top;"><br> </td>
     1886<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
     1887opened 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>
    40581888No opening of units 101 - 108 in case of missing NetCDF support.</td>
    4059 
    4060       <td style="vertical-align: top;">check_open.f90, netcdf.f90<br>
    4061 
    4062       </td>
    4063 
    4064     </tr>
    4065 
    4066     <tr>
    4067 
    4068       <td style="vertical-align: top;">30/06/05<br>
    4069 
    4070       </td>
    4071 
    4072       <td style="vertical-align: top;">GS<br>
    4073 
    4074       </td>
    4075 
    4076       <td style="vertical-align: top;">2.11a<br>
    4077 
    4078       </td>
    4079 
    4080       <td style="vertical-align: top;">C<br>
    4081 
    4082       </td>
    4083 
    4084       <td style="vertical-align: top;">Scalars ug and vg have been
     1889<td style="vertical-align: top;">check_open.f90, netcdf.f90<br>
     1890</td> </tr> <tr> <td style="vertical-align: top;">30/06/05<br> </td>
     1891<td style="vertical-align: top;">GS<br> </td>
     1892<td style="vertical-align: top;">2.11a<br> </td>
     1893<td style="vertical-align: top;">C<br> </td> <td style="vertical-align: top;">Scalars ug and vg have been
    40851894changed into
    40861895arrays in order to allow the specification of a geostrophic wind that
    40871896depends on height (baroclinicity). The initial profiles of the the
    40881897u- and v-component of the geostrophic wind are initialized by
    4089 specifying the new initialization parameters <span style="font-family: monospace;">ug_surface</span>,
    4090       <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>,
    4091       <span style="font-family: monospace;">vg_vertical_gradient</span>, <span style="font-family: monospace;">vg_vertical_gradient_level</span>, respectively. <br>
    4092 
    4093       <br>
    4094 
    4095 The former initialization parameters <span style="font-family: monospace;">ug</span> and <span style="font-family: monospace;">vg</span> have been removed. <br>
    4096 
    4097       </td>
    4098 
    4099       <td style="vertical-align: top;">boundary_conds,
     1898specifying the new initialization parameters <span style="font-family: monospace;">ug_surface</span>, <span style="font-family: monospace;">ug_vertical_gradient</span>,
     1899<span style="font-family: monospace;">ug_vertical_gradient_level</span>
     1900and <span style="font-family: monospace;">vg_surface</span>,
     1901<span style="font-family: monospace;">vg_vertical_gradient</span>,
     1902<span style="font-family: monospace;">vg_vertical_gradient_level</span>,
     1903respectively. <br> <br>
     1904The former initialization parameters <span style="font-family: monospace;">ug</span> and <span style="font-family: monospace;">vg</span> have been
     1905removed. <br> </td> <td style="vertical-align: top;">boundary_conds,
    41001906check_parameters, coriolis, header, init_1d_model, modules, parin,
    41011907prognostic_equations, read_var_list, spline_z, write_var_list<br>
    4102 
    4103       </td>
    4104 
    4105     </tr>
    4106 
    4107     <tr>
    4108 
    4109       <td style="vertical-align: top;"><br>
    4110 
    4111       </td>
    4112 
    4113       <td style="vertical-align: top;"><br>
    4114 
    4115       </td>
    4116 
    4117       <td style="vertical-align: top;"><br>
    4118 
    4119       </td>
    4120 
    4121       <td style="vertical-align: top;">E<br>
    4122 
    4123       </td>
    4124 
    4125       <td style="vertical-align: top;">Error in the calculation of u_0
     1908</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
    41261909and
    4127 v_0 in production_e.f90 removed.<br>
    4128 
    4129       <br>
    4130 
    4131       <span style="font-weight: bold;">Attention:</span> <br>
    4132 
     1910v_0 in production_e.f90 removed.<br> <br> <span style="font-weight: bold;">Attention:</span> <br>
    41331911The content of the testresult-file (run control output) has changed
    4134 due to this modification.<br>
    4135 
    4136       </td>
    4137 
    4138       <td style="vertical-align: top;">production_e<br>
    4139 
    4140       </td>
    4141 
    4142     </tr>
    4143     <tr>
    4144       <td style="text-align: left; vertical-align: top;">20/10/05</td>
    4145       <td style="vertical-align: top;">SR</td>
    4146       <td style="vertical-align: top;">2.11b</td>
    4147       <td style="vertical-align: top;">N/C</td>
    4148       <td style="vertical-align: top;">Collision process for droplet growth completed.<br>
    4149       <br>
    4150       <span style="font-weight: bold;">The droplet code is still under development and requires further speed optimization!<br>
    4151       <br>
    4152       </span>Number of particles really used is additionally output on the netcdf particle data file.<span style="font-weight: bold;"></span></td>
    4153       <td style="vertical-align: top;">advec_particles, modules, netcdf</td>
    4154     </tr>
    4155     <tr>
    4156       <td style="vertical-align: top;">&nbsp;</td>
    4157       <td style="vertical-align: top;">&nbsp;</td>
    4158       <td style="vertical-align: top;">&nbsp;</td>
    4159       <td style="vertical-align: top;">E</td>
    4160       <td style="vertical-align: top;">The
     1912due to this modification.<br> </td> <td style="vertical-align: top;">production_e<br> </td>
     1913</tr> <tr> <td style="text-align: left; vertical-align: top;">20/10/05</td>
     1914<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
     1915growth completed.<br> <br> <span style="font-weight: bold;">The droplet code is still under
     1916development and requires further speed optimization!<br> <br>
     1917</span>Number of particles really used is additionally output on
     1918the netcdf particle data file.<span style="font-weight: bold;"></span></td>
     1919<td style="vertical-align: top;">advec_particles, modules,
     1920netcdf</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
    41611921last PE in a row is not allowed to have more grid points than the other
    41621922PES (only less). Jobs crashed in these cases that the last PE has more
    41631923grid points. Therefore, the number of gridpoints along x (and y) must
    4164 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>
    4165       <br>
    4166 Error removed in calculating y axis data for yz cross sections. Error in output of netcdf yz-cross-sections removed.<br>
    4167       <br>
    4168 2*r replaced by r in the exponential term of the particle momentum equation.<br>
    4169 Error in output of yz-slice information removed.</td>
    4170       <td style="vertical-align: top;">advec_particles, header, init_pegrid, netcdf, plot_2d</td>
    4171     </tr>
    4172     <tr>
    4173       <td style="vertical-align: top;">06/12/05</td>
    4174       <td style="vertical-align: top;">SR</td>
    4175       <td style="vertical-align: top;">2.11c</td>
    4176       <td style="vertical-align: top;">N</td>
    4177       <td style="vertical-align: top;">Output of ql profile is allowed in case of using cloud droplets.</td>
    4178       <td style="vertical-align: top;">check_parameters, flow_statistics, modules</td>
    4179     </tr>
    4180     <tr>
    4181       <td style="vertical-align: top;">&nbsp;</td>
    4182       <td style="vertical-align: top;">&nbsp;</td>
    4183       <td style="vertical-align: top;">&nbsp;</td>
    4184       <td style="vertical-align: top;">E</td>
    4185       <td style="vertical-align: top;">The horizontally averaged pt profile is calculated within<span style="font-family: monospace;"> buoyancy </span>only
     1924now meet a special condition which is checked in case that <span style="font-family: monospace;">grid_matching</span> =
     1925<span style="font-style: italic;">'match'</span> is
     1926used.<br> <br>
     1927Error removed in calculating y axis data for yz cross sections. Error
     1928in output of netcdf yz-cross-sections removed.<br> <br>
     19292*r replaced by r in the exponential term of the particle momentum
     1930equation.<br>
     1931Error in output of yz-slice information removed.</td> <td style="vertical-align: top;">advec_particles, header,
     1932init_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
     1933in case of using cloud droplets.</td> <td style="vertical-align: top;">check_parameters,
     1934flow_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
     1935profile is calculated within<span style="font-family: monospace;">
     1936buoyancy </span>only
    41861937in case of the first respective intermediate timestep. This is done in
    41871938order to spare communication time and to produce identical model
    4188 results with jobs which are calling<span style="font-family: monospace;"> flow_statistics </span>at different time intervals.<br>
    4189       <br>
    4190 Error in netcdf variable declaration for<span style="font-family: monospace;"> statistic_regions </span>/= <span style="font-style: italic;">0</span> removed.</td>
    4191       <td style="vertical-align: top;">buoyancy, netcdf</td>
    4192     </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
     1939results with jobs which are calling<span style="font-family: monospace;"> flow_statistics </span>at
     1940different time intervals.<br> <br>
     1941Error in netcdf variable declaration for<span style="font-family: monospace;"> statistic_regions </span>/=
     1942<span style="font-style: italic;">0</span> removed.</td>
     1943<td style="vertical-align: top;">buoyancy, netcdf</td>
     1944</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
     1945topography (buildings, mountains, etc.)</span><br style="font-weight: bold;"><br>Besides
    41931946the implementation of topography, this version contains several other
    4194 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>
    4195       <br>
    4196 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>
     1947improvements. The most important ones are listed here:<br><ul><li>The
     1948cloud droplet code has been optimized (it now runs about 100 times
     1949faster than before).</li><li>Output of time-averaged 2d/3d
     1950data (sections / volume data) is possible.</li><li>Output
     1951of 2d-section data averaged along the direction normal to this section
     1952can be done.</li><li>The user-interface has been extended
     1953in order to allow 2d-/3d-output of user-defined quantities.</li></ul>The
     1954kind of topography to be used is controlled by the new initialization
     1955parameter <span style="font-family: monospace;">topography</span>.
     1956Allowed values are <span style="font-style: italic;">'flat'</span>,
     1957<span style="font-style: italic;">'single_building'</span>,
     1958and <span style="font-style: italic;">'read_from_file'</span>.
     1959The user can define his own special topography setting within the new
     1960user-interface routine <span style="font-family: monospace;">user_init_grid</span>.
     1961For the single building case, the&nbsp;building (rectangular) size
     1962and position can be controlled with parameters <span style="font-family: monospace;">building_height</span>,
     1963<span style="font-family: monospace;">building_length_x</span>,
     1964<span style="font-family: monospace;">building_length_y</span>,
     1965<span style="font-family: monospace;">building_wall_left</span>,
     1966and <span style="font-family: monospace;">building_wall_south</span>.<br>
     1967<br>
     1968The topography code is already optimized (vectorized) for use on the
     1969NEC-SX6.<br><br>Output of time-averaged 2d-/3d-data can be
     1970enabled by appending the string <span style="font-style: italic;">'_av'</span>
     1971to the respective output quantities given with the new
     1972runtime-parameter <span style="font-family: monospace;">data_output</span>
    41971973(see further below for the (name)changes in the parameters for data
    41981974output). Example: if a time-average of the vertical cross-section of
    … …  
    42021978the averaging interval and the temporal distance of the single
    42031979instantaneous sections (volumes) entering into this averaging is
    4204 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
     1980controlled by the new runtime-parameters <span style="font-family: monospace;">averaging_interval</span>and
     1981<span style="font-family: monospace;">dt_averaging_input</span>.
     1982<br><br>An average normal to the direction of a
     1983cross-section can be output by setting the respective cross section
     1984index to <span style="font-style: italic;">-1</span>
     1985(example: <span style="font-family: monospace;">section_xz</span>
     1986= <span style="font-style: italic;">-1</span>).<br><br>New
     1987user-interface routines allowing the output of user-defined quantities
     1988are <span style="font-family: monospace;">user_check_data_output</span>,
     1989<span style="font-family: monospace;">user_define_netcdf_grid</span>,
     1990<span style="font-family: monospace;">user_data_output_2d</span>,
     1991<span style="font-family: monospace;">user_data_output_3d</span>,
     1992and <span style="font-family: monospace;">user_3d_data_averaging</span>.
     1993These quantities can be calculated using the new <span style="font-family: monospace;">CASE</span>-Entry <span style="font-style: italic;">'after integration'</span>
     1994in the user-interface routine <span style="font-family: monospace;">user_actions</span>.<br><br>Optimization
    42051995of the cloud droplet code is mainly done by re-sorting all particles
    42061996after every timestep in a way that now all particles which belong to
    42071997the same grid-box (k,j,i) are stored consecutively (wthout any strides)
    4208 in memory.<br>
    4209       <br>
    4210 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
     1998in memory.<br> <br>
     1999Code adaptation for the IBM at the department of atmospheric sciences,
     2000Yonsei 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
     2001of particle tails now requires setting of the new package-parameter <span style="font-family: monospace;">use_particle_tails</span>.
     2002The new parameter skip_particles_for_tail allows only every <span style="font-family: monospace;">skip_particle_for_tail</span>'th
     2003parameter having a tail.</li><li>Initialization-parameter <span style="font-family: monospace;">e_min</span> can be
     2004used to set a lower limit for the subgrid-scale TKE (i.e. to guarantee
     2005a lower limit for the flow's Reynolds-number).</li><li>A
    42112006conservation of the volume flow (through the complete xz- and
    42122007yz-sections &nbsp;of the total domain) can be enforced by the new
    4213 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>
    4214 </li><li>By default, NetCDF output is now using 64-bit offset format
     2008initialization-parameter <span style="font-family: monospace;">conserve_volume_flow</span>.</li><li>Data
     2009output can be skipped for a given time interval from simulation start
     2010(t=0) using new runtime-parameters <span style="font-family: monospace;">skip_time_dopr</span>,
     2011<span style="font-family: monospace;">skip_time_dosp</span>,
     2012<span style="font-family: monospace;">skip_time_do2d_xy</span>,
     2013<span style="font-family: monospace;">skip_time_do2d_xz</span>,
     2014<span style="font-family: monospace;">skip_time_do2d_yz</span>,
     2015and <span style="font-family: monospace;">skip_time_do3d</span>.<br>
     2016</li><li>By default, NetCDF output is now using 64-bit
     2017offset format
    42152018(large file support) on most machines. The user can switch to the
    4216 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>
    4217         </li>
    4218         <li>Data
     201932-bit offset format with the new runtime-parameter <span style="font-family: monospace;">netcdf_64bit</span>.
     2020Units 111:113&nbsp; and 116 are opened for NetCDF output of
     2021time-averaged 2d-3d data.<br> </li> <li>Data
    42192022logging routines are added (see file data_log.f90), which can be used
    42202023for debugging purposes. Output is done on unit 20 (local file
    4221 name/directory name DATA_LOG).</li>
    4222         <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>
    4223         <li>Two different methods for calculating the mixing length and
     2024name/directory name DATA_LOG).</li> <li>New routine <span style="font-family: monospace;">exchange_horiz_2d_int</span>
     2025for&nbsp; ghostpoint exchange of 2d-integer arrays. Routine <span style="font-family: monospace;">exchange_horiz_2d</span>
     2026is extended for non-cyclic boundary conditions in the non-parallel case.</li>
     2027<li>Two different methods for calculating the mixing length and
    42242028the dissipation can be used in the 1d-model. These are steered by the
    4225 new initializing-parameters <span style="font-family: monospace;">dissipation_1d</span> and <span style="font-family: monospace;">mixing_length_1d</span>.<br>
    4226         </li>
    4227 </ul></td><td style="vertical-align: top;">advec_particles, advec_s_pw,
     2029new initializing-parameters <span style="font-family: monospace;">dissipation_1d</span>
     2030and <span style="font-family: monospace;">mixing_length_1d</span>.<br>
     2031</li>
     2032</ul></td><td style="vertical-align: top;">advec_particles,
     2033advec_s_pw,
    42282034advec_s_up, advec_u_pw, advec_u_up, advec_v_pw, advec_v_up, advec_w_pw,
    42292035advec_w_up, boundary_conds, buoyancy, check_open, check_parameters,
    … …  
    42352041prandtl_fluxes, pres, production_e, prognostic_equations,
    42362042read_3d_binary, read_var_list, run_control, time_integration,
    4237 user_interface, write_3d_binary, write_var_list<br>
    4238       <br>
    4239       <span style="font-weight: bold;">new:</span><br>
    4240 average_3d_data, data_log, sum_up_3d_data<br>
    4241       <br>
    4242       <span style="font-weight: bold;">renamed:<br>
    4243       </span>plot_dvrp -&gt; data_output_dvrp<br>
     2043user_interface, write_3d_binary, write_var_list<br> <br> <span style="font-weight: bold;">new:</span><br>
     2044average_3d_data, data_log, sum_up_3d_data<br> <br> <span style="font-weight: bold;">renamed:<br> </span>plot_dvrp
     2045-&gt; data_output_dvrp<br>
    42442046plot_spectra -&gt; data_output_spectra<br>
    42452047plot_ts -&gt; data_output_tseries<br>
    4246 plot_1d -&gt; data_output_profiles<br>
    4247       <span style="font-weight: bold;"></span>plot_2d -&gt; data_output_2d<br>
     2048plot_1d -&gt; data_output_profiles<br> <span style="font-weight: bold;"></span>plot_2d -&gt;
     2049data_output_2d<br>
    42482050plot_3d -&gt; data_output_3d<br>
    4249 </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
     2051</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
     2052parallel mode, all PEs are opening the same copy of the
     2053NAMELIST-parameter file <span style="font-family: monospace;">PARIN</span>,
     2054i.e. from now on, the file attribute "<span style="font-family: monospace;">npe</span>" must be
     2055removed from the corresponding file connection statements in the <span style="font-weight: bold;">mrun</span> configuration
     2056file (.mrun.config).<br><br>A
    42502057large number of parameter names and local filenames have been changed
    42512058(see&nbsp;list below). Most of them are parameters concerning data
    … …  
    42532060to "data_output" and "do", respectively. In addition to these changes,
    42542061the names of many internal PALM parameters and variables have also
    4255 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>
    4256       <br>
     2062changed.<br><br>Restart runs now require setting of the
     2063initialization-parameter <span style="font-family: monospace;">initializing_actions</span>
     2064= <span style="font-style: italic;">'read_restart_data'</span>.<br>
     2065<br>
    42572066Concerning particles, the parameters <span style="font-family: monospace;">psl</span>, <span style="font-family: monospace;">psr</span>, <span style="font-family: monospace;">pdx</span>,
    42582067etc., which are controlling the position of the particle source and the
    42592068number of particles within this source, are now 1d-arrays. This allows
    42602069to define different particle sources for different particle groups.<br>
    4261       <br>
    4262 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>
    4263 </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>
     2070<br>
     2071The number of particle groups has to be set by the user (no automatic
     2072calculation from the value of parameter <span style="font-family: monospace;">density_ratio</span>
     2073any more)<span style="font-style: italic;"></span>.
     2074Variable <span style="font-family: monospace;">idum</span>
     2075in type <span style="font-family: monospace;">particle_type</span>
     2076has been renamed <span style="font-family: monospace;">tail_id</span>.<br><br>Output
     2077for units 15 and 17 flushed in <span style="font-family: monospace;">init_1d_model</span>.<br><br>List
     2078of 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>
     2079</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
     2080is 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>
    42642081</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>
    42652082</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>
    … …  
    42752092</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>
    42762093</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>
    4277 </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>
     2094</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
     2095are 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>
    42782096</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>
    42792097</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>
    … …  
    42922110run_control, time_integration, timestep, write_compressed,
    42932111write_var_list<br>
    4294 </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>
    4295       <br>
    4296 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>
    4297 </td><td style="vertical-align: top;">advec_particles, data_output_tseries, header, init_particles, init_1d_model, netcdf<br>
    4298 </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
     2112</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td style="vertical-align: top;">E</td><td>Error in
     2113the 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
     2114boundary has been fixed.<br> <br>
     2115Error removed getting the variable ids for <span style="font-family: monospace;">_ext</span> for
     2116profiles and time series.<br><br>NetCDF calls in <span style="font-family: monospace;">data_output_tseries</span>
     2117only if NetCDF output is switched on.<br><br>Output of the
     2118initial geostrophic wind profile corrected.<br><br>Maximum
     2119possibel timestep for Runge-Kutta-schemes reduced, error concerning
     2120initialization of&nbsp; <span style="font-family: monospace;">l_black</span>
     2121removed (both in <span style="font-family: monospace;">init_1d_model</span>).<br>
     2122</td><td style="vertical-align: top;">advec_particles,
     2123data_output_tseries, header, init_particles, init_1d_model, netcdf<br>
     2124</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
     2125the cache-optimized PALM code.<br><br>OpenMP
    42992126directives have been added where necessary. Still further tuning will
    43002127be necessary to get optimum performance. Other parts of the code than
    4301 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
     2128the cache-optimized code still need to be (OpenMP-) parallelized. <br><br>So
     2129far, 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>
     2130and <span style="font-family: monospace;">-O</span>,
     2131i.e. when the Option <span style="font-family: monospace;">-O</span>
     2132is given, the <span style="font-family: monospace;">-T</span>
     2133argument is interpreted as the number of threads to be used. When <span style="font-family: monospace;">-O</span> is given,
     2134the number of MPI tasks per node is automatically set to <span style="font-style: italic;">1</span>.<br><br>Beside
    43022135the additional compiler directives, the main code change required by
    43032136the OpenMP parallelization is that global sums are now calculated by
    43042137first calculating local sums on each thread. As the next step, local
    43052138sums are calculated from these thread sums for each MPI task before the
    4306 global sum is computed via MPI_ALLREDUCE.&nbsp; For storing the thread
     2139global sum is computed via MPI_ALLREDUCE.&nbsp; For storing the
     2140thread
    43072141sums, arrays sums_l and sums_l_l now have three dimensions where the
    43082142number of elements of the third dimension is equal to the number of
    … …  
    43102144cpu_statistics, diffusivities, flow_statistics, header, init_pegrid,
    43112145init_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
    4312 correction for Piacsek &amp; Williams advection scheme: keep u and v
    4313 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-
     2146correction for Piacsek &amp; Williams advection scheme: keep u and
     2147v
     2148zero 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>
     2149nzb_s_inner(j,i) replaced by nzb in determination of z_i.<br><br>Errors
     2150removed in the computation of the diabatic mixing length (<span style="font-family: monospace;">init_1d_model.f90</span>).<br><br>Error
     2151removed in extend mode when checking whether the selected cross
     2152sections match those in the already existing NetCDF file (<span style="font-family: monospace;">netcdf.f90</span>).</td><td align="left" valign="top">flow_statistics,
     2153init_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
     2154system 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,
     2155local_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-
    43142156and 3d-datasets now contain the exact coordinates of the variables
    43152157along x and y with respect to the positions where they are defined on
    4316 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
     2158the staggered grid.<br><br>NetCDF datasets of cross
     2159sections (e.g. <span style="font-family: monospace;">DATA_2D_XY_NETCDF</span>)
     2160are only opened if the respective cross sections are really requested
     2161by the settings of parameter <span style="font-family: monospace;">data_output</span>.</td><td align="left" valign="top">check_parameters,
     2162data_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>
     2163instead 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
    43172164scale velocities can (optionally) be included for calculating the
    43182165particle advection, using the method of Weil et al. (2004, JAS, 61,
    431921662877-2887). This method is switched on by the new particle package
    4320 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,
     2167parameter <span style="font-family: monospace;">use_sgs_for_particles</span>.
     2168This also forces the Euler/upstream method to be used for time
     2169advancement of the TKE (see new parameter <span style="font-family: monospace;">use_upstream_for_tke</span>).
     2170The minimum timestep during the sub-timesteps is controlled by
     2171parameter <span style="font-family: monospace;">dt_min_part</span>.
     2172The data type <span style="font-family: monospace;">particle_type</span>
     2173has additional new attributes <span style="font-family: monospace;">e_m</span>,
     2174<span style="font-family: monospace;">dt_sum</span>,
     2175and <span style="font-family: monospace;">speed_x/y/z_sgs</span>.<br><br>Other
     2176new particle features: output of particle quantities as timeseries in
     2177NetCDF format (on local file <span style="font-family: monospace;">DATA_1D_PTS_NETCDF</span>).
     2178The output time interval is controlled by parameter <span style="font-family: monospace;">dt_dopts</span>.
     2179Particle advection can be switched off after some time using parameter <span style="font-family: monospace;">end_time_prel</span>.
     2180More than one particle per point can be started with parameter <span style="font-family: monospace;">particles_per_point</span>.<br><br>Additional
     2181parameter in function <span style="font-family: monospace;">random_gauss</span>
     2182which limits the range of the created random numbers to five times the
     2183standard deviation (=1). Seeds <span style="font-family: monospace;">iran</span>
     2184and <span style="font-family: monospace;">iran_part</span>
     2185are stored for restart runs.</td><td align="left" valign="top">advec_particles,
    43212186check_open, check_parameters, close_file, diffusion_e,
    43222187disturb_heatflux, header, init_3d_model, init_particles, modules,
    43232188netcdf, package_parin, parin, prognostic_equations, random_gauss,
    43242189read_3d_binary, read_var_list, time_integration, write_3d_binary,
    4325 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
     2190write_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
     2191after call of subroutine <span style="font-family: monospace;">init_3d_model</span>.
     2192Generation of <span style="font-family: monospace;">run_description_header</span>
     2193is moved from routines <span style="font-family: monospace;">palm</span>
     2194and <span style="font-family: monospace;">header</span>
     2195to <span style="font-family: monospace;">check_parameters</span>.
     2196Determination 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,
     2197disturb_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
    43262198do2d_unit and do3d_unit now defined as 2d-arrays. Before, in some
    43272199cases, the units of variables in the 2d- and 3d-NetCDF-files have been
    4328 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>
    4329 
     2200wrong.<br><br>In routine <span style="font-family: monospace;">poisfft</span> default
     2201setting of the thread number tn in case of not using OpenMP.<br><br>Error
     2202removed in the non-parallel part of routine <span style="font-family: monospace;">flow_statistics</span>
     2203(number of arguments of array <span style="font-family: monospace;">sums_l</span>).<br><br>Error
     2204removed which appeared if the user had decreased the value of <span style="font-family: monospace;">dt_dopr</span> within
     2205a job chain and if simulataneous time averaging of profiles was
     2206switched on.</td><td align="left" valign="top">check_parameters,
     2207data_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
     2208particle group, seperate output of timeseries for each of the groups.<br><br>New
     2209initial parameter <span style="font-family: monospace;">dz_max</span>,
     2210which limits the vertical gridspacing in case of a vertically stretched
     2211grid.</td><td style="vertical-align: top;">data_output_ptseries,
     2212header, 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
     2213for the last Runge-Kutta-substep. <br><span style="font-weight: bold;">Attention:</span> <br>
    43302214The content of the testresult-file (run control output) has changed
    4331 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
     2215due to this modification.<br><br>Output of xz and yz cross
     2216sections now up to gridpoint nzt+1.<br><br>Default settings
     2217of particle start positions changed.</td><td style="vertical-align: top;">check_open, close_file,
     2218data_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
     2219arrays (t.._m) needed for the Runge-Kutta schemes.<br><br>Bugfix
     2220in index array initialization for line- or point-like topography
     2221structures.<br><br>Bugfix: yv coordinates are now used for
     2222yz 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
     2223is the last revision before switching to the subversion revison control
     2224system!<br><br>Informative output to the job protocoll in
     2225case 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
     2226are now read from local file <span style="font-family: monospace;">ENVPAR</span>
     2227instead of getting them by a system call.<br><br>For
     2228interpolation in <span style="font-family: monospace;">advec_particles</span>,
     2229allways level k is used.</td><td style="vertical-align: top;">advec_particles,
     2230local_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>:
     2231new particles are released only if <span style="font-family: monospace;">end_time_prel</span>
     2232&gt; <span style="font-family: monospace;">simulated_time</span>,&nbsp;transfer
    43322233of particles when x &lt; -0.5*dx (0.0 before), etc., index i,j used
    43332234instead of cartesian (x,y) coordinate to check for transfer because
    43342235this failed under very rare conditions, calculation of number of
    4335 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>
    4336 
     2236particles with same radius as the current particle (cloud droplet code).<br><br>Allocation
     2237of <span style="font-family: monospace;">tail_mask</span>
     2238and <span style="font-family: monospace;">new_tail_id</span>
     2239in 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
     2240the top with new inipar parameters <span style="font-family: monospace;">top_heatflux</span>
     2241and <span style="font-family: monospace;">use_top_fluxes</span>.
     2242New 2d-arrays <span style="font-family: monospace;">qswst</span>,
     2243<span style="font-family: monospace;">qswst_m</span>,
     2244<span style="font-family: monospace;">tswst</span>
     2245and <span style="font-family: monospace;">tswst_m</span>
     2246are used to store this flux. Use of fluxes are controlled with new
     2247index variable <span style="font-family: monospace;">nzt_diff</span>.
     2248A Neumann boundary condition for temperature can be applied under these
     2249conditions.<br><br>Additionally, a Dirichlet condition for
     2250temperature can be used at the top.<br><br><span style="font-weight: bold;">Attention:</span> <br>
    43372251The content of the testresult-file (run control output) has changed
    43382252due to this modification.</td><td style="vertical-align: top;">check_parameters,
    43392253diffusion_s, flow_statistics, header, init_grid, init_3d_model,
    43402254modules, parin, production_e, prognostic_equations, read_var_list,
    4341 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,
     2255read_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
     2256scalars are now solved up to gridpoint <span style="font-family: monospace;">nzt</span> (formerly <span style="font-family: monospace;">nzt-1</span>).
     2257Boundary conditions for scalars at top adjusted respectively (now
     2258applied only at <span style="font-family: monospace;">nzt+1</span>).<br><br>The
     2259default top boundary condition for temperature has been renamed to <span style="font-style: italic;">'initial_gradient'</span>.<br><br>Calls
     2260of <span style="font-family: monospace;">dvrp_output_local</span>,
     2261which were commented out for a long time, are now activated for all
     2262streams.</td><td style="vertical-align: top;">advec_s_pw,
    43422263boundary_conds, calc_precipitation, check_parameters, diffusion_e,
    43432264diffusion_s, impact_of_latent_heat, init_dvrp, init_pt_anomaly,
    4344 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>
    4345 
    4346  
    4347   </tbody>
    4348 </table>
    4349 
    4350 &nbsp;<b><blink>Attention:</blink></b> If<tt> make </tt>is not used
     2265modules, 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
     2266pointer any more.<br><br>Bugfix in <span style="font-family: monospace;">init_particles</span>:
     2267<span style="font-family: monospace;">MPI_REAL</span>
     2268argument in <span style="font-family: monospace;">MPI_ALLREDUCE</span>
     2269replaced by<br><span style="font-family: monospace;">MPI_INTEGER</span>
     2270(caused error on NEC only).<br><br>Bugfix:&nbsp; <span style="font-family: monospace;">ddzw</span> now
     2271dimensioned <span style="font-family: monospace;">1:nzt"+1".</span></td><td style="vertical-align: top;">diffusion_e, diffusion_s,
     2272diffusion_u, diffusion_v, diffusion_w, init_particles, modules</td></tr>
     2273</tbody>
     2274</table>&nbsp;<b><blink>Attention:</blink></b>
     2275If<tt> make </tt>is not used
    43512276for
    43522277compiling,
    4353 <b>all routines</b> have to be re-compiled after every change
     2278<b>all routines</b> have to be re-compiled after every
     2279change
    43542280to <b>modules.f90!</b>
    4355 <br>
    4356 
    4357 &nbsp;
    4358 <br>
    4359 
    4360 &nbsp;
    4361 <h2><a name="Kapitel2.0"></a>2.0&nbsp; How to change the model source
     2281<br>&nbsp;
     2282<br>&nbsp;
     2283<h2><a name="Kapitel2.0"></a>2.0&nbsp; How
     2284to change the model source
    43622285code</h2>
    4363 
    43642286&Auml;nderungen, Erweiterungen oder Fehlerkorrekturen am Modellcode
    43652287(gemeint
    43662288sind alle Modellteile, die nicht zur benutzereigenen Software
    43672289geh&ouml;ren)
    4368 erfordern vom jeweiligen Benutzer Gruppenzugeh&ouml;rigkeit zur Gruppe
     2290erfordern vom jeweiligen Benutzer Gruppenzugeh&ouml;rigkeit zur
     2291Gruppe
    43692292<tt>"palm"</tt>.
    43702293Zu dieser Gruppe geh&ouml;ren alle Benutzer, die aktiv an der
    43712294Modellentwicklung
    43722295mitwirken (im weiteren "Modellarbeitsgruppe" genannt).
    4373 <p>Die einzelnen Quelltextdateien des Modells werden mit RCS (Revision
     2296<p>Die einzelnen Quelltextdateien des Modells werden mit RCS
     2297(Revision
    43742298Control System) verwaltet. Grundlegende Kenntnisse &uuml;ber dieses
    43752299System
    43762300werden im weiteren vorausgesetzt.
    4377 </p>
    4378 
    4379 <p>&Auml;nderungen am Modellcode erfordern die Durchf&uuml;hrung
     2301</p><p>&Auml;nderungen am Modellcode erfordern die
     2302Durchf&uuml;hrung
    43802303bestimmter
    43812304Aktionen in einer festgelegten Reihenfolge, die nun beschrieben werden
    43822305sollen.
    4383 </p>
    4384 
    4385 <ol>
    4386 
    4387   <li>Konzeptplanung.</li>
    4388 
    4389   <li>Diskussion der geplanten &Auml;nderungen in der
    4390 Modellarbeitsgruppe.</li>
    4391 
    4392   <li>Auschecken der ben&ouml;tigten Quelltextdateien,
     2306</p><ol> <li>Konzeptplanung.</li> <li>Diskussion
     2307der geplanten &Auml;nderungen in der
     2308Modellarbeitsgruppe.</li> <li>Auschecken der
     2309ben&ouml;tigten Quelltextdateien,
    43932310Durchf&uuml;hrung der
    43942311&Auml;nderungen und Test des Modells. Die Modul-Datei <tt>modules.f90</tt>
    43952312sollte nur dann ausgecheckt werden, wenn dort aufgef&uuml;hrte
    43962313Variablen
    4397 ver&auml;ndert werden. Neu geschaffene Variablen sollten w&auml;hrend
     2314ver&auml;ndert werden. Neu geschaffene Variablen sollten
     2315w&auml;hrend
    43982316der
    43992317Testphase in ein ebenfalls tempor&auml;r neu zu schaffendes Modul
    … …  
    44032321entsprechender USE-Anweisungen). Die in den einzelnen Dateien
    44042322durchgef&uuml;hrten
    4405 Arbeiten m&uuml;ssen in den Kopfzeilen (unter "Aktuelle Aenderungen")
     2323Arbeiten m&uuml;ssen in den Kopfzeilen (unter "Aktuelle
     2324Aenderungen")
    44062325der
    4407 Dateien vermerkt werden. Dies tut man am besten noch <b>bevor</b> man
     2326Dateien vermerkt werden. Dies tut man am besten noch <b>bevor</b>
     2327man
    44082328die
    44092329eigentlichen &Auml;nderungen durchf&uuml;hrt (sonst droht das
    4410 Vergessen...).</li>
    4411 
    4412   <li>Zum Abschlu&szlig; der Tests sollte mit dem Modell eine
     2330Vergessen...).</li> <li>Zum Abschlu&szlig; der Tests
     2331sollte mit dem Modell eine
    44132332Kontrollrechnung
    44142333durchgef&uuml;hrt und die Ergebnisse mit denen des sogenannten
    … …  
    44182337durchzuf&uuml;hren, die auch zum Testen der Modellinstallation
    44192338verwendet
    4420 werden (s. <a href="Anwendung/Kapitel_5.0.html">Kapitel 5.0</a> der
     2339werden (s. <a href="Anwendung/Kapitel_5.0.html">Kapitel
     23405.0</a> der
    44212341Anwenderdokumentation).
    44222342Die 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>
    … …  
    44302350so
    44312351ist unbedingt eine Diskussion in der Modellarbeitsgruppe notwendig.</li>
    4432 
    4433   <li>Nach Durchf&uuml;hrung der Tests m&uuml;ssen bei Bedarf die
     2352<li>Nach Durchf&uuml;hrung der Tests m&uuml;ssen bei
     2353Bedarf die
    44342354vorl&auml;ufig
    4435 im tempor&auml;ren Modul eingetragenen Variablen in die eigentlichen
     2355im tempor&auml;ren Modul eingetragenen Variablen in die
     2356eigentlichen
    44362357Module
    44372358des Modells &uuml;bertragen werden. Dazu ist die Modul-Datei <tt>modules.f90</tt>
    44382359auszuchecken. Nach Eintrag der Variablen sollte das Modell noch einmal
    4439 testweise &uuml;bersetzt werden, um Sytaxfehler auszuschlie&szlig;en
     2360testweise &uuml;bersetzt werden, um Sytaxfehler
     2361auszuschlie&szlig;en
    44402362(evtl.
    44412363auch noch einmal einen Probelauf starten). Die Verwendung des
    44422364tempor&auml;ren
    44432365Moduls ist aus allen entsprechenden Programmteilen zu entfernen.</li>
    4444 
    4445   <li>Vergabe einer neuen Versionsnummer (Variable <tt>version</tt> im
     2366<li>Vergabe einer neuen Versionsnummer (Variable <tt>version</tt>
     2367im
    44462368Modul <tt>steuer</tt>),
    4447 Bsp.: 2.3c. Kleinere &Auml;nderungen werden durch angeh&auml;ngten
     2369Bsp.: 2.3c. Kleinere &Auml;nderungen werden durch
     2370angeh&auml;ngten
    44482371kleinen
    4449 Buchstaben kenntlich gemacht, gr&ouml;&szlig;ere &Auml;nderungen durch
     2372Buchstaben kenntlich gemacht, gr&ouml;&szlig;ere
     2373&Auml;nderungen durch
    44502374die Zahl hinter dem Punkt. Eine Inkrementierung der Zahl vor dem Punkt
    4451 geschieht nur bei ganz grunds&auml;tzlichen Revisionen des Modells, die
    4452 weite Teile des Modellcodes betreffen.</li>
    4453 
    4454   <li>Nun k&ouml;nnen die ausgecheckten Dateien wieder eingecheckt
     2375geschieht nur bei ganz grunds&auml;tzlichen Revisionen des Modells,
     2376die
     2377weite Teile des Modellcodes betreffen.</li> <li>Nun
     2378k&ouml;nnen die ausgecheckten Dateien wieder eingecheckt
    44552379werden.
    44562380Vor
    … …  
    44622386der vom RCS-System vergebenen Versionsnummer (daf&uuml;r sorgt die
    44632387$Log:
    4464 ... $ - Zeile, die in jeder Quelltextdatei steht).</li>
    4465 
    4466   <li>Eine Zusammenfassung der durchgef&uuml;hrten Arbeiten ist im <a href="#Kapitel1.0">Kapitel
    4467 1.0</a> einzutragen.</li>
    4468 
    4469   <li>Die Modellarbeitsgruppe ist &uuml;ber den Abschlu&szlig; der
     2388... $ - Zeile, die in jeder Quelltextdatei steht).</li> <li>Eine
     2389Zusammenfassung der durchgef&uuml;hrten Arbeiten ist im <a href="#Kapitel1.0">Kapitel
     23901.0</a> einzutragen.</li> <li>Die
     2391Modellarbeitsgruppe ist &uuml;ber den Abschlu&szlig; der
    44702392durchgef&uuml;hrten
    44712393Arbeiten zu informieren.</li>
    4472 
    4473 </ol>
    4474 
    4475 <h2>
    4476 <a name="Kapitel3.0"></a>3.0&nbsp; Description of selected parts of the
     2394</ol><h2>
     2395<a name="Kapitel3.0"></a>3.0&nbsp; Description
     2396of selected parts of the
    44772397model source code</h2>
    4478 
    44792398<b>This chapter is still under construction (Feb. 04).</b>
    4480 <p>Dieser Abschnitt verweist auf vorhandene Beschreibungen der genauen
    4481 Funktionsweise einzelner, spezieller Modellteile. Dazu geh&ouml;rt z.B.
     2399<p>Dieser Abschnitt verweist auf vorhandene Beschreibungen der
     2400genauen
     2401Funktionsweise einzelner, spezieller Modellteile. Dazu geh&ouml;rt
     2402z.B.
    44822403die Beschreibung bestimmter numerischer Verfahren (auch ihr
    44832404theoretischer
    … …  
    44882409Aufgaben (z.B. der Berechnung horizontal gemittelter
    44892410Gr&ouml;&szlig;en).
    4490 <br>
    4491 
    4492 Die Beschreibungen liegen in jeweils getrennten Dokumenten, in der
     2411<br>Die Beschreibungen liegen in jeweils getrennten Dokumenten,
     2412in der
    44932413Regel als TeX- und/oder Postscript-Datei vor und sind &uuml;ber die
    44942414folgenden
    44952415Links zug&auml;nglich.
    4496 <br>
    4497 
     2416<br>&nbsp;
     2417</p><ul> <li> <a name="UPS"></a>upstream-spline
     2418advection scheme ( <a href="Upstream_Spline/ups.ps">.ps</a>
     2419)</li> <li> <a name="Cloud_physics"></a>cloud
     2420physics module ( <a href="Cloud_physics/wolken.pdf">.pdf</a>
     2421)</li> <li> <a name="Bitkompression"></a>Datenkompression
     2422mit dem Verfahren
     2423der <a href="Bitkompression/kompression.html">Bitverschiebung</a></li>
     2424<li> <a name="Runge-kutta"></a>Runge-Kutta
     2425time integration scheme ( <a href="numerik.heiko/zeitschrittverfahren.pdf">.pdf</a>
     2426)</li>
     2427</ul><br>
    44982428&nbsp;
    4499 </p>
    4500 
    4501 <ul>
    4502 
    4503   <li> <a name="UPS"></a>upstream-spline advection scheme ( <a href="Upstream_Spline/ups.ps">.ps</a>
    4504 )</li>
    4505 
    4506   <li> <a name="Cloud_physics"></a>cloud physics module ( <a href="Cloud_physics/wolken.pdf">.pdf</a>
    4507 )</li>
    4508 
    4509   <li> <a name="Bitkompression"></a>Datenkompression mit dem Verfahren
    4510 der <a href="Bitkompression/kompression.html">Bitverschiebung</a></li>
    4511 
    4512   <li> <a name="Runge-kutta"></a>Runge-Kutta time integration scheme (
    4513     <a href="numerik.heiko/zeitschrittverfahren.pdf">.pdf</a>
    4514 )</li>
    4515 
    4516 </ul>
    4517 
    4518 <br>
    4519 
    4520 &nbsp;
    4521 <br>
    4522 
    4523 &nbsp;
    4524 <br>
    4525 
    4526 &nbsp;
    4527 <br>
    4528 
    4529 &nbsp;
    4530 <br>
    4531 
    4532 &nbsp;
    4533 <br>
    4534 
    4535 &nbsp;
    4536 <br>
    4537 
    4538 &nbsp;
    4539 <br>
    4540 
    4541 &nbsp;
     2429<br>&nbsp;
     2430<br>&nbsp;
     2431<br>&nbsp;
     2432<br>&nbsp;
     2433<br>&nbsp;
     2434<br>&nbsp;
     2435<br>&nbsp;
    45422436</body></html>
Note: See TracChangeset for help on using the changeset viewer.
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |