Index: /palm/trunk/DOC/app/chapter_3.8.html
===================================================================
--- /palm/trunk/DOC/app/chapter_3.8.html	(revision 343)
+++ /palm/trunk/DOC/app/chapter_3.8.html	(revision 344)
@@ -1,130 +1,138 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><head>
-
-  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
-  
-
-
-  <title>PALM chapter 3.8</title><meta name="GENERATOR" content="StarOffice 7 (Win32)">
-
-  <meta name="AUTHOR" content="Siegfried Raasch">
-
-  <meta name="CREATED" content="20040809;13460943">
-
-  <meta name="CHANGED" content="20041112;15085727">
-
-  <meta name="KEYWORDS" content="parallel LES model">
-
-  <style>
-<!--
-@page { size: 21cm 29.7cm }
--->
-  </style></head>
-
-<body style="direction: ltr;" lang="en-US">
-
-<h3 style="line-height: 100%;">3.8 Coupled model runs</h3>
-
-<p style="line-height: 100%;">Starting from version 3.4
-PALM allows coupled atmosphere-ocean model runs. By analogy with the
-modular structure of PALM, <span style="font-weight: bold;">mrun</span>
-starts the coupled model as two concurrent executables, the atmosphere
-version and&nbsp;the ocean version of PALM.</p>
-
-<p style="line-height: 100%;">Currently, the coupler
-is at an experimental stage using a simple MPI2 intercommunicator that
-matches the atmosphere and ocean processors one-to-one. This approach
-has&nbsp;limited flexibility and performance, because it requires
-identical horizontal numerical grids and it uses the same number of
-atmosphere and ocean processors, which does not necessarily guarrantee
-a good load balancing.</p>
-
-<p style="line-height: 100%;">The coupler establishes a
-one-way interaction between the
-atmosphere and the ocean. The atmosphere sends its bottom surface
-fluxes
-(temperature, humidity, momentum) to the ocean. The ocean sends its top
-surface temperature to the atmosphere. The atmosphere assumes
-saturation of humidity and zero wind speed at its bottom surface. For
-calculations with <a href="chapter_4.1.html#humidity">humidity</a>
-= .T. the atmospheric evaporation leads to a salinity flux in the ocean
-(see e.g. Steinhorn 1991, JPO 21, p. 1681).</p>
-
-<p style="line-height: 100%;">The full MPI-2
-standard must be available in order to use the coupling, and it must be
-activated by adding the preprocessor directive <tt><font style="font-size: 10pt;" size="2">-D__mpi2</font></tt>
-to <tt><font style="font-size: 10pt;" size="2">cpp_options</font></tt>
-in the .mrun.config configuration file. (Note: MPI-2 is
-not available for the IBM-Regatta systems.) To start a
-coupled&nbsp;model run,
-this must be requested with the <b>mrun</b> option <tt><font style="font-size: 10pt;" size="2">-Y</font>.</tt>
-This tells <span style="font-weight: bold;">mrun</span>
-to start two PALM executables. Coupled runs are only possible in
-parallel mode, which means that the <b>mrun</b> option <tt><font style="font-size: 10pt;" size="2">-K parallel</font></tt>
-must also be set.&nbsp;The <b>mrun</b> call
-for coupled runs has to include the following coupling-related options:
-</p>
-
-<ul>
-
-  <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">mrun </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2"> -K parallel -r
-&ldquo;d3# d3o# </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2">&rdquo;</font></tt><tt><font style="font-size: 10pt;" size="2"> </font></tt><tt><font style="font-size: 10pt;" size="2">-X </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2"> -Y</font></tt><tt>.</tt></p>
-
-</ul>
-
-<p style="line-height: 100%;">The <tt><font style="font-size: 10pt;" size="2">-X </font></tt><font style="font-size: 10pt;" size="2">...</font><tt><font style="font-size: 10pt;" size="2">&nbsp;</font></tt>option
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+	<TITLE>PALM chapter 3.8</TITLE>
+	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0  (Unix)">
+	<META NAME="AUTHOR" CONTENT="Siegfried Raasch">
+	<META NAME="CREATED" CONTENT="20040809;13461000">
+	<META NAME="CHANGED" CONTENT="20090624;16024200">
+	<META NAME="KEYWORDS" CONTENT="parallel LES model">
+	<STYLE TYPE="text/css">
+	<!--
+		@page { size: 8.27in 11.69in }
+		P { color: #000000 }
+		H3 { color: #000000 }
+		PRE { color: #000000 }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="en-US" TEXT="#000000" DIR="LTR">
+<H3 STYLE="line-height: 100%">3.8 Coupled model runs</H3>
+<P STYLE="line-height: 100%">Starting from version 3.4 PALM allows
+coupled atmosphere-ocean model runs. By analogy with the modular
+structure of PALM, <B>mrun</B> starts the coupled model as two
+concurrent executables, the atmosphere version and&nbsp;the ocean
+version of PALM.</P>
+<P STYLE="line-height: 100%">Currently, the coupler is at an
+experimental stage using either a MPI2 (more flexible) or a MPI1
+intercommunicator that matches the atmosphere and ocean processors
+one-to-one. This approach has&nbsp;limited flexibility and
+performance, because it requires identical horizontal numerical grids
+and it uses the same number of atmosphere and ocean processors, which
+does not necessarily guarrantee a good load balancing.</P>
+<P STYLE="line-height: 100%">The coupler establishes a one-way
+interaction between the atmosphere and the ocean. The atmosphere
+sends its bottom surface fluxes (temperature, humidity, momentum) to
+the ocean. The ocean sends its top surface temperature to the
+atmosphere. The atmosphere assumes saturation of humidity and zero
+wind speed at its bottom surface. For calculations with <A HREF="chapter_4.1.html#humidity">humidity</A>
+= .T. the atmospheric evaporation leads to a salinity flux in the
+ocean (see e.g. Steinhorn 1991, JPO 21, p. 1681).</P>
+<P STYLE="line-height: 100%">If the full MPI-2 standard is available,
+it can be activated by adding the preprocessor directive <TT><FONT SIZE=2>-D__mpi2</FONT></TT>
+to <TT><FONT SIZE=2>cpp_options</FONT></TT> in the .mrun.config
+configuration file. Otherwise, PALM will use a coupling via MPI1. To
+start a coupled&nbsp;model run, this must be requested with the <B>mrun</B>
+option <TT><FONT SIZE=2>-Y â#1 #2â</FONT></TT><TT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>,
+where </FONT></FONT></TT><TT><FONT FACE="Andale Mono"><FONT SIZE=2>#1</FONT></FONT></TT><TT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>
+is the number of processors for the atmospheric and </FONT></FONT></TT><TT><FONT FACE="Andale Mono"><FONT SIZE=2>#2</FONT></FONT></TT><TT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>
+the number of processors for the oceanic version of PALM (Please note
+that currently only one-to-one topologies are supported and </FONT></FONT></TT><TT><FONT FACE="Andale Mono"><FONT SIZE=2>#1</FONT></FONT></TT><TT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>
+must be equal to </FONT></FONT></TT><TT><FONT FACE="Andale Mono"><FONT SIZE=2>#2</FONT></FONT></TT><TT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>).
+</FONT></FONT></TT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>Thi</FONT></FONT>s
+tells <B>mrun</B> to start two PALM executables. Coupled runs are
+only possible in parallel mode, which means that the <B>mrun</B>
+option <TT><FONT SIZE=2>-K parallel</FONT></TT> must also be set.&nbsp;The
+<B>mrun</B> call for coupled runs has to include the following
+coupling-related options: 
+</P>
+<UL>
+	<P STYLE="line-height: 100%"><TT><FONT SIZE=2>mrun </FONT></TT><FONT SIZE=2>...</FONT><TT>
+	</TT><TT><FONT SIZE=2>-K parallel -r âd3# d3o# </FONT></TT><FONT SIZE=2>...</FONT><TT>â
+	</TT><TT><FONT SIZE=2>-X </FONT></TT><FONT SIZE=2>...</FONT><TT> </TT><TT><FONT SIZE=2>-Y
+	â#1 #2â</FONT></TT><TT>.</TT></P>
+</UL>
+<P STYLE="line-height: 100%">The <TT><FONT SIZE=2>-X </FONT></TT><FONT SIZE=2>...</FONT><TT>&nbsp;</TT>option
 here specifies the total number of processors assigned to the coupled
-model. Currently, half of them are assigned to each of the two coupled
-executables. Therefore it is advisable to specify an even number
-with&nbsp;<tt><font style="font-size: 10pt;" size="2">-X </font></tt><font style="font-size: 10pt;" size="2">...</font><tt>
-</tt>. Otherwise, in case of an odd total number of processors,
-one processor remains idle.</p>
-
-<p style="line-height: 100%;">Each coupled executable has
-its own, unique set of I/O filenames; <a href="chapter_3.4.html#coupled">chapter 3.4</a> gives
-information on file name conventions of coupled runs. The configuration
-file .mrun.config has to be extended for coupled runs. It is
-recommended to duplicate existing file connection identifiers such as
-"d3#", "pr#" etc. using the coupled ocean filenames accordingly. For
-example,&nbsp;the example of the previous chapters could be
-duplicated as follows:</p>
-
-<pre style="line-height: 100%;"><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<br>#</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<br>#<br></font><font style="font-size: 10pt;" size="2">PARIN</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> in:job:npe d3<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/INPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">p3d</font><br><font style="font-size: 10pt;" size="2">PARIN<span style="font-weight: bold;">_O</span> in:job:npe d3<span style="font-weight: bold;">o</span>f ~/palm/current_version/JOBS/$fname/INPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">p3df</font><br><font style="font-size: 10pt;" size="2">BININ</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> in:loc d3<span style="font-weight: bold;">o</span>f ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">d3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><font style="font-size: 10pt;" size="2">BINOUT</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">d3d</font><br><font style="font-size: 10pt;" size="2">#</font><br><font style="font-size: 10pt;" size="2">RUN_CONTROL<span style="font-weight: bold;">_O</span></font><font style="font-size: 10pt;" size="2"> out:loc:tr d3<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/MONITORING <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">rc</font><br><font style="font-size: 10pt;" size="2">HEADER</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> out:loc:tr d3<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/MONITORING <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">header</font><br><font style="font-size: 10pt;" size="2">PLOT1D_PAR<span style="font-weight: bold;">_O</span></font><font style="font-size: 10pt;" size="2"> out:loc:tr pr<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">pr_par</font><br><font style="font-size: 10pt;" size="2">PLOT1D_DATA</font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">_O</span> out:loc:tr pr<span style="font-weight: bold;">o</span># ~/palm/current_version/JOBS/$fname/OUTPUT <span style="font-weight: bold;">_</span></font><font style="font-size: 10pt;" size="2"><span style="font-weight: bold;">o</span>_</font><font style="font-size: 10pt;" size="2">pr_in</font><br></pre>
-
-<p style="line-height: 100%;">The coupled ocean model
-filenames in the first column (e.g.<font style="font-size: 10pt;" size="2"><span style="font-family: mon;"> </span><a href="chapter_3.4.html#PARIN">PARIN_O</a></font>)&nbsp;must
-be specified as given in <a href="chapter_3.4.html#coupled">chapter
-3.4</a>; the file connection identifiers (e.g.&nbsp; <font style="font-size: 10pt;" size="2">d3o#</font>)
-and the file name extension (e.g. &nbsp;<font style="font-size: 10pt;" size="2"><span style="font-weight: bold;"><span style="font-family: mon;"></span></span>_</font><font style="font-size: 10pt;" size="2">o_</font><font style="font-size: 10pt;" size="2">p3d</font>)
-may be changed at the user's discretion.</p>
-
-<p style="line-height: 100%;">The coupler requires the
-following parameters to be equal in both <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
-and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>:
-<a href="chapter_4.1.html#dx">dx</a>, <a href="chapter_4.1.html#dy">dy</a>, <a href="chapter_4.1.html#nx">nx</a>, <a href="chapter_4.1.html#ny">ny</a>, <a href="chapter_4.2.html#dt_coupling">dt_coupling</a>, <a href="chapter_4.2.html#end_time">end_time</a>, <a href="chapter_4.2.html#restart_time">restart_time</a>,
-<a href="chapter_4.2.html#dt_restart">dt_restart</a>.
-In the coupled atmosphere executable,&nbsp;<a href="chapter_4.2.html#bc_pt_b">bc_pt_b</a> is
-internally set and does not need to be prescribed; in the coupled ocean
-executable, <a href="chapter_4.2.html#bc_uv_t">bc_uv_t</a>&nbsp;is
+model. Currently, half of them are assigned to each of the two
+coupled executables. Therefore it is advisable to specify an even
+number with&nbsp;<TT><FONT SIZE=2>-X </FONT></TT><FONT SIZE=2>...</FONT><TT>
+</TT>. Otherwise, in case of an odd total number of processors, one
+processor remains idle.</P>
+<P STYLE="line-height: 100%">Each coupled executable has its own,
+unique set of I/O filenames; <A HREF="chapter_3.4.html#coupled">chapter
+3.4</A> gives information on file name conventions of coupled runs.
+The configuration file .mrun.config has to be extended for coupled
+runs. It is recommended to duplicate existing file connection
+identifiers such as &quot;d3#&quot;, &quot;pr#&quot; etc. using the
+coupled ocean filenames accordingly. For example,&nbsp;the example of
+the previous chapters could be duplicated as follows:</P>
+<PRE STYLE="line-height: 100%"><A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN</FONT></A> <FONT SIZE=2>in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d</FONT>
+<FONT SIZE=2>PARIN in:job:npe d3f ~/palm/current_version/JOBS/$fname/INPUT _p3df</FONT>
+<A HREF="chapter_3.4.html#BININ"><FONT SIZE=2>BININ</FONT></A> <FONT SIZE=2>in:loc d3f ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</FONT>
+<FONT SIZE=2>#</FONT>
+<A HREF="chapter_3.4.html#BINOUT"><FONT SIZE=2>BINOUT</FONT></A> <FONT SIZE=2>out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT _d3d</FONT>
+<FONT SIZE=2>#</FONT>
+<A HREF="chapter_3.4.html#RUN_CONTROL"><FONT SIZE=2>RUN_CONTROL</FONT></A> <FONT SIZE=2>out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _rc</FONT>
+<A HREF="chapter_3.4.html#HEADER"><FONT SIZE=2>HEADER</FONT></A> <FONT SIZE=2>out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _header</FONT>
+<A HREF="chapter_3.4.html#PLOT1D_PAR"><FONT SIZE=2>PLOT1D_PAR</FONT></A> <FONT SIZE=2>out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_par</FONT>
+<A HREF="chapter_3.4.html#PLOT1D_DATA"><FONT SIZE=2>PLOT1D_DATA</FONT></A> <FONT SIZE=2>out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_in</FONT>
+<FONT SIZE=2>#</FONT>
+<FONT SIZE=2>PARIN</FONT><FONT SIZE=2><B>_O</B></FONT><FONT SIZE=2> in:job:npe d3</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2># ~/palm/current_version/JOBS/$fname/INPUT </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_p3d</FONT>
+<FONT SIZE=2>PARIN</FONT><FONT SIZE=2><B>_O</B></FONT><FONT SIZE=2> in:job:npe d3</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2>f ~/palm/current_version/JOBS/$fname/INPUT </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_p3df</FONT>
+<FONT SIZE=2>BININ</FONT><FONT SIZE=2><B>_O</B></FONT><FONT SIZE=2> in:loc d3</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2>f ~/palm/current_version/JOBS/$fname/OUTPUT </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_d3d</FONT>
+<FONT SIZE=2>#</FONT>
+<FONT SIZE=2>BINOUT</FONT><FONT SIZE=2><B>_O</B></FONT><FONT SIZE=2> out:loc restart ~/palm/current_version/JOBS/$fname/OUTPUT </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_d3d</FONT>
+<FONT SIZE=2>#</FONT>
+<FONT SIZE=2>RUN_CONTROL</FONT><FONT SIZE=2><B>_O</B></FONT> <FONT SIZE=2>out:loc:tr d3</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2># ~/palm/current_version/JOBS/$fname/MONITORING </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_rc</FONT>
+<FONT SIZE=2>HEADER</FONT><FONT SIZE=2><B>_O</B></FONT><FONT SIZE=2> out:loc:tr d3</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2># ~/palm/current_version/JOBS/$fname/MONITORING </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_header</FONT>
+<FONT SIZE=2>PLOT1D_PAR</FONT><FONT SIZE=2><B>_O</B></FONT> <FONT SIZE=2>out:loc:tr pr</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2># ~/palm/current_version/JOBS/$fname/OUTPUT </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_pr_par</FONT>
+<FONT SIZE=2>PLOT1D_DATA</FONT><FONT SIZE=2><B>_O</B></FONT><FONT SIZE=2> out:loc:tr pr</FONT><FONT SIZE=2><B>o</B></FONT><FONT SIZE=2># ~/palm/current_version/JOBS/$fname/OUTPUT </FONT><FONT SIZE=2><B>_o</B></FONT><FONT SIZE=2>_pr_in</FONT></PRE><P STYLE="line-height: 100%">
+The coupled ocean model filenames in the first column (e.g.
+<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>)&nbsp;must
+be specified as given in <A HREF="chapter_3.4.html#coupled">chapter
+3.4</A>; the file connection identifiers (e.g.&nbsp; <FONT SIZE=2>d3o#</FONT>)
+and the file name extension (e.g. &nbsp;<FONT SIZE=2>_o_p3d</FONT>)
+may be changed at the user's discretion.</P>
+<P STYLE="line-height: 100%">The coupler requires the following
+parameters to be equal in both <A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN</FONT></A>
+and&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>:
+<A HREF="chapter_4.1.html#dx">dx</A>, <A HREF="chapter_4.1.html#dy">dy</A>,
+<A HREF="chapter_4.1.html#nx">nx</A>, <A HREF="chapter_4.1.html#ny">ny</A>,
+<A HREF="chapter_4.2.html#dt_coupling">dt_coupling</A>, <A HREF="chapter_4.2.html#end_time">end_time</A>,
+<A HREF="chapter_4.2.html#restart_time">restart_time</A>, <A HREF="chapter_4.2.html#dt_restart">dt_restart</A>.
+In the coupled atmosphere executable,&nbsp;<A HREF="chapter_4.2.html#bc_pt_b">bc_pt_b</A>
+is internally set and does not need to be prescribed; in the coupled
+ocean executable, <A HREF="chapter_4.2.html#bc_uv_t">bc_uv_t</A>&nbsp;is
 internally set ('neumann') and does not need to be prescribed. The
-coupled ocean parameter file&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>
-should include dummy REAL value assignments to both <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a>
-and&nbsp;<a href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a>
+coupled ocean parameter file&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>
+should include dummy REAL value assignments to both
+<A HREF="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</A>
+and&nbsp;<A HREF="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</A>
 (e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to
-enable the momentum flux coupling.</p>
-
-<p style="line-height: 100%;">The coupling interval <a href="chapter_4.2.html#dt_coupling">dt_coupling</a>
+enable the momentum flux coupling.</P>
+<P STYLE="line-height: 100%">The coupling interval <A HREF="chapter_4.2.html#dt_coupling">dt_coupling</A>
 must be explicity set. In order to ensure synchronous coupling
-throughout the simulation, <a href="chapter_4.2.html#dt_coupling">dt_coupling</a>
-should be chosen larger than
-<a href="chapter_4.2.html#dt_max">dt_max</a>.</p>
-
-<hr>
-<p style="line-height: 100%;"><br>
-
-<font color="#000080"><font color="#000080"><a href="chapter_3.7.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="left.gif" name="Grafik1"></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.9.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="right.gif" name="Grafik3"></font></a></font></font></p>
-
-<p style="line-height: 100%;"><i>Last
-change:&nbsp;</i> $Id$</p>
-
-</body></html>
+throughout the simulation, <A HREF="chapter_4.2.html#dt_coupling">dt_coupling</A>
+should be chosen larger than <A HREF="chapter_4.2.html#dt_max">dt_max</A>.</P>
+<P STYLE="line-height: 100%">It's also possible to perform precursor
+runs (one atmospheric and one oceanic) followed by a coupled restart
+run. In order to achieve this, the parameter <A HREF="chapter_4.1.html#coupling_start_time">coupling_time_start</A>
+must be set according to the <A HREF="../misc/precursor_run_control.pdf">documentation.</A></P>
+<HR>
+<P STYLE="line-height: 100%"><BR><FONT COLOR="#000080"><A HREF="chapter_3.7.html"><FONT COLOR="#000000"><IMG SRC="left.gif" NAME="Grafik1" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A><A HREF="index.html"><FONT COLOR="#000080"><IMG SRC="up.gif" NAME="Grafik2" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A><A HREF="chapter_3.9.html"><FONT COLOR="#000000"><IMG SRC="right.gif" NAME="Grafik3" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A></FONT></P>
+<P STYLE="line-height: 100%"><I>Last change:&nbsp;</I> $Id:
+chapter_3.8.html 197 2008-09-16 15:29:03Z raasch $</P>
+</BODY>
+</HTML>
Index: /palm/trunk/DOC/app/chapter_4.1.html
===================================================================
--- /palm/trunk/DOC/app/chapter_4.1.html	(revision 343)
+++ /palm/trunk/DOC/app/chapter_4.1.html	(revision 344)
@@ -1,17078 +1,4401 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html><head>
-
-
-
-
-
-
-
-  
-  
-  
-  
-  
-  
-  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
-
-
-
-
-
-
-  
-  
-  
-  
-  
-  
-  <title>PALM chapter 4.1</title></head>
-<body>
-
-
-
-
-
-
-<h3><a name="chapter4.1"></a>4.1
-Initialization parameters</h3>
-
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
-
-
-
-
-
-
- <tbody>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><font size="4"><b>Parameter name</b></font></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><b><font size="4">Default</font></b> <br>
-
-
-
-
-
-
- <b><font size="4">value</font></b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="adjust_mixing_length"></a><b>adjust_mixing_length</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Near-surface adjustment of the
-mixing length to the Prandtl-layer law.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Usually
-the mixing length in LES models l<sub>LES</sub>
-depends (as in PALM) on the grid size and is possibly restricted
-further in case of stable stratification and near the lower wall (see
-parameter <a href="#wall_adjustment">wall_adjustment</a>).
-With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span>
-the Prandtl' mixing length l<sub>PR</sub> = kappa * z/phi
-is calculated
-and the mixing length actually used in the model is set l = MIN (l<sub>LES</sub>,
-l<sub>PR</sub>). This usually gives a decrease of the
-mixing length at
-the bottom boundary and considers the fact that eddy sizes
-decrease in the vicinity of the wall.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;"><b>Warning:</b> So
-far, there is
-no good experience with <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> !&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>With <b>adjust_mixing_length</b> = <span style="font-style: italic;">.T.</span> and the
-Prandtl-layer being
-switched on (see <a href="#prandtl_layer">prandtl_layer</a>)
-      <span style="font-style: italic;">'(u*)** 2+neumann'</span>
-should always be set as the lower boundary condition for the TKE (see <a href="#bc_e_b">bc_e_b</a>),
-otherwise the near-surface value of the TKE is not in agreement with
-the Prandtl-layer law (Prandtl-layer law and Prandtl-Kolmogorov-Ansatz
-should provide the same value for K<sub>m</sub>). A warning
-is given,
-if this is not the case.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="alpha_surface"></a><b>alpha_surface</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Inclination of the model domain
-with respect to the horizontal (in degrees).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">By means of <b>alpha_surface</b>
-the model domain can be inclined in x-direction with respect to the
-horizontal. In this way flows over inclined surfaces (e.g. drainage
-flows, gravity flows) can be simulated. In case of <b>alpha_surface
-      </b>/= <span style="font-style: italic;">0</span>
-the buoyancy term
-appears both in
-the equation of motion of the u-component and of the w-component.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">An inclination
-is only possible in
-case of cyclic horizontal boundary conditions along x AND y (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>) and <a href="#topography">topography</a> = <span style="font-style: italic;">'flat'</span>. </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Runs with inclined surface still require additional
-user-defined code as well as modifications to the default code. Please
-ask the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">PALM
-developer&nbsp; group</a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_e_b"></a><b>bc_e_b</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-TKE.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><b>bc_e_b</b> may be
-set to&nbsp;<span style="font-style: italic;">'neumann'</span>
-or <span style="font-style: italic;">'(u*) ** 2+neumann'</span>.
-      <b>bc_e_b</b>
-= <span style="font-style: italic;">'neumann'</span>
-yields to
-e(k=0)=e(k=1) (Neumann boundary condition), where e(k=1) is calculated
-via the prognostic TKE equation. Choice of <span style="font-style: italic;">'(u*)**2+neumann'</span>
-also yields to
-e(k=0)=e(k=1), but the TKE at the Prandtl-layer top (k=1) is calculated
-diagnostically by e(k=1)=(us/0.1)**2. However, this is only allowed if
-a Prandtl-layer is used (<a href="#prandtl_layer">prandtl_layer</a>).
-If this is not the case, a warning is given and <b>bc_e_b</b>
-is reset
-to <span style="font-style: italic;">'neumann'</span>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">At the top
-boundary a Neumann
-boundary condition is generally used: (e(nz+1) = e(nz)).</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_lr"></a><b>bc_lr</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Boundary
-condition along x (for all quantities).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-By default, a cyclic boundary condition is used along x.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">bc_lr</span> may
-also be
-assigned the values <span style="font-style: italic;">'dirichlet/radiation'</span>
-(inflow from left, outflow to the right) or <span style="font-style: italic;">'radiation/dirichlet'</span>
-(inflow from
-right, outflow to the left). This requires the multi-grid method to be
-used for solving the Poisson equation for perturbation pressure (see <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</a>)
-and it also requires cyclic boundary conditions along y (see&nbsp;<a href="#bc_ns">bc_ns</a>).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-In case of these non-cyclic lateral boundaries, a Dirichlet condition
-is used at the inflow for all quantities (initial vertical profiles -
-see <a href="#initializing_actions">initializing_actions</a>
-- are fixed during the run) except u, to which a Neumann (zero
-gradient) condition is applied. At the outflow, a radiation condition is used for all velocity components, while a Neumann (zero
-gradient) condition is used for the scalars. For perturbation
-pressure Neumann (zero gradient) conditions are assumed both at the
-inflow and at the outflow.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-When using non-cyclic lateral boundaries, a filter is applied to the
-velocity field in the vicinity of the outflow in order to suppress any
-reflections of outgoing disturbances (see <a href="#km_damp_max">km_damp_max</a>
-and <a href="#outflow_damping_width">outflow_damping_width</a>).<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-In order to maintain a turbulent state of the flow, it may be
-neccessary to continuously impose perturbations on the horizontal
-velocity field in the vicinity of the inflow throughout the whole run.
-This can be switched on using <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#create_disturbances">create_disturbances</a>.
-The horizontal range to which these perturbations are applied is
-controlled by the parameters <a href="#inflow_disturbance_begin">inflow_disturbance_begin</a>
-and <a href="#inflow_disturbance_end">inflow_disturbance_end</a>.
-The vertical range and the perturbation amplitude are given by <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_b</a>,
-      <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_t</a>,
-and <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_amplitude</a>.
-The time interval at which perturbations are to be imposed is set by <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#dt_disturb">dt_disturb</a>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-In case of non-cyclic horizontal boundaries <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#call_psolver_at_all_substeps">call_psolver
-at_all_substeps</a> = .T. should be used.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-weight: bold;">Note:</span><br>
-
-
-
-
-
-
-
-Using non-cyclic lateral boundaries requires very sensitive adjustments
-of the inflow (vertical profiles) and the bottom boundary conditions,
-e.g. a surface heating should not be applied near the inflow boundary
-because this may significantly disturb the inflow. Please check the
-model results very carefully.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_ns"></a><b>bc_ns</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'cyclic'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Boundary
-condition along y (for all quantities).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-By default, a cyclic boundary condition is used along y.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-      <span style="font-weight: bold;">bc_ns</span> may
-also be
-assigned the values <span style="font-style: italic;">'dirichlet/radiation'</span>
-(inflow from rear ("north"), outflow to the front ("south")) or <span style="font-style: italic;">'radiation/dirichlet'</span>
-(inflow from front ("south"), outflow to the rear ("north")). This
-requires the multi-grid
-method to be used for solving the Poisson equation for perturbation
-pressure (see <a href="chapter_4.2.html#psolver">psolver</a>)
-and it also requires cyclic boundary conditions along x (see<br>
-
-
-
-
-
-
- <a href="#bc_lr">bc_lr</a>).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-In case of these non-cyclic lateral boundaries, a Dirichlet condition
-is used at the inflow for all quantities (initial vertical profiles -
-see <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>
-- are fixed during the run) except u, to which a Neumann (zero
-gradient) condition is applied. At the outflow, a radiation condition is used for all velocity components, while a Neumann (zero
-gradient) condition is used for the scalars. For perturbation
-pressure Neumann (zero gradient) conditions are assumed both at the
-inflow and at the outflow.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-For further details regarding non-cyclic lateral boundary conditions
-see <a href="#bc_lr">bc_lr</a>.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_p_b"></a><b>bc_p_b</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-perturbation pressure.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed values
-are <span style="font-style: italic;">'dirichlet'</span>,
-      <span style="font-style: italic;">'neumann'</span>
-and <span style="font-style: italic;">'neumann+inhomo'</span>.&nbsp;
-      <span style="font-style: italic;">'dirichlet'</span>
-sets
-p(k=0)=0.0,&nbsp; <span style="font-style: italic;">'neumann'</span>
-sets p(k=0)=p(k=1). <span style="font-style: italic;">'neumann+inhomo'</span>
-corresponds to an extended Neumann boundary condition where heat flux
-or temperature inhomogeneities near the
-surface (pt(k=1))&nbsp; are additionally regarded (see Shen and
-LeClerc
-(1995, Q.J.R. Meteorol. Soc.,
-1209)). This condition is only permitted with the Prandtl-layer
-switched on (<a href="#prandtl_layer">prandtl_layer</a>),
-otherwise the run is terminated.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Since
-at the bottom boundary of the model the vertical
-velocity
-disappears (w(k=0) = 0.0), the consistent Neumann condition (<span style="font-style: italic;">'neumann'</span> or <span style="font-style: italic;">'neumann+inhomo'</span>)
-dp/dz = 0 should
-be used, which leaves the vertical component w unchanged when the
-pressure solver is applied. Simultaneous use of the Neumann boundary
-conditions both at the bottom and at the top boundary (<a href="#bc_p_t">bc_p_t</a>)
-usually yields no consistent solution for the perturbation pressure and
-should be avoided.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_p_t"></a><b>bc_p_t</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-perturbation pressure.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Allowed values are <span style="font-style: italic;">'dirichlet'</span>
-(p(k=nz+1)= 0.0) or <span style="font-style: italic;">'neumann'</span>
-(p(k=nz+1)=p(k=nz)).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Simultaneous use
-of Neumann boundary conditions both at the
-top and bottom boundary (<a href="#bc_p_b">bc_p_b</a>)
-usually yields no consistent solution for the perturbation pressure and
-should be avoided. Since at the bottom boundary the Neumann
-condition&nbsp; is a good choice (see <a href="#bc_p_b">bc_p_b</a>),
-a Dirichlet condition should be set at the top boundary.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_pt_b"></a><b>bc_pt_b</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C*20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-potential temperature.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed values
-are <span style="font-style: italic;">'dirichlet'</span>
-(pt(k=0) = const. = <a href="#pt_surface">pt_surface</a>
-+ <a href="#pt_surface_initial_change">pt_surface_initial_change</a>;
-the user may change this value during the run using user-defined code)
-and <span style="font-style: italic;">'neumann'</span>
-(pt(k=0)=pt(k=1)).&nbsp; <br>
-
-
-
-
-
-
-
-When a constant surface sensible heat flux is used (<a href="#surface_heatflux">surface_heatflux</a>), <b>bc_pt_b</b>
-= <span style="font-style: italic;">'neumann'</span>
-must be used, because otherwise the resolved scale may contribute to
-the surface flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>In the <a href="chapter_3.8.html">coupled</a> atmosphere executable,&nbsp;<a href="chapter_4.2.html#bc_pt_b">bc_pt_b</a> is internally set and does not need to be prescribed.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="pc_pt_t"></a><b>bc_pt_t</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'initial_ gradient'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-potential temperature.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed are the
-values <span style="font-style: italic;">'dirichlet' </span>(pt(k=nz+1)
-does not change during the run), <span style="font-style: italic;">'neumann'</span>
-(pt(k=nz+1)=pt(k=nz)), and <span style="font-style: italic;">'initial_gradient'</span>.
-With the 'initial_gradient'-condition the value of the temperature
-gradient at the top is
-calculated from the initial
-temperature profile (see <a href="#pt_surface">pt_surface</a>,
-      <a href="#pt_vertical_gradient">pt_vertical_gradient</a>)
-by bc_pt_t_val = (pt_init(k=nz+1) -
-pt_init(k=nz)) / dzu(nz+1).<br>
-
-
-
-
-
-
-
-Using this value (assumed constant during the
-run) the temperature boundary values are calculated as&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">pt(k=nz+1) =
-pt(k=nz) +
-bc_pt_t_val * dzu(nz+1)</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">(up to k=nz the prognostic
-equation for the temperature is solved).<br>
-
-
-
-
-
-
-
-When a constant sensible heat flux is used at the top boundary (<a href="chapter_4.1.html#top_heatflux">top_heatflux</a>),
-      <b>bc_pt_t</b> = <span style="font-style: italic;">'neumann'</span>
-must be used, because otherwise the resolved scale may contribute to
-the top flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_q_b"></a><b>bc_q_b</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-specific humidity / total water content.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed
-values are <span style="font-style: italic;">'dirichlet'</span>
-(q(k=0) = const. = <a href="#q_surface">q_surface</a>
-+ <a href="#q_surface_initial_change">q_surface_initial_change</a>;
-the user may change this value during the run using user-defined code)
-and <span style="font-style: italic;">'neumann'</span>
-(q(k=0)=q(k=1)).&nbsp; <br>
-
-
-
-
-
-
-
-When a constant surface latent heat flux is used (<a href="#surface_waterflux">surface_waterflux</a>), <b>bc_q_b</b>
-= <span style="font-style: italic;">'neumann'</span>
-must be used, because otherwise the resolved scale may contribute to
-the surface flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_q_t"></a><b>bc_q_t</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">C
-* 20</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-specific humidity / total water content.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed
-are the values <span style="font-style: italic;">'dirichlet'</span>
-(q(k=nz) and q(k=nz+1) do
-not change during the run) and <span style="font-style: italic;">'neumann'</span>.
-With the Neumann boundary
-condition the value of the humidity gradient at the top is calculated
-from the
-initial humidity profile (see <a href="#q_surface">q_surface</a>,
-      <a href="#q_vertical_gradient">q_vertical_gradient</a>)
-by: bc_q_t_val = ( q_init(k=nz) - q_init(k=nz-1)) / dzu(nz).<br>
-
-
-
-
-
-
-
-Using this value (assumed constant during the run) the humidity
-boundary values
-are calculated as&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">q(k=nz+1) =q(k=nz) +
-bc_q_t_val * dzu(nz+1)</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">(up tp k=nz the prognostic
-equation for q is solved). </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_s_b"></a><b>bc_s_b</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-scalar concentration.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed values
-are <span style="font-style: italic;">'dirichlet'</span>
-(s(k=0) = const. = <a href="#s_surface">s_surface</a>
-+ <a href="#s_surface_initial_change">s_surface_initial_change</a>;
-the user may change this value during the run using user-defined code)
-and <span style="font-style: italic;">'neumann'</span>
-(s(k=0) =
-s(k=1)).&nbsp; <br>
-
-
-
-
-
-
-
-When a constant surface concentration flux is used (<a href="#surface_scalarflux">surface_scalarflux</a>), <b>bc_s_b</b>
-= <span style="font-style: italic;">'neumann'</span>
-must be used, because otherwise the resolved scale may contribute to
-the surface flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_s_t"></a><b>bc_s_t</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-scalar concentration.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed are the
-values <span style="font-style: italic;">'dirichlet'</span>
-(s(k=nz) and s(k=nz+1) do
-not change during the run) and <span style="font-style: italic;">'neumann'</span>.
-With the Neumann boundary
-condition the value of the scalar concentration gradient at the top is
-calculated
-from the initial scalar concentration profile (see <a href="#s_surface">s_surface</a>, <a href="#s_vertical_gradient">s_vertical_gradient</a>)
-by: bc_s_t_val = (s_init(k=nz) - s_init(k=nz-1)) / dzu(nz).<br>
-
-
-
-
-
-
-
-Using this value (assumed constant during the run) the concentration
-boundary values
-are calculated as </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">s(k=nz+1) = s(k=nz) +
-bc_s_t_val * dzu(nz+1)</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">(up to k=nz the prognostic
-equation for the scalar concentration is
-solved).</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="bc_sa_t"></a><span style="font-weight: bold;">bc_sa_t</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the salinity.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This parameter only comes into effect for ocean runs (see parameter <a href="#ocean">ocean</a>).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Allowed are the
-values <span style="font-style: italic;">'dirichlet' </span>(sa(k=nz+1)
-does not change during the run) and <span style="font-style: italic;">'neumann'</span>
-(sa(k=nz+1)=sa(k=nz))<span style="font-style: italic;"></span>.&nbsp;<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-When a constant salinity flux is used at the top boundary (<a href="chapter_4.1.html#top_salinityflux">top_salinityflux</a>),
-      <b>bc_sa_t</b> = <span style="font-style: italic;">'neumann'</span>
-must be used, because otherwise the resolved scale may contribute to
-the top flux so that a constant value cannot be guaranteed.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_uv_b"></a><b>bc_uv_b</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Bottom boundary condition of the
-horizontal velocity components u and v.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed
-values are <span style="font-style: italic;">'dirichlet' </span>and
-      <span style="font-style: italic;">'neumann'</span>. <b>bc_uv_b</b>
-= <span style="font-style: italic;">'dirichlet'</span>
-yields the
-no-slip condition with u=v=0 at the bottom. Due to the staggered grid
-u(k=0) and v(k=0) are located at z = - 0,5 * <a href="#dz">dz</a>
-(below the bottom), while u(k=1) and v(k=1) are located at z = +0,5 *
-dz. u=v=0 at the bottom is guaranteed using mirror boundary
-condition:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p style="font-style: normal;">u(k=0) = - u(k=1) and v(k=0) = -
-v(k=1)</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">The
-Neumann boundary condition
-yields the free-slip condition with u(k=0) = u(k=1) and v(k=0) =
-v(k=1).
-With Prandtl - layer switched on (see <a href="#prandtl_layer">prandtl_layer</a>), the free-slip condition is not
-allowed (otherwise the run will be terminated)<font color="#000000">.</font></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="bc_uv_t"></a><b>bc_uv_t</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'dirichlet'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Top boundary condition of the
-horizontal velocity components u and v.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Allowed
-values are <span style="font-style: italic;">'dirichlet'</span>, <span style="font-style: italic;">'dirichlet_0'</span>
-and <span style="font-style: italic;">'neumann'</span>.
-The
-Dirichlet condition yields u(k=nz+1) = ug(nz+1) and v(k=nz+1) =
-vg(nz+1),
-Neumann condition yields the free-slip condition with u(k=nz+1) =
-u(k=nz) and v(k=nz+1) = v(k=nz) (up to k=nz the prognostic equations
-for the velocities are solved). The special condition&nbsp;<span style="font-style: italic;">'dirichlet_0'</span> can be used for channel flow, it yields the no-slip condition u(k=nz+1) = ug(nz+1) = 0 and v(k=nz+1) =
-vg(nz+1) = 0.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>In the <a href="chapter_3.8.html">coupled</a> ocean executable, <a href="chapter_4.2.html#bc_uv_t">bc_uv_t</a>&nbsp;is internally set ('neumann') and does not need to be prescribed.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="bottom_salinityflux"></a><span style="font-weight: bold;">bottom_salinityflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p>Kinematic salinity flux near the surface (in psu m/s).&nbsp;</p>
-
-
-
-
-
-
-This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).
-      
-      
-      
-      
-      
-      
-      <p>The
-respective salinity flux value is used
-as bottom (horizontally homogeneous) boundary condition for the salinity equation. This additionally requires that a Neumann
-condition must be used for the salinity, which is currently the only available condition.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_height"></a>building_height</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
-
-
-
-
-
-
- <td>Height
-of a single building in m.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-weight: bold;">building_height</span> must
-be less than the height of the model domain. This parameter requires
-the use of&nbsp;<a href="#topography">topography</a>
-= <span style="font-style: italic;">'single_building'</span>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_x"></a>building_length_x</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
-
-
-
-
-
-
- <td><span style="font-style: italic;"></span>Width of a single
-building in m.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_length_x</span>
-must be at least <span style="font-style: italic;">3
-*&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#nx">nx</a><span style="font-style: italic;"> - 1 ) </span><span style="font-style: italic;"> * <a href="#dx">dx</a>
-      </span><span style="font-style: italic;">- <a href="#building_wall_left">building_wall_left</a></span>.
-This parameter requires the use of&nbsp;<a href="#topography">topography</a>
-= <span style="font-style: italic;">'single_building'</span>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_length_y"></a>building_length_y</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">50.0</span></td>
-
-
-
-
-
-
- <td>Depth
-of a single building in m.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_length_y</span>
-must be at least <span style="font-style: italic;">3
-*&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="#ny">ny</a><span style="font-style: italic;"> - 1 )&nbsp;</span><span style="font-style: italic;"> * <a href="#dy">dy</a></span><span style="font-style: italic;"> - <a href="#building_wall_south">building_wall_south</a></span>. This parameter requires
-the use of&nbsp;<a href="#topography">topography</a>
-= <span style="font-style: italic;">'single_building'</span>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_left"></a>building_wall_left</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">building centered in x-direction</span></td>
-
-
-
-
-
-
-
-      <td>x-coordinate of the left building wall (distance between the
-left building wall and the left border of the model domain) in m.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_wall_left</span>
-must be at least <span style="font-style: italic;">1
-*&nbsp;</span><a style="font-style: italic;" href="#dx">dx</a> and less than <span style="font-style: italic;">( <a href="#nx">nx</a>&nbsp;
-- 1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a></span>.
-This parameter requires the use of&nbsp;<a href="#topography">topography</a>
-= <span style="font-style: italic;">'single_building'</span>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-The default value&nbsp;<span style="font-weight: bold;">building_wall_left</span>
-= <span style="font-style: italic;">( ( <a href="#nx">nx</a>&nbsp;+
-1 ) * <a href="#dx">dx</a> -&nbsp; <a href="#building_length_x">building_length_x</a> ) / 2</span>
-centers the building in x-direction.&nbsp;<font color="#000000">Due to the staggered grid the building will be displaced by -0.5 <a href="chapter_4.1.html#dx">dx</a> in x-direction and -0.5 <a href="chapter_4.1.html#dy">dy</a> in y-direction.</font> </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="building_wall_south"></a>building_wall_south</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;"></span><span style="font-style: italic;">building centered in y-direction</span></td>
-
-
-
-
-
-
-
-      <td>y-coordinate of the South building wall (distance between the
-South building wall and the South border of the model domain) in m.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">building_wall_south</span>
-must be at least <span style="font-style: italic;">1
-*&nbsp;</span><a style="font-style: italic;" href="#dy">dy</a> and less than <span style="font-style: italic;">( <a href="#ny">ny</a>&nbsp;
-- 1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a></span>.
-This parameter requires the use of&nbsp;<a href="#topography">topography</a>
-= <span style="font-style: italic;">'single_building'</span>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-The default value&nbsp;<span style="font-weight: bold;">building_wall_south</span>
-= <span style="font-style: italic;">( ( <a href="#ny">ny</a>&nbsp;+
-1 ) * <a href="#dy">dy</a> -&nbsp; <a href="#building_length_y">building_length_y</a> ) / 2</span>
-centers the building in y-direction.&nbsp;<font color="#000000">Due to the staggered grid the building will be displaced by -0.5 <a href="chapter_4.1.html#dx">dx</a> in x-direction and -0.5 <a href="chapter_4.1.html#dy">dy</a> in y-direction.</font> </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-      <td style="vertical-align: top;"><a name="canopy_mode"></a><span style="font-weight: bold;">canopy_mode</span></td>
-
-      <td style="vertical-align: top;">C * 20</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'block'</span></td>
-
-      <td style="vertical-align: top;">Canopy mode.<br>
-
-      <br>
-
-      <font color="#000000">
-Besides using the default value, that will create a horizontally
-homogeneous plant canopy that extends over the total horizontal
-extension of the model domain, the user may add code to the user
-interface subroutine <a href="chapter_3.5.1.html#user_init_plant_canopy">user_init_plant_canopy</a>
-to allow further canopy&nbsp;modes. <br>
-
-      <br>
-
-The setting of <a href="#canopy_mode">canopy_mode</a> becomes only active, if&nbsp;<a href="#plant_canopy">plant_canopy</a> has been set <span style="font-style: italic;">.T.</span> and a non-zero <a href="#drag_coefficient">drag_coefficient</a> has been defined.</font></td>
-
-    </tr>
-
-    <tr><td style="font-weight: bold; vertical-align: top;"><a name="canyon_height"></a>canyon_height</td><td style="vertical-align: top;">R</td><td style="font-style: italic; vertical-align: top;">50.0</td><td>Street canyon height
-in m.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-weight: bold;">canyon_height</span> must
-be less than the height of the model domain. This parameter requires&nbsp;<a href="chapter_4.1.html#topography">topography</a>
-= <span style="font-style: italic;">'single_street_canyon'</span>.</td></tr><tr><td style="font-weight: bold; vertical-align: top;"><a name="canyon_width_x"></a>canyon_width_x</td><td style="vertical-align: top;">R</td><td style="font-style: italic; vertical-align: top;">9999999.9</td><td>Street canyon width in x-direction in m.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">canyon_width_x</span>
-must be at least <span style="font-style: italic;">3
-*&nbsp;</span><a style="font-style: italic;" href="chapter_4.1.html#dx">dx</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="chapter_4.1.html#nx">nx</a><span style="font-style: italic;"> - 1 ) </span><span style="font-style: italic;"> * <a href="chapter_4.1.html#dx">dx</a>
-      </span><span style="font-style: italic;">- <a href="chapter_4.1.html#canyon_wall_left">canyon_wall_left</a></span>.
-This parameter requires&nbsp;<a href="chapter_4.1.html#topography">topography</a>
-= <span style="font-style: italic;">'</span><span style="font-style: italic;">single_street_canyon</span><span style="font-style: italic;">'</span>. A non-default value implies a canyon orientation in y-direction.</td></tr><tr><td style="font-weight: bold; vertical-align: top;"><a name="canyon_width_y"></a>canyon_width_y</td><td style="vertical-align: top;">R</td><td style="font-style: italic; vertical-align: top;">9999999.9</td><td>Street canyon width in y-direction in m.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">canyon_width_y</span>
-must be at least <span style="font-style: italic;">3
-*&nbsp;</span><a style="font-style: italic;" href="chapter_4.1.html#dy">dy</a> and no more than <span style="font-style: italic;">(&nbsp;</span><a style="font-style: italic;" href="chapter_4.1.html#ny">ny</a><span style="font-style: italic;"> - 1 )&nbsp;</span><span style="font-style: italic;"> * <a href="chapter_4.1.html#dy">dy</a></span><span style="font-style: italic;"> - <a href="chapter_4.1.html#canyon_wall_south">canyon_wall_south</a></span>. This parameter requires&nbsp;<a href="chapter_4.1.html#topography">topography</a>
-= <span style="font-style: italic;">'</span><span style="font-style: italic;">single_street_canyon</span>.&nbsp;A non-default value implies a canyon orientation in x-direction.</td></tr><tr><td style="font-weight: bold; vertical-align: top;"><a name="canyon_wall_left"></a>canyon_wall_left</td><td style="vertical-align: top;">R</td><td style="font-style: italic; vertical-align: top;"><span style="font-style: italic;">canyon centered in x-direction</span></td><td>x-coordinate of the left canyon wall (distance between the
-left canyon wall and the left border of the model domain) in m.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">canyon_wall_left</span>
-must be at least <span style="font-style: italic;">1
-*&nbsp;</span><a style="font-style: italic;" href="chapter_4.1.html#dx">dx</a> and less than <span style="font-style: italic;">( <a href="chapter_4.1.html#nx">nx</a>&nbsp;
-- 1 ) * <a href="chapter_4.1.html#dx">dx</a> -&nbsp; <a href="chapter_4.1.html#canyon_width_x">canyon_width_x</a></span>.
-This parameter requires&nbsp;<a href="chapter_4.1.html#topography">topography</a>
-= <span style="font-style: italic;">'</span><span style="font-style: italic;">single_street_canyon</span><span style="font-style: italic;">'</span>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-The default value <span style="font-weight: bold;">canyon_wall_left</span>
-= <span style="font-style: italic;">( ( <a href="chapter_4.1.html#nx">nx</a>&nbsp;+
-1 ) * <a href="chapter_4.1.html#dx">dx</a> -&nbsp; <a href="chapter_4.1.html#canyon_width_x">canyon_width_x</a> ) / 2</span>
-centers the canyon in x-direction.</td></tr><tr><td style="font-weight: bold; vertical-align: top;"><a name="canyon_wall_south"></a>canyon_wall_south</td><td style="vertical-align: top;">R</td><td style="font-style: italic; vertical-align: top;"><span style="font-style: italic;">canyon centered in y-direction</span></td><td>y-coordinate of the South canyon wall (distance between the
-South canyon wall and the South border of the model domain) in m.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-Currently, <span style="font-weight: bold;">canyon_wall_south</span>
-must be at least <span style="font-style: italic;">1
-*&nbsp;</span><a style="font-style: italic;" href="chapter_4.1.html#dy">dy</a> and less than <span style="font-style: italic;">( <a href="chapter_4.1.html#ny">ny</a>&nbsp;
-- 1 ) * <a href="chapter_4.1.html#dy">dy</a> -&nbsp; <a href="chapter_4.1.html#canyon_width_y">canyon_width_y</a></span>.
-This parameter requires&nbsp;<a href="chapter_4.1.html#topography">topography</a>
-= <span style="font-style: italic;">'</span><span style="font-style: italic;">single_street_canyon</span><span style="font-style: italic;">'</span>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-The default value <span style="font-weight: bold;">canyon_wall_south</span>
-= <span style="font-style: italic;">( ( <a href="chapter_4.1.html#ny">ny</a>&nbsp;+
-1 ) * <a href="chapter_4.1.html#dy">dy</a> -&nbsp;&nbsp;</span><a href="chapter_4.1.html#building_length_y"><span style="font-style: italic;"></span></a><a style="font-style: italic;" href="chapter_4.1.html#canyon_width_y">canyon_wid</a><span style="font-style: italic;"><a style="font-style: italic;" href="chapter_4.1.html#canyon_width_y">th_y</a> ) / 2</span>
-centers the canyon in y-direction.</td></tr><tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="cloud_droplets"></a>cloud_droplets</span><br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Parameter to switch on
-usage of cloud droplets.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-      <span style="font-weight: bold;"></span><span style="font-family: monospace;"></span>
-
-
-
-
-Cloud droplets require to use&nbsp;particles (i.e. the NAMELIST group <span style="font-family: Courier New,Courier,monospace;">particles_par</span> has to be included in the parameter file<span style="font-family: monospace;"></span>). Then each particle is a representative for a certain number of droplets. The droplet
-features (number of droplets, initial radius, etc.) can be steered with
-the&nbsp; respective particle parameters (see e.g. <a href="#chapter_4.2.html#radius">radius</a>).
-The real number of initial droplets in a grid cell is equal to the
-initial number of droplets (defined by the particle source parameters <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
-      <span lang="en-GB"><font face="Thorndale, serif">and
-      </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>)
-times the <a href="#initial_weighting_factor">initial_weighting_factor</a>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-In case of using cloud droplets, the default condensation scheme in
-PALM cannot be used, i.e. <a href="#cloud_physics">cloud_physics</a>
-must be set <span style="font-style: italic;">.F.</span>.<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="cloud_physics"></a><b>cloud_physics</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch
-on the condensation scheme.&nbsp; </p>
-
-
-
-
-
-
-
-For <b>cloud_physics =</b> <span style="font-style: italic;">.TRUE.</span>, equations
-for the
-liquid water&nbsp;
-content and the liquid water potential temperature are solved instead
-of those for specific humidity and potential temperature. Note
-that a grid volume is assumed to be either completely saturated or
-completely
-unsaturated (0%-or-100%-scheme). A simple precipitation scheme can
-additionally be switched on with parameter <a href="#precipitation">precipitation</a>.
-Also cloud-top cooling by longwave radiation can be utilized (see <a href="#radiation">radiation</a>)<br>
-
-
-
-
-
-
- <b><br>
-
-
-
-
-
-
-
-cloud_physics =</b> <span style="font-style: italic;">.TRUE.
-      </span>requires&nbsp;<a href="#humidity">humidity</a>
-=<span style="font-style: italic;"> .TRUE.</span> .<br>
-
-
-
-
-
-
-
-Detailed information about the condensation scheme is given in the
-description of the <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM-1/Dokumentationen/Cloud_physics/wolken.pdf">cloud
-physics module</a> (pdf-file, only in German).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-This condensation scheme is not allowed if cloud droplets are simulated
-explicitly (see <a href="#cloud_droplets">cloud_droplets</a>).<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="conserve_volume_flow"></a>conserve_volume_flow</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
- <td>Conservation
-of volume flow in x- and y-direction.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-weight: bold;">conserve_volume_flow</span>
-= <span style="font-style: italic;">.T.</span>
-guarantees that the volume flow through the xz- and yz-cross-sections of
-the total model domain remains constant throughout the run depending on the chosen <a href="#conserve_volume_flow_mode">conserve_volume_flow_mode</a>.<br><br>Note that&nbsp;<span style="font-weight: bold;">conserve_volume_flow</span>
-= <span style="font-style: italic;">.T.</span> requires <a href="#dp_external">dp_external</a> = <span style="font-style: italic;">.F.</span> .<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="conserve_volume_flow_mode"></a>conserve_volume_flow_mode</span></td><td style="vertical-align: top;">C * 16</td><td style="vertical-align: top;"><span style="font-style: italic;">'default'</span></td><td>Modus of volume flow conservation.<br><br>The following values are allowed:<br><p style="font-style: normal;"><span style="font-style: italic;">'default'</span>
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul><p>Per default, PALM uses&nbsp;<span style="font-style: italic;">'initial_profiles'</span> for cyclic lateral boundary conditions (<a href="#bc_lr">bc_lr</a> = <span style="font-style: italic;">'cyclic'</span> and <a href="#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>) and&nbsp;<span style="font-style: italic;">'inflow_profile'</span> for non-cyclic lateral boundary conditions (<a href="chapter_4.1.html#bc_lr">bc_lr</a> /= <span style="font-style: italic;">'cyclic'</span> or <a href="chapter_4.1.html#bc_ns">bc_ns</a> /= <span style="font-style: italic;">'cyclic'</span>).</p></ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: italic;">'initial_profiles' </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <ul><p>The
-target volume flow&nbsp;is calculated at t=0 from the initial profiles
-of u and v.&nbsp;This setting is only allowed for&nbsp;cyclic lateral
-boundary conditions (<a href="chapter_4.1.html#bc_lr">bc_lr</a> = <span style="font-style: italic;">'cyclic'</span> and <a href="chapter_4.1.html#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>).</p></ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;"><span style="font-style: italic;">'inflow_profile'</span>
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul><p>The
-target volume flow&nbsp;is&nbsp;calculated at every timestep from the
-inflow profile of&nbsp;u or v, respectively. This setting&nbsp;is only
-allowed for&nbsp;non-cyclic lateral boundary conditions (<a href="chapter_4.1.html#bc_lr">bc_lr</a> /= <span style="font-style: italic;">'cyclic'</span> or <a href="chapter_4.1.html#bc_ns">bc_ns</a> /= <span style="font-style: italic;">'cyclic'</span>).</p></ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: italic;">'bulk_velocity' </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <ul><p>The target volume flow is calculated from a predefined bulk velocity (see <a href="#u_bulk">u_bulk</a> and <a href="#v_bulk">v_bulk</a>). This setting is only allowed for&nbsp;cyclic lateral boundary conditions (<a href="chapter_4.1.html#bc_lr">bc_lr</a> = <span style="font-style: italic;">'cyclic'</span> and <a href="chapter_4.1.html#bc_ns">bc_ns</a> = <span style="font-style: italic;">'cyclic'</span>).</p></ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <span style="font-style: italic;"></span>Note that&nbsp;<span style="font-weight: bold;">conserve_volume_flow_mode</span>
-only comes into effect if <a href="#conserve_volume_flow">conserve_volume_flow</a> = <span style="font-style: italic;">.T. .</span> </td></tr><tr>
-
-      <td style="vertical-align: top;"><a name="cthf"></a><span style="font-weight: bold;">cthf</span></td>
-
-      <td style="vertical-align: top;">R</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-      <td style="vertical-align: top;">Average heat flux that is prescribed at the top of the plant canopy.<br>
-
-
-      <br>
-
-
-If <a href="#plant_canopy">plant_canopy</a> is set <span style="font-style: italic;">.T.</span>, the user can prescribe a heat flux at the top of the plant canopy.<br>
-
-
-It is assumed that solar radiation penetrates the canopy and warms the
-foliage which, in turn, warms the air in contact with it. <br>
-
-
-Note: Instead of using the value prescribed by <a href="#surface_heatflux">surface_heatflux</a>,
-the near surface heat flux is determined from an exponential function
-that is dependent on the cumulative leaf_area_index (Shaw and Schumann
-(1992, Boundary Layer Meteorol., 61, 47-64)).</td>
-
-    </tr>
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="cut_spline_overshoot"></a><b>cut_spline_overshoot</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Cuts off of
-so-called overshoots, which can occur with the
-upstream-spline scheme.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><font color="#000000">The cubic splines tend to overshoot in
-case of discontinuous changes of variables between neighbouring grid
-points.</font><font color="#ff0000"> </font><font color="#000000">This
-may lead to errors in calculating the advection tendency.</font>
-Choice
-of <b>cut_spline_overshoot</b> = <i>.TRUE.</i>
-(switched on by
-default)
-allows variable values not to exceed an interval defined by the
-respective adjacent grid points. This interval can be adjusted
-seperately for every prognostic variable (see initialization parameters
-      <a href="#overshoot_limit_e">overshoot_limit_e</a>, <a href="#overshoot_limit_pt">overshoot_limit_pt</a>, <a href="#overshoot_limit_u">overshoot_limit_u</a>,
-etc.). This might be necessary in case that the
-default interval has a non-tolerable effect on the model
-results.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Overshoots may also be removed
-using the parameters <a href="#ups_limit_e">ups_limit_e</a>,
-      <a href="#ups_limit_pt">ups_limit_pt</a>,
-etc. as well as by applying a long-filter (see <a href="#long_filter_factor">long_filter_factor</a>).</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="damp_level_1d"></a><b>damp_level_1d</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz+1)</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Height where
-the damping layer begins in the 1d-model
-(in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This parameter is used to
-switch on a damping layer for the
-1d-model, which is generally needed for the damping of inertia
-oscillations. Damping is done by gradually increasing the value
-of the eddy diffusivities about 10% per vertical grid level
-(starting with the value at the height given by <b>damp_level_1d</b>,
-or possibly from the next grid pint above), i.e. K<sub>m</sub>(k+1)
-=
-1.1 * K<sub>m</sub>(k).
-The values of K<sub>m</sub> are limited to 10 m**2/s at
-maximum.&nbsp; <br>
-
-
-
-
-
-
-
-This parameter only comes into effect if the 1d-model is switched on
-for
-the initialization of the 3d-model using <a href="#initializing_actions">initializing_actions</a>
-= <span style="font-style: italic;">'set_1d-model_profiles'</span>.
-      <br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><a name="dissipation_1d"></a><span style="font-weight: bold;">dissipation_1d</span><br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C*20<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">model'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Calculation method for
-the energy dissipation term in the TKE equation of the 1d-model.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-By default the dissipation is calculated as in the 3d-model using diss
-= (0.19 + 0.74 * l / l_grid) * e**1.5 / l.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-Setting <span style="font-weight: bold;">dissipation_1d</span>
-= <span style="font-style: italic;">'detering'</span>
-forces the dissipation to be calculated as diss = 0.064 * e**1.5 / l.<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-    <tr><td style="vertical-align: top;"><p><a name="dp_external"></a><b>dp_external</b></p></td><td style="vertical-align: top;">L</td><td style="vertical-align: top; font-style: italic;">.F.</td><td>External pressure gradient switch.<br><br>This
-parameter is used to switch on/off an external pressure gradient as
-driving force. The external pressure gradient is controlled by the
-parameters <a href="#dp_smooth">dp_smooth</a>, <a href="#dp_level_b">dp_level_b</a> and <a href="#dpdxy">dpdxy</a>.<br><br>Note that&nbsp;<span style="font-weight: bold;">dp_external</span> = <span style="font-style: italic;">.T.</span> requires <a href="#conserve_volume_flow">conserve_volume_flow</a> =<span style="font-style: italic;"> .F. </span>It is normally recommended to disable the Coriolis force by setting <a href="l#omega">omega</a> = 0.0.</td></tr><tr><td style="vertical-align: top;"><p><a name="dp_smooth"></a><b>dp_smooth</b></p></td><td style="vertical-align: top;">L</td><td style="vertical-align: top; font-style: italic;">.F.</td><td>Vertically smooth the external pressure gradient using a sinusoidal smoothing function.<br><br>This parameter only applies if <a href="#dp_external">dp_external</a> = <span style="font-style: italic;">.T. </span>. It is useful in combination with&nbsp;<a href="#dp_level_b">dp_level_b</a> &gt;&gt; 0 to generate a non-accelerated boundary layer well below&nbsp;<a href="#dp_level_b">dp_level_b</a>.</td></tr><tr><td style="vertical-align: top;"><p><a name="dp_level_b"></a><b>dp_level_b</b></p></td><td style="vertical-align: top;">R</td><td style="vertical-align: top; font-style: italic;">0.0</td><td><font size="3">Lower
-limit of the vertical range for which the external pressure gradient is applied (</font>in <font size="3">m).</font><br><br>This parameter only applies if <a href="#dp_external">dp_external</a> = <span style="font-style: italic;">.T. </span><span lang="en-GB">It
-must hold the condition zu(0) &lt;= <b>dp_level_b</b>
-&lt;= zu(</span><a href="#nz"><span lang="en-GB">nz</span></a><span lang="en-GB">)</span><span lang="en-GB">.&nbsp;</span>It can be used in combination with&nbsp;<a href="#dp_smooth">dp_smooth</a> = <span style="font-style: italic;">.T.</span> to generate a non-accelerated boundary layer well below&nbsp;<span style="font-weight: bold;">dp_level_b</span> if&nbsp;<span style="font-weight: bold;">dp_level_b</span> &gt;&gt; 0.<br><br>Note
-that there is no upper limit of the vertical range because the external
-pressure gradient is always applied up to the top of the model domain.</td></tr><tr><td style="vertical-align: top;"><p><a name="dpdxy"></a><b>dpdxy</b></p></td><td style="vertical-align: top;">R(2)</td><td style="font-style: italic; vertical-align: top;">2 * 0.0</td><td>Values of the external pressure gradient applied in x- and y-direction, respectively (in Pa/m).<br><br>This parameter only applies if <a href="#dp_external">dp_external</a> = <span style="font-style: italic;">.T. </span>It sets the pressure gradient values. Negative values mean an acceleration, positive values mean deceleration. For example, <span style="font-weight: bold;">dpdxy</span> = -0.0002, 0.0, drives the flow in positive x-direction, <span lang="en-GB"></span></td></tr>
-
-
-
-
-
-
-    <tr>
-
-      <td style="vertical-align: top;"><a name="drag_coefficient"></a><span style="font-weight: bold;">drag_coefficient</span></td>
-
-      <td style="vertical-align: top;">R</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-      <td style="vertical-align: top;">Drag coefficient used in the plant canopy model.<br>
-
-      <br>
-
-This parameter has to be non-zero, if the parameter <a href="#plant_canopy">plant_canopy</a> is set <span style="font-style: italic;">.T.</span>.</td>
-
-    </tr>
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="dt"></a><b>dt</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">variable</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Time step for
-the 3d-model (in s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>By default, (i.e.
-if a Runge-Kutta scheme is used, see <a href="#timestep_scheme">timestep_scheme</a>)
-the value of the time step is calculating after each time step
-(following the time step criteria) and
-used for the next step.</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If the user assigns <b>dt</b>
-a value, then the time step is
-fixed to this value throughout the whole run (whether it fulfills the
-time step
-criteria or not). However, changes are allowed for restart runs,
-because <b>dt</b> can also be used as a <a href="chapter_4.2.html#dt_laufparameter">run
-parameter</a>.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>In case that the
-calculated time step meets the condition<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        <p><b>dt</b> &lt; 0.00001 * <a href="chapter_4.2.html#dt_max">dt_max</a> (with dt_max
-= 20.0)</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>the simulation will be
-aborted. Such situations usually arise
-in case of any numerical problem / instability which causes a
-non-realistic increase of the wind speed.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>A
-small time step due to a large mean horizontal windspeed
-speed may be enlarged by using a coordinate transformation (see <a href="#galilei_transformation">galilei_transformation</a>),
-in order to spare CPU time.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If the
-leapfrog timestep scheme is used (see <a href="#timestep_scheme">timestep_scheme</a>)
-a temporary time step value dt_new is calculated first, with dt_new = <a href="chapter_4.2.html#fcl_factor">cfl_factor</a>
-* dt_crit where dt_crit is the maximum timestep allowed by the CFL and
-diffusion condition. Next it is examined whether dt_new exceeds or
-falls below the
-value of the previous timestep by at
-least +5 % / -2%. If it is smaller, <span style="font-weight: bold;">dt</span>
-= dt_new is immediately used for the next timestep. If it is larger,
-then <span style="font-weight: bold;">dt </span>=
-1.02 * dt_prev
-(previous timestep) is used as the new timestep, however the time
-step is only increased if the last change of the time step is dated
-back at
-least 30 iterations. If dt_new is located in the interval mentioned
-above, then dt
-does not change at all. By doing so, permanent time step changes as
-well as large
-sudden changes (increases) in the time step are avoided.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="dt_pr_1d"></a><b>dt_pr_1d</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Temporal
-interval of vertical profile output of the 1D-model
-(in s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Data are written in ASCII
-format to file <a href="chapter_3.4.html#LIST_PROFIL_1D">LIST_PROFIL_1D</a>.
-This parameter is only in effect if the 1d-model has been switched on
-for the
-initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
-= <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="dt_run_control_1d"></a><b>dt_run_control_1d</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">60.0</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Temporal interval of
-runtime control output of the 1d-model
-(in s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Data are written in ASCII
-format to file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
-This parameter is only in effect if the 1d-model is switched on for the
-initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
-= <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="dx"></a><b>dx</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Horizontal grid
-spacing along the x-direction (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Along
-x-direction only a constant grid spacing is allowed.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
-and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="dy"></a><b>dy</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Horizontal grid
-spacing along the y-direction (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Along y-direction only a constant grid spacing is allowed.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
-and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="dz"></a><b>dz</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Vertical grid
-spacing (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This parameter must be
-assigned by the user, because no
-default value is given.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>By default, the
-model uses constant grid spacing along z-direction, but it can be
-stretched using the parameters <a href="#dz_stretch_level">dz_stretch_level</a>
-and <a href="#dz_stretch_factor">dz_stretch_factor</a>.
-In case of stretching, a maximum allowed grid spacing can be given by <a href="#dz_max">dz_max</a>.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Assuming
-a constant <span style="font-weight: bold;">dz</span>,
-the scalar levels (zu) are calculated directly by:&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p>zu(0) = - dz * 0.5&nbsp; <br>
-
-
-
-
-
-
-
-zu(1) = dz * 0.5</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The w-levels lie
-half between them:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p>zw(k) =
-( zu(k) + zu(k+1) ) * 0.5</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="dz_max"></a><span style="font-weight: bold;">dz_max</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">Allowed maximum vertical grid
-spacing (in m).<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-If the vertical grid is stretched
-(see <a href="#dz_stretch_factor">dz_stretch_factor</a>
-and <a href="#dz_stretch_level">dz_stretch_level</a>),
-      <span style="font-weight: bold;">dz_max</span> can
-be used to limit the vertical grid spacing.</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="dz_stretch_factor"></a><b>dz_stretch_factor</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">1.08</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Stretch factor for a
-vertically stretched grid (see <a href="#dz_stretch_level">dz_stretch_level</a>).&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The stretch factor should not exceed a value of
-approx. 1.10 -
-1.12, otherwise the discretization errors due to the stretched grid not
-negligible any more. (refer Kalnay de Rivas)</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="dz_stretch_level"></a><b>dz_stretch_level</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">100000.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Height level
-above/below which the grid is to be stretched
-vertically (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For <a href="chapter_4.1.html#ocean">ocean</a> = .F., <b>dz_stretch_level </b>is the height level (in m)&nbsp;<span style="font-weight: bold;">above </span>which the grid is to be stretched
-vertically. The vertical grid
-spacings <a href="#dz">dz</a>
-above this level are calculated as&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p><b>dz</b>(k+1)
-= <b>dz</b>(k) * <a href="#dz_stretch_factor">dz_stretch_factor</a></p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>and used as spacings for the scalar levels (zu).
-The
-w-levels are then defined as:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p>zw(k)
-= ( zu(k) + zu(k+1) ) * 0.5.
-
- 
-      
-      </p>
-
-
-
-
-      
-      
-      
-      
-      </ul>
-
-
-
-
-      
-      
-      
-      
-      <p>For <a href="#ocean">ocean</a> = .T., <b>dz_stretch_level </b>is the height level (in m, negative) <span style="font-weight: bold;">below</span> which the grid is to be stretched
-vertically. The vertical grid
-spacings <a href="chapter_4.1.html#dz">dz</a> below this level are calculated correspondingly as 
-
- 
-      
-      </p>
-
-
-
-
-      
-      
-      
-      
-      <ul>
-
-
-
-
-        
-        
-        
-        
-        <p><b>dz</b>(k-1)
-= <b>dz</b>(k) * <a href="chapter_4.1.html#dz_stretch_factor">dz_stretch_factor</a>.</p>
-
-
-
-
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="e_init"></a>e_init</span></td>
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-
-
-
-
-      <td>Initial subgrid-scale TKE in m<sup>2</sup>s<sup>-2</sup>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-This
-option prescribes an initial&nbsp;subgrid-scale TKE from which the initial diffusion coefficients K<sub>m</sub> and K<sub>h</sub> will be calculated if <span style="font-weight: bold;">e_init</span> is positive. This option only has an effect if&nbsp;<a href="#km_constant">km_constant</a> is not set.</td>
-
-
-
-
-
-    </tr>
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="e_min"></a>e_min</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-
-
-
-
-
- <td>Minimum
-subgrid-scale TKE in m<sup>2</sup>s<sup>-2</sup>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-This
-option&nbsp;adds artificial viscosity to the flow by ensuring that
-the
-subgrid-scale TKE does not fall below the minimum threshold <span style="font-weight: bold;">e_min</span>.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="end_time_1d"></a><b>end_time_1d</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">864000.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Time to be
-simulated for the 1d-model (in s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The
-default value corresponds to a simulated time of 10 days.
-Usually, after such a period the inertia oscillations have completely
-decayed and the solution of the 1d-model can be regarded as stationary
-(see <a href="#damp_level_1d">damp_level_1d</a>).
-This parameter is only in effect if the 1d-model is switched on for the
-initialization of the 3d-model with <a href="#initializing_actions">initializing_actions</a>
-= <span style="font-style: italic;">'set_1d-model_profiles'</span>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="fft_method"></a><b>fft_method</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'system-</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">specific'</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>FFT-method to
-be used.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><br>
-
-
-
-
-
-
-
-The fast fourier transformation (FFT) is used for solving the
-perturbation pressure equation with a direct method (see <a href="chapter_4.2.html#psolver">psolver</a>)
-and for calculating power spectra (see optional software packages,
-section <a href="chapter_4.2.html#spectra_package">4.2</a>).</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><br>
-
-
-
-
-
-
-
-By default, system-specific, optimized routines from external
-vendor libraries are used. However, these are available only on certain
-computers and there are more or less severe restrictions concerning the
-number of gridpoints to be used with them.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>There
-are two other PALM internal methods available on every
-machine (their respective source code is part of the PALM source code):</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>1.: The <span style="font-weight: bold;">Temperton</span>-method
-from Clive Temperton (ECWMF) which is computationally very fast and
-switched on with <b>fft_method</b> = <span style="font-style: italic;">'temperton-algorithm'</span>.
-The number of horizontal gridpoints (nx+1, ny+1) to be used with this
-method must be composed of prime factors 2, 3 and 5.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
-
-2.: The <span style="font-weight: bold;">Singleton</span>-method
-which is very slow but has no restrictions concerning the number of
-gridpoints to be used with, switched on with <b>fft_method</b>
-= <span style="font-style: italic;">'singleton-algorithm'</span>.
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="galilei_transformation"></a><b>galilei_transformation</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Application of a
-Galilei-transformation to the
-coordinate
-system of the model.<br>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>With <b>galilei_transformation</b>
-= <i>.T.,</i> a so-called
-Galilei-transformation is switched on which ensures that the coordinate
-system of the model is moved along with the geostrophical wind.
-Alternatively, the model domain can be moved along with the averaged
-horizontal wind (see <a href="#use_ug_for_galilei_tr">use_ug_for_galilei_tr</a>,
-this can and will naturally change in time). With this method,
-numerical inaccuracies of the Piascek - Williams - scheme (concerns in
-particular the momentum advection) are minimized. Beyond that, in the
-majority of cases the lower relative velocities in the moved system
-permit a larger time step (<a href="#dt">dt</a>).
-Switching the transformation on is only worthwhile if the geostrophical
-wind (ug, vg)
-and the averaged horizontal wind clearly deviate from the value 0. In
-each case, the distance the coordinate system has been moved is written
-to the file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>), the specification
-of a gestrophic
-wind that is not constant with height
-as well as e.g. stationary inhomogeneities at the bottom boundary do
-not allow the use of this transformation.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="grid_matching"></a><b>grid_matching</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 6</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">'strict'</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Variable to adjust the
-subdomain
-sizes in parallel runs.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-For <b>grid_matching</b> = <span style="font-style: italic;">'strict'</span>,
-the subdomains are forced to have an identical
-size on all processors. In this case the processor numbers in the
-respective directions of the virtual processor net must fulfill certain
-divisor conditions concerning the grid point numbers in the three
-directions (see <a href="#nx">nx</a>, <a href="#ny">ny</a>
-and <a href="#nz">nz</a>).
-Advantage of this method is that all PEs bear the same computational
-load.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-There is no such restriction by default, because then smaller
-subdomains are allowed on those processors which
-form the right and/or north boundary of the virtual processor grid. On
-all other processors the subdomains are of same size. Whether smaller
-subdomains are actually used, depends on the number of processors and
-the grid point numbers used. Information about the respective settings
-are given in file <a href="file:///home/raasch/public_html/PALM_group/home/raasch/public_html/PALM_group/doc/app/chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-When using a multi-grid method for solving the Poisson equation (see <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</a>)
-only <b>grid_matching</b> = <span style="font-style: italic;">'strict'</span>
-is allowed.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <b>Note:</b><br>
-
-
-
-
-
-
-
-In some cases for small processor numbers there may be a very bad load
-balancing among the
-processors which may reduce the performance of the code.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><p><a name="humidity"></a><b>humidity</b></p></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;"><i>.F.</i></td><td style="vertical-align: top;"><p>Parameter to
-switch on the prognostic equation for specific
-humidity q.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The initial vertical
-profile of q can be set via parameters <a href="chapter_4.1.html#q_surface">q_surface</a>, <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
-and <a href="chapter_4.1.html#q_vertical_gradient_level">q_vertical_gradient_level</a>.&nbsp;
-Boundary conditions can be set via <a href="chapter_4.1.html#q_surface_initial_change">q_surface_initial_change</a>
-and <a href="chapter_4.1.html#surface_waterflux">surface_waterflux</a>.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-If the condensation scheme is switched on (<a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
-= .TRUE.), q becomes the total liquid water content (sum of specific
-humidity and liquid water content).</td></tr><tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="inflow_damping_height"></a>inflow_damping_height</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">from precursor run</span></td><td style="vertical-align: top;">Height below which the turbulence signal is used for turbulence recycling (in m).<br><br>In case of a turbulent inflow (see <a href="chapter_4.1.html#turbulent_inflow">turbulent_inflow</a>),
-this parameter defines the vertical thickness of the turbulent layer up
-to which the turbulence extracted at the recycling plane (see <a href="chapter_4.1.html#recycling_width">recycling_width</a>)
-shall be imposed to the inflow. Above this level the turbulence signal
-is linearly damped to zero. The transition range within which the
-signal falls to zero is given by the parameter <a href="chapter_4.1.html#inflow_damping_width">inflow_damping_width</a>.<br><br>By default, this height is set as the height of the convective boundary layer as calculated from a precursor run. See <a href="chapter_3.9.html">chapter 3.9</a> about proper settings for getting this CBL height from a precursor run. </td></tr><tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="inflow_damping_width"></a>inflow_damping_width</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.1 * <a href="chapter_4.1.html#inflow_damping_height">inflow_damping</a></span><a href="chapter_4.1.html#inflow_damping_height"><br style="font-style: italic;"><span style="font-style: italic;">_height</span></a></td><td style="vertical-align: top;">Transition range within which the turbulance signal is damped to zero (in m).<br><br>See <a href="chapter_4.1.html#inflow_damping_height">inflow_damping_height</a> for explanation.</td></tr><tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><a name="inflow_disturbance_begin"></a><b>inflow_disturbance_<br>
-
-
-
-
-
-
-
-begin</b></td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(10,</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">nx/2 or ny/2)</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Lower
-limit of the horizontal range for which random perturbations are to be
-imposed on the horizontal velocity field (gridpoints).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-If non-cyclic lateral boundary conditions are used (see <a href="#bc_lr">bc_lr</a>
-or <a href="#bc_ns">bc_ns</a>),
-this parameter gives the gridpoint number (counted horizontally from
-the inflow)&nbsp; from which on perturbations are imposed on the
-horizontal velocity field. Perturbations must be switched on with
-parameter <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><a name="inflow_disturbance_end"></a><b>inflow_disturbance_<br>
-
-
-
-
-
-
-
-end</b></td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(100,</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">3/4*nx or</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">3/4*ny)</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Upper
-limit of the horizontal range for which random perturbations are
-to be imposed on the horizontal velocity field (gridpoints).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-If non-cyclic lateral boundary conditions are used (see <a href="#bc_lr">bc_lr</a>
-or <a href="#bc_ns">bc_ns</a>),
-this parameter gives the gridpoint number (counted horizontally from
-the inflow)&nbsp; unto which perturbations are imposed on the
-horizontal
-velocity field. Perturbations must be switched on with parameter <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="initializing_actions"></a><b>initializing_actions</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 100</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">Initialization actions
-to be carried out.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;">This parameter does not have a
-default value and therefore must be assigned with each model run. For
-restart runs <b>initializing_actions</b> = <span style="font-style: italic;">'read_restart_data'</span>
-must be set. For the initial run of a job chain the following values
-are allowed:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: normal;"><span style="font-style: italic;">'set_constant_profiles'</span>
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p>A horizontal wind profile consisting
-of linear sections (see <a href="#ug_surface">ug_surface</a>,
-        <a href="#ug_vertical_gradient">ug_vertical_gradient</a>,
-        <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>
-and <a href="#vg_surface">vg_surface</a>, <a href="#vg_vertical_gradient">vg_vertical_gradient</a>,
-        <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
-respectively) as well as a vertical temperature (humidity) profile
-consisting of
-linear sections (see <a href="#pt_surface">pt_surface</a>,
-        <a href="#pt_vertical_gradient">pt_vertical_gradient</a>,
-        <a href="#q_surface">q_surface</a>
-and <a href="#q_vertical_gradient">q_vertical_gradient</a>)
-are assumed as initial profiles. The subgrid-scale TKE is set to 0 but K<sub>m</sub>
-and K<sub>h</sub> are set to very small values because
-otherwise no TKE
-would be generated.</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: italic;">'set_1d-model_profiles' </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p>The arrays of the 3d-model are initialized with
-the
-(stationary) solution of the 1d-model. These are the variables e, kh,
-km, u, v and with Prandtl layer switched on rif, us, usws, vsws. The
-temperature (humidity) profile consisting of linear sections is set as
-for 'set_constant_profiles' and assumed as constant in time within the
-1d-model. For steering of the 1d-model a set of parameters with suffix
-"_1d" (e.g. <a href="#end_time_1d">end_time_1d</a>,
-        <a href="#damp_level_1d">damp_level_1d</a>)
-is available.</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'by_user'</span></p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">The initialization of the arrays
-of the 3d-model is under complete control of the user and has to be
-done in routine <a href="chapter_3.5.1.html#user_init_3d_model">user_init_3d_model</a>
-of the user-interface.<span style="font-style: italic;"></span></p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'initialize_vortex'</span>
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The initial
-velocity field of the
-3d-model corresponds to a
-Rankine-vortex with vertical axis. This setting may be used to test
-advection schemes. Free-slip boundary conditions for u and v (see <a href="#bc_uv_b">bc_uv_b</a>, <a href="#bc_uv_t">bc_uv_t</a>)
-are necessary. In order not to distort the vortex, an initial
-horizontal wind profile constant
-with height is necessary (to be set by <b>initializing_actions</b>
-= <span style="font-style: italic;">'set_constant_profiles'</span>)
-and some other conditions have to be met (neutral stratification,
-diffusion must be
-switched off, see <a href="#km_constant">km_constant</a>).
-The center of the vortex is located at jc = (nx+1)/2. It
-extends from k = 0 to k = nz+1. Its radius is 8 * <a href="#dx">dx</a>
-and the exponentially decaying part ranges to 32 * <a href="#dx">dx</a>
-(see init_rankine.f90). </div>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'initialize_ptanom'</span>
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p>A 2d-Gauss-like shape disturbance
-(x,y) is added to the
-initial temperature field with radius 10.0 * <a href="#dx">dx</a>
-and center at jc = (nx+1)/2. This may be used for tests of scalar
-advection schemes
-(see <a href="#scalar_advec">scalar_advec</a>).
-Such tests require a horizontal wind profile constant with hight and
-diffusion
-switched off (see <span style="font-style: italic;">'initialize_vortex'</span>).
-Additionally, the buoyancy term
-must be switched of in the equation of motion&nbsp; for w (this
-requires the user to comment out the call of <span style="font-family: monospace;">buoyancy</span> in the
-source code of <span style="font-family: monospace;">prognostic_equations.f90</span>).</p></ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="font-style: italic;">'cyclic_fill'</p><p style="font-style: normal; margin-left: 40px;">Here,
-3d-data from a precursor run are read by the initial (main) run. The
-precursor run is allowed to have a smaller domain along x and y
-compared with the main run. Also, different numbers of processors can
-be used for these two runs. Limitations are that the precursor run must
-use cyclic horizontal boundary conditions and that the number of vertical grid points, <a href="#nz">nz</a>, must be same for the precursor run and the main run. If the total domain of the main run is larger than that of the precursor
-run, the domain is filled by cyclic repetition&nbsp;of the (cyclic)
-precursor data. This initialization method is recommended if a
-turbulent inflow is used (see <a href="chapter_4.1.html#turbulent_inflow">turbulent_inflow</a>). 3d-data must be made available to the run by activating an appropriate file connection statement for local file BININ. See <a href="chapter_3.9.html">chapter 3.9</a> for more details, where usage of a turbulent inflow is explained. </p><p style="font-style: normal;">Values may be
-combined, e.g. <b>initializing_actions</b> = <span style="font-style: italic;">'set_constant_profiles
-initialize_vortex'</span>, but the values of <span style="font-style: italic;">'set_constant_profiles'</span>,
-      <span style="font-style: italic;">'set_1d-model_profiles'</span>
-, and <span style="font-style: italic;">'by_user'</span>
-must not be given at the same time.</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="km_constant"></a><b>km_constant</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>variable<br>
-
-
-
-
-
-
-
-(computed from TKE)</i></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Constant eddy
-diffusivities are used (laminar
-simulations).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If this parameter is
-specified, both in the 1d and in the
-3d-model constant values for the eddy diffusivities are used in
-space and time with K<sub>m</sub> = <b>km_constant</b>
-and K<sub>h</sub> = K<sub>m</sub> / <a href="chapter_4.2.html#prandtl_number">prandtl_number</a>.
-The prognostic equation for the subgrid-scale TKE is switched off.
-Constant eddy diffusivities are only allowed with the Prandtl layer (<a href="#prandtl_layer">prandtl_layer</a>)
-switched off.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="km_damp_max"></a><b>km_damp_max</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.5*(dx
-or dy)</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Maximum
-diffusivity used for filtering the velocity field in the vicinity of
-the outflow (in m<sup>2</sup>/s).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-When using non-cyclic lateral boundaries (see <a href="#bc_lr">bc_lr</a>
-or <a href="#bc_ns">bc_ns</a>),
-a smoothing has to be applied to the
-velocity field in the vicinity of the outflow in order to suppress any
-reflections of outgoing disturbances. Smoothing is done by increasing
-the eddy diffusivity along the horizontal direction which is
-perpendicular to the outflow boundary. Only velocity components
-parallel to the outflow boundary are filtered (e.g. v and w, if the
-outflow is along x). Damping is applied from the bottom to the top of
-the domain.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The horizontal range of the smoothing is controlled by <a href="#outflow_damping_width">outflow_damping_width</a>
-which defines the number of gridpoints (counted from the outflow
-boundary) from where on the smoothing is applied. Starting from that
-point, the eddy diffusivity is linearly increased (from zero to its
-maximum value given by <span style="font-weight: bold;">km_damp_max</span>)
-until half of the damping range width, from where it remains constant
-up to the outflow boundary. If at a certain grid point the eddy
-diffusivity calculated from the flow field is larger than as described
-above, it is used instead.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The default value of <span style="font-weight: bold;">km_damp_max</span>
-has been empirically proven to be sufficient.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-      <td style="vertical-align: top;"><a name="lad_surface"></a><span style="font-weight: bold;">lad_surface</span></td>
-
-      <td style="vertical-align: top;">R</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-      <td style="vertical-align: top;">Surface value of the leaf area density (in m<sup>2</sup>/m<sup>3</sup>).<br>
-
-      <br>
-
-This
-parameter assigns the value of the leaf area density <span style="font-weight: bold;">lad</span> at the surface (k=0)<b>.</b> Starting from this value,
-the leaf area density profile is constructed with <a href="#lad_vertical_gradient">lad_vertical_gradient</a>
-and <a href="#lad_vertical_gradient_level">lad_vertical_gradient_level
-      </a>.</td>
-
-    </tr>
-
-    <tr>
-
-      <td style="vertical-align: top;"><a name="lad_vertical_gradient"></a><span style="font-weight: bold;">lad_vertical_gradient</span></td>
-
-      <td style="vertical-align: top;">R (10)</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td>
-
-      <td style="vertical-align: top;">Gradient(s) of the leaf area density (in&nbsp;m<sup>2</sup>/m<sup>4</sup>).<br>
-
-      <br>
-
-      
-      <p>This leaf area density gradient
-holds starting from the height&nbsp;
-level defined by <a href="#lad_vertical_gradient_level">lad_vertical_gradient_level</a>
-(precisely: for all uv levels k where zu(k) &gt; lad_vertical_gradient_level, lad(k) is set: lad(k) = lad(k-1) + dzu(k) * <b>lad_vertical_gradient</b>)
-up to the level defined by <a href="#pch_index">pch_index</a>. Above that level lad(k) will automatically set to 0.0. A total of 10 different gradients for 11 height intervals (10 intervals
-if <a href="#lad_vertical_gradient_level">lad_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be assigned. The leaf area density at the surface is
-assigned via <a href="#lad_surface">lad_surface</a>.&nbsp;
-      </p>
-
-      </td>
-
-    </tr>
-
-    <tr>
-
-      <td style="vertical-align: top;"><a name="lad_vertical_gradient_level"></a><span style="font-weight: bold;">lad_vertical_gradient_level</span></td>
-
-      <td style="vertical-align: top;">R (10)</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td>
-
-      <td style="vertical-align: top;">Height level from which on the&nbsp;gradient
-of the leaf area density defined by <a href="#lad_vertical_gradient_level">lad_vertical_gradient_level</a>
-is effective (in m).<br>
-
-      <br>
-
-The height levels have to be assigned in ascending order. The
-default values result in a leaf area density that is constant with height uup to the top of the plant canopy layer defined by <a href="#pch_index">pch_index</a>. For the piecewise construction of temperature profiles see <a href="#lad_vertical_gradient">lad_vertical_gradient</a>.</td>
-
-    </tr>
-
-    <tr>
-
-      <td style="vertical-align: top;"><a name="leaf_surface_concentration"></a><b>leaf_surface_concentration</b></td>
-
-      <td style="vertical-align: top;">R</td>
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-      <td style="vertical-align: top;">Concentration of a passive scalar at the surface of a leaf (in K m/s).<br>
-
-
-      <br>
-
-
-This parameter is only of importance in cases in that both, <a href="#plant_canopy">plant_canopy</a> and <a href="#passive_scalar">passive_scalar</a>, are set <span style="font-style: italic;">.T.</span>.
-The value of the concentration of a passive scalar at the surface of a
-leaf is required for the parametrisation of the sources and sinks of
-scalar concentration due to the canopy.</td>
-
-    </tr>
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="long_filter_factor"></a><b>long_filter_factor</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Filter factor
-for the so-called Long-filter.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><br>
-
-
-
-
-
-
-
-This filter very efficiently
-eliminates 2-delta-waves sometimes cauesed by the upstream-spline
-scheme (see Mahrer and
-Pielke, 1978: Mon. Wea. Rev., 106, 818-830). It works in all three
-directions in space. A value of <b>long_filter_factor</b>
-= <i>0.01</i>
-sufficiently removes the small-scale waves without affecting the
-longer waves.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>By default, the filter is
-switched off (= <i>0.0</i>).
-It is exclusively applied to the tendencies calculated by the
-upstream-spline scheme (see <a href="#momentum_advec">momentum_advec</a>
-and <a href="#scalar_advec">scalar_advec</a>),
-not to the prognostic variables themselves. At the bottom and top
-boundary of the model domain the filter effect for vertical
-2-delta-waves is reduced. There, the amplitude of these waves is only
-reduced by approx. 50%, otherwise by nearly 100%.&nbsp; <br>
-
-
-
-
-
-
-
-Filter factors with values &gt; <i>0.01</i> also
-reduce the amplitudes
-of waves with wavelengths longer than 2-delta (see the paper by Mahrer
-and
-Pielke, quoted above). </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="loop_optimization"></a><span style="font-weight: bold;">loop_optimization</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">C*16</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
-
-
-
-
-
-
-      <td>Method used to optimize loops for solving the prognostic equations .<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-By
-default, the optimization method depends on the host on which PALM is
-running. On machines with vector-type CPUs, single 3d-loops are used to
-calculate each tendency term of each prognostic equation, while on all
-other machines, all prognostic equations are solved within one big loop
-over the two horizontal indices<span style="font-family: Courier New,Courier,monospace;"> i </span>and<span style="font-family: Courier New,Courier,monospace;"> j </span>(giving a good cache uitilization).<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-The default behaviour can be changed by setting either <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'vector'</span> or <span style="font-weight: bold;">loop_optimization</span> = <span style="font-style: italic;">'cache'</span>.</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="mixing_length_1d"></a><span style="font-weight: bold;">mixing_length_1d</span><br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C*20<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'as_in_3d_</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">model'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Mixing length used in the
-1d-model.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-By default the mixing length is calculated as in the 3d-model (i.e. it
-depends on the grid spacing).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-By setting <span style="font-weight: bold;">mixing_length_1d</span>
-= <span style="font-style: italic;">'blackadar'</span>,
-the so-called Blackadar mixing length is used (l = kappa * z / ( 1 +
-kappa * z / lambda ) with the limiting value lambda = 2.7E-4 * u_g / f).<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- 
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="momentum_advec"></a><b>momentum_advec</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 10</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>'pw-scheme'</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Advection
-scheme to be used for the momentum equations.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The user can choose between the following schemes:<br>
-
-
-
-
-
-
-
-&nbsp;<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-style: italic;">'pw-scheme'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The scheme of
-Piascek and
-Williams (1970, J. Comp. Phys., 6,
-392-405) with central differences in the form C3 is used.<br>
-
-
-
-
-
-
-
-If intermediate Euler-timesteps are carried out in case of <a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'leapfrog+euler'</span>
-the
-advection scheme is - for the Euler-timestep - automatically switched
-to an upstream-scheme.<br>
-
-
-
-
-
-
- </div>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p> </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'ups-scheme'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The
-upstream-spline scheme is
-used
-(see Mahrer and Pielke,
-1978: Mon. Wea. Rev., 106, 818-830). In opposite to the
-Piascek-Williams scheme, this is characterized by much better numerical
-features (less numerical diffusion, better preservation of flow
-structures, e.g. vortices), but computationally it is much more
-expensive. In
-addition, the use of the Euler-timestep scheme is mandatory (<a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'</span><i>euler'</i>),
-i.e. the
-timestep accuracy is only of first order.
-For this reason the advection of scalar variables (see <a href="#scalar_advec">scalar_advec</a>)
-should then also be carried out with the upstream-spline scheme,
-because otherwise the scalar variables would
-be subject to large numerical diffusion due to the upstream
-scheme.&nbsp; </div>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">Since
-the cubic splines used tend
-to overshoot under
-certain circumstances, this effect must be adjusted by suitable
-filtering and smoothing (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>,
-      <a href="#long_filter_factor">long_filter_factor</a>,
-      <a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>, <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
-This is always neccessary for runs with stable stratification,
-even if this stratification appears only in parts of the model domain.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">With stable
-stratification the
-upstream-spline scheme also
-produces gravity waves with large amplitude, which must be
-suitably damped (see <a href="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</a>).<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
- <span style="font-weight: bold;">Important: </span>The&nbsp;
-upstream-spline scheme is not implemented for humidity and passive
-scalars (see&nbsp;<a href="#humidity">humidity</a>
-and <a href="#passive_scalar">passive_scalar</a>)
-and requires the use of a 2d-domain-decomposition. The last conditions
-severely restricts code optimization on several machines leading to
-very long execution times! The scheme is also not allowed for
-non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>).</div>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><a name="netcdf_precision"></a><span style="font-weight: bold;">netcdf_precision</span><br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C*20<br>
-
-
-
-
-
-
-
-(10)<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">single preci-</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">sion for all</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">output quan-</span><br style="font-style: italic;">
-
-
-
-
-
-
- <span style="font-style: italic;">tities</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Defines the accuracy of
-the NetCDF output.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-By default, all NetCDF output data (see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
-have single precision&nbsp; (4 byte) accuracy. Double precision (8
-byte) can be choosen alternatively.<br>
-
-
-
-
-
-
-
-Accuracy for the different output data (cross sections, 3d-volume data,
-spectra, etc.) can be set independently.<br>
-
-
-
-
-
-
- <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL4'</span>
-(single precision) or <span style="font-style: italic;">'&lt;out&gt;_NF90_REAL8'</span>
-(double precision) are the two principally allowed values for <span style="font-weight: bold;">netcdf_precision</span>,
-where the string <span style="font-style: italic;">'&lt;out&gt;'
-      </span>can be chosen out of the following list:<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <table style="text-align: left; width: 284px; height: 234px;" border="1" cellpadding="2" cellspacing="2">
-
-
-
-
-
-
- <tbody>
-
-
-
-
-
-
-
-          <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'xy'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">horizontal cross section<br>
-
-
-
-
-
-
-
-            </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'xz'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">vertical (xz) cross
-section<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'yz'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">vertical (yz) cross
-section<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'2d'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">all cross sections<br>
-
-
-
-
-
-
-
-            </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'3d'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">volume data<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-          </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'pr'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">vertical profiles<br>
-
-
-
-
-
-
-
-            </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'ts'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">time series, particle
-time series<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'sp'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">spectra<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-          </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'prt'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">particles<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-          </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'all'</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-            <td style="vertical-align: top;">all output quantities<br>
-
-
-
-
-
-
-
-            </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        </tbody> 
-      
-      
-      
-      
-      
-      
-      </table>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-weight: bold;">Example:</span><br>
-
-
-
-
-
-
-
-If all cross section data and the particle data shall be output in
-double precision and all other quantities in single precision, then <span style="font-weight: bold;">netcdf_precision</span> = <span style="font-style: italic;">'2d_NF90_REAL8'</span>, <span style="font-style: italic;">'prt_NF90_REAL8'</span>
-has to be assigned.<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    
-
-
-
-
-
-
- 
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="nsor_ini"></a><b>nsor_ini</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>100</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Initial number
-of iterations with the SOR algorithm.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This
-parameter is only effective if the SOR algorithm was
-selected as the pressure solver scheme (<a href="chapter_4.2.html#psolver">psolver</a>
-= <span style="font-style: italic;">'sor'</span>)
-and specifies the
-number of initial iterations of the SOR
-scheme (at t = 0). The number of subsequent iterations at the following
-timesteps is determined
-with the parameter <a href="#nsor">nsor</a>.
-Usually <b>nsor</b> &lt; <b>nsor_ini</b>,
-since in each case
-subsequent calls to <a href="chapter_4.2.html#psolver">psolver</a>
-use the solution of the previous call as initial value. Suitable
-test runs should determine whether sufficient convergence of the
-solution is obtained with the default value and if necessary the value
-of <b>nsor_ini</b> should be changed.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="nx"></a><b>nx</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Number of grid
-points in x-direction.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>A value for this
-parameter must be assigned. Since the lower
-array bound in PALM
-starts with i = 0, the actual number of grid points is equal to <b>nx+1</b>.
-In case of cyclic boundary conditions along x, the domain size is (<b>nx+1</b>)*
-      <a href="#dx">dx</a>.</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For
-parallel runs, in case of <a href="#grid_matching">grid_matching</a>
-= <span style="font-style: italic;">'strict'</span>,
-      <b>nx+1</b> must
-be an integral multiple
-of the processor numbers (see <a href="#npex">npex</a>
-and <a href="#npey">npey</a>)
-along x- as well as along y-direction (due to data
-transposition restrictions).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
-and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ny"></a><b>ny</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Number of grid
-points in y-direction.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>A value for this
-parameter must be assigned. Since the lower
-array bound in PALM starts with j = 0, the actual number of grid points
-is equal to <b>ny+1</b>. In case of cyclic boundary
-conditions along
-y, the domain size is (<b>ny+1</b>) * <a href="#dy">dy</a>.</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>For parallel runs, in case of <a href="#grid_matching">grid_matching</a>
-= <span style="font-style: italic;">'strict'</span>,
-      <b>ny+1</b> must
-be an integral multiple
-of the processor numbers (see <a href="#npex">npex</a>
-and <a href="#npey">npey</a>)&nbsp;
-along y- as well as along x-direction (due to data
-transposition restrictions).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
-and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="nz"></a><b>nz</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Number of grid
-points in z-direction.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>A value for this
-parameter must be assigned. Since the lower
-array bound in PALM
-starts with k = 0 and since one additional grid point is added at the
-top boundary (k = <b>nz+1</b>), the actual number of grid
-points is <b>nz+2</b>.
-However, the prognostic equations are only solved up to <b>nz</b>
-(u,
-v)
-or up to <b>nz-1</b> (w, scalar quantities). The top
-boundary for u
-and v is at k = <b>nz+1</b> (u, v) while at k = <b>nz</b>
-for all
-other quantities.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For parallel
-runs,&nbsp; in case of <a href="#grid_matching">grid_matching</a>
-= <span style="font-style: italic;">'strict'</span>,
-      <b>nz</b> must
-be an integral multiple of
-the number of processors in x-direction (due to data transposition
-restrictions).</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="ocean"></a><span style="font-weight: bold;">ocean</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">Parameter to switch on&nbsp;ocean runs.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-By default PALM is configured to simulate&nbsp;atmospheric flows. However, starting from version 3.3, <span style="font-weight: bold;">ocean</span> = <span style="font-style: italic;">.T.</span> allows&nbsp;simulation of ocean turbulent flows. Setting this switch has several effects:<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-        <li>An additional prognostic equation for salinity is solved.</li>
-
-
-
-
-
-
-        <li>Potential temperature in buoyancy and stability-related terms is replaced by potential density.</li>
-
-
-
-
-
-
-        <li>Potential
-density is calculated from the equation of state for seawater after
-each timestep, using the algorithm proposed by Jackett et al. (2006, J.
-Atmos. Oceanic Technol., <span style="font-weight: bold;">23</span>, 1709-1728).<br>
-
-
-
-
-
-
-So far, only the initial hydrostatic pressure is entered into this equation.</li>
-
-
-
-
-
-
-        <li>z=0 (sea surface) is assumed at the model top (vertical grid index <span style="font-family: Courier New,Courier,monospace;">k=nzt</span> on the w-grid), with negative values of z indicating the depth.</li>
-
-
-
-
-
-
-        <li>Initial profiles are constructed (e.g. from <a href="#pt_vertical_gradient">pt_vertical_gradient</a> / <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>) starting from the sea surface, using surface values&nbsp;given by <a href="#pt_surface">pt_surface</a>, <a href="#sa_surface">sa_surface</a>, <a href="#ug_surface">ug_surface</a>, and <a href="#vg_surface">vg_surface</a>.</li>
-
-
-
-
-
-
-        <li>Zero salinity flux is used as default boundary condition at the bottom of the sea.</li>
-
-
-
-
-
-
-        <li>If switched on, random perturbations are by default imposed to the upper model domain from zu(nzt*2/3) to zu(nzt-3).</li>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-Relevant parameters to be exclusively used for steering ocean runs are <a href="#bc_sa_t">bc_sa_t</a>, <a href="#bottom_salinityflux">bottom_salinityflux</a>, <a href="#sa_surface">sa_surface</a>, <a href="#sa_vertical_gradient">sa_vertical_gradient</a>, <a href="#sa_vertical_gradient_level">sa_vertical_gradient_level</a>, and <a href="#top_salinityflux">top_salinityflux</a>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-Section <a href="chapter_4.2.2.html">4.4.2</a> gives an example for appropriate settings of these and other parameters neccessary for ocean runs.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">ocean</span> = <span style="font-style: italic;">.T.</span> does not allow settings of <a href="#timestep_scheme">timestep_scheme</a> = <span style="font-style: italic;">'leapfrog'</span> or <span style="font-style: italic;">'leapfrog+euler'</span> as well as <a href="#scalar_advec">scalar_advec</a> = <span style="font-style: italic;">'ups-scheme'</span>.<span style="font-weight: bold;"></span><br>
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="omega"></a><b>omega</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>7.29212E-5</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Angular
-velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The angular velocity of the earth is set by
-default. The
-values
-of the Coriolis parameters are calculated as:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        <p>f = 2.0 * <b>omega</b> * sin(<a href="#phi">phi</a>)&nbsp;
-        <br>
-
-
-
-
-
-
-f* = 2.0 * <b>omega</b> * cos(<a href="#phi">phi</a>)</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="outflow_damping_width"></a><b>outflow_damping_width</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">MIN(20,
-nx/2</span> or <span style="font-style: italic;">ny/2)</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Width of
-the damping range in the vicinity of the outflow (gridpoints).<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-When using non-cyclic lateral boundaries (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
-or <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
-a smoothing has to be applied to the
-velocity field in the vicinity of the outflow in order to suppress any
-reflections of outgoing disturbances. This parameter controlls the
-horizontal range to which the smoothing is applied. The range is given
-in gridpoints counted from the respective outflow boundary. For further
-details about the smoothing see parameter <a href="chapter_4.1.html#km_damp_max">km_damp_max</a>,
-which defines the magnitude of the damping.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_e"></a><b>overshoot_limit_e</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit
-for the overshooting of subgrid-scale TKE in
-case that the upstream-spline scheme is switched on (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>By deafult, if cut-off of overshoots is switched
-on for the
-upstream-spline scheme (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>),
-no overshoots are permitted at all. If <b>overshoot_limit_e</b>
-is given a non-zero value, overshoots with the respective
-amplitude (both upward and downward) are allowed.&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_e</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_pt"></a><b>overshoot_limit_pt</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit
-for the overshooting of potential temperature in
-case that the upstream-spline scheme is switched on (in K).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_pt</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_u"></a><b>overshoot_limit_u</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">Allowed limit for the
-overshooting of
-the u-component of velocity in case that the upstream-spline scheme is
-switched on (in m/s). 
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_u</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_v"></a><b>overshoot_limit_v</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit
-for the overshooting of the v-component of
-velocity in case that the upstream-spline scheme is switched on
-(in m/s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>overshoot_limit_v</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="overshoot_limit_w"></a><b>overshoot_limit_w</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Allowed limit
-for the overshooting of the w-component of
-velocity in case that the upstream-spline scheme is switched on
-(in m/s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For further information see <a href="#overshoot_limit_e">overshoot_limit_e</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>overshoot_limit_w</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="passive_scalar"></a><b>passive_scalar</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-switch on the prognostic equation for a passive
-scalar. <br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The initial vertical profile
-of s can be set via parameters <a href="#s_surface">s_surface</a>,
-      <a href="#s_vertical_gradient">s_vertical_gradient</a>
-and&nbsp; <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.
-Boundary conditions can be set via <a href="#s_surface_initial_change">s_surface_initial_change</a>
-and <a href="#surface_scalarflux">surface_scalarflux</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><b>Note:</b> <br>
-
-
-
-
-
-
-
-With <span style="font-weight: bold;">passive_scalar</span>
-switched
-on, the simultaneous use of humidity (see&nbsp;<a href="#humidity">humidity</a>)
-is impossible.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-      <td style="vertical-align: top;"><a name="pch_index"></a><span style="font-weight: bold;">pch_index</span></td>
-
-      <td style="vertical-align: top;">I</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0</span></td>
-
-      <td style="vertical-align: top;">Grid point index (scalar) of the upper boundary of the plant canopy layer.<br>
-
-      <br>
-
-Above <span style="font-weight: bold;">pch_index</span> the arrays of leaf area density and drag_coeffient are automatically set to zero in case of <a href="#plant_canopy">plant_canopy</a> = .T.. Up to <span style="font-weight: bold;">pch_index</span> a leaf area density profile can be prescribed by using the parameters <a href="#lad_surface">lad_surface</a>, <a href="#lad_vertical_gradient">lad_vertical_gradient</a> and <a href="#lad_vertical_gradient_level">lad_vertical_gradient_level</a>.</td>
-
-    </tr>
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="phi"></a><b>phi</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>55.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Geographical
-latitude (in degrees).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The value of
-this parameter determines the value of the
-Coriolis parameters f and f*, provided that the angular velocity (see <a href="#omega">omega</a>)
-is non-zero.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-      <td style="vertical-align: top;"><a name="plant_canopy"></a><span style="font-weight: bold;">plant_canopy</span></td>
-
-      <td style="vertical-align: top;">L</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-      <td style="vertical-align: top;">Switch for the plant_canopy_model.<br>
-
-      <br>
-
-If <span style="font-weight: bold;">plant_canopy</span> is set <span style="font-style: italic;">.T.</span>, the plant canopy model of Watanabe (2004, BLM 112, 307-341) is used. <br>
-
-The
-impact of a plant canopy on a turbulent flow is considered by an
-additional drag term in the momentum equations and an additional sink
-term in the prognostic equation for the subgrid-scale TKE. These
-additional terms are dependent on the leaf drag coefficient (see <a href="#drag_coefficient">drag_coefficient</a>) and the leaf area density (see <a href="#lad_surface">lad_surface</a>, <a href="#lad_vertical_gradient">lad_vertical_gradient</a>, <a href="#lad_vertical_gradient_level">lad_vertical_gradient_level</a>). The top boundary of the plant canopy is determined by the parameter <a href="#pch_index">pch_index</a>. For all heights equal to or larger than zw(k=<span style="font-weight: bold;">pch_index</span>) the leaf area density is 0 (i.e. there is no canopy at these heights!). <br>
-
-By default, a horizontally homogeneous plant canopy is prescribed, if&nbsp; <span style="font-weight: bold;">plant_canopy</span> is set <span style="font-style: italic;">.T.</span>. However, the user can define other types of plant canopies (see <a href="#canopy_mode">canopy_mode</a>).<br><br>If <span style="font-weight: bold;">plant_canopy</span> and&nbsp; <span style="font-weight: bold;">passive_scalar</span><span style="font-style: italic;"> </span>are set <span style="font-style: italic;">.T.</span>,
-the canopy acts as an additional source or sink, respectively, of
-scalar concentration. The source/sink strength is dependent on the
-scalar concentration at the leaf surface, which is generally constant
-with time in PALM and which can be specified by specifying the
-parameter <a href="#leaf_surface_concentration">leaf_surface_concentration</a>. <br><br>Additional heating of the air by the plant canopy is taken into account, when the default value of the parameter <a href="#cthf">cthf</a> is altered in the parameter file. In that case the value of <a href="#surface_heatflux">surface_heatflux</a>
-specified in the parameter file is not used in the model. Instead the
-near-surface heat flux is derived from an expontial function that is
-dependent on the cumulative leaf area index. <br> 
-
-      <br>
-
-      <span style="font-weight: bold;">plant_canopy</span> = <span style="font-style: italic;">.T. </span>is only allowed together with a non-zero <a href="#drag_coefficient">drag_coefficient</a>.</td>
-
-    </tr>
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="prandtl_layer"></a><b>prandtl_layer</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.T.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-switch on a Prandtl layer.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>By default,
-a Prandtl layer is switched on at the bottom
-boundary between z = 0 and z = 0.5 * <a href="#dz">dz</a>
-(the first computational grid point above ground for u, v and the
-scalar quantities).
-In this case, at the bottom boundary, free-slip conditions for u and v
-(see <a href="#bc_uv_b">bc_uv_b</a>)
-are not allowed. Likewise, laminar
-simulations with constant eddy diffusivities (<a href="#km_constant">km_constant</a>)
-are forbidden.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>With Prandtl-layer
-switched off, the TKE boundary condition <a href="#bc_e_b">bc_e_b</a>
-= '<i>(u*)**2+neumann'</i> must not be used and is
-automatically
-changed to <i>'neumann'</i> if necessary.&nbsp; Also,
-the pressure
-boundary condition <a href="#bc_p_b">bc_p_b</a>
-= <i>'neumann+inhomo'</i>&nbsp; is not allowed. </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>The roughness length is declared via the parameter <a href="#roughness_length">roughness_length</a>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="precipitation"></a><b>precipitation</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to switch
-on the precipitation scheme.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For
-precipitation processes PALM uses a simplified Kessler
-scheme. This scheme only considers the
-so-called autoconversion, that means the generation of rain water by
-coagulation of cloud drops among themselves. Precipitation begins and
-is immediately removed from the flow as soon as the liquid water
-content exceeds the critical value of 0.5 g/kg.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>The precipitation rate and amount can be output by assigning the runtime parameter <a href="chapter_4.2.html#data_output">data_output</a> = <span style="font-style: italic;">'prr*'</span> or <span style="font-style: italic;">'pra*'</span>, respectively. The time interval on which the precipitation amount is defined can be controlled via runtime parameter <a href="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_interval</a>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="pt_reference"></a><span style="font-weight: bold;">pt_reference</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">use horizontal average as
-refrence</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">Reference
-temperature to be used in all buoyancy terms (in K).<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-By
-default, the instantaneous horizontal average over the total model
-domain is used.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>), always a reference temperature is used in the buoyancy terms with a default value of <span style="font-weight: bold;">pt_reference</span> = <a href="#pt_surface">pt_surface</a>.</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_surface"></a><b>pt_surface</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>300.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Surface
-potential temperature (in K).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This
-parameter assigns the value of the potential temperature
-      <span style="font-weight: bold;">pt</span> at the surface (k=0)<b>.</b> Starting from this value,
-the
-initial vertical temperature profile is constructed with <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
-and <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level
-      </a>.
-This profile is also used for the 1d-model as a stationary profile.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="#ocean">ocean</a>),
-this parameter gives the temperature value at the sea surface, which is
-at k=nzt. The profile is then constructed from the surface down to the
-bottom of the model.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_surface_initial_change"></a><b>pt_surface_initial</b>
-      <br>
-
-
-
-
-
-
- <b>_change</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Change in
-surface temperature to be made at the beginning of
-the 3d run
-(in K).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If <b>pt_surface_initial_change</b>
-is set to a non-zero
-value, the near surface sensible heat flux is not allowed to be given
-simultaneously (see <a href="#surface_heatflux">surface_heatflux</a>).</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_vertical_gradient"></a><b>pt_vertical_gradient</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>10 * 0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Temperature
-gradient(s) of the initial temperature profile (in
-K
-/ 100 m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This temperature gradient
-holds starting from the height&nbsp;
-level defined by <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>
-(precisely: for all uv levels k where zu(k) &gt;
-pt_vertical_gradient_level,
-pt_init(k) is set: pt_init(k) = pt_init(k-1) + dzu(k) * <b>pt_vertical_gradient</b>)
-up to the top boundary or up to the next height level defined
-by <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>.
-A total of 10 different gradients for 11 height intervals (10 intervals
-if <a href="#pt_vertical_gradient_level">pt_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be assigned. The surface temperature is
-assigned via <a href="#pt_surface">pt_surface</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p><b>pt_vertical_gradient</b>
-= <i>1.0</i>, <i>0.5</i>,&nbsp; <br>
-
-
-
-
-
-
-
-        <b>pt_vertical_gradient_level</b> = <i>500.0</i>,
-        <i>1000.0</i>,</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>That
-defines the temperature profile to be neutrally
-stratified
-up to z = 500.0 m with a temperature given by <a href="#pt_surface">pt_surface</a>.
-For 500.0 m &lt; z &lt;= 1000.0 m the temperature gradient is
-1.0 K /
-100 m and for z &gt; 1000.0 m up to the top boundary it is
-0.5 K / 100 m (it is assumed that the assigned height levels correspond
-with uv levels).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
-the profile is constructed like described above, but starting from the
-sea surface (k=nzt) down to the bottom boundary of the model. Height
-levels have then to be given as negative values, e.g. <span style="font-weight: bold;">pt_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="pt_vertical_gradient_level"></a><b>pt_vertical_gradient</b>
-      <br>
-
-
-
-
-
-
- <b>_level</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><i>10 *</i>&nbsp;
-      <span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p>Height level from which on the temperature gradient defined by
-      <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The height levels have to be assigned in ascending order. The
-default values result in a neutral stratification regardless of the
-values of <a href="#pt_vertical_gradient">pt_vertical_gradient</a>
-(unless the top boundary of the model is higher than 100000.0 m).
-For the piecewise construction of temperature profiles see <a href="#pt_vertical_gradient">pt_vertical_gradient</a>.</p>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="q_surface"></a><b>q_surface</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Surface
-specific humidity / total water content (kg/kg).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This
-parameter assigns the value of the specific humidity q at
-the surface (k=0).&nbsp; Starting from this value, the initial
-humidity
-profile is constructed with&nbsp; <a href="#q_vertical_gradient">q_vertical_gradient</a>
-and <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>.
-This profile is also used for the 1d-model as a stationary profile.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="q_surface_initial_change"></a><b>q_surface_initial</b>
-      <br>
-
-
-
-
-
-
- <b>_change</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Change in
-surface specific humidity / total water content to
-be made at the beginning
-of the 3d run (kg/kg).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If <b>q_surface_initial_change</b><i>
-      </i>is set to a
-non-zero value the
-near surface latent heat flux (water flux) is not allowed to be given
-simultaneously (see <a href="#surface_waterflux">surface_waterflux</a>).</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="q_vertical_gradient"></a><b>q_vertical_gradient</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>10 * 0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Humidity
-gradient(s) of the initial humidity profile
-(in 1/100 m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This humidity gradient
-holds starting from the height
-level&nbsp; defined by <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>
-(precisely: for all uv levels k, where zu(k) &gt;
-q_vertical_gradient_level,
-q_init(k) is set: q_init(k) = q_init(k-1) + dzu(k) * <b>q_vertical_gradient</b>)
-up to the top boundary or up to the next height level defined
-by <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>.
-A total of 10 different gradients for 11 height intervals (10 intervals
-if <a href="#q_vertical_gradient_level">q_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be asigned. The surface humidity is
-assigned
-via <a href="#q_surface">q_surface</a>. </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p><b>q_vertical_gradient</b>
-= <i>0.001</i>, <i>0.0005</i>,&nbsp; <br>
-
-
-
-
-
-
-
-        <b>q_vertical_gradient_level</b> = <i>500.0</i>,
-        <i>1000.0</i>,</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
-
-That defines the humidity to be constant with height up to z =
-500.0
-m with a
-value given by <a href="#q_surface">q_surface</a>.
-For 500.0 m &lt; z &lt;= 1000.0 m the humidity gradient is
-0.001 / 100
-m and for z &gt; 1000.0 m up to the top boundary it is
-0.0005 / 100 m (it is assumed that the assigned height levels
-correspond with uv
-levels). </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="q_vertical_gradient_level"></a><b>q_vertical_gradient</b>
-      <br>
-
-
-
-
-
-
- <b>_level</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><i>10 *</i>&nbsp;
-      <i>0.0</i></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Height level from
-which on the humidity gradient defined by <a href="#q_vertical_gradient">q_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The height levels
-are to be assigned in ascending order. The
-default values result in a humidity constant with height regardless of
-the values of <a href="#q_vertical_gradient">q_vertical_gradient</a>
-(unless the top boundary of the model is higher than 100000.0 m). For
-the piecewise construction of humidity profiles see <a href="#q_vertical_gradient">q_vertical_gradient</a>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="radiation"></a><b>radiation</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-switch on longwave radiation cooling at
-cloud-tops.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Long-wave radiation
-processes are parameterized by the
-effective emissivity, which considers only the absorption and emission
-of long-wave radiation at cloud droplets. The radiation scheme can be
-used only with <a href="#cloud_physics">cloud_physics</a>
-= .TRUE. .</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="random_generator"></a><b>random_generator</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><i>'numerical</i><br>
-
-
-
-
-
-
-
-      <i>recipes'</i></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Random number
-generator to be used for creating uniformly
-distributed random numbers. <br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>It is
-used if random perturbations are to be imposed on the
-velocity field or on the surface heat flux field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>
-and <a href="chapter_4.2.html#random_heatflux">random_heatflux</a>).
-By default, the "Numerical Recipes" random number generator is used.
-This one provides exactly the same order of random numbers on all
-different machines and should be used in particular for comparison runs.<br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-
-Besides, a system-specific generator is available ( <b>random_generator</b>
-= <i>'system-specific')</i> which should particularly be
-used for runs
-on vector parallel computers (NEC), because the default generator
-cannot be vectorized and therefore significantly drops down the code
-performance on these machines.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- <span style="font-weight: bold;">Note:</span><br>
-
-
-
-
-
-
-
-Results from two otherwise identical model runs will not be comparable
-one-to-one if they used different random number generators.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="random_heatflux"></a><b>random_heatflux</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-impose random perturbations on the internal two-dimensional near
-surface heat flux field <span style="font-style: italic;">shf</span>.
-      <br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
-If a near surface heat flux is used as bottom
-boundary
-condition (see <a href="#surface_heatflux">surface_heatflux</a>),
-it is by default assumed to be horizontally homogeneous. Random
-perturbations can be imposed on the internal
-two-dimensional&nbsp;heat flux field <span style="font-style: italic;">shf</span> by assigning <b>random_heatflux</b>
-= <i>.T.</i>. The disturbed heat flux field is calculated
-by
-multiplying the
-values at each mesh point with a normally distributed random number
-with a mean value and standard deviation of 1. This is repeated after
-every timestep.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-In case of a non-flat <a href="#topography">topography</a>,&nbsp;assigning
-      <b>random_heatflux</b>
-= <i>.T.</i> imposes random perturbations on the
-combined&nbsp;heat
-flux field <span style="font-style: italic;">shf</span>
-composed of <a href="#surface_heatflux">surface_heatflux</a>
-at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a>
-at the topography top face.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="recycling_width"></a>recycling_width</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.1 * <a href="chapter_4.1.html#nx">nx</a> * <a href="chapter_4.1.html#dx">dx</a></span></td><td style="vertical-align: top;">Distance of the recycling plane from the inflow boundary (in m).<br><br>This
-parameter sets the horizontal extension (along the direction of the
-main flow) of the so-called recycling domain which is used to generate
-a turbulent inflow (see <a href="chapter_4.1.html#turbulent_inflow">turbulent_inflow</a>). <span style="font-weight: bold;">recycling_width</span> must be larger than the grid spacing (dx) and smaller than the length of the total domain (nx * dx).</td></tr><tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="rif_max"></a><b>rif_max</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>1.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Upper limit of
-the flux-Richardson number.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>With the
-Prandtl layer switched on (see <a href="#prandtl_layer">prandtl_layer</a>),
-flux-Richardson numbers (rif) are calculated for z=z<sub>p</sub>
-(k=1)
-in the 3d-model (in the 1d model for all heights). Their values in
-particular determine the
-values of the friction velocity (1d- and 3d-model) and the values of
-the eddy diffusivity (1d-model). With small wind velocities at the
-Prandtl layer top or small vertical wind shears in the 1d-model, rif
-can take up unrealistic large values. They are limited by an upper (<span style="font-weight: bold;">rif_max</span>) and lower
-limit (see <a href="#rif_min">rif_min</a>)
-for the flux-Richardson number. The condition <b>rif_max</b>
-&gt; <b>rif_min</b>
-must be met.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="rif_min"></a><b>rif_min</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>- 5.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Lower limit of
-the flux-Richardson number.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>For further
-explanations see <a href="#rif_max">rif_max</a>.
-The condition <b>rif_max</b> &gt; <b>rif_min </b>must
-be met.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="roughness_length"></a><b>roughness_length</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.1</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Roughness
-length (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This parameter is
-effective only in case that a Prandtl layer
-is switched
-on (see <a href="#prandtl_layer">prandtl_layer</a>).</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="sa_surface"></a><span style="font-weight: bold;">sa_surface</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Surface salinity (in psu).&nbsp;</p>
-
-
-
-
-
-
-This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).
-      
-      
-      
-      
-      
-      
-      <p>This
-parameter assigns the value of the salinity <span style="font-weight: bold;">sa</span> at the sea surface (k=nzt)<b>.</b> Starting from this value,
-the
-initial vertical salinity profile is constructed from the surface down to the bottom of the model (k=0) by using&nbsp;<a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
-and&nbsp;<a href="chapter_4.1.html#sa_vertical_gradient_level">sa_vertical_gradient_level
-      </a>.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="sa_vertical_gradient"></a><span style="font-weight: bold;">sa_vertical_gradient</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(10)</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p>Salinity gradient(s) of the initial salinity profile (in psu
-/ 100 m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>This salinity gradient
-holds starting from the height&nbsp;
-level defined by <a href="chapter_4.1.html#sa_vertical_gradient_level">sa_vertical_gradient_level</a>
-(precisely: for all uv levels k where zu(k) &lt;
-sa_vertical_gradient_level, sa_init(k) is set: sa_init(k) =
-sa_init(k+1) - dzu(k+1) * <b>sa_vertical_gradient</b>) down to the bottom boundary or down to the next height level defined
-by <a href="chapter_4.1.html#sa_vertical_gradient_level">sa_vertical_gradient_level</a>.
-A total of 10 different gradients for 11 height intervals (10 intervals
-if <a href="chapter_4.1.html#sa_vertical_gradient_level">sa_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be assigned. The surface salinity at k=nzt is
-assigned via <a href="chapter_4.1.html#sa_surface">sa_surface</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
-        
-        
-        
-        
-        
-        
-        <p><b>sa_vertical_gradient</b>
-= <i>1.0</i>, <i>0.5</i>,&nbsp; <br>
-
-
-
-
-
-
-
-        <b>sa_vertical_gradient_level</b> = <i>-500.0</i>,
--<i>1000.0</i>,</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>That
-defines the salinity to be constant down to z = -500.0 m with a salinity given by <a href="chapter_4.1.html#sa_surface">sa_surface</a>.
-For -500.0 m &lt; z &lt;= -1000.0 m the salinity gradient is
-1.0 psu /
-100 m and for z &lt; -1000.0 m down to the bottom boundary it is
-0.5 psu / 100 m (it is assumed that the assigned height levels correspond
-with uv levels).</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="sa_vertical_gradient_level"></a><span style="font-weight: bold;">sa_vertical_gradient_level</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(10)</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p>Height level from which on the salinity gradient defined by <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>The height levels have to be assigned in descending order. The
-default values result in a constant salinity profile regardless of the
-values of <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
-(unless the bottom boundary of the model is lower than -100000.0 m).
-For the piecewise construction of salinity profiles see <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="scalar_advec"></a><b>scalar_advec</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 10</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>'pw-scheme'</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Advection
-scheme to be used for the scalar quantities.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The
-user can choose between the following schemes:<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'pw-scheme'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The scheme of
-Piascek and
-Williams (1970, J. Comp. Phys., 6,
-392-405) with central differences in the form C3 is used.<br>
-
-
-
-
-
-
-
-If intermediate Euler-timesteps are carried out in case of <a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'leapfrog+euler'</span>
-the
-advection scheme is - for the Euler-timestep - automatically switched
-to an upstream-scheme. <br>
-
-
-
-
-
-
- </div>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'bc-scheme'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The Bott
-scheme modified by
-Chlond (1994, Mon.
-Wea. Rev., 122, 111-125). This is a conservative monotonous scheme with
-very small numerical diffusion and therefore very good conservation of
-scalar flow features. The scheme however, is computationally very
-expensive both because it is expensive itself and because it does (so
-far) not allow specific code optimizations (e.g. cache optimization).
-Choice of this
-scheme forces the Euler timestep scheme to be used for the scalar
-quantities. For output of horizontally averaged
-profiles of the resolved / total heat flux, <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
-= <i>'w*pt*BC'</i> / <i>'wptBC' </i>should
-be used, instead of the
-standard profiles (<span style="font-style: italic;">'w*pt*'</span>
-and <span style="font-style: italic;">'wpt'</span>)
-because these are
-too inaccurate with this scheme. However, for subdomain analysis (see <a href="#statistic_regions">statistic_regions</a>)
-exactly the reverse holds: here <i>'w*pt*BC'</i> and <i>'wptBC'</i>
-show very large errors and should not be used.<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-This scheme is not allowed for non-cyclic lateral boundary conditions
-(see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
- <span style="font-style: italic;">'ups-scheme'</span><br>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">The upstream-spline-scheme
-is used
-(see Mahrer and Pielke,
-1978: Mon. Wea. Rev., 106, 818-830). In opposite to the Piascek
-Williams scheme, this is characterized by much better numerical
-features (less numerical diffusion, better preservation of flux
-structures, e.g. vortices), but computationally it is much more
-expensive. In
-addition, the use of the Euler-timestep scheme is mandatory (<a href="#timestep_scheme">timestep_scheme</a>
-= <span style="font-style: italic;">'</span><i>euler'</i>),
-i.e. the
-timestep accuracy is only first order. For this reason the advection of
-momentum (see <a href="#momentum_advec">momentum_advec</a>)
-should then also be carried out with the upstream-spline scheme,
-because otherwise the momentum would
-be subject to large numerical diffusion due to the upstream
-scheme.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">Since
-the cubic splines used tend
-to overshoot under
-certain circumstances, this effect must be adjusted by suitable
-filtering and smoothing (see <a href="#cut_spline_overshoot">cut_spline_overshoot</a>,
-      <a href="#long_filter_factor">long_filter_factor</a>,
-      <a href="#ups_limit_pt">ups_limit_pt</a>, <a href="#ups_limit_u">ups_limit_u</a>, <a href="#ups_limit_v">ups_limit_v</a>, <a href="#ups_limit_w">ups_limit_w</a>).
-This is always neccesssary for runs with stable stratification,
-even if this stratification appears only in parts of the model
-domain.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;">With
-stable stratification the
-upstream-upline scheme also produces gravity waves with large
-amplitude, which must be
-suitably damped (see <a href="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</a>).<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p style="margin-left: 40px;"><span style="font-weight: bold;">Important: </span>The&nbsp;
-upstream-spline scheme is not implemented for humidity and passive
-scalars (see&nbsp;<a href="#humidity">humidity</a>
-and <a href="#passive_scalar">passive_scalar</a>)
-and requires the use of a 2d-domain-decomposition. The last conditions
-severely restricts code optimization on several machines leading to
-very long execution times! This scheme is also not allowed for
-non-cyclic lateral boundary conditions (see <a href="#bc_lr">bc_lr</a>
-and <a href="#bc_ns">bc_ns</a>).</p>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-A
-differing advection scheme can be choosed for the subgrid-scale TKE
-using parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-      <td style="vertical-align: top;"><a name="scalar_exchange_coefficient"></a><b>scalar_exchange_coefficient</b></td>
-
-      <td style="vertical-align: top;">R</td>
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
-
-      <td style="vertical-align: top;">Scalar exchange coefficient for a leaf (dimensionless).<br>
-
-
-      <br>
-
-
-This parameter is only of importance in cases in that both, <a href="../../../../../DEVELOPER_VERSION/chapter_4.1_adjusted.html#plant_canopy">plant_canopy</a> and <a href="../../../../../DEVELOPER_VERSION/chapter_4.1_adjusted.html#passive_scalar">passive_scalar</a>, are set <span style="font-style: italic;">.T.</span>.
-The value of the scalar exchange coefficient is required for the parametrisation of the sources and sinks of
-scalar concentration due to the canopy.</td>
-
-    </tr>
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="statistic_regions"></a><b>statistic_regions</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">I</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Number of
-additional user-defined subdomains for which
-statistical analysis
-and corresponding output (profiles, time series) shall be
-made.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>By default, vertical profiles and
-other statistical quantities
-are calculated as horizontal and/or volume average of the total model
-domain. Beyond that, these calculations can also be carried out for
-subdomains which can be defined using the field <a href="chapter_3.5.3.html">rmask </a>within the
-user-defined software
-(see <a href="chapter_3.5.3.html">chapter
-3.5.3</a>). The number of these subdomains is determined with the
-parameter <b>statistic_regions</b>. Maximum 9 additional
-subdomains
-are allowed. The parameter <a href="chapter_4.3.html#region">region</a>
-can be used to assigned names (identifier) to these subdomains which
-are then used in the headers
-of the output files and plots.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If the default NetCDF
-output format is selected (see parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>),
-data for the total domain and all defined subdomains are output to the
-same file(s) (<a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>,
-      <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>).
-In case of <span style="font-weight: bold;">statistic_regions</span>
-&gt; <span style="font-style: italic;">0</span>,
-data on the file for the different domains can be distinguished by a
-suffix which is appended to the quantity names. Suffix 0 means data for
-the total domain, suffix 1 means data for subdomain 1, etc.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>In
-case of <span style="font-weight: bold;">data_output_format</span>
-= <span style="font-style: italic;">'profil'</span>,
-individual local files for profiles (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)&nbsp;are
-created for each subdomain. The individual subdomain files differ by
-their name (the
-number of the respective subdomain is attached, e.g.
-PLOT1D_DATA_1). In this case the name of the file with the data of
-the total domain is PLOT1D_DATA_0. If no subdomains
-are declared (<b>statistic_regions</b> = <i>0</i>),
-the name
-PLOT1D_DATA is used (this must be considered in the
-respective file connection statements of the <span style="font-weight: bold;">mrun</span> configuration
-file).</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_heatflux"></a><b>surface_heatflux</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
-
-
-
-
-
-
-
-heatflux<br>
-
-
-
-
-
-
- </span></td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Kinematic sensible
-heat flux at the bottom surface (in K m/s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If
-a value is assigned to this parameter, the internal two-dimensional
-surface heat flux field <span style="font-style: italic;">shf</span>
-is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span>&nbsp;as
-bottom (horizontally homogeneous) boundary condition for the
-temperature equation. This additionally requires that a Neumann
-condition must be used for the potential temperature (see <a href="#bc_pt_b">bc_pt_b</a>),
-because otherwise the resolved scale may contribute to
-the surface flux so that a constant value cannot be guaranteed. Also,
-changes of the
-surface temperature (see <a href="#pt_surface_initial_change">pt_surface_initial_change</a>)
-are not allowed. The parameter <a href="#random_heatflux">random_heatflux</a>
-can be used to impose random perturbations on the (homogeneous) surface
-heat
-flux field <span style="font-style: italic;">shf</span>.&nbsp;</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>
-In case of a non-flat <a href="#topography">topography</a>,&nbsp;the
-internal two-dimensional&nbsp;surface heat
-flux field <span style="font-style: italic;">shf</span>
-is initialized with the value of <span style="font-weight: bold;">surface_heatflux</span>
-at the bottom surface and <a href="#wall_heatflux">wall_heatflux(0)</a>
-at the topography top face.&nbsp;The parameter<a href="#random_heatflux"> random_heatflux</a>
-can be used to impose random perturbations on this combined surface
-heat
-flux field <span style="font-style: italic;">shf</span>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If no surface heat flux is assigned, <span style="font-style: italic;">shf</span> is calculated
-at each timestep by u<sub>*</sub> * theta<sub>*</sub>
-(of course only with <a href="#prandtl_layer">prandtl_layer</a>
-switched on). Here, u<sub>*</sub>
-and theta<sub>*</sub> are calculated from the Prandtl law
-assuming
-logarithmic wind and temperature
-profiles between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_pt_b">bc_pt_b</a>)
-must be used as bottom boundary condition for the potential temperature.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>See
-also <a href="#top_heatflux">top_heatflux</a>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_pressure"></a><b>surface_pressure</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>1013.25</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Atmospheric
-pressure at the surface (in hPa).&nbsp; </p>
-
-
-
-
-
-
-
-Starting from this surface value, the vertical pressure
-profile is calculated once at the beginning of the run assuming a
-neutrally stratified
-atmosphere. This is needed for
-converting between the liquid water potential temperature and the
-potential temperature (see <a href="#cloud_physics">cloud_physics</a><span style="text-decoration: underline;"></span>).</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_scalarflux"></a><b>surface_scalarflux</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Scalar flux at
-the surface (in kg/(m<sup>2</sup> s)).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If a non-zero value is assigned to this parameter, the
-respective scalar flux value is used
-as bottom (horizontally homogeneous) boundary condition for the scalar
-concentration equation.&nbsp;This additionally requires that a
-Neumann
-condition must be used for the scalar concentration&nbsp;(see <a href="#bc_s_b">bc_s_b</a>),
-because otherwise the resolved scale may contribute to
-the surface flux so that a constant value cannot be guaranteed. Also,
-changes of the
-surface scalar concentration (see <a href="#s_surface_initial_change">s_surface_initial_change</a>)
-are not allowed. <br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If no surface scalar
-flux is assigned (<b>surface_scalarflux</b>
-= <i>0.0</i>),
-it is calculated at each timestep by u<sub>*</sub> * s<sub>*</sub>
-(of course only with Prandtl layer switched on). Here, s<sub>*</sub>
-is calculated from the Prandtl law assuming a logarithmic scalar
-concentration
-profile between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_s_b">bc_s_b</a>)
-must be used as bottom boundary condition for the scalar concentration.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="surface_waterflux"></a><b>surface_waterflux</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Kinematic
-water flux near the surface (in m/s).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If
-a non-zero value is assigned to this parameter, the
-respective water flux value is used
-as bottom (horizontally homogeneous) boundary condition for the
-humidity equation. This additionally requires that a Neumann
-condition must be used for the specific humidity / total water content
-(see <a href="#bc_q_b">bc_q_b</a>),
-because otherwise the resolved scale may contribute to
-the surface flux so that a constant value cannot be guaranteed. Also,
-changes of the
-surface humidity (see <a href="#q_surface_initial_change">q_surface_initial_change</a>)
-are not allowed.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>If no surface water
-flux is assigned (<b>surface_waterflux</b>
-= <i>0.0</i>),
-it is calculated at each timestep by u<sub>*</sub> * q<sub>*</sub>
-(of course only with Prandtl layer switched on). Here, q<sub>*</sub>
-is calculated from the Prandtl law assuming a logarithmic temperature
-profile between k=0 and k=1. In this case a Dirichlet condition (see <a href="#bc_q_b">bc_q_b</a>)
-must be used as the bottom boundary condition for the humidity.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="s_surface"></a><b>s_surface</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Surface value
-of the passive scalar (in kg/m<sup>3</sup>).&nbsp;<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-This parameter assigns the value of the passive scalar s at
-the surface (k=0)<b>.</b> Starting from this value, the
-initial vertical scalar concentration profile is constructed with<a href="#s_vertical_gradient">
-s_vertical_gradient</a> and <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="s_surface_initial_change"></a><b>s_surface_initial</b>
-      <br>
-
-
-
-
-
-
- <b>_change</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Change in
-surface scalar concentration to be made at the
-beginning of the 3d run (in kg/m<sup>3</sup>).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If <b>s_surface_initial_change</b><i>&nbsp;</i>is
-set to a
-non-zero
-value, the near surface scalar flux is not allowed to be given
-simultaneously (see <a href="#surface_scalarflux">surface_scalarflux</a>).</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="s_vertical_gradient"></a><b>s_vertical_gradient</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>10 * 0</i><i>.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Scalar
-concentration gradient(s) of the initial scalar
-concentration profile (in kg/m<sup>3 </sup>/
-100 m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The scalar gradient holds
-starting from the height level
-defined by <a href="#s_vertical_gradient_level">s_vertical_gradient_level
-      </a>(precisely: for all uv levels k, where zu(k) &gt;
-s_vertical_gradient_level, s_init(k) is set: s_init(k) = s_init(k-1) +
-dzu(k) * <b>s_vertical_gradient</b>) up to the top
-boundary or up to
-the next height level defined by <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>.
-A total of 10 different gradients for 11 height intervals (10 intervals
-if <a href="#s_vertical_gradient_level">s_vertical_gradient_level</a>(1)
-= <i>0.0</i>) can be assigned. The surface scalar value is
-assigned
-via <a href="#s_surface">s_surface</a>.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Example:&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <ul>
-
-
-
-
-
-
- 
-        
-        
-        
-        
-        
-        
-        <p><b>s_vertical_gradient</b>
-= <i>0.1</i>, <i>0.05</i>,&nbsp; <br>
-
-
-
-
-
-
-
-        <b>s_vertical_gradient_level</b> = <i>500.0</i>,
-        <i>1000.0</i>,</p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      </ul>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>That
-defines the scalar concentration to be constant with
-height up to z = 500.0 m with a value given by <a href="#s_surface">s_surface</a>.
-For 500.0 m &lt; z &lt;= 1000.0 m the scalar gradient is 0.1
-kg/m<sup>3 </sup>/ 100 m and for z &gt; 1000.0 m up to
-the top
-boundary it is 0.05 kg/m<sup>3 </sup>/ 100 m (it is
-assumed that the
-assigned height levels
-correspond with uv
-levels).</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="s_vertical_gradient_level"></a><b>s_vertical_gradient_</b>
-      <br>
-
-
-
-
-
-
- <b>level</b></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R (10)</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><i>10 *</i>
-      <i>0.0</i></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Height level from
-which on the scalar gradient defined by <a href="#s_vertical_gradient">s_vertical_gradient</a>
-is effective (in m).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The height levels
-are to be assigned in ascending order. The
-default values result in a scalar concentration constant with height
-regardless of the values of <a href="#s_vertical_gradient">s_vertical_gradient</a>
-(unless the top boundary of the model is higher than 100000.0 m). For
-the
-piecewise construction of scalar concentration profiles see <a href="#s_vertical_gradient">s_vertical_gradient</a>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="timestep_scheme"></a><b>timestep_scheme</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">C * 20</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><i>'runge</i><br>
-
-
-
-
-
-
-
-      <i>kutta-3'</i></p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Time step scheme to
-be used for the integration of the prognostic
-variables.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The user can choose between
-the following schemes:<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'runge-kutta-3'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Third order
-Runge-Kutta scheme.<br>
-
-
-
-
-
-
-
-This scheme requires the use of <a href="#momentum_advec">momentum_advec</a>
-= <a href="#scalar_advec">scalar_advec</a>
-= '<i>pw-scheme'</i>. Please refer to the&nbsp;<a href="../tec/numerik.heiko/zeitschrittverfahren.pdf">documentation
-on PALM's time integration schemes&nbsp;(28p., in German)</a>
-fur further details.<br>
-
-
-
-
-
-
- </div>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'runge-kutta-2'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Second order
-Runge-Kutta scheme.<br>
-
-
-
-
-
-
-
-For special features see <b>timestep_scheme</b> = '<i>runge-kutta-3'</i>.<br>
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-style: italic;"><span style="font-style: italic;">'leapfrog'</span><br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
- </span> 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Second
-order leapfrog scheme.<br>
-
-
-
-
-
-
-
-Although this scheme requires a constant timestep (because it is
-centered in time),&nbsp; is even applied in case of changes in
-timestep. Therefore, only small
-changes of the timestep are allowed (see <a href="#dt">dt</a>).
-However, an Euler timestep is always used as the first timestep of an
-initiali run. When using the Bott-Chlond scheme for scalar advection
-(see <a href="#scalar_advec">scalar_advec</a>),
-the prognostic equation for potential temperature will be calculated
-with the Euler scheme, although the leapfrog scheme is switched
-on.&nbsp; <br>
-
-
-
-
-
-
-
-The leapfrog scheme must not be used together with the upstream-spline
-scheme for calculating the advection (see <a href="#scalar_advec">scalar_advec</a>
-= '<i>ups-scheme'</i> and <a href="#momentum_advec">momentum_advec</a>
-= '<i>ups-scheme'</i>).<br>
-
-
-
-
-
-
- </div>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-      <span style="font-style: italic;">'</span><span style="font-style: italic;"><span style="font-style: italic;">leapfrog+euler'</span><br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
- </span> 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">The
-leapfrog scheme is used, but
-after each change of a timestep an Euler timestep is carried out.
-Although this method is theoretically correct (because the pure
-leapfrog method does not allow timestep changes), the divergence of the
-velocity field (after applying the pressure solver) may be
-significantly larger than with <span style="font-style: italic;">'leapfrog'</span>.<br>
-
-
-
-
-
-
-
-      </div>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- <span style="font-style: italic;">'euler'</span><br>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">First order
-Euler scheme.&nbsp; <br>
-
-
-
-
-
-
-
-The Euler scheme must be used when treating the advection terms with
-the upstream-spline scheme (see <a href="#scalar_advec">scalar_advec</a>
-= <span style="font-style: italic;">'ups-scheme'</span>
-and <a href="#momentum_advec">momentum_advec</a>
-= <span style="font-style: italic;">'ups-scheme'</span>).</div>
-
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-A differing timestep scheme can be choosed for the
-subgrid-scale TKE using parameter <a href="#use_upstream_for_tke">use_upstream_for_tke</a>.<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="text-align: left; vertical-align: top;"><span style="font-weight: bold;"><a name="topography"></a></span><span style="font-weight: bold;">topography</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">C * 40</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">'flat'</span></td>
-
-
-
-
-
-
- <td>
-      
-      
-      
-      
-      
-      
-      <p>Topography mode.&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The user can
-choose between the following modes:<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'flat'</span><br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flat surface.</div>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'single_building'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flow
-around&nbsp;a single rectangular building mounted on a flat surface.<br>
-
-
-
-
-
-
-
-The building size and location can be specified by the parameters <a href="#building_height">building_height</a>, <a href="#building_length_x">building_length_x</a>, <a href="#building_length_y">building_length_y</a>, <a href="#building_wall_left">building_wall_left</a> and <a href="#building_wall_south">building_wall_south</a>.<font color="#000000"><br></font></div>
-
-
-
-
-
-
-
-      <span style="font-style: italic;"></span> 
-      
-      
-      
-      
-      
-      
-      <p><span style="font-style: italic;">'single_street_canyon'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flow
-over a single, quasi-2D street canyon of infinite length oriented either in x- or in y-direction.<br>
-
-
-
-
-
-
-
-The canyon size, orientation and location can be specified by the parameters <a href="chapter_4.1.html#canyon_height">canyon_height</a> plus <span style="font-weight: bold;">either</span>&nbsp;<a href="chapter_4.1.html#canyon_width_x">canyon_width_x</a> and <a href="chapter_4.1.html#canyon_wall_left">canyon_wall_left</a> <span style="font-weight: bold;">or</span>&nbsp; <a href="chapter_4.1.html#canyon_width_y">canyon_width_y</a> and <a href="chapter_4.1.html#canyon_wall_south">canyon_wall_south</a>.<font color="#000000"><br></font></div>
-
-
-
-
-
-
-
-      <span style="font-style: italic;"></span>&nbsp;<span style="font-style: italic;"></span><p><span style="font-style: italic;">'read_from_file'</span><br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;">Flow around
-arbitrary topography.<br>
-
-
-
-
-
-
-
-This mode requires the input file <a href="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</a><font color="#000000">. This file contains </font><font color="#000000"><font color="#000000">the&nbsp;</font></font><font color="#000000">arbitrary topography </font><font color="#000000"><font color="#000000">height
-information</font></font><font color="#000000">
-in m. These data&nbsp;<span style="font-style: italic;"></span>must
-exactly match the horizontal grid.<br></font> </div>
-
-
-
-
-
-
- <span style="font-style: italic;"><br>
-
-
-
-
-
-
- </span><font color="#000000">
-Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a>
-to allow further topography modes. </font>These require to explicitly set the<span style="font-weight: bold;"> </span><a href="#topography_grid_convention">topography_grid_convention</a>&nbsp;to either <span style="font-style: italic;">'cell_edge'</span> or <span style="font-style: italic;">'cell_center'</span>.<br>
-
-      <font color="#000000">
-
-
-
-
- <br>
-
-
-
-
-
-
-
-Non-flat <span style="font-weight: bold;">topography</span>
-modes may assign a</font>
-kinematic sensible<font color="#000000"> <a href="chapter_4.1.html#wall_heatflux">wall_heatflux</a> at the five topography faces.</font><br>
-
-      <font color="#000000">
-
-
-
-
- <br>
-
-
-
-
-
-
-
-All non-flat <span style="font-weight: bold;">topography</span>
-modes </font>require the use of <a href="#momentum_advec">momentum_advec</a>
-= <a href="#scalar_advec">scalar_advec</a>
-= '<i>pw-scheme'</i>, <a href="chapter_4.2.html#psolver">psolver</a>
-/= <i>'sor</i><i>'</i>,
-      <i>&nbsp;</i><a href="#alpha_surface">alpha_surface</a>
-= 0.0,<span style="font-style: italic;"></span>&nbsp;<a style="" href="#galilei_transformation">galilei_transformation</a>
-= <span style="font-style: italic;">.F.</span>,&nbsp;<a href="#cloud_physics">cloud_physics&nbsp;</a> = <span style="font-style: italic;">.F.</span>,&nbsp; <a href="#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.F.</span>,&nbsp;&nbsp;<a href="#humidity">humidity</a> = <span style="font-style: italic;">.F.</span>, and <a href="#prandtl_layer">prandtl_layer</a> = .T..<br>
-
-
-
-
-
-
-
-      <font color="#000000"><br>
-
-
-
-
-
-
-
-Note that an inclined model domain requires the use of <span style="font-weight: bold;">topography</span> = <span style="font-style: italic;">'flat'</span> and a
-nonzero </font><a href="#alpha_surface">alpha_surface</a>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr><td style="vertical-align: top;"><a name="topography_grid_convention"></a><span style="font-weight: bold;">topography_grid_</span><br style="font-weight: bold;"><span style="font-weight: bold;">convention</span></td><td style="vertical-align: top;">C*11</td><td style="vertical-align: top;"><span style="font-style: italic;">default depends on value of <a href="chapter_4.1.html#topography">topography</a>; see text for details</span></td><td>Convention for defining the&nbsp;topography grid.<br><br>Possible values are<br><ul><li><span style="font-style: italic;">'cell_edge':&nbsp;</span>the distance between cell edges defines the extent of topography. This setting is normally for <span style="font-style: italic;">generic topographies</span>, i.e. topographies that are constructed using length parameters. For example, <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'single_building'</span> is constructed using <a href="chapter_4.1.html#building_length_x">building_length_x</a> and <a href="chapter_4.1.html#building_length_y">building_length_y</a>.
-The advantage of this setting is that the actual size of generic
-topography is independent of the grid size, provided that the length
-parameters are an integer multiple of the grid lengths&nbsp;<a href="chapter_4.1.html#dx">dx</a> and&nbsp;<a href="chapter_4.1.html#dy">dy</a>. This is convenient&nbsp;for resolution parameter studies.</li><li><span style="font-style: italic;">'cell_center'</span><span style="font-style: italic;">:&nbsp;</span>the number of topography cells define the extent of topography. This setting is normally for <span style="font-style: italic;">rastered real topographies</span> derived from digital elevation models.&nbsp;For example, <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'read_from_file'</span> is constructed using&nbsp;the input file <a href="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</a><font color="#000000">.&nbsp;</font>The
-advantage of this setting is that the&nbsp;rastered topography cells of
-the input file are directly mapped to topography grid boxes in PALM. <span style="font-style: italic;"></span></li></ul>The example files&nbsp;<big><code>example_topo_file</code></big> and&nbsp;<big><code>example_building</code></big> in <big><code>trunk/EXAMPLES/</code></big>
-illustrate the difference between
-both approaches. Both examples simulate a single building and yield the
-same results. The former uses a rastered topography input file with <span style="font-style: italic;">'cell_center'</span> convention, the latter applies a generic topography with <span style="font-style: italic;">'cell_edge'</span> convention.<br><br>The default value is<br><ul><li><span style="font-style: italic;">'cell_edge' </span>if <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'single_building'</span> or <span style="font-style: italic;">'single_street_canyon'</span>,</li><li><span style="font-style: italic;">'cell_center'</span><span style="font-style: italic;"></span> if <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'read_from_file'</span>,</li><li><span style="font-style: italic;">none (' '</span> ) otherwise, leading to an abort if&nbsp;<span style="font-weight: bold;">topography_grid_convention</span> is not set.</li></ul>This means that <br><ul><li>For PALM simulations using a <span style="font-style: italic;">user-defined topography</span>, the<span style="font-weight: bold;"> topography_grid_convention</span> must be explicitly set to either <span style="font-style: italic;">'cell_edge'</span> or <span style="font-style: italic;">'cell_center'</span>.</li><li>For PALM simulations using a <span style="font-style: italic;">standard topography</span> <span style="font-style: italic;">('single_building'</span>, <span style="font-style: italic;">'single_street_canyon'</span> or <span style="font-style: italic;">'read_from_file')</span>, it is possible but not required to set the&nbsp; <span style="font-weight: bold;">topography_grid_convention</span> because appropriate default values apply.</li></ul></td></tr><tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="top_heatflux"></a><span style="font-weight: bold;">top_heatflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
-
-
-
-
-
-
-
-heatflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p>Kinematic
-sensible heat flux at the top boundary (in K m/s).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If a value is assigned to this parameter, the internal
-two-dimensional surface heat flux field <span style="font-family: monospace;">tswst</span> is
-initialized with the value of <span style="font-weight: bold;">top_heatflux</span>&nbsp;as
-top (horizontally homogeneous) boundary condition for the
-temperature equation. This additionally requires that a Neumann
-condition must be used for the potential temperature (see <a href="chapter_4.1.html#bc_pt_t">bc_pt_t</a>),
-because otherwise the resolved scale may contribute to
-the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-weight: bold;">Note:</span><br>
-
-
-
-
-
-
-The
-application of a top heat flux additionally requires the setting of
-initial parameter <a href="#use_top_fluxes">use_top_fluxes</a>
-= .T..<span style="font-style: italic;"></span><span style="font-weight: bold;"></span> </p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>No
-Prandtl-layer is available at the top boundary so far.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>See
-also <a href="#surface_heatflux">surface_heatflux</a>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="top_momentumflux_u"></a><span style="font-weight: bold;">top_momentumflux_u</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed momentumflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">Momentum flux along x at the top boundary (in m2/s2).<br>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If a value is assigned to this parameter, the internal
-two-dimensional u-momentum flux field <span style="font-family: monospace;">uswst</span> is
-initialized with the value of <span style="font-weight: bold;">top_momentumflux_u</span> as
-top (horizontally homogeneous) boundary condition for the u-momentum equation.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-weight: bold;">Notes:</span><br>
-
-
-
-
-
-
-The
-application of a top momentum flux additionally requires the setting of
-initial parameter <a href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a>
-= .T.. Setting of <span style="font-weight: bold;">top_momentumflux_u</span> requires setting of <a href="#top_momentumflux_v">top_momentumflux_v</a> also.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>A&nbsp;Neumann
-condition should be used for the u velocity component (see <a href="chapter_4.1.html#bc_uv_t">bc_uv_t</a>),
-because otherwise the resolved scale may contribute to
-the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-
-
-
-
-
-
-
-      <span style="font-weight: bold;"></span>
-      
-      
-      
-      
-      
-      
-      <p>No
-Prandtl-layer is available at the top boundary so far.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p> The <a href="chapter_3.8.html">coupled</a> ocean parameter file&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a> should include dummy REAL value assignments to both <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> and&nbsp;<a href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a> (e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to enable the momentum flux coupling.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="top_momentumflux_v"></a><span style="font-weight: bold;">top_momentumflux_v</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed momentumflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">Momentum flux along y at the top boundary (in m2/s2).<br>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If a value is assigned to this parameter, the internal
-two-dimensional v-momentum flux field <span style="font-family: monospace;">vswst</span> is
-initialized with the value of <span style="font-weight: bold;">top_momentumflux_v</span> as
-top (horizontally homogeneous) boundary condition for the v-momentum equation.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-weight: bold;">Notes:</span><br>
-
-
-
-
-
-
-The
-application of a top momentum flux additionally requires the setting of
-initial parameter <a href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a>
-= .T.. Setting of <span style="font-weight: bold;">top_momentumflux_v</span> requires setting of <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> also.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>A&nbsp;Neumann
-condition should be used for the v velocity component (see <a href="chapter_4.1.html#bc_uv_t">bc_uv_t</a>),
-because otherwise the resolved scale may contribute to
-the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-
-
-
-
-
-
-
-      <span style="font-weight: bold;"></span>
-      
-      
-      
-      
-      
-      
-      <p>No
-Prandtl-layer is available at the top boundary so far.</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p> The <a href="chapter_3.8.html">coupled</a> ocean parameter file&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a> should include dummy REAL value assignments to both <a href="chapter_4.1.html#top_momentumflux_u">top_momentumflux_u</a> and&nbsp;<a href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a> (e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to enable the momentum flux coupling.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="top_salinityflux"></a><span style="font-weight: bold;">top_salinityflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">no prescribed<br>
-
-
-
-
-
-
-
-salinityflux</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p>Kinematic
-salinity flux at the top boundary, i.e. the sea surface (in psu m/s).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>This parameter only comes into effect for ocean runs (see parameter <a href="chapter_4.1.html#ocean">ocean</a>).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>If a value is assigned to this parameter, the internal
-two-dimensional surface heat flux field <span style="font-family: monospace;">saswst</span> is
-initialized with the value of <span style="font-weight: bold;">top_salinityflux</span>&nbsp;as
-top (horizontally homogeneous) boundary condition for the salinity equation. This additionally requires that a Neumann
-condition must be used for the salinity (see <a href="chapter_4.1.html#bc_sa_t">bc_sa_t</a>),
-because otherwise the resolved scale may contribute to
-the top flux so that a constant flux value cannot be guaranteed.<span style="font-style: italic;"></span>&nbsp;</p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><span style="font-weight: bold;">Note:</span><br>
-
-
-
-
-
-
-The
-application of a salinity flux at the model top additionally requires the setting of
-initial parameter <a href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a>
-= .T..<span style="font-style: italic;"></span><span style="font-weight: bold;"></span> </p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>See
-also <a href="chapter_4.1.html#bottom_salinityflux">bottom_salinityflux</a>.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><a name="turbulent_inflow"></a><span style="font-weight: bold;">turbulent_inflow</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td><td style="vertical-align: top;">Generates a turbulent inflow at side boundaries using a turbulence recycling method.<br><br>Turbulent inflow is realized using the turbulence recycling method from Lund et al. (1998, J. Comp. Phys., <span style="font-weight: bold;">140</span>, 233-258) modified by Kataoka and Mizuno (2002, Wind and Structures, <span style="font-weight: bold;">5</span>, 379-392).<br><br>A turbulent inflow requires Dirichlet conditions at the respective inflow boundary. <span style="font-weight: bold;">So far, a turbulent inflow is realized from the left (west) side only, i.e. </span><a style="font-weight: bold;" href="chapter_4.1.html#bc_lr">bc_lr</a><span style="font-weight: bold;">&nbsp;=</span><span style="font-style: italic; font-weight: bold;"> 'dirichlet/radiation'</span><span style="font-weight: bold;"> is required!</span><br><br>The initial (quasi-stationary) turbulence field should be generated by a precursor run and used by setting <a href="chapter_4.1.html#initializing_actions">initializing_actions</a> =<span style="font-style: italic;"> 'cyclic_fill'</span>.<br><br>The distance of the recycling plane from the inflow boundary can be set with parameter <a href="chapter_4.1.html#recycling_width">recycling_width</a>.
-The heigth above ground above which the turbulence signal is not used
-for recycling and the width of the layer within&nbsp;the magnitude of
-the turbulence signal is damped from 100% to 0% can be set with
-parameters <a href="chapter_4.1.html#inflow_damping_height">inflow_damping_height</a> and <a href="chapter_4.1.html#inflow_damping_width">inflow_damping_width</a>.<br><br>The detailed setup for a turbulent inflow is described in <a href="chapter_3.9.html">chapter 3.9</a>.</td></tr><tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="u_bulk"></a>u_bulk</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td><td>u-component of the predefined bulk velocity (in m/s).<br><br>This parameter comes into effect if <a href="#conserve_volume_flow">conserve_volume_flow</a> = <span style="font-style: italic;">.T.</span> and <a href="#conserve_volume_flow_mode">conserve_volume_flow_mode</a> = <span style="font-style: italic;">'bulk_velocity'</span>.</td></tr><tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="ug_surface"></a><span style="font-weight: bold;">ug_surface</span></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">u-component of the
-geostrophic
-wind at the surface (in m/s).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-This parameter assigns the value of the u-component of the geostrophic
-wind (ug) at the surface (k=0). Starting from this value, the initial
-vertical profile of the <br>
-
-
-
-
-
-
-
-u-component of the geostrophic wind is constructed with <a href="#ug_vertical_gradient">ug_vertical_gradient</a>
-and <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>.
-The
-profile constructed in that way is used for creating the initial
-vertical velocity profile of the 3d-model. Either it is applied, as it
-has been specified by the user (<a href="#initializing_actions">initializing_actions</a>
-= 'set_constant_profiles') or it is used for calculating a stationary
-boundary layer wind profile (<a href="#initializing_actions">initializing_actions</a>
-= 'set_1d-model_profiles'). If ug is constant with height (i.e. ug(k)=<span style="font-weight: bold;">ug_surface</span>)
-and&nbsp; has a large
-value, it is recommended to use a Galilei-transformation of the
-coordinate system, if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
-in order to obtain larger time steps.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
-this parameter gives the geostrophic velocity value (i.e. the pressure gradient) at the sea surface, which is
-at k=nzt. The profile is then constructed from the surface down to the
-bottom of the model.<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ug_vertical_gradient"></a><span style="font-weight: bold;">ug_vertical_gradient</span></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Gradient(s) of the initial
-profile of the&nbsp; u-component of the geostrophic wind (in
-1/100s).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The gradient holds starting from the height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>
-(precisely: for all uv levels k where zu(k) &gt; <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>,
-ug(k) is set: ug(k) = ug(k-1) + dzu(k) * <span style="font-weight: bold;">ug_vertical_gradient</span>)
-up to the top
-boundary or up to the next height level defined by <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>.
-A
-total of 10 different gradients for 11 height intervals (10
-intervals&nbsp; if <a href="#ug_vertical_gradient_level">ug_vertical_gradient_level</a>(1)
-= 0.0) can be assigned. The surface geostrophic wind is assigned by <a href="#ug_surface">ug_surface</a>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
-the profile is constructed like described above, but starting from the
-sea surface (k=nzt) down to the bottom boundary of the model. Height
-levels have then to be given as negative values, e.g. <span style="font-weight: bold;">ug_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="ug_vertical_gradient_level"></a><span style="font-weight: bold;">ug_vertical_gradient_level</span></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Height level from which on the
-gradient defined by <a href="#ug_vertical_gradient">ug_vertical_gradient</a>
-is effective (in m).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The height levels have to be assigned in ascending order. For the
-piecewise construction of a profile of the u-component of the
-geostrophic wind component (ug) see <a href="#ug_vertical_gradient">ug_vertical_gradient</a>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_e"></a><b>ups_limit_e</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Subgrid-scale
-turbulent kinetic energy difference used as
-criterion for applying the upstream scheme when upstream-spline
-advection is switched on (in m<sup>2</sup>/s<sup>2</sup>).
-&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate
-treatment of the
-advection of the subgrid-scale turbulent kinetic energy in case that
-the uptream-spline scheme is used . For further information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are allowed for <b>ups_limit_e</b>.
-      </p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_pt"></a><b>ups_limit_pt</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Temperature
-difference used as criterion for applying&nbsp;
-the upstream scheme when upstream-spline advection&nbsp; is
-switched on
-(in K).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>This criterion is used if the
-upstream-spline scheme is
-switched on (see <a href="#scalar_advec">scalar_advec</a>).<br>
-
-
-
-
-
-
-
-If, for a given gridpoint, the absolute temperature difference with
-respect to the upstream
-grid point is smaller than the value given for <b>ups_limit_pt</b>,
-the upstream scheme is used for this gridpoint (by default, the
-upstream-spline scheme is always used). Reason: in case of a very small
-upstream gradient, the advection should cause only a very small
-tendency. However, in such situations the upstream-spline scheme may
-give wrong tendencies at a
-grid point due to spline overshooting, if simultaneously the downstream
-gradient is very large. In such cases it may be more reasonable to use
-the upstream scheme. The numerical diffusion caused by the upstream
-schme remains small as long as the upstream gradients are small.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The percentage of grid points for which the
-upstream
-scheme is actually used, can be output as a time series with respect to
-the
-three directions in space with run parameter (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>, the
-timeseries names in the NetCDF file are <i>'splptx'</i>, <i>'splpty'</i>,
-      <i>'splptz'</i>). The percentage
-of gridpoints&nbsp; should stay below a certain limit, however, it
-is
-not possible to give
-a general limit, since it depends on the respective flow.&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_pt</b>.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
-
-A more effective control of
-the &ldquo;overshoots&rdquo; can be achieved with parameter <a href="#cut_spline_overshoot">cut_spline_overshoot</a>.
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_u"></a><b>ups_limit_u</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Velocity
-difference (u-component) used as criterion for
-applying the upstream scheme
-when upstream-spline advection is switched on (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
-advection of the u-velocity-component in case that the upstream-spline
-scheme is used. For further
-information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_u</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_v"></a><b>ups_limit_v</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Velocity
-difference (v-component) used as criterion for
-applying the upstream scheme
-when upstream-spline advection is switched on (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
-advection of the v-velocity-component in case that the upstream-spline
-scheme is used. For further
-information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_v</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="ups_limit_w"></a><b>ups_limit_w</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>0.0</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Velocity
-difference (w-component) used as criterion for
-applying the upstream scheme
-when upstream-spline advection is switched on (in m/s).&nbsp; </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>This variable steers the appropriate treatment of the
-advection of the w-velocity-component in case that the upstream-spline
-scheme is used. For further
-information see <a href="#ups_limit_pt">ups_limit_pt</a>.&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Only positive values are permitted for <b>ups_limit_w</b>.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="use_surface_fluxes"></a><b>use_surface_fluxes</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.F.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-steer the treatment of the subgrid-scale vertical
-fluxes within the diffusion terms at k=1 (bottom boundary).<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>By default, the near-surface subgrid-scale fluxes are
-parameterized (like in the remaining model domain) using the gradient
-approach. If <b>use_surface_fluxes</b>
-= <i>.TRUE.</i>, the user-assigned surface fluxes are used
-instead
-(see <a href="#surface_heatflux">surface_heatflux</a>,
-      <a href="#surface_waterflux">surface_waterflux</a>
-and <a href="#surface_scalarflux">surface_scalarflux</a>)
-      <span style="font-weight: bold;">or</span> the
-surface fluxes are
-calculated via the Prandtl layer relation (depends on the bottom
-boundary conditions, see <a href="#bc_pt_b">bc_pt_b</a>,
-      <a href="#bc_q_b">bc_q_b</a>
-and <a href="#bc_s_b">bc_s_b</a>).<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p><b>use_surface_fluxes</b>
-is automatically set <i>.TRUE.</i>, if a Prandtl layer is
-used (see <a href="#prandtl_layer">prandtl_layer</a>).&nbsp;
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>The user may prescribe the surface fluxes at the
-bottom
-boundary without using a Prandtl layer by setting <span style="font-weight: bold;">use_surface_fluxes</span> =
-      <span style="font-style: italic;">.T.</span> and <span style="font-weight: bold;">prandtl_layer</span> = <span style="font-style: italic;">.F.</span>. If , in this
-case, the
-momentum flux (u<sub>*</sub><sup>2</sup>)
-should also be prescribed,
-the user must assign an appropriate value within the user-defined code.</p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><a name="use_top_fluxes"></a><span style="font-weight: bold;">use_top_fluxes</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to steer
-the treatment of the subgrid-scale vertical
-fluxes within the diffusion terms at k=nz (top boundary).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>By
-default, the fluxes at nz are calculated using the gradient approach.
-If <b>use_top_fluxes</b>
-= <i>.TRUE.</i>, the user-assigned top fluxes are used
-instead
-(see <a href="chapter_4.1.html#top_heatflux">top_heatflux</a>, <a href="#top_momentumflux_u">top_momentumflux_u</a>, <a href="#top_momentumflux_v">top_momentumflux_v</a>, <a href="#top_salinityflux">top_salinityflux</a>).</p>
-
-
-
-
-
-
-      
-      
-      
-      
-      
-      
-      <p>Currently, no value for the latent heatflux can be assigned. In case of <span style="font-weight: bold;">use_top_fluxes</span> = <span style="font-style: italic;">.TRUE.</span>, the latent
-heat flux at the top will be automatically set to zero.</p>
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="use_ug_for_galilei_tr"></a><b>use_ug_for_galilei_tr</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.T.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Switch to
-determine the translation velocity in case that a
-Galilean transformation is used.<br>
-
-
-
-
-
-
- </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>In
-case of a Galilean transformation (see <a href="#galilei_transformation">galilei_transformation</a>),
-      <b>use_ug_for_galilei_tr</b>
-= <i>.T.</i>&nbsp; ensures
-that the coordinate system is translated with the geostrophic windspeed.<br>
-
-
-
-
-
-
-
-      </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>Alternatively, with <b>use_ug_for_galilei_tr</b>
-= <i>.F</i>.,
-the
-geostrophic wind can be replaced as translation speed by the (volume)
-averaged velocity. However, in this case the user must be aware of fast
-growing gravity waves, so this
-choice is usually not recommended!</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
-      <td align="left" valign="top"><a name="use_upstream_for_tke"></a><span style="font-weight: bold;">use_upstream_for_tke</span></td>
-
-
-
-
-
-
-      <td align="left" valign="top">L</td>
-
-
-
-
-
-
-      <td align="left" valign="top"><span style="font-style: italic;">.F.</span></td>
-
-
-
-
-
-
-      <td align="left" valign="top">Parameter to choose the
-advection/timestep scheme to be used for the subgrid-scale TKE.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-By
-default, the advection scheme and the timestep scheme to be used for
-the subgrid-scale TKE are set by the initialization parameters <a href="#scalar_advec">scalar_advec</a> and <a href="#timestep_scheme">timestep_scheme</a>,
-respectively. <span style="font-weight: bold;">use_upstream_for_tke</span>
-= <span style="font-style: italic;">.T.</span>
-forces the Euler-scheme and the upstream-scheme to be used as timestep
-scheme and advection scheme, respectively. By these methods, the strong
-(artificial) near-surface vertical gradients of the subgrid-scale TKE
-are significantly reduced. This is required when subgrid-scale
-velocities are used for advection of particles (see particle package
-parameter <a href="chapter_4.2.html#use_sgs_for_particles">use_sgs_for_particles</a>).</td>
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
-    <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="v_bulk"></a>v_bulk</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td><td>v-component of the predefined bulk velocity (in m/s).<br><br>This parameter comes into effect if <a href="chapter_4.1.html#conserve_volume_flow">conserve_volume_flow</a> = <span style="font-style: italic;">.T.</span> and <a href="chapter_4.1.html#conserve_volume_flow_mode">conserve_volume_flow_mode</a> = <span style="font-style: italic;">'bulk_velocity'</span>.</td></tr><tr>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="vg_surface"></a><span style="font-weight: bold;">vg_surface</span></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R<br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">v-component of the
-geostrophic
-wind at the surface (in m/s).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-This parameter assigns the value of the v-component of the geostrophic
-wind (vg) at the surface (k=0). Starting from this value, the initial
-vertical profile of the <br>
-
-
-
-
-
-
-
-v-component of the geostrophic wind is constructed with <a href="#vg_vertical_gradient">vg_vertical_gradient</a>
-and <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>.
-The
-profile
-constructed in that way is used for creating the initial vertical
-velocity profile of the 3d-model. Either it is applied, as it has been
-specified by the user (<a href="#initializing_actions">initializing_actions</a>
-= 'set_constant_profiles')
-or it is used for calculating a stationary boundary layer wind profile
-(<a href="#initializing_actions">initializing_actions</a>
-=
-'set_1d-model_profiles'). If vg is constant
-with height (i.e. vg(k)=<span style="font-weight: bold;">vg_surface</span>)
-and&nbsp; has a large value, it is
-recommended to use a Galilei-transformation of the coordinate system,
-if possible (see <a href="#galilei_transformation">galilei_transformation</a>),
-in order to obtain larger
-time steps.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
-this parameter gives the geostrophic velocity value (i.e. the pressure gradient) at the sea surface, which is
-at k=nzt. The profile is then constructed from the surface down to the
-bottom of the model.</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p><a name="vg_vertical_gradient"></a><span style="font-weight: bold;">vg_vertical_gradient</span></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Gradient(s) of the initial
-profile of the&nbsp; v-component of the geostrophic wind (in
-1/100s).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The gradient holds starting from the height level defined by <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>
-(precisely: for all uv levels k where zu(k)
-&gt; <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>,
-vg(k) is set: vg(k) = vg(k-1) + dzu(k)
-* <span style="font-weight: bold;">vg_vertical_gradient</span>)
-up to
-the top boundary or up to the next height
-level defined by <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>.
-A total of 10 different
-gradients for 11 height intervals (10 intervals&nbsp; if <a href="#vg_vertical_gradient_level">vg_vertical_gradient_level</a>(1)
-=
-0.0) can be assigned. The surface
-geostrophic wind is assigned by <a href="#vg_surface">vg_surface</a>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>),
-the profile is constructed like described above, but starting from the
-sea surface (k=nzt) down to the bottom boundary of the model. Height
-levels have then to be given as negative values, e.g. <span style="font-weight: bold;">vg_vertical_gradient_level</span> = <span style="font-style: italic;">-500.0</span>, <span style="font-style: italic;">-1000.0</span>.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="vg_vertical_gradient_level"></a><span style="font-weight: bold;">vg_vertical_gradient_level</span></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">R(10)<br>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">10
-* 0.0</span><br>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">Height level from which on the
-gradient defined by <a href="#vg_vertical_gradient">vg_vertical_gradient</a>
-is effective (in m).<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-The height levels have to be assigned in ascending order. For the
-piecewise construction of a profile of the v-component of the
-geostrophic wind component (vg) see <a href="#vg_vertical_gradient">vg_vertical_gradient</a>.<br>
-
-
-
-
-
-
-      <br>
-
-
-
-
-
-
-      <span style="font-weight: bold;">Attention:</span><br>
-
-
-
-
-
-
-In case of ocean runs&nbsp;(see <a href="chapter_4.1.html#ocean">ocean</a>), the (negative) height levels have to be assigned in descending order.</td>
-
-
-
-
-
-
-
-    </tr>
-
-
-
-
-
-
- <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;">
-      
-      
-      
-      
-      
-      
-      <p><a name="wall_adjustment"></a><b>wall_adjustment</b></p>
-
-
-
-
-
-
-
-      </td>
-
-
-
-
-
-
- <td style="vertical-align: top;">L</td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"><i>.T.</i></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;"> 
-      
-      
-      
-      
-      
-      
-      <p>Parameter to
-restrict the mixing length in the vicinity of the
-bottom
-boundary (and near vertical walls of a non-flat <a href="chapter_4.1.html#topography">topography</a>).&nbsp; </p>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <p>With <b>wall_adjustment</b>
-= <i>.TRUE., </i>the mixing
-length is limited to a maximum of&nbsp; 1.8 * z. This condition
-typically affects only the
-first grid points above the bottom boundary.</p>
-
-
-      
-      
-      <p>In case of&nbsp; a non-flat <a href="chapter_4.1.html#topography">topography</a> the respective horizontal distance from vertical walls is used.</p>
-
-
-
-
-
-
- </td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
-
-    <tr>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="wall_heatflux"></a>wall_heatflux</span></td>
-
-
-
-
-
-
-
-      <td style="vertical-align: top;">R(5)</td>
-
-
-
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">5 * 0.0</span></td>
-
-
-
-
-
-
- <td>Prescribed
-kinematic sensible heat flux in K m/s
-at the five topography faces:<br>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
- 
-      
-      
-      
-      
-      
-      
-      <div style="margin-left: 40px;"><span style="font-weight: bold;">wall_heatflux(0)&nbsp;&nbsp;
-&nbsp;</span>top face<br>
-
-
-
-
-
-
- <span style="font-weight: bold;">wall_heatflux(1)&nbsp;&nbsp;&nbsp;
-      </span>left face<br>
-
-
-
-
-
-
- <span style="font-weight: bold;">wall_heatflux(2)&nbsp;&nbsp;&nbsp;
-      </span>right face<br>
-
-
-
-
-
-
- <span style="font-weight: bold;">wall_heatflux(3)&nbsp;&nbsp;&nbsp;
-      </span>south face<br>
-
-
-
-
-
-
- <span style="font-weight: bold;">wall_heatflux(4)&nbsp;&nbsp;&nbsp;
-      </span>north face</div>
-
-
-
-
-
-
- <br>
-
-
-
-
-
-
-
-This parameter applies only in case of a non-flat <a href="#topography">topography</a>.&nbsp;The
-parameter <a href="#random_heatflux">random_heatflux</a>
-can be used to impose random perturbations on the internal
-two-dimensional surface heat
-flux field <span style="font-style: italic;">shf</span>
-that is composed of <a href="#surface_heatflux">surface_heatflux</a>
-at the bottom surface and <span style="font-weight: bold;">wall_heatflux(0)</span>
-at the topography top face.&nbsp;</td>
-
-
-
-
-
-
- </tr>
-
-
-
-
-
-
- 
-  
-  
-  
-  
-  
-  
-  </tbody>
-</table>
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-
-<p style="line-height: 100%;"><br>
-
-
-
-
-
-
-<font color="#000080"><font color="#000080"><a href="chapter_4.0.html"><font color="#000080"><img name="Grafik1" src="left.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img name="Grafik2" src="up.gif" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.2.html"><font color="#000080"><img name="Grafik3" src="right.gif" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
-
-
-
-
-
-
-
-<p style="line-height: 100%;"><i>Last
-change:&nbsp;</i> $Id$ </p>
-
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-<br>
-
-
-
-
-
-
-
-</body></html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+	<TITLE>PALM chapter 4.1</TITLE>
+	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0  (Unix)">
+	<META NAME="CREATED" CONTENT="0;0">
+	<META NAME="CHANGED" CONTENT="20090624;16094200">
+</HEAD>
+<BODY LANG="en-US" DIR="LTR">
+<H3><A NAME="chapter4.1"></A>4.1 Initialization parameters</H3>
+<P STYLE="margin-bottom: 0in"><BR>
+</P>
+<TABLE WIDTH=1643 BORDER=1 CELLPADDING=2 CELLSPACING=3>
+	<COL WIDTH=126>
+	<COL WIDTH=45>
+	<COL WIDTH=159>
+	<COL WIDTH=1280>
+	<TR>
+		<TD WIDTH=126>
+			<P><FONT SIZE=4><B>Parameter name</B></FONT></P>
+		</TD>
+		<TD WIDTH=45>
+			<P><FONT SIZE=4><B>Type</B></FONT></P>
+		</TD>
+		<TD WIDTH=159>
+			<P><FONT SIZE=4><B>Default</B></FONT> <BR><FONT SIZE=4><B>value</B></FONT></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P><FONT SIZE=4><B>Explanation</B></FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="adjust_mixing_length"></A><B>adjust_mixing_length</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Near-surface adjustment of the
+			mixing length to the Prandtl-layer law.&nbsp; 
+			</P>
+			<P>Usually the mixing length in LES models l<SUB>LES</SUB> depends
+			(as in PALM) on the grid size and is possibly restricted further
+			in case of stable stratification and near the lower wall (see
+			parameter <A HREF="#wall_adjustment">wall_adjustment</A>). With
+			<B>adjust_mixing_length</B> = <I>.T.</I> the Prandtl' mixing
+			length l<SUB>PR</SUB> = kappa * z/phi is calculated and the mixing
+			length actually used in the model is set l = MIN (l<SUB>LES</SUB>,
+			l<SUB>PR</SUB>). This usually gives a decrease of the mixing
+			length at the bottom boundary and considers the fact that eddy
+			sizes decrease in the vicinity of the wall.&nbsp; 
+			</P>
+			<P STYLE="font-style: normal"><B>Warning:</B> So far, there is no
+			good experience with <B>adjust_mixing_length</B> = <I>.T.</I> !&nbsp;
+						</P>
+			<P>With <B>adjust_mixing_length</B> = <I>.T.</I> and the
+			Prandtl-layer being switched on (see <A HREF="#prandtl_layer">prandtl_layer</A>)
+			<I>'(u*)** 2+neumann'</I> should always be set as the lower
+			boundary condition for the TKE (see <A HREF="#bc_e_b">bc_e_b</A>),
+			otherwise the near-surface value of the TKE is not in agreement
+			with the Prandtl-layer law (Prandtl-layer law and
+			Prandtl-Kolmogorov-Ansatz should provide the same value for K<SUB>m</SUB>).
+			A warning is given, if this is not the case.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="alpha_surface"></A><B>alpha_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Inclination of the model domain with
+			respect to the horizontal (in degrees).&nbsp; 
+			</P>
+			<P STYLE="font-style: normal">By means of <B>alpha_surface</B> the
+			model domain can be inclined in x-direction with respect to the
+			horizontal. In this way flows over inclined surfaces (e.g.
+			drainage flows, gravity flows) can be simulated. In case of
+			<B>alpha_surface </B>/= <I>0</I> the buoyancy term appears both in
+			the equation of motion of the u-component and of the w-component.</P>
+			<P><SPAN STYLE="font-style: normal">An inclination is only
+			possible in case of cyclic horizontal boundary conditions along x
+			AND y (see <A HREF="#bc_lr">bc_lr</A> and <A HREF="#bc_ns">bc_ns</A>)
+			and <A HREF="#topography">topography</A> = </SPAN><I>'flat'</I><SPAN STYLE="font-style: normal">.
+			</SPAN>
+			</P>
+			<P>Runs with inclined surface still require additional
+			user-defined code as well as modifications to the default code.
+			Please ask the <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PALM_group.html#0">PALM
+			developer&nbsp; group</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_e_b"></A><B>bc_e_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Bottom boundary condition of the
+			TKE.&nbsp; 
+			</P>
+			<P><B>bc_e_b</B> may be set to&nbsp;<I>'neumann'</I> or <I>'(u*)
+			** 2+neumann'</I>. <B>bc_e_b</B> = <I>'neumann'</I> yields to
+			e(k=0)=e(k=1) (Neumann boundary condition), where e(k=1) is
+			calculated via the prognostic TKE equation. Choice of
+			<I>'(u*)**2+neumann'</I> also yields to e(k=0)=e(k=1), but the TKE
+			at the Prandtl-layer top (k=1) is calculated diagnostically by
+			e(k=1)=(us/0.1)**2. However, this is only allowed if a
+			Prandtl-layer is used (<A HREF="#prandtl_layer">prandtl_layer</A>).
+			If this is not the case, a warning is given and <B>bc_e_b</B> is
+			reset to <I>'neumann'</I>.&nbsp; 
+			</P>
+			<P STYLE="font-style: normal">At the top boundary a Neumann
+			boundary condition is generally used: (e(nz+1) = e(nz)).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_lr"></A><B>bc_lr</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'cyclic'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Boundary condition along x (for all quantities).<BR><BR>By
+			default, a cyclic boundary condition is used along x.<BR><BR><B>bc_lr</B>
+			may also be assigned the values <I>'dirichlet/radiation'</I>
+			(inflow from left, outflow to the right) or <I>'radiation/dirichlet'</I>
+			(inflow from right, outflow to the left). This requires the
+			multi-grid method to be used for solving the Poisson equation for
+			perturbation pressure (see <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</A>)
+			and it also requires cyclic boundary conditions along y
+			(see&nbsp;<A HREF="#bc_ns">bc_ns</A>).<BR><BR>In case of these
+			non-cyclic lateral boundaries, a Dirichlet condition is used at
+			the inflow for all quantities (initial vertical profiles - see
+			<A HREF="#initializing_actions">initializing_actions</A> - are
+			fixed during the run) except u, to which a Neumann (zero gradient)
+			condition is applied. At the outflow, a radiation condition is
+			used for all velocity components, while a Neumann (zero gradient)
+			condition is used for the scalars. For perturbation pressure
+			Neumann (zero gradient) conditions are assumed both at the inflow
+			and at the outflow.<BR><BR>When using non-cyclic lateral
+			boundaries, a filter is applied to the velocity field in the
+			vicinity of the outflow in order to suppress any reflections of
+			outgoing disturbances (see <A HREF="#km_damp_max">km_damp_max</A>
+			and <A HREF="#outflow_damping_width">outflow_damping_width</A>).<BR><BR>In
+			order to maintain a turbulent state of the flow, it may be
+			neccessary to continuously impose perturbations on the horizontal
+			velocity field in the vicinity of the inflow throughout the whole
+			run. This can be switched on using <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#create_disturbances">create_disturbances</A>.
+			The horizontal range to which these perturbations are applied is
+			controlled by the parameters <A HREF="#inflow_disturbance_begin">inflow_disturbance_begin</A>
+			and <A HREF="#inflow_disturbance_end">inflow_disturbance_end</A>.
+			The vertical range and the perturbation amplitude are given by
+			<A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_b</A>,
+			<A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_level_t</A>,
+			and <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">disturbance_amplitude</A>.
+			The time interval at which perturbations are to be imposed is set
+			by <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#dt_disturb">dt_disturb</A>.<BR><BR>In
+			case of non-cyclic horizontal boundaries <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#call_psolver_at_all_substeps">call_psolver
+			at_all_substeps</A> = .T. should be used.<BR><BR><B>Note:</B><BR>Using
+			non-cyclic lateral boundaries requires very sensitive adjustments
+			of the inflow (vertical profiles) and the bottom boundary
+			conditions, e.g. a surface heating should not be applied near the
+			inflow boundary because this may significantly disturb the inflow.
+			Please check the model results very carefully.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_ns"></A><B>bc_ns</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'cyclic'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Boundary condition along y (for all quantities).<BR><BR>By
+			default, a cyclic boundary condition is used along y.<BR><BR><B>bc_ns</B>
+			may also be assigned the values <I>'dirichlet/radiation'</I>
+			(inflow from rear (&quot;north&quot;), outflow to the front
+			(&quot;south&quot;)) or <I>'radiation/dirichlet'</I> (inflow from
+			front (&quot;south&quot;), outflow to the rear (&quot;north&quot;)).
+			This requires the multi-grid method to be used for solving the
+			Poisson equation for perturbation pressure (see <A HREF="chapter_4.2.html#psolver">psolver</A>)
+			and it also requires cyclic boundary conditions along x
+			(see<BR><A HREF="#bc_lr">bc_lr</A>).<BR><BR>In case of these
+			non-cyclic lateral boundaries, a Dirichlet condition is used at
+			the inflow for all quantities (initial vertical profiles - see
+			<A HREF="#initializing_actions">initializing_actions</A> - are
+			fixed during the run) except u, to which a Neumann (zero gradient)
+			condition is applied. At the outflow, a radiation condition is
+			used for all velocity components, while a Neumann (zero gradient)
+			condition is used for the scalars. For perturbation pressure
+			Neumann (zero gradient) conditions are assumed both at the inflow
+			and at the outflow.<BR><BR>For further details regarding
+			non-cyclic lateral boundary conditions see <A HREF="#bc_lr">bc_lr</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_p_b"></A><B>bc_p_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Bottom boundary condition of the
+			perturbation pressure.&nbsp; 
+			</P>
+			<P>Allowed values are <I>'dirichlet'</I>, <I>'neumann'</I> and
+			<I>'neumann+inhomo'</I>.&nbsp; <I>'dirichlet'</I> sets
+			p(k=0)=0.0,&nbsp; <I>'neumann'</I> sets p(k=0)=p(k=1).
+			<I>'neumann+inhomo'</I> corresponds to an extended Neumann
+			boundary condition where heat flux or temperature inhomogeneities
+			near the surface (pt(k=1))&nbsp; are additionally regarded (see
+			Shen and LeClerc (1995, Q.J.R. Meteorol. Soc., 1209)). This
+			condition is only permitted with the Prandtl-layer switched on
+			(<A HREF="#prandtl_layer">prandtl_layer</A>), otherwise the run is
+			terminated.&nbsp; 
+			</P>
+			<P>Since at the bottom boundary of the model the vertical velocity
+			disappears (w(k=0) = 0.0), the consistent Neumann condition
+			(<I>'neumann'</I> or <I>'neumann+inhomo'</I>) dp/dz = 0 should be
+			used, which leaves the vertical component w unchanged when the
+			pressure solver is applied. Simultaneous use of the Neumann
+			boundary conditions both at the bottom and at the top boundary
+			(<A HREF="#bc_p_t">bc_p_t</A>) usually yields no consistent
+			solution for the perturbation pressure and should be avoided.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_p_t"></A><B>bc_p_t</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Top boundary condition of the
+			perturbation pressure.&nbsp; 
+			</P>
+			<P STYLE="font-style: normal">Allowed values are <I>'dirichlet'</I>
+			(p(k=nz+1)= 0.0) or <I>'neumann'</I> (p(k=nz+1)=p(k=nz)).&nbsp; 
+			</P>
+			<P>Simultaneous use of Neumann boundary conditions both at the top
+			and bottom boundary (<A HREF="#bc_p_b">bc_p_b</A>) usually yields
+			no consistent solution for the perturbation pressure and should be
+			avoided. Since at the bottom boundary the Neumann condition&nbsp;
+			is a good choice (see <A HREF="#bc_p_b">bc_p_b</A>), a Dirichlet
+			condition should be set at the top boundary.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_pt_b"></A><B>bc_pt_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C*20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Bottom boundary condition of the
+			potential temperature.&nbsp; 
+			</P>
+			<P>Allowed values are <I>'dirichlet'</I> (pt(k=0) = const. =
+			<A HREF="#pt_surface">pt_surface</A> + <A HREF="#pt_surface_initial_change">pt_surface_initial_change</A>;
+			the user may change this value during the run using user-defined
+			code) and <I>'neumann'</I> (pt(k=0)=pt(k=1)).&nbsp; <BR>When a
+			constant surface sensible heat flux is used (<A HREF="#surface_heatflux">surface_heatflux</A>),
+			<B>bc_pt_b</B> = <I>'neumann'</I> must be used, because otherwise
+			the resolved scale may contribute to the surface flux so that a
+			constant value cannot be guaranteed.</P>
+			<P>In the <A HREF="chapter_3.8.html">coupled</A> atmosphere
+			executable,&nbsp;<A HREF="chapter_4.2.html#bc_pt_b">bc_pt_b</A> is
+			internally set and does not need to be prescribed.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pc_pt_t"></A><B>bc_pt_t</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'initial_ gradient'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Top boundary condition of the
+			potential temperature.&nbsp; 
+			</P>
+			<P>Allowed are the values <I>'dirichlet' </I>(pt(k=nz+1) does not
+			change during the run), <I>'neumann'</I> (pt(k=nz+1)=pt(k=nz)),
+			and <I>'initial_gradient'</I>. With the
+			'initial_gradient'-condition the value of the temperature gradient
+			at the top is calculated from the initial temperature profile (see
+			<A HREF="#pt_surface">pt_surface</A>, <A HREF="#pt_vertical_gradient">pt_vertical_gradient</A>)
+			by bc_pt_t_val = (pt_init(k=nz+1) - pt_init(k=nz)) /
+			dzu(nz+1).<BR>Using this value (assumed constant during the run)
+			the temperature boundary values are calculated as&nbsp; 
+			</P>
+			<UL>
+				<P STYLE="font-style: normal">pt(k=nz+1) = pt(k=nz) + bc_pt_t_val
+				* dzu(nz+1)</P>
+			</UL>
+			<P><SPAN STYLE="font-style: normal">(up to k=nz the prognostic
+			equation for the temperature is solved).<BR>When a constant
+			sensible heat flux is used at the top boundary (<A HREF="#top_heatflux">top_heatflux</A>),
+			</SPAN><SPAN STYLE="font-style: normal"><B>bc_pt_t</B></SPAN> <SPAN STYLE="font-style: normal">=
+			</SPAN><I>'neumann'</I> <SPAN STYLE="font-style: normal">must be
+			used, because otherwise the resolved scale may contribute to the
+			top flux so that a constant value cannot be guaranteed.</SPAN></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_q_b"></A><B>bc_q_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Bottom boundary condition of the
+			specific humidity / total water content.&nbsp; 
+			</P>
+			<P>Allowed values are <I>'dirichlet'</I> (q(k=0) = const. =
+			<A HREF="#q_surface">q_surface</A> + <A HREF="#q_surface_initial_change">q_surface_initial_change</A>;
+			the user may change this value during the run using user-defined
+			code) and <I>'neumann'</I> (q(k=0)=q(k=1)).&nbsp; <BR>When a
+			constant surface latent heat flux is used (<A HREF="#surface_waterflux">surface_waterflux</A>),
+			<B>bc_q_b</B> = <I>'neumann'</I> must be used, because otherwise
+			the resolved scale may contribute to the surface flux so that a
+			constant value cannot be guaranteed.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_q_t"></A><B>bc_q_t</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P><I>C * 20</I></P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Top boundary condition of the
+			specific humidity / total water content.&nbsp; 
+			</P>
+			<P>Allowed are the values <I>'dirichlet'</I> (q(k=nz) and
+			q(k=nz+1) do not change during the run) and <I>'neumann'</I>. With
+			the Neumann boundary condition the value of the humidity gradient
+			at the top is calculated from the initial humidity profile (see
+			<A HREF="#q_surface">q_surface</A>, <A HREF="#q_vertical_gradient">q_vertical_gradient</A>)
+			by: bc_q_t_val = ( q_init(k=nz) - q_init(k=nz-1)) / dzu(nz).<BR>Using
+			this value (assumed constant during the run) the humidity boundary
+			values are calculated as&nbsp; 
+			</P>
+			<UL>
+				<P STYLE="font-style: normal">q(k=nz+1) =q(k=nz) + bc_q_t_val *
+				dzu(nz+1)</P>
+			</UL>
+			<P STYLE="font-style: normal">(up tp k=nz the prognostic equation
+			for q is solved). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_s_b"></A><B>bc_s_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Bottom boundary condition of the
+			scalar concentration.&nbsp; 
+			</P>
+			<P>Allowed values are <I>'dirichlet'</I> (s(k=0) = const. =
+			<A HREF="#s_surface">s_surface</A> + <A HREF="#s_surface_initial_change">s_surface_initial_change</A>;
+			the user may change this value during the run using user-defined
+			code) and <I>'neumann'</I> (s(k=0) = s(k=1)).&nbsp; <BR>When a
+			constant surface concentration flux is used (<A HREF="#surface_scalarflux">surface_scalarflux</A>),
+			<B>bc_s_b</B> = <I>'neumann'</I> must be used, because otherwise
+			the resolved scale may contribute to the surface flux so that a
+			constant value cannot be guaranteed.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_s_t"></A><B>bc_s_t</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Top boundary condition of the scalar
+			concentration.&nbsp; 
+			</P>
+			<P>Allowed are the values <I>'dirichlet'</I> (s(k=nz) and
+			s(k=nz+1) do not change during the run) and <I>'neumann'</I>. With
+			the Neumann boundary condition the value of the scalar
+			concentration gradient at the top is calculated from the initial
+			scalar concentration profile (see <A HREF="#s_surface">s_surface</A>,
+			<A HREF="#s_vertical_gradient">s_vertical_gradient</A>) by:
+			bc_s_t_val = (s_init(k=nz) - s_init(k=nz-1)) / dzu(nz).<BR>Using
+			this value (assumed constant during the run) the concentration
+			boundary values are calculated as 
+			</P>
+			<UL>
+				<P STYLE="font-style: normal">s(k=nz+1) = s(k=nz) + bc_s_t_val *
+				dzu(nz+1)</P>
+			</UL>
+			<P STYLE="font-style: normal">(up to k=nz the prognostic equation
+			for the scalar concentration is solved).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_sa_t"></A><B>bc_sa_t</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Top boundary condition of the
+			salinity.&nbsp; 
+			</P>
+			<P>This parameter only comes into effect for ocean runs (see
+			parameter <A HREF="#ocean">ocean</A>).</P>
+			<P><SPAN STYLE="font-style: normal">Allowed are the values
+			</SPAN><I>'dirichlet' </I><SPAN STYLE="font-style: normal">(sa(k=nz+1)
+			does not change during the run) and </SPAN><I>'neumann'</I>
+			<SPAN STYLE="font-style: normal">(sa(k=nz+1)=sa(k=nz)).&nbsp;<BR><BR>When
+			a constant salinity flux is used at the top boundary
+			(<A HREF="#top_salinityflux">top_salinityflux</A>), </SPAN><SPAN STYLE="font-style: normal"><B>bc_sa_t</B></SPAN>
+			<SPAN STYLE="font-style: normal">= </SPAN><I>'neumann'</I> <SPAN STYLE="font-style: normal">must
+			be used, because otherwise the resolved scale may contribute to
+			the top flux so that a constant value cannot be guaranteed.</SPAN></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_uv_b"></A><B>bc_uv_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Bottom boundary condition of the
+			horizontal velocity components u and v.&nbsp; 
+			</P>
+			<P>Allowed values are <I>'dirichlet' </I>and <I>'neumann'</I>.
+			<B>bc_uv_b</B> = <I>'dirichlet'</I> yields the no-slip condition
+			with u=v=0 at the bottom. Due to the staggered grid u(k=0) and
+			v(k=0) are located at z = - 0,5 * <A HREF="#dz">dz</A> (below the
+			bottom), while u(k=1) and v(k=1) are located at z = +0,5 * dz.
+			u=v=0 at the bottom is guaranteed using mirror boundary
+			condition:&nbsp; 
+			</P>
+			<UL>
+				<P STYLE="font-style: normal">u(k=0) = - u(k=1) and v(k=0) = -
+				v(k=1)</P>
+			</UL>
+			<P><SPAN STYLE="font-style: normal">The Neumann boundary condition
+			yields the free-slip condition with u(k=0) = u(k=1) and v(k=0) =
+			v(k=1). With Prandtl - layer switched on (see <A HREF="#prandtl_layer">prandtl_layer</A>),
+			the free-slip condition is not allowed (otherwise the run will be
+			terminated)</SPAN><FONT COLOR="#000000"><SPAN STYLE="font-style: normal">.</SPAN></FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bc_uv_t"></A><B>bc_uv_t</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Top boundary condition of the
+			horizontal velocity components u and v.&nbsp; 
+			</P>
+			<P>Allowed values are <I>'dirichlet'</I>, <I>'dirichlet_0'</I> and
+			<I>'neumann'</I>. The Dirichlet condition yields u(k=nz+1) =
+			ug(nz+1) and v(k=nz+1) = vg(nz+1), Neumann condition yields the
+			free-slip condition with u(k=nz+1) = u(k=nz) and v(k=nz+1) =
+			v(k=nz) (up to k=nz the prognostic equations for the velocities
+			are solved). The special condition&nbsp;<I>'dirichlet_0'</I> can
+			be used for channel flow, it yields the no-slip condition
+			u(k=nz+1) = ug(nz+1) = 0 and v(k=nz+1) = vg(nz+1) = 0.</P>
+			<P>In the <A HREF="chapter_3.8.html">coupled</A> ocean executable,
+			<A HREF="chapter_4.2.html#bc_uv_t">bc_uv_t</A>&nbsp;is internally
+			set ('neumann') and does not need to be prescribed.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="bottom_salinityflux"></A><B>bottom_salinityflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Kinematic salinity flux near the surface (in psu m/s).&nbsp;</P>
+			<P>This parameter only comes into effect for ocean runs (see
+			parameter <A HREF="#ocean">ocean</A>). 
+			</P>
+			<P>The respective salinity flux value is used as bottom
+			(horizontally homogeneous) boundary condition for the salinity
+			equation. This additionally requires that a Neumann condition must
+			be used for the salinity, which is currently the only available
+			condition.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="building_height"></A><B>building_height</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height of a single building in m.<BR><BR><B>building_height</B>
+			must be less than the height of the model domain. This parameter
+			requires the use of&nbsp;<A HREF="#topography">topography</A> =
+			<I>'single_building'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="building_length_x"></A><B>building_length_x</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Width of a single building in m.<BR><BR>Currently,
+			<B>building_length_x</B> must be at least <I>3 *&nbsp;<A HREF="#dx">dx</A></I>
+			and no more than <I>(&nbsp;<A HREF="#nx">nx</A></I> <I>- 1 ) * <A HREF="#dx">dx</A>
+			- <A HREF="#building_wall_left">building_wall_left</A></I>. This
+			parameter requires the use of&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_building'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="building_length_y"></A><B>building_length_y</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Depth of a single building in m.<BR><BR>Currently,
+			<B>building_length_y</B> must be at least <I>3 *&nbsp;<A HREF="#dy">dy</A></I>
+			and no more than <I>(&nbsp;<A HREF="#ny">ny</A></I> <I>- 1 )&nbsp;</I>
+			<I>* <A HREF="#dy">dy</A></I> <I>- <A HREF="#building_wall_south">building_wall_south</A></I>.
+			This parameter requires the use of&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_building'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="building_wall_left"></A><B>building_wall_left</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>building centered in x-direction</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>x-coordinate of the left building wall (distance between the
+			left building wall and the left border of the model domain) in
+			m.<BR><BR>Currently, <B>building_wall_left</B> must be at least <I>1
+			*&nbsp;<A HREF="#dx">dx</A></I> and less than <I>( <A HREF="#nx">nx</A>&nbsp;
+			- 1 ) * <A HREF="#dx">dx</A> -&nbsp; <A HREF="#building_length_x">building_length_x</A></I>.
+			This parameter requires the use of&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_building'</I>.<BR><BR>The default
+			value&nbsp;<B>building_wall_left</B> = <I>( ( <A HREF="#nx">nx</A>&nbsp;+
+			1 ) * <A HREF="#dx">dx</A> -&nbsp; <A HREF="#building_length_x">building_length_x</A>
+			) / 2</I> centers the building in x-direction.&nbsp;<FONT COLOR="#000000">Due
+			to the staggered grid the building will be displaced by -0.5 <A HREF="#dx">dx</A>
+			in x-direction and -0.5 <A HREF="#dy">dy</A> in y-direction.</FONT>
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="building_wall_south"></A><B>building_wall_south</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>building centered in y-direction</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>y-coordinate of the South building wall (distance between the
+			South building wall and the South border of the model domain) in
+			m.<BR><BR>Currently, <B>building_wall_south</B> must be at least <I>1
+			*&nbsp;<A HREF="#dy">dy</A></I> and less than <I>( <A HREF="#ny">ny</A>&nbsp;
+			- 1 ) * <A HREF="#dy">dy</A> -&nbsp; <A HREF="#building_length_y">building_length_y</A></I>.
+			This parameter requires the use of&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_building'</I>.<BR><BR>The default
+			value&nbsp;<B>building_wall_south</B> = <I>( ( <A HREF="#ny">ny</A>&nbsp;+
+			1 ) * <A HREF="#dy">dy</A> -&nbsp; <A HREF="#building_length_y">building_length_y</A>
+			) / 2</I> centers the building in y-direction.&nbsp;<FONT COLOR="#000000">Due
+			to the staggered grid the building will be displaced by -0.5 <A HREF="#dx">dx</A>
+			in x-direction and -0.5 <A HREF="#dy">dy</A> in y-direction.</FONT>
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="canopy_mode"></A><B>canopy_mode</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'block'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Canopy mode.<BR><BR><FONT COLOR="#000000">Besides using the
+			default value, that will create a horizontally homogeneous plant
+			canopy that extends over the total horizontal extension of the
+			model domain, the user may add code to the user interface
+			subroutine <A HREF="chapter_3.5.1.html#user_init_plant_canopy">user_init_plant_canopy</A>
+			to allow further canopy&nbsp;modes. <BR><BR>The setting of
+			<A HREF="#canopy_mode">canopy_mode</A> becomes only active,
+			if&nbsp;<A HREF="#plant_canopy">plant_canopy</A> has been set </FONT><FONT COLOR="#000000"><I>.T.</I></FONT><FONT COLOR="#000000">
+			and a non-zero <A HREF="#drag_coefficient">drag_coefficient</A>
+			has been defined.</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="canyon_height"></A><B>canyon_height</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Street canyon height in m.<BR><BR><B>canyon_height</B> must be
+			less than the height of the model domain. This parameter
+			requires&nbsp;<A HREF="#topography">topography</A> =
+			<I>'single_street_canyon'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="canyon_width_x"></A><B>canyon_width_x</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Street canyon width in x-direction in m.<BR><BR>Currently,
+			<B>canyon_width_x</B> must be at least <I>3 *&nbsp;<A HREF="#dx">dx</A></I>
+			and no more than <I>(&nbsp;<A HREF="#nx">nx</A></I> <I>- 1 ) * <A HREF="#dx">dx</A>
+			- <A HREF="#canyon_wall_left">canyon_wall_left</A></I>. This
+			parameter requires&nbsp;<A HREF="#topography">topography</A> =
+			<I>'single_street_canyon'</I>. A non-default value implies a
+			canyon orientation in y-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="canyon_width_y"></A><B>canyon_width_y</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Street canyon width in y-direction in m.<BR><BR>Currently,
+			<B>canyon_width_y</B> must be at least <I>3 *&nbsp;<A HREF="#dy">dy</A></I>
+			and no more than <I>(&nbsp;<A HREF="#ny">ny</A></I> <I>- 1 )&nbsp;</I>
+			<I>* <A HREF="#dy">dy</A></I> <I>- <A HREF="#canyon_wall_south">canyon_wall_south</A></I>.
+			This parameter requires&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_street_canyon</I>.&nbsp;A non-default value implies a
+			canyon orientation in x-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="canyon_wall_left"></A><B>canyon_wall_left</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>canyon centered in x-direction</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>x-coordinate of the left canyon wall (distance between the left
+			canyon wall and the left border of the model domain) in
+			m.<BR><BR>Currently, <B>canyon_wall_left</B> must be at least <I>1
+			*&nbsp;<A HREF="#dx">dx</A></I> and less than <I>( <A HREF="#nx">nx</A>&nbsp;
+			- 1 ) * <A HREF="#dx">dx</A> -&nbsp; <A HREF="#canyon_width_x">canyon_width_x</A></I>.
+			This parameter requires&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_street_canyon'</I>.<BR><BR>The default value
+			<B>canyon_wall_left</B> = <I>( ( <A HREF="#nx">nx</A>&nbsp;+ 1 ) *
+			<A HREF="#dx">dx</A> -&nbsp; <A HREF="#canyon_width_x">canyon_width_x</A>
+			) / 2</I> centers the canyon in x-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="canyon_wall_south"></A><B>canyon_wall_south</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>canyon centered in y-direction</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>y-coordinate of the South canyon wall (distance between the
+			South canyon wall and the South border of the model domain) in
+			m.<BR><BR>Currently, <B>canyon_wall_south</B> must be at least <I>1
+			*&nbsp;<A HREF="#dy">dy</A></I> and less than <I>( <A HREF="#ny">ny</A>&nbsp;
+			- 1 ) * <A HREF="#dy">dy</A> -&nbsp; <A HREF="#canyon_width_y">canyon_width_y</A></I>.
+			This parameter requires&nbsp;<A HREF="#topography">topography</A>
+			= <I>'single_street_canyon'</I>.<BR><BR>The default value
+			<B>canyon_wall_south</B> = <I>( ( <A HREF="#ny">ny</A>&nbsp;+ 1 )
+			* <A HREF="#dy">dy</A> -&nbsp;&nbsp;<A HREF="#canyon_width_y">canyon_wid</A><A HREF="#canyon_width_y">th_y</A>
+			) / 2</I> centers the canyon in y-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="cloud_droplets"></A><B>cloud_droplets</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on usage of cloud droplets.<BR><BR>Cloud
+			droplets require to use&nbsp;particles (i.e. the NAMELIST group
+			<FONT FACE="Courier New, Courier, monospace">particles_par</FONT>
+			has to be included in the parameter file). Then each particle is a
+			representative for a certain number of droplets. The droplet
+			features (number of droplets, initial radius, etc.) can be steered
+			with the&nbsp; respective particle parameters (see e.g. <A HREF="#chapter_4.2.html#radius">radius</A>).
+			The real number of initial droplets in a grid cell is equal to the
+			initial number of droplets (defined by the particle source
+			parameters <FONT FACE="Thorndale, serif"><SPAN LANG="en-GB"><A HREF="chapter_4.2.html#pst">pst</A>,
+			<A HREF="chapter_4.2.html#psl">psl</A>, <A HREF="chapter_4.2.html#psr">psr</A>,
+			<A HREF="chapter_4.2.html#pss">pss</A>, <A HREF="chapter_4.2.html#psn">psn</A>,
+			<A HREF="chapter_4.2.html#psb">psb</A>, <A HREF="chapter_4.2.html#pdx">pdx</A>,
+			<A HREF="chapter_4.2.html#pdy">pdy</A></SPAN></FONT> <FONT FACE="Thorndale, serif"><SPAN LANG="en-GB">and
+			<A HREF="chapter_4.2.html#pdz">pdz</A></SPAN></FONT>) times the
+			<A HREF="#initial_weighting_factor">initial_weighting_factor</A>.<BR><BR>In
+			case of using cloud droplets, the default condensation scheme in
+			PALM cannot be used, i.e. <A HREF="#cloud_physics">cloud_physics</A>
+			must be set <I>.F.</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="cloud_physics"></A><B>cloud_physics</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on the condensation scheme.&nbsp; 
+			</P>
+			<P>For <B>cloud_physics =</B> <I>.TRUE.</I>, equations for the
+			liquid water&nbsp; content and the liquid water potential
+			temperature are solved instead of those for specific humidity and
+			potential temperature. Note that a grid volume is assumed to be
+			either completely saturated or completely unsaturated
+			(0%-or-100%-scheme). A simple precipitation scheme can
+			additionally be switched on with parameter <A HREF="#precipitation">precipitation</A>.
+			Also cloud-top cooling by longwave radiation can be utilized (see
+			<A HREF="#radiation">radiation</A>)<BR><B><BR>cloud_physics =</B>
+			<I>.TRUE. </I>requires&nbsp;<A HREF="#humidity">humidity</A> =
+			<I>.TRUE.</I> .<BR>Detailed information about the condensation
+			scheme is given in the description of the <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM-1/Dokumentationen/Cloud_physics/wolken.pdf">cloud
+			physics module</A> (pdf-file, only in German).<BR><BR>This
+			condensation scheme is not allowed if cloud droplets are simulated
+			explicitly (see <A HREF="#cloud_droplets">cloud_droplets</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="conserve_volume_flow"></A><B>conserve_volume_flow</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Conservation of volume flow in x- and
+			y-direction.<BR><BR><B>conserve_volume_flow</B> = <I>.T.</I>
+			guarantees that the volume flow through the xz- and
+			yz-cross-sections of the total model domain remains constant
+			throughout the run depending on the chosen
+			<A HREF="#conserve_volume_flow_mode">conserve_volume_flow_mode</A>.<BR><BR>Note
+			that&nbsp;<B>conserve_volume_flow</B> = <I>.T.</I> requires
+			<A HREF="#dp_external">dp_external</A> = <I>.F.</I> .</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="conserve_volume_flow_mode"></A><B>conserve_volume_flow_mode</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 16</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'default'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Modus of volume flow conservation.<BR><BR>The following values
+			are allowed:</P>
+			<P STYLE="font-style: normal"><I>'default'</I> 
+			</P>
+			<UL>
+				<P>Per default, PALM uses&nbsp;<I>'initial_profiles'</I> for
+				cyclic lateral boundary conditions (<A HREF="#bc_lr">bc_lr</A> =
+				<I>'cyclic'</I> and <A HREF="#bc_ns">bc_ns</A> = <I>'cyclic'</I>)
+				and&nbsp;<I>'inflow_profile'</I> for non-cyclic lateral boundary
+				conditions (<A HREF="#bc_lr">bc_lr</A> /= <I>'cyclic'</I> or
+				<A HREF="#bc_ns">bc_ns</A> /= <I>'cyclic'</I>).</P>
+			</UL>
+			<P><I>'initial_profiles' </I>
+			</P>
+			<UL>
+				<P>The target volume flow&nbsp;is calculated at t=0 from the
+				initial profiles of u and v.&nbsp;This setting is only allowed
+				for&nbsp;cyclic lateral boundary conditions (<A HREF="#bc_lr">bc_lr</A>
+				= <I>'cyclic'</I> and <A HREF="#bc_ns">bc_ns</A> = <I>'cyclic'</I>).</P>
+			</UL>
+			<P STYLE="font-style: normal"><I>'inflow_profile'</I> 
+			</P>
+			<UL>
+				<P>The target volume flow&nbsp;is&nbsp;calculated at every
+				timestep from the inflow profile of&nbsp;u or v, respectively.
+				This setting&nbsp;is only allowed for&nbsp;non-cyclic lateral
+				boundary conditions (<A HREF="#bc_lr">bc_lr</A> /= <I>'cyclic'</I>
+				or <A HREF="#bc_ns">bc_ns</A> /= <I>'cyclic'</I>).</P>
+			</UL>
+			<P><I>'bulk_velocity' </I>
+			</P>
+			<UL>
+				<P>The target volume flow is calculated from a predefined bulk
+				velocity (see <A HREF="#u_bulk">u_bulk</A> and <A HREF="#v_bulk">v_bulk</A>).
+				This setting is only allowed for&nbsp;cyclic lateral boundary
+				conditions (<A HREF="#bc_lr">bc_lr</A> = <I>'cyclic'</I> and
+				<A HREF="#bc_ns">bc_ns</A> = <I>'cyclic'</I>).</P>
+			</UL>
+			<P>Note that&nbsp;<B>conserve_volume_flow_mode</B> only comes into
+			effect if <A HREF="#conserve_volume_flow">conserve_volume_flow</A>
+			= <I>.T. .</I> 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="coupling_start_time"></A><B>coupling_start_time</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Simulation time of precursor run.</P>
+			<P>Sets the time period a precursor run shall run uncoupled. This
+			parameter is used to set up the precursor run control for
+			atmosphere-ocean-<A HREF="chapter_3.8.html">coupled runs</A>. It
+			has to be set individually to the atmospheric / oceanic precursor
+			run. The time in the data output will show negative values during
+			the precursor run. See <A HREF="../misc/precursor_run_control.pdf">documentation</A>
+			for further information.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="cthf"></A><B>cthf</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Average heat flux that is prescribed at the top of the plant
+			canopy.<BR><BR>If <A HREF="#plant_canopy">plant_canopy</A> is set
+			<I>.T.</I>, the user can prescribe a heat flux at the top of the
+			plant canopy.<BR>It is assumed that solar radiation penetrates the
+			canopy and warms the foliage which, in turn, warms the air in
+			contact with it. <BR>Note: Instead of using the value prescribed
+			by <A HREF="#surface_heatflux">surface_heatflux</A>, the near
+			surface heat flux is determined from an exponential function that
+			is dependent on the cumulative leaf_area_index (Shaw and Schumann
+			(1992, Boundary Layer Meteorol., 61, 47-64)).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="cut_spline_overshoot"></A><B>cut_spline_overshoot</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Cuts off of so-called overshoots, which can occur with the
+			upstream-spline scheme.&nbsp; 
+			</P>
+			<P><FONT COLOR="#000000">The cubic splines tend to overshoot in
+			case of discontinuous changes of variables between neighbouring
+			grid points.</FONT><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#000000">This
+			may lead to errors in calculating the advection tendency.</FONT>
+			Choice of <B>cut_spline_overshoot</B> = <I>.TRUE.</I> (switched on
+			by default) allows variable values not to exceed an interval
+			defined by the respective adjacent grid points. This interval can
+			be adjusted seperately for every prognostic variable (see
+			initialization parameters <A HREF="#overshoot_limit_e">overshoot_limit_e</A>,
+			<A HREF="#overshoot_limit_pt">overshoot_limit_pt</A>,
+			<A HREF="#overshoot_limit_u">overshoot_limit_u</A>, etc.). This
+			might be necessary in case that the default interval has a
+			non-tolerable effect on the model results.&nbsp; 
+			</P>
+			<P>Overshoots may also be removed using the parameters
+			<A HREF="#ups_limit_e">ups_limit_e</A>, <A HREF="#ups_limit_pt">ups_limit_pt</A>,
+			etc. as well as by applying a long-filter (see
+			<A HREF="#long_filter_factor">long_filter_factor</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="damp_level_1d"></A><B>damp_level_1d</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>zu(nz+1)</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height where the damping layer begins in the 1d-model (in m).&nbsp;
+						</P>
+			<P>This parameter is used to switch on a damping layer for the
+			1d-model, which is generally needed for the damping of inertia
+			oscillations. Damping is done by gradually increasing the value of
+			the eddy diffusivities about 10% per vertical grid level (starting
+			with the value at the height given by <B>damp_level_1d</B>, or
+			possibly from the next grid pint above), i.e. K<SUB>m</SUB>(k+1) =
+			1.1 * K<SUB>m</SUB>(k). The values of K<SUB>m</SUB> are limited to
+			10 m**2/s at maximum.&nbsp; <BR>This parameter only comes into
+			effect if the 1d-model is switched on for the initialization of
+			the 3d-model using <A HREF="#initializing_actions">initializing_actions</A>
+			= <I>'set_1d-model_profiles'</I>. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dissipation_1d"></A><B>dissipation_1d</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C*20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'as_in_3d_</I><BR><I>model'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Calculation method for the energy dissipation term in the TKE
+			equation of the 1d-model.<BR><BR>By default the dissipation is
+			calculated as in the 3d-model using diss = (0.19 + 0.74 * l /
+			l_grid) * e**1.5 / l.<BR><BR>Setting <B>dissipation_1d</B> =
+			<I>'detering'</I> forces the dissipation to be calculated as diss
+			= 0.064 * e**1.5 / l.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dp_external"></A><B>dp_external</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>External pressure gradient switch.<BR><BR>This parameter is
+			used to switch on/off an external pressure gradient as driving
+			force. The external pressure gradient is controlled by the
+			parameters <A HREF="#dp_smooth">dp_smooth</A>, <A HREF="#dp_level_b">dp_level_b</A>
+			and <A HREF="#dpdxy">dpdxy</A>.<BR><BR>Note that&nbsp;<B>dp_external</B>
+			= <I>.T.</I> requires <A HREF="#conserve_volume_flow">conserve_volume_flow</A>
+			= <I>.F. </I>It is normally recommended to disable the Coriolis
+			force by setting <A HREF="l#omega">omega</A> = 0.0.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dp_smooth"></A><B>dp_smooth</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Vertically smooth the external pressure gradient using a
+			sinusoidal smoothing function.<BR><BR>This parameter only applies
+			if <A HREF="#dp_external">dp_external</A> = <I>.T. </I>. It is
+			useful in combination with&nbsp;<A HREF="#dp_level_b">dp_level_b</A>
+			&gt;&gt; 0 to generate a non-accelerated boundary layer well
+			below&nbsp;<A HREF="#dp_level_b">dp_level_b</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dp_level_b"></A><B>dp_level_b</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P><FONT SIZE=3>Lower limit of the vertical range for which the
+			external pressure gradient is applied (</FONT>in <FONT SIZE=3>m).</FONT><BR><BR>This
+			parameter only applies if <A HREF="#dp_external">dp_external</A> =
+			<I>.T. </I><SPAN LANG="en-GB">It must hold the condition zu(0) &lt;=
+			</SPAN><SPAN LANG="en-GB"><B>dp_level_b</B></SPAN> <SPAN LANG="en-GB">&lt;=
+			zu(<A HREF="#nz">nz</A>).&nbsp;</SPAN>It can be used in
+			combination with&nbsp;<A HREF="#dp_smooth">dp_smooth</A> = <I>.T.</I>
+			to generate a non-accelerated boundary layer well below&nbsp;<B>dp_level_b</B>
+			if&nbsp;<B>dp_level_b</B> &gt;&gt; 0.<BR><BR>Note that there is no
+			upper limit of the vertical range because the external pressure
+			gradient is always applied up to the top of the model domain.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dpdxy"></A><B>dpdxy</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(2)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>2 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Values of the external pressure gradient applied in x- and
+			y-direction, respectively (in Pa/m).<BR><BR>This parameter only
+			applies if <A HREF="#dp_external">dp_external</A> = <I>.T. </I>It
+			sets the pressure gradient values. Negative values mean an
+			acceleration, positive values mean deceleration. For example,
+			<B>dpdxy</B> = -0.0002, 0.0, drives the flow in positive
+			x-direction, 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="drag_coefficient"></A><B>drag_coefficient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Drag coefficient used in the plant canopy model.<BR><BR>This
+			parameter has to be non-zero, if the parameter <A HREF="#plant_canopy">plant_canopy</A>
+			is set <I>.T.</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dt"></A><B>dt</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>variable</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Time step for the 3d-model (in s).&nbsp; 
+			</P>
+			<P>By default, (i.e. if a Runge-Kutta scheme is used, see
+			<A HREF="#timestep_scheme">timestep_scheme</A>) the value of the
+			time step is calculating after each time step (following the time
+			step criteria) and used for the next step.</P>
+			<P>If the user assigns <B>dt</B> a value, then the time step is
+			fixed to this value throughout the whole run (whether it fulfills
+			the time step criteria or not). However, changes are allowed for
+			restart runs, because <B>dt</B> can also be used as a <A HREF="chapter_4.2.html#dt_laufparameter">run
+			parameter</A>.&nbsp; 
+			</P>
+			<P>In case that the calculated time step meets the condition</P>
+			<UL>
+				<P><B>dt</B> &lt; 0.00001 * <A HREF="chapter_4.2.html#dt_max">dt_max</A>
+				(with dt_max = 20.0)</P>
+			</UL>
+			<P>the simulation will be aborted. Such situations usually arise
+			in case of any numerical problem / instability which causes a
+			non-realistic increase of the wind speed.&nbsp; 
+			</P>
+			<P>A small time step due to a large mean horizontal windspeed
+			speed may be enlarged by using a coordinate transformation (see
+			<A HREF="#galilei_transformation">galilei_transformation</A>), in
+			order to spare CPU time.</P>
+			<P>If the leapfrog timestep scheme is used (see <A HREF="#timestep_scheme">timestep_scheme</A>)
+			a temporary time step value dt_new is calculated first, with
+			dt_new = <A HREF="chapter_4.2.html#fcl_factor">cfl_factor</A> *
+			dt_crit where dt_crit is the maximum timestep allowed by the CFL
+			and diffusion condition. Next it is examined whether dt_new
+			exceeds or falls below the value of the previous timestep by at
+			least +5 % / -2%. If it is smaller, <B>dt</B> = dt_new is
+			immediately used for the next timestep. If it is larger, then <B>dt
+			</B>= 1.02 * dt_prev (previous timestep) is used as the new
+			timestep, however the time step is only increased if the last
+			change of the time step is dated back at least 30 iterations. If
+			dt_new is located in the interval mentioned above, then dt does
+			not change at all. By doing so, permanent time step changes as
+			well as large sudden changes (increases) in the time step are
+			avoided.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dt_pr_1d"></A><B>dt_pr_1d</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Temporal interval of vertical profile output of the 1D-model
+			(in s).&nbsp; 
+			</P>
+			<P>Data are written in ASCII format to file <A HREF="chapter_3.4.html#LIST_PROFIL_1D">LIST_PROFIL_1D</A>.
+			This parameter is only in effect if the 1d-model has been switched
+			on for the initialization of the 3d-model with
+			<A HREF="#initializing_actions">initializing_actions</A> =
+			<I>'set_1d-model_profiles'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dt_run_control_1d"></A><B>dt_run_control_1d</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>60.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Temporal interval of runtime control output of the 1d-model (in
+			s).&nbsp; 
+			</P>
+			<P>Data are written in ASCII format to file <A HREF="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</A>.
+			This parameter is only in effect if the 1d-model is switched on
+			for the initialization of the 3d-model with <A HREF="#initializing_actions">initializing_actions</A>
+			= <I>'set_1d-model_profiles'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dx"></A><B>dx</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Horizontal grid spacing along the x-direction (in m).&nbsp; 
+			</P>
+			<P>Along x-direction only a constant grid spacing is allowed.</P>
+			<P>For <A HREF="chapter_3.8.html">coupled runs</A> this parameter
+			must be&nbsp;equal in both parameter files <A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN</FONT></A>
+			and&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dy"></A><B>dy</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Horizontal grid spacing along the y-direction (in m).&nbsp; 
+			</P>
+			<P>Along y-direction only a constant grid spacing is allowed.</P>
+			<P>For <A HREF="chapter_3.8.html">coupled runs</A> this parameter
+			must be&nbsp;equal in both parameter files <A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN</FONT></A>
+			and&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dz"></A><B>dz</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><BR>
+			</P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Vertical grid spacing (in m).&nbsp; 
+			</P>
+			<P>This parameter must be assigned by the user, because no default
+			value is given.</P>
+			<P>By default, the model uses constant grid spacing along
+			z-direction, but it can be stretched using the parameters
+			<A HREF="#dz_stretch_level">dz_stretch_level</A> and
+			<A HREF="#dz_stretch_factor">dz_stretch_factor</A>. In case of
+			stretching, a maximum allowed grid spacing can be given by <A HREF="#dz_max">dz_max</A>.</P>
+			<P>Assuming a constant <B>dz</B>, the scalar levels (zu) are
+			calculated directly by:&nbsp; 
+			</P>
+			<UL>
+				<P>zu(0) = - dz * 0.5&nbsp; <BR>zu(1) = dz * 0.5</P>
+			</UL>
+			<P>The w-levels lie half between them:&nbsp; 
+			</P>
+			<UL>
+				<P>zw(k) = ( zu(k) + zu(k+1) ) * 0.5</P>
+			</UL>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dz_max"></A><B>dz_max</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Allowed maximum vertical grid spacing (in m).<BR><BR>If the
+			vertical grid is stretched (see <A HREF="#dz_stretch_factor">dz_stretch_factor</A>
+			and <A HREF="#dz_stretch_level">dz_stretch_level</A>), <B>dz_max</B>
+			can be used to limit the vertical grid spacing.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dz_stretch_factor"></A><B>dz_stretch_factor</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>1.08</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Stretch factor for a vertically stretched grid (see
+			<A HREF="#dz_stretch_level">dz_stretch_level</A>).&nbsp; 
+			</P>
+			<P>The stretch factor should not exceed a value of approx. 1.10 -
+			1.12, otherwise the discretization errors due to the stretched
+			grid not negligible any more. (refer Kalnay de Rivas)</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="dz_stretch_level"></A><B>dz_stretch_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>100000.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level above/below which the grid is to be stretched
+			vertically (in m).&nbsp; 
+			</P>
+			<P>For <A HREF="#ocean">ocean</A> = .F., <B>dz_stretch_level </B>is
+			the height level (in m)&nbsp;<B>above </B>which the grid is to be
+			stretched vertically. The vertical grid spacings <A HREF="#dz">dz</A>
+			above this level are calculated as&nbsp; 
+			</P>
+			<UL>
+				<P><B>dz</B>(k+1) = <B>dz</B>(k) * <A HREF="#dz_stretch_factor">dz_stretch_factor</A></P>
+			</UL>
+			<P>and used as spacings for the scalar levels (zu). The w-levels
+			are then defined as:&nbsp; 
+			</P>
+			<UL>
+				<P>zw(k) = ( zu(k) + zu(k+1) ) * 0.5. 
+				</P>
+			</UL>
+			<P>For <A HREF="#ocean">ocean</A> = .T., <B>dz_stretch_level </B>is
+			the height level (in m, negative) <B>below</B> which the grid is
+			to be stretched vertically. The vertical grid spacings <A HREF="#dz">dz</A>
+			below this level are calculated correspondingly as 
+			</P>
+			<UL>
+				<P><B>dz</B>(k-1) = <B>dz</B>(k) * <A HREF="#dz_stretch_factor">dz_stretch_factor</A>.</P>
+			</UL>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="e_init"></A><B>e_init</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Initial subgrid-scale TKE in m<SUP>2</SUP>s<SUP>-2</SUP>.<BR><BR>This
+			option prescribes an initial&nbsp;subgrid-scale TKE from which the
+			initial diffusion coefficients K<SUB>m</SUB> and K<SUB>h</SUB>
+			will be calculated if <B>e_init</B> is positive. This option only
+			has an effect if&nbsp;<A HREF="#km_constant">km_constant</A> is
+			not set.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="e_min"></A><B>e_min</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Minimum subgrid-scale TKE in m<SUP>2</SUP>s<SUP>-2</SUP>.<BR><BR>This
+			option&nbsp;adds artificial viscosity to the flow by ensuring that
+			the subgrid-scale TKE does not fall below the minimum threshold
+			<B>e_min</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="end_time_1d"></A><B>end_time_1d</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>864000.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Time to be simulated for the 1d-model (in s).&nbsp; 
+			</P>
+			<P>The default value corresponds to a simulated time of 10 days.
+			Usually, after such a period the inertia oscillations have
+			completely decayed and the solution of the 1d-model can be
+			regarded as stationary (see <A HREF="#damp_level_1d">damp_level_1d</A>).
+			This parameter is only in effect if the 1d-model is switched on
+			for the initialization of the 3d-model with <A HREF="#initializing_actions">initializing_actions</A>
+			= <I>'set_1d-model_profiles'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="fft_method"></A><B>fft_method</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'system-</I><BR><I>specific'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>FFT-method to be used.</P>
+			<P><BR>The fast fourier transformation (FFT) is used for solving
+			the perturbation pressure equation with a direct method (see
+			<A HREF="chapter_4.2.html#psolver">psolver</A>) and for
+			calculating power spectra (see optional software packages, section
+			<A HREF="chapter_4.2.html#spectra_package">4.2</A>).</P>
+			<P><BR>By default, system-specific, optimized routines from
+			external vendor libraries are used. However, these are available
+			only on certain computers and there are more or less severe
+			restrictions concerning the number of gridpoints to be used with
+			them.</P>
+			<P>There are two other PALM internal methods available on every
+			machine (their respective source code is part of the PALM source
+			code):</P>
+			<P>1.: The <B>Temperton</B>-method from Clive Temperton (ECWMF)
+			which is computationally very fast and switched on with <B>fft_method</B>
+			= <I>'temperton-algorithm'</I>. The number of horizontal
+			gridpoints (nx+1, ny+1) to be used with this method must be
+			composed of prime factors 2, 3 and 5.</P>
+			<P>2.: The <B>Singleton</B>-method which is very slow but has no
+			restrictions concerning the number of gridpoints to be used with,
+			switched on with <B>fft_method</B> = <I>'singleton-algorithm'</I>.
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="galilei_transformation"></A><B>galilei_transformation</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Application of a Galilei-transformation to the coordinate
+			system of the model.</P>
+			<P>With <B>galilei_transformation</B> = <I>.T.,</I> a so-called
+			Galilei-transformation is switched on which ensures that the
+			coordinate system of the model is moved along with the
+			geostrophical wind. Alternatively, the model domain can be moved
+			along with the averaged horizontal wind (see
+			<A HREF="#use_ug_for_galilei_tr">use_ug_for_galilei_tr</A>, this
+			can and will naturally change in time). With this method,
+			numerical inaccuracies of the Piascek - Williams - scheme
+			(concerns in particular the momentum advection) are minimized.
+			Beyond that, in the majority of cases the lower relative
+			velocities in the moved system permit a larger time step (<A HREF="#dt">dt</A>).
+			Switching the transformation on is only worthwhile if the
+			geostrophical wind (ug, vg) and the averaged horizontal wind
+			clearly deviate from the value 0. In each case, the distance the
+			coordinate system has been moved is written to the file
+			<A HREF="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</A>.&nbsp; 
+			</P>
+			<P>Non-cyclic lateral boundary conditions (see <A HREF="#bc_lr">bc_lr</A>
+			and <A HREF="#bc_ns">bc_ns</A>), the specification of a gestrophic
+			wind that is not constant with height as well as e.g. stationary
+			inhomogeneities at the bottom boundary do not allow the use of
+			this transformation.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="grid_matching"></A><B>grid_matching</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 6</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'strict'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Variable to adjust the subdomain sizes in parallel runs.<BR><BR>For
+			<B>grid_matching</B> = <I>'strict'</I>, the subdomains are forced
+			to have an identical size on all processors. In this case the
+			processor numbers in the respective directions of the virtual
+			processor net must fulfill certain divisor conditions concerning
+			the grid point numbers in the three directions (see <A HREF="#nx">nx</A>,
+			<A HREF="#ny">ny</A> and <A HREF="#nz">nz</A>). Advantage of this
+			method is that all PEs bear the same computational load.<BR><BR>There
+			is no such restriction by default, because then smaller subdomains
+			are allowed on those processors which form the right and/or north
+			boundary of the virtual processor grid. On all other processors
+			the subdomains are of same size. Whether smaller subdomains are
+			actually used, depends on the number of processors and the grid
+			point numbers used. Information about the respective settings are
+			given in file <A HREF="../../../../../../raasch/public_html/PALM_group/home/raasch/public_html/PALM_group/doc/app/chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</A>.<BR><BR>When
+			using a multi-grid method for solving the Poisson equation (see
+			<A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.2.html#psolver">psolver</A>)
+			only <B>grid_matching</B> = <I>'strict'</I> is allowed.<BR><BR><B>Note:</B><BR>In
+			some cases for small processor numbers there may be a very bad
+			load balancing among the processors which may reduce the
+			performance of the code.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="humidity"></A><B>humidity</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on the prognostic equation for specific
+			humidity q.</P>
+			<P>The initial vertical profile of q can be set via parameters
+			<A HREF="#q_surface">q_surface</A>, <A HREF="#q_vertical_gradient">q_vertical_gradient</A>
+			and <A HREF="#q_vertical_gradient_level">q_vertical_gradient_level</A>.&nbsp;
+			Boundary conditions can be set via <A HREF="#q_surface_initial_change">q_surface_initial_change</A>
+			and <A HREF="#surface_waterflux">surface_waterflux</A>.</P>
+			<P>If the condensation scheme is switched on (<A HREF="#cloud_physics">cloud_physics</A>
+			= .TRUE.), q becomes the total liquid water content (sum of
+			specific humidity and liquid water content).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="inflow_damping_height"></A><B>inflow_damping_height</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>from precursor run</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height below which the turbulence signal is used for turbulence
+			recycling (in m).<BR><BR>In case of a turbulent inflow (see
+			<A HREF="#turbulent_inflow">turbulent_inflow</A>), this parameter
+			defines the vertical thickness of the turbulent layer up to which
+			the turbulence extracted at the recycling plane (see
+			<A HREF="#recycling_width">recycling_width</A>) shall be imposed
+			to the inflow. Above this level the turbulence signal is linearly
+			damped to zero. The transition range within which the signal falls
+			to zero is given by the parameter <A HREF="#inflow_damping_width">inflow_damping_width</A>.<BR><BR>By
+			default, this height is set as the height of the convective
+			boundary layer as calculated from a precursor run. See <A HREF="chapter_3.9.html">chapter
+			3.9</A> about proper settings for getting this CBL height from a
+			precursor run. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="inflow_damping_width"></A><B>inflow_damping_width</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.1 * <A HREF="#inflow_damping_height">inflow_damping</A></I><A HREF="#inflow_damping_height"><BR><I>_height</I></A></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Transition range within which the turbulance signal is damped
+			to zero (in m).<BR><BR>See <A HREF="#inflow_damping_height">inflow_damping_height</A>
+			for explanation.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="inflow_disturbance_begin"></A><B>inflow_disturbance_<BR>begin</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>MIN(10,</I><BR><I>nx/2 or ny/2)</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Lower limit of the horizontal range for which random
+			perturbations are to be imposed on the horizontal velocity field
+			(gridpoints).<BR><BR>If non-cyclic lateral boundary conditions are
+			used (see <A HREF="#bc_lr">bc_lr</A> or <A HREF="#bc_ns">bc_ns</A>),
+			this parameter gives the gridpoint number (counted horizontally
+			from the inflow)&nbsp; from which on perturbations are imposed on
+			the horizontal velocity field. Perturbations must be switched on
+			with parameter <A HREF="chapter_4.2.html#create_disturbances">create_disturbances</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="inflow_disturbance_end"></A><B>inflow_disturbance_<BR>end</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>MIN(100,</I><BR><I>3/4*nx or</I><BR><I>3/4*ny)</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Upper limit of the horizontal range for which random
+			perturbations are to be imposed on the horizontal velocity field
+			(gridpoints).<BR><BR>If non-cyclic lateral boundary conditions are
+			used (see <A HREF="#bc_lr">bc_lr</A> or <A HREF="#bc_ns">bc_ns</A>),
+			this parameter gives the gridpoint number (counted horizontally
+			from the inflow)&nbsp; unto which perturbations are imposed on the
+			horizontal velocity field. Perturbations must be switched on with
+			parameter <A HREF="chapter_4.2.html#create_disturbances">create_disturbances</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="initializing_actions"></A><B>initializing_actions</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 100</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><BR>
+			</P>
+		</TD>
+		<TD WIDTH=1280>
+			<P STYLE="font-style: normal">Initialization actions to be carried
+			out.&nbsp; 
+			</P>
+			<P STYLE="font-style: normal">This parameter does not have a
+			default value and therefore must be assigned with each model run.
+			For restart runs <B>initializing_actions</B> = <I>'read_restart_data'</I>
+			must be set. For the initial run of a job chain the following
+			values are allowed:&nbsp; 
+			</P>
+			<P STYLE="font-style: normal"><I>'set_constant_profiles'</I> 
+			</P>
+			<UL>
+				<P>A horizontal wind profile consisting of linear sections (see
+				<A HREF="#ug_surface">ug_surface</A>, <A HREF="#ug_vertical_gradient">ug_vertical_gradient</A>,
+				<A HREF="#ug_vertical_gradient_level">ug_vertical_gradient_level</A>
+				and <A HREF="#vg_surface">vg_surface</A>, <A HREF="#vg_vertical_gradient">vg_vertical_gradient</A>,
+				<A HREF="#vg_vertical_gradient_level">vg_vertical_gradient_level</A>,
+				respectively) as well as a vertical temperature (humidity)
+				profile consisting of linear sections (see <A HREF="#pt_surface">pt_surface</A>,
+				<A HREF="#pt_vertical_gradient">pt_vertical_gradient</A>,
+				<A HREF="#q_surface">q_surface</A> and <A HREF="#q_vertical_gradient">q_vertical_gradient</A>)
+				are assumed as initial profiles. The subgrid-scale TKE is set to
+				0 but K<SUB>m</SUB> and K<SUB>h</SUB> are set to very small
+				values because otherwise no TKE would be generated.</P>
+			</UL>
+			<P><I>'set_1d-model_profiles' </I>
+			</P>
+			<UL>
+				<P>The arrays of the 3d-model are initialized with the
+				(stationary) solution of the 1d-model. These are the variables e,
+				kh, km, u, v and with Prandtl layer switched on rif, us, usws,
+				vsws. The temperature (humidity) profile consisting of linear
+				sections is set as for 'set_constant_profiles' and assumed as
+				constant in time within the 1d-model. For steering of the
+				1d-model a set of parameters with suffix &quot;_1d&quot; (e.g.
+				<A HREF="#end_time_1d">end_time_1d</A>, <A HREF="#damp_level_1d">damp_level_1d</A>)
+				is available.</P>
+			</UL>
+			<P><I>'by_user'</I></P>
+			<P STYLE="margin-left: 0.42in">The initialization of the arrays of
+			the 3d-model is under complete control of the user and has to be
+			done in routine <A HREF="chapter_3.5.1.html#user_init_3d_model">user_init_3d_model</A>
+			of the user-interface.</P>
+			<P><I>'initialize_vortex'</I> 
+			</P>
+			<P STYLE="margin-left: 0.42in">The initial velocity field of the
+			3d-model corresponds to a Rankine-vortex with vertical axis. This
+			setting may be used to test advection schemes. Free-slip boundary
+			conditions for u and v (see <A HREF="#bc_uv_b">bc_uv_b</A>,
+			<A HREF="#bc_uv_t">bc_uv_t</A>) are necessary. In order not to
+			distort the vortex, an initial horizontal wind profile constant
+			with height is necessary (to be set by <B>initializing_actions</B>
+			= <I>'set_constant_profiles'</I>) and some other conditions have
+			to be met (neutral stratification, diffusion must be switched off,
+			see <A HREF="#km_constant">km_constant</A>). The center of the
+			vortex is located at jc = (nx+1)/2. It extends from k = 0 to k =
+			nz+1. Its radius is 8 * <A HREF="#dx">dx</A> and the exponentially
+			decaying part ranges to 32 * <A HREF="#dx">dx</A> (see
+			init_rankine.f90). 
+			</P>
+			<P><I>'initialize_ptanom'</I> 
+			</P>
+			<UL>
+				<P>A 2d-Gauss-like shape disturbance (x,y) is added to the
+				initial temperature field with radius 10.0 * <A HREF="#dx">dx</A>
+				and center at jc = (nx+1)/2. This may be used for tests of scalar
+				advection schemes (see <A HREF="#scalar_advec">scalar_advec</A>).
+				Such tests require a horizontal wind profile constant with hight
+				and diffusion switched off (see <I>'initialize_vortex'</I>).
+				Additionally, the buoyancy term must be switched of in the
+				equation of motion&nbsp; for w (this requires the user to comment
+				out the call of <FONT FACE="monospace">buoyancy</FONT> in the
+				source code of <FONT FACE="monospace">prognostic_equations.f90</FONT>).</P>
+			</UL>
+			<P><I>'cyclic_fill'</I></P>
+			<P STYLE="margin-left: 0.42in"><SPAN STYLE="font-style: normal">Here,
+			3d-data from a precursor run are read by the initial (main) run.
+			The precursor run is allowed to have a smaller domain along x and
+			y compared with the main run. Also, different numbers of
+			processors can be used for these two runs. Limitations are that
+			the precursor run must use cyclic horizontal boundary conditions
+			and that the number of vertical grid points, <A HREF="#nz">nz</A>,
+			must be same for the precursor run and the main run. If the total
+			domain of the main run is larger than that of the precursor run,
+			the domain is filled by cyclic repetition&nbsp;of the (cyclic)
+			precursor data. This initialization method is recommended if a
+			turbulent inflow is used (see <A HREF="#turbulent_inflow">turbulent_inflow</A>).
+			3d-data must be made available to the run by activating an
+			appropriate file connection statement for local file BININ. See
+			<A HREF="chapter_3.9.html">chapter 3.9</A> for more details, where
+			usage of a turbulent inflow is explained. </SPAN>
+			</P>
+			<P STYLE="font-style: normal">Values may be combined, e.g.
+			<B>initializing_actions</B> = <I>'set_constant_profiles
+			initialize_vortex'</I>, but the values of <I>'set_constant_profiles'</I>,
+			<I>'set_1d-model_profiles'</I> , and <I>'by_user'</I> must not be
+			given at the same time.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="km_constant"></A><B>km_constant</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>variable<BR>(computed from TKE)</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Constant eddy diffusivities are used (laminar simulations).&nbsp;
+						</P>
+			<P>If this parameter is specified, both in the 1d and in the
+			3d-model constant values for the eddy diffusivities are used in
+			space and time with K<SUB>m</SUB> = <B>km_constant</B> and K<SUB>h</SUB>
+			= K<SUB>m</SUB> / <A HREF="chapter_4.2.html#prandtl_number">prandtl_number</A>.
+			The prognostic equation for the subgrid-scale TKE is switched off.
+			Constant eddy diffusivities are only allowed with the Prandtl
+			layer (<A HREF="#prandtl_layer">prandtl_layer</A>) switched off.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="km_damp_max"></A><B>km_damp_max</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.5*(dx or dy)</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Maximum diffusivity used for filtering the velocity field in
+			the vicinity of the outflow (in m<SUP>2</SUP>/s).<BR><BR>When
+			using non-cyclic lateral boundaries (see <A HREF="#bc_lr">bc_lr</A>
+			or <A HREF="#bc_ns">bc_ns</A>), a smoothing has to be applied to
+			the velocity field in the vicinity of the outflow in order to
+			suppress any reflections of outgoing disturbances. Smoothing is
+			done by increasing the eddy diffusivity along the horizontal
+			direction which is perpendicular to the outflow boundary. Only
+			velocity components parallel to the outflow boundary are filtered
+			(e.g. v and w, if the outflow is along x). Damping is applied from
+			the bottom to the top of the domain.<BR><BR>The horizontal range
+			of the smoothing is controlled by <A HREF="#outflow_damping_width">outflow_damping_width</A>
+			which defines the number of gridpoints (counted from the outflow
+			boundary) from where on the smoothing is applied. Starting from
+			that point, the eddy diffusivity is linearly increased (from zero
+			to its maximum value given by <B>km_damp_max</B>) until half of
+			the damping range width, from where it remains constant up to the
+			outflow boundary. If at a certain grid point the eddy diffusivity
+			calculated from the flow field is larger than as described above,
+			it is used instead.<BR><BR>The default value of <B>km_damp_max</B>
+			has been empirically proven to be sufficient.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="lad_surface"></A><B>lad_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Surface value of the leaf area density (in m<SUP>2</SUP>/m<SUP>3</SUP>).<BR><BR>This
+			parameter assigns the value of the leaf area density <B>lad</B> at
+			the surface (k=0)<B>.</B> Starting from this value, the leaf area
+			density profile is constructed with <A HREF="#lad_vertical_gradient">lad_vertical_gradient</A>
+			and <A HREF="#lad_vertical_gradient_level">lad_vertical_gradient_level
+			</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="lad_vertical_gradient"></A><B>lad_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Gradient(s) of the leaf area density (in&nbsp;m<SUP>2</SUP>/m<SUP>4</SUP>).</P>
+			<P>This leaf area density gradient holds starting from the height&nbsp;
+			level defined by <A HREF="#lad_vertical_gradient_level">lad_vertical_gradient_level</A>
+			(precisely: for all uv levels k where zu(k) &gt;
+			lad_vertical_gradient_level, lad(k) is set: lad(k) = lad(k-1) +
+			dzu(k) * <B>lad_vertical_gradient</B>) up to the level defined by
+			<A HREF="#pch_index">pch_index</A>. Above that level lad(k) will
+			automatically set to 0.0. A total of 10 different gradients for 11
+			height intervals (10 intervals if <A HREF="#lad_vertical_gradient_level">lad_vertical_gradient_level</A>(1)
+			= <I>0.0</I>) can be assigned. The leaf area density at the
+			surface is assigned via <A HREF="#lad_surface">lad_surface</A>.&nbsp;
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="lad_vertical_gradient_level"></A><B>lad_vertical_gradient_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the&nbsp;gradient of the leaf area
+			density defined by <A HREF="#lad_vertical_gradient_level">lad_vertical_gradient_level</A>
+			is effective (in m).<BR><BR>The height levels have to be assigned
+			in ascending order. The default values result in a leaf area
+			density that is constant with height uup to the top of the plant
+			canopy layer defined by <A HREF="#pch_index">pch_index</A>. For
+			the piecewise construction of temperature profiles see
+			<A HREF="#lad_vertical_gradient">lad_vertical_gradient</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="leaf_surface_concentration"></A><B>leaf_surface_concentration</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Concentration of a passive scalar at the surface of a leaf (in
+			K m/s).<BR><BR>This parameter is only of importance in cases in
+			that both, <A HREF="#plant_canopy">plant_canopy</A> and
+			<A HREF="#passive_scalar">passive_scalar</A>, are set <I>.T.</I>.
+			The value of the concentration of a passive scalar at the surface
+			of a leaf is required for the parametrisation of the sources and
+			sinks of scalar concentration due to the canopy.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="long_filter_factor"></A><B>long_filter_factor</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Filter factor for the so-called Long-filter.</P>
+			<P><BR>This filter very efficiently eliminates 2-delta-waves
+			sometimes cauesed by the upstream-spline scheme (see Mahrer and
+			Pielke, 1978: Mon. Wea. Rev., 106, 818-830). It works in all three
+			directions in space. A value of <B>long_filter_factor</B> = <I>0.01</I>
+			sufficiently removes the small-scale waves without affecting the
+			longer waves.</P>
+			<P>By default, the filter is switched off (= <I>0.0</I>). It is
+			exclusively applied to the tendencies calculated by the
+			upstream-spline scheme (see <A HREF="#momentum_advec">momentum_advec</A>
+			and <A HREF="#scalar_advec">scalar_advec</A>), not to the
+			prognostic variables themselves. At the bottom and top boundary of
+			the model domain the filter effect for vertical 2-delta-waves is
+			reduced. There, the amplitude of these waves is only reduced by
+			approx. 50%, otherwise by nearly 100%.&nbsp; <BR>Filter factors
+			with values &gt; <I>0.01</I> also reduce the amplitudes of waves
+			with wavelengths longer than 2-delta (see the paper by Mahrer and
+			Pielke, quoted above). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="loop_optimization"></A><B>loop_optimization</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C*16</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>see right</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Method used to optimize loops for solving the prognostic
+			equations .<BR><BR>By default, the optimization method depends on
+			the host on which PALM is running. On machines with vector-type
+			CPUs, single 3d-loops are used to calculate each tendency term of
+			each prognostic equation, while on all other machines, all
+			prognostic equations are solved within one big loop over the two
+			horizontal indices <FONT FACE="Courier New, Courier, monospace">i
+			</FONT>and <FONT FACE="Courier New, Courier, monospace">j </FONT>(giving
+			a good cache uitilization).<BR><BR>The default behaviour can be
+			changed by setting either <B>loop_optimization</B> = <I>'vector'</I>
+			or <B>loop_optimization</B> = <I>'cache'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="mixing_length_1d"></A><B>mixing_length_1d</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C*20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'as_in_3d_</I><BR><I>model'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Mixing length used in the 1d-model.<BR><BR>By default the
+			mixing length is calculated as in the 3d-model (i.e. it depends on
+			the grid spacing).<BR><BR>By setting <B>mixing_length_1d</B> =
+			<I>'blackadar'</I>, the so-called Blackadar mixing length is used
+			(l = kappa * z / ( 1 + kappa * z / lambda ) with the limiting
+			value lambda = 2.7E-4 * u_g / f).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="momentum_advec"></A><B>momentum_advec</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 10</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'pw-scheme'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Advection scheme to be used for the momentum equations.<BR><BR>The
+			user can choose between the following schemes:<BR>&nbsp;<BR><BR><I>'pw-scheme'</I></P>
+			<P STYLE="margin-left: 0.42in">The scheme of Piascek and Williams
+			(1970, J. Comp. Phys., 6, 392-405) with central differences in the
+			form C3 is used.<BR>If intermediate Euler-timesteps are carried
+			out in case of <A HREF="#timestep_scheme">timestep_scheme</A> =
+			<I>'leapfrog+euler'</I> the advection scheme is - for the
+			Euler-timestep - automatically switched to an upstream-scheme.</P>
+			<P><I>'ups-scheme'</I></P>
+			<P STYLE="margin-left: 0.42in">The upstream-spline scheme is used
+			(see Mahrer and Pielke, 1978: Mon. Wea. Rev., 106, 818-830). In
+			opposite to the Piascek-Williams scheme, this is characterized by
+			much better numerical features (less numerical diffusion, better
+			preservation of flow structures, e.g. vortices), but
+			computationally it is much more expensive. In addition, the use of
+			the Euler-timestep scheme is mandatory (<A HREF="#timestep_scheme">timestep_scheme</A>
+			= <I>'euler'</I>), i.e. the timestep accuracy is only of first
+			order. For this reason the advection of scalar variables (see
+			<A HREF="#scalar_advec">scalar_advec</A>) should then also be
+			carried out with the upstream-spline scheme, because otherwise the
+			scalar variables would be subject to large numerical diffusion due
+			to the upstream scheme.&nbsp; 
+			</P>
+			<P STYLE="margin-left: 0.42in">Since the cubic splines used tend
+			to overshoot under certain circumstances, this effect must be
+			adjusted by suitable filtering and smoothing (see
+			<A HREF="#cut_spline_overshoot">cut_spline_overshoot</A>,
+			<A HREF="#long_filter_factor">long_filter_factor</A>,
+			<A HREF="#ups_limit_pt">ups_limit_pt</A>, <A HREF="#ups_limit_u">ups_limit_u</A>,
+			<A HREF="#ups_limit_v">ups_limit_v</A>, <A HREF="#ups_limit_w">ups_limit_w</A>).
+			This is always neccessary for runs with stable stratification,
+			even if this stratification appears only in parts of the model
+			domain.</P>
+			<P STYLE="margin-left: 0.42in">With stable stratification the
+			upstream-spline scheme also produces gravity waves with large
+			amplitude, which must be suitably damped (see
+			<A HREF="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</A>).<BR><BR><B>Important:
+			</B>The&nbsp; upstream-spline scheme is not implemented for
+			humidity and passive scalars (see&nbsp;<A HREF="#humidity">humidity</A>
+			and <A HREF="#passive_scalar">passive_scalar</A>) and requires the
+			use of a 2d-domain-decomposition. The last conditions severely
+			restricts code optimization on several machines leading to very
+			long execution times! The scheme is also not allowed for
+			non-cyclic lateral boundary conditions (see <A HREF="#bc_lr">bc_lr</A>
+			and <A HREF="#bc_ns">bc_ns</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="netcdf_precision"></A><B>netcdf_precision</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C*20<BR>(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>single preci-</I><BR><I>sion for all</I><BR><I>output
+			quan-</I><BR><I>tities</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Defines the accuracy of the NetCDF output.<BR><BR>By default,
+			all NetCDF output data (see <A HREF="chapter_4.2.html#data_output_format">data_output_format</A>)
+			have single precision&nbsp; (4 byte) accuracy. Double precision (8
+			byte) can be choosen alternatively.<BR>Accuracy for the different
+			output data (cross sections, 3d-volume data, spectra, etc.) can be
+			set independently.<BR><I>'&lt;out&gt;_NF90_REAL4'</I> (single
+			precision) or <I>'&lt;out&gt;_NF90_REAL8'</I> (double precision)
+			are the two principally allowed values for <B>netcdf_precision</B>,
+			where the string <I>'&lt;out&gt;' </I>can be chosen out of the
+			following list:</P>
+			<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+				<TR>
+					<TD>
+						<P><I>'xy'</I></P>
+					</TD>
+					<TD>
+						<P>horizontal cross section</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'xz'</I></P>
+					</TD>
+					<TD>
+						<P>vertical (xz) cross section</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'yz'</I></P>
+					</TD>
+					<TD>
+						<P>vertical (yz) cross section</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'2d'</I></P>
+					</TD>
+					<TD>
+						<P>all cross sections</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'3d'</I></P>
+					</TD>
+					<TD>
+						<P>volume data</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'pr'</I></P>
+					</TD>
+					<TD>
+						<P>vertical profiles</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'ts'</I></P>
+					</TD>
+					<TD>
+						<P>time series, particle time series</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'sp'</I></P>
+					</TD>
+					<TD>
+						<P>spectra</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'prt'</I></P>
+					</TD>
+					<TD>
+						<P>particles</P>
+					</TD>
+				</TR>
+				<TR>
+					<TD>
+						<P><I>'all'</I></P>
+					</TD>
+					<TD>
+						<P>all output quantities</P>
+					</TD>
+				</TR>
+			</TABLE>
+			<P><BR><B>Example:</B><BR>If all cross section data and the
+			particle data shall be output in double precision and all other
+			quantities in single precision, then <B>netcdf_precision</B> =
+			<I>'2d_NF90_REAL8'</I>, <I>'prt_NF90_REAL8'</I> has to be
+			assigned.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="nsor_ini"></A><B>nsor_ini</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>100</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Initial number of iterations with the SOR algorithm.&nbsp; 
+			</P>
+			<P>This parameter is only effective if the SOR algorithm was
+			selected as the pressure solver scheme (<A HREF="chapter_4.2.html#psolver">psolver</A>
+			= <I>'sor'</I>) and specifies the number of initial iterations of
+			the SOR scheme (at t = 0). The number of subsequent iterations at
+			the following timesteps is determined with the parameter <A HREF="#nsor">nsor</A>.
+			Usually <B>nsor</B> &lt; <B>nsor_ini</B>, since in each case
+			subsequent calls to <A HREF="chapter_4.2.html#psolver">psolver</A>
+			use the solution of the previous call as initial value. Suitable
+			test runs should determine whether sufficient convergence of the
+			solution is obtained with the default value and if necessary the
+			value of <B>nsor_ini</B> should be changed.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="nx"></A><B>nx</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><BR><BR>
+			</P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Number of grid points in x-direction.&nbsp; 
+			</P>
+			<P>A value for this parameter must be assigned. Since the lower
+			array bound in PALM starts with i = 0, the actual number of grid
+			points is equal to <B>nx+1</B>. In case of cyclic boundary
+			conditions along x, the domain size is (<B>nx+1</B>)* <A HREF="#dx">dx</A>.</P>
+			<P>For parallel runs, in case of <A HREF="#grid_matching">grid_matching</A>
+			= <I>'strict'</I>, <B>nx+1</B> must be an integral multiple of the
+			processor numbers (see <A HREF="#npex">npex</A> and <A HREF="#npey">npey</A>)
+			along x- as well as along y-direction (due to data transposition
+			restrictions).</P>
+			<P>For <A HREF="chapter_3.8.html">coupled runs</A> this parameter
+			must be&nbsp;equal in both parameter files <A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN</FONT></A>
+			and&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ny"></A><B>ny</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><BR><BR>
+			</P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Number of grid points in y-direction.&nbsp; 
+			</P>
+			<P>A value for this parameter must be assigned. Since the lower
+			array bound in PALM starts with j = 0, the actual number of grid
+			points is equal to <B>ny+1</B>. In case of cyclic boundary
+			conditions along y, the domain size is (<B>ny+1</B>) * <A HREF="#dy">dy</A>.</P>
+			<P>For parallel runs, in case of <A HREF="#grid_matching">grid_matching</A>
+			= <I>'strict'</I>, <B>ny+1</B> must be an integral multiple of the
+			processor numbers (see <A HREF="#npex">npex</A> and <A HREF="#npey">npey</A>)&nbsp;
+			along y- as well as along x-direction (due to data transposition
+			restrictions).</P>
+			<P>For <A HREF="chapter_3.8.html">coupled runs</A> this parameter
+			must be&nbsp;equal in both parameter files <A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN</FONT></A>
+			and&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="nz"></A><B>nz</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><BR><BR>
+			</P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Number of grid points in z-direction.&nbsp; 
+			</P>
+			<P>A value for this parameter must be assigned. Since the lower
+			array bound in PALM starts with k = 0 and since one additional
+			grid point is added at the top boundary (k = <B>nz+1</B>), the
+			actual number of grid points is <B>nz+2</B>. However, the
+			prognostic equations are only solved up to <B>nz</B> (u, v) or up
+			to <B>nz-1</B> (w, scalar quantities). The top boundary for u and
+			v is at k = <B>nz+1</B> (u, v) while at k = <B>nz</B> for all
+			other quantities.&nbsp; 
+			</P>
+			<P>For parallel runs,&nbsp; in case of <A HREF="#grid_matching">grid_matching</A>
+			= <I>'strict'</I>, <B>nz</B> must be an integral multiple of the
+			number of processors in x-direction (due to data transposition
+			restrictions).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ocean"></A><B>ocean</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on&nbsp;ocean runs.<BR><BR>By default PALM
+			is configured to simulate&nbsp;atmospheric flows. However,
+			starting from version 3.3, <B>ocean</B> = <I>.T.</I>
+			allows&nbsp;simulation of ocean turbulent flows. Setting this
+			switch has several effects:</P>
+			<UL>
+				<LI><P STYLE="margin-bottom: 0in">An additional prognostic
+				equation for salinity is solved. 
+				</P>
+				<LI><P STYLE="margin-bottom: 0in">Potential temperature in
+				buoyancy and stability-related terms is replaced by potential
+				density. 
+				</P>
+				<LI><P STYLE="margin-bottom: 0in">Potential density is calculated
+				from the equation of state for seawater after each timestep,
+				using the algorithm proposed by Jackett et al. (2006, J. Atmos.
+				Oceanic Technol., <B>23</B>, 1709-1728).<BR>So far, only the
+				initial hydrostatic pressure is entered into this equation. 
+				</P>
+				<LI><P STYLE="margin-bottom: 0in">z=0 (sea surface) is assumed at
+				the model top (vertical grid index <FONT FACE="Courier New, Courier, monospace">k=nzt</FONT>
+				on the w-grid), with negative values of z indicating the depth. 
+				</P>
+				<LI><P STYLE="margin-bottom: 0in">Initial profiles are
+				constructed (e.g. from <A HREF="#pt_vertical_gradient">pt_vertical_gradient</A>
+				/ <A HREF="#pt_vertical_gradient_level">pt_vertical_gradient_level</A>)
+				starting from the sea surface, using surface values&nbsp;given by
+				<A HREF="#pt_surface">pt_surface</A>, <A HREF="#sa_surface">sa_surface</A>,
+				<A HREF="#ug_surface">ug_surface</A>, and <A HREF="#vg_surface">vg_surface</A>.
+								</P>
+				<LI><P STYLE="margin-bottom: 0in">Zero salinity flux is used as
+				default boundary condition at the bottom of the sea. 
+				</P>
+				<LI><P>If switched on, random perturbations are by default
+				imposed to the upper model domain from zu(nzt*2/3) to zu(nzt-3). 
+				</P>
+			</UL>
+			<P><BR>Relevant parameters to be exclusively used for steering
+			ocean runs are <A HREF="#bc_sa_t">bc_sa_t</A>,
+			<A HREF="#bottom_salinityflux">bottom_salinityflux</A>,
+			<A HREF="#sa_surface">sa_surface</A>, <A HREF="#sa_vertical_gradient">sa_vertical_gradient</A>,
+			<A HREF="#sa_vertical_gradient_level">sa_vertical_gradient_level</A>,
+			and <A HREF="#top_salinityflux">top_salinityflux</A>.<BR><BR>Section
+			<A HREF="chapter_4.2.2.html">4.4.2</A> gives an example for
+			appropriate settings of these and other parameters neccessary for
+			ocean runs.<BR><BR><B>ocean</B> = <I>.T.</I> does not allow
+			settings of <A HREF="#timestep_scheme">timestep_scheme</A> =
+			<I>'leapfrog'</I> or <I>'leapfrog+euler'</I> as well as
+			<A HREF="#scalar_advec">scalar_advec</A> = <I>'ups-scheme'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="omega"></A><B>omega</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>7.29212E-5</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Angular velocity of the rotating system (in rad s<SUP>-1</SUP>).&nbsp;
+						</P>
+			<P>The angular velocity of the earth is set by default. The values
+			of the Coriolis parameters are calculated as:&nbsp; 
+			</P>
+			<UL>
+				<P>f = 2.0 * <B>omega</B> * sin(<A HREF="#phi">phi</A>)&nbsp; <BR>f*
+				= 2.0 * <B>omega</B> * cos(<A HREF="#phi">phi</A>)</P>
+			</UL>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="outflow_damping_width"></A><B>outflow_damping_width</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>MIN(20, nx/2</I> or <I>ny/2)</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Width of the damping range in the vicinity of the outflow
+			(gridpoints).<BR><BR>When using non-cyclic lateral boundaries (see
+			<A HREF="#bc_lr">bc_lr</A> or <A HREF="#bc_ns">bc_ns</A>), a
+			smoothing has to be applied to the velocity field in the vicinity
+			of the outflow in order to suppress any reflections of outgoing
+			disturbances. This parameter controlls the horizontal range to
+			which the smoothing is applied. The range is given in gridpoints
+			counted from the respective outflow boundary. For further details
+			about the smoothing see parameter <A HREF="#km_damp_max">km_damp_max</A>,
+			which defines the magnitude of the damping.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="overshoot_limit_e"></A><B>overshoot_limit_e</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Allowed limit for the overshooting of subgrid-scale TKE in case
+			that the upstream-spline scheme is switched on (in m<SUP>2</SUP>/s<SUP>2</SUP>).&nbsp;
+						</P>
+			<P>By deafult, if cut-off of overshoots is switched on for the
+			upstream-spline scheme (see <A HREF="#cut_spline_overshoot">cut_spline_overshoot</A>),
+			no overshoots are permitted at all. If <B>overshoot_limit_e</B> is
+			given a non-zero value, overshoots with the respective amplitude
+			(both upward and downward) are allowed.&nbsp; 
+			</P>
+			<P>Only positive values are allowed for <B>overshoot_limit_e</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="overshoot_limit_pt"></A><B>overshoot_limit_pt</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Allowed limit for the overshooting of potential temperature in
+			case that the upstream-spline scheme is switched on (in K).&nbsp; 
+			</P>
+			<P>For further information see <A HREF="#overshoot_limit_e">overshoot_limit_e</A>.&nbsp;
+						</P>
+			<P>Only positive values are allowed for <B>overshoot_limit_pt</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="overshoot_limit_u"></A><B>overshoot_limit_u</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Allowed limit for the overshooting of the u-component of
+			velocity in case that the upstream-spline scheme is switched on
+			(in m/s). 
+			</P>
+			<P>For further information see <A HREF="#overshoot_limit_e">overshoot_limit_e</A>.&nbsp;
+						</P>
+			<P>Only positive values are allowed for <B>overshoot_limit_u</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="overshoot_limit_v"></A><B>overshoot_limit_v</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Allowed limit for the overshooting of the v-component of
+			velocity in case that the upstream-spline scheme is switched on
+			(in m/s).&nbsp; 
+			</P>
+			<P>For further information see <A HREF="#overshoot_limit_e">overshoot_limit_e</A>.&nbsp;
+						</P>
+			<P>Only positive values are allowed for <B>overshoot_limit_v</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="overshoot_limit_w"></A><B>overshoot_limit_w</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Allowed limit for the overshooting of the w-component of
+			velocity in case that the upstream-spline scheme is switched on
+			(in m/s).&nbsp; 
+			</P>
+			<P>For further information see <A HREF="#overshoot_limit_e">overshoot_limit_e</A>.&nbsp;
+						</P>
+			<P>Only positive values are permitted for <B>overshoot_limit_w</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="passive_scalar"></A><B>passive_scalar</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on the prognostic equation for a passive
+			scalar. 
+			</P>
+			<P>The initial vertical profile of s can be set via parameters
+			<A HREF="#s_surface">s_surface</A>, <A HREF="#s_vertical_gradient">s_vertical_gradient</A>
+			and&nbsp; <A HREF="#s_vertical_gradient_level">s_vertical_gradient_level</A>.
+			Boundary conditions can be set via <A HREF="#s_surface_initial_change">s_surface_initial_change</A>
+			and <A HREF="#surface_scalarflux">surface_scalarflux</A>.&nbsp; 
+			</P>
+			<P><B>Note:</B> <BR>With <B>passive_scalar</B> switched on, the
+			simultaneous use of humidity (see&nbsp;<A HREF="#humidity">humidity</A>)
+			is impossible.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pch_index"></A><B>pch_index</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Grid point index (scalar) of the upper boundary of the plant
+			canopy layer.<BR><BR>Above <B>pch_index</B> the arrays of leaf
+			area density and drag_coeffient are automatically set to zero in
+			case of <A HREF="#plant_canopy">plant_canopy</A> = .T.. Up to
+			<B>pch_index</B> a leaf area density profile can be prescribed by
+			using the parameters <A HREF="#lad_surface">lad_surface</A>,
+			<A HREF="#lad_vertical_gradient">lad_vertical_gradient</A> and
+			<A HREF="#lad_vertical_gradient_level">lad_vertical_gradient_level</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="phi"></A><B>phi</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>55.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Geographical latitude (in degrees).&nbsp; 
+			</P>
+			<P>The value of this parameter determines the value of the
+			Coriolis parameters f and f*, provided that the angular velocity
+			(see <A HREF="#omega">omega</A>) is non-zero.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="plant_canopy"></A><B>plant_canopy</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Switch for the plant_canopy_model.<BR><BR>If <B>plant_canopy</B>
+			is set <I>.T.</I>, the plant canopy model of Watanabe (2004, BLM
+			112, 307-341) is used. <BR>The impact of a plant canopy on a
+			turbulent flow is considered by an additional drag term in the
+			momentum equations and an additional sink term in the prognostic
+			equation for the subgrid-scale TKE. These additional terms are
+			dependent on the leaf drag coefficient (see <A HREF="#drag_coefficient">drag_coefficient</A>)
+			and the leaf area density (see <A HREF="#lad_surface">lad_surface</A>,
+			<A HREF="#lad_vertical_gradient">lad_vertical_gradient</A>,
+			<A HREF="#lad_vertical_gradient_level">lad_vertical_gradient_level</A>).
+			The top boundary of the plant canopy is determined by the
+			parameter <A HREF="#pch_index">pch_index</A>. For all heights
+			equal to or larger than zw(k=<B>pch_index</B>) the leaf area
+			density is 0 (i.e. there is no canopy at these heights!). <BR>By
+			default, a horizontally homogeneous plant canopy is prescribed,
+			if&nbsp; <B>plant_canopy</B> is set <I>.T.</I>. However, the user
+			can define other types of plant canopies (see <A HREF="#canopy_mode">canopy_mode</A>).<BR><BR>If
+			<B>plant_canopy</B> and&nbsp; <B>passive_scalar</B> are set <I>.T.</I>,
+			the canopy acts as an additional source or sink, respectively, of
+			scalar concentration. The source/sink strength is dependent on the
+			scalar concentration at the leaf surface, which is generally
+			constant with time in PALM and which can be specified by
+			specifying the parameter <A HREF="#leaf_surface_concentration">leaf_surface_concentration</A>.
+			<BR><BR>Additional heating of the air by the plant canopy is taken
+			into account, when the default value of the parameter <A HREF="#cthf">cthf</A>
+			is altered in the parameter file. In that case the value of
+			<A HREF="#surface_heatflux">surface_heatflux</A> specified in the
+			parameter file is not used in the model. Instead the near-surface
+			heat flux is derived from an expontial function that is dependent
+			on the cumulative leaf area index. <BR><BR><B>plant_canopy</B> =
+			<I>.T. </I>is only allowed together with a non-zero
+			<A HREF="#drag_coefficient">drag_coefficient</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="prandtl_layer"></A><B>prandtl_layer</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on a Prandtl layer.&nbsp; 
+			</P>
+			<P>By default, a Prandtl layer is switched on at the bottom
+			boundary between z = 0 and z = 0.5 * <A HREF="#dz">dz</A> (the
+			first computational grid point above ground for u, v and the
+			scalar quantities). In this case, at the bottom boundary,
+			free-slip conditions for u and v (see <A HREF="#bc_uv_b">bc_uv_b</A>)
+			are not allowed. Likewise, laminar simulations with constant eddy
+			diffusivities (<A HREF="#km_constant">km_constant</A>) are
+			forbidden.&nbsp; 
+			</P>
+			<P>With Prandtl-layer switched off, the TKE boundary condition
+			<A HREF="#bc_e_b">bc_e_b</A> = '<I>(u*)**2+neumann'</I> must not
+			be used and is automatically changed to <I>'neumann'</I> if
+			necessary.&nbsp; Also, the pressure boundary condition <A HREF="#bc_p_b">bc_p_b</A>
+			= <I>'neumann+inhomo'</I>&nbsp; is not allowed. 
+			</P>
+			<P>The roughness length is declared via the parameter
+			<A HREF="#roughness_length">roughness_length</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="precipitation"></A><B>precipitation</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on the precipitation scheme.</P>
+			<P>For precipitation processes PALM uses a simplified Kessler
+			scheme. This scheme only considers the so-called autoconversion,
+			that means the generation of rain water by coagulation of cloud
+			drops among themselves. Precipitation begins and is immediately
+			removed from the flow as soon as the liquid water content exceeds
+			the critical value of 0.5 g/kg.</P>
+			<P>The precipitation rate and amount can be output by assigning
+			the runtime parameter <A HREF="chapter_4.2.html#data_output">data_output</A>
+			= <I>'prr*'</I> or <I>'pra*'</I>, respectively. The time interval
+			on which the precipitation amount is defined can be controlled via
+			runtime parameter <A HREF="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_interval</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pt_reference"></A><B>pt_reference</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>use horizontal average as refrence</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Reference temperature to be used in all buoyancy terms (in
+			K).<BR><BR>By default, the instantaneous horizontal average over
+			the total model domain is used.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs (see <A HREF="#ocean">ocean</A>), always a
+			reference temperature is used in the buoyancy terms with a default
+			value of <B>pt_reference</B> = <A HREF="#pt_surface">pt_surface</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pt_surface"></A><B>pt_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>300.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Surface potential temperature (in K).&nbsp; 
+			</P>
+			<P>This parameter assigns the value of the potential temperature
+			<B>pt</B> at the surface (k=0)<B>.</B> Starting from this value,
+			the initial vertical temperature profile is constructed with
+			<A HREF="#pt_vertical_gradient">pt_vertical_gradient</A> and
+			<A HREF="#pt_vertical_gradient_level">pt_vertical_gradient_level </A>.
+			This profile is also used for the 1d-model as a stationary
+			profile.</P>
+			<P><B>Attention:</B><BR>In case of ocean runs (see <A HREF="#ocean">ocean</A>),
+			this parameter gives the temperature value at the sea surface,
+			which is at k=nzt. The profile is then constructed from the
+			surface down to the bottom of the model.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pt_surface_initial_change"></A><B>pt_surface_initial</B>
+			<BR><B>_change</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Change in surface temperature to be made at the beginning of
+			the 3d run (in K).&nbsp; 
+			</P>
+			<P>If <B>pt_surface_initial_change</B> is set to a non-zero value,
+			the near surface sensible heat flux is not allowed to be given
+			simultaneously (see <A HREF="#surface_heatflux">surface_heatflux</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pt_vertical_gradient"></A><B>pt_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Temperature gradient(s) of the initial temperature profile (in
+			K / 100 m).&nbsp; 
+			</P>
+			<P>This temperature gradient holds starting from the height&nbsp;
+			level defined by <A HREF="#pt_vertical_gradient_level">pt_vertical_gradient_level</A>
+			(precisely: for all uv levels k where zu(k) &gt;
+			pt_vertical_gradient_level, pt_init(k) is set: pt_init(k) =
+			pt_init(k-1) + dzu(k) * <B>pt_vertical_gradient</B>) up to the top
+			boundary or up to the next height level defined by
+			<A HREF="#pt_vertical_gradient_level">pt_vertical_gradient_level</A>.
+			A total of 10 different gradients for 11 height intervals (10
+			intervals if <A HREF="#pt_vertical_gradient_level">pt_vertical_gradient_level</A>(1)
+			= <I>0.0</I>) can be assigned. The surface temperature is assigned
+			via <A HREF="#pt_surface">pt_surface</A>.&nbsp; 
+			</P>
+			<P>Example:&nbsp; 
+			</P>
+			<UL>
+				<P><B>pt_vertical_gradient</B> = <I>1.0</I>, <I>0.5</I>,&nbsp;
+				<BR><B>pt_vertical_gradient_level</B> = <I>500.0</I>, <I>1000.0</I>,</P>
+			</UL>
+			<P>That defines the temperature profile to be neutrally stratified
+			up to z = 500.0 m with a temperature given by <A HREF="#pt_surface">pt_surface</A>.
+			For 500.0 m &lt; z &lt;= 1000.0 m the temperature gradient is 1.0
+			K / 100 m and for z &gt; 1000.0 m up to the top boundary it is 0.5
+			K / 100 m (it is assumed that the assigned height levels
+			correspond with uv levels).</P>
+			<P><B>Attention:</B><BR>In case of ocean runs (see <A HREF="#ocean">ocean</A>),
+			the profile is constructed like described above, but starting from
+			the sea surface (k=nzt) down to the bottom boundary of the model.
+			Height levels have then to be given as negative values, e.g.
+			<B>pt_vertical_gradient_level</B> = <I>-500.0</I>, <I>-1000.0</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="pt_vertical_gradient_level"></A><B>pt_vertical_gradient</B>
+			<BR><B>_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 *</I>&nbsp; <I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the temperature gradient defined by
+			<A HREF="#pt_vertical_gradient">pt_vertical_gradient</A> is
+			effective (in m).&nbsp; 
+			</P>
+			<P>The height levels have to be assigned in ascending order. The
+			default values result in a neutral stratification regardless of
+			the values of <A HREF="#pt_vertical_gradient">pt_vertical_gradient</A>
+			(unless the top boundary of the model is higher than 100000.0 m).
+			For the piecewise construction of temperature profiles see
+			<A HREF="#pt_vertical_gradient">pt_vertical_gradient</A>.</P>
+			<P><B>Attention:</B><BR>In case of ocean runs&nbsp;(see <A HREF="#ocean">ocean</A>),
+			the (negative) height levels have to be assigned in descending
+			order. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="q_surface"></A><B>q_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Surface specific humidity / total water content (kg/kg).&nbsp; 
+			</P>
+			<P>This parameter assigns the value of the specific humidity q at
+			the surface (k=0).&nbsp; Starting from this value, the initial
+			humidity profile is constructed with&nbsp; <A HREF="#q_vertical_gradient">q_vertical_gradient</A>
+			and <A HREF="#q_vertical_gradient_level">q_vertical_gradient_level</A>.
+			This profile is also used for the 1d-model as a stationary
+			profile.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="q_surface_initial_change"></A><B>q_surface_initial</B>
+			<BR><B>_change</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Change in surface specific humidity / total water content to be
+			made at the beginning of the 3d run (kg/kg).&nbsp; 
+			</P>
+			<P>If <B>q_surface_initial_change</B> is set to a non-zero value
+			the near surface latent heat flux (water flux) is not allowed to
+			be given simultaneously (see <A HREF="#surface_waterflux">surface_waterflux</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="q_vertical_gradient"></A><B>q_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Humidity gradient(s) of the initial humidity profile (in 1/100
+			m).&nbsp; 
+			</P>
+			<P>This humidity gradient holds starting from the height level&nbsp;
+			defined by <A HREF="#q_vertical_gradient_level">q_vertical_gradient_level</A>
+			(precisely: for all uv levels k, where zu(k) &gt;
+			q_vertical_gradient_level, q_init(k) is set: q_init(k) =
+			q_init(k-1) + dzu(k) * <B>q_vertical_gradient</B>) up to the top
+			boundary or up to the next height level defined by
+			<A HREF="#q_vertical_gradient_level">q_vertical_gradient_level</A>.
+			A total of 10 different gradients for 11 height intervals (10
+			intervals if <A HREF="#q_vertical_gradient_level">q_vertical_gradient_level</A>(1)
+			= <I>0.0</I>) can be asigned. The surface humidity is assigned via
+			<A HREF="#q_surface">q_surface</A>. 
+			</P>
+			<P>Example:&nbsp; 
+			</P>
+			<UL>
+				<P><B>q_vertical_gradient</B> = <I>0.001</I>, <I>0.0005</I>,&nbsp;
+				<BR><B>q_vertical_gradient_level</B> = <I>500.0</I>, <I>1000.0</I>,</P>
+			</UL>
+			<P>That defines the humidity to be constant with height up to z =
+			500.0 m with a value given by <A HREF="#q_surface">q_surface</A>.
+			For 500.0 m &lt; z &lt;= 1000.0 m the humidity gradient is 0.001 /
+			100 m and for z &gt; 1000.0 m up to the top boundary it is 0.0005
+			/ 100 m (it is assumed that the assigned height levels correspond
+			with uv levels). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="q_vertical_gradient_level"></A><B>q_vertical_gradient</B>
+			<BR><B>_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 *</I>&nbsp; <I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the humidity gradient defined by
+			<A HREF="#q_vertical_gradient">q_vertical_gradient</A> is
+			effective (in m).&nbsp; 
+			</P>
+			<P>The height levels are to be assigned in ascending order. The
+			default values result in a humidity constant with height
+			regardless of the values of <A HREF="#q_vertical_gradient">q_vertical_gradient</A>
+			(unless the top boundary of the model is higher than 100000.0 m).
+			For the piecewise construction of humidity profiles see
+			<A HREF="#q_vertical_gradient">q_vertical_gradient</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="radiation"></A><B>radiation</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to switch on longwave radiation cooling at
+			cloud-tops.&nbsp; 
+			</P>
+			<P>Long-wave radiation processes are parameterized by the
+			effective emissivity, which considers only the absorption and
+			emission of long-wave radiation at cloud droplets. The radiation
+			scheme can be used only with <A HREF="#cloud_physics">cloud_physics</A>
+			= .TRUE. .</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="random_generator"></A><B>random_generator</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'numerical</I><BR><I>recipes'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Random number generator to be used for creating uniformly
+			distributed random numbers. 
+			</P>
+			<P>It is used if random perturbations are to be imposed on the
+			velocity field or on the surface heat flux field (see
+			<A HREF="chapter_4.2.html#create_disturbances">create_disturbances</A>
+			and <A HREF="chapter_4.2.html#random_heatflux">random_heatflux</A>).
+			By default, the &quot;Numerical Recipes&quot; random number
+			generator is used. This one provides exactly the same order of
+			random numbers on all different machines and should be used in
+			particular for comparison runs.<BR><BR>Besides, a system-specific
+			generator is available ( <B>random_generator</B> =
+			<I>'system-specific')</I> which should particularly be used for
+			runs on vector parallel computers (NEC), because the default
+			generator cannot be vectorized and therefore significantly drops
+			down the code performance on these machines.</P>
+			<P><B>Note:</B><BR>Results from two otherwise identical model runs
+			will not be comparable one-to-one if they used different random
+			number generators.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="random_heatflux"></A><B>random_heatflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to impose random perturbations on the internal
+			two-dimensional near surface heat flux field <I>shf</I>. 
+			</P>
+			<P>If a near surface heat flux is used as bottom boundary
+			condition (see <A HREF="#surface_heatflux">surface_heatflux</A>),
+			it is by default assumed to be horizontally homogeneous. Random
+			perturbations can be imposed on the internal two-dimensional&nbsp;heat
+			flux field <I>shf</I> by assigning <B>random_heatflux</B> = <I>.T.</I>.
+			The disturbed heat flux field is calculated by multiplying the
+			values at each mesh point with a normally distributed random
+			number with a mean value and standard deviation of 1. This is
+			repeated after every timestep.<BR><BR>In case of a non-flat
+			<A HREF="#topography">topography</A>,&nbsp;assigning
+			<B>random_heatflux</B> = <I>.T.</I> imposes random perturbations
+			on the combined&nbsp;heat flux field <I>shf</I> composed of
+			<A HREF="#surface_heatflux">surface_heatflux</A> at the bottom
+			surface and <A HREF="#wall_heatflux">wall_heatflux(0)</A> at the
+			topography top face.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="recycling_width"></A><B>recycling_width</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.1 * <A HREF="#nx">nx</A> * <A HREF="#dx">dx</A></I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Distance of the recycling plane from the inflow boundary (in
+			m).<BR><BR>This parameter sets the horizontal extension (along the
+			direction of the main flow) of the so-called recycling domain
+			which is used to generate a turbulent inflow (see
+			<A HREF="#turbulent_inflow">turbulent_inflow</A>). <B>recycling_width</B>
+			must be larger than the grid spacing (dx) and smaller than the
+			length of the total domain (nx * dx).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="rif_max"></A><B>rif_max</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Upper limit of the flux-Richardson number.&nbsp; 
+			</P>
+			<P>With the Prandtl layer switched on (see <A HREF="#prandtl_layer">prandtl_layer</A>),
+			flux-Richardson numbers (rif) are calculated for z=z<SUB>p</SUB>
+			(k=1) in the 3d-model (in the 1d model for all heights). Their
+			values in particular determine the values of the friction velocity
+			(1d- and 3d-model) and the values of the eddy diffusivity
+			(1d-model). With small wind velocities at the Prandtl layer top or
+			small vertical wind shears in the 1d-model, rif can take up
+			unrealistic large values. They are limited by an upper (<B>rif_max</B>)
+			and lower limit (see <A HREF="#rif_min">rif_min</A>) for the
+			flux-Richardson number. The condition <B>rif_max</B> &gt; <B>rif_min</B>
+			must be met.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="rif_min"></A><B>rif_min</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>- 5.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Lower limit of the flux-Richardson number.&nbsp; 
+			</P>
+			<P>For further explanations see <A HREF="#rif_max">rif_max</A>.
+			The condition <B>rif_max</B> &gt; <B>rif_min </B>must be met.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="roughness_length"></A><B>roughness_length</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.1</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Roughness length (in m).&nbsp; 
+			</P>
+			<P>This parameter is effective only in case that a Prandtl layer
+			is switched on (see <A HREF="#prandtl_layer">prandtl_layer</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="sa_surface"></A><B>sa_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>35.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Surface salinity (in psu).&nbsp;</P>
+			<P>This parameter only comes into effect for ocean runs (see
+			parameter <A HREF="#ocean">ocean</A>). 
+			</P>
+			<P>This parameter assigns the value of the salinity <B>sa</B> at
+			the sea surface (k=nzt)<B>.</B> Starting from this value, the
+			initial vertical salinity profile is constructed from the surface
+			down to the bottom of the model (k=0) by
+			using&nbsp;<A HREF="#sa_vertical_gradient">sa_vertical_gradient</A>
+			and&nbsp;<A HREF="#sa_vertical_gradient_level">sa_vertical_gradient_level
+			</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="sa_vertical_gradient"></A><B>sa_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Salinity gradient(s) of the initial salinity profile (in psu /
+			100 m).&nbsp; 
+			</P>
+			<P>This parameter only comes into effect for ocean runs (see
+			parameter <A HREF="#ocean">ocean</A>).</P>
+			<P>This salinity gradient holds starting from the height&nbsp;
+			level defined by <A HREF="#sa_vertical_gradient_level">sa_vertical_gradient_level</A>
+			(precisely: for all uv levels k where zu(k) &lt;
+			sa_vertical_gradient_level, sa_init(k) is set: sa_init(k) =
+			sa_init(k+1) - dzu(k+1) * <B>sa_vertical_gradient</B>) down to the
+			bottom boundary or down to the next height level defined by
+			<A HREF="#sa_vertical_gradient_level">sa_vertical_gradient_level</A>.
+			A total of 10 different gradients for 11 height intervals (10
+			intervals if <A HREF="#sa_vertical_gradient_level">sa_vertical_gradient_level</A>(1)
+			= <I>0.0</I>) can be assigned. The surface salinity at k=nzt is
+			assigned via <A HREF="#sa_surface">sa_surface</A>.&nbsp; 
+			</P>
+			<P>Example:&nbsp; 
+			</P>
+			<UL>
+				<P><B>sa_vertical_gradient</B> = <I>1.0</I>, <I>0.5</I>,&nbsp;
+				<BR><B>sa_vertical_gradient_level</B> = <I>-500.0</I>, -<I>1000.0</I>,</P>
+			</UL>
+			<P>That defines the salinity to be constant down to z = -500.0 m
+			with a salinity given by <A HREF="#sa_surface">sa_surface</A>. For
+			-500.0 m &lt; z &lt;= -1000.0 m the salinity gradient is 1.0 psu /
+			100 m and for z &lt; -1000.0 m down to the bottom boundary it is
+			0.5 psu / 100 m (it is assumed that the assigned height levels
+			correspond with uv levels).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="sa_vertical_gradient_level"></A><B>sa_vertical_gradient_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the salinity gradient defined by
+			<A HREF="#sa_vertical_gradient">sa_vertical_gradient</A> is
+			effective (in m).&nbsp; 
+			</P>
+			<P>This parameter only comes into effect for ocean runs (see
+			parameter <A HREF="#ocean">ocean</A>).</P>
+			<P>The height levels have to be assigned in descending order. The
+			default values result in a constant salinity profile regardless of
+			the values of <A HREF="#sa_vertical_gradient">sa_vertical_gradient</A>
+			(unless the bottom boundary of the model is lower than -100000.0
+			m). For the piecewise construction of salinity profiles see
+			<A HREF="#sa_vertical_gradient">sa_vertical_gradient</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="scalar_advec"></A><B>scalar_advec</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 10</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'pw-scheme'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Advection scheme to be used for the scalar quantities.&nbsp; 
+			</P>
+			<P>The user can choose between the following schemes:</P>
+			<P><I>'pw-scheme'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">The scheme of
+			Piascek and Williams (1970, J. Comp. Phys., 6, 392-405) with
+			central differences in the form C3 is used.<BR>If intermediate
+			Euler-timesteps are carried out in case of <A HREF="#timestep_scheme">timestep_scheme</A>
+			= <I>'leapfrog+euler'</I> the advection scheme is - for the
+			Euler-timestep - automatically switched to an upstream-scheme. 
+			</P>
+			<P><BR><BR>
+			</P>
+			<P><I>'bc-scheme'</I></P>
+			<P STYLE="margin-left: 0.42in">The Bott scheme modified by Chlond
+			(1994, Mon. Wea. Rev., 122, 111-125). This is a conservative
+			monotonous scheme with very small numerical diffusion and
+			therefore very good conservation of scalar flow features. The
+			scheme however, is computationally very expensive both because it
+			is expensive itself and because it does (so far) not allow
+			specific code optimizations (e.g. cache optimization). Choice of
+			this scheme forces the Euler timestep scheme to be used for the
+			scalar quantities. For output of horizontally averaged profiles of
+			the resolved / total heat flux, <A HREF="chapter_4.2.html#data_output_pr">data_output_pr</A>
+			= <I>'w*pt*BC'</I> / <I>'wptBC' </I>should be used, instead of the
+			standard profiles (<I>'w*pt*'</I> and <I>'wpt'</I>) because these
+			are too inaccurate with this scheme. However, for subdomain
+			analysis (see <A HREF="#statistic_regions">statistic_regions</A>)
+			exactly the reverse holds: here <I>'w*pt*BC'</I> and <I>'wptBC'</I>
+			show very large errors and should not be used.<BR><BR>This scheme
+			is not allowed for non-cyclic lateral boundary conditions (see
+			<A HREF="#bc_lr">bc_lr</A> and <A HREF="#bc_ns">bc_ns</A>).</P>
+			<P><I>'ups-scheme'</I></P>
+			<P STYLE="margin-left: 0.42in">The upstream-spline-scheme is used
+			(see Mahrer and Pielke, 1978: Mon. Wea. Rev., 106, 818-830). In
+			opposite to the Piascek Williams scheme, this is characterized by
+			much better numerical features (less numerical diffusion, better
+			preservation of flux structures, e.g. vortices), but
+			computationally it is much more expensive. In addition, the use of
+			the Euler-timestep scheme is mandatory (<A HREF="#timestep_scheme">timestep_scheme</A>
+			= <I>'euler'</I>), i.e. the timestep accuracy is only first order.
+			For this reason the advection of momentum (see <A HREF="#momentum_advec">momentum_advec</A>)
+			should then also be carried out with the upstream-spline scheme,
+			because otherwise the momentum would be subject to large numerical
+			diffusion due to the upstream scheme.&nbsp; 
+			</P>
+			<P STYLE="margin-left: 0.42in">Since the cubic splines used tend
+			to overshoot under certain circumstances, this effect must be
+			adjusted by suitable filtering and smoothing (see
+			<A HREF="#cut_spline_overshoot">cut_spline_overshoot</A>,
+			<A HREF="#long_filter_factor">long_filter_factor</A>,
+			<A HREF="#ups_limit_pt">ups_limit_pt</A>, <A HREF="#ups_limit_u">ups_limit_u</A>,
+			<A HREF="#ups_limit_v">ups_limit_v</A>, <A HREF="#ups_limit_w">ups_limit_w</A>).
+			This is always neccesssary for runs with stable stratification,
+			even if this stratification appears only in parts of the model
+			domain.&nbsp; 
+			</P>
+			<P STYLE="margin-left: 0.42in">With stable stratification the
+			upstream-upline scheme also produces gravity waves with large
+			amplitude, which must be suitably damped (see
+			<A HREF="chapter_4.2.html#rayleigh_damping_factor">rayleigh_damping_factor</A>).</P>
+			<P STYLE="margin-left: 0.42in"><B>Important: </B>The&nbsp;
+			upstream-spline scheme is not implemented for humidity and passive
+			scalars (see&nbsp;<A HREF="#humidity">humidity</A> and
+			<A HREF="#passive_scalar">passive_scalar</A>) and requires the use
+			of a 2d-domain-decomposition. The last conditions severely
+			restricts code optimization on several machines leading to very
+			long execution times! This scheme is also not allowed for
+			non-cyclic lateral boundary conditions (see <A HREF="#bc_lr">bc_lr</A>
+			and <A HREF="#bc_ns">bc_ns</A>).</P>
+			<P><BR>A differing advection scheme can be choosed for the
+			subgrid-scale TKE using parameter <A HREF="#use_upstream_for_tke">use_upstream_for_tke</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="scalar_exchange_coefficient"></A><B>scalar_exchange_coefficient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Scalar exchange coefficient for a leaf (dimensionless).<BR><BR>This
+			parameter is only of importance in cases in that both,
+			<A HREF="../../../../../DEVELOPER_VERSION/chapter_4.1_adjusted.html#plant_canopy">plant_canopy</A>
+			and <A HREF="../../../../../DEVELOPER_VERSION/chapter_4.1_adjusted.html#passive_scalar">passive_scalar</A>,
+			are set <I>.T.</I>. The value of the scalar exchange coefficient
+			is required for the parametrisation of the sources and sinks of
+			scalar concentration due to the canopy.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="statistic_regions"></A><B>statistic_regions</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Number of additional user-defined subdomains for which
+			statistical analysis and corresponding output (profiles, time
+			series) shall be made.&nbsp; 
+			</P>
+			<P>By default, vertical profiles and other statistical quantities
+			are calculated as horizontal and/or volume average of the total
+			model domain. Beyond that, these calculations can also be carried
+			out for subdomains which can be defined using the field <A HREF="chapter_3.5.3.html">rmask
+			</A>within the user-defined software (see <A HREF="chapter_3.5.3.html">chapter
+			3.5.3</A>). The number of these subdomains is determined with the
+			parameter <B>statistic_regions</B>. Maximum 9 additional
+			subdomains are allowed. The parameter <A HREF="chapter_4.3.html#region">region</A>
+			can be used to assigned names (identifier) to these subdomains
+			which are then used in the headers of the output files and plots.</P>
+			<P>If the default NetCDF output format is selected (see parameter
+			<A HREF="chapter_4.2.html#data_output_format">data_output_format</A>),
+			data for the total domain and all defined subdomains are output to
+			the same file(s) (<A HREF="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</A>,
+			<A HREF="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</A>).
+			In case of <B>statistic_regions</B> &gt; <I>0</I>, data on the
+			file for the different domains can be distinguished by a suffix
+			which is appended to the quantity names. Suffix 0 means data for
+			the total domain, suffix 1 means data for subdomain 1, etc.</P>
+			<P>In case of <B>data_output_format</B> = <I>'profil'</I>,
+			individual local files for profiles (<A HREF="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</A>)&nbsp;are
+			created for each subdomain. The individual subdomain files differ
+			by their name (the number of the respective subdomain is attached,
+			e.g. PLOT1D_DATA_1). In this case the name of the file with the
+			data of the total domain is PLOT1D_DATA_0. If no subdomains are
+			declared (<B>statistic_regions</B> = <I>0</I>), the name
+			PLOT1D_DATA is used (this must be considered in the respective
+			file connection statements of the <B>mrun</B> configuration file).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="surface_heatflux"></A><B>surface_heatflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>no prescribed<BR>heatflux</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Kinematic sensible heat flux at the bottom surface (in K m/s).&nbsp;
+						</P>
+			<P>If a value is assigned to this parameter, the internal
+			two-dimensional surface heat flux field <I>shf</I> is initialized
+			with the value of <B>surface_heatflux</B>&nbsp;as bottom
+			(horizontally homogeneous) boundary condition for the temperature
+			equation. This additionally requires that a Neumann condition must
+			be used for the potential temperature (see <A HREF="#bc_pt_b">bc_pt_b</A>),
+			because otherwise the resolved scale may contribute to the surface
+			flux so that a constant value cannot be guaranteed. Also, changes
+			of the surface temperature (see <A HREF="#pt_surface_initial_change">pt_surface_initial_change</A>)
+			are not allowed. The parameter <A HREF="#random_heatflux">random_heatflux</A>
+			can be used to impose random perturbations on the (homogeneous)
+			surface heat flux field <I>shf</I>.&nbsp;</P>
+			<P>In case of a non-flat <A HREF="#topography">topography</A>,&nbsp;the
+			internal two-dimensional&nbsp;surface heat flux field <I>shf</I>
+			is initialized with the value of <B>surface_heatflux</B> at the
+			bottom surface and <A HREF="#wall_heatflux">wall_heatflux(0)</A>
+			at the topography top face.&nbsp;The parameter<A HREF="#random_heatflux">
+			random_heatflux</A> can be used to impose random perturbations on
+			this combined surface heat flux field <I>shf</I>.&nbsp; 
+			</P>
+			<P>If no surface heat flux is assigned, <I>shf</I> is calculated
+			at each timestep by u<SUB>*</SUB> * theta<SUB>*</SUB> (of course
+			only with <A HREF="#prandtl_layer">prandtl_layer</A> switched on).
+			Here, u<SUB>*</SUB> and theta<SUB>*</SUB> are calculated from the
+			Prandtl law assuming logarithmic wind and temperature profiles
+			between k=0 and k=1. In this case a Dirichlet condition (see
+			<A HREF="#bc_pt_b">bc_pt_b</A>) must be used as bottom boundary
+			condition for the potential temperature.</P>
+			<P>See also <A HREF="#top_heatflux">top_heatflux</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="surface_pressure"></A><B>surface_pressure</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>1013.25</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Atmospheric pressure at the surface (in hPa).&nbsp; 
+			</P>
+			<P>Starting from this surface value, the vertical pressure profile
+			is calculated once at the beginning of the run assuming a
+			neutrally stratified atmosphere. This is needed for converting
+			between the liquid water potential temperature and the potential
+			temperature (see <A HREF="#cloud_physics">cloud_physics</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="surface_scalarflux"></A><B>surface_scalarflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Scalar flux at the surface (in kg/(m<SUP>2</SUP> s)).&nbsp; 
+			</P>
+			<P>If a non-zero value is assigned to this parameter, the
+			respective scalar flux value is used as bottom (horizontally
+			homogeneous) boundary condition for the scalar concentration
+			equation.&nbsp;This additionally requires that a Neumann condition
+			must be used for the scalar concentration&nbsp;(see <A HREF="#bc_s_b">bc_s_b</A>),
+			because otherwise the resolved scale may contribute to the surface
+			flux so that a constant value cannot be guaranteed. Also, changes
+			of the surface scalar concentration (see <A HREF="#s_surface_initial_change">s_surface_initial_change</A>)
+			are not allowed. 
+			</P>
+			<P>If no surface scalar flux is assigned (<B>surface_scalarflux</B>
+			= <I>0.0</I>), it is calculated at each timestep by u<SUB>*</SUB>
+			* s<SUB>*</SUB> (of course only with Prandtl layer switched on).
+			Here, s<SUB>*</SUB> is calculated from the Prandtl law assuming a
+			logarithmic scalar concentration profile between k=0 and k=1. In
+			this case a Dirichlet condition (see <A HREF="#bc_s_b">bc_s_b</A>)
+			must be used as bottom boundary condition for the scalar
+			concentration.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="surface_waterflux"></A><B>surface_waterflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Kinematic water flux near the surface (in m/s).&nbsp; 
+			</P>
+			<P>If a non-zero value is assigned to this parameter, the
+			respective water flux value is used as bottom (horizontally
+			homogeneous) boundary condition for the humidity equation. This
+			additionally requires that a Neumann condition must be used for
+			the specific humidity / total water content (see <A HREF="#bc_q_b">bc_q_b</A>),
+			because otherwise the resolved scale may contribute to the surface
+			flux so that a constant value cannot be guaranteed. Also, changes
+			of the surface humidity (see <A HREF="#q_surface_initial_change">q_surface_initial_change</A>)
+			are not allowed.</P>
+			<P>If no surface water flux is assigned (<B>surface_waterflux</B>
+			= <I>0.0</I>), it is calculated at each timestep by u<SUB>*</SUB>
+			* q<SUB>*</SUB> (of course only with Prandtl layer switched on).
+			Here, q<SUB>*</SUB> is calculated from the Prandtl law assuming a
+			logarithmic temperature profile between k=0 and k=1. In this case
+			a Dirichlet condition (see <A HREF="#bc_q_b">bc_q_b</A>) must be
+			used as the bottom boundary condition for the humidity.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="s_surface"></A><B>s_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Surface value of the passive scalar (in kg/m<SUP>3</SUP>).&nbsp;</P>
+			<P>This parameter assigns the value of the passive scalar s at the
+			surface (k=0)<B>.</B> Starting from this value, the initial
+			vertical scalar concentration profile is constructed with<A HREF="#s_vertical_gradient">
+			s_vertical_gradient</A> and <A HREF="#s_vertical_gradient_level">s_vertical_gradient_level</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="s_surface_initial_change"></A><B>s_surface_initial</B>
+			<BR><B>_change</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Change in surface scalar concentration to be made at the
+			beginning of the 3d run (in kg/m<SUP>3</SUP>).&nbsp; 
+			</P>
+			<P>If <B>s_surface_initial_change</B>&nbsp;is set to a non-zero
+			value, the near surface scalar flux is not allowed to be given
+			simultaneously (see <A HREF="#surface_scalarflux">surface_scalarflux</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="s_vertical_gradient"></A><B>s_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Scalar concentration gradient(s) of the initial scalar
+			concentration profile (in kg/m<SUP>3 </SUP>/ 100 m).&nbsp; 
+			</P>
+			<P>The scalar gradient holds starting from the height level
+			defined by <A HREF="#s_vertical_gradient_level">s_vertical_gradient_level
+			</A>(precisely: for all uv levels k, where zu(k) &gt;
+			s_vertical_gradient_level, s_init(k) is set: s_init(k) =
+			s_init(k-1) + dzu(k) * <B>s_vertical_gradient</B>) up to the top
+			boundary or up to the next height level defined by
+			<A HREF="#s_vertical_gradient_level">s_vertical_gradient_level</A>.
+			A total of 10 different gradients for 11 height intervals (10
+			intervals if <A HREF="#s_vertical_gradient_level">s_vertical_gradient_level</A>(1)
+			= <I>0.0</I>) can be assigned. The surface scalar value is
+			assigned via <A HREF="#s_surface">s_surface</A>.</P>
+			<P>Example:&nbsp; 
+			</P>
+			<UL>
+				<P><B>s_vertical_gradient</B> = <I>0.1</I>, <I>0.05</I>,&nbsp;
+				<BR><B>s_vertical_gradient_level</B> = <I>500.0</I>, <I>1000.0</I>,</P>
+			</UL>
+			<P>That defines the scalar concentration to be constant with
+			height up to z = 500.0 m with a value given by <A HREF="#s_surface">s_surface</A>.
+			For 500.0 m &lt; z &lt;= 1000.0 m the scalar gradient is 0.1 kg/m<SUP>3
+			</SUP>/ 100 m and for z &gt; 1000.0 m up to the top boundary it is
+			0.05 kg/m<SUP>3 </SUP>/ 100 m (it is assumed that the assigned
+			height levels correspond with uv levels).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="s_vertical_gradient_level"></A><B>s_vertical_gradient_</B>
+			<BR><B>level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 *</I> <I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the scalar gradient defined by
+			<A HREF="#s_vertical_gradient">s_vertical_gradient</A> is
+			effective (in m).&nbsp; 
+			</P>
+			<P>The height levels are to be assigned in ascending order. The
+			default values result in a scalar concentration constant with
+			height regardless of the values of <A HREF="#s_vertical_gradient">s_vertical_gradient</A>
+			(unless the top boundary of the model is higher than 100000.0 m).
+			For the piecewise construction of scalar concentration profiles
+			see <A HREF="#s_vertical_gradient">s_vertical_gradient</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="timestep_scheme"></A><B>timestep_scheme</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'runge</I><BR><I>kutta-3'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Time step scheme to be used for the integration of the
+			prognostic variables.&nbsp; 
+			</P>
+			<P>The user can choose between the following schemes:</P>
+			<P><I>'runge-kutta-3'</I></P>
+			<P STYLE="margin-left: 0.42in">Third order Runge-Kutta
+			scheme.<BR>This scheme requires the use of <A HREF="#momentum_advec">momentum_advec</A>
+			= <A HREF="#scalar_advec">scalar_advec</A> = '<I>pw-scheme'</I>.
+			Please refer to the&nbsp;<A HREF="../tec/numerik.heiko/zeitschrittverfahren.pdf">documentation
+			on PALM's time integration schemes&nbsp;(28p., in German)</A> fur
+			further details.</P>
+			<P><I>'runge-kutta-2'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">Second order
+			Runge-Kutta scheme.<BR>For special features see <B>timestep_scheme</B>
+			= '<I>runge-kutta-3'</I>.</P>
+			<P><BR><I>'leapfrog'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">Second order
+			leapfrog scheme.<BR>Although this scheme requires a constant
+			timestep (because it is centered in time),&nbsp; is even applied
+			in case of changes in timestep. Therefore, only small changes of
+			the timestep are allowed (see <A HREF="#dt">dt</A>). However, an
+			Euler timestep is always used as the first timestep of an initiali
+			run. When using the Bott-Chlond scheme for scalar advection (see
+			<A HREF="#scalar_advec">scalar_advec</A>), the prognostic equation
+			for potential temperature will be calculated with the Euler
+			scheme, although the leapfrog scheme is switched on.&nbsp; <BR>The
+			leapfrog scheme must not be used together with the upstream-spline
+			scheme for calculating the advection (see <A HREF="#scalar_advec">scalar_advec</A>
+			= '<I>ups-scheme'</I> and <A HREF="#momentum_advec">momentum_advec</A>
+			= '<I>ups-scheme'</I>).</P>
+			<P><BR><I>'leapfrog+euler'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">The leapfrog
+			scheme is used, but after each change of a timestep an Euler
+			timestep is carried out. Although this method is theoretically
+			correct (because the pure leapfrog method does not allow timestep
+			changes), the divergence of the velocity field (after applying the
+			pressure solver) may be significantly larger than with <I>'leapfrog'</I>.</P>
+			<P><BR><I>'euler'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">First order
+			Euler scheme.&nbsp; <BR>The Euler scheme must be used when
+			treating the advection terms with the upstream-spline scheme (see
+			<A HREF="#scalar_advec">scalar_advec</A> = <I>'ups-scheme'</I> and
+			<A HREF="#momentum_advec">momentum_advec</A> = <I>'ups-scheme'</I>).</P>
+			<P STYLE="margin-bottom: 0in"><BR><BR>A differing timestep scheme
+			can be choosed for the subgrid-scale TKE using parameter
+			<A HREF="#use_upstream_for_tke">use_upstream_for_tke</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P ALIGN=LEFT><A NAME="topography"></A><B>topography</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C * 40</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>'flat'</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Topography mode.&nbsp; 
+			</P>
+			<P>The user can choose between the following modes:</P>
+			<P><I>'flat'</I></P>
+			<P STYLE="margin-left: 0.42in">Flat surface.</P>
+			<P><I>'single_building'</I></P>
+			<P STYLE="margin-left: 0.42in">Flow around&nbsp;a single
+			rectangular building mounted on a flat surface.<BR>The building
+			size and location can be specified by the parameters
+			<A HREF="#building_height">building_height</A>, <A HREF="#building_length_x">building_length_x</A>,
+			<A HREF="#building_length_y">building_length_y</A>,
+			<A HREF="#building_wall_left">building_wall_left</A> and
+			<A HREF="#building_wall_south">building_wall_south</A>.</P>
+			<P><I>'single_street_canyon'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">Flow over a
+			single, quasi-2D street canyon of infinite length oriented either
+			in x- or in y-direction.<BR>The canyon size, orientation and
+			location can be specified by the parameters <A HREF="#canyon_height">canyon_height</A>
+			plus <B>either</B>&nbsp;<A HREF="#canyon_width_x">canyon_width_x</A>
+			and <A HREF="#canyon_wall_left">canyon_wall_left</A> <B>or</B>&nbsp;
+			<A HREF="#canyon_width_y">canyon_width_y</A> and
+			<A HREF="#canyon_wall_south">canyon_wall_south</A>.</P>
+			<P>&nbsp;</P>
+			<P><I>'read_from_file'</I></P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in">Flow around
+			arbitrary topography.<BR>This mode requires the input file
+			<A HREF="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</A><FONT COLOR="#000000">.
+			This file contains the&nbsp;arbitrary topography height
+			information in m. These data&nbsp;must exactly match the
+			horizontal grid.</FONT></P>
+			<P STYLE="margin-bottom: 0in"><I><BR></I><FONT COLOR="#000000">Alternatively,
+			the user may add code to the user interface subroutine
+			<A HREF="chapter_3.5.1.html#user_init_grid">user_init_grid</A> to
+			allow further topography modes. </FONT>These require to explicitly
+			set the <A HREF="#topography_grid_convention">topography_grid_convention</A>&nbsp;to
+			either <I>'cell_edge'</I> or <I>'cell_center'</I>.<BR><FONT COLOR="#000000"><BR>Non-flat
+			</FONT><FONT COLOR="#000000"><B>topography</B></FONT><FONT COLOR="#000000">
+			modes may assign a</FONT> kinematic sensible<FONT COLOR="#000000">
+			<A HREF="#wall_heatflux">wall_heatflux</A> at the five topography
+			faces.</FONT><BR><FONT COLOR="#000000"><BR>All non-flat </FONT><FONT COLOR="#000000"><B>topography</B></FONT><FONT COLOR="#000000">
+			modes </FONT>require the use of <A HREF="#momentum_advec">momentum_advec</A>
+			= <A HREF="#scalar_advec">scalar_advec</A> = '<I>pw-scheme'</I>,
+			<A HREF="chapter_4.2.html#psolver">psolver</A> /= <I>'sor'</I>,
+			&nbsp;<A HREF="#alpha_surface">alpha_surface</A> =
+			0.0,&nbsp;<A HREF="#galilei_transformation">galilei_transformation</A>
+			= <I>.F.</I>,&nbsp;<A HREF="#cloud_physics">cloud_physics&nbsp;</A>
+			= <I>.F.</I>,&nbsp; <A HREF="#cloud_droplets">cloud_droplets</A> =
+			<I>.F.</I>,&nbsp;&nbsp;<A HREF="#humidity">humidity</A> = <I>.F.</I>,
+			and <A HREF="#prandtl_layer">prandtl_layer</A> = .T..<BR><FONT COLOR="#000000"><BR>Note
+			that an inclined model domain requires the use of </FONT><FONT COLOR="#000000"><B>topography</B></FONT><FONT COLOR="#000000">
+			= </FONT><FONT COLOR="#000000"><I>'flat'</I></FONT><FONT COLOR="#000000">
+			and a nonzero </FONT><A HREF="#alpha_surface">alpha_surface</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="topography_grid_convention"></A><B>topography_grid_</B><BR><B>convention</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>C*11</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>default depends on value of <A HREF="#topography">topography</A>;
+			see text for details</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Convention for defining the&nbsp;topography grid.<BR><BR>Possible
+			values are</P>
+			<UL>
+				<LI><P STYLE="margin-bottom: 0in"><I>'cell_edge':&nbsp;</I>the
+				distance between cell edges defines the extent of topography.
+				This setting is normally for <I>generic topographies</I>, i.e.
+				topographies that are constructed using length parameters. For
+				example, <A HREF="#topography">topography</A> = <I>'single_building'</I>
+				is constructed using <A HREF="#building_length_x">building_length_x</A>
+				and <A HREF="#building_length_y">building_length_y</A>. The
+				advantage of this setting is that the actual size of generic
+				topography is independent of the grid size, provided that the
+				length parameters are an integer multiple of the grid lengths&nbsp;<A HREF="#dx">dx</A>
+				and&nbsp;<A HREF="#dy">dy</A>. This is convenient&nbsp;for
+				resolution parameter studies.</P>
+				<LI><P><I>'cell_center':&nbsp;</I>the number of topography cells
+				define the extent of topography. This setting is normally for
+				<I>rastered real topographies</I> derived from digital elevation
+				models.&nbsp;For example, <A HREF="#topography">topography</A> =
+				<I>'read_from_file'</I> is constructed using&nbsp;the input file
+				<A HREF="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</A><FONT COLOR="#000000">.&nbsp;</FONT>The
+				advantage of this setting is that the&nbsp;rastered topography
+				cells of the input file are directly mapped to topography grid
+				boxes in PALM. 
+				</P>
+			</UL>
+			<P>The example files&nbsp;<CODE><FONT SIZE=4>example_topo_file</FONT></CODE>
+			and&nbsp;<CODE><FONT SIZE=4>example_building</FONT></CODE> in
+			<CODE><FONT SIZE=4>trunk/EXAMPLES/</FONT></CODE> illustrate the
+			difference between both approaches. Both examples simulate a
+			single building and yield the same results. The former uses a
+			rastered topography input file with <I>'cell_center'</I>
+			convention, the latter applies a generic topography with
+			<I>'cell_edge'</I> convention.<BR><BR>The default value is</P>
+			<UL>
+				<LI><P STYLE="margin-bottom: 0in"><I>'cell_edge' </I>if
+				<A HREF="#topography">topography</A> = <I>'single_building'</I>
+				or <I>'single_street_canyon'</I>,</P>
+				<LI><P STYLE="margin-bottom: 0in"><I>'cell_center'</I> if
+				<A HREF="#topography">topography</A> = <I>'read_from_file'</I>,</P>
+				<LI><P><I>none (' '</I> ) otherwise, leading to an abort
+				if&nbsp;<B>topography_grid_convention</B> is not set.</P>
+			</UL>
+			<P>This means that 
+			</P>
+			<UL>
+				<LI><P STYLE="margin-bottom: 0in">For PALM simulations using a
+				<I>user-defined topography</I>, the <B>topography_grid_convention</B>
+				must be explicitly set to either <I>'cell_edge'</I> or
+				<I>'cell_center'</I>.</P>
+				<LI><P>For PALM simulations using a <I>standard topography</I>
+				<I>('single_building'</I>, <I>'single_street_canyon'</I> or
+				<I>'read_from_file')</I>, it is possible but not required to set
+				the&nbsp; <B>topography_grid_convention</B> because appropriate
+				default values apply.</P>
+			</UL>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="top_heatflux"></A><B>top_heatflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>no prescribed<BR>heatflux</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Kinematic sensible heat flux at the top boundary (in K m/s).&nbsp;
+						</P>
+			<P>If a value is assigned to this parameter, the internal
+			two-dimensional surface heat flux field <FONT FACE="monospace">tswst</FONT>
+			is initialized with the value of <B>top_heatflux</B>&nbsp;as top
+			(horizontally homogeneous) boundary condition for the temperature
+			equation. This additionally requires that a Neumann condition must
+			be used for the potential temperature (see <A HREF="#bc_pt_t">bc_pt_t</A>),
+			because otherwise the resolved scale may contribute to the top
+			flux so that a constant flux value cannot be guaranteed.&nbsp;</P>
+			<P><B>Note:</B><BR>The application of a top heat flux additionally
+			requires the setting of initial parameter <A HREF="#use_top_fluxes">use_top_fluxes</A>
+			= .T.. 
+			</P>
+			<P>No Prandtl-layer is available at the top boundary so far.</P>
+			<P>See also <A HREF="#surface_heatflux">surface_heatflux</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="top_momentumflux_u"></A><B>top_momentumflux_u</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>no prescribed momentumflux</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Momentum flux along x at the top boundary (in m2/s2).</P>
+			<P>If a value is assigned to this parameter, the internal
+			two-dimensional u-momentum flux field <FONT FACE="monospace">uswst</FONT>
+			is initialized with the value of <B>top_momentumflux_u</B> as top
+			(horizontally homogeneous) boundary condition for the u-momentum
+			equation.</P>
+			<P><B>Notes:</B><BR>The application of a top momentum flux
+			additionally requires the setting of initial parameter
+			<A HREF="#use_top_fluxes">use_top_fluxes</A> = .T.. Setting of
+			<B>top_momentumflux_u</B> requires setting of <A HREF="#top_momentumflux_v">top_momentumflux_v</A>
+			also.</P>
+			<P>A&nbsp;Neumann condition should be used for the u velocity
+			component (see <A HREF="#bc_uv_t">bc_uv_t</A>), because otherwise
+			the resolved scale may contribute to the top flux so that a
+			constant flux value cannot be guaranteed.&nbsp;</P>
+			<P>No Prandtl-layer is available at the top boundary so far.</P>
+			<P>The <A HREF="chapter_3.8.html">coupled</A> ocean parameter
+			file&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>
+			should include dummy REAL value assignments to both
+			<A HREF="#top_momentumflux_u">top_momentumflux_u</A>
+			and&nbsp;<A HREF="#top_momentumflux_v">top_momentumflux_v</A>
+			(e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to
+			enable the momentum flux coupling.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="top_momentumflux_v"></A><B>top_momentumflux_v</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>no prescribed momentumflux</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Momentum flux along y at the top boundary (in m2/s2).</P>
+			<P>If a value is assigned to this parameter, the internal
+			two-dimensional v-momentum flux field <FONT FACE="monospace">vswst</FONT>
+			is initialized with the value of <B>top_momentumflux_v</B> as top
+			(horizontally homogeneous) boundary condition for the v-momentum
+			equation.</P>
+			<P><B>Notes:</B><BR>The application of a top momentum flux
+			additionally requires the setting of initial parameter
+			<A HREF="#use_top_fluxes">use_top_fluxes</A> = .T.. Setting of
+			<B>top_momentumflux_v</B> requires setting of <A HREF="#top_momentumflux_u">top_momentumflux_u</A>
+			also.</P>
+			<P>A&nbsp;Neumann condition should be used for the v velocity
+			component (see <A HREF="#bc_uv_t">bc_uv_t</A>), because otherwise
+			the resolved scale may contribute to the top flux so that a
+			constant flux value cannot be guaranteed.&nbsp;</P>
+			<P>No Prandtl-layer is available at the top boundary so far.</P>
+			<P>The <A HREF="chapter_3.8.html">coupled</A> ocean parameter
+			file&nbsp;<A HREF="chapter_3.4.html#PARIN"><FONT SIZE=2>PARIN_O</FONT></A>
+			should include dummy REAL value assignments to both
+			<A HREF="#top_momentumflux_u">top_momentumflux_u</A>
+			and&nbsp;<A HREF="#top_momentumflux_v">top_momentumflux_v</A>
+			(e.g.&nbsp;top_momentumflux_u = 0.0, top_momentumflux_v = 0.0) to
+			enable the momentum flux coupling.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="top_salinityflux"></A><B>top_salinityflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>no prescribed<BR>salinityflux</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Kinematic salinity flux at the top boundary, i.e. the sea
+			surface (in psu m/s).&nbsp; 
+			</P>
+			<P>This parameter only comes into effect for ocean runs (see
+			parameter <A HREF="#ocean">ocean</A>).</P>
+			<P>If a value is assigned to this parameter, the internal
+			two-dimensional surface heat flux field <FONT FACE="monospace">saswst</FONT>
+			is initialized with the value of <B>top_salinityflux</B>&nbsp;as
+			top (horizontally homogeneous) boundary condition for the salinity
+			equation. This additionally requires that a Neumann condition must
+			be used for the salinity (see <A HREF="#bc_sa_t">bc_sa_t</A>),
+			because otherwise the resolved scale may contribute to the top
+			flux so that a constant flux value cannot be guaranteed.&nbsp;</P>
+			<P><B>Note:</B><BR>The application of a salinity flux at the model
+			top additionally requires the setting of initial parameter
+			<A HREF="#use_top_fluxes">use_top_fluxes</A> = .T.. 
+			</P>
+			<P>See also <A HREF="#bottom_salinityflux">bottom_salinityflux</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="turbulent_inflow"></A><B>turbulent_inflow</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Generates a turbulent inflow at side boundaries using a
+			turbulence recycling method.<BR><BR>Turbulent inflow is realized
+			using the turbulence recycling method from Lund et al. (1998, J.
+			Comp. Phys., <B>140</B>, 233-258) modified by Kataoka and Mizuno
+			(2002, Wind and Structures, <B>5</B>, 379-392).<BR><BR>A turbulent
+			inflow requires Dirichlet conditions at the respective inflow
+			boundary. <B>So far, a turbulent inflow is realized from the left
+			(west) side only, i.e. <A HREF="#bc_lr">bc_lr</A></B>&nbsp;<B>=</B>
+			<I><B>'dirichlet/radiation'</B></I> <B>is required!</B><BR><BR>The
+			initial (quasi-stationary) turbulence field should be generated by
+			a precursor run and used by setting <A HREF="#initializing_actions">initializing_actions</A>
+			= <I>'cyclic_fill'</I>.<BR><BR>The distance of the recycling plane
+			from the inflow boundary can be set with parameter
+			<A HREF="#recycling_width">recycling_width</A>. The heigth above
+			ground above which the turbulence signal is not used for recycling
+			and the width of the layer within&nbsp;the magnitude of the
+			turbulence signal is damped from 100% to 0% can be set with
+			parameters <A HREF="#inflow_damping_height">inflow_damping_height</A>
+			and <A HREF="#inflow_damping_width">inflow_damping_width</A>.<BR><BR>The
+			detailed setup for a turbulent inflow is described in <A HREF="chapter_3.9.html">chapter
+			3.9</A>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="u_bulk"></A><B>u_bulk</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>u-component of the predefined bulk velocity (in m/s).<BR><BR>This
+			parameter comes into effect if <A HREF="#conserve_volume_flow">conserve_volume_flow</A>
+			= <I>.T.</I> and <A HREF="#conserve_volume_flow_mode">conserve_volume_flow_mode</A>
+			= <I>'bulk_velocity'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ug_surface"></A><B>ug_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>u-component of the geostrophic wind at the surface (in
+			m/s).<BR><BR>This parameter assigns the value of the u-component
+			of the geostrophic wind (ug) at the surface (k=0). Starting from
+			this value, the initial vertical profile of the <BR>u-component of
+			the geostrophic wind is constructed with <A HREF="#ug_vertical_gradient">ug_vertical_gradient</A>
+			and <A HREF="#ug_vertical_gradient_level">ug_vertical_gradient_level</A>.
+			The profile constructed in that way is used for creating the
+			initial vertical velocity profile of the 3d-model. Either it is
+			applied, as it has been specified by the user
+			(<A HREF="#initializing_actions">initializing_actions</A> =
+			'set_constant_profiles') or it is used for calculating a
+			stationary boundary layer wind profile (<A HREF="#initializing_actions">initializing_actions</A>
+			= 'set_1d-model_profiles'). If ug is constant with height (i.e.
+			ug(k)=<B>ug_surface</B>) and&nbsp; has a large value, it is
+			recommended to use a Galilei-transformation of the coordinate
+			system, if possible (see <A HREF="#galilei_transformation">galilei_transformation</A>),
+			in order to obtain larger time steps.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs (see <A HREF="#ocean">ocean</A>), this
+			parameter gives the geostrophic velocity value (i.e. the pressure
+			gradient) at the sea surface, which is at k=nzt. The profile is
+			then constructed from the surface down to the bottom of the model.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ug_vertical_gradient"></A><B>ug_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Gradient(s) of the initial profile of the&nbsp; u-component of
+			the geostrophic wind (in 1/100s).<BR><BR>The gradient holds
+			starting from the height level defined by
+			<A HREF="#ug_vertical_gradient_level">ug_vertical_gradient_level</A>
+			(precisely: for all uv levels k where zu(k) &gt;
+			<A HREF="#ug_vertical_gradient_level">ug_vertical_gradient_level</A>,
+			ug(k) is set: ug(k) = ug(k-1) + dzu(k) * <B>ug_vertical_gradient</B>)
+			up to the top boundary or up to the next height level defined by
+			<A HREF="#ug_vertical_gradient_level">ug_vertical_gradient_level</A>.
+			A total of 10 different gradients for 11 height intervals (10
+			intervals&nbsp; if <A HREF="#ug_vertical_gradient_level">ug_vertical_gradient_level</A>(1)
+			= 0.0) can be assigned. The surface geostrophic wind is assigned
+			by <A HREF="#ug_surface">ug_surface</A>.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs (see <A HREF="#ocean">ocean</A>), the profile
+			is constructed like described above, but starting from the sea
+			surface (k=nzt) down to the bottom boundary of the model. Height
+			levels have then to be given as negative values, e.g.
+			<B>ug_vertical_gradient_level</B> = <I>-500.0</I>, <I>-1000.0</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ug_vertical_gradient_level"></A><B>ug_vertical_gradient_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the gradient defined by
+			<A HREF="#ug_vertical_gradient">ug_vertical_gradient</A> is
+			effective (in m).<BR><BR>The height levels have to be assigned in
+			ascending order. For the piecewise construction of a profile of
+			the u-component of the geostrophic wind component (ug) see
+			<A HREF="#ug_vertical_gradient">ug_vertical_gradient</A>.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs&nbsp;(see <A HREF="#ocean">ocean</A>), the
+			(negative) height levels have to be assigned in descending order.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ups_limit_e"></A><B>ups_limit_e</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Subgrid-scale turbulent kinetic energy difference used as
+			criterion for applying the upstream scheme when upstream-spline
+			advection is switched on (in m<SUP>2</SUP>/s<SUP>2</SUP>). &nbsp; 
+			</P>
+			<P>This variable steers the appropriate treatment of the advection
+			of the subgrid-scale turbulent kinetic energy in case that the
+			uptream-spline scheme is used . For further information see
+			<A HREF="#ups_limit_pt">ups_limit_pt</A>.&nbsp; 
+			</P>
+			<P>Only positive values are allowed for <B>ups_limit_e</B>. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ups_limit_pt"></A><B>ups_limit_pt</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Temperature difference used as criterion for applying&nbsp; the
+			upstream scheme when upstream-spline advection&nbsp; is switched
+			on (in K).&nbsp; 
+			</P>
+			<P>This criterion is used if the upstream-spline scheme is
+			switched on (see <A HREF="#scalar_advec">scalar_advec</A>).<BR>If,
+			for a given gridpoint, the absolute temperature difference with
+			respect to the upstream grid point is smaller than the value given
+			for <B>ups_limit_pt</B>, the upstream scheme is used for this
+			gridpoint (by default, the upstream-spline scheme is always used).
+			Reason: in case of a very small upstream gradient, the advection
+			should cause only a very small tendency. However, in such
+			situations the upstream-spline scheme may give wrong tendencies at
+			a grid point due to spline overshooting, if simultaneously the
+			downstream gradient is very large. In such cases it may be more
+			reasonable to use the upstream scheme. The numerical diffusion
+			caused by the upstream schme remains small as long as the upstream
+			gradients are small.</P>
+			<P>The percentage of grid points for which the upstream scheme is
+			actually used, can be output as a time series with respect to the
+			three directions in space with run parameter (see <A HREF="chapter_4.2.html#dt_dots">dt_dots</A>,
+			the timeseries names in the NetCDF file are <I>'splptx'</I>,
+			<I>'splpty'</I>, <I>'splptz'</I>). The percentage of gridpoints&nbsp;
+			should stay below a certain limit, however, it is not possible to
+			give a general limit, since it depends on the respective flow.&nbsp;
+						</P>
+			<P>Only positive values are permitted for <B>ups_limit_pt</B>.</P>
+			<P>A more effective control of the âovershootsâ can be
+			achieved with parameter <A HREF="#cut_spline_overshoot">cut_spline_overshoot</A>.
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ups_limit_u"></A><B>ups_limit_u</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Velocity difference (u-component) used as criterion for
+			applying the upstream scheme when upstream-spline advection is
+			switched on (in m/s).&nbsp; 
+			</P>
+			<P>This variable steers the appropriate treatment of the advection
+			of the u-velocity-component in case that the upstream-spline
+			scheme is used. For further information see <A HREF="#ups_limit_pt">ups_limit_pt</A>.&nbsp;
+						</P>
+			<P>Only positive values are permitted for <B>ups_limit_u</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ups_limit_v"></A><B>ups_limit_v</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Velocity difference (v-component) used as criterion for
+			applying the upstream scheme when upstream-spline advection is
+			switched on (in m/s).&nbsp; 
+			</P>
+			<P>This variable steers the appropriate treatment of the advection
+			of the v-velocity-component in case that the upstream-spline
+			scheme is used. For further information see <A HREF="#ups_limit_pt">ups_limit_pt</A>.&nbsp;
+						</P>
+			<P>Only positive values are permitted for <B>ups_limit_v</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="ups_limit_w"></A><B>ups_limit_w</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Velocity difference (w-component) used as criterion for
+			applying the upstream scheme when upstream-spline advection is
+			switched on (in m/s).&nbsp; 
+			</P>
+			<P>This variable steers the appropriate treatment of the advection
+			of the w-velocity-component in case that the upstream-spline
+			scheme is used. For further information see <A HREF="#ups_limit_pt">ups_limit_pt</A>.&nbsp;
+						</P>
+			<P>Only positive values are permitted for <B>ups_limit_w</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="use_surface_fluxes"></A><B>use_surface_fluxes</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to steer the treatment of the subgrid-scale vertical
+			fluxes within the diffusion terms at k=1 (bottom boundary).</P>
+			<P>By default, the near-surface subgrid-scale fluxes are
+			parameterized (like in the remaining model domain) using the
+			gradient approach. If <B>use_surface_fluxes</B> = <I>.TRUE.</I>,
+			the user-assigned surface fluxes are used instead (see
+			<A HREF="#surface_heatflux">surface_heatflux</A>,
+			<A HREF="#surface_waterflux">surface_waterflux</A> and
+			<A HREF="#surface_scalarflux">surface_scalarflux</A>) <B>or</B>
+			the surface fluxes are calculated via the Prandtl layer relation
+			(depends on the bottom boundary conditions, see <A HREF="#bc_pt_b">bc_pt_b</A>,
+			<A HREF="#bc_q_b">bc_q_b</A> and <A HREF="#bc_s_b">bc_s_b</A>).</P>
+			<P><B>use_surface_fluxes</B> is automatically set <I>.TRUE.</I>,
+			if a Prandtl layer is used (see <A HREF="#prandtl_layer">prandtl_layer</A>).&nbsp;
+						</P>
+			<P>The user may prescribe the surface fluxes at the bottom
+			boundary without using a Prandtl layer by setting
+			<B>use_surface_fluxes</B> = <I>.T.</I> and <B>prandtl_layer</B> =
+			<I>.F.</I>. If , in this case, the momentum flux (u<SUB>*</SUB><SUP>2</SUP>)
+			should also be prescribed, the user must assign an appropriate
+			value within the user-defined code.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="use_top_fluxes"></A><B>use_top_fluxes</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to steer the treatment of the subgrid-scale vertical
+			fluxes within the diffusion terms at k=nz (top boundary).</P>
+			<P>By default, the fluxes at nz are calculated using the gradient
+			approach. If <B>use_top_fluxes</B> = <I>.TRUE.</I>, the
+			user-assigned top fluxes are used instead (see <A HREF="#top_heatflux">top_heatflux</A>,
+			<A HREF="#top_momentumflux_u">top_momentumflux_u</A>,
+			<A HREF="#top_momentumflux_v">top_momentumflux_v</A>,
+			<A HREF="#top_salinityflux">top_salinityflux</A>).</P>
+			<P>Currently, no value for the latent heatflux can be assigned. In
+			case of <B>use_top_fluxes</B> = <I>.TRUE.</I>, the latent heat
+			flux at the top will be automatically set to zero.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="use_ug_for_galilei_tr"></A><B>use_ug_for_galilei_tr</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Switch to determine the translation velocity in case that a
+			Galilean transformation is used.</P>
+			<P>In case of a Galilean transformation (see
+			<A HREF="#galilei_transformation">galilei_transformation</A>),
+			<B>use_ug_for_galilei_tr</B> = <I>.T.</I>&nbsp; ensures that the
+			coordinate system is translated with the geostrophic windspeed.</P>
+			<P>Alternatively, with <B>use_ug_for_galilei_tr</B> = <I>.F</I>.,
+			the geostrophic wind can be replaced as translation speed by the
+			(volume) averaged velocity. However, in this case the user must be
+			aware of fast growing gravity waves, so this choice is usually not
+			recommended!</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=126>
+			<P ALIGN=LEFT><A NAME="use_upstream_for_tke"></A><B>use_upstream_for_tke</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P ALIGN=LEFT>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P ALIGN=LEFT><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P ALIGN=LEFT>Parameter to choose the advection/timestep scheme to
+			be used for the subgrid-scale TKE.<BR><BR>By default, the
+			advection scheme and the timestep scheme to be used for the
+			subgrid-scale TKE are set by the initialization parameters
+			<A HREF="#scalar_advec">scalar_advec</A> and <A HREF="#timestep_scheme">timestep_scheme</A>,
+			respectively. <B>use_upstream_for_tke</B> = <I>.T.</I> forces the
+			Euler-scheme and the upstream-scheme to be used as timestep scheme
+			and advection scheme, respectively. By these methods, the strong
+			(artificial) near-surface vertical gradients of the subgrid-scale
+			TKE are significantly reduced. This is required when subgrid-scale
+			velocities are used for advection of particles (see particle
+			package parameter <A HREF="chapter_4.2.html#use_sgs_for_particles">use_sgs_for_particles</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="v_bulk"></A><B>v_bulk</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>v-component of the predefined bulk velocity (in m/s).<BR><BR>This
+			parameter comes into effect if <A HREF="#conserve_volume_flow">conserve_volume_flow</A>
+			= <I>.T.</I> and <A HREF="#conserve_volume_flow_mode">conserve_volume_flow_mode</A>
+			= <I>'bulk_velocity'</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="vg_surface"></A><B>vg_surface</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>v-component of the geostrophic wind at the surface (in
+			m/s).<BR><BR>This parameter assigns the value of the v-component
+			of the geostrophic wind (vg) at the surface (k=0). Starting from
+			this value, the initial vertical profile of the <BR>v-component of
+			the geostrophic wind is constructed with <A HREF="#vg_vertical_gradient">vg_vertical_gradient</A>
+			and <A HREF="#vg_vertical_gradient_level">vg_vertical_gradient_level</A>.
+			The profile constructed in that way is used for creating the
+			initial vertical velocity profile of the 3d-model. Either it is
+			applied, as it has been specified by the user
+			(<A HREF="#initializing_actions">initializing_actions</A> =
+			'set_constant_profiles') or it is used for calculating a
+			stationary boundary layer wind profile (<A HREF="#initializing_actions">initializing_actions</A>
+			= 'set_1d-model_profiles'). If vg is constant with height (i.e.
+			vg(k)=<B>vg_surface</B>) and&nbsp; has a large value, it is
+			recommended to use a Galilei-transformation of the coordinate
+			system, if possible (see <A HREF="#galilei_transformation">galilei_transformation</A>),
+			in order to obtain larger time steps.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs (see <A HREF="#ocean">ocean</A>), this
+			parameter gives the geostrophic velocity value (i.e. the pressure
+			gradient) at the sea surface, which is at k=nzt. The profile is
+			then constructed from the surface down to the bottom of the model.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="vg_vertical_gradient"></A><B>vg_vertical_gradient</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Gradient(s) of the initial profile of the&nbsp; v-component of
+			the geostrophic wind (in 1/100s).<BR><BR>The gradient holds
+			starting from the height level defined by
+			<A HREF="#vg_vertical_gradient_level">vg_vertical_gradient_level</A>
+			(precisely: for all uv levels k where zu(k) &gt;
+			<A HREF="#vg_vertical_gradient_level">vg_vertical_gradient_level</A>,
+			vg(k) is set: vg(k) = vg(k-1) + dzu(k) * <B>vg_vertical_gradient</B>)
+			up to the top boundary or up to the next height level defined by
+			<A HREF="#vg_vertical_gradient_level">vg_vertical_gradient_level</A>.
+			A total of 10 different gradients for 11 height intervals (10
+			intervals&nbsp; if <A HREF="#vg_vertical_gradient_level">vg_vertical_gradient_level</A>(1)
+			= 0.0) can be assigned. The surface geostrophic wind is assigned
+			by <A HREF="#vg_surface">vg_surface</A>.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs (see <A HREF="#ocean">ocean</A>), the profile
+			is constructed like described above, but starting from the sea
+			surface (k=nzt) down to the bottom boundary of the model. Height
+			levels have then to be given as negative values, e.g.
+			<B>vg_vertical_gradient_level</B> = <I>-500.0</I>, <I>-1000.0</I>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="vg_vertical_gradient_level"></A><B>vg_vertical_gradient_level</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Height level from which on the gradient defined by
+			<A HREF="#vg_vertical_gradient">vg_vertical_gradient</A> is
+			effective (in m).<BR><BR>The height levels have to be assigned in
+			ascending order. For the piecewise construction of a profile of
+			the v-component of the geostrophic wind component (vg) see
+			<A HREF="#vg_vertical_gradient">vg_vertical_gradient</A>.<BR><BR><B>Attention:</B><BR>In
+			case of ocean runs&nbsp;(see <A HREF="#ocean">ocean</A>), the
+			(negative) height levels have to be assigned in descending order.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="wall_adjustment"></A><B>wall_adjustment</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Parameter to restrict the mixing length in the vicinity of the
+			bottom boundary (and near vertical walls of a non-flat
+			<A HREF="#topography">topography</A>).&nbsp; 
+			</P>
+			<P>With <B>wall_adjustment</B> = <I>.TRUE., </I>the mixing length
+			is limited to a maximum of&nbsp; 1.8 * z. This condition typically
+			affects only the first grid points above the bottom boundary.</P>
+			<P>In case of&nbsp; a non-flat <A HREF="#topography">topography</A>
+			the respective horizontal distance from vertical walls is used.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=126>
+			<P><A NAME="wall_heatflux"></A><B>wall_heatflux</B></P>
+		</TD>
+		<TD WIDTH=45>
+			<P>R(5)</P>
+		</TD>
+		<TD WIDTH=159>
+			<P><I>5 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=1280>
+			<P>Prescribed kinematic sensible heat flux in K m/s at the five
+			topography faces:</P>
+			<P STYLE="margin-left: 0.42in; margin-bottom: 0in"><B>wall_heatflux(0)&nbsp;&nbsp;
+			&nbsp;</B>top face<BR><B>wall_heatflux(1)&nbsp;&nbsp;&nbsp; </B>left
+			face<BR><B>wall_heatflux(2)&nbsp;&nbsp;&nbsp; </B>right
+			face<BR><B>wall_heatflux(3)&nbsp;&nbsp;&nbsp; </B>south
+			face<BR><B>wall_heatflux(4)&nbsp;&nbsp;&nbsp; </B>north face</P>
+			<P STYLE="margin-bottom: 0in"><BR>This parameter applies only in
+			case of a non-flat <A HREF="#topography">topography</A>.&nbsp;The
+			parameter <A HREF="#random_heatflux">random_heatflux</A> can be
+			used to impose random perturbations on the internal
+			two-dimensional surface heat flux field <I>shf</I> that is
+			composed of <A HREF="#surface_heatflux">surface_heatflux</A> at
+			the bottom surface and <B>wall_heatflux(0)</B> at the topography
+			top face.&nbsp;</P>
+		</TD>
+	</TR>
+</TABLE>
+<P><BR><BR>
+</P>
+<P STYLE="line-height: 100%"><BR><FONT COLOR="#000080"><A HREF="chapter_4.0.html"><FONT COLOR="#000080"><IMG SRC="left.gif" NAME="Grafik1" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A><A HREF="index.html"><FONT COLOR="#000080"><IMG SRC="up.gif" NAME="Grafik2" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A><A HREF="chapter_4.2.html"><FONT COLOR="#000080"><IMG SRC="right.gif" NAME="Grafik3" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A></FONT></P>
+<P STYLE="line-height: 100%"><I>Last change:&nbsp;</I> $Id:
+chapter_4.1.html 328 2009-05-28 12:13:56Z letzel $ 
+</P>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
Index: /palm/trunk/DOC/app/chapter_4.6.html
===================================================================
--- /palm/trunk/DOC/app/chapter_4.6.html	(revision 343)
+++ /palm/trunk/DOC/app/chapter_4.6.html	(revision 344)
@@ -1,15427 +1,5447 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html><head>
-
-
-
-
-  
-  
-  
-  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
-
-
-
-  
- 
-  
-  
-  
-  
-  
-  
-  <title>PALM chapter 4.6</title><meta name="GENERATOR" content="StarOffice 7 (Win32)">
-
-
-
- 
-  
-  
-  
-  <meta name="AUTHOR" content="Marcus Oliver Letzel">
-
-
-
- 
-  
-  
-  
-  <meta name="CREATED" content="20041103;9554421">
-
-
-
- 
-  
-  
-  
-  <meta name="CHANGED" content="20041117;12591937">
-
-
-
- 
-  
-  
-  
-  <meta name="KEYWORDS" content="parallel LES model">
-
-
-
- 
-  
-  
-  
-  <style>
-<!--
-@page { size: 21cm 29.7cm }
--->
-  </style></head>
-<body style="direction: ltr;" lang="en-US">
-
-
-
-<h3>4.6
-Listing of the steering parameters in alphabetical order<br>
-
-
-
-
-</h3>
-
-
-
-<p style="margin-bottom: 0cm;">Initialization
-parameters
-(class = I),
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
+	<TITLE>PALM chapter 4.6</TITLE>
+	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0  (Unix)">
+	<META NAME="AUTHOR" CONTENT="Marcus Oliver Letzel">
+	<META NAME="CREATED" CONTENT="20041103;9554500">
+	<META NAME="CHANGED" CONTENT="20090624;15364600">
+	<META NAME="KEYWORDS" CONTENT="parallel LES model">
+	<STYLE TYPE="text/css">
+	<!--
+		@page { size: 8.27in 11.69in }
+		TD P { color: #000000 }
+		P { color: #000000 }
+		H3 { color: #000000 }
+	-->
+	</STYLE>
+</HEAD>
+<BODY LANG="en-US" TEXT="#000000" DIR="LTR">
+<H3>4.6 Listing of the steering parameters in alphabetical order</H3>
+<P STYLE="margin-bottom: 0in">Initialization parameters (class = I),
 run parameters (R), package parameters (P) as well as user-defined
-parameters (U) are alphabetically listed in the following table. <br>
-
-
-
-
-&nbsp;
-</p>
-
-
-
-<p style="margin-bottom: 0cm;" align="center"><br>
-
-
-
-
-</p>
-
-
-
-<table style="width: 100%;" border="1" cellpadding="2" cellspacing="4">
-
-
-
- <col width="38*">
-  <col width="12*"> <col width="18*"> <col width="42*"> <col width="146*"> <tbody>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <h3><b>Parameter name</b></h3>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="5%"> 
-      
-      
-      
-      <h3>Class</h3>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="7%">
-      
-      
-      
-      <h3>Type</h3>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <h3>Default<br>
-
-
-
-
-value</h3>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <h3>Explanation</h3>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#adjust_mixing_length"><b>adjust_mixing_length</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Near-surface
-adjustment of the
-mixing length to the Prandtl-layer law.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#alpha_surface"><b>alpha_surface</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Inclination
-of the model domain
-with respect to the horizontal (in degrees).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#averaging_interval"><span style="font-weight: bold;">averaging_interval</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">0.0</span></td>
-
-
-
- <td>Averaging
-interval for all&nbsp;output of temporally averaged data (in s).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#averaging_interval_pr"><b>averaging_interval_pr</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
-
-
-
-
-interval</a></span></td>
-
-
-
- <td style="width: 57%; text-align: left; vertical-align: middle;">
-Averaging interval for vertical profiles&nbsp;output to local
-file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
-      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
-(in s).&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#averaging_interval_sp"><b>averaging_interval_sp</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
-
-
-
-
-interval</a></span></td>
-
-
-
- <td style="vertical-align: middle;" width="57%">Averaging
-interval for spectra output to local
-file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
-      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
-/ &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
-(in s).&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_e_b"><b>bc_e_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'neumann'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom boundary condition of the
-TKE. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#bc_lr"><b>bc_lr</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">C * 20<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">&acute;cyclic&acute;</span><br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;">Boundary
-condition along x (for all quantities).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#bc_ns"><b>bc_ns</b></a></b></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">C * 20</td>
-
-
-
- <td style="vertical-align: middle;"><span style="font-style: italic;">'cyclic'</span></td>
-
-
-
-
-      <td style="vertical-align: middle;">Boundary
-condition along y (for all quantities).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_p_b"><b>bc_p_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'neumann'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom boundary condition of the
-perturbation pressure. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_p_t"><b>bc_p_t</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'dirichlet'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Top boundary condition of the
-perturbation pressure. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_b"><b>bc_par_b</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">C*15</td>
-
-
-
- <td style="vertical-align: middle;"><i>&acute;reflect&acute;</i></td>
-
-
-
-
-      <td style="vertical-align: middle;"> 
-      
-      
-      
-      <p>Bottom
-boundary condition for particle transport. </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_lr"><b>bc_par_lr</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">C*15</td>
-
-
-
- <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Lateral boundary
-condition
-(x-direction) for particle
-transport.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_ns"><b>bc_par_ns</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">C*15</td>
-
-
-
- <td style="vertical-align: middle;"><i>&acute;cyclic&acute;</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Lateral boundary
-condition
-(y-direction) for particle
-transport.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#bc_par_t"><b>bc_par_t</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">C*15</td>
-
-
-
- <td style="vertical-align: middle;"><i>&acute;absorb&acute;</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Top boundary
-condition for
-particle transport.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_pt_b"><b>bc_pt_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'dirichlet'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom boundary condition of the
-potential temperature. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#pc_pt_t"><b>bc_pt_t</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'initial_gradient'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Top boundary condition of the
-potential temperature. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_q_b"><b>bc_q_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'dirichlet'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom boundary condition of the
-specific humidity / total water content. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_q_t"><b>bc_q_t</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'neumann'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Top boundary condition of the
-specific humidity / total water content. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_s_b"><b>bc_s_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'dirichlet'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom boundary condition of the
-scalar concentration. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_s_t"><b>bc_s_t</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>&acute;neumann&acute;</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Top boundary condition of the
-scalar concentration. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#bc_sa_t"><span style="font-weight: bold;">bc_sa_t</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">C * 20</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">'neumann'</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Top boundary condition of the salinity.&nbsp;</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_uv_b"><b>bc_uv_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'dirichlet'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom boundary condition of the horizontal wind
-components u
-and v.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#bc_uv_t"><b>bc_uv_t</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'dirichlet'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Top boundary condition of the
-horizontal velocity components u and v.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#bottom_salinityflux"><span style="font-weight: bold;">bottom_salinityflux</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">0.0</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Kinematic salinity flux near the surface (in psu m/s).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td style="font-weight: bold;"><a href="chapter_4.1.html#building_height">building_height</a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R</td>
-
-
-
- <td style="font-style: italic;">50.0</td>
-
-
-
- <td>Height
-of a single building in m.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_x">building_length_x</a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R</td>
-
-
-
- <td style="font-style: italic;">50.0</td>
-
-
-
- <td>Width
-of a single building in m.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="font-weight: bold;"><a href="chapter_4.1.html#building_length_y">building_length_y</a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R</td>
-
-
-
- <td style="font-style: italic;">50.0</td>
-
-
-
- <td>Depth
-of a single building in m.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_left">building_wall_left</a></td>
-
-
-
-
-      <td style="vertical-align: middle;">I</td>
-
-
-
- <td style="vertical-align: middle;">R</td>
-
-
-
- <td style="font-style: italic;"><span style="font-style: italic;">building centered in x-direction</span></td>
-
-
-
-
-      <td style="vertical-align: middle;">x-coordinate of the
-left building wall in m.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="font-weight: bold; vertical-align: middle;"><a href="chapter_4.1.html#building_wall_south">building_wall_south</a></td>
-
-
-
-
-      <td style="vertical-align: middle;">I</td>
-
-
-
- <td style="vertical-align: middle;">R</td>
-
-
-
- <td style="font-style: italic;"><span style="font-style: italic;">building centered in y-direction</span></td>
-
-
-
-
-      <td style="vertical-align: middle;">y-coordinate of the
-South building wall&nbsp;in m.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#call_psolver_at_all_substeps"><b>call_psolver_at_all_substeps</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">L<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">.T..</span><br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">Switch
-to steer the call of the pressure solver.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-      <td><b><b><a href="chapter_4.2.html#fcl_factor"><b>canopy_mode</b></a></b></b></td>
-      <td>I</td>
-      <td>C * 20</td>
-      <td><span style="font-style: italic;">'block'</span></td>
-      <td>Canopy mode</td>
-    </tr>
-    <tr><td style="font-weight: bold;"><a href="chapter_4.1.html#canyon_height">canyon_height</a></td><td>I</td><td>R</td><td style="font-style: italic;">50.0</td><td>Street canyon height
-in m.</td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#canyon_width_x">canyon_width_x</a></td><td>I</td><td>R</td><td style="font-style: italic;">9999999.9</td><td>Street canyon width in x-direction in m.</td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#canyon_width_y">canyon_width_y</a></td><td>I</td><td>R</td><td style="font-style: italic;">9999999.9</td><td>Street canyon width in y-direction in m.</td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#canyon_wall_left">canyon_wall_left</a></td><td>I</td><td>R</td><td style="font-style: italic;">canyon centered in x-direction</td><td>x-coordinate of the left canyon wall&nbsp;in m.</td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#canyon_wall_south">canyon_wall_south</a></td><td>I</td><td>R</td><td style="font-style: italic;">canyon centered in y-direction</td><td>y-coordinate of the South canyon wall&nbsp;in m.</td></tr><tr>
-
-
-
-
-      <td><b><a href="chapter_4.2.html#fcl_factor"><b>cfl_factor</b></a></b></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><i>0.1,
-0.8&nbsp;or 0.9 </i>(see parameter description)</td>
-
-
-
- <td>Time
-step limiting factor.</td>
-
-
-
- </tr>
-
-
-
- <tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#clip_dvrp_l"><span style="font-weight: bold;">clip_dvrp_l</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.0</span></td><td align="undefined" valign="undefined">Left boundary of the displayed domain (in m).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#clip_dvrp_n"><span style="font-weight: bold;">clip_dvrp_n</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">(ny+1)*dy</span></td><td align="undefined" valign="undefined">North boundary of the displayed domain (in m).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#clip_dvrp_r"><span style="font-weight: bold;">clip_dvrp_r</span></a></td><td align="undefined" valign="undefined">P</td><td style="font-style: italic;" align="undefined" valign="undefined">R</td><td style="font-style: italic;" align="undefined" valign="undefined">(nx+1)*dx</td><td align="undefined" valign="undefined">Right boundary of the displayed domain (in m).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#clip_dvrp_s"><span style="font-weight: bold;">clip_dvrp_s</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined">0.0</td><td align="undefined" valign="undefined">South boundary of the displayed domain (in m).</td></tr><tr>
-
-
-
- <td style="vertical-align: top;"><a href="chapter_4.1.html#cloud_droplets"><span style="font-weight: bold;">cloud_droplets</span></a><br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: top;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: top;">L<br>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: top;">Parameter to switch
-on usage of cloud droplets.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#cloud_physics"><b>cloud_physics</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to switch on the condensation scheme. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr><td><a href="chapter_4.2.html#cluster_size"><span style="font-weight: bold;">cluster_size</span></a></td><td>P</td><td>I</td><td><span style="font-style: italic;">1</span></td><td>Vertex cluster size for polygon reduction of topography.</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#color_interval"><span style="font-weight: bold;">color_interval</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R(2)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.0</span>, <span style="font-style: italic;">1.0</span></td><td align="undefined" valign="undefined">Interval of values used for determining the particle color displayed in the animation.</td></tr><tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#comp_spectra_level"><b>comp_spectra_level</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I
-(100)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>no level</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Vertical level for which horizontal spectra are to be
-calculated and output (gridpoints).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.1.html#conserve_volume_flow"><span style="font-weight: bold;">conserve_volume_flow</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>L</td>
-
-
-
- <td><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td>Conservation
-of volume flow in x- and y-direction.</td>
-
-
-
- </tr>
-
-
-
- <tr><td><a href="chapter_4.1.html#conserve_volume_flow_mode"><span style="font-weight: bold;">conserve_volume_flow_mode</span></a></td><td>I</td><td>C * 16</td><td><span style="font-style: italic;">'default'</span></td><td>Modus of volume flow conservation.</td></tr><tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#create_disturbances"><b>create_disturbances</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.T.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Switch
-to impose random perturbations to the horizontal
-velocity field. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#cross_normalized_x"><b>cross_normalized_x</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 10 (100)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>100
-* ' '</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Type
-of normalization applied to the x-coordinate of
-vertical
-profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#cross_normalized_y"><b>cross_normalized_y</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 10&nbsp; <br>
-
-
-
-
-(100)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>100 * ' '</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Type of normalization applied to the y-coordinate of
-vertical
-profiles to be plotted with <span style="font-weight: bold;">profil</span>.
-      <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#cross_profiles"><b>cross_profiles</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 100 (100)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p>see
-parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Determines
-which vertical profiles are to be presented
-in
-which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is
-used.&nbsp; <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#cross_xtext"><b>cross_xtext</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 40&nbsp; <br>
-
-
-
-
-&nbsp;(100)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p>see
-parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>x-axis
-labels of vertical profile coordinate systems to
-be
-plotted with <span style="font-weight: bold;">profil</span>.
-      <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-      <td><b><b><a href="chapter_4.1.html#cthf"><b>cthf</b></a></b></b></td>
-      <td>R</td>
-      <td>R</td>
-      <td><span style="font-style: italic;">0.0</span></td>
-      <td>Average heat flux that is prescribed at the top of the plant canopy (in K m/s).</td>
-    </tr>
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#cut_spline_overshoot"><b>cut_spline_overshoot</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.T.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Cut
-off of so-called overshoots, which can occur with
-the upstream-spline-scheme.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#cycle_mg"><b>cycle_mg</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 1</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'w'</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%">Type
-of cycle to
-be used with the multi-grid
-method.&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#damp_level_1d"><b>damp_level_1d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>zu(nz+1)</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Height
-where the damping layer begins in the 1d-model
-(in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#data_output"><span style="font-weight: bold;">data_output</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>C * 10 (100)</td>
-
-
-
- <td><span style="font-style: italic;">100 * &acute; &acute;</span></td>
-
-
-
-
-      <td>Quantities for which 2d cross section and/or 3d volume data
-are to be output.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#data_output_format"><span style="font-weight: bold;">data_output_format</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>C * 10 (10)</td>
-
-
-
- <td><span style="font-style: italic;">'netcdf'</span></td>
-
-
-
-
-      <td>Format of output data.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#data_output_pr"><span style="font-weight: bold;">data_output_pr</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>C * 10 (100)</td>
-
-
-
- <td><span style="font-style: italic;">100 * ' '</span></td>
-
-
-
-
-      <td>Quantities for which vertical profiles (horizontally
-averaged)
-are to be output.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td><a href="chapter_4.3.html#data_output_pr_user"><span style="font-weight: bold;">data_output_pr_user</span></a></td>
-
-
-
-      <td>U</td>
-
-
-
-      <td>C * 10<br>
-
-
-
-(200)</td>
-
-
-
-      <td><span style="font-style: italic;">200 * ' '</span></td>
-
-
-
-      <td>User defined quantities for which horizontally averaged profile data is to be output.</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#data_output_sp"><span style="font-weight: bold;">data_output_sp</span></a></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>C * 10 (10)</td>
-
-
-
- <td><span style="font-style: italic;">10 * ' '</span></td>
-
-
-
-
-      <td>Quantities for which horizontal spectra are to be calculated
-and output.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.3.html#data_output_user"><span style="font-weight: bold;">data_output_user</span></a></td>
-
-
-
-
-      <td>U</td>
-
-
-
- <td>C * 10 (100)</td>
-
-
-
- <td><span style="font-style: italic;">100 * ' '</span></td>
-
-
-
-
-      <td>User defined quantities for which 2d cross section and/or 3d
-volume data are to be output.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#data_output_2d_on_each_pe"><span style="font-weight: bold;">data_output_2d_on_each_pe</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>L</td>
-
-
-
- <td><span style="font-style: italic;">.T.</span></td>
-
-
-
- <td>Output
-2d cross section data by one or
-all processors.&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#density_ratio"><b>density_ratio</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>0.0, 9</i> * <i>9999999.9</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Ratio of the density of the fluid and the density of the
-particles.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#dissipation_1d"><span style="font-weight: bold;">dissipation_1d</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>C * 20</td>
-
-
-
- <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
-
-
-
-
-      <td>Calculation method for the energy dissipation term in the TKE
-equation of the 1d-model.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#disturbance_amplitude"><b>disturbance</b></a>&nbsp;&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#disturbance_amplitude">&nbsp;<b>_amplitude</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.25</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Maximum
-perturbation amplitude of the random
-perturbations
-imposed to the horizontal velocity field (in m/s). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#disturbance_energy_limit"><b>disturbance_energy</b></a>&nbsp;&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#disturbance_energy_limit">&nbsp;<b>_limit</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.01</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB">Upper limit value of the
-perturbation energy of
-the velocity field used as a criterion for imposing random
-perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#disturbance_level_b"><b>disturbance_level_b</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>zu(3) or zu(nz*2/3)</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
-limit of the vertical range for which random perturbations are to be
-imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
-      </font></font> </p>
-
-
-
- <span lang="en-GB"></span></td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#disturbance_level_t"><b>disturbance_level_t</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>zu(nz/3) or zu(nzt-3)</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
-limit of the vertical range for which random perturbations are to be
-imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m). <br>
-
-
-
-
-      </font></font></p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td><a href="chapter_4.2.html#do2d_at_begin"><span style="font-weight: bold;">do2d_at_begin</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>L</td>
-
-
-
- <td><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td>Output
-2d cross section data by one or
-all processors.&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#do3d_at_begin"><span style="font-weight: bold;">do3d_at_begin</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>L</td>
-
-
-
- <td><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td>Output
-of 3d volume data at the beginning
-of a run.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#do3d_compress"><span style="font-weight: bold;">do3d_compress</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>L</td>
-
-
-
- <td><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td>Output
-of data for 3d plots in compressed form.&nbsp;</td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#do3d_comp_prec"><span style="font-weight: bold;">do3d_comp_prec</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>C * 7 (100)</td>
-
-
-
- <td>see
-parameter description</td>
-
-
-
- <td>Significant digits in case
-of compressed data output.&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr><td style="font-weight: bold;"><a href="chapter_4.1.html#dp_external">dp_external</a></td><td>R</td><td>L</td><td style="font-style: italic;">.F.</td><td>External pressure gradient switch.</td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#dp_smooth">dp_smooth</a></td><td>R</td><td>L</td><td style="font-style: italic;">.F.</td><td>Vertically smooth the external pressure gradient using a sinusoidal smoothing function.</td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#dp_level_b">dp_level_b</a></td><td>R</td><td>R</td><td style="font-style: italic;">0.0</td><td><font size="3">Lower
-limit of the vertical range for which the external pressure gradient is applied (</font>in <font size="3">m).</font></td></tr><tr><td style="font-weight: bold;"><a href="chapter_4.1.html#dpdxy">dpdxy</a></td><td>R</td><td>R (2)</td><td style="font-style: italic;">2 * 0.0</td><td>Values of the external pressure gradient applied in x- and y-direction, respectively (in Pa/m).<br></td></tr><tr>
-      <td><a href="chapter_4.1.html#drag_coefficient"><span style="font-weight: bold;">drag_coefficient</span></a></td>
-      <td>I</td>
-      <td>R</td>
-      <td><span style="font-style: italic;">0.0</span></td>
-      <td>Drag coefficient used in the plant canopy model.</td>
-    </tr>
-    <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dt"><b>dt</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I/R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>variable</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p><font face="Thorndale, serif"><font size="3">Time
-step for the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s). <br>
-
-
-
-
-      </font></font></p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td><a href="chapter_4.2.html#dt_averaging_input"><span style="font-weight: bold;">dt_averaging_input</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">0.0</span></td>
-
-
-
- <td>Temporal
-interval of&nbsp;data which are subject to temporal averaging (in
-s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_averaging_input_pr"><b>dt_averaging_input_pr</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><span style="font-style: italic;">value of <a href="chapter_4.2.html#dt_averaging_input">dt_<br>
-
-
-
-
-averaging_<br>
-
-
-
-
-input</a></span></td>
-
-
-
- <td style="vertical-align: middle;" width="57%">Temporal
-interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
-profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;</font></font></td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.2.html#dt_coupling">dt_coupling</a></td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined">9999999.9</td>
-
-
-
-      <td align="undefined" valign="undefined">Temporal interval for the data exchange in case of runs with coupled models (e.g. atmosphere - ocean) (in s).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#dt_data_output"><span style="font-weight: bold;">dt_data_output</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-      <td> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
-at which&nbsp;data (3d volume data (instantaneous or time
-averaged),
-cross sections (instantaneous or time averaged), vertical profiles,
-spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#dt_data_output_av"><span style="font-weight: bold;">dt_data_output_av</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
-interval</font>
-at which time averaged 3d volume data and/or 2d cross section data
-shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_disturb"><b>dt_disturb</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>9999999.9</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which random
-perturbations are to be imposed on the horizontal velocity field
-(</font>in <font face="Thorndale">s). <br>
-
-
-
- </font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#dt_dopr"><span style="font-weight: bold;">dt_dopr</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td><span lang="en-GB"><font face="Thorndale">Temporal interval at
-which data&nbsp;of vertical profiles shall be output (to local
-file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
-or/and </font></span><a href="chapter_3.4.html#PLOT1D_DATA"><span lang="en-GB"><font face="Thorndale">PLOT1D_DATA</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
-      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span></td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#dt_dopr_listing"><span style="font-weight: bold;">dt_dopr_listing</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-      <td> 
-      
-      
-      
-      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
-interval</font> at which data <font face="Thorndale">of
-vertical
-profiles shall be output (output for printouts, local file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
-      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_dopts"><span style="font-weight: bold;">dt_dopts</span></a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">P</td>
-
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td align="undefined" valign="undefined"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
-interval</font> at which time series data of particle quantities
-shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_dosp"><b>dt_dosp</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td style="vertical-align: middle;" width="57%">Temporal
-interval at which&nbsp;spectra data shall be output
-(in s).&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_dots"><b>dt_dots</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>see parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which&nbsp;time series data shall be output (</font>in <font face="Thorndale">s). <br>
-
-
-
- </font></p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_do2d_xy"><b>dt_do2d_xy</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which horizontal cross section data shall be output (</font>in <font face="Thorndale">s). <br>
-
-
-
- </font></p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_do2d_xz"><b>dt_do2d_xz</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which vertical cross section data (xz) shall be output&nbsp;(</font>in
-      <font face="Thorndale">s). <br>
-
-
-
- </font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_do2d_yz"><b>dt_do2d_yz</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which vertical cross section data (yz)&nbsp;shall be
-output&nbsp;(</font>in s<font face="Thorndale">).</font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_do3d"><b>dt_do3d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
-
-
-
-
-output</a></i></td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which 3d volume data shall be output (</font>in <font face="Thorndale">s). <br>
-
-
-
- </font></p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td><b><a href="chapter_4.2.html#dt_dvrp"><b>dt_dvrp</b></a></b></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-      <td>Temporal interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
-s). </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.2.html#dt_max">dt_max</a></td>
-
-
-
-      <td>R</td>
-
-
-
-      <td>R</td>
-
-
-
-      <td><span style="font-style: italic;">20.0</span></td>
-
-
-
-      <td>Maximum
-allowed value of the timestep (in s).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td align="undefined" valign="undefined"><a href="chapter_4.2.html#dt_min_part"><span style="font-weight: bold;">dt_min_part</span></a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">P</td>
-
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">0.0002</span></td>
-
-
-
- <td align="undefined" valign="undefined">Minimum value
-for the particle timestep when SGS velocities are used (in s).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_prel"><b>dt_prel</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>9999999.9</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
-interval at
-which particles are to be released <span lang="en-GB">from
-a particle
-source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;</font></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dt_pr_1d"><b>dt_pr_1d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>9999999.9</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Temporal
-interval of vertical profile output of the
-1D-model
-(in s).&nbsp;</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_restart"><b>dt_restart</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">9999999.9<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><font face="Thorndale"><font face="Thorndale, serif">Temporal
-interval</font> at which a new
-restart run is to be carried out (</font>in <font face="Thorndale">s).</font></td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dt_run_control"><b>dt_run_control</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>60.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font> at
-which run control
-output is to be made (</font>in <font face="Thorndale">s).
-      <br>
-
-
-
- </font></p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dt_run_control_1d"><b>dt_run_control_1d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>60.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Temporal
-interval of runtime control output of the
-1d-model
-(in s).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-      <td><a href="chapter_4.2.html#dt_sort_particles"><span style="font-weight: bold;">dt_sort_particles</span></a></td>
-      <td>P</td>
-      <td>R</td>
-      <td><span style="font-style: italic;">0.0</span></td>
-      <td>Temporal interval for sorting particles (in s).</td>
-    </tr>
-    <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#dt_write_particle_data"><b>dt_write_particle_data</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><i>9999999.9</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Temporal
-interval for output
-of particle data (in s).</td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_directory"><b>dvrp_directory</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 80</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'default'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Name of the directory into which data created by the <span style="font-weight: bold;">dvrp</span>
-software shall be saved. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_file"><b>dvrp_file</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 80</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'default'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Name of the file into which data created by the <span style="font-weight: bold;">dvrp</span> software shall
-be output.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_host"><b>dvrp_host</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 80</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'origin.rvs. <br>
-
-
-
-
-uni- hanover.de'</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Name
-of the computer to which data created by the <span style="font-weight: bold;">dvrp</span> software shall
-be
-transferred. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_output"><b>dvrp_output</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 10</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'rtsp'</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Output
-mode for the <span style="font-weight: bold;">dvrp</span>
-software. </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_password"><b>dvrp_password</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 80</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'********'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">Password
-for the
-computer to which data created
-by the <span style="font-weight: bold;">dvrp</span>
-software is to be
-transferred.</td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_psize"><b>dvrp_psize</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.2</i> * <i>dx</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Diameter
-that the particles is given in visualizations
-with
-the <span style="font-weight: bold;">dvrp</span>
-software (in
-m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#dvrpsize_interval"><span style="font-weight: bold;">dvrpsize_interval</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R(2)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.0</span>, <span style="font-style: italic;">1.0</span></td><td align="undefined" valign="undefined">Interval of values used for determining the particle size displayed in the animation.</td></tr><tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#dvrp_username"><b>dvrp_username</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 80</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p>no default value </p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>User
-name of a valid account on the computer to which
-data
-created by the <span style="font-weight: bold;">dvrp</span>
-software
-is to be
-transferred. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dx"><b>dx</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Horizontal
-grid spacing along the x-direction (in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dy"><b>dy</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Horizontal
-grid spacing along the y-direction (in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dz"><b>dz</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>no default, see parameter description </p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Vertical
-grid spacing (in m).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#dz_max">dz_max</a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-      <td align="undefined" valign="undefined">Allowed
-maximum vertical grid spacing (in m).<br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#dz_stretch_factor"><b>dz_stretch_factor</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.08</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Stretch
-factor for a vertically stretched grid (see <a href="chapter_4.1.html#dz_stretch_level">dz_stretch_level</a>).</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#dz_stretch_level"><b>dz_stretch_level</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>100000.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Height
-level above/below which the grid is to be stretched
-vertically (in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td><a href="chapter_4.1.html#e_init"><span style="font-weight: bold;">e_init</span></a></td>
-
-
-
-      <td>I</td>
-
-
-
-      <td>R</td>
-
-
-
-      <td style="font-style: italic;">0.0</td>
-
-
-
-      <td>Initial TKE in m<sup>2</sup>s<sup>-2</sup>.</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-
-      <td><a href="chapter_4.1.html#e_min"><b>e_min</b></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R</td>
-
-
-
- <td style="font-style: italic;">0.0</td>
-
-
-
-
-      <td>Minimum TKE in m<sup>2</sup>s<sup>-2</sup>.</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#end_time"><b>end_time</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p lang="en-GB"><font face="Thorndale">Simulation
-time of the 3D
-model (</font>in <font face="Thorndale">s)</font><font face="Thorndale">.</font></p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td align="undefined" valign="undefined"><a href="chapter_4.2.html#end_time_prel"><span style="font-weight: bold;">end_time_prel</span></a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">P</td>
-
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">9999999.9</span></td>
-
-
-
-
-      <td align="undefined" valign="undefined">Time of
-the last release of particles (in s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#end_time_1d"><b>end_time_1d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>864000.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Time
-to be simulated for the 1D-model (in s).&nbsp;</p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#fft_method"><b>fft_method</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'system specific'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>FFT-method to be used.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#force_print_header"><b>force_print_header</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="width: 57%; vertical-align: middle;"> 
-      
-      
-      
-      <p>Steering
-of header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>. </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#galilei_transformation"><b>galilei_transformation</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Application
-of a Galilei-transformation to the
-coordinate
-system of the model.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#grid_matching"><b>grid_matching</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 6</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'strict'</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Variable
-to adjust the subdomain sizes in parallel runs.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#groundplate_color"><span style="font-weight: bold;">groundplate_color</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R(3)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.0, 0.6, 0.0</span></td><td align="undefined" valign="undefined">Color of the ground plate</td></tr><tr>
-
-
-
-      <td><b><a href="chapter_4.1.html#humidity"><b>humidity</b></a></b></td>
-
-
-
-      <td>I</td>
-
-
-
-      <td>L</td>
-
-
-
-      <td><span style="font-style: italic;">.F.</span></td>
-
-
-
-      <td>Parameter
-to switch on the prognostic equation for
-specific
-humidity q.</td>
-
-
-
-    </tr>
-
-
-
-    <tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#inflow_damping_height"><span style="font-weight: bold;">inflow_damping_height</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">from precursor run</span></td><td align="undefined" valign="undefined">Height below which the turbulence signal is used for turbulence recycling (in m).</td></tr><tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#inflow_damping_width"><span style="font-weight: bold;">inflow_damping_width</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.1 * <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#inflow_damping_height">inflow_damping</a></span><a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#inflow_damping_height"><span style="font-style: italic;">_height</span></a></td><td align="undefined" valign="undefined">Transition range within which the turbulance signal is damped to zero (in m).</td></tr><tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#inflow_disturbance_begin"><b>inflow_disturbance_begin</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(10,</span><br style="font-style: italic;">
-
-
-
- <span style="font-style: italic;">nx/2 or ny/2)</span></td>
-
-
-
-
-      <td style="vertical-align: middle;">Lower
-limit of the horizontal range for which random perturbations are to be
-imposed on the horizontal velocity field (gridpoints).</td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#inflow_disturbance_end"><b>inflow_disturbance_end</b></a></b></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(100,</span><br style="font-style: italic;">
-
-
-
- <span style="font-style: italic;">3/4*nx or</span><br style="font-style: italic;">
-
-
-
- <span style="font-style: italic;">3/4*ny)</span></td>
-
-
-
- <td style="vertical-align: middle;">Upper
-limit of the horizontal range for which random perturbations are
-to be imposed on the horizontal velocity field (gridpoints).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#initializing_actions"><b>initializing_actions</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 100</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p>no default, see parameter description</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p style="font-style: normal;">Initialization
-actions
-to be carried out. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: top;"><a href="chapter_4.2.html#initial_weighting_factor"><span style="font-weight: bold;">initial_weighting_factor</span></a><br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: top;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: top;">R<br>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: top;">Factor to define
-the real number of initial droplets in a grid cell.</td>
-
-
-
- </tr>
-
-
-
-
-    <tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#isosurface_color"><span style="font-weight: bold;">isosurface_color</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R(3,10)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.9, 0.9, 0.9</span><br style="font-style: italic;"><span style="font-style: italic;">0.8, 0.1, 0.1</span><br style="font-style: italic;"><span style="font-style: italic;">......</span></td><td align="undefined" valign="undefined">Color of the isosurface(s).</td></tr><tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#km_constant"><b>km_constant</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>variable (computed from TKE)</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Constant
-eddy diffusivities are used (laminar
-simulations).&nbsp;</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#km_damp_max"><b>km_damp_max</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">0.5*(dx
-or dy)</span></td>
-
-
-
- <td style="vertical-align: middle;">Maximum
-diffusivity used for filtering the velocity field in the vicinity of
-the outflow (in m<sup>2</sup>/s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-      <td><b><a href="chapter_4.1.html#lad_surface"><b>lad_surface</b></a></b></td>
-      <td>I</td>
-      <td>R</td>
-      <td><span style="font-style: italic;">0.0</span></td>
-      <td>Surface value of the leaf area density (in m<sup>2</sup>/m<sup>3</sup>)</td>
-    </tr>
-    <tr>
-      <td><b><a href="chapter_4.1.html#lad_vertical_gradient"><b>lad_vertical_gradient</b></a></b></td>
-      <td>I</td>
-      <td>R (10)</td>
-      <td><span style="font-style: italic;">10 * 0.0</span></td>
-      <td>Gradient(s) of the leaf area density (in&nbsp;m<sup>2</sup>/m<sup>4</sup>)</td>
-    </tr>
-    <tr>
-      <td><b><b><a href="chapter_4.1.html#lad_vertical_gradient_level"><b>lad_vertical_gradient_level</b></a></b></b></td>
-      <td>I</td>
-      <td>R (10)</td>
-      <td><span style="font-style: italic;">10 * 0.0</span></td>
-      <td>Height level from which on the&nbsp;gradient
-of the leaf area density defined by <a href="chapter_4.1.html#lad_vertical_gradient">lad_vertical_gradient_level</a>
-is effective (in m).</td>
-    </tr>
-    <tr>
-      <td><b><b><b><b><a href="chapter_4.1.html#leaf_surface_concentration"><b>leaf_surface_concentration</b></a></b></b></b></b></td>
-      <td>R</td>
-      <td>R</td>
-      <td><span style="font-style: italic;">0.0</span></td>
-      <td>Concentration of a passive
-scalar at the surface of a leaf (in kg/m<sup>3</sup>).</td>
-    </tr>
-    <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#long_filter_factor"><b>long_filter_factor</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Filter
-factor for the so-called Long-filter.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.1.html#loop_optimization">loop_optimization</a></td>
-
-
-
-      <td>I</td>
-
-
-
-      <td>C * 16</td>
-
-
-
-      <td>see parameter description</td>
-
-
-
-      <td>Method used to optimize loops for solving the prognostic equations .</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#maximum_number_of_particles"><b>maximum_number_</b></a>
-      <br>
-
-
-
- <a href="chapter_4.2.html#maximum_number_of_particles"><b>of_particles</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1000</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Maximum
-number of particles (on a PE). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>maximum_number_</b></a>
-      <br>
-
-
-
- <a href="chapter_4.2.html#maximum_number_of_tailpoints"><b>of_tailpoints</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>100</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Maximum
-number of tailpoints that a particle tail can
-have. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#maximum_tailpoint_age"><b>maximum_tailpoint_</b></a>
-      <br>
-
-
-
- <a href="chapter_4.2.html#maximum_tailpoint_age"><b>age</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>100000.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Maximum
-age that the end point of a particle tail is allowed to have (in s). <br>
-
-
-
-
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><b><a href="chapter_4.2.html#mg_cycles"><b>mg_cycles</b></a></b></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>I</td>
-
-
-
- <td><i>- 1</i></td>
-
-
-
-
-      <td>Number of cycles to be used with the multi-grid scheme.</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td><b><b><a href="chapter_4.2.html#mg_switch_to_pe0_level"><b>mg_switch_to_pe0_level</b></a></b></b></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>I</td>
-
-
-
- <td>see parameter
-description</td>
-
-
-
- <td>Grid
-level at which data shall be gathered on PE0.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#minimum_tailpoint_distance"><b>minimum_tailpoint_</b></a>
-      <br>
-
-
-
- <a href="chapter_4.2.html#minimum_tailpoint_distance"><b>distance</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Minimum
-distance allowed between two adjacent points of
-a
-particle tail (in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.1.html#mixing_length_1d"><span style="font-weight: bold;">mixing_length_1d</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>C * 20</td>
-
-
-
- <td><span style="font-style: italic;">'as_in_3d_model'</span></td>
-
-
-
-
-      <td>Mixing length used in the 1d-model.</td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#mode_dvrp"><b>mode_dvrp</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20 (10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * ' '</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Graphical objects (isosurfaces, slicers, particles)
-which are
-to be created by the <span style="font-weight: bold;">dvrp</span>
-software. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-  <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#momentum_advec"><b>momentum_advec</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 10</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'pw-scheme</i>'</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Advection scheme to be used for the momentum equations.</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#netcdf_precision"><span style="font-weight: bold;">netcdf_precision</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>C * 20 (10)</td>
-
-
-
- <td><span style="font-style: italic;">single preci</span><span style="font-style: italic;">sion for all</span><br style="font-style: italic;">
-
-
-
- <span style="font-style: italic;">output quan</span><span style="font-style: italic;">tities</span></td>
-
-
-
- <td>Defines
-the accuracy of the NetCDF output.<br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td><a href="chapter_4.2.html#netcdf_64bit"><span style="font-weight: bold;">netcdf_64bit</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>L</td>
-
-
-
- <td><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td>All NetCDF files - except those containing 3d
-volume data - will have 64 bit offset format.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.2.html#netcdf_64bit_3d">netcdf_64bit_3d</a></td>
-
-
-
-      <td>R</td>
-
-
-
-      <td>L</td>
-
-
-
-      <td><span style="font-style: italic;">.T.</span></td>
-
-
-
-      <td>NetCDF
-files containing 3d volume data will have 64 bit offset format.</td>
-
-
-
-    </tr>
-
-
-
-    <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#ngsrb"><b>ngsrb</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>2</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Grid
-level at which data shall be gathered on PE0.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#normalizing_region"><b>normalizing_region</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Determines
-the subdomain from which the normalization
-quantities are calculated. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#npex"><b>npex</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>no default, see parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of processors along x-direction of the virtual
-processor
-net. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#npey"><b>npey</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>no default, see parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of processors along y-direction of the virtual
-processor
-net. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#nsor"><b>nsor</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>20</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of iterations to be used with the SOR-scheme. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#nsor_ini"><b>nsor_ini</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>100</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Initial
-number of iterations with the SOR algorithm</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#number_of_particle_groups"><span style="font-weight: bold;">number_of_particle_groups</span></a></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>I</td>
-
-
-
- <td><span style="font-style: italic;">1</span></td>
-
-
-
- <td>Number
-of particle groups to be used.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#nx"><b>nx</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>no default, see parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of grid points in x-direction. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#ny"><b>ny</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>no default, see parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of grid points in y-direction.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#nz"><b>nz</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p>no default, see parameter description</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of grid points in z-direction.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#nz_do3d"><b>nz_do3d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>nz+1</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> Limits
-the output of 3d volume data along the vertical direction (grid point
-index k).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#ocean"><span style="font-weight: bold;">ocean</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">L</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Parameter to switch on&nbsp;ocean runs.</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#omega"><b>omega</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>7.29212E-5</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Angular
-velocity of the rotating system (in rad s<sup>-1</sup>).&nbsp;</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#omega_sor"><b>omega_sor</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.8</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Convergence
-factor to be used with the the SOR-scheme. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#outflow_damping_width"><b>outflow_damping_width</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">MIN(20,
-nx/2</span> or <span style="font-style: italic;">ny/2)</span></td>
-
-
-
-
-      <td style="vertical-align: middle;">Width of
-the damping range in the vicinity of the outflow (gridpoints).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#overshoot_limit_e"><b>overshoot_limit_e</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Allowed
-limit for the overshooting of subgrid-scale TKE
-in
-case that the upstream-spline scheme is switched on (in m<sup>2</sup>/s<sup>2</sup>).</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#overshoot_limit_pt"><b>overshoot_limit_pt</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Allowed
-limit for the overshooting of potential
-temperature in
-case that the upstream-spline scheme is switched on (in K). <br>
-
-
-
-
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#overshoot_limit_u"><b>overshoot_limit_u</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Allowed
-limit for the
-overshooting of
-the u-component of velocity in case that the upstream-spline scheme is
-switched on (in m/s).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#overshoot_limit_v"><b>overshoot_limit_v</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Allowed
-limit for the overshooting of the v-component of
-velocity in case that the upstream-spline scheme is switched on
-(in m/s). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#overshoot_limit_w"><b>overshoot_limit_w</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Allowed
-limit for the overshooting of the w-component of
-velocity in case that the upstream-spline scheme is switched on
-(in m/s). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.2.html#particles_per_point"><span style="font-weight: bold;">particles_per_point</span></a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">P</td>
-
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">1</span></td>
-
-
-
- <td align="undefined" valign="undefined">Number of
-particles to be started per point.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: top;"><b><a href="chapter_4.2.html#particle_advection_start"><b>particle_advection_start</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: top;">P<br>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: top;">R<br>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: top;">Time of the first
-release of
-particles (in s).</td>
-
-
-
- </tr>
-
-
-
- <tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#particle_color"><span style="font-weight: bold;">particle_color</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">C*10</td><td align="undefined" valign="undefined"><span style="font-style: italic;">'none'</span></td><td align="undefined" valign="undefined">Parameter, which allows to bind the displayed particle color to certain flow quantities.</td></tr><tr><td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.2.html#particle_dvrpsize">particle_dvrpsize</a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">C*10</td><td align="undefined" valign="undefined"><span style="font-style: italic;">'none'</span></td><td align="undefined" valign="undefined">Parameter, which allows to bind the displayed particle size to certain flow quantities.</td></tr><tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#particle_maximum_age"><b>particle_maximum_age</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>9999999.9</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Maximum
-allowed age of particles (in s). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#passive_scalar"><b>passive_scalar</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to switch on the prognostic equation for a
-passive
-scalar. </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-      <td><b><a href="chapter_4.1.html#pch_index"><b>pch_index</b></a></b></td>
-      <td>I</td>
-      <td>I</td>
-      <td><code></code><i>0 </i></td>
-      <td>Grid point index (scalar) of the upper boundary of the plant canopy layer</td>
-    </tr>
-    <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#pdx"><b>pdx</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * dx</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Distance
-along x between particles within a particle
-source
-(in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#pdy"><b>pdy</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * dy</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Distance
-along y between
-particles within a
-particle source (in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#pdz"><b>pdz</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * ( zu(2) - zu(1) )</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Distance along z between
-particles within a particle source
-(in m).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#phi"><b>phi</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>55.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Geographical
-latitude (in degrees). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-      <td><b><a href="chapter_4.1.html#plant_canopy"><b>plant_canopy</b></a></b></td>
-      <td>I</td>
-      <td>L</td>
-      <td><i>.F.</i></td>
-      <td>Parameter to switch on the plant canopy model</td>
-    </tr>
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#plot_spectra_level"><b>plot_spectra_level</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I
-(100)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>No level</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Vertical level(s) for which horizontal spectra are to be
-plotted (in gridpoints). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#prandtl_layer"><b>prandtl_layer</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.T.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to switch on a Prandtl layer. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.2.html#prandtl_number"><b>prandtl_number</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Ratio
-of the eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).
-      <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#precipitation"><b>precipitation</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">L<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td style="vertical-align: middle;">Parameter to
-switch on the
-precipitation scheme.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.2.html#precipitation_amount_interval">precipitation_amount_<br>
-
-
-
-interval</a></td>
-
-
-
-      <td>R</td>
-
-
-
-      <td>R</td>
-
-
-
-      <td><i>value
-of &nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>
-
-
-
-
-xy</a></i></td>
-
-
-
-      <td><font face="Thorndale"><font face="Thorndale, serif">Temporal
-interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;</font></td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#profile_columns"><b>profile_columns</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>3</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of coordinate systems to be plotted<span style="font-weight: bold;"></span>
-in one row by <span style="font-weight: bold;">profil</span>.
-      <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#profile_rows"><b>profile_rows</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>2</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of rows of coordinate systems to be plotted on
-one page
-by <span style="font-weight: bold;">profil</span>. <br>
-
-
-
-
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#psb"><b>psb</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * zu(nz/2)</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Bottom edge of a particle
-source (in m).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#psl"><b>psl</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * 0.0</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Left edge of a particle source
-(in m). </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#psn"><b>psn</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * ( ny * dy )</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Rear (&ldquo;north&rdquo;) edge of a particle
-source (in m).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#psolver"><b>psolver</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 10</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'poisfft'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Scheme to be used to solve the Poisson equation for the
-perturbation pressure. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#psr"><b>psr</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * ( nx * dx )</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Right edge of a particle source (in m).</p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#pss"><b>pss</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * 0.0</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Front (&ldquo;south&rdquo;) edge of a particle
-source (in m).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#pst"><b>pst</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * zu(nz/2)</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Top edge of a particle source (in m).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.1.html#pt_reference">pt_reference</a></td>
-
-
-
-      <td>I</td>
-
-
-
-      <td>R</td>
-
-
-
-      <td><span style="font-style: italic;">use horizontal average as
-reference</span></td>
-
-
-
-      <td>Reference temperature to be
-used in all buoyancy terms (in K).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#pt_surface"><b>pt_surface</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>300.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Surface
-potential temperature (in K). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#pt_surface_initial_change"><b>pt_surface_initial</b></a>&nbsp;&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.1.html#pt_surface_initial_change">&nbsp;<b>_change</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">Change
-in surface
-temperature to be made at the
-beginning of
-the 3d run
-(in K).&nbsp;</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#pt_vertical_gradient"><b>pt_vertical_gradient</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * 0.0</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Temperature gradient(s) of the initial temperature
-profile (in
-K
-/ 100 m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#pt_vertical_gradient_level"><b>pt_vertical_gradient</b></a>&nbsp;&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.1.html#pt_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Height level from which on the temperature gradient
-defined by <a href="chapter_4.1.html#pt_vertical_gradient">pt_vertical_gradient</a>
-is effective (in m).&nbsp;</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#q_surface"><b>q_surface</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Surface
-specific humidity / total water content (kg/kg). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#q_surface_initial_change"><b>q_surface_initial</b></a>
-      <br>
-
-
-
- <a href="chapter_4.1.html#q_surface_initial_change">&nbsp;<b>_change</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Change
-in surface specific humidity / total water
-content to
-be made at the beginning
-of the 3d run (kg/kg). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#q_vertical_gradient"><b>q_vertical_gradient</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * 0.0</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="width: 57%; vertical-align: middle;">
-      
-      
-      
-      <p>Humidity gradient(s) of the initial humidity profile
-(in 1/100 m). </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#q_vertical_gradient_level"><b>q_vertical_gradient</b></a>
-      <br>
-
-
-
- <a href="chapter_4.1.html#q_vertical_gradient_level">&nbsp;<b>_level</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 *</i>&nbsp; <i>0.0</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Height level from which on the humidity gradient defined
-by <a href="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</a>
-is effective (in m).&nbsp;</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#radiation"><b>radiation</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to switch on longwave radiation cooling at
-cloud-tops. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td><a href="chapter_4.2.html#radius"><span style="font-weight: bold;">radius</span></a></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>R (10)</td>
-
-
-
- <td><i>0.0,
-9</i>*<br>
-
-
-
- <i>9999999.9</i></td>
-
-
-
- <td>Particle
-radius (in m).</td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#random_generator"><b>random_generator</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'numerical recipes'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Random number generator to be used for creating
-uniformly
-distributed random numbers. </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#random_heatflux"><b>random_heatflux</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to impose random perturbations on the internal two-dimensional near
-surface heat flux field <span style="font-style: italic;">shf</span>.
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#random_start_position"><b>random_start_position</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
-particles is
-varied randomly within certain limits.&nbsp;</span></p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#rayleigh_damping_factor"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#rayleigh_damping_factor">&nbsp;<b>_factor</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><span style="font-style: italic;">0.0</span>
-and/or <span style="font-style: italic;">0.01</span>
-(see parameter description)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Factor
-for Rayleigh damping.&nbsp;</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#rayleigh_damping_height"><b>rayleigh_damping</b></a>&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#rayleigh_damping_height">&nbsp;<b>_height</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle; font-style: italic;" width="16%"> 
-      
-      
-      
-      <p>2/3 * zu(nz)</p>
-
-
-
- </td>
-
-
-
- <td style="width: 57%; text-align: left; vertical-align: middle;">
-      
-      
-      
-      <p>Height where the Rayleigh damping starts (in
-m).&nbsp; </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#read_particles_from_restartfile"><b>read_particles_from_</b></a>
-      <br>
-
-
-
- <a href="chapter_4.2.html#read_particles_from_restartfile"><b>restartfile</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.T.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Read
-particle data from the previous run. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#recycling_width"><span style="font-weight: bold;">recycling_width</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">R</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.1 * <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#nx">nx</a> * <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#dx">dx</a></span></td><td align="undefined" valign="undefined">Distance of the recycling plane from the inflow boundary (in m).<br></td></tr><tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.3.html#region"><b>region</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>U</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 40 (0:9)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p>&nbsp;</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Name(s) of the subdomain(s) defined by the user.</p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#residual_limit"><b>residual_limit</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0E-6</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Largest
-residual permitted for the multi-grid scheme (in
-s<sup>-2</sup>m<sup>-3</sup>). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.2.html#restart_time"><b>restart_time</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">9999999.9<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">Simulated time
-after which a
-restart run is to be carried out
-(in s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#rif_max"><b>rif_max</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Upper
-limit of the flux-Richardson number. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#rif_min"><b>rif_min</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>- 5.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Lower
-limit of the flux-Richardson number. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#roughness_length"><b>roughness_length</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.1</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Roughness
-length (in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_surface"><span style="font-weight: bold;">sa_surface</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">35.0</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Surface salinity (in psu).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_vertical_gradient"><span style="font-weight: bold;">sa_vertical_gradient</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R(10)</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Salinity gradient(s) of the initial salinity profile (in psu
-/ 100 m).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#sa_vertical_gradient_level"><span style="font-weight: bold;">sa_vertical_gradient_level</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R(10)</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Height level from which on the salinity gradient defined by <a href="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</a>
-is effective (in m).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#scalar_advec"><b>scalar_advec</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 10</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'pw-scheme'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Advection scheme to be used for the scalar quantities. <br>
-
-
-
-
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-      <td><b><b><a href="../../../../../DEVELOPER_VERSION/chapter_4.1.html#scalar_exchange_coefficient"><b>scalar_exchange_coefficient</b></a></b></b></td>
-      <td>R</td>
-      <td>R</td>
-      <td><span style="font-style: italic;">0.0</span></td>
-      <td>Scalar exchange coefficient for a leaf (dimensionless).</td>
-    </tr>
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#section_xy"><span style="font-weight: bold;">section_xy</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>I (100)</td>
-
-
-
- <td><span style="font-style: italic;">no section</span></td>
-
-
-
-
-      <td><font face="Thorndale">Position
-of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
-sections (grid point index k).&nbsp;</font></td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#section_xz"><span style="font-weight: bold;">section_xz</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>I (100)</td>
-
-
-
- <td><span style="font-style: italic;">no section</span></td>
-
-
-
-
-      <td><font face="Thorndale">Position
-of&nbsp;cross section(s) for&nbsp;output of 2d (xz) vertical
-cross sections (grid point index j).&nbsp;</font></td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#section_yz"><span style="font-weight: bold;">section_yz</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>I (100)</td>
-
-
-
- <td><span style="font-style: italic;">no section</span></td>
-
-
-
-
-      <td><font face="Thorndale">Position
-of&nbsp;cross section(s) for&nbsp;output of 2d (yz) vertical
-cross sections (grid point index i).&nbsp;</font></td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_particles_for_tail"><span style="font-weight: bold;">skip_particles_for_tail</span></a></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>I</td>
-
-
-
- <td><span style="font-style: italic;">100</span></td>
-
-
-
- <td>Limit
-the number of particle tails.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_data_output"><span style="font-weight: bold;">skip_time_data_output</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">0.0</span></td>
-
-
-
- <td>No
-data output before this interval has passed (in s).</td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_data_output_av"><span style="font-weight: bold;">skip_time_data_output_av</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-temporally averaged 2d/3d data before this interval has passed (in s).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_dopr"><span style="font-weight: bold;">skip_time_dopr</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-vertical profile data before this interval has passed (in s).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_dosp"><span style="font-weight: bold;">skip_time_dosp</span></a></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-spectra data before this interval has passed (in s).</td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_do2d_xy"><span style="font-weight: bold;">skip_time_do2d_xy</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-instantaneous horizontal cross section data before this interval has
-passed (in s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_do2d_xz"><span style="font-weight: bold;">skip_time_do2d_xz</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-instantaneous vertical (xz) cross section data before this interval has
-passed (in s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_do2d_yz"><span style="font-weight: bold;">skip_time_do2d_yz</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-instantaneous vertical (yz) cross section data before this interval has
-passed (in s).<br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#skip_time_do3d"><span style="font-weight: bold;">skip_time_do3d</span></a></td>
-
-
-
-
-      <td>R</td>
-
-
-
- <td>R</td>
-
-
-
- <td><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>
-
-
-
-
-data_output</a></span></td>
-
-
-
- <td>No output of
-instantaneous 3d volume data before this interval has passed (in s).</td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="file:///home/raasch/public_html/PALM_group/doc/app/chapter_4.2.html#spectra_direction"><b>slicer_range_limits_dvrp</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">P<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R(2,10)<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><span style="font-style: italic;">10
-* (-1,1)</span></td>
-
-
-
- <td style="vertical-align: middle;">Ranges
-of values to which a color table has to be mapped (units of the
-respective quantity).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#spectra_direction"><b>spectra_direction</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 2 (10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>10 * ' '</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Direction(s) along which spectra are to be calculated. <br>
-
-
-
-
-      </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#statistic_regions"><b>statistic_regions</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>I</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Number
-of additional user-defined subdomains for which
-statistical analysis
-and corresponding output (profiles, time series) shall be made.</p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#superelevation"><b>superelevation</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Superelevation
-factor for the vertical coordinate. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#superelevation_x"><b>superelevation_x</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Superelevation
-factor for the horizontal (x) coordinate. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#superelevation_y"><b>superelevation_y</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Superelevation
-factor for the
-horizontal (y) coordinate. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#surface_heatflux"><b>surface_heatflux</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><span style="font-style: italic;">no prescribed
-heatflux</span></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Kinematic
-sensible heat flux at the bottom surface (in K m/s).</p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#surface_pressure"><b>surface_pressure</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>1013.25</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Atmospheric
-pressure at the surface (in hPa)</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#surface_scalarflux"><b>surface_scalarflux</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><i>0.0</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Scalar flux at
-the surface
-(in kg/(m<sup>2</sup> s)). <br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#surface_waterflux"><b>surface_waterflux</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Kinematic
-water flux near the surface (in m/s). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><a href="chapter_4.1.html#s_surface"><b>s_surface</b></a></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><i>0.0</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Surface value of
-the passive
-scalar (in kg/m<sup>3</sup>). <br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_surface_initial_change"><b>s_surface_initial_change</b></a></b></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><i>0.0</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Change in
-surface scalar
-concentration to be made at the
-beginning of the 3d run (in kg/m<sup>3</sup>). <br>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"><b><b><a href="chapter_4.1.html#s_vertical_gradient"><b>s_vertical_gradient</b></a></b></b></td>
-
-
-
-
-      <td style="vertical-align: middle;">I<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;">R(10)<br>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;"><i>10 * 0</i><i>.0</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Scalar
-concentration
-gradient(s) of the initial scalar
-concentration profile (in kg/m<sup>3 </sup>/
-100 m). <br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#s_vertical_gradient_level"><span style="font-weight: bold;">s_vertical_gradient_level</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R(10)</td>
-
-
-
- <td><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-      <td>Height level from which on the scalar gradient defined by <a href="chapter_4.1.html#s_vertical_gradient">s_vertical_gradient</a>
-is effective (in m).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#termination_time_needed"><b>termination_time</b></a>&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#termination_time_needed">&nbsp;<b>_needed</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>35.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>CPU
-time needed for terminal actions at the end of a run
-in
-batch mode (in s).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#threshold"><b>threshold</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>P</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R
-(10)</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
-
-      <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Threshold
-value for which an isosurface is to be created
-by
-the <span style="font-weight: bold;">dvrp</span>
-software. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#timestep_scheme"><b>timestep_scheme</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>C
-* 20</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"> 
-      
-      
-      
-      <p><i>'runge-kutta-3'</i></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="57%">
-      
-      
-      
-      <p>Time step scheme to be used for integration of the prognostic
-variables. <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td><a href="chapter_4.1.html#topography"><span style="font-weight: bold;">topography</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>C * 40</td>
-
-
-
- <td><span style="font-style: italic;">'flat'</span></td>
-
-
-
- <td>Topography
-mode.</td>
-
-
-
- </tr>
-
-
-
- <tr><td align="undefined" valign="undefined"><a href="chapter_4.2.html#topography_color"><span style="font-weight: bold;">topography_color</span></a></td><td align="undefined" valign="undefined">P</td><td align="undefined" valign="undefined">R(3)</td><td align="undefined" valign="undefined"><span style="font-style: italic;">0.8, 0.7, 0.6</span></td><td align="undefined" valign="undefined">Color of the topography.</td></tr><tr><td style="vertical-align: top;"><a style="font-weight: bold;" href="chapter_4.1.html#topography_grid_convention">topography_grid_convention</a></td><td style="vertical-align: top;">I</td><td style="vertical-align: top;">C * 11</td><td><span style="font-style: italic;">default depends on value of <a href="chapter_4.1.html#topography">topography</a>; see text for details</span><span style="font-style: italic;"></span></td><td style="vertical-align: top;">Convention for defining the&nbsp;topography grid.</td></tr><tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.1.html#top_heatflux">top_heatflux</a></td>
-
-
-
-      <td>I</td>
-
-
-
-      <td>R</td>
-
-
-
-      <td><span style="font-style: italic;">no prescribed heatflux</span></td>
-
-
-
-      <td>Kinematic
-sensible heat flux at the top surface (in K m/s).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#top_momentumflux_u"><span style="font-weight: bold;">top_momentumflux_u</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed momentumflux</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Momentum flux along x at the top boundary (in m2/s2).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a style="font-weight: bold;" href="chapter_4.1.html#top_momentumflux_v">top_momentumflux_v</a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed momentumflux</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Momentum flux along y at the top boundary (in m2/s2).</td>
-
-
-
-    </tr>
-
-
-
-    <tr>
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#top_salinityflux"><span style="font-weight: bold;">top_salinityflux</span></a></td>
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-      <td align="undefined" valign="undefined">R</td>
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">no prescribed</span><br style="font-style: italic;">
-
-
-
-      <span style="font-style: italic;">salinityflux</span></td>
-
-
-
-      <td align="undefined" valign="undefined">Kinematic
-salinity flux at the top boundary, i.e. the sea surface (in psu m/s).</td>
-
-
-
-    </tr>
-
-
-
-    <tr><td align="undefined" valign="undefined"><a href="chapter_4.1.html#turbulent_inflow"><span style="font-weight: bold;">turbulent_inflow</span></a></td><td align="undefined" valign="undefined">I</td><td align="undefined" valign="undefined">L</td><td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td><td align="undefined" valign="undefined">Generates a turbulent inflow at side boundaries using a turbulence recycling method.</td></tr><tr><td><a href="chapter_4.1.html#u_bulk"><span style="font-weight: bold;">u_bulk</span></a></td><td>I</td><td>R</td><td><span style="font-style: italic;">0.0</span></td><td>u-component of the predefined bulk velocity (in m/s).</td></tr><tr>
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#ug_surface"><b>ug_surface</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>u-component
-of the geostrophic wind at the surface (in m/s). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#ug_vertical_gradient"><span style="font-weight: bold;">ug_vertical_gradient</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R(10)</td>
-
-
-
- <td><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-      <td>Gradient(s) of the initial
-profile of the&nbsp; u-component of the geostrophic wind (in
-1/100s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#ug_vertical_gradient_level"><span style="font-weight: bold;">ug_vertical_gradient_level</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R(10)</td>
-
-
-
- <td><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-      <td>Height level from which on the
-gradient defined by <a href="chapter_4.1.html#ug_vertical_gradient">ug_vertical_gradient</a>
-is effective (in m).<br>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#ups_limit_e"><b>ups_limit_e</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Subgrid-scale
-turbulent kinetic energy difference used
-as
-criterion for applying the upstream scheme when upstream-spline
-advection is switched on (in m<sup>2</sup>/s<sup>2</sup>).
-&nbsp;</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#ups_limit_pt"><b>ups_limit_pt</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Temperature
-difference used as criterion for
-applying&nbsp;
-the upstream scheme when upstream-spline advection&nbsp; is
-switched on
-(in K). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#ups_limit_u"><b>ups_limit_u</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Velocity
-difference (u-component) used as criterion for
-applying the upstream scheme
-when upstream-spline advection is switched on (in m/s). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#ups_limit_v"><b>ups_limit_v</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Velocity
-difference (v-component) used as criterion for
-applying the upstream scheme
-when upstream-spline advection is switched on (in m/s). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#ups_limit_w"><b>ups_limit_w</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Velocity
-difference (w-component) used as criterion for
-applying the upstream scheme
-when upstream-spline advection is switched on (in m/s). <br>
-
-
-
- </p>
-
-
-
-
-      </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.2.html#use_particle_tails"><span style="font-weight: bold;">use_particle_tails</span></a></td>
-
-
-
-
-      <td>P</td>
-
-
-
- <td>L</td>
-
-
-
- <td style="font-style: italic;">.F.</td>
-
-
-
-
-      <td>Give particles a tail.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#use_prior_plot1d_parameters"><b>use_prior_plot1d</b></a>&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#use_prior_plot1d_parameters">&nbsp;<b>_parameters</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="width: 57%; text-align: left; vertical-align: middle;">
-      
-      
-      
-      <p>Additional plot of vertical profile data with <span style="font-weight: bold;">profil</span> from
-preceding runs of the
-job chain.&nbsp; </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td align="undefined" valign="undefined"><a href="chapter_4.2.html#use_sgs_for_particles"><span style="font-weight: bold;">use_sgs_for_particles</span></a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">P</td>
-
-
-
-
-      <td align="undefined" valign="undefined">L</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td align="undefined" valign="undefined">Use
-subgrid-scale velocities for particle advection.</td>
-
-
-
- </tr>
-
-
-
-
-    <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%">
-      
-      
-      
-      <p><a href="chapter_4.1.html#use_surface_fluxes"><b>use_surface_fluxes</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.F.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to steer the treatment of the subgrid-scale
-vertical
-fluxes within the diffusion terms at k=1 (bottom boundary).</p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
-      <td><a style="font-weight: bold;" href="chapter_4.1.html#use_top_fluxes">use_top_fluxes</a></td>
-
-
-
-      <td>I</td>
-
-
-
-      <td>L</td>
-
-
-
-      <td><span style="font-style: italic;">.F.</span></td>
-
-
-
-      <td>Parameter
-to steer the treatment of the subgrid-scale
-vertical
-fluxes within the diffusion terms at k=nz (top boundary).</td>
-
-
-
-    </tr>
-
-
-
-    <tr valign="top">
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#use_ug_for_galilei_tr"><b>use_ug_for_galilei_tr</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.T.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Switch
-to determine the translation velocity in case
-that a
-Galilean transformation is used.</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
-
-      <td align="undefined" valign="undefined"><a href="chapter_4.1.html#use_upstream_for_tke"><span style="font-weight: bold;">use_upstream_for_tke</span></a></td>
-
-
-
-
-      <td align="undefined" valign="undefined">I</td>
-
-
-
-
-      <td align="undefined" valign="undefined">L</td>
-
-
-
-
-      <td align="undefined" valign="undefined"><span style="font-style: italic;">.F.</span></td>
-
-
-
- <td align="undefined" valign="undefined">Parameter to
-choose the advection/timestep scheme to be used for the subgrid-scale
-TKE.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#vertical_particle_advection"><b>vertical_particle_advection</b></a><br>
-
-
-
-
-      </p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;">P<br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;">L<br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;"><i>.T.</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Switch on/off
-vertical
-particle transport.</td>
-
-
-
- </tr>
-
-
-
- <tr><td><a href="chapter_4.1.html#v_bulk"><span style="font-weight: bold;">v_bulk</span></a></td><td>I</td><td>R</td><td><span style="font-style: italic;">0.0</span></td><td>v-component of the predefined bulk velocity (in m/s).</td></tr><tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#vg_surface"><b>vg_surface</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>0.0</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>v-component
-of the geostrophic wind at the surface (in m/s).</p>
-
-
-
- </td>
-
-
-
-
-    </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#vg_vertical_gradient"><span style="font-weight: bold;">vg_vertical_gradient</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R(10)</td>
-
-
-
- <td><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-      <td>Gradient(s) of the initial
-profile of the&nbsp; v-component of the geostrophic wind (in
-1/100s).</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#vg_vertical_gradient_level"><span style="font-weight: bold;">vg_vertical_gradient_level</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R(10)</td>
-
-
-
- <td><span style="font-style: italic;">10 * 0.0</span></td>
-
-
-
-
-      <td>Height level from which on the
-gradient defined by <a href="chapter_4.1.html#vg_vertical_gradient">vg_vertical_gradient</a>
-is effective (in m).</td>
-
-
-
- </tr>
-
-
-
- <tr valign="top">
-
-
-
-
-      <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.1.html#wall_adjustment"><b>wall_adjustment</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>I</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>L</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>.T.</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Parameter
-to restrict the mixing length in the vicinity
-of the
-bottom
-boundary  (and near vertical walls of a non-flat <a href="chapter_4.1.html#topography">topography</a>).</p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td><a href="chapter_4.1.html#wall_heatflux"><span style="font-weight: bold;">wall_heatflux</span></a></td>
-
-
-
-
-      <td>I</td>
-
-
-
- <td>R(5)</td>
-
-
-
- <td><span style="font-style: italic;">5 * 0.0</span></td>
-
-
-
- <td>Prescribed
-kinematic sensible heat flux in K m/s&nbsp;at
-the five topography faces.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#write_particle_statistics"><b>write_particle_</b></a>
-      <br>
-
-
-
- <a href="chapter_4.2.html#write_particle_statistics"><b>statistics</b></a>
-      </p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;">P<br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;">L<br>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;"><i>.F.</i></td>
-
-
-
-
-      <td style="vertical-align: middle;">Switch on/off
-output of
-particle informations.</td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#z_max_do1d"><b>z_max_do1d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%"><i>zu(nzt+1)
-(model top)</i></td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Height level up to which horizontally
-averaged profiles
-are to
-be
-plotted with <span style="font-weight: bold;">profil</span>
-(in
-m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#z_max_do1d_normalized"><b>z_max_do1d</b></a>&nbsp;&nbsp;
-      <br>
-
-
-
- <a href="chapter_4.2.html#z_max_do1d_normalized">&nbsp;<b>_normalized</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>determined by plot <br>
-
-
-
-
-data</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Normalized
-height level up to which horizontally
-averaged
-profiles are to be plotted with <span style="font-weight: bold;">profil</span>.
-      <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- <tr>
-
-
-
- <td style="vertical-align: middle;" width="15%"> 
-      
-      
-      
-      <p><a href="chapter_4.2.html#z_max_do2d"><b>z_max_do2d</b></a></p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="5%">
-      
-      
-      
-      <p>R</p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="7%"> 
-      
-      
-      
-      <p>R</p>
-
-
-
-
-      </td>
-
-
-
- <td style="vertical-align: middle;" width="16%">
-      
-      
-      
-      <p><i>zu(nz)</i></p>
-
-
-
- </td>
-
-
-
- <td style="vertical-align: middle;" width="57%"> 
-      
-      
-      
-      <p>Height
-level up to which 2d cross sections are to be
-plotted
-with <span style="font-weight: bold;">iso2d</span>
-(in m). <br>
-
-
-
- </p>
-
-
-
- </td>
-
-
-
- </tr>
-
-
-
- 
-  
-  
-  
-  </tbody>
-</table>
-
-
-
-<hr>
-<p><br>
-
-
-
-<font color="#000080"><a href="chapter_4.5.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_5.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></p>
-
-
-
-
-<p>&nbsp;<i>Last change:&nbsp;&nbsp;</i>
-$Id$ </p>
-
-
-
-
-<p><br>
-
-
-
-<br>
-
-
-
-
-<br>
-
-
-
-</p>
-
-
-
-
-</body></html>
+parameters (U) are alphabetically listed in the following table. <BR>&nbsp;
+</P>
+<P ALIGN=CENTER STYLE="margin-bottom: 0in"><BR>
+</P>
+<TABLE WIDTH=1160 BORDER=1 CELLPADDING=2 CELLSPACING=3>
+	<COL WIDTH=164>
+	<COL WIDTH=47>
+	<COL WIDTH=75>
+	<COL WIDTH=183>
+	<COL WIDTH=651>
+	<TR>
+		<TD WIDTH=164>
+			<H3><B>Parameter name</B></H3>
+		</TD>
+		<TD WIDTH=47>
+			<H3>Class</H3>
+		</TD>
+		<TD WIDTH=75>
+			<H3>Type</H3>
+		</TD>
+		<TD WIDTH=183>
+			<H3>Default<BR>value</H3>
+		</TD>
+		<TD WIDTH=651>
+			<H3>Explanation</H3>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#adjust_mixing_length"><B>adjust_mixing_length</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Near-surface adjustment of the mixing length to the
+			Prandtl-layer law.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#alpha_surface"><B>alpha_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Inclination of the model domain with respect to the horizontal
+			(in degrees).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#averaging_interval"><B>averaging_interval</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Averaging interval for all&nbsp;output of temporally averaged
+			data (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#averaging_interval_pr"><B>averaging_interval_pr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#averaging_interval">averaging_<BR>interval</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P ALIGN=LEFT>Averaging interval for vertical profiles&nbsp;output
+			to local file <FONT COLOR="#000000"><A HREF="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</A>
+			</FONT>and/or&nbsp; <A HREF="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</A>
+			(in s).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#averaging_interval_sp"><B>averaging_interval_sp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#averaging_interval">averaging_<BR>interval</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Averaging interval for spectra output to local file
+			<FONT COLOR="#000000"><A HREF="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</A>
+			</FONT>and/or&nbsp; <A HREF="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</A>
+			/ &nbsp;&nbsp; <A HREF="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</A>
+			(in s).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_e_b"><B>bc_e_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition of the TKE. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_lr"><B>bc_lr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>ÂŽcyclicÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Boundary condition along x (for all quantities).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_ns"><B>bc_ns</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'cyclic'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Boundary condition along y (for all quantities).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_p_b"><B>bc_p_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition of the perturbation pressure. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_p_t"><B>bc_p_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition of the perturbation pressure. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#bc_par_b"><B>bc_par_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C*15</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>ÂŽreflectÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition for particle transport. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#bc_par_lr"><B>bc_par_lr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C*15</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>ÂŽcyclicÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Lateral boundary condition (x-direction) for particle
+			transport.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#bc_par_ns"><B>bc_par_ns</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C*15</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>ÂŽcyclicÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Lateral boundary condition (y-direction) for particle
+			transport.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#bc_par_t"><B>bc_par_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C*15</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>ÂŽabsorbÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition for particle transport.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_pt_b"><B>bc_pt_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition of the potential temperature. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pc_pt_t"><B>bc_pt_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'initial_gradient'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition of the potential temperature. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_q_b"><B>bc_q_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition of the specific humidity / total
+			water content. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_q_t"><B>bc_q_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition of the specific humidity / total water
+			content. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_s_b"><B>bc_s_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition of the scalar concentration. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_s_t"><B>bc_s_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>ÂŽneumannÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition of the scalar concentration. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_sa_t"><B>bc_sa_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'neumann'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition of the salinity.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_uv_b"><B>bc_uv_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom boundary condition of the horizontal wind components u
+			and v.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bc_uv_t"><B>bc_uv_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'dirichlet'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top boundary condition of the horizontal velocity components u
+			and v.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#bottom_salinityflux"><B>bottom_salinityflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Kinematic salinity flux near the surface (in psu m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#building_height"><B>building_height</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height of a single building in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#building_length_x"><B>building_length_x</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Width of a single building in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#building_length_y"><B>building_length_y</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Depth of a single building in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#building_wall_left"><B>building_wall_left</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>building centered in x-direction</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>x-coordinate of the left building wall in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#building_wall_south"><B>building_wall_south</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>building centered in y-direction</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>y-coordinate of the South building wall&nbsp;in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#call_psolver_at_all_substeps"><B>call_psolver_at_all_substeps</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T..</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Switch to steer the call of the pressure solver.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#fcl_factor"><B>canopy_mode</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'block'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Canopy mode</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#canyon_height"><B>canyon_height</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>50.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Street canyon height in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#canyon_width_x"><B>canyon_width_x</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Street canyon width in x-direction in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#canyon_width_y"><B>canyon_width_y</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Street canyon width in y-direction in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#canyon_wall_left"><B>canyon_wall_left</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>canyon centered in x-direction</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>x-coordinate of the left canyon wall&nbsp;in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#canyon_wall_south"><B>canyon_wall_south</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>canyon centered in y-direction</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>y-coordinate of the South canyon wall&nbsp;in m.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#fcl_factor"><B>cfl_factor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.1, 0.8&nbsp;or 0.9 </I>(see parameter description)</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Time step limiting factor.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#clip_dvrp_l"><B>clip_dvrp_l</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Left boundary of the displayed domain (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#clip_dvrp_n"><B>clip_dvrp_n</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>(ny+1)*dy</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>North boundary of the displayed domain (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#clip_dvrp_r"><B>clip_dvrp_r</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P><I>R</I></P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>(nx+1)*dx</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Right boundary of the displayed domain (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#clip_dvrp_s"><B>clip_dvrp_s</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>0.0</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>South boundary of the displayed domain (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#cloud_droplets"><B>cloud_droplets</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on usage of cloud droplets.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#cloud_physics"><B>cloud_physics</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on the condensation scheme. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#cluster_size"><B>cluster_size</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Vertex cluster size for polygon reduction of topography.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#color_interval"><B>color_interval</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(2)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I>, <I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Interval of values used for determining the particle color
+			displayed in the animation.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#comp_spectra_level"><B>comp_spectra_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no level</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Vertical level for which horizontal spectra are to be
+			calculated and output (gridpoints).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#conserve_volume_flow"><B>conserve_volume_flow</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Conservation of volume flow in x- and y-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#conserve_volume_flow_mode"><B>conserve_volume_flow_mode</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 16</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'default'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Modus of volume flow conservation.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#coupling_start_time"><B>coupling_start_time</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Simulation time of a precursor run.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#create_disturbances"><B>create_disturbances</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Switch to impose random perturbations to the horizontal
+			velocity field. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#cross_normalized_x"><B>cross_normalized_x</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10 (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Type of normalization applied to the x-coordinate of vertical
+			profiles to be plotted with <B>profil</B>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#cross_normalized_y"><B>cross_normalized_y</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10&nbsp; <BR>(100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Type of normalization applied to the y-coordinate of vertical
+			profiles to be plotted with <B>profil</B>. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#cross_profiles"><B>cross_profiles</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 100 (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Determines which vertical profiles are to be presented in which
+			coordinate system if the plot software <B>profil</B> is used.&nbsp;
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#cross_xtext"><B>cross_xtext</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 40&nbsp; <BR>&nbsp;(100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>x-axis labels of vertical profile coordinate systems to be
+			plotted with <B>profil</B>. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#cthf"><B>cthf</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Average heat flux that is prescribed at the top of the plant
+			canopy (in K m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#cut_spline_overshoot"><B>cut_spline_overshoot</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Cut off of so-called overshoots, which can occur with the
+			upstream-spline-scheme.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#cycle_mg"><B>cycle_mg</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 1</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'w'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Type of cycle to be used with the multi-grid method.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#damp_level_1d"><B>damp_level_1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>zu(nz+1)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height where the damping layer begins in the 1d-model (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#data_output"><B>data_output</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10 (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100 * ÂŽ ÂŽ</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Quantities for which 2d cross section and/or 3d volume data are
+			to be output.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#data_output_format"><B>data_output_format</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10 (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'netcdf'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Format of output data.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#data_output_pr"><B>data_output_pr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10 (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Quantities for which vertical profiles (horizontally averaged)
+			are to be output.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.3.html#data_output_pr_user"><B>data_output_pr_user</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>U</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10<BR>(200)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>200 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>User defined quantities for which horizontally averaged profile
+			data is to be output.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#data_output_sp"><B>data_output_sp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10 (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Quantities for which horizontal spectra are to be calculated
+			and output.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.3.html#data_output_user"><B>data_output_user</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>U</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10 (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>User defined quantities for which 2d cross section and/or 3d
+			volume data are to be output.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#data_output_2d_on_each_pe"><B>data_output_2d_on_each_pe</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Output 2d cross section data by one or all processors.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#density_ratio"><B>density_ratio</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0, 9</I> * <I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Ratio of the density of the fluid and the density of the
+			particles.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dissipation_1d"><B>dissipation_1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'as_in_3d_model'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Calculation method for the energy dissipation term in the TKE
+			equation of the 1d-model.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#disturbance_amplitude"><B>disturbance</B></A>&nbsp;&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#disturbance_amplitude">&nbsp;<B>_amplitude</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.25</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum perturbation amplitude of the random perturbations
+			imposed to the horizontal velocity field (in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#disturbance_energy_limit"><B>disturbance_energy</B></A>&nbsp;&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#disturbance_energy_limit">&nbsp;<B>_limit</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.01</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB">Upper limit value of the perturbation energy of
+			the velocity field used as a criterion for imposing random
+			perturbations (in m<SUP>2</SUP>/s<SUP>2</SUP>).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#disturbance_level_b"><B>disturbance_level_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>zu(3) or zu(nz*2/3)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif"><FONT SIZE=3>Lower
+			limit of the vertical range for which random perturbations are to
+			be imposed on the horizontal wind field (</FONT></FONT>in <FONT FACE="Thorndale, serif"><FONT SIZE=3>m).&nbsp;
+			</FONT></FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#disturbance_level_t"><B>disturbance_level_t</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>zu(nz/3) or zu(nzt-3)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif"><FONT SIZE=3>Upper
+			limit of the vertical range for which random perturbations are to
+			be imposed on the horizontal wind field (</FONT></FONT>in <FONT FACE="Thorndale, serif"><FONT SIZE=3>m).
+			</FONT></FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#do2d_at_begin"><B>do2d_at_begin</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Output 2d cross section data by one or all processors.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#do3d_at_begin"><B>do3d_at_begin</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Output of 3d volume data at the beginning of a run.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#do3d_compress"><B>do3d_compress</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Output of data for 3d plots in compressed form.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#do3d_comp_prec"><B>do3d_comp_prec</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 7 (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Significant digits in case of compressed data output.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dp_external"><B>dp_external</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>External pressure gradient switch.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dp_smooth"><B>dp_smooth</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Vertically smooth the external pressure gradient using a
+			sinusoidal smoothing function.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dp_level_b"><B>dp_level_b</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT SIZE=3>Lower limit of the vertical range for which the
+			external pressure gradient is applied (</FONT>in <FONT SIZE=3>m).</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dpdxy"><B>dpdxy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (2)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>2 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Values of the external pressure gradient applied in x- and
+			y-direction, respectively (in Pa/m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#drag_coefficient"><B>drag_coefficient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Drag coefficient used in the plant canopy model.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dt"><B>dt</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I/R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>variable</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale, serif"><FONT SIZE=3>Time step for the
+			3d-model (</FONT></FONT>in <FONT FACE="Thorndale, serif"><FONT SIZE=3>s).
+			</FONT></FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_averaging_input"><B>dt_averaging_input</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval of&nbsp;data which are subject to temporal
+			averaging (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_averaging_input_pr"><B>dt_averaging_input_pr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#dt_averaging_input">dt_<BR>averaging_<BR>input</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval of&nbsp;data which are subject to temporal
+			averaging of <FONT FACE="Thorndale, serif"><FONT SIZE=3>vertical
+			profiles and/or spectra&nbsp;(</FONT></FONT>in <FONT FACE="Thorndale, serif"><FONT SIZE=3>s).&nbsp;</FONT></FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_coupling"><B>dt_coupling</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>9999999.9</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval for the data exchange in case of runs with
+			coupled models (e.g. atmosphere - ocean) (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_data_output"><B>dt_data_output</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which&nbsp;data (3d volume data
+			(instantaneous or time averaged), cross sections (instantaneous or
+			time averaged), vertical profiles, spectra) shall be output (</FONT>in
+			<FONT FACE="Thorndale">s).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_data_output_av"><B>dt_data_output_av</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which time averaged 3d volume data
+			and/or 2d cross section data shall be output (</FONT>in <FONT FACE="Thorndale">s).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_disturb"><B>dt_disturb</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which random perturbations are to be
+			imposed on the horizontal velocity field (</FONT>in <FONT FACE="Thorndale">s).
+			</FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_dopr"><B>dt_dopr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale"><SPAN LANG="en-GB">Temporal interval at
+			which data&nbsp;of vertical profiles shall be output (to local
+			file <A HREF="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</A>
+			or/and <A HREF="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</A>) (</SPAN></FONT>in
+			<FONT FACE="Thorndale"><SPAN LANG="en-GB">s).&nbsp;</SPAN></FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_dopr_listing"><B>dt_dopr_listing</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale, serif"><SPAN LANG="en-GB">Temporal
+			interval</SPAN></FONT> <SPAN LANG="en-GB">at which data </SPAN><FONT FACE="Thorndale"><SPAN LANG="en-GB">of
+			vertical profiles shall be output (output for printouts, local
+			file <A HREF="chapter_3.4.html#LIST_PROFIL">LIST_PROFIL</A>) (</SPAN></FONT>in
+			<FONT FACE="Thorndale"><SPAN LANG="en-GB">s).&nbsp;</SPAN></FONT> 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_dopts"><B>dt_dopts</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which time series data of particle
+			quantities shall be output (</FONT>in <FONT FACE="Thorndale">s).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_dosp"><B>dt_dosp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval at which&nbsp;spectra data shall be output
+			(in s).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_dots"><B>dt_dots</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which&nbsp;time series data shall be
+			output (</FONT>in <FONT FACE="Thorndale">s). </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_do2d_xy"><B>dt_do2d_xy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which horizontal cross section data
+			shall be output (</FONT>in <FONT FACE="Thorndale">s). </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_do2d_xz"><B>dt_do2d_xz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which vertical cross section data (xz)
+			shall be output&nbsp;(</FONT>in <FONT FACE="Thorndale">s). </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_do2d_yz"><B>dt_do2d_yz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which vertical cross section data
+			(yz)&nbsp;shall be output&nbsp;(</FONT>in s<FONT FACE="Thorndale">).</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_do3d"><B>dt_do3d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_data_output">dt_data_<BR>output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which 3d volume data shall be output (</FONT>in
+			<FONT FACE="Thorndale">s). </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_dvrp"><B>dt_dvrp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval of scenes to be displayed with the <B>dvrp</B>
+			software (in s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_max"><B>dt_max</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>20.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum allowed value of the timestep (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_min_part"><B>dt_min_part</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0002</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Minimum value for the particle timestep when SGS velocities are
+			used (in s).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_prel"><B>dt_prel</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale, serif"><SPAN LANG="en-GB">Temporal
+			interval at which particles are to be released from a particle
+			source (</SPAN></FONT>in <FONT FACE="Thorndale, serif"><SPAN LANG="en-GB">s).</SPAN></FONT>&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dt_pr_1d"><B>dt_pr_1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval of vertical profile output of the 1D-model
+			(in s).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_restart"><B>dt_restart</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>9999999.9</P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale, serif">Temporal interval</FONT> <FONT FACE="Thorndale">at
+			which a new restart run is to be carried out (</FONT>in <FONT FACE="Thorndale">s).</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_run_control"><B>dt_run_control</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>60.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale, serif">Temporal interval</FONT>
+			<FONT FACE="Thorndale">at which run control output is to be made
+			(</FONT>in <FONT FACE="Thorndale">s). </FONT>
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dt_run_control_1d"><B>dt_run_control_1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>60.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval of runtime control output of the 1d-model (in
+			s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_sort_particles"><B>dt_sort_particles</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval for sorting particles (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dt_write_particle_data"><B>dt_write_particle_data</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temporal interval for output of particle data (in s).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_directory"><B>dvrp_directory</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 80</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'default'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Name of the directory into which data created by the <B>dvrp</B>
+			software shall be saved. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_file"><B>dvrp_file</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 80</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'default'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Name of the file into which data created by the <B>dvrp</B>
+			software shall be output.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_host"><B>dvrp_host</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 80</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'origin.rvs. <BR>uni- hanover.de'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Name of the computer to which data created by the <B>dvrp</B>
+			software shall be transferred. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_output"><B>dvrp_output</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'rtsp'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Output mode for the <B>dvrp</B> software. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_password"><B>dvrp_password</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 80</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'********'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Password for the computer to which data created by the <B>dvrp</B>
+			software is to be transferred.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_psize"><B>dvrp_psize</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.2</I> * <I>dx</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Diameter that the particles is given in visualizations with the
+			<B>dvrp</B> software (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrpsize_interval"><B>dvrpsize_interval</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(2)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I>, <I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Interval of values used for determining the particle size
+			displayed in the animation.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#dvrp_username"><B>dvrp_username</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 80</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default value 
+			</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>User name of a valid account on the computer to which data
+			created by the <B>dvrp</B> software is to be transferred. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dx"><B>dx</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Horizontal grid spacing along the x-direction (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dy"><B>dy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Horizontal grid spacing along the y-direction (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dz"><B>dz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description 
+			</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Vertical grid spacing (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dz_max"><B>dz_max</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Allowed maximum vertical grid spacing (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dz_stretch_factor"><B>dz_stretch_factor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.08</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Stretch factor for a vertically stretched grid (see
+			<A HREF="chapter_4.1.html#dz_stretch_level">dz_stretch_level</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#dz_stretch_level"><B>dz_stretch_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100000.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level above/below which the grid is to be stretched
+			vertically (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#e_init"><B>e_init</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Initial TKE in m<SUP>2</SUP>s<SUP>-2</SUP>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#e_min"><B>e_min</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Minimum TKE in m<SUP>2</SUP>s<SUP>-2</SUP>.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#end_time"><B>end_time</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P LANG="en-GB"><FONT FACE="Thorndale">Simulation time of the 3D
+			model (</FONT>in <FONT FACE="Thorndale">s).</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#end_time_prel"><B>end_time_prel</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Time of the last release of particles (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#end_time_1d"><B>end_time_1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>864000.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Time to be simulated for the 1D-model (in s).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#fft_method"><B>fft_method</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'system specific'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>FFT-method to be used.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#force_print_header"><B>force_print_header</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Steering of header output to the local file <A HREF="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</A>.
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#galilei_transformation"><B>galilei_transformation</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Application of a Galilei-transformation to the coordinate
+			system of the model.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#grid_matching"><B>grid_matching</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 6</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'strict'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Variable to adjust the subdomain sizes in parallel runs.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#groundplate_color"><B>groundplate_color</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(3)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0, 0.6, 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Color of the ground plate</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#humidity"><B>humidity</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on the prognostic equation for specific
+			humidity q.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#inflow_damping_height"><B>inflow_damping_height</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>from precursor run</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height below which the turbulence signal is used for turbulence
+			recycling (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#inflow_damping_width"><B>inflow_damping_width</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.1 * <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#inflow_damping_height">inflow_damping</A><A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#inflow_damping_height">_height</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Transition range within which the turbulance signal is damped
+			to zero (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#inflow_disturbance_begin"><B>inflow_disturbance_begin</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>MIN(10,</I><BR><I>nx/2 or ny/2)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Lower limit of the horizontal range for which random
+			perturbations are to be imposed on the horizontal velocity field
+			(gridpoints).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#inflow_disturbance_end"><B>inflow_disturbance_end</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>MIN(100,</I><BR><I>3/4*nx or</I><BR><I>3/4*ny)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Upper limit of the horizontal range for which random
+			perturbations are to be imposed on the horizontal velocity field
+			(gridpoints).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#initializing_actions"><B>initializing_actions</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 100</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P STYLE="font-style: normal">Initialization actions to be carried
+			out. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#initial_weighting_factor"><B>initial_weighting_factor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Factor to define the real number of initial droplets in a grid
+			cell.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#isosurface_color"><B>isosurface_color</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(3,10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.9, 0.9, 0.9</I><BR><I>0.8, 0.1, 0.1</I><BR><I>......</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Color of the isosurface(s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#km_constant"><B>km_constant</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>variable (computed from TKE)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Constant eddy diffusivities are used (laminar simulations).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#km_damp_max"><B>km_damp_max</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.5*(dx or dy)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum diffusivity used for filtering the velocity field in
+			the vicinity of the outflow (in m<SUP>2</SUP>/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#lad_surface"><B>lad_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Surface value of the leaf area density (in m<SUP>2</SUP>/m<SUP>3</SUP>)</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#lad_vertical_gradient"><B>lad_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Gradient(s) of the leaf area density (in&nbsp;m<SUP>2</SUP>/m<SUP>4</SUP>)</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#lad_vertical_gradient_level"><B>lad_vertical_gradient_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the&nbsp;gradient of the leaf area
+			density defined by <A HREF="chapter_4.1.html#lad_vertical_gradient">lad_vertical_gradient_level</A>
+			is effective (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#leaf_surface_concentration"><B>leaf_surface_concentration</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Concentration of a passive scalar at the surface of a leaf (in
+			kg/m<SUP>3</SUP>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#long_filter_factor"><B>long_filter_factor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Filter factor for the so-called Long-filter.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#loop_optimization"><B>loop_optimization</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 16</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Method used to optimize loops for solving the prognostic
+			equations .</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#maximum_number_of_particles"><B>maximum_number_</B></A>
+			<BR><A HREF="chapter_4.2.html#maximum_number_of_particles"><B>of_particles</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1000</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum number of particles (on a PE). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#maximum_number_of_tailpoints"><B>maximum_number_</B></A>
+			<BR><A HREF="chapter_4.2.html#maximum_number_of_tailpoints"><B>of_tailpoints</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum number of tailpoints that a particle tail can have. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#maximum_tailpoint_age"><B>maximum_tailpoint_</B></A>
+			<BR><A HREF="chapter_4.2.html#maximum_tailpoint_age"><B>age</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100000.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum age that the end point of a particle tail is allowed to
+			have (in s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#mg_cycles"><B>mg_cycles</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>- 1</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of cycles to be used with the multi-grid scheme.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#mg_switch_to_pe0_level"><B>mg_switch_to_pe0_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Grid level at which data shall be gathered on PE0.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#minimum_tailpoint_distance"><B>minimum_tailpoint_</B></A>
+			<BR><A HREF="chapter_4.2.html#minimum_tailpoint_distance"><B>distance</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Minimum distance allowed between two adjacent points of a
+			particle tail (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#mixing_length_1d"><B>mixing_length_1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'as_in_3d_model'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Mixing length used in the 1d-model.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#mode_dvrp"><B>mode_dvrp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20 (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Graphical objects (isosurfaces, slicers, particles) which are
+			to be created by the <B>dvrp</B> software. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#momentum_advec"><B>momentum_advec</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'pw-scheme</I>'</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Advection scheme to be used for the momentum equations.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#netcdf_precision"><B>netcdf_precision</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20 (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>single precision for all</I><BR><I>output quantities</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Defines the accuracy of the NetCDF output.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#netcdf_64bit"><B>netcdf_64bit</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>All NetCDF files - except those containing 3d volume data -
+			will have 64 bit offset format.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#netcdf_64bit_3d"><B>netcdf_64bit_3d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>NetCDF files containing 3d volume data will have 64 bit offset
+			format.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#ngsrb"><B>ngsrb</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>2</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Grid level at which data shall be gathered on PE0.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#normalizing_region"><B>normalizing_region</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Determines the subdomain from which the normalization
+			quantities are calculated. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#npex"><B>npex</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of processors along x-direction of the virtual processor
+			net. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#npey"><B>npey</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of processors along y-direction of the virtual processor
+			net. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#nsor"><B>nsor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>20</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of iterations to be used with the SOR-scheme. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#nsor_ini"><B>nsor_ini</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Initial number of iterations with the SOR algorithm</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#number_of_particle_groups"><B>number_of_particle_groups</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of particle groups to be used.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#nx"><B>nx</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of grid points in x-direction. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ny"><B>ny</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of grid points in y-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#nz"><B>nz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>no default, see parameter description</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of grid points in z-direction.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#nz_do3d"><B>nz_do3d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>nz+1</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Limits the output of 3d volume data along the vertical
+			direction (grid point index k).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ocean"><B>ocean</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on&nbsp;ocean runs.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#omega"><B>omega</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>7.29212E-5</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Angular velocity of the rotating system (in rad s<SUP>-1</SUP>).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#omega_sor"><B>omega_sor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.8</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Convergence factor to be used with the the SOR-scheme. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#outflow_damping_width"><B>outflow_damping_width</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>MIN(20, nx/2</I> or <I>ny/2)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Width of the damping range in the vicinity of the outflow
+			(gridpoints).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#overshoot_limit_e"><B>overshoot_limit_e</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Allowed limit for the overshooting of subgrid-scale TKE in case
+			that the upstream-spline scheme is switched on (in m<SUP>2</SUP>/s<SUP>2</SUP>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#overshoot_limit_pt"><B>overshoot_limit_pt</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Allowed limit for the overshooting of potential temperature in
+			case that the upstream-spline scheme is switched on (in K). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#overshoot_limit_u"><B>overshoot_limit_u</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Allowed limit for the overshooting of the u-component of
+			velocity in case that the upstream-spline scheme is switched on
+			(in m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#overshoot_limit_v"><B>overshoot_limit_v</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Allowed limit for the overshooting of the v-component of
+			velocity in case that the upstream-spline scheme is switched on
+			(in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#overshoot_limit_w"><B>overshoot_limit_w</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Allowed limit for the overshooting of the w-component of
+			velocity in case that the upstream-spline scheme is switched on
+			(in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#particles_per_point"><B>particles_per_point</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of particles to be started per point.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#particle_advection_start"><B>particle_advection_start</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Time of the first release of particles (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#particle_color"><B>particle_color</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C*10</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'none'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter, which allows to bind the displayed particle color to
+			certain flow quantities.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#particle_dvrpsize"><B>particle_dvrpsize</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C*10</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'none'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter, which allows to bind the displayed particle size to
+			certain flow quantities.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#particle_maximum_age"><B>particle_maximum_age</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Maximum allowed age of particles (in s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#passive_scalar"><B>passive_scalar</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on the prognostic equation for a passive
+			scalar. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pch_index"><B>pch_index</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0 </I>
+			</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Grid point index (scalar) of the upper boundary of the plant
+			canopy layer</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#pdx"><B>pdx</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * dx</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Distance along x between particles within a particle source (in
+			m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#pdy"><B>pdy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * dy</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Distance along y between particles within a particle source (in
+			m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#pdz"><B>pdz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * ( zu(2) - zu(1) )</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Distance along z between particles within a particle source (in
+			m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#phi"><B>phi</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>55.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Geographical latitude (in degrees). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#plant_canopy"><B>plant_canopy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on the plant canopy model</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#plot_spectra_level"><B>plot_spectra_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>No level</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Vertical level(s) for which horizontal spectra are to be
+			plotted (in gridpoints). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#prandtl_layer"><B>prandtl_layer</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on a Prandtl layer. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#prandtl_number"><B>prandtl_number</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Ratio of the eddy diffusivities for momentum and heat (K<SUB>m</SUB>/K<SUB>h</SUB>).
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#precipitation"><B>precipitation</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on the precipitation scheme.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#precipitation_amount_interval"><B>precipitation_amount_<BR>interval</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of &nbsp;<A HREF="chapter_4.2.html#dt_do2d_xy">dt_do2d_<BR>xy</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale, serif">Temporal interval</FONT> <FONT FACE="Thorndale">for
+			which the precipitation amount (in mm) shall be calculated and
+			output (</FONT>in <FONT FACE="Thorndale">s).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#profile_columns"><B>profile_columns</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>3</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of coordinate systems to be plotted in one row by
+			<B>profil</B>. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#profile_rows"><B>profile_rows</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>2</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of rows of coordinate systems to be plotted on one page
+			by <B>profil</B>. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#psb"><B>psb</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * zu(nz/2)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Bottom edge of a particle source (in m).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#psl"><B>psl</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Left edge of a particle source (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#psn"><B>psn</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * ( ny * dy )</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Rear (ânorthâ) edge of a particle source (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#psolver"><B>psolver</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'poisfft'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Scheme to be used to solve the Poisson equation for the
+			perturbation pressure. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#psr"><B>psr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * ( nx * dx )</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Right edge of a particle source (in m).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#pss"><B>pss</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Front (âsouthâ) edge of a particle source (in m).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#pst"><B>pst</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * zu(nz/2)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Top edge of a particle source (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pt_reference"><B>pt_reference</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>use horizontal average as reference</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Reference temperature to be used in all buoyancy terms (in K).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pt_surface"><B>pt_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>300.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Surface potential temperature (in K). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pt_surface_initial_change"><B>pt_surface_initial</B></A>&nbsp;&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.1.html#pt_surface_initial_change">&nbsp;<B>_change</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Change in surface temperature to be made at the beginning of
+			the 3d run (in K).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pt_vertical_gradient"><B>pt_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temperature gradient(s) of the initial temperature profile (in
+			K / 100 m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#pt_vertical_gradient_level"><B>pt_vertical_gradient</B></A>&nbsp;&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.1.html#pt_vertical_gradient_level">&nbsp;<B>_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 *</I>&nbsp; <I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the temperature gradient defined by
+			<A HREF="chapter_4.1.html#pt_vertical_gradient">pt_vertical_gradient</A>
+			is effective (in m).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#q_surface"><B>q_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Surface specific humidity / total water content (kg/kg). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#q_surface_initial_change"><B>q_surface_initial</B></A>
+			<BR><A HREF="chapter_4.1.html#q_surface_initial_change">&nbsp;<B>_change</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Change in surface specific humidity / total water content to be
+			made at the beginning of the 3d run (kg/kg). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#q_vertical_gradient"><B>q_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Humidity gradient(s) of the initial humidity profile (in 1/100
+			m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#q_vertical_gradient_level"><B>q_vertical_gradient</B></A>
+			<BR><A HREF="chapter_4.1.html#q_vertical_gradient_level">&nbsp;<B>_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 *</I>&nbsp; <I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the humidity gradient defined by
+			<A HREF="chapter_4.1.html#q_vertical_gradient">q_vertical_gradient</A>
+			is effective (in m).&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#radiation"><B>radiation</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to switch on longwave radiation cooling at
+			cloud-tops. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#radius"><B>radius</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0, 9</I>*<BR><I>9999999.9</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Particle radius (in m).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#random_generator"><B>random_generator</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'numerical recipes'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Random number generator to be used for creating uniformly
+			distributed random numbers. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#random_heatflux"><B>random_heatflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to impose random perturbations on the internal
+			two-dimensional near surface heat flux field <I>shf</I>. 
+			</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#random_start_position"><B>random_start_position</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><SPAN STYLE="background: transparent"><FONT COLOR="#000000">Initial
+			position of the</FONT> particles is varied randomly within certain
+			limits.&nbsp;</SPAN></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#rayleigh_damping_factor"><B>rayleigh_damping</B></A>&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#rayleigh_damping_factor">&nbsp;<B>_factor</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I> and/or <I>0.01</I> (see parameter description)</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Factor for Rayleigh damping.&nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#rayleigh_damping_height"><B>rayleigh_damping</B></A>&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#rayleigh_damping_height">&nbsp;<B>_height</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>2/3 * zu(nz)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P ALIGN=LEFT>Height where the Rayleigh damping starts (in m).&nbsp;
+						</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#read_particles_from_restartfile"><B>read_particles_from_</B></A>
+			<BR><A HREF="chapter_4.2.html#read_particles_from_restartfile"><B>restartfile</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Read particle data from the previous run. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#recycling_width"><B>recycling_width</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.1 * <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#nx">nx</A>
+			* <A HREF="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/doc/app/chapter_4.1.html#dx">dx</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Distance of the recycling plane from the inflow boundary (in
+			m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.3.html#region"><B>region</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>U</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 40 (0:9)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>&nbsp;</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Name(s) of the subdomain(s) defined by the user.</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#residual_limit"><B>residual_limit</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0E-6</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Largest residual permitted for the multi-grid scheme (in
+			s<SUP>-2</SUP>m<SUP>-3</SUP>). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#restart_time"><B>restart_time</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P>9999999.9</P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Simulated time after which a restart run is to be carried out
+			(in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#rif_max"><B>rif_max</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Upper limit of the flux-Richardson number. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#rif_min"><B>rif_min</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>- 5.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Lower limit of the flux-Richardson number. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#roughness_length"><B>roughness_length</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.1</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Roughness length (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#sa_surface"><B>sa_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>35.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Surface salinity (in psu).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#sa_vertical_gradient"><B>sa_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Salinity gradient(s) of the initial salinity profile (in psu /
+			100 m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#sa_vertical_gradient_level"><B>sa_vertical_gradient_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the salinity gradient defined by
+			<A HREF="chapter_4.1.html#sa_vertical_gradient">sa_vertical_gradient</A>
+			is effective (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#scalar_advec"><B>scalar_advec</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 10</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'pw-scheme'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Advection scheme to be used for the scalar quantities. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="../../../../../DEVELOPER_VERSION/chapter_4.1.html#scalar_exchange_coefficient"><B>scalar_exchange_coefficient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Scalar exchange coefficient for a leaf (dimensionless).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#section_xy"><B>section_xy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no section</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale">Position of&nbsp;cross section(s)
+			for&nbsp;output of 2d horizontal cross sections (grid point index
+			k).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#section_xz"><B>section_xz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no section</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale">Position of&nbsp;cross section(s)
+			for&nbsp;output of 2d (xz) vertical cross sections (grid point
+			index j).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#section_yz"><B>section_yz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I (100)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no section</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P><FONT FACE="Thorndale">Position of&nbsp;cross section(s)
+			for&nbsp;output of 2d (yz) vertical cross sections (grid point
+			index i).&nbsp;</FONT></P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_particles_for_tail"><B>skip_particles_for_tail</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>100</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Limit the number of particle tails.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_data_output"><B>skip_time_data_output</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No data output before this interval has passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_data_output_av"><B>skip_time_data_output_av</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of temporally averaged 2d/3d data before this
+			interval has passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_dopr"><B>skip_time_dopr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of vertical profile data before this interval has
+			passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_dosp"><B>skip_time_dosp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of spectra data before this interval has passed (in
+			s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_do2d_xy"><B>skip_time_do2d_xy</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of instantaneous horizontal cross section data before
+			this interval has passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_do2d_xz"><B>skip_time_do2d_xz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of instantaneous vertical (xz) cross section data
+			before this interval has passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_do2d_yz"><B>skip_time_do2d_yz</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of instantaneous vertical (yz) cross section data
+			before this interval has passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#skip_time_do3d"><B>skip_time_do3d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>value of <A HREF="chapter_4.2.html#skip_time_data_output">skip_time_<BR>data_output</A></I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>No output of instantaneous 3d volume data before this interval
+			has passed (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="../../../../../../raasch/public_html/PALM_group/doc/app/chapter_4.2.html#spectra_direction"><B>slicer_range_limits_dvrp</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(2,10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * (-1,1)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Ranges of values to which a color table has to be mapped (units
+			of the respective quantity).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#spectra_direction"><B>spectra_direction</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 2 (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * ' '</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Direction(s) along which spectra are to be calculated. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#statistic_regions"><B>statistic_regions</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Number of additional user-defined subdomains for which
+			statistical analysis and corresponding output (profiles, time
+			series) shall be made.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#superelevation"><B>superelevation</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Superelevation factor for the vertical coordinate. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#superelevation_x"><B>superelevation_x</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Superelevation factor for the horizontal (x) coordinate. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#superelevation_y"><B>superelevation_y</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Superelevation factor for the horizontal (y) coordinate. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#surface_heatflux"><B>surface_heatflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no prescribed heatflux</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Kinematic sensible heat flux at the bottom surface (in K m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#surface_pressure"><B>surface_pressure</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>1013.25</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Atmospheric pressure at the surface (in hPa)</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#surface_scalarflux"><B>surface_scalarflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Scalar flux at the surface (in kg/(m<SUP>2</SUP> s)). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#surface_waterflux"><B>surface_waterflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Kinematic water flux near the surface (in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#s_surface"><B>s_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Surface value of the passive scalar (in kg/m<SUP>3</SUP>). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#s_surface_initial_change"><B>s_surface_initial_change</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Change in surface scalar concentration to be made at the
+			beginning of the 3d run (in kg/m<SUP>3</SUP>). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#s_vertical_gradient"><B>s_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Scalar concentration gradient(s) of the initial scalar
+			concentration profile (in kg/m<SUP>3 </SUP>/ 100 m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#s_vertical_gradient_level"><B>s_vertical_gradient_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the scalar gradient defined by
+			<A HREF="chapter_4.1.html#s_vertical_gradient">s_vertical_gradient</A>
+			is effective (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#termination_time_needed"><B>termination_time</B></A>&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#termination_time_needed">&nbsp;<B>_needed</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>35.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>CPU time needed for terminal actions at the end of a run in
+			batch mode (in s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#threshold"><B>threshold</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R (10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Threshold value for which an isosurface is to be created by the
+			<B>dvrp</B> software. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#timestep_scheme"><B>timestep_scheme</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 20</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'runge-kutta-3'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Time step scheme to be used for integration of the prognostic
+			variables. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#topography"><B>topography</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 40</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>'flat'</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Topography mode.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#topography_color"><B>topography_color</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(3)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.8, 0.7, 0.6</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Color of the topography.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#topography_grid_convention"><B>topography_grid_convention</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>C * 11</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>default depends on value of <A HREF="chapter_4.1.html#topography">topography</A>;
+			see text for details</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Convention for defining the&nbsp;topography grid.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#top_heatflux"><B>top_heatflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no prescribed heatflux</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Kinematic sensible heat flux at the top surface (in K m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#top_momentumflux_u"><B>top_momentumflux_u</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no prescribed momentumflux</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Momentum flux along x at the top boundary (in m2/s2).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#top_momentumflux_v"><B>top_momentumflux_v</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no prescribed momentumflux</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Momentum flux along y at the top boundary (in m2/s2).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#top_salinityflux"><B>top_salinityflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>no prescribed</I><BR><I>salinityflux</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Kinematic salinity flux at the top boundary, i.e. the sea
+			surface (in psu m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#turbulent_inflow"><B>turbulent_inflow</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Generates a turbulent inflow at side boundaries using a
+			turbulence recycling method.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#u_bulk"><B>u_bulk</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>u-component of the predefined bulk velocity (in m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ug_surface"><B>ug_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>u-component of the geostrophic wind at the surface (in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ug_vertical_gradient"><B>ug_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Gradient(s) of the initial profile of the&nbsp; u-component of
+			the geostrophic wind (in 1/100s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ug_vertical_gradient_level"><B>ug_vertical_gradient_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the gradient defined by
+			<A HREF="chapter_4.1.html#ug_vertical_gradient">ug_vertical_gradient</A>
+			is effective (in m).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ups_limit_e"><B>ups_limit_e</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Subgrid-scale turbulent kinetic energy difference used as
+			criterion for applying the upstream scheme when upstream-spline
+			advection is switched on (in m<SUP>2</SUP>/s<SUP>2</SUP>). &nbsp;</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ups_limit_pt"><B>ups_limit_pt</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Temperature difference used as criterion for applying&nbsp; the
+			upstream scheme when upstream-spline advection&nbsp; is switched
+			on (in K). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ups_limit_u"><B>ups_limit_u</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Velocity difference (u-component) used as criterion for
+			applying the upstream scheme when upstream-spline advection is
+			switched on (in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ups_limit_v"><B>ups_limit_v</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Velocity difference (v-component) used as criterion for
+			applying the upstream scheme when upstream-spline advection is
+			switched on (in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#ups_limit_w"><B>ups_limit_w</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Velocity difference (w-component) used as criterion for
+			applying the upstream scheme when upstream-spline advection is
+			switched on (in m/s). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#use_particle_tails"><B>use_particle_tails</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Give particles a tail.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#use_prior_plot1d_parameters"><B>use_prior_plot1d</B></A>&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#use_prior_plot1d_parameters">&nbsp;<B>_parameters</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P ALIGN=LEFT>Additional plot of vertical profile data with <B>profil</B>
+			from preceding runs of the job chain.&nbsp; 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#use_sgs_for_particles"><B>use_sgs_for_particles</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Use subgrid-scale velocities for particle advection.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#use_surface_fluxes"><B>use_surface_fluxes</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to steer the treatment of the subgrid-scale vertical
+			fluxes within the diffusion terms at k=1 (bottom boundary).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#use_top_fluxes"><B>use_top_fluxes</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to steer the treatment of the subgrid-scale vertical
+			fluxes within the diffusion terms at k=nz (top boundary).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#use_ug_for_galilei_tr"><B>use_ug_for_galilei_tr</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Switch to determine the translation velocity in case that a
+			Galilean transformation is used.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#use_upstream_for_tke"><B>use_upstream_for_tke</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to choose the advection/timestep scheme to be used
+			for the subgrid-scale TKE.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#vertical_particle_advection"><B>vertical_particle_advection</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Switch on/off vertical particle transport.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#v_bulk"><B>v_bulk</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>v-component of the predefined bulk velocity (in m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#vg_surface"><B>vg_surface</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>v-component of the geostrophic wind at the surface (in m/s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#vg_vertical_gradient"><B>vg_vertical_gradient</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Gradient(s) of the initial profile of the&nbsp; v-component of
+			the geostrophic wind (in 1/100s).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#vg_vertical_gradient_level"><B>vg_vertical_gradient_level</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(10)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>10 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level from which on the gradient defined by
+			<A HREF="chapter_4.1.html#vg_vertical_gradient">vg_vertical_gradient</A>
+			is effective (in m).</P>
+		</TD>
+	</TR>
+	<TR VALIGN=TOP>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#wall_adjustment"><B>wall_adjustment</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.T.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Parameter to restrict the mixing length in the vicinity of the
+			bottom boundary (and near vertical walls of a non-flat
+			<A HREF="chapter_4.1.html#topography">topography</A>).</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.1.html#wall_heatflux"><B>wall_heatflux</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>I</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R(5)</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>5 * 0.0</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Prescribed kinematic sensible heat flux in K m/s&nbsp;at the
+			five topography faces.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#write_particle_statistics"><B>write_particle_</B></A>
+			<BR><A HREF="chapter_4.2.html#write_particle_statistics"><B>statistics</B></A>
+						</P>
+		</TD>
+		<TD WIDTH=47>
+			<P>P</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>L</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>.F.</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Switch on/off output of particle informations.</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#z_max_do1d"><B>z_max_do1d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>zu(nzt+1) (model top)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level up to which horizontally averaged profiles are to
+			be plotted with <B>profil</B> (in m). 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#z_max_do1d_normalized"><B>z_max_do1d</B></A>&nbsp;&nbsp;
+			<BR><A HREF="chapter_4.2.html#z_max_do1d_normalized">&nbsp;<B>_normalized</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>determined by plot <BR>data</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Normalized height level up to which horizontally averaged
+			profiles are to be plotted with <B>profil</B>. 
+			</P>
+		</TD>
+	</TR>
+	<TR>
+		<TD WIDTH=164>
+			<P><A HREF="chapter_4.2.html#z_max_do2d"><B>z_max_do2d</B></A></P>
+		</TD>
+		<TD WIDTH=47>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=75>
+			<P>R</P>
+		</TD>
+		<TD WIDTH=183>
+			<P><I>zu(nz)</I></P>
+		</TD>
+		<TD WIDTH=651>
+			<P>Height level up to which 2d cross sections are to be plotted
+			with <B>iso2d</B> (in m). 
+			</P>
+		</TD>
+	</TR>
+</TABLE>
+<HR>
+<P><BR><FONT COLOR="#000080"><A HREF="chapter_4.5.6.html"><FONT COLOR="#000080"><IMG SRC="left.gif" NAME="Grafik1" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A><A HREF="index.html"><FONT COLOR="#000080"><IMG SRC="up.gif" NAME="Grafik2" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A><A HREF="chapter_5.0.html"><FONT COLOR="#000080"><IMG SRC="right.gif" NAME="Grafik3" ALIGN=BOTTOM WIDTH=32 HEIGHT=32 BORDER=1></FONT></A></FONT></P>
+<P>&nbsp;<I>Last change:&nbsp;&nbsp;</I> $Id: chapter_4.6.html 336
+2009-06-10 11:19:35Z raasch $ 
+</P>
+<P><BR><BR><BR>
+</P>
+</BODY>
+</HTML>
