source: palm/trunk/DOC/app/chapter_4.2.html @ 54

Last change on this file since 54 was 54, checked in by raasch, 17 years ago

property Id set for most of all files, small bug in mbuild fixed

  • Property svn:keywords set to Id
File size: 225.8 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html><head>
3<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>PALM chapter 4.2</title></head>
4<body><h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
5parameters</a> and <a href="#Paketparameter">package
6parameters</a></h3>
7<h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3>
8<br><br>
9<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr>
10<td style="vertical-align: top;"><font size="4"><b>Parameter
11name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
12<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
13<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
14</tr> <tr> <td style="vertical-align: top;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
15</td> <td style="vertical-align: top;">R<br> </td>
16<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
17<td style="vertical-align: top;">Averaging interval for
18all&nbsp;output of temporally averaged data (in s).<br><br>This
19parameter defines the time interval length for temporally averaged data
20(vertical profiles, spectra, 2d cross-sections, 3d volume data). By
21default,&nbsp;data are not subject to temporal averaging. The
22interval
23length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
24In any case, <span style="font-weight: bold;">averaging_interval</span>
25&lt;= <span style="font-weight: bold;">dt_data_output_av</span>
26must hold.<br><br>If
27an interval is defined, then by default the average is calculated from
28the data values of all timesteps lying within this interval. The number
29of time levels entering into the average can be reduced with the
30parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br><br>If
31an averaging interval can not be completed at the end of a run, it
32will be finished at the beginning of the next restart run. Thus for
33restart runs, averaging intervals do not
34necessarily begin at the beginning of the run.<br><br>Parameters
35<a href="#averaging_interval_pr">averaging_interval_pr</a>
36and <a href="#averaging_interval_sp">averaging_interval_sp</a>
37can be used to define different averaging intervals for vertical
38profile data and spectra, respectively.<br> </td> </tr>
39<tr> <td style="vertical-align: top;"> <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
40</td> <td style="vertical-align: top;">R<br> </td>
41<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
42interval</a><br>
43</span> </td> <td style="vertical-align: top;">
44<p>Averaging interval for output of vertical profiles&nbsp;to
45local
46file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
47</font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
48(in s).&nbsp; </p> <p>If
49this parameter is given a non-zero value, temporally
50averaged vertical profile data are output. By default, profile data
51data are not subject to temporal averaging. The interval length is
52limited by the parameter <a href="#dt_dopr">dt_dopr</a>.
53In any case <b>averaging_interval_pr</b> &lt;= <b>dt_dopr
54</b>must
55hold.</p>If an interval is defined, then by default the average
56is calculated
57from the data values of all timesteps lying within this interval. The
58number of time levels entering into the average can be reduced with the
59parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>.
60<p>If
61an averaging interval can not be completed at the end of a run, it will
62be finished at the beginning of the next restart run. Thus for restart
63runs, averaging intervals do not
64necessarily begin at the beginning of the run.</p> </td> </tr>
65<tr> <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
66substeps</span></td> <td style="vertical-align: top;">L<br>
67</td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
68<td style="vertical-align: top;">Switch
69to steer the call of the pressure solver.<br> <br>
70In order to speed-up performance, the Poisson equation for perturbation
71pressure (see <a href="#psolver">psolver</a>) can
72be called only at the last substep of multistep Runge-Kutta
73timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>)
74by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span>
75= <span style="font-style: italic;">.F.</span>.
76In many cases, this sufficiently reduces the divergence of the velocity
77field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this
78case and in case
79of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span>
80= <span style="font-style: italic;">.T.</span>
81should be used.&nbsp;<span style="font-weight: bold;"></span></td>
82</tr> <tr> <td style="vertical-align: top;">
83<p><a name="fcl_factor"></a><b>cfl_factor</b></p>
84</td> <td style="vertical-align: top;">R<br> </td>
85<td style="vertical-align: top;"> <p><i>0.1,
860.8 or 0.9</i> <br> <i>(see right)</i></p>
87</td> <td style="vertical-align: top;"> <p lang="en-GB">Time step limiting factor.&nbsp; </p>
88<p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
89allowed </span>time step according to CFL and
90diffusion-criterion
91dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">=
92dt_max * <b>cfl_factor</b>
93in order to avoid stability problems which may arise in the vicinity of
94the maximum allowed timestep. The condition <i>0.0</i>
95&lt; <b>cfl_factor</b>
96&lt; <i>1.0 </i>applies.<br> </span></p>
97<p><span lang="en-GB">The default value of
98cfl_factor depends on
99the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br> </span></p> <p><span lang="en-GB">For the third order Runge-Kutta scheme it
100is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br> </span></p> <p><span lang="en-GB">In case of the leapfrog scheme a quite
101restrictive value of <span style="font-weight: bold;">cfl_factor</span>
102= <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
103divergence
104significantly effects the accuracy of the model results.</span><a href="chapter_4.1.html#scalar_advec"><span lang="en-GB"></span></a><span lang="en-GB"> Possibly larger values may
105be used with the leapfrog scheme but these are to be determined by
106appropriate test runs.<span style="font-family: times new roman;"><br>
107</span></span></p> <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
108scheme is <span style="font-weight: bold;">cfl_factor</span>
109= <span style="font-style: italic;">0.8</span> .</font></span></td>
110</tr>
111<tr> <td style="vertical-align: top;"> <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
112</td> <td style="vertical-align: top;">L<br> </td>
113<td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
114<td style="vertical-align: top;"> <p>Switch to
115impose random perturbations to the horizontal
116velocity field.&nbsp; </p> <p>With <b>create_disturbances</b>
117= <i>.T.,</i> random
118perturbations can be imposed to the horizontal velocity field at
119certain times e.g. in order to trigger off the onset of convection,
120etc..<br> </p> <p>The temporal interval between
121these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
122the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a>
123and <a href="#disturbance_level_t">disturbance_level_t</a>,
124and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>.
125In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
126and <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
127the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a>
128and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>.
129A perturbation is added to each grid point with its individual value
130determined by multiplying the disturbance amplitude with a uniformly
131distributed random number.
132After this, the arrays of u and v are smoothed by applying a
133Shuman-filter twice and made divergence-free by applying the pressure
134solver.<br> </p> <p>The random number generator to
135be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br>
136</p> <p>As soon as the desired flow features have
137developed
138(e.g.&nbsp; convection has started), further imposing of
139perturbations
140is not necessary and can be omitted (this does not hold for non-cyclic
141lateral boundaries!). This can be steered by assigning
142an upper limit value for the perturbation energy (the perturbation
143energy is defined by the deviation of the velocity from the mean flow)
144using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>.
145As soon as the perturbation energy has exceeded this energy limit, no
146more random perturbations are assigned<br>
147.&nbsp; <br>
148Timesteps where a random perturbation has been imposed are marked in
149the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
150by the character "D" appended to the values of the maximum horizontal
151velocities. </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
152</td> <td style="vertical-align: top;">C*10&nbsp;
153<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td>
154<td style="vertical-align: top;"> <p>Type of
155normalization applied to the x-coordinate of vertical
156profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
157<p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
158= <span style="font-style: italic;">'profil'</span>.</p><p>If
159vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
160local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
161parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
162the x-values of the data points can be normalized with respect to
163certain quantities (e.g. the near-surface heat flux) in order to ensure
164a better comparability. This type of normalization then applies to all
165profiles of one coordinate system (panel). The normalization quantities
166are re-calculated for each output time of each individual profile. If
167temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>),
168then the normalization quantities are also temporally averaged
169accordingly. If the value of a normalization quantity becomes zero,
170then normalization for the total respective coordinate system (panel)
171is switched off automatically (also for the y-axis).<br> </p>
172<p>By default, the normalization quantities are calculated as the
173horizontal mean of the total model domain and and these values are also
174used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
175Instead of this, they can be calculated from the data of a certain
176subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a>
177(however, they are used again for all subdomains and even for the total
178domain).&nbsp; </p> <p>The user can choose between
179the following normalization
180quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'wpt0'</i></td>
181<td style="vertical-align: top;">Normalization with
182respect
183to the total surface sensible heat
184flux (k=0 ).</td> </tr> <tr> <td style="vertical-align: middle;"><i>'ws2'</i></td>
185<td style="vertical-align: top;">Normalization with
186respect
187to w<sub>*</sub> <sup>2</sup>
188(square of the characteristic vertical wind speed of the CBL)</td>
189</tr> <tr> <td style="vertical-align: top;"><i>'tsw2'</i></td>
190<td style="vertical-align: top;">Normalization with
191respect
192to the square of the characteristic
193temperature of the CBL theta<sub>*</sub> (this is defined
194as ratio of
195the surface heat flux and w<sub>*</sub>).</td> </tr>
196<tr> <td style="vertical-align: middle;"><i>'ws3'</i></td>
197<td style="vertical-align: top;">Normalization with
198respect
199to w<sub>*</sub> <sup>3</sup>.</td> </tr>
200<tr> <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
201<td style="vertical-align: top;">Normalization with
202respect
203to w<sub>*</sub><sup>2</sup>theta<sub>*</sub>
204(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
205</tr> <tr> <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
206<td style="vertical-align: top;">Normalization with
207respect
208to w<sub>*</sub><sup>2 </sup>theta<sub>*</sub>
209(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
210</tr> </tbody> </table> <p>For each
211coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>)
212an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> =
213<span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
214then the
215x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
216and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>.
217Data
218of the further coordinate systems (if any are to be drawn) are not
219normalized.&nbsp; </p> <p>Using a normalization
220leaves all vertical profile data on
221local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
222unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the
223normalization is steered
224by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a>
225which may be changed subsequently by the user in the parameter file
226(local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
227&nbsp;<br>
228The assigned normalization quantity is noted in the axes labels of the
229respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
230</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
231</td> <td style="vertical-align: top;">C*10&nbsp;
232<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td>
233<td style="vertical-align: top;"> <p>Type of
234normalization applied to the y-coordinate of vertical
235profiles to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;</p>
236<p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
237= <span style="font-style: italic;">'profil'</span>.</p><p>If
238vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
239local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
240parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
241the y-values of the data points can be normalized with respect to
242certain quantities (at present only the normalization with respect to
243the boundary layer height is possible) in order to ensure a better
244comparability. </p> <p>The user can choose between the
245following normalization
246quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'z_i'</i></td>
247<td style="vertical-align: top;">Normalization with
248respect
249to the boundary layer height
250(determined from the height where the heat flux achieves its minimum
251value).</td> </tr> </tbody> </table> <p>For
252further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p>
253</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
254</td> <td style="vertical-align: top;">C*100&nbsp;
255<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;">see right<br> </td>
256<td style="vertical-align: top;"> <p>Determines
257which vertical profiles are to be presented in
258which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used.
259&nbsp; </p> <p>This parameter only applies for
260&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
261= <span style="font-style: italic;">'profil'</span>.</p><p>The
262default assignment is:&nbsp; </p> <p><b>cross_profiles</b>
263=&nbsp; </p> <ul> <p><span style="font-family: monospace; font-style: italic;">'
264u v ',</span><br> <span style="font-family: monospace; font-style: italic;">' pt
265',&nbsp; </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">'
266w"pt" w*pt* w*pt*BC wpt wptBC ',&nbsp; </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">'
267w"u" w*u* wu w"v"w*v* wv ',&nbsp; </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' km
268kh ',</span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' l '
269,</span><br>
27014 * <span style="font-family: monospace; font-style: italic;">'
271'</span></p> </ul> <p>If plot output of
272vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
273the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.
274Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
275which describes the layout for a plot to be generated with the plot
276program <span style="font-weight: bold;">profil</span>.
277The parameter <b>cross_profiles</b>
278determines how many coordinate systems (panels) the plot contains and
279which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
280expects a character string (up to 100 characters long) for each
281coordinate system, which consists of the names of the profiles to be
282drawn into this system (all available profiles and their respective
283names are described at parameter <a href="#data_output_pr">data_output_pr</a>).
284The single names have to be separated by one blank (' ') and a blank
285must be spent also at the beginning and at the end of the
286string.&nbsp; </p> <p>Example:&nbsp; </p> <ul>
287<p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
288' pt '</span></p> </ul> <p>In this case the
289plot consists of two coordinate systems
290(panels) with the first panel containing the profiles of the horizontal
291velocity components (<span style="font-style: italic;">'u'</span>
292and <span style="font-style: italic;">'v'</span>)
293of all output times (see <a href="#dt_dopr">dt_dopr</a>)
294and the second one containing the profiles of the potential temperature
295(<span style="font-style: italic;">'pt'</span>).<br>
296</p> <p>Whether the coordinate systems are actually drawn,
297depends on
298whether data of the appropriate profiles were output during the run
299(profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>).
300For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned,
301then
302the plot only consists of one panel, since no profiles of the potential
303temperature were output. On the other hand, if profiles were assigned
304to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>,
305then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
306but they are not drawn in the plot. <br> </p>
307The arrangement of the panels in the plot can be controlled
308with the parameters <a href="#profile_columns">profile_columns</a>
309and <a href="#profile_rows">profile_rows</a>.
310Up to 100 panels systems are allowed in a plot (however, they may be
311distributed on several pages).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
312</td> <td style="vertical-align: top;">C*40&nbsp;
313<br>&nbsp;&nbsp; (100)</td> <td style="vertical-align: top;">see right<br> </td>
314<td style="vertical-align: top;"> <p>x-axis labels
315of vertical profile coordinate systems to be
316plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
317</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
318= <span style="font-style: italic;">'profil'</span>.</p><p>The
319default assignment is:&nbsp; </p> <p><b>cross_xtext</b>
320=&nbsp; </p> <ul> <p><span style="font-style: italic;">'wind speed in
321ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'pot. temperature in
322K',&nbsp; </span><br style="font-style: italic;">
323<span style="font-style: italic;">'heat flux in K
324ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'momentum flux in
325m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'eddy diffusivity in
326m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;"> <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
327<br>14 * <span style="font-style: italic;">' '</span></p>
328</ul> <p>This parameter can be used to assign x-axis
329labels to vertical
330profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output
331of vertical
332profile data see <a href="#data_output_pr">data_output_pr</a>).<br>
333The labels are assigned to those coordinate systems (panels) defined by
334<a href="#cross_profiles">cross_profiles</a>
335according to their respective order (compare the default values of <b>cross_xtext</b>
336and <b>cross_profiles</b>). </p> <p>Umlauts
337are possible (write &ldquo; in front of, similar to TeX), as
338well as super- and subscripts (use "&gt;" or "&lt;" in front of
339each
340character), special characters etc. (see UNIRAS manuals) when using the
341plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p>
342</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
343</td> <td style="vertical-align: top;">C*1</td>
344<td style="vertical-align: top;"><i>'w'</i></td>
345<td style="vertical-align: top;"> <p>Type of cycle
346to be used with the multi-grid method.&nbsp; </p> <p>This
347parameter determines which type of cycle is applied in
348the multi-grid method used for solving the Poisson equation for
349perturbation pressure (see <a href="#psolver">psolver</a>).
350It defines in which way it is switched between the fine and coarse
351grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b>
352may be assigned the values <i>'v'</i> or <i>'w'</i>).
353The
354computational cost of w-cycles is much higher than that of v-cycles,
355however, w-cycles give a much better convergence. </p> </td>
356</tr> <tr> <td style="vertical-align: top;">
357<p><a name="data_output"></a><b>data_output</b></p>
358</td> <td style="vertical-align: top;">C * 10 (100)<br>
359</td> <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
360</td> <td style="vertical-align: top;">Quantities
361for which 2d cross section and/or 3d volume data are to be output.<br><br>PALM
362allows the output of instantaneous data as well as of temporally
363averaged data which is steered by the strings assigned to this
364parameter (see below).<br><br>By default, cross section
365data are output (depending on the selected cross sections(s), see
366below)&nbsp; to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>,
367<a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
368and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>.
369Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>.
370If the user has switched on the output of temporally averaged data,
371these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>,
372<a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
373<a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
374and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
375respectively.<br><br>The
376filenames already suggest that all files have NetCDF format.
377Informations about the file content (kind of quantities, array
378dimensions and grid coordinates) are part of the self describing NetCDF
379format and can be extracted from the NetCDF files using the command
380"ncdump -c &lt;filename&gt;". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing
381the PALM NetCDF data.<br><br>The following quantities are
382available for output by default:<br><br><table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="width: 106px;"><span style="font-weight: bold;">quantity
383name</span></td><td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td><td><span style="font-weight: bold;">unit</span></td><td><span style="font-weight: bold;">remarks</span></td></tr><tr><td style="width: 106px;"><span style="font-style: italic;">e</span></td><td style="width: 196px;">SGS TKE</td><td>m<sup>2</sup>/s<sup>2</sup></td><td></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td><td style="width: 196px; vertical-align: top;">liquid water path</td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">only horizontal cross section
384is allowed,&nbsp;requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
385= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td><td style="width: 196px; vertical-align: top;">perturpation
386pressure</td><td style="vertical-align: top;">N/m<sup>2</sup>,
387Pa</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td><td style="width: 196px; vertical-align: top;">particle/droplet
388concentration</td><td style="vertical-align: top;">#/gridbox</td><td style="vertical-align: top;">requires that particle
389advection is switched on by <span style="font-weight: bold;">mrun</span>-option
390"-p particles"</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td><td style="width: 196px; vertical-align: top;">mean
391particle/droplet radius </td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">requires that particle
392advection is switched on by <span style="font-weight: bold;">mrun</span>-option
393"-p particles"</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td><td style="width: 196px; vertical-align: top;">potential
394temperature<br></td><td style="vertical-align: top;">K</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td><td style="width: 196px; vertical-align: top;">specific humidity
395(or total water content, if cloud physics is switched on)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#moisture">moisture</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td><td style="width: 196px; vertical-align: top;">liquid water
396content</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
397= <span style="font-style: italic;">.TRUE.</span>
398or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
399= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td><td style="width: 196px; vertical-align: top;">change in liquid
400water content due to condensation/evaporation during last timestep</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
401= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td><td style="width: 196px; vertical-align: top;">volume of liquid
402water</td><td style="vertical-align: top;">m<sup>3</sup>/gridbox</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
403= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td><td style="width: 196px; vertical-align: top;">weighting factor</td><td style="vertical-align: top;"></td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
404= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td><td style="width: 196px; vertical-align: top;">water vapor
405content (specific humidity)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
406= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td><td style="width: 196px; vertical-align: top;">concentration of
407the scalar</td><td style="vertical-align: top;">1/m<sup>3</sup></td><td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
408= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td><td style="width: 196px; vertical-align: top;">(near surface)
409characteristic temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">only horizontal cross section
410is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td><td style="width: 196px; vertical-align: top;">u-component of
411the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td><td style="width: 196px; vertical-align: top;">(near surface)
412friction velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;">only horizontal cross section
413is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td><td style="width: 196px; vertical-align: top;">v-component of
414the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td><td style="width: 196px; vertical-align: top;">virtual potential
415temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#moisture">moisture</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td><td style="width: 196px; vertical-align: top;">w-component of
416the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr></tbody></table><br>Multiple
417quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span>
418= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br><br>By
419assigning the pure strings from the above table, 3d volume data is
420output. Cross section data can be output by appending the string <span style="font-style: italic;">'_xy'</span>, <span style="font-style: italic;">'_xz'</span>, or <span style="font-style: italic;">'_yz'</span> to the
421respective quantities. Time averaged&nbsp;output is created by
422appending the string <span style="font-style: italic;">'_av'
423</span>(for
424cross section data, this string must be appended after the cross
425section string). Cross section data can also be (additionally) averaged
426along the direction normal to the respective section (see below).
427Assignments of quantities can be given in arbitrary
428order:<br><br>Example:<br><br><div style="margin-left: 40px;"><span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'pt_xz_av'</span>, <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'u_av'</span>.<br></div><br>This
429example will create the following output: instantaneous 3d volume data
430of u-velocity component (by default on file DATA_3D_NETCDF), temporally
431averaged 3d volume data of u-velocity component (by default on file
432DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of
433w-velocity component (by default on file DATA_2D_XY_NETCDF), and
434temporally averaged vertical cross section data of potential
435temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br><br>The
436user is allowed to extend the above list of quantities by defining his
437own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br><br>The
438time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
439This is valid for all types of output quantities by default. Individual
440time intervals for instantaneous &nbsp;(!) 3d and section data can
441be
442declared using <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="#dt_do2d_xz">dt_do2d_xz</a>, and <a href="#dt_do2d_yz">dt_do2d_yz</a>.<br><br>Also,
443an individual time interval for output of temporally averaged data can
444be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
445This applies to both 3d volume and cross section data. The length of
446the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br><br>The
447parameter <a href="#skip_time_data_output">skip_time_data_output</a>
448can be used to shift data output activities for a given time interval.
449Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>,
450<a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><p>With
451the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>&nbsp;
452the output can be limited in the vertical direction up to a certain
453grid point.<br> </p> Cross sections extend through the
454total model
455domain. In the two horizontal directions all grid points with 0
456&lt;= i
457&lt;= nx+1 and 0 &lt;= j
458&lt;= ny+1 are output so that in case of cyclic boundary conditions
459the
460complete total domain is represented. The location(s) of the cross
461sections can be defined with parameters <a href="#section_xy">section_xy</a>,
462<a href="#section_xz">section_xz</a>, and <a href="#section_yz">section_yz</a>. Assigning <span style="font-weight: bold;">section_..</span> = <span style="font-style: italic;">-1</span>
463causes&nbsp;the output data to be averaged along the direction
464normal to the respective section.<br><br><br><span style="font-weight: bold;">Output of user defined quantities:</span><br><br>Beside
465the standard quantities from the above list, the user can output any
466other quantities. These have to be defined and calculated within the
467user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>).
468They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>
469for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
470Output of the user defined quantities (time interval, averaging,
471selection of cross sections, etc.) is controlled with the parameters
472listed above and data are written to the same file(s) as the standard
473quantities.<br><br><p style="font-weight: bold;">Output
474on parallel machines:</p><p>
475By default, with parallel runs, processors output only data
476of their respective subdomains into seperate local files (file names
477are
478constructed by appending the four digit processor ID, e.g.
479&lt;filename&gt;_0000, &lt;filename&gt;_0001, etc.).
480After PALM has
481finished, the contents of these individual
482files are sampled into one final file<span style="font-weight: bold;"></span>
483using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
484(to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
485configuration file).</p> <p>Alternatively, PALM is able to
486collect all grid points of a
487cross section on PE0 before output is done. In this case only
488one&nbsp;
489output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
490does not have to be called. In case of very large numbers of horizontal
491gridpoints, sufficient
492memory is required on PE0.&nbsp; This method can be used by
493assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
494= <i>.F.</i>.</p><p>3d volume data output is
495always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span>
496has to be called anyway after PALM has been finished.</p><p><br><span style="font-weight: bold;">Old formats:</span></p>
497<p>Beside
498the NetCDF format,&nbsp;2d cross section data and 3d volume data
499can
500also be output, for historical reasons, in a different (binary) format
501using parameter <a href="#data_output_format">data_output_format</a>.</p><p>By
502assigning <span style="font-weight: bold;">data_output_format
503</span>= <span style="font-style: italic;">'avs'</span>,
504the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
505Output is in FORTRAN binary format&nbsp;readable by
506the plot software <span style="font-weight: bold;">AVS</span>.&nbsp;
507The order of data on the file follows the order used in the assignment
508for <b>data_output</b> (e.g. <b>data_output</b>
509= <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,...&nbsp;
510means that the file starts with the pressure data, followed by the
511v-component of the velocity, etc.). Both instantaneous and time
512averaged data are written on this file! Additional to this file, PALM
513creates
514a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>)
515with coordinate information needed by <span style="font-weight: bold;">AVS</span>.
516As third and
517fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
518and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>),
519which describe the contents of the data file and/or coordinate file
520and are used by AVS. However, AVS expects the content description in
521one file. This needs the local file PLOT3D_FLD_COOR to be appended to
522the file
523PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
524configuration file: &ldquo;<span style="font-family: monospace;">cat
525PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>&rdquo;)
526after PALM has
527finished.&nbsp;To reduce the amount of data, output to this file
528can be done
529in
530compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>).
531Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in
532<a href="chapter_4.5.5.html">chapter
5334.5.5</a>.</p>By assigning <span style="font-weight: bold;">data_output_format </span>=
534<span style="font-style: italic;">'iso2d'</span>,
535the cross section data is output to the local files <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>, <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>, and <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
536Output is in FORTRAN binary format&nbsp;readable by
537the plot software&nbsp;<span style="font-weight: bold;">iso2d</span>.&nbsp;
538The order of data on the files follows the order used in the assignment
539for <b>data_output</b> (e.g. <b>data_output</b>
540= <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,...&nbsp;
541means that the file containing the horizontal cross section data starts
542with the instantaneous pressure data, followed by the
543temporally averaged v-component of the velocity, etc.). Both
544instantaneous and time averaged data are written on this
545file!Additional to these binary files, PALM
546creates NAMELIST parameter files
547(local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>,
548<a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
549<a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
550<a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
551<a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
552<a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
553which can be used as parameter input files for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
554That needs local files with suffix _LOCAL to be appended to the
555respective files with suffix _GLOBAL (by
556suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span>
557configuration file, e.g.: &ldquo;<span style="font-family: monospace;">cat
558PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</span>&rdquo;)
559after PALM has
560finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the
561respective data and
562parameter file. The plot layout is steered via the parameter input
563file.
564The values of these <span style="font-weight: bold;">iso2d</span>
565parameters are determined by a set of mostly internal PALM parameters
566(exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>).
567All parameter values can be changed by editing the parameter input
568file.&nbsp;Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found
569in <a href="chapter_4.5.4.html">chapter
5704.5.4</a>.<br><br><span style="font-weight: bold;">Important:</span><br>There
571is no guarantee that iso2d- and avs-output will be available in future
572PALM versions (later than 3.0). </td> </tr> <tr> <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
573</td> <td style="vertical-align: top;">C * 10 (10) </td>
574<td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
575<td style="vertical-align: top;">Format of output data.<br><br>By
576default, all data (profiles, time
577series, spectra, particle data, cross sections, volume data) are output
578in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).
579Exception: restart data (local files <a href="chapter_3.4.html#BININ">BININ</a>, <a href="chapter_3.4.html#BINOUT">BINOUT</a>, <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
580<a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
581are always output in FORTRAN binary format.<br><br>The
582numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br><br>The
583maximum file size for NetCDF files is 2 GByte by default. Use the
584parameter <a href="#netcdf_64bit">netcdf_64bit</a>
585if larger files have to be created.<br><br>For historical
586reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span>
587may be assigned the following values:<br><br><table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td><td>output
588of profiles,&nbsp;time series and spectra in ASCII format to be
589read by the graphic software <span style="font-weight: bold;">profil
590</span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
591<a href="#chapter_4.5.3.html">4.5.3</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td><td>output
592of 2d cross-sections in FORTRAN binary format to be read by the graphic
593software <span style="font-weight: bold;">iso2d</span>
594(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td><td>output
595of 3d volume data in FORTRAN binary format to be read by the graphic
596software <span style="font-weight: bold;">AVS</span>
597(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td></tr></tbody></table><br>Multiple
598values can be assigned to <span style="font-weight: bold;">data_output_format</span>,
599i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as
600cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> =
601<span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
602assigned.<br><br><span style="font-weight: bold;">Warning:</span>
603There is no guarantee that the "old" formats will be available in
604future PALM versions (beyond 3.0)!<br> </td> </tr> <tr>
605<td style="vertical-align: top;"> <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
606</td> <td style="vertical-align: top;">C *
60710&nbsp; <br>
608(100)</td> <td style="vertical-align: top;"><i>100
609* ' '</i></td> <td style="vertical-align: top;">
610<p>Quantities for which vertical profiles (horizontally averaged)
611are to be output.&nbsp; </p> <p>By default vertical
612profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>.
613The file's format is NetCDF.&nbsp; Further details about processing
614NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>For
615historical reasons, data can also be output in ASCII-format on local
616file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
617which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See
618parameter <a href="#data_output_format">data_output_format</a>
619for defining the format in which data shall be output.<br> </p>
620<p>For horizontally averaged vertical
621profiles always <span style="font-weight: bold;">all</span>
622vertical
623grid points (0 &lt;= k &lt;= nz+1) are output to file. Vertical
624profile data refers to the total domain but profiles for subdomains can
625also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).&nbsp;
626</p> <p>The temporal interval of the output times of
627profiles is
628assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>.
629Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
630the profiles are ordered with respect to their
631output times.</p><p>Profiles can also be temporally
632averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>).&nbsp;<br>
633</p> <p>The following list shows the values which can be
634assigned to <span style="font-weight: bold;">data_output_pr</span>.
635The profile data is either defined on
636u-v-levels (variables marked in <font color="#ff6600">red</font>)
637or
638on w-levels (<font color="#33ff33">green</font>).
639According to this,
640the
641z-coordinates of the individual profiles vary. Beyond that, with a
642Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>)
643the lowest output
644level is z = zu(1) instead of z = zw(0) for profiles <i>w''
645u'',w''v"</i>, <i>wu</i> and <i>wv</i>
646.&nbsp; <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
647<td style="vertical-align: top;">u-component of the
648velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
649<td style="vertical-align: top;">v-component of the
650velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
651<td style="vertical-align: top;">w-component of the
652velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
653<td style="vertical-align: top;">Potential temperature (in
654K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
655<td style="vertical-align: top;">Virtual potential
656temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
657<td style="vertical-align: top;">Potential liquid water
658temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
659<td style="vertical-align: top;">Total water content
660(in kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
661<td style="vertical-align: top;">Specific humidity (in
662kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
663<td style="vertical-align: top;">Liquid water content
664(in kg/kg).</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600">s</font></td>
665<td style="vertical-align: top;">Scalar concentration (in
666kg/m<sup>3</sup>).</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
667<td style="vertical-align: top;">Turbulent kinetic energy
668(TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td>
669</tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
670<td style="vertical-align: top;">Perturbation energy
671(resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td>
672</tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
673<td style="vertical-align: top;">Eddy diffusivity for
674momentum (in m<sup>2</sup>/s).</td> </tr> <tr>
675<td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
676<td style="vertical-align: top;">Eddy diffusivity for heat
677(in m<sup>2</sup>/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
678<td style="vertical-align: top;">Mixing length (in m).</td>
679</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
680<td style="vertical-align: top;">u-component of the
681subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
682</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td>
683<td style="vertical-align: top;">u-component of the
684resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
685</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
686<td style="vertical-align: top;">u-component of the total
687vertical momentum flux (<i>w"u"</i> + <i>w*u*</i>)
688(in m<sup>2</sup>/s<sup>2</sup>).</td> </tr>
689<tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
690<td style="vertical-align: top;">v-component of the
691subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
692</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td>
693<td style="vertical-align: top;">v-component of the
694resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
695</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
696<td style="vertical-align: top;">v-component of the total
697vertical momentum flux (<i>w"v"</i> + <i>w*v*</i>)
698(in m<sup>2</sup>/s<sup>2</sup>).</td> </tr>
699<tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
700<td style="vertical-align: top;">Subgrid-scale vertical
701sensible heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
702<td style="vertical-align: top;">Resolved vertical
703sensible
704heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
705<td style="vertical-align: top;">Total vertical sensible
706heat flux (<i>w"pt"</i> + <i>w*pt*</i>)
707(in K
708m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td>
709<td style="vertical-align: top;">Subgrid-scale vertical
710sensible heat flux using the
711Bott-Chlond scheme (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
712<td style="vertical-align: top;">Total vertical sensible
713heat flux using the Bott-Chlond scheme
714(<i>w"pt"</i>
715+ <i>w*pt*BC</i>) (in K m/s).</td> </tr> <tr>
716<td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
717<td style="vertical-align: top;">Subgrid-scale vertical
718buoyancy flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
719<td style="vertical-align: top;">Resolved vertical
720buoyancy
721flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
722<td style="vertical-align: top;">Total vertical buoyancy
723flux (w"vpt" + w*vpt*) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
724<td style="vertical-align: top;">Subgrid-scale vertical
725water flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td>
726<td style="vertical-align: top;">Resolved vertical water
727flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
728<td style="vertical-align: top;">Total vertical water flux
729(w"q" + w*q*) (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
730<td style="vertical-align: top;">Subgrid-scale vertical
731latent heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td>
732<td style="vertical-align: top;">Resolved vertical latent
733heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
734<td style="vertical-align: top;">Total vertical latent
735heat
736flux (w"qv" + w*qv*) (in kg/kg m/s).</td> </tr> <tr>
737<td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
738<td style="vertical-align: top;">Subgrid-scale vertical
739scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td>
740</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td>
741<td style="vertical-align: top;">Resolved vertical scalar
742concentration flux (in kg/m<sup>3</sup>)</td> </tr>
743<tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
744<td style="vertical-align: top;">Total vertical scalar
745concentration flux (w"s" + w*s*) (in kg/m<sup>3 </sup>m/s).</td>
746</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td>
747<td style="vertical-align: top;">Vertical flux of
748perturbation energy (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
749<td style="vertical-align: top;">Variance of the
750u-velocity
751component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
752<td style="vertical-align: top;">Variance of the
753v-velocity
754component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
755<td style="vertical-align: top;">Variance of the potential
756temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
757<td style="vertical-align: top;">Variance of the potential
758temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
759<td style="vertical-align: top;">Third moment of the
760w-velocity component (resolved)</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
761<td style="vertical-align: top;">Skewness of the
762w-velocity
763component (resolved, S<sub>w</sub>
764= W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td>
765</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td>
766<td style="vertical-align: top;">Third moment (resolved)</td>
767</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td>
768<td style="vertical-align: top;">Third moment (resolved)</td>
769</tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*/dz</i></font></td>
770<td style="vertical-align: top;">Energy production by
771shear
772(resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*/dz</i></font></td>
773<td style="vertical-align: top;">Energy production by
774turbulent transport of pressure
775fluctuations (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
776<td style="vertical-align: top;">Energy production by
777transport of resolved-scale TKE</td> </tr> </tbody>
778</table> <br>
779Beyond that, initial profiles (t=0) of some variables can be also be
780output (this output is only done once
781with the first plot output and not repeated with the profile output at
782later
783times). The names of these profiles result from the ones specified
784above leaded by a hash "#".&nbsp; Allowed values are:<br> <ul>
785<p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
786<i>#km</i>, <i>#kh</i>, <i>#l</i></p>
787</ul> <p>These initial profiles have been either set by
788the user or
789have been calculated by a 1d-model prerun.<br> </p>In case
790of ASCII data output to local file PLOT1D_DATA,
791PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
792which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>.
793Profiles can be directly plotted with <span style="font-weight: bold;">profil</span>
794using these two files. The
795plot layout is
796steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters
797are determined by
798a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>,
799<a href="chapter_4.2.html#profile_rows">profile_rows</a>,
800<a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
801<a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
802etc.) All parameter values can be changed by editing the parameter
803input
804file. <br><br>Further details about plotting vertical
805profiles with <span style="font-weight: bold;">profil </span>can
806be found in <a href="chapter_4.5.2.html">chapter
8074.5.2</a></td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
808<br> <b>_each_pe</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
809<td style="vertical-align: top;">Output 2d cross section
810data by one or
811all processors.&nbsp; <p>In runs with several processors, by
812default, each processor
813outputs cross section data of its subdomain&nbsp;into an individual
814file. After PALM
815has finished, the contents of these files have to be sampled into one
816file<span style="font-weight: bold;"></span> using
817the program <tt>combine_plot_fields.x</tt>.&nbsp; </p>
818<p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
819= <i>.F.,</i>
820the respective data is gathered on PE0 and output is done directly
821into one file, so <tt>combine_plot_fields.x</tt> does not
822have to be
823called. However, in case of very large numbers of horizontal
824gridpoints, sufficient
825memory is required on PE0. </p> </td> </tr>
826<tr> <td style="vertical-align: top;"> <p><a name="disturbance_amplitude"></a><b>disturbance<br>
827_amplitude</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.25</i></td>
828<td style="vertical-align: top;"> <p>Maximum
829perturbation amplitude of the random perturbations
830imposed to the horizontal velocity field (in m/s).&nbsp; </p>
831<p>The parameter <a href="#create_disturbances">create_disturbances</a>
832describes how to impose random perturbations to the horizontal velocity
833field. Since the perturbation procedure includes two filter operations,
834the amplitude assigned by <b>disturbance_amplitude</b> is
835only an
836approximate value of the real magnitude of the perturbation.</p> </td>
837</tr> <tr> <td style="vertical-align: top;">
838<p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
839<br> <b>_limit</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.01</i></td>
840<td style="vertical-align: top;"> <p lang="en-GB">Upper
841limit value of the perturbation energy of
842the velocity field used as a criterion for imposing random
843perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
844</p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
845describes how to impose
846random perturbations to the horizontal velocity field. The perturbation
847energy is defined as the volume average (over the total model domain)
848of the squares of the deviations of the velocity components from the
849mean flow (horizontal average). If the perturbation energy exceeds the
850assigned value, random perturbations to the fields of horizontal
851velocities are imposed no more. The value of this parameter usually
852must be determined by trial and error (it depends e.g. on the total
853number of grid points).</span> </font> </p> </td>
854</tr> <tr> <td style="vertical-align: top;">
855<p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
856</td> <td style="vertical-align: top;">R</td>
857<td style="vertical-align: top;"><i>zu(3)</i></td>
858<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
859limit of the vertical range for which random perturbations are to be
860imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
861</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This
862parameter must hold the condition zu<i>(3)</i> &lt;= <b>disturbance_level_b</b>
863&lt;= <i>zu(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">.
864Additionally, <b>disturbance_level_b</b>
865&lt;= </font></span><a href="#disturbance_level_t"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_t</font></span></a>
866<span lang="en-GB"><font face="Thorndale, serif">must
867also hold. <br> </font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">The
868parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
869describes how to impose
870random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
871</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
872</td> <td style="vertical-align: top;">R</td>
873<td style="vertical-align: top;"><i>zu(nz/3)</i></td>
874<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
875limit of the vertical range for which random perturbations are to be
876imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
877</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This
878parameter must hold the condition <b>disturbance_level_t</b>
879&lt;= zu<i>(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">.
880Additionally, </font></span><a href="#disturbance_level_b"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_b</font></span></a>
881<span lang="en-GB"><font face="Thorndale, serif">&lt;=
882<b>disturbance_level_t</b>
883must also hold.<br> </font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">The
884parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
885describes how to impose
886random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
887</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
888</td> <td style="vertical-align: top;">L<br> </td>
889<td style="vertical-align: top;">.F.<br> </td>
890<td style="vertical-align: top;"> <p>Output of 2d
891cross section data at the beginning of a run.&nbsp; </p> <p>The
892temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>)
893are usually determined with parameters <a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_xy</a>, <a href="chapter_4.2.html#dt_do2d_xz">dt_do2d_xz</a>
894and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>.
895By assigning <b>do2d_at_begin</b> = <i>.T.</i>
896an additional output
897will be made at the
898beginning of a run (thus at the time t = 0 or at the respective
899starting times of restart runs).</p> </td> </tr> <tr>
900<td style="vertical-align: top;"> <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
901</td> <td style="vertical-align: top;">L<br> </td>
902<td style="vertical-align: top;">.F.<br> </td>
903<td style="vertical-align: top;">Output of 3d volume data
904at the beginning
905of a run.<br><br>The temporal intervals of output times of
9063d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
907is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>.
908By assigning <b>do3d_at_begin</b> = <i>.T.</i>
909an additional output
910will be made at the
911beginning of a run (thus at the time t = 0 or at the respective
912starting times of restart runs).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
913</td> <td style="vertical-align: top;">L<br> </td>
914<td style="vertical-align: top;">.F.<br> </td>
915<td style="vertical-align: top;"> <p>Output of data
916for 3d plots in compressed form.&nbsp; </p> <p>This
917parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
918= <span style="font-style: italic;">'avs'</span>.</p><p>Output
919of 3d volume data may need huge amounts of disc storage
920(up to several Terabytes ore more). Data compression can serve to
921reduce this requirement. PALM is able to output 3d data in compressed
922form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span>
923= <span style="font-style: italic;">.T.</span> is
924assigned. This
925yields a loss of accuracy, but the file size is clearly reduced. The
926parameter <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>
927can be used to separately define the number of significant digits for
928each quantity.<br> </p> <p>So far compressed data
929output is only possible for Cray-T3E
930machines. Additional information for
931handling compressed data is given in <a href="chapter_4.5.6.html">chapter
9324.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_precision"></a><b>do3d_precision</b></p>
933</td> <td style="vertical-align: top;">C *
9347&nbsp; <br>
935&nbsp; (100)</td> <td style="vertical-align: top;">see
936right<br> </td> <td style="vertical-align: top;">
937<p>Significant digits in case of compressed data
938output.&nbsp; </p> <p>This parameter only applies for
939&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
940= <span style="font-style: italic;">'avs'</span>.</p><p>In
941case that data compression is used for output of 3d data
942(see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>),
943this parameter determines the number of significant digits
944which are to be output.<br> </p> <p>Fewer digits
945clearly reduce the amount
946of data. Assignments have to be given separately for each individual
947quantity via a character string of the form <span style="font-style: italic;">'&lt;quantity
948name&gt;&lt;number of
949significant digits&gt;'</span>, e.g. <span style="font-style: italic;">'pt2'</span>.
950Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a>
951are admitted. Up to 9 significant digits are allowed (but large values
952are not very reasonable
953because they do not effect a significant compression).<br> </p>
954<p>The default assignment is <span style="font-weight: bold;">do3d_precision</span>
955= <span style="font-style: italic;">'u2'</span>, <span style="font-style: italic;">'v2'</span>, <span style="font-style: italic;">'w2'</span>, <span style="font-style: italic;">'p5'</span>, <span style="font-style: italic;">'pt2'</span>.</p> </td>
956</tr>
957<tr> <td style="vertical-align: top;"> <p><a name="dt_laufparameter"></a><b>dt</b></p>
958</td> <td style="vertical-align: top;">R</td>
959<td style="vertical-align: top;"><i>variable</i></td>
960<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Time
961step to be used by the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
962</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This parameter</font></span>
963<font face="Thorndale, serif"><span lang="en-GB">is
964described in
965detail with the initialization parameters (see</span></font><span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB">).
966Additionally, it may be
967used as a run parameter and then applies to all restart runs (until it
968is changed again). A switch from a constant time step to a variable
969time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span>
970</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
971</td> <td style="vertical-align: top;">R<br> </td>
972<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
973<td style="vertical-align: top;">Temporal interval
974of&nbsp;data which are subject to temporal averaging (in s).<br><br>By
975default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>
976are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span>
977&gt; <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
978the number of time levels entering the average can be minimized. This
979reduces the CPU-time of a run but may worsen the quality of the
980average's statistics.<br><br><font face="Thorndale, serif"><span lang="en-GB">With
981variable time step (see <span style="font-weight: bold;">dt</span>),
982the number of time levels entering the average can vary from one
983averaging interval to the next (for a more detailed explanation see </span></font><font><a href="#averaging_interval"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval</font></span></a>)</font><font face="Thorndale, serif"><span lang="en-GB">. It
984is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> /
985MAX(<span style="font-weight: bold;"> dt_averaging_input</span>,
986<span style="font-weight: bold;">dt</span>) (which
987gives a more or less exact value if a fixed timestep is used and if
988this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font>&nbsp;
989<br><br><span style="font-weight: bold;">Example:</span><br>With
990an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> =
991<span style="font-style: italic;">10.0</span>,
992the time levels entering the average have a (minimum) distance of 10.0
993s (their distance may of course be larger if the current timestep is
994larger than 10.0 s), so the average is calculated from the data of
995(maximum) 10 time levels.<br><br><font face="Thorndale, serif"><span lang="en-GB">It
996is allowed
997to change <b>dt_averaging_input</b> during a job chain. If
998the last averaging
999interval of the run previous to the change could not be completed (i.e.
1000has to be finished in the current run), the individual profiles and/or
1001spectra entering the averaging are not uniformly distributed over the
1002averaging interval.<br><br></span></font>Parameter&nbsp;<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>&nbsp;can
1003be used to define&nbsp;a different temporal interval&nbsp;for
1004vertical profile data and spectra.<br> </td> </tr>
1005<tr> <td style="vertical-align: top;"> <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
1006</td> <td style="vertical-align: top;">R</td>
1007<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>averaging_<br>input</a></span></td>
1008<td style="vertical-align: top;"> <p lang="en-GB">Temporal
1009interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
1010profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
1011</font></font> </p> <p>By default, data from
1012each timestep within the interval defined by<font face="Thorndale, serif"><span lang="en-GB"> </span></font><a href="#averaging_interval_pr"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_pr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><span lang="en-GB"><font face="Thorndale, serif">and </font></span><a href="#averaging_interval_sp"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_sp</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> </font></span>are
1013used for calculating the temporal average.&nbsp;By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span>
1014&gt; <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
1015the number of time levels entering the average can be minimized. This
1016reduces the CPU-time of a run but may worsen the quality of the
1017average's statistics. <span lang="en-GB"><font face="Thorndale, serif"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span></font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><br> </p><p>For
1018more explanations see parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font></p></td>
1019</tr> <tr> <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
1020</td> <td style="vertical-align: top;">R<br> </td>
1021<td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
1022</td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
1023at which&nbsp;data (3d volume data (instantaneous or time
1024averaged),
1025cross sections (instantaneous or time averaged), vertical profiles,
1026spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
1027<span lang="en-GB"><font face="Thorndale">If
1028data output&nbsp;is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">, <a href="#data_output_pr">data_output_pr</a>, <a href="#data_output_sp">data_output_sp</a>, and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
1029parameter can be used to
1030assign the temporal interval at which these data shall be
1031output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
1032simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>,
1033which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
1034time is the beginning of the simulation, i.e. output
1035takes place at times t = <b>skip_time_data_output +
1036dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
1037+ 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
1038+ 3*<b>dt_data_output</b>,
1039etc. Since output is only done at the discrete time levels given by
1040the&nbsp;timestep used, the actual output times can slightly
1041deviate
1042from these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br>Individual temporal
1043intervals for the different output quantities can be assigned using
1044parameters <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="dt_do2d_xz">dt_do2d_xz</a>, <a href="#dt_do2d_yz">dt_do2d_yz</a>, <a href="#dt_dopr">dt_dopr</a>, <a href="#dt_dosp">dt_dosp</a>,
1045and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span>
1046</td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
1047</td> <td style="vertical-align: top;">R<br> </td>
1048<td style="vertical-align: top;"><i>value of
1049&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i>
1050</td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
1051at which time averaged 3d volume data and/or 2d cross section data
1052shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p><span lang="en-GB"><font face="Thorndale">If data
1053output of time averaged 2d and 3d data is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>&nbsp;<span lang="en-GB"><font face="Thorndale">and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
1054parameter can be used to
1055assign the temporal interval at which they shall be
1056output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
1057simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>,
1058which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
1059time is the beginning of the simulation, i.e. output
1060takes place at times t = <b>skip_time_data_output_av +
1061dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
1062+ 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
1063+ 3*<b>dt_data_output_av</b>,
1064etc. Since output is only done at the discrete time levels given by
1065the&nbsp;timestep used, the actual output times can slightly
1066deviate from
1067these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br></font></span>The
1068length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td>
1069</tr>
1070<tr> <td style="vertical-align: top;"> <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
1071</td> <td style="vertical-align: top;">R</td>
1072<td style="vertical-align: top;"><i>9999999.9</i></td>
1073<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1074interval</font> at which random
1075perturbations are to be imposed on the horizontal velocity field
1076(</font>in <font face="Thorndale">s).&nbsp; </font>
1077</p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
1078describes how to impose
1079random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
1080</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
1081</td> <td style="vertical-align: top;">R</td>
1082<td style="vertical-align: top;"><i>value of
1083&nbsp;<a href="#dt_data_output">dt_data_<br>output</a></i></td>
1084<td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale">Temporal
1085interval at
1086which data&nbsp;of vertical profiles shall be output (to local
1087file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
1088or/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
1089<span lang="en-GB"><font face="Thorndale">s).&nbsp;
1090</font></span> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
1091horizontally averaged vertical profiles is switched on (see </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
1092parameter can be used to
1093assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> </font></span><span lang="en-GB"><font face="Thorndale">Output can
1094be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has
1095zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
1096time is the beginning
1097of the simulation, thus t = 0,&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">i.e. output
1098takes place at times t = <b>skip_time_dopr + dt_dopr</b>, <span style="font-weight: bold;">skip_time_dopr</span> + 2*<b>dt_dopr</b>,
1099<span style="font-weight: bold;">skip_time_dopr</span>
1100+ 3*<b>dt_dopr</b>,
1101etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
1102profiles can not be calculated for times lying within a time step
1103interval, the output times can deviate from these theoretical values.
1104If a time step ranges from t = 1799.8 to t = 1800.2, then in the
1105example above the output would take place at t = 1800.2. In general,
1106the output always lie between t = 1800.0 and t = 1800.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If the
1107model uses a variable time step, these
1108deviations from the theoretical output times will of course be
1109different for each output time.<br> </font></span></p>
1110<p><span lang="en-GB"><font face="Thorndale">In
1111order to
1112guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">,&nbsp;
1113<span style="font-weight: bold;">end_time</span>
1114should be equal or a little bit
1115larger than the respective theoretical output time. For example, if <b>dt_dopr</b>
1116= <i>900.0</i><span style="font-style: italic;">
1117</span>and 3600.0
1118seconds are to be simulated, then <b>end_time</b>
1119&gt;= 3600.0 should be chosen.</font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span>&nbsp; </font></span>
1120</p> <p><span lang="en-GB"><font face="Thorndale">A selection of
1121profiles to be output can be done via parameter </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">.&nbsp;</font></span>
1122</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
1123</td> <td style="vertical-align: top;">R<br> </td>
1124<td style="vertical-align: top;"><i>9999999.9</i></td>
1125<td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
1126interval</font> at which data <font face="Thorndale">of
1127vertical
1128profiles 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
1129<span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
1130</p> <p>T<span lang="en-GB"></span><a href="chapter_4.2.html#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
1131parameter can be used to
1132assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
1133time is the beginning
1134of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b>
1135= 1800.0,
1136then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since
1137profiles can not be calculated for times lying within a time step
1138interval, the output times can deviate from these theoretical values.
1139If a time step ranges from t = 1799.8 to t = 1800.2, then in the
1140example above the output would take place at t = 1800.2. In general,
1141the output always lie between t = 1800.0 and t = 1800.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a> <span lang="en-GB"><font face="Thorndale">(numbers
1142are related to
1143the
1144example above). If the model uses a variable time step, these
1145deviations from the theoretical output times will of course be
1146different for each output time.<br> </font></span></p>
1147<p><span lang="en-GB"><font face="Thorndale">In
1148order to
1149guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">,&nbsp;
1150<span style="font-weight: bold;">end_time</span>
1151should be a little bit
1152larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b>
1153= <i>900.0</i><span style="font-style: italic;">
1154</span>and 3600.0
1155seconds are to be simulated, then it should be at least&nbsp; <b>end_time</b>
1156&gt; 3600.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If
1157variable time steps are used
1158(which is the default), <span style="font-weight: bold;">dt</span>
1159should be properly estimated.&nbsp; </font></span> </p>
1160<p><span lang="en-GB"><font face="Thorndale">Data
1161and output
1162format of the file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a>
1163<span lang="en-GB"><font face="Thorndale">is
1164internally fixed. In this file
1165the profiles of the most important model variables are arranged in
1166adjacent columns.</font></span> </p> </td> </tr>
1167<tr> <td style="vertical-align: top;"> <p><a name="dt_dots"></a><b>dt_dots</b></p>
1168</td> <td style="vertical-align: top;">R</td>
1169<td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
1170<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1171interval</font> at which&nbsp;time series data shall be
1172output (</font>in <font face="Thorndale">s).&nbsp;</font>
1173</p> <p>The default interval for the output of timeseries
1174is calculated as shown below (this tries to minimize the number of
1175calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p><p style="font-family: Courier New,Courier,monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1176IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
1177== 0.0 )&nbsp; THEN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1178<span style="font-weight: bold;">dt_dots</span> =
1179MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1180ELSE<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1181<span style="font-weight: bold;">dt_dots</span> =
1182MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
1183)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1184ENDIF</p><p>This parameter can be used to
1185assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
1186time is the beginning of
1187&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
11882*<b>dt_dots</b>, 3*<b>dt_dots</b>, etc. The
1189actual output times can
1190deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).&nbsp;
1191Is <b>dt_dots</b> &lt; </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then data
1192of the time series are
1193written after each time step (if this is requested it should be <b>dt_dots</b>
1194= <i>0</i>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">The default
1195value of <span style="font-weight: bold;">dt_dots</span>
1196is calculated as follows:</font></span></p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1197IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
1198== 0.0 )&nbsp; THEN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1199<span style="font-weight: bold;">dt_dots</span> =
1200MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1201ELSE<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1202<span style="font-weight: bold;">dt_dots</span> =
1203MIN( <span style="font-weight: bold;">dt_run_control</span>,
1204<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
1205)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1206ENDIF<br><br>(which minimizes the number of calls of
1207routine flow_statistics).<br><p>By default time series data
1208is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>.
1209Because of the default settings of <span style="font-weight: bold;">dt_dots</span>,
1210it will&nbsp;generally be created for each model run. The file's
1211format is NetCDF.&nbsp; Further details about processing NetCDF
1212data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>The
1213file contains the following timeseries quantities (the first column
1214gives the name of the quantities as used in the NetCDF file):<br><table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="font-style: italic; vertical-align: middle;">E<br>
1215</td> <td style="vertical-align: top;">Total
1216kinetic energy of
1217the flow (in m<sup>2</sup>/s<sup>2</sup>)
1218(normalized with respect to the total number of grid points).</td>
1219</tr> <tr> <td style="font-style: italic; vertical-align: middle;">E*<br>
1220</td> <td style="vertical-align: top;">Perturbation
1221kinetic
1222energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
1223</sup>(normalized
1224with respect to the total number of grid
1225points)</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">dt<br>
1226</td> <td style="vertical-align: top;">Time step
1227size (in s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
1228<td style="vertical-align: top;">Friction velocity (in
1229m/s)
1230(horizontal average).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
1231<td style="vertical-align: top;">Vertical velocity scale
1232of
1233the CBL (in m/s) (horizontal average)</td> </tr> <tr>
1234<td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
1235<td style="vertical-align: top;">Temperature
1236scale (Prandtl layer), defined as <i>w"pt"0
1237/&nbsp;</i><i>u<sub>*</sub></i>
1238(horizontal
1239average) (in K).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">umax<br>
1240</td> <td style="vertical-align: top;">Maximum
1241u-component of the
1242velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">vmax<br>
1243</td> <td style="vertical-align: top;">Maximum
1244v-component of the
1245velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wmax<br>
1246</td> <td style="vertical-align: top;">Maximum
1247w-component of the
1248velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_old<br>
1249</td> <td style="vertical-align: top;">Divergence
1250of the velocity
1251field before the pressure
1252solver has been called (normalized with respect to the total number of
1253grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_new</td>
1254<td style="vertical-align: top;">Divergence of the
1255velocity
1256field after the pressure
1257solver has been called (normalized with respect to the total number of
1258grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
1259<td style="vertical-align: top;">Height of the convective
1260boundary layer (horizontal average)
1261determined by the height of the minimum sensible heat flux (in m).</td>
1262</tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
1263<td style="vertical-align: top;">Height of the convective
1264boundary layer (horizontal average)
1265determined by the temperature profile (in m).</td> </tr> <tr>
1266<td style="vertical-align: top; font-style: italic;">w"pt"0</td>
1267<td style="vertical-align: top;">Subgrid-scale sensible
1268heat flux near the surface (horizontal
1269average)
1270between z = 0 and z = z<sub>p</sub> = zu(1) (there it
1271corresponds to
1272the total heat flux) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w"pt"</td>
1273<td style="vertical-align: top;">Subgrid-scale heat flux
1274(horizontal average) for z = zw(1) (in K
1275m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wpt</td>
1276<td style="vertical-align: top;">Total heat flux
1277(horizontal average) for z = zw(1) (in K m/s).</td> </tr> <tr>
1278<td style="vertical-align: top; font-style: italic;">pt(0)</td>
1279<td style="vertical-align: top;">Potential temperature at
1280the surface (horizontal average) (in K).</td> </tr> <tr>
1281<td style="vertical-align: top; font-style: italic;">pt(zp)</td>
1282<td style="vertical-align: top;">Potential temperature for
1283z = zu(1) (horizontal average) (in K).</td> </tr> <tr>
1284<td style="vertical-align: top; font-style: italic;">splptx</td>
1285<td style="vertical-align: top;">Percentage of grid points
1286using upstream scheme along x with
1287upstream-spline advection switched on.</td> </tr> <tr>
1288<td style="vertical-align: top; font-style: italic;">splpty</td>
1289<td style="vertical-align: top;">Percentage of grid points
1290using upstream scheme along y with
1291upstream-spline
1292advection switched on.</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">splptz</td>
1293<td style="vertical-align: top;">Percentage of grid points
1294using upstream scheme along z with
1295upstream-spline
1296advection switched on.<br> </td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">L</td>
1297<td style="vertical-align: top;">Monin-Obukhov length.</td>
1298</tr> </tbody> </table><br>Additionally, the
1299user can add his own timeseries quantities to the file, by using the
1300user-interface subroutines<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_init">user_init</a> </span>and<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_statistics">user_statistics</a></span>.
1301These routines contain (as comment lines) a simple example how to do
1302this.<br><br>Time series data refers to the total
1303domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
1304However, the following time series always present the values of the
1305total model domain (even with output for subdomains): <i>umax</i>,
1306<i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
1307<i>div_new</i>.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
1308</td> <td style="vertical-align: top;">R</td>
1309<td style="vertical-align: top;"><i>value of
1310&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
1311<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1312interval</font> at which&nbsp;horizontal cross section data
1313shall be output (</font>in <font face="Thorndale">s).&nbsp;
1314</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
1315horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
1316<span lang="en-GB"><font face="Thorndale">and
1317</font></span><a href="#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
1318parameter can be used to
1319assign the temporal interval at which cross section data shall be
1320output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
1321simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>,
1322which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
1323time is the beginning of the simulation, i.e. output
1324takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>,
1325<span style="font-weight: bold;">skip_time_do2d_xy</span>
1326+ 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span>
1327+ 3*<b>dt_do2d_xy</b>,
1328etc. The actual output times can deviate from these theoretical values
1329(see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
1330</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
1331has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
1332the time t = 0 or at the
1333respective starting times of restart runs).</font></span> </p>
1334</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
1335</td> <td style="vertical-align: top;">R</td>
1336<td style="vertical-align: top;"><i>value of
1337&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
1338<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1339interval</font> at which&nbsp;vertical cross sections data
1340(xz) shall be output (</font>in <font face="Thorndale">s).&nbsp;
1341</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
1342horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
1343<span lang="en-GB"><font face="Thorndale">and
1344</font></span><a href="#section_xz"><span lang="en-GB"><font face="Thorndale">section_xz</font></span></a><span lang="en-GB"><font face="Thorndale">),
1345this parameter can be used to assign the temporal interval at which
1346cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
1347be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which
1348has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
1349the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz
1350+ dt_do2d_xz</b>,
1351<span style="font-weight: bold;">skip_time_do2d_xz</span>
1352+ 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span>
1353+ 3*<b>dt_do2d_xz</b>, etc. The actual output times
1354can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
1355</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
1356has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
1357the time t = 0 or at the
1358respective starting times of restart runs).</font></span> </p>
1359</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
1360</td> <td style="vertical-align: top;">R</td>
1361<td style="vertical-align: top;"><i>value of
1362&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
1363<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1364interval</font> at which&nbsp;vertical cross section data
1365(yz) shall be output (</font>in s<font face="Thorndale">).&nbsp;
1366</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
1367horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
1368<span lang="en-GB"><font face="Thorndale">and
1369</font></span><a href="#section_yz"><span lang="en-GB"><font face="Thorndale">section_yz</font></span></a><span lang="en-GB"><font face="Thorndale">),
1370this parameter can be used to assign the temporal interval at which
1371cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
1372be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which
1373has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
1374time is the beginning of
1375the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz
1376+ dt_do2d_yz</b>,
1377<span style="font-weight: bold;">skip_time_do2d_yz</span>
1378+ 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz
1379</span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
1380times
1381can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
1382</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
1383has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
1384the time t = 0 or at the
1385respective starting times of restart runs).</font></span> </p>
1386</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
1387</td> <td style="vertical-align: top;">R</td>
1388<td style="vertical-align: top;"><i>value of
1389&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
1390<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1391interval</font> at which 3d volume data shall be output (</font>in
1392<font face="Thorndale">s).&nbsp; </font> </p>
1393<p><span lang="en-GB"><font face="Thorndale">If
1394output of
13953d-volume data is switched on (see </font></span><font><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>)<span style="font-family: thorndale;">, this parameter can be used
1396to assign
1397th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
1398interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
1399be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has
1400zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
1401time is the
1402beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d
1403+ dt_do3d</b>,
1404<span style="font-weight: bold;">skip_time_do3d</span>
1405+ 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span>
1406+ 3*<b>dt_do3d</b>, etc. The actual output times can
1407deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). <br>
1408</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do3d_at_begin"><span lang="en-GB"><font face="Thorndale">do3d_at_begin</font></span></a>
1409has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
1410the time t = 0 or at the
1411respective starting times of restart runs).</font></span> </p>
1412</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_restart"></a><b>dt_restart</b></p>
1413</td> <td style="vertical-align: top;">R</td>
1414<td style="vertical-align: top;"><i>9999999.9</i></td>
1415<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1416interval</font> at which a new
1417restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p> <p><span lang="en-GB"><font face="Thorndale">For a
1418description
1419how to assign restart times manually see run time parameter </font></span><a href="#restart_time"><span lang="en-GB"><font face="Thorndale">restart_time</font></span></a><span lang="en-GB"><font face="Thorndale">. <span style="font-weight: bold;">dt_restart</span>
1420does not show any effect, if <span style="font-weight: bold;">restart_time</span>
1421has not been set.</font></span> </p> </td> </tr>
1422<tr> <td style="vertical-align: top;"> <p><a name="dt_run_control"></a><b>dt_run_control</b></p>
1423</td> <td style="vertical-align: top;">R</td>
1424<td style="vertical-align: top;"><i>60.0</i></td>
1425<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
1426interval</font> at which run control
1427output is to be made (</font>in <font face="Thorndale">s).&nbsp;
1428</font> </p> <p><span lang="en-GB"><font face="Thorndale">Run control
1429information is output to the local ASCII-file </font></span><a href="chapter_3.4.html#RUN_CONTROL"><span lang="en-GB"><font face="Thorndale">RUN_CONTROL</font></span></a><span lang="en-GB"><font face="Thorndale">. At each
1430output time, one line
1431with information about the size of the time step, maximum speeds, total
1432kinetic energy etc. is written to this file. Reference time is the
1433beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>,
14342*<b>dt_run_control</b>, 3*<b>dt_run_control</b>,
1435etc., and always at
1436the beginning of a model run (thus at the time t = 0 or at the
1437respective starting times of restart runs). The actual output times can
1438deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
1439</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Run control
1440information is output after each time step can be achieved via <b>dt_run_control</b>
1441= <i>0.0</i>.</font></span> </p> </td>
1442</tr> <tr> <td style="vertical-align: top;">
1443<p><a name="end_time"></a><b>end_time</b></p>
1444</td> <td style="vertical-align: top;">R</td>
1445<td style="vertical-align: top;"><i>0.0</i></td>
1446<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Simulation time of the 3D
1447model (</font>in <font face="Thorndale">s).&nbsp;
1448</font> </p> <p><span lang="en-GB"><font face="Thorndale">The simulation time
1449is starting from the beginning of the initialization run (t = 0), not
1450starting from the beginning of the respective restart run.</font></span>
1451</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="force_print_header"></a><b>force_print_header</b></p>
1452</td> <td style="vertical-align: top;">L</td>
1453<td style="vertical-align: top;"><i>.F.</i></td>
1454<td style="vertical-align: top;"> <p>Steering of
1455header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
1456</p> <p>By default, informations about the model
1457parameters in use are
1458output to the beginning of file RUN_CONTROL for initial runs only
1459(these informations are identical to that which are output to the local
1460file <a href="chapter_3.4.html#HEADER">HEADER</a>).
1461With <b>force_print_header</b> = <i>.T.</i>,
1462these informations are
1463also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
1464at restart runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
1465</td> <td style="vertical-align: top;">I</td>
1466<td style="vertical-align: top;"><i>-1</i></td>
1467<td style="vertical-align: top;"> <p>Number of
1468cycles to be used with the multi-grid scheme.<br> <br>
1469This parameter determines the number of cycles to be carried out in the
1470multi-grid method used for solving the Poisson equation for
1471perturbation pressure (see <a href="#psolver">psolver</a>).
1472The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br>
1473</p> <br>
1474By default (<b>mg_cyles</b> = <i>- 1</i>), the
1475number of cycles
1476depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>)
1477and may vary from time step to time step. In this case, the CPU time
1478for a run will be difficult to estimate, since it heavily depends on
1479the total number of the cycles to be carried out.<br> <br>
1480By assigning <b>mg_cycles</b> a value (&gt;=<span style="font-style: italic;">1</span>), the number of
1481cycles can be
1482fixed so that the CPU time can be clearly estimated. <br> <br>
1483<b>Note:</b> When using a fixed number of cycles, the user
1484must
1485examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
1486regularly to check whether the divergence of the velocity field is
1487sufficiently reduced by the pressure solver. It should be reduced at
1488least by two orders of magnitude. For cyclic boundary conditions along
1489both horizontal directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
1490and <a href="chapter_4.1.html#bc_ns">bc_ns</a>) <span style="font-weight: bold;">mg_cycles</span> = <span style="font-style: italic;">2</span> is typically a
1491good choice, for
1492non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span>
1493= <span style="font-style: italic;">4</span> may be
1494sufficient.</td> </tr> <tr> <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
1495level</b></td> <td style="vertical-align: top;">I</td>
1496<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;">Grid
1497level at which data shall be gathered on PE0.<br> <br>
1498In case of a run using several PEs and the multigrid method for solving
1499the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
1500the value of this parameter defines on which grid level the data are
1501gathered on PE0 in order to allow for a further coarsening of the grid.
1502The finest grid defines the largest grid level. By default, the
1503gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
1504It is only possible to gather data from a level larger than the one
1505determined automatically. A test run may be neccessary to determine
1506this level.</td> </tr> <tr> <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</span><br>
1507</td> <td style="vertical-align: top;">L<br> </td>
1508<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td>
1509<td style="vertical-align: top;">NetCDF files will have 64
1510bit offset format.<br><br>By
1511default, the maximum file size of the NetCDF files opened by PALM is 2
1512GByte. Using netcdf_64bit = .TRUE. allows file sizes larger than 2
1513GByte.<br><br>The 64 bit offset format can be separately
1514switched off for those NetCDF files containing 3d volume date (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
1515<span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>)
1516using <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br><br><span style="font-weight: bold;">Warning:</span><br>Some
1517(PD or commercial) software may not support the 64 bit offset format.<br>
1518</td> </tr>
1519<tr><td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;">.T.</td><td style="vertical-align: top;">NetCDF files containing 3d
1520volume data will have 64 bit offset format.<br><br>This
1521switch&nbsp;only comes into effect if <a href="#netcdf_64bit">netcdf_64bit</a>
1522= .TRUE.. It allows to switch off separately the 64 bit offset format
1523for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
1524<span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>).</td></tr><tr>
1525<td style="vertical-align: top;"> <p><a name="ngsrb"></a><b>ngsrb</b></p> </td>
1526<td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>2</i></td>
1527<td style="vertical-align: top;">Grid
1528level at which data shall be gathered on PE0.<br> <br>
1529In case of a run using several PEs and the multigrid method for solving
1530the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
1531the value of this parameter defines on which grid level the data are
1532gathered on PE0 in order to allow for a further coarsening of the grid.
1533The finest grid defines the largest grid level. By default, the
1534gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
1535It is only possible to gather data from a level larger than the one
1536determined automatically. A test run may be neccessary to determine
1537this level.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
1538</td> <td style="vertical-align: top;">I</td>
1539<td style="vertical-align: top;"><span style="font-style: italic;">0</span><br> </td>
1540<td style="vertical-align: top;"> <p>Determines the
1541subdomain from which the normalization
1542quantities are calculated.&nbsp; </p> <p>If output
1543data of the horizontally averaged vertical profiles
1544(see <a href="#data_output_pr">data_output_pr</a>)
1545is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>,
1546<a href="#cross_normalized_y">cross_normalized_y</a>),
1547the respective normalization quantities are by default calculated from
1548the averaged data of the total model domain (<b>normalizing_region</b>
1549= <i>0</i>) and are thus representative for the total
1550domain. Instead
1551of that, normalization quantities can also be calculated for a
1552subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>,
1553where <i>1</i>
1554&lt;= <b>normalizing_region</b> &lt;= <i>9 </i>must
1555hold. These
1556quantities are then used for normalizing of all profiles (even for that
1557of the total domain).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nsor"></a><b>nsor</b></p>
1558</td> <td style="vertical-align: top;">I</td>
1559<td style="vertical-align: top;"><i>20</i></td>
1560<td style="vertical-align: top;"> <p>Number of
1561iterations to be used with the SOR-scheme.&nbsp; </p> <p>This
1562parameter is only effective if the SOR-scheme is selected
1563as pressure solver (<a href="#psolver">psolver</a>
1564= <span style="font-style: italic;">'sor'</span>).
1565The number of
1566iterations necessary for a sufficient convergence of the scheme depends
1567on the grid point numbers and is to be determined by appropriate test
1568runs (the default value will not at all be sufficient for larger grid
1569point numbers). The number of iterations used for the first call of the
1570SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p>
1571</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
1572</td> <td style="vertical-align: top;">I</td>
1573<td style="vertical-align: top;"><i>nz+1</i></td>
1574<td style="vertical-align: top;"> Limits the output of 3d
1575volume data along the vertical direction (grid point index k).<br><br>By
1576default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
1577can be used to limit the output up to a certain vertical grid point
1578(e.g. in order to reduce the amount of output data). It affects all
1579output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output
1580for <span style="font-weight: bold;">dvrp</span>-software,
1581see <a href="#mode_dvrp">mode_dvrp</a>).</td>
1582</tr> <tr> <td style="vertical-align: top;">
1583<p><a name="omega_sor"></a><b>omega_sor</b></p>
1584</td> <td style="vertical-align: top;">R</td>
1585<td style="vertical-align: top;"><i>1.8</i></td>
1586<td style="vertical-align: top;"> <p>Convergence
1587factor to be used with the the SOR-scheme.&nbsp; </p> <p>If
1588the SOR-scheme is selected (<a href="#psolver">psolver</a>
1589= <span style="font-style: italic;">'sor'</span>),
1590this parameter
1591determines the value of the convergence factor, where <i>1.0</i>
1592&lt;= <b>omega_sor</b> &lt; <i>2.0 </i>.
1593The optimum value of <b>omega_sor</b>
1594depends on the number of grid points along the different directions in
1595space. For non-equidistant grids it can only be determined by
1596appropriate test runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="prandtl_number"></a><b>prandtl_number</b></p>
1597</td> <td style="vertical-align: top;">R</td>
1598<td style="vertical-align: top;"><i>1.0</i></td>
1599<td style="vertical-align: top;"> <p>Ratio of the
1600eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).&nbsp;
1601</p> <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
1602this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub>
1603/ K<sub>h</sub>).</p> </td> </tr> <tr>
1604<td style="vertical-align: top;"> <p><a name="profile_columns"></a><b>profile_columns</b></p>
1605</td> <td style="vertical-align: top;">I</td>
1606<td style="vertical-align: top;"><i>3</i></td>
1607<td style="vertical-align: top;"> <p>Number of
1608coordinate systems to be plotted<span style="font-weight: bold;"></span>
1609in one row by <span style="font-weight: bold;">profil</span>.&nbsp;
1610</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1611= <span style="font-style: italic;">'profil'</span>.</p><p>It
1612determines the layout of plots of
1613horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
1614when plotted with the plot software <span style="font-weight: bold;">profil</span>.
1615Generally, the number and sequence of coordinate systems (panels) to be
1616plotted on one page are
1617determined by <a href="#cross_profiles">cross_profiles</a>.
1618<b>profile_columns</b>
1619determines how many panels are to be
1620arranged next to each other in one row (number of columns). The
1621respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>.
1622According to their order given by <a href="#data_output_pr">data_output_pr</a>,
1623the panels are arranged beginning in the top row from left to right and
1624then continued in the following row. If the number of panels cranz
1625&gt; <b>profile_columns</b> * <b>profile_rows</b>,
1626the remaining
1627panels are drawn on an additional page. If cranz &lt; <b>profile_columns</b>,
1628then <b>profile_columns</b> = cranz is automatically set.
1629If
1630row&nbsp; contains any panel, then the value of <b>profile_rows</b>
1631is reduced automatically.</p> </td> </tr> <tr>
1632<td style="vertical-align: top;"> <p><a name="profile_rows"></a><b>profile_rows</b></p>
1633</td> <td style="vertical-align: top;">I</td>
1634<td style="vertical-align: top;"><i>2</i></td>
1635<td style="vertical-align: top;"> <p>Number of rows
1636of coordinate systems to be plotted on one page
1637by <span style="font-weight: bold;">profil</span>.&nbsp;
1638</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1639= <span style="font-style: italic;">'profil'</span>.</p><p>It
1640determines the layout of plots of horizontally averaged
1641profiles. See <a href="#profile_columns">profile_columns</a>.</p>
1642</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psolver"></a><b>psolver</b></p>
1643</td> <td style="vertical-align: top;">C * 10</td>
1644<td style="vertical-align: top;"><i>'poisfft'</i></td>
1645<td style="vertical-align: top;"> <p>Scheme to be
1646used to solve the Poisson equation for the
1647perturbation pressure.&nbsp; </p> <br>
1648The user can choose between the following schemes:<br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>poisfft</i></td>
1649<td style="vertical-align: top;">Direct method using FFT
1650along x and y, solution of a
1651tridiagonal matrix along z, and backward
1652FFT (see Siano, institute reports, volume 54). The FFT routines to be
1653used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
1654This solver is specially optimized for 1d domain decompositions.
1655Vectorization is optimized for domain decompositions along x only.</td>
1656</tr> <tr> <td style="vertical-align: top;">
1657<p><i>poisfft_</i> <br> <i>hybrid</i></p>
1658</td> <td style="vertical-align: top;">Direct
1659method using FFT
1660along x and y, solution of a
1661tridiagonal matrix along z, and backward
1662FFT (see Siano, institute reports, volume 54). The FFT routines to be
1663used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
1664This solver is specially optimized for 1d domain decompositions.
1665Vectorization is optimized for domain decompositions along x only.</td>
1666</tr> <tr> <td style="vertical-align: top;"><i>multigrid</i></td>
1667<td style="vertical-align: top;"> <p>Multi-grid
1668scheme (see Uhlenbrock, diploma thesis). v-
1669and
1670w-cycles (see <a href="#cycle_mg">cycle_mg</a>)
1671are implemented. The convergence of the iterative scheme can be
1672steered by the number of v-/w-cycles to be carried out for each call of
1673the scheme (<a href="#mg_cycles">mg_cycles</a>)
1674and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>)
1675to be carried out on each grid level. Instead the requested accuracy
1676can be given via <a href="#residual_limit">residual_limit</a>.
1677<span style="font-weight: bold;">This is the default!</span>
1678The
1679smaller this limit is, the more cycles have to be carried out in this
1680case and the number of cycles may vary from timestep to timestep.</p>
1681<br>
1682If <a href="#mg_cycles">mg_cycles</a>
1683is set to its optimal value, the computing time of the
1684multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
1685the number of
1686grid points in the three directions
1687of space corresponds to a power-of-two (2<sup>n</sup>)
1688where <i>n</i> &gt;= 5 must hold. With large <i>n,
1689</i>the
1690multi-grid scheme can even be faster than the direct solver (although
1691its accuracy is several orders of magnitude worse, but this does not
1692affect the accuracy of the simulation). Nevertheless, the user should
1693always carry out some test runs in order to find out the optimum value
1694for <a href="#mg_cycles">mg_cycles</a>,
1695because the CPU time of a run very critically depends on this
1696parameter. <p>This scheme requires that the number of grid
1697points of
1698the
1699subdomains (or of the total domain, if only one PE is uesd) along each
1700of the directions can at least be devided once by 2 without rest.</p>
1701With parallel runs, starting from a certain grid level the
1702data of the subdomains are possibly gathered on PE0 in order to allow
1703for a further coarsening of the grid. The grid level for gathering can
1704be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
1705<p>Using this procedure requires the subdomains to be of
1706identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p>
1707</td> </tr> <tr> <td style="vertical-align: top;"><i>sor</i></td>
1708<td style="vertical-align: top;">Successive over
1709relaxation
1710method (SOR). The convergence of
1711this
1712iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>,
1713<a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
1714and <a href="chapter_4.1.html#nsor">nsor</a>.&nbsp;
1715<br>Compared to the direct method and the multi-grid method, this
1716scheme
1717needs substantially
1718more computing time. It should only be used for test runs, e.g. if
1719errors in the other pressure solver methods are assumed.</td> </tr>
1720</tbody> </table> <br>
1721In order to speed-up performance, the Poisson equation is by default
1722only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver
1723at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>).&nbsp;
1724</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
1725<br> <b>_factor</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.0 or</i><br>
1726<i>0.01</i></td> <td style="vertical-align: top;">
1727<p>Factor for Rayleigh damping.&nbsp; </p> <p>A
1728so-called Rayleigh damping is applied to all prognostic
1729variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>.&nbsp;
1730If switched on, variables are forced towards the value of their
1731respective basic states (e.g. the geostrophic wind). The intensity of
1732damping is controlled by the value the <b>rayleigh_damping_factor</b>
1733is assigned to.
1734The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a>
1735and rises according to a sin<sup>2</sup>-function to its
1736maximum value
1737at
1738the top boundary. </p> <p>This method
1739effectively damps gravity waves, caused by boundary layer convection,
1740which may spread out vertically in the inversion layer and which are
1741reflected&nbsp; at the top
1742boundary. This particularly happens with the upstream-spline scheme
1743switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
1744or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>).
1745Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b>
1746= <i>0.01</i>) by default. Otherwise it remains switched
1747off.&nbsp; </p> <p>The Rayleigh damping factor must
1748hold the condition <i>0.0</i>
1749&lt;= <b>rayleigh_damping_factor</b>
1750&lt;= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
1751numerical instabilities.</p> </td> </tr> <tr>
1752<td style="vertical-align: top;"> <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
1753<br> <b>_height</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"> <p><i>2/3 *</i>
1754<br><span style="font-style: italic;">
1755zu</span><i style="font-style: italic;">(nz)</i></p>
1756</td> <td style="vertical-align: top;"> <p>Height
1757where the Rayleigh damping starts (in m).&nbsp; </p> <p>With
1758Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
1759this parameter determines the range where damping is applied. By
1760default, Rayleigh damping will be applied in the upper third of the
1761model
1762domain.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="residual_limit"></a><b>residual_limit</b></p>
1763</td> <td style="vertical-align: top;">R</td>
1764<td style="vertical-align: top;"><i>1.0E-6</i></td>
1765<td style="vertical-align: top;"> <p>Largest
1766residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>).&nbsp;
1767</p> <p>This is a parameter to steer the accuracy of the
1768multi-grid
1769scheme (see <a href="#psolver">psolver</a>).
1770The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>)
1771is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If
1772this
1773is not the case after 1000 cycles, the PALM aborts with a corresponding
1774error message.</p> <p>The reciprocal value of this
1775parameter can be interpreted as
1776a factor by the divergence of the provisional
1777velocity field is approximately reduced after the multi-grid scheme has
1778been applied (thus the default value causes a reduction of the
1779divergence by approx. 6 orders of magnitude).&nbsp; </p> </td>
1780</tr> <tr> <td style="vertical-align: top;">
1781<p><a name="restart_time"></a><b>restart_time</b></p>
1782</td> <td style="vertical-align: top;">R</td>
1783<td style="vertical-align: top;"><i>9999999.9</i></td>
1784<td style="vertical-align: top;"> <p>Simulated time
1785after which a restart run is to be carried out
1786(in s). </p> <p>The simulated time refers to the
1787beginning of the
1788initial run (t = 0), not to the beginning of the respective
1789restart run. Restart runs can additionally be forced to be carried out
1790in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p> <p><span style="font-weight: bold;">Note:</span><br>
1791A successful operation of this parameter requires additional
1792modifications in the <span style="font-weight: bold;">mrun</span>-call
1793for the respective run (see <a href="chapter_3.3.html">chapter
17943.3</a>).<br> </p> <p>The choice of <b>restart_time</b>
1795or <b>dt_restart</b> does
1796not override the automatic start of restart runs in case that the job
1797runs out of CPU time. <br> </p> </td> </tr>
1798<tr> <td style="vertical-align: top;"> <p><a name="section_xy"></a><b>section_xy</b></p>
1799</td> <td style="vertical-align: top;">I(100)<br>
1800</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
1801</td> <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position
1802of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
1803sections (grid point index k).&nbsp; </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output
1804of
1805horizontal cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this
1806parameter can be used to
1807define the position(s) of the cross section(s). Up to 100 positions of
1808cross sections can be selected by assigning <b>section_xy</b>
1809the
1810corresponding vertical grid point index/indices k of the requested
1811cross section(s). The exact location (height level) of the cross
1812section depends on the variable for which the output is made: zu(k) for
1813scalars and horizontal velocities, zw(k) for the vertical velocity.
1814Information about the exact location of the cross section is contained
1815in the NetCDF output file (if the default NetCDF output is switched on;
1816see <a href="#data_output_format">data_output_format</a>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
1817creates the output of horizontal cross sections averaged along z. In
1818the
1819NetCDF output file these (averaged) cross sections are given the
1820z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
1821does not effect the output of horizontal cross sections of variable u<sub>*</sub>
1822and theta<sub>*</sub> and the liquid water path lwp*. For
1823these quantities always only one cross
1824section (for z=zu(1)) is output.</font></span></p><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
1825<span style="font-style: italic;">'iso2d'</span> and
1826if several cross sections are selected (e.g. <b>section_xy</b>
1827= <i>1</i>, <i>10</i>, <i>15</i>),
1828then the respective data are
1829successively written to file. The output order follows the order given
1830by <b>section_xy</b>.&nbsp;</font></span></td>
1831</tr> <tr> <td style="vertical-align: top;">
1832<p><a name="section_xz"></a><b>section_xz</b></p>
1833</td> <td style="vertical-align: top;">I(100)<br>
1834</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
1835<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
1836for&nbsp;output of 2d (xz) vertical cross sections (grid point
1837index j).&nbsp; </font> </p> <span lang="en-GB"><font face="Thorndale">If output of
1838vertical xz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this
1839parameter can be used to
1840define the position(s) of the cross section(s). Up to 100 positions of
1841cross sections can be selected by assigning <b>section_xz</b>
1842the
1843corresponding horizontal grid point index/indices j of the requested
1844cross section(s). The exact position (in y-direction) of the cross
1845section is given by j*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a> <span lang="en-GB"><font face="Thorndale">or (j-0.5)*</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a><span lang="en-GB"><font face="Thorndale">, depending
1846on which grid the output quantity is defined. However, in
1847the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
1848default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
1849no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all
1850positions.<br><br>Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
1851creates the output of vertical cross sections averaged along y. In the
1852NetCDF output file these (averaged) cross sections are given the
1853y-coordinate <span style="font-style: italic;">-1.0</span>.<br></font></span><span lang="en-GB"><font face="Thorndale"><br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
1854<span style="font-style: italic;">'iso2d'</span> and
1855</font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
1856selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>,
1857<i>27</i>),
1858then the respective data are successively written to file. The output
1859order follows the order given by <b>section_xz</b>.</font></span></td>
1860</tr> <tr> <td style="vertical-align: top;">
1861<p><a name="section_yz"></a><b>section_yz</b></p>
1862</td> <td style="vertical-align: top;">I(100)<br>
1863</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
1864<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
1865for&nbsp;output of 2d (yz) vertical cross sections (grid point
1866index i).&nbsp; </font> </p> <span lang="en-GB"><font face="Thorndale">If output of
1867vertical yz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">),
1868this parameter can be used to define the position(s) of the cross
1869section(s). Up to 100 positions of cross sections can be selected by
1870assigning <b>section_yz</b> the corresponding horizontal
1871grid point
1872index/indices i of the requested cross section(s). The exact position
1873(in x-direction) of the cross section is given by i*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a> <span lang="en-GB"><font face="Thorndale">or (i-0.5)*</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a><span lang="en-GB"><font face="Thorndale">, depending
1874on which grid the output quantity is defined.&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">However, in
1875the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
1876default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
1877no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all
1878positions.<br><br></font></span><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_yz</span> = <span style="font-style: italic;">-1</span>
1879creates the output of vertical cross sections averaged along x. In the
1880NetCDF output file these (averaged) cross sections are given the
1881x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
1882<span style="font-style: italic;">'iso2d'</span> and
1883</font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
1884selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the
1885respective data are successively written to file. The output order
1886follows the order given by <b>section_yz</b>.</font></span></td>
1887</tr> <tr> <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
1888</td> <td style="vertical-align: top;">R<br> </td>
1889<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
1890<td style="vertical-align: top;">No data output before
1891this interval has passed (in s).<br><br>This
1892parameter causes that data output activities are starting not before
1893this interval
1894(counting from the beginning of the simulation, t=0) has passed. By
1895default, this
1896applies for output of instantaneous 3d volume data, cross section data,
1897spectra and vertical profile data as well as for temporally averaged 2d
1898and 3d data. Individual intervals can be assigned using parameters <a href="#skip_time_do3d">skip_time_do3d</a>, <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, <a href="#skip_time_dosp">skip_time_dosp</a>,&nbsp;<a href="#skip_time_dopr">skip_time_dopr</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><br><span style="font-weight: bold;">Example:</span><br>If
1899the user has set <a href="#dt_data_output">dt_data_output</a>
1900= <span style="font-style: italic;">3600.0</span>
1901and <span style="font-weight: bold;">skip_time_data_output</span>
1902= <span style="font-style: italic;">1800.0</span>,
1903then the first output will be done at t = 5400 s.<br> </td>
1904</tr> <tr><td style="vertical-align: top;"><a name="skip_time_data_output_av"></a><span style="font-weight: bold;">skip_time_data_output_av</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>data_output</a></span></td><td style="vertical-align: top;">No output of temporally
1905averaged 2d/3d data before this interval has passed (in s).<br><br>This
1906parameter causes that data output activities are starting not before
1907this interval
1908(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
1909the user has set <a href="#dt_data_output_av">dt_data_output_av</a>
1910= <span style="font-style: italic;">3600.0</span>
1911and <span style="font-weight: bold;">skip_time_data_output_av</span>
1912= <span style="font-style: italic;">1800.0</span>,
1913then the first output will be done at t = 5400 s.</td></tr><tr>
1914<td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
1915</td> <td style="vertical-align: top;">R<br> </td>
1916<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
1917</td> <td style="vertical-align: top;">No output of
1918vertical profile data before this interval has passed (in s).<br><br>This
1919parameter causes that data output activities are starting not before
1920this interval
1921(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
1922the user has set <a href="#dt_dopr">dt_dopr</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dopr</span> = <span style="font-style: italic;">1800.0</span>, then the
1923first output will be done at t = 5400 s. </td> </tr> <tr>
1924<td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
1925</td> <td style="vertical-align: top;">R<br> </td>
1926<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
1927</td> <td style="vertical-align: top;">No output of
1928instantaneous horizontal cross section data before this interval has
1929passed (in s).<br><br>This
1930parameter causes that data output activities are starting not before
1931this interval
1932(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
1933the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a>
1934= <span style="font-style: italic;">3600.0</span>
1935and <span style="font-weight: bold;">skip_time_do2d_xy</span>
1936= <span style="font-style: italic;">1800.0</span>,
1937then the first output will be done at t = 5400 s. </td> </tr>
1938<tr> <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
1939</td> <td style="vertical-align: top;">R<br> </td>
1940<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
1941</td> <td style="vertical-align: top;">No output of
1942instantaneous vertical (xz) cross section data before this interval has
1943passed (in s).<br><br>This
1944parameter causes that data output activities are starting not before
1945this interval
1946(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
1947the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a>
1948= <span style="font-style: italic;">3600.0</span>
1949and <span style="font-weight: bold;">skip_time_do2d_xz</span>
1950= <span style="font-style: italic;">1800.0</span>,
1951then the first output will be done at t = 5400 s. </td> </tr>
1952<tr> <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
1953</td> <td style="vertical-align: top;">R<br> </td>
1954<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
1955</td> <td style="vertical-align: top;">No output of
1956instantaneous vertical (yz) cross section data before this interval has
1957passed (in s).<br><br>This
1958parameter causes that data output activities are starting not before
1959this interval
1960(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
1961the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a>
1962= <span style="font-style: italic;">3600.0</span>
1963and <span style="font-weight: bold;">skip_time_do2d_yz</span>
1964= <span style="font-style: italic;">1800.0</span>,
1965then the first output will be done at t = 5400 s. </td> </tr>
1966<tr> <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
1967</td> <td style="vertical-align: top;">R<br> </td>
1968<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
1969</td> <td style="vertical-align: top;">No output of
1970instantaneous 3d volume data before this interval has passed (in s).<br><br>This
1971parameter causes that data output activities are starting not before
1972this interval
1973(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
1974the user has set <a href="#dt_do3d">dt_do3d</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_do3d</span> = <span style="font-style: italic;">1800.0</span>, then the
1975first output will be done at t = 5400 s. </td> </tr>
1976<tr> <td style="vertical-align: top;"> <p><a name="termination_time_needed"></a><b>termination_time</b>
1977<br> <b>_needed</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br> </td>
1978<td style="vertical-align: top;"> <p>CPU time
1979needed for terminal actions at the end of a run in
1980batch mode (in s).<br> </p> <p>If the environment
1981variable <b>write_binary </b>is
1982set <i>true</i> (see <a href="chapter_3.3.html">chapter
19833.3</a>), PALM checks the remaining CPU time of the job after
1984each
1985timestep. Time integration must not consume the CPU time completely,
1986since several actions still have to be carried out after time
1987integration has finished (e.g. writing of binary data for the restart
1988run, carrying out output commands, copying of local files to their
1989permanent destinations, etc.) which also takes some time. The maximum
1990possible time needed for these activities plus a reserve is to be given
1991with the parameter <b>termination_time_needed</b>. Among
1992other things,
1993it depends on
1994the number of grid points used. If its value is selected too small,
1995then the
1996respective job will be prematurely aborted by the queuing system, which
1997may result in a data loss and will possibly interrupt the job chain.<br>
1998</p> <p>An abort happens in any way, if the environment
1999variable <span style="font-weight: bold;">write_binary</span>
2000is not set to <span style="font-style: italic;">true</span>
2001and if moreover the job has
2002been assigned an insufficient CPU time by <b>mrun</b>
2003option <tt><tt>-t</tt></tt>. <i><br>
2004</i> </p> <p><span style="font-weight: bold;">Note:</span><br>
2005On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of
2006PALM
2007have also to be accounted for (e.g. for
2008compilation and copying of input files).</p> </td> </tr>
2009<tr> <td style="vertical-align: top;"> <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
2010<br> <b>_parameters</b></p> </td> <td style="vertical-align: top;">L</td> <td style="vertical-align: top;"><i>.F.</i></td>
2011<td style="vertical-align: top;"> <p>Additional
2012plot of vertical profile data with <span style="font-weight: bold;">profil</span>
2013from preceding runs of the
2014job chain.&nbsp; </p> <p>This parameter only applies
2015for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
2016= <span style="font-style: italic;">'profil'</span>.</p><p>By
2017default, plots of horizontally averaged vertical profiles
2018(see <a href="#data_output_pr">data_output_pr</a>)
2019only contain profiles of data produced by the model
2020run. If profiles of prior times (i.e. data of preceding jobs of a
2021job chain) shall be plotted additionally (e.g. for comparison
2022purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>.
2023must be
2024set.<br> </p> <p>For further explanation see <a href="chapter_4.5.2.html">chapter
20254.5.2</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
2026</td> <td style="vertical-align: top;">R</td>
2027<td style="vertical-align: top;"><i>zu(nzt+1) (model
2028top)</i></td> <td style="vertical-align: top;">
2029<p>Height level up to which horizontally averaged profiles are to
2030be
2031plotted with <span style="font-weight: bold;">profil</span>
2032(in
2033m).&nbsp; </p> <p>This parameter only applies for
2034&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
2035= <span style="font-style: italic;">'profil'</span>.</p><p>It
2036affects plots of horizontally averaged profiles
2037(<a href="#data_output_pr">data_output_pr</a>)
2038when plotted with the plot software <span style="font-weight: bold;">profil</span>.
2039By default, profiles are plotted up to the top boundary. The height
2040level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller
2041value.
2042Nevertheless, <span style="font-weight: bold;">all</span>
2043vertical
2044grid points (0 &lt;= k &lt;= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p>
2045<p>If a normalization for the vertical axis was selected (see <a href="#cross_normalized_y">cross_normalized_y</a>), <b>z_max_do1d</b>
2046has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a>
2047must be used.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
2048<br> <b>_normalized</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>determined by plot</i>
2049<br> <i>data</i> <br> </td> <td style="vertical-align: top;"> <p>Normalized height
2050level up to which horizontally averaged
2051profiles are to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
2052</p> <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
2053= <span style="font-style: italic;">'profil'</span>.</p><p>It
2054affects plots of horizontally averaged profiles
2055(<a href="#data_output_pr">data_output_pr</a>)
2056when plotted with the plot software <span style="font-weight: bold;">profil</span>,
2057if a normalization for the vertical axis is selected
2058(see <a href="#cross_normalized_y">cross_normalized_y</a>).
2059If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b>
2060= <i>1.5</i> means that all profiles up to the height
2061level of z =
20621.5* z<sub>i </sub>are plotted.</p> </td> </tr>
2063<tr> <td style="vertical-align: top;"> <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
2064</td> <td style="vertical-align: top;">R<br> </td>
2065<td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br> </td>
2066<td style="vertical-align: top;"> <p>Height level
2067up to which 2d cross sections are to be plotted
2068with <span style="font-weight: bold;">iso2d</span>
2069(in m).&nbsp; </p> <p>This parameter only applies for
2070&nbsp;<a href="#data_output_format">data_output_format</a>
2071= <span style="font-style: italic;">'iso2d'</span>.</p><p>It
2072affects plots of&nbsp; 2d vertical cross
2073sections (<a href="#data_output">data_output</a>)
2074when plotted with <span style="font-weight: bold;">iso2d</span>.
2075By
2076default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d
2077</b>the
2078visualization within
2079the plot can be limited to a certain height level (0 &lt;= z
2080&lt;= <b>z_max_do2d</b>).
2081Nevertheless, <span style="font-weight: bold;">all</span>
2082grid points
2083of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>
2084or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
2085The level up to which the section is visualized can later be changed by
2086manually editing the
2087file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>
2088or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>
2089(the respective <span style="font-weight: bold;">iso2d</span>-parameter
2090is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p>
2091</td> </tr> </tbody>
2092</table><br>
2093<br><h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
2094parameters: </h3>
2095Package (<span style="font-weight: bold;">mrun</span>
2096option -p): <span style="font-weight: bold;"><a name="particles_package"></a>particles</span>&nbsp;&nbsp;&nbsp;&nbsp;
2097NAMELIST group name: <span style="font-weight: bold;">particles_par<br>
2098</span><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody>
2099<tr> <td style="vertical-align: top;"><font size="4"><b>Parameter name</b></font></td>
2100<td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
2101<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
2102<td style="vertical-align: top;"> <p><font size="4"><b>Explanation</b></font></p>
2103</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_prel"></a><b>dt_prel</b></p>
2104</td> <td style="vertical-align: top;">R</td>
2105<td style="vertical-align: top;"><i>9999999.9</i></td>
2106<td style="vertical-align: top;"> <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
2107interval at
2108which particles are to be released <span lang="en-GB">from
2109a particle
2110source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;
2111</font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">By default
2112particles are released only at the beginning of a simulation
2113(t_init=0). The time of the first release (t_init) can be changed with
2114package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>.
2115</font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
2116set with the package parameter <a href="#end_time_prel">end_time_prel</a>.
2117If <span style="font-weight: bold;">dt_prel</span>
2118has been set, additional
2119releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>,
2120t_init+2*<span style="font-weight: bold;">dt_prel</span>,
2121t_init+3*<span style="font-weight: bold;">dt_prel</span>,
2122etc.. Actual release times
2123may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see
2124e.g. </font></span><a href="#dt_dopr"><span lang="en-GB"><font face="Thorndale, serif">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">).</font></span></p>
2125<p><span lang="en-GB"><font face="Thorndale, serif"> The domain
2126of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as
2127well as the distance of&nbsp; released particles
2128within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package
2129parameters </font></span><a href="#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
2130<span lang="en-GB"><font face="Thorndale, serif">and
2131</font></span><a href="#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"><font face="Thorndale, serif"> By
2132default, one particle is released at all points defined by these
2133parameters. The package parameter <a href="#particles_per_point">particles_per_point</a>
2134can be used to start more than one particle per point.<br>
2135</font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
2136different groups of particles can be released at the same time (see </font></span><a href="chapter_4.2.html#number_of_particle_groups"><span lang="en-GB"><font face="Thorndale, serif">number_of_particle_groups</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)
2137where each group may have a different source. All particles belonging
2138to one group have the same density ratio and the same radius. All other
2139particle features (e.g. location of the source) are
2140identical for all groups of particles.</font></span></p>Subgrid
2141scale velocities can (optionally) be included for calculating the
2142particle advection, using the method of Weil et al. (2004, JAS, 61,
21432877-2887). This method is switched on by the package
2144parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.
2145This also forces the Euler/upstream method to be used for time
2146advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>).
2147The minimum timestep during the sub-timesteps is controlled by package
2148parameter <a href="#dt_min_part">dt_min_part</a>. <p><span lang="en-GB"><font face="Thorndale, serif">By
2149default, particles are weightless and transported passively with the
2150resolved scale flow. Particles can be given a mass and thus an inertia
2151by assigning the
2152package parameter </font></span><a href="#density_ratio"><span lang="en-GB"><font face="Thorndale, serif">density_ratio</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> a
2153non-zero value (it
2154defines the ratio of the density of the fluid and the density of the
2155particles). In these cases their </font></span><a href="#radius"><span lang="en-GB"><font face="Thorndale, serif">radius</font></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">
2156must also be defined, which affects their flow resistance. </font></span><a href="#diameter"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif"> </font></span> </p>
2157<p><span lang="en-GB"><font face="Thorndale, serif">Boundary
2158conditions for the particle transport can be defined with package
2159parameters </font></span><a href="#bc_par_t"><span lang="en-GB"><font face="Thorndale, serif">bc_par_t</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#bc_par_lr"><span lang="en-GB"><font face="Thorndale, serif">bc_par_lr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="bc_par_ns"><span lang="en-GB"><font face="Thorndale, serif">bc_par_ns</font></span></a>
2160<span lang="en-GB"><font face="Thorndale, serif">and
2161</font></span><a href="#bc_par_b"><span lang="en-GB"><font face="Thorndale, serif">bc_par_b</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span></p><span lang="en-GB"><font face="Thorndale, serif">Timeseries
2162of particle quantities in NetCDF format can be output to local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>
2163by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br></font></span><p>For
2164analysis, additional output of
2165particle
2166information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a>
2167(file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br>
2168</p> <p><span style="font-family: thorndale,serif;">Statistical
2169informations</span> (e.g. the total number of particles used, the
2170number of particles exchanged between the PEs, etc.) are output to the
2171local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>,
2172if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>.
2173<br> </p> <p><span lang="en-GB"><font face="Thorndale, serif">If a job
2174chain is to be carried out, particle
2175informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
2176location of
2177all
2178particles at the end of the
2179run) is output to
2180the local file</font></span> <font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font><a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a><font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font>,
2181<span lang="en-GB"><font face="Thorndale, serif">which
2182must be saved at the
2183end of the run <tt><span lang="en-GB"></span></tt>and
2184given as an
2185input file to the restart run
2186under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>
2187u<span lang="en-GB"><font face="Thorndale, serif">sing
2188respective file
2189connection statements in the <span style="font-weight: bold;">mrun</span>
2190configuration file. </font></span> <span lang="en-GB"></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
2191particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by
2192the package
2193parameter </font></span><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"><font face="Thorndale, serif">dt_dvrp</font></span></a><font face="Thorndale, serif"><span lang="en-GB">.
2194For visualization
2195purposes particles can be given a
2196diameter by the parameter <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a>
2197(this diameter only affects the visualization). All particles have the
2198same size. Alternatively, particles can be given an individual size and
2199a </span>color <span lang="en-GB">by modifying the
2200user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">.
2201Particles can pull a
2202&ldquo;tail&rdquo; behind themselves to improve their
2203visualization.
2204This is steered via the parameter&nbsp;<a href="chapter_4.2.html#use_particle_tails">use_particle_tails</a>.</font></span><a href="chapter_4.2.html#maximum_number_of_tailpoints"><span lang="en-GB"></span></a></p> <span lang="en-GB"></span><p><b>So far, the
2205particle transport realized in PALM does only
2206work
2207duly in case of a constant vertical grid spacing!</b></p> </td>
2208</tr> <tr> <td style="vertical-align: top;">
2209<p><a name="bc_par_b"></a><b>bc_par_b</b></p>
2210</td> <td style="vertical-align: top;">C*15</td>
2211<td style="vertical-align: top;"><i>&acute;reflect&acute;</i></td>
2212<td style="vertical-align: top;"> <p>Bottom
2213boundary condition for particle transport. </p> <p>By
2214default, particles are reflected at the bottom boundary.
2215Alternatively, a particle absorption can set by <b>bc_par_b</b>
2216= <i>&acute;absorb&acute;</i>.</p> </td>
2217</tr> <tr> <td style="vertical-align: top;">
2218<p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
2219</td> <td style="vertical-align: top;">C*15</td>
2220<td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
2221<td style="vertical-align: top;"> <p>Lateral
2222boundary condition (x-direction) for particle
2223transport. </p> <p>By default, cyclic boundary conditions
2224are used along x.
2225Alternatively, reflection (<b>bc_par_lr</b>
2226= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_lr</b>
2227= <i>&acute;absorb&acute;</i>)
2228can be set. <br> </p> <p>This lateral boundary
2229conditions should correspond to the
2230lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p> </td>
2231</tr> <tr> <td style="vertical-align: top;">
2232<p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
2233</td> <td style="vertical-align: top;">C*15</td>
2234<td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
2235<td style="vertical-align: top;"> <p>Lateral
2236boundary condition (y-direction) for particle
2237transport. </p> <p>By default, cyclic boundary conditions
2238are used along y.
2239Alternatively, reflection (<b>bc_par_ns</b>
2240= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_ns</b>
2241= <i>&acute;absorb&acute;</i>)
2242can be set.<br> </p>
2243This lateral boundary conditions should correspond to the lateral
2244boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td> </tr>
2245<tr> <td style="vertical-align: top;"> <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
2246</td> <td style="vertical-align: top;">C*15</td>
2247<td style="vertical-align: top;"><i>&acute;absorb&acute;</i></td>
2248<td style="vertical-align: top;"> <p>Top boundary
2249condition for particle transport. </p> <p>By default,
2250particles are absorbed at the top boundary.
2251Alternatively, a reflection condition can be set by <b>bc_par_t</b>
2252= <i>&acute;reflect&acute;</i>.</p> </td>
2253</tr> <tr> <td style="vertical-align: top;">
2254<p><a name="density_ratio"></a><b>density_ratio</b></p>
2255</td> <td style="vertical-align: top;">R (10)</td>
2256<td style="vertical-align: top;"> <p><i>0.0, 9</i>
2257*<br> <i>9999999.9</i></p> </td> <td style="vertical-align: top;"> <p>Ratio of the density
2258of the fluid and the density of the
2259particles. </p> <p>With the default value<i> </i>the
2260particles are weightless and transported passively with the resolved
2261scale flow.
2262In case of <span style="font-weight: bold;">density_ratio</span>
2263/=
22640.0 particles have a mass and hence inertia so that their velocity
2265deviates more or less from the velocity of the surrounding flow.
2266Particle velocity is calculated analytically and depends on (besides
2267the density ratio and the current velocity difference between particles
2268and surrounding fluid) the
2269particle radius which is determined via <a href="#radius">radius</a>
2270as well as on the molecular viscosity (assumed as 1.461E-5 m<sup>2</sup>/s).
2271</p> <p>If <b>density_ratio</b> = <i>1.0</i>,
2272the particle density
2273corresponds to the density of the surrounding fluid and the particles
2274do not feel any buoyancy. Otherwise, particles will be accelerated
2275upwards (<b>density_ratio</b> &gt; <i>1.0</i>)
2276or downwards (<b>density_ratio</b> &lt; <i>1.0</i>).<br>
2277</p> <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
2278each group can be assigned a different value. If the number of values
2279given for <span style="font-weight: bold;">density_ratio</span>
2280is less than the number of
2281groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
2282then the last assigned value is used for all remaining groups. This
2283means that by default the particle density ratio for all groups will be
2284<span style="font-style: italic;">0.0</span>.</p>
2285</td> </tr> <tr><td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td><td align="left" valign="top"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
2286interval</font> at which time series data of particle quantities
2287shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
2288<span lang="en-GB"><font face="Thorndale">If
2289particle advection is switched on (see</font></span><font><span style="font-family: thorndale;"> <a href="#dt_prel">dt_prel</a>)
2290this parameter can be used to assign
2291th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
2292interval at which time series of particle quantities shall be output.
2293Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br><br>The
2294following list gives a short description of the&nbsp;quantities
2295available. Most quantities are averages over all particles. The
2296quantity name given in the first column is identical to the respective
2297name of the variable on the NetCDF file (see section <a href="chapter_4.5.1.html">4.5.1</a> for a general
2298description of the NetCDF files).<br><br>In case of using
2299more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
2300seperate time series are output for each of the groups. The long names
2301of the variables in the NetCDF file containing the respective
2302timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle
2303group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>&nbsp;</font></span><table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td><td align="undefined" valign="undefined">total number of
2304particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td><td align="undefined" valign="undefined">particle
2305x-coordinate&nbsp;with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td><td align="undefined" valign="undefined">particle
2306y-coordinate&nbsp;with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td><td align="undefined" valign="undefined">particle
2307z-coordinate&nbsp;with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td><td align="undefined" valign="undefined">absolute
2308particle z-coordinate (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td><td align="undefined" valign="undefined">u particle
2309velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td><td align="undefined" valign="undefined">v particle
2310velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td><td align="undefined" valign="undefined">w particle
2311velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td><td align="undefined" valign="undefined">subgrid-scale u
2312particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td><td align="undefined" valign="undefined">subgrid-scale v
2313particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td><td align="undefined" valign="undefined">subgrid-scale w
2314particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td><td align="undefined" valign="undefined">total number of
2315upward moving particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td><td align="undefined" valign="undefined">vertical
2316velocity of the upward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td><td align="undefined" valign="undefined">vertical
2317velocity of the downward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td><td align="undefined" valign="undefined">maximum number
2318of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td><td align="undefined" valign="undefined">minimum number
2319of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td><td align="undefined" valign="undefined">variance of the
2320particle x-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td><td align="undefined" valign="undefined">variance of the
2321particle y-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td><td align="undefined" valign="undefined">variance of the
2322particle z-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td><td align="undefined" valign="undefined">variance of the
2323u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v*2</td><td align="undefined" valign="undefined">variance of the
2324v particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">v </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w*2</td><td align="undefined" valign="undefined">variance of the
2325w particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">w </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">u"2</td><td align="undefined" valign="undefined">variance of the
2326subgrid-scale u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v"2</td><td align="undefined" valign="undefined">variance of the
2327subgrid-scale v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w"2</td><td align="undefined" valign="undefined">variance of the
2328subgrid-scale w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">npt*2</td><td align="undefined" valign="undefined">variance of the
2329number of particles with respect to the average number of particles per
2330subdomain</td></tr></tbody></table><span lang="en-GB"></span><span lang="en-GB"></span></td></tr><tr><td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td><td align="left" valign="top">Minimum value for the
2331particle timestep when SGS velocities are used (in s).<br><br>For
2332a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td></tr><tr>
2333<td style="vertical-align: top;"> <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b>
2334<b>data</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><i>9999999.9</i></td>
2335<td style="vertical-align: top;"> <p>Temporal
2336interval for output of particle data (in s). </p> <p>T<span lang="en-GB"></span><a href="#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
2337parameter can be used to
2338assign the temporal interval at which particle data shall be output.</font></span>
2339Data are output to
2340the local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>.
2341<span style="font-family: mon;">See the file description
2342for more
2343details about its format</span>. </p> <p>By
2344default, no particle data are output.</p> </td> </tr>
2345<tr> <td style="vertical-align: top;"> <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p>
2346</td> <td style="vertical-align: top;">R<br> </td>
2347<td style="vertical-align: top;">0.2 * dx<br> </td>
2348<td style="vertical-align: top;"> <p>Diameter that
2349the particles is given in visualizations with
2350the <span style="font-weight: bold;">dvrp</span>
2351software (in
2352m).&nbsp; </p> <p>In case that particles are
2353visualized with the <span style="font-weight: bold;">dvrp</span>
2354software (see <a href="chapter_4.5.7.html">chapter
23554.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>.
2356All
2357particles are displayed with this same size.<br> </p> <p>Alternatively,
2358the particle diameters can be set with the
2359user-interface in routine <span style="font-family: monospace;">user_init_particles</span>
2360(at the beginning of the simulation) and/or can be redefined after each
2361timestep in routine <tt>user<font style="font-size: 11pt;" size="2">_particle_attributes</font></tt>
2362(both routines can be found in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt><font style="font-size: 11pt;" size="2">)</font>.&nbsp;</p>
2363<p><b>Note:</b> This parameter determines exclusively
2364the size
2365under which particles appear in the <span style="font-weight: bold;">dvrp</span>
2366visualization. The flow relevant particle radius is determined via the
2367particle package parameter <a href="#radius">radius</a>!</p>
2368</td> </tr> <tr><td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td><td align="left" valign="top">Time of the last release of
2369particles (in s).<br><br>See also <a href="#particle_advection_start">particle_advection_start</a>.</td></tr><tr>
2370<td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td>
2371<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br> </td>
2372<td style="vertical-align: top;">Factor to define the real
2373number of initial droplets in a grid box.<br> <br>
2374In case of explicitly simulating cloud droplets (see <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>),
2375the real number of initial droplets in a grid box is equal to the
2376initial number of droplets in this box (defined by the particle source
2377parameters <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>
2378<span lang="en-GB"><font face="Thorndale, serif">and
2379</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>)
2380times the <span style="font-weight: bold;">initial_weighting_factor</span>.</td>
2381</tr>
2382<tr> <td style="vertical-align: top;"> <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b>
2383<br> <b>particles</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>1000</i></td>
2384<td style="vertical-align: top;"> <p>Maximum number
2385of particles (on a PE).&nbsp; </p> <p>This parameter
2386allows to set the number of particles for which
2387memory must be allocated at the beginning of the run.
2388If this memory becomes insufficient during the run, due to the
2389release of further particles (see <a href="#dt_prel">dt_prel</a>),
2390then more memory is automatically allocated.<br> </p>
2391For runs on several processors, <span style="font-weight: bold;">maximum_number_of_particles</span>
2392defines
2393the maximum number on each PE. This number must be larger than the
2394maximum number of particles initially released in a subdomain.</td>
2395</tr> <tr> <td style="vertical-align: top;">
2396<p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b>
2397<br> <b>tailpoints</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>100</i></td>
2398<td style="vertical-align: top;"> <p>Maximum number
2399of tailpoints that a particle tail can
2400have.&nbsp; </p> <p>&nbsp;<b>maximum_number_of_tailpoints</b>
2401sets the number of descrete points the tail consists of. A new point is
2402added to the particle tails after each time step. If the maximum number
2403of tail
2404points is reached after the corresponding number of timesteps, the
2405oldest respective tail points is deleted within the following
2406timestep.&nbsp; </p> <p>All particle tails have the
2407same number of points. The maximum
2408length of
2409these
2410tails is determined by the value of <b>maximum_number_of_tailpoints</b>
2411and by the minimum distance between each of the adjoining
2412tailpoints,&nbsp; which can be set by <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.
2413Additionally, it can be determined that the temporal displacement
2414between the current position of the particle and the oldest point of
2415the tail may become not larger than a value to be assigned by <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>.</p>
2416</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b>
2417<br> <b>age</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;">100000.0</td> <td style="vertical-align: top;"> <p>Maximum age that the
2418end point of a particle tail is allowed to have (in s).&nbsp; </p>
2419<p>If the temporal displacement between the oldest point of a
2420particle tail and the current position of the particle becomes larger
2421than the value given by <b>maximum_tailpoint_age</b>, this
2422oldest
2423point (which defines the end of the tail) is
2424removed. If this time is so small that the number of points defining
2425the particle tail do not exceed the value given by <b>maximum_number_of_tailpoints</b>,
2426then the length the particle tails is a measure for the distance the
2427particle travelled along during the time interval defined via <b>maximum_tailpoint_age</b>,
2428i.e. for the
2429particle velocity. Fast particles will have long tails, slow particles
2430shorter ones (note: this will not neccessarily hold if <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>
2431= <i>0.0</i>).</p> </td> </tr> <tr>
2432<td style="vertical-align: top;"> <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</b></p>
2433</td> <td style="vertical-align: top;">R</td>
2434<td style="vertical-align: top;"><i>0.0</i></td>
2435<td style="vertical-align: top;"> <p>Minimum
2436distance allowed between two adjacent points of a
2437particle tail (in m).&nbsp; </p> <p>In case of <b>minimum_tailpoint_distance</b>
2438&gt; <i>0.0 </i>the
2439particle tail is extended by a new point only if the distance between
2440its current position and the most recent tail point exceed the
2441distance given via <b>minimum_tailpoint_distance</b>.<br>
2442</p> <p>If the length of the particle tails shall be
2443proportional to
2444the respective particle velocity, the parameter <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>
2445must also be set appropriately. </p> <b>Note:</b><br>
2446A suitable choice of <b>minimum_tailpoint_distance</b>
2447&gt; <i>0.0</i> is recommended, because then the tail
2448coordinates of
2449slowly moving particles require less memory and can also be drawn
2450faster. The upper limit of <b>minimum_tailpoint_distance</b>
2451should be chosen in a way that the visualized particle
2452tails still appear as smooth lines. Example: with a model domain of
24531000 m and a monitor resolution of 1280 * 1024 pixels it
2454should be sufficient to set <b>minimum_tailpoint_distance</b>
2455= <i>5.0</i>
2456(m). </td> </tr> <tr> <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br>
2457</td> <td style="vertical-align: top;">I<br> </td>
2458<td style="vertical-align: top;">1<br> </td> <td style="vertical-align: top;">Number of particle groups to be
2459used.<br> <br>
2460Each particle group can be assigned its own source region (see <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
2461<a href="#psr">psr</a>, etc.), particle diameter (<a href="#radius">radius</a>) and particle density ratio (<a href="density_ratio">density_ratio</a>).<br><br>If
2462less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
2463etc. than the number of particle groups, then the last value is used
2464for the remaining values (or the default value, if the user did not set
2465the parameter).<br> <br>
2466The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br> </td>
2467</tr>
2468<tr><td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td><td align="left" valign="top">I</td><td align="left" valign="top">1</td><td align="left" valign="top">Number of particles to be
2469started per point.<br><br>By default, one particle is
2470started at all points of the particle source,&nbsp;defined by <span style="font-family: Thorndale,serif;">the </span><span lang="en-GB"><font face="Thorndale, serif">package
2471parameters </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>
2472<span lang="en-GB"><font face="Thorndale, serif">and
2473</font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"></span></td></tr><tr> <td style="vertical-align: top;"> <p><a name="particle_advection_start"></a><b>particle_advection_</b>
2474<br> <b>start</b></p> </td> <td style="vertical-align: top;">R </td> <td style="vertical-align: top;">0.0 </td> <td style="vertical-align: top;"> <p>Time of the first
2475release of particles (in s). </p> <p>If particles are not
2476to be released at the beginning of the
2477run, the release time can be set via <b>particle_advection_start</b>.<br>
2478If particle transport is switched on in a restart run, then <a href="#read_particles_from_restartfile">read_particles_from_restartfile</a>
2479= <span style="font-style: italic;">.F.</span> is
2480also required.</p><p>See also <a href="#end_time_prel">end_time_prel</a>.
2481</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p>
2482</td> <td style="vertical-align: top;">R </td>
2483<td style="vertical-align: top;"><i>9999999.9</i>
2484</td> <td style="vertical-align: top;"> <p>Maximum
2485allowed age of particles (in s).&nbsp; </p> <p>If the
2486age of a particle exceeds the time set by <b>particle_maximum_age</b>,
2487the particle as well as its tail is deleted.</p> </td> </tr>
2488<tr> <td style="vertical-align: top;"> <p><a name="pdx"></a><b>pdx</b></p> </td>
2489<td style="vertical-align: top;">R (10)<br> </td>
2490<td style="vertical-align: top;"><i>10 * dx</i>
2491</td> <td style="vertical-align: top;"> <p>Distance
2492along x between particles within a particle source
2493(in m).&nbsp; </p> <p>If the particle source shall be
2494confined to one grid point,
2495the distances given by <span style="font-weight: bold;">pdx</span>,
2496<a href="#pdy">pdy</a>
2497and <a href="#pdz">pdz</a>
2498must be set larger than the respective domain size or <a href="#psl">psl</a>
2499= <a href="#psr">psr</a> has to be set
2500alternatively.<br>
2501</p> <p><span style="font-weight: bold;">pdx</span>
2502can be assigned a different value for each particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>).<br>
2503</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pdy"></a><b>pdy</b></p>
2504</td> <td style="vertical-align: top;">R (10)<br>
2505</td> <td style="vertical-align: top;"><i>10
2506* dy</i> </td> <td style="vertical-align: top;">Distance
2507along y between
2508particles within a
2509particle source (in m).&nbsp; </td> </tr> <tr>
2510<td style="vertical-align: top;"> <p><a name="pdz"></a><b>pdz</b></p> </td>
2511<td style="vertical-align: top;">R (10)<br>
2512</td> <td style="vertical-align: top;"><i>10
2513* ( zu(2) - zu(1) )</i> </td> <td style="vertical-align: top;">Distance along z between
2514particles within a particle source
2515(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psb"></a><b>psb</b></p>
2516</td> <td style="vertical-align: top;">R (10)<br>
2517</td> <td style="vertical-align: top;"><i>10&nbsp;
2518* zu(nz/2)</i> </td> <td style="vertical-align: top;">Bottom
2519edge of a particle
2520source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psl"></a><b>psl</b></p>
2521</td> <td style="vertical-align: top;">R (10)<br>
2522</td> <td style="vertical-align: top;"><i>10
2523* 0.0</i> </td> <td style="vertical-align: top;">Left
2524edge of a particle source
2525(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psn"></a><b>psn</b></p>
2526</td> <td style="vertical-align: top;">R (10)<br>
2527</td> <td style="vertical-align: top;"><i>10
2528* (ny * dy)</i> </td> <td style="vertical-align: top;">Rear
2529(&ldquo;north&rdquo;) edge of a
2530particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psr"></a><b>psr</b></p>
2531</td> <td style="vertical-align: top;">R (10)<br>
2532</td> <td style="vertical-align: top;"><i>10
2533* (nx * dx)</i> </td> <td style="vertical-align: top;">Right
2534edge of a particle
2535source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pss"></a><b>pss</b></p>
2536</td> <td style="vertical-align: top;">R (10)<br>
2537</td> <td style="vertical-align: top;"><i>10
2538* 0.0</i> </td> <td style="vertical-align: top;">Front
2539(&ldquo;south&rdquo;) edge of a
2540particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pst"></a><b>pst</b></p>
2541</td> <td style="vertical-align: top;">R (10)<br>
2542</td> <td style="vertical-align: top;"><i>10
2543* zu(nz/2)</i> </td> <td style="vertical-align: top;">Top
2544edge of a particle source
2545(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="radius"></a><b>radius</b></p>
2546</td> <td style="vertical-align: top;">R (10)</td>
2547<td style="vertical-align: top;"><i>0.0, 9</i>*<br>
2548<i>9999999.9</i></td> <td style="vertical-align: top;">Particle radius (in m).<br>
2549<br>
2550The viscous friction (in case of a velocity difference between
2551particles and surrounding fluid) depends on the particle radius which
2552must be assigned as soon as <a href="chapter_4.2.html#density_ratio">density_ratio</a>
2553/= <i>0.0</i>.<br> <br>
2554With several groups of particles (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
2555each group can be assigned a different value. If the number of values
2556given for <span style="font-weight: bold;">radius</span>
2557is less than the number of
2558groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
2559then the last assigned value is used for all remaining groups. This
2560means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br> </td>
2561</tr>
2562<tr> <td style="vertical-align: top;"> <p><a name="random_start_position"></a><b>random_start_position</b></p>
2563</td> <td style="vertical-align: top;">L<br> </td>
2564<td style="vertical-align: top;"><i>.F.</i> </td>
2565<td style="vertical-align: top;"> <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
2566particles is
2567varied randomly within certain limits.&nbsp; </p> <p>By
2568default, the initial positions of particles within the
2569source excatly correspond with the positions given by <a href="#psl">psl</a>,
2570<a href="#psr">psr</a>, <a href="#psn">psn</a>,
2571<a href="#pss">pss</a>, <a href="#psb">psb</a>,
2572<a href="#pst">pst</a>, <a href="#pdx">pdx</a>,
2573<a href="#pdy">pdy</a>,
2574and<a href="#pdz">
2575pdz</a>. With <b>random_start_position</b> = <i>.T.
2576</i>the initial
2577positions of the particles are allowed to randomly vary from these
2578positions within certain limits.&nbsp; </p> <p><b>Very
2579important:<br> </b>In case of <b>random_start_position</b>
2580= <i>.T.</i>, the
2581random-number generators on the individual PEs no longer&nbsp;
2582run synchronously. If random disturbances are applied to the velocity
2583field
2584(see <a href="#create_disturbances">create_disturbances</a>),
2585<font color="#000000">then as consequence for parallel
2586runs the
2587realizations of the turbulent flow
2588fields will deviate between runs which used different numbers of PEs!</font></p>
2589</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b>
2590<br> <b>restartfile</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td>
2591<td style="vertical-align: top;"> <p>Read particle
2592data from the previous run.&nbsp; </p> <p>By default,
2593with restart runs particle data is read
2594from file <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
2595which is created by the preceding run. If this is not requested or if
2596in a restart run particle transport is switched on for the
2597first time (see <a href="#particle_advection_start">particle_advection_start</a>),
2598then <b>read_particles_from_restartfile</b> = <i>.F.</i>
2599is required.</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br>
2600</td> <td style="vertical-align: top;">I<br> </td>
2601<td style="vertical-align: top;"><span style="font-style: italic;">1</span><br> </td>
2602<td style="vertical-align: top;">Limit the number of
2603particle tails.<br> <br>
2604If particle tails are switched on (see <a href="#use_particle_tails">use_particle_tails</a>),
2605every particle is given a tail by default. <span style="font-weight: bold;">skip_particles_for_tail </span>can
2606be used to give only every n'th particle a tail.<br> <br> <span style="font-weight: bold;">Example:</span><br> <span style="font-weight: bold;">skip_particles_for_tail</span>
2607= <span style="font-style: italic;">10</span> means
2608that only every 10th particle will be given a tail.<br> </td>
2609</tr> <tr> <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</span><br>
2610</td> <td style="vertical-align: top;">L<br> </td>
2611<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td>
2612<td style="vertical-align: top;">Give particles a tail.<br>
2613<br>
2614A particle tail is defined by the path a particle has moved
2615along starting from some point of time in the past. It consists of a
2616set of descrete points in space which may e.g. be connected by a line
2617in order visualize how the particle has moved.<br> <br>
2618By default, particles have no tail. Parameter&nbsp;<a href="#skip_particles_for_tail">skip_particles_for_tail</a>
2619can be used to give only every n'th particle a tail.<br> <br>
2620The length of the tail is controlled by parameters&nbsp;<a href="#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>,&nbsp;<a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>,
2621and <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.<br>
2622</td> </tr>
2623<tr><td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</span></td><td align="left" valign="top">L</td><td align="left" valign="top"><span style="font-style: italic;">.F.</span></td><td align="left" valign="top">Use subgrid-scale
2624velocities for particle advection.<br><br>These
2625velocities are calculated from the resolved and subgrid-scale TKE using
2626the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
262761,
26282877-2887). When using this method, the timestep for the advancement of
2629the particles is limited by the so-called Lagrangian time scale. This
2630may be smaller than the current LES timestep so that several particle
2631(sub-) timesteps have to be carried out within one LES timestep. In
2632order to limit the number of sub-timesteps (and to limit the CPU-time),
2633the minimum value for the particle timestep is defined by the package
2634parameter <a href="#dt_min_part">dt_min_part</a>.<br><br>Setting
2635<span style="font-weight: bold;">use_sgs_for_particles</span>
2636= <span style="font-style: italic;">.TRUE.</span>
2637automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>
2638= <span style="font-style: italic;">.TRUE.</span>.
2639This inhibits the occurrence of large (artificial) spatial gradients of
2640the subgrid-scale TKE which otherwise would lead to wrong results for
2641the particle advection.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b>
2642<br> <b>advection</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td>
2643<td style="vertical-align: top;"> <p>Switch on/off
2644vertical particle transport. </p> <p>By default,
2645particles are transported along all three
2646directions in space. With <b>vertical_particle_advection</b>
2647= <i>.F., </i>the
2648particles will only be transported horizontally.</p> </td>
2649</tr> <tr> <td style="vertical-align: top;">
2650<p><a name="write_particle_statistics"></a><b>write_particle_</b>
2651<br> <b>statistics</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.F.</i> </td>
2652<td style="vertical-align: top;"> <p>Switch on/off
2653output of particle informations.<br> </p> <p><br>
2654For <span style="font-weight: bold;">write_particle_statistics</span>
2655= <span style="font-style: italic;">.T.</span> s<span style="font-family: thorndale,serif;">tatistical
2656informations</span> (e.g. the total number of particles used, the
2657number of particles exchanged between the PEs, etc.) which may be used
2658for debugging are output to the
2659local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>.&nbsp;
2660</p> <p><b>Note:</b> For parallel runs files
2661may become very large
2662and performance of PALM may decrease.</p> </td> </tr>
2663</tbody>
2664</table><span style="font-weight: bold;"><br>
2665<br></span><span style="font-weight: bold;">Package
2666(<span style="font-weight: bold;">mrun</span> option
2667-p): <span style="font-weight: bold;"><a name="dvrp_graphics"></a>dvrp_graphics</span>
2668&nbsp;&nbsp;&nbsp;
2669NAMELIST group name: <span style="font-weight: bold;">dvrp_graphics_par<br>
2670<br></span></span>
2671<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr>
2672<td style="vertical-align: top;"><font size="4"><b>Parameter
2673name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
2674<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
2675<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
2676</tr> <tr> <td style="vertical-align: top;">
2677<p><a name="dt_dvrp"></a><b>dt_dvrp</b></p>
2678</td> <td style="vertical-align: top;">R</td>
2679<td style="vertical-align: top;"><i>9999999.9</i></td>
2680<td style="vertical-align: top;"> <p>Temporal
2681interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
2682s).&nbsp; </p> <p>Isosurfaces, cross sections and
2683particles can be displayed
2684simultaneous. The display of particles requires that the particle
2685transport is switched on (see <a href="#dt_prel">dt_prel</a>).
2686Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p> <p>If
2687output of scenes created by dvrp software is switched on
2688(see <a href="#mode_dvrp">mode_dvrp</a>),
2689this parameter can be used to assign the temporal interval at which
2690scenes are to be created (and the respective&nbsp; graphical data
2691is to
2692be output to the streaming server). <span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
2693&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dvrp</b>,
26942*<b>dt_dvrp</b>, 3*<b>dt_dvrp</b>, etc. The
2695actual output times can
2696deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).&nbsp;
2697Is <b>dt_dvrp</b> &lt; </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then
2698scenes are created and
2699output after each time step (if this is requested it should be <b>dt_dvrp</b>
2700= <i>0</i>).</font></span> </p> </td>
2701</tr> <tr> <td style="vertical-align: top;">
2702<p><a name="dvrp_directory"></a><b>dvrp_directory</b></p>
2703</td> <td style="vertical-align: top;">C*80</td>
2704<td style="vertical-align: top;"><i>'default'</i></td>
2705<td style="vertical-align: top;"> <p>Name of the
2706directory into which data created by the <span style="font-weight: bold;">dvrp</span>
2707software shall be saved.&nbsp; </p> <p>By default,
2708the directory name is generated from the user
2709name
2710(see package parameter <a href="#dvrp_username">dvrp_username</a>)
2711and the base file name (given as the argument of <span style="font-weight: bold;">mrun</span> option -d) as <span style="font-style: italic;">'&lt;user
2712name&gt;/&lt;base file name&gt;'</span>.</p> </td>
2713</tr> <tr> <td style="vertical-align: top;">
2714<p><a name="dvrp_file"></a><b>dvrp_file</b></p>
2715</td> <td style="vertical-align: top;">C*80</td>
2716<td style="vertical-align: top;"><i>'default'</i></td>
2717<td style="vertical-align: top;"> <p>Name of the
2718file into which data created by the <span style="font-weight: bold;">dvrp</span>
2719software shall be output.&nbsp; </p> <p>This
2720parameter can be given a value only in case of <a href="#dvrp_output">dvrp_output</a>
2721= <span style="font-style: italic;">'local'</span><i>
2722</i>which
2723determines that the data created by <span style="font-weight: bold;">dvrp</span>
2724is output to a local file (on the machine where PALM is executed).
2725Apart from the default, it is only allowed to assign <span style="font-style: italic;">'/dev/null'</span> (which
2726means that no output is really stored). This can be used for special
2727runtime measurements of the <span style="font-weight: bold;">dvrp</span>
2728software.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_host"></a><b>dvrp_host</b></p>
2729</td> <td style="vertical-align: top;">C*80</td>
2730<td style="vertical-align: top;"> <p><i>'origin.rvs.</i>
2731<br>
2732u<i>ni- hanover.de'</i></p> </td> <td style="vertical-align: top;"> <p>Name of the computer
2733to which data created by the <span style="font-weight: bold;">dvrp</span>
2734software shall be
2735transferred.&nbsp; </p> <p>In case of <a href="#dvrp_output">dvrp_output</a>
2736= <span style="font-style: italic;">'rtsp'</span>
2737only the default
2738value is allowed (streaming server of
2739the RRZN). For <a href="#dvrp_output">dvrp_output</a>
2740= <span style="font-style: italic;">'local'</span><i>
2741</i>the
2742assigned value is ignored.</p> </td> </tr> <tr>
2743<td style="vertical-align: top;"> <p><a name="dvrp_output"></a><b>dvrp_output</b></p>
2744</td> <td style="vertical-align: top;">C*10</td>
2745<td style="vertical-align: top;"><i>'rtsp'</i></td>
2746<td style="vertical-align: top;"> <p>Output mode
2747for the <span style="font-weight: bold;">dvrp</span>
2748software. <br> <br> </p>
2749The following settings are allowed:<br> <br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'rtsp'</i></td>
2750<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
2751software is transferred using
2752a special transmission protocol to a so-called streaming server, which
2753is able to continuously transfer visualization data with a
2754high transmission rate.&nbsp; <br>
2755Additionally, with this output mode a
2756set of files is generated automatically
2757within a directory on the streaming server (beside the visualization
2758data e.g. some html-files) which can be used to
2759visualize the data via an internet-browser plugin. Host
2760(streaming-server) and directory can be defined by the user with <a href="#dvrp_host">dvrp_host</a>
2761and <a href="#dvrp_directory">dvrp_directory</a>.</td>
2762</tr> <tr> <td style="vertical-align: top;"><i>'ftp'</i></td>
2763<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
2764software is transferred to the destination host (see <a href="#dvrp_host">dvrp_host</a>
2765and <a href="#dvrp_directory">dvrp_directory</a>)
2766using ftp.</td> </tr> <tr> <td style="vertical-align: top;"><i>'local'</i></td>
2767<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
2768software is output locally on a file defined by <a href="#dvrp_file">dvrp_file
2769</a>.</td> </tr> </tbody> </table> <br>
2770</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_password"></a><b>dvrp_password</b></p>
2771</td> <td style="vertical-align: top;">C*80</td>
2772<td style="vertical-align: top;">'********'</td> <td style="vertical-align: top;"> <p>Password for the
2773computer to which data created by the <span style="font-weight: bold;">dvrp</span> software is to
2774be
2775transferred.&nbsp; </p> <p>Assigning a password is
2776only necessary in case of <a href="#dvrp_output">dvrp_output</a>
2777= <span style="font-style: italic;">'ftp'</span>.
2778For <a href="#dvrp_output">dvrp_output</a>
2779= <span style="font-style: italic;">'rtsp'</span><i>
2780</i>the default
2781value must not be changed!</p> </td> </tr> <tr>
2782<td style="vertical-align: top;"> <p><a name="dvrp_username"></a><b>dvrp_username</b></p>
2783</td> <td style="vertical-align: top;">C*80</td>
2784<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>User name of a valid
2785account on the computer to which data
2786created by the <span style="font-weight: bold;">dvrp</span>
2787software
2788is to be
2789transferred.&nbsp; </p> <p>Assigning a value to this
2790parameter is required in case of <a href="#dvrp_output">dvrp_output</a>
2791= <span style="font-style: italic;">'rtsp'</span>
2792or <span style="font-style: italic;">'ftp'</span>.</p>
2793</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p>
2794</td> <td style="vertical-align: top;">C*20&nbsp;
2795<br>(10)</td> <td style="vertical-align: top;"><i>10
2796* ''</i></td> <td style="vertical-align: top;">
2797<p>Graphical objects (isosurfaces, slicers, particles) which are
2798to be created by the <span style="font-weight: bold;">dvrp</span>
2799software.&nbsp; </p> <p>Several different objects can
2800be assigned simultaneously and
2801will be displayed in the same scene. Allowed values for <span style="font-weight: bold;">mode_dvrp</span> are <span style="font-style: italic;">'isosurface#'</span>
2802(isosurface), <span style="font-style: italic;">'slicer#'</span>
2803(cross sections), and <span style="font-style: italic;">'particles'</span>.
2804Within the strings the hash character ("#") has to be replaced by a
2805digit &le;9. Up to 10 objects
2806can be assigned at the same time, e.g. :&nbsp; </p> <blockquote><b>mode_dvrp</b>
2807= <span style="font-style: italic;">'isosurface2'</span><i>,
2808'slicer1',
2809'particles', 'slicer2'</i></blockquote> <p>In this
2810case one isosurface, two cross sections, and particles
2811will be created. The quantities for which an isosurface are to be
2812created have to be selected with
2813the parameter <a href="#data_output">data_output</a>,
2814those for cross sections with <a href="#data_output">data_output</a>
2815(<span style="font-weight: bold;">data_output</span>
2816also determines the
2817orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> lists of
2818variables may be
2819assigned, the digit at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string
2820selects the quantity, which is given
2821at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface2'</span>
2822selects the quantity
2823given in the second position of <span style="font-weight: bold;">data_output</span>).
2824If e.g. <span style="font-weight: bold;">data_output</span>
2825and <span style="font-weight: bold;">data_output</span>
2826are assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
2827'w_xz', 'v_yz'</i> and <b>data_output</b> = <span style="font-style: italic;">'pt'</span><i>,
2828'u', 'w' </i>are
2829indicated, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
2830isosurface of u, a
2831horizontal cross section of u and
2832a vertical cross section (xz) of w is created. For locations of the
2833cross sections see <a href="#data_output">data_output</a>.
2834The theshold value for which the isosurface is
2835to be created can be defined with parameter <a href="#threshold">threshold</a>.<br>
2836</p> <p>The vertical extension of the displayed domain is
2837given by <a href="#nz_do3d">nz_do3d</a>.<br> </p>
2838<p>The vertical extension of the displayed domain is given by <a href="#nz_do3d">nz_do3d</a>. </p> <p><b>Assignments
2839of mode_dvrp must correspond to those of data_output
2840and
2841data_output! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>
2842and <b>data_output</b>
2843= 'w'<i> </i>was set, then only the digit "1" is allowed
2844for <b>mode_dvrp</b>,
2845thus <span style="font-style: italic;">'isosurface1'</span>
2846and/or <span style="font-style: italic;">'slicer1'</span><i>.</i>&nbsp;
2847</p> <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are
2848given in <a href="chapter_4.5.7.html">chapter
28494.5.7</a>.<br> </p> <b>Note:</b><br>
2850The declaration color charts to be
2851used still have to be given "manually" in subroutine <span style="font-family: monospace;">user_dvrp_coltab</span>
2852(file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;
2853<br>A change of particle colors and/or particle diameters (e.g.
2854according
2855to the local characteristics of the flow field) to be used for the
2856visualization, must be carried out by adding respective code extensions
2857to <tt><font style="font-size: 11pt;" size="2">user_particle_attributes</font></tt>
2858(in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;</td>
2859</tr> <tr> <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br>
2860dvrp</span></td> <td style="vertical-align: top;">R(2,10)</td>
2861<td style="vertical-align: top;"><span style="font-style: italic;">10
2862* (-1,1)</span></td> <td style="vertical-align: top;">Ranges
2863of values to which a color table has to be mapped (units of the
2864respective quantity).<br> <br>
2865In case that slicers have to be displayed (see <a href="#threshold">mode_dvrp</a>),
2866this parameter defines the ranges of values of the respective
2867quantities to which the colortable in use has to be mapped. If e.g. a
2868temperature slice shall be displayed, the colortable defines colors
2869from blue to red, and <span style="font-weight: bold;">slicer_range_limits_dvrp</span>
2870= 290.0, 305.0 then areas with temperature of 290 K are displayed in
2871dark blue and those with 305.0 are displayed in dark red. Temperatures
2872within these limits will be displayed by a continuous color gradient
2873from blue to red and Temperatures outside the limits will
2874be displayed either in dark blue or in dark red.<br> <br>
2875Up to ten different ranges can be assigned in case that more than one
2876slicer has to be displayed.<br> <br>
2877See <a href="#threshold">mode_dvrp</a>
2878for the declaration of color charts.</td> </tr> <tr>
2879<td style="vertical-align: top;"> <p><a name="superelevation"></a><b>superelevation</b></p>
2880</td> <td style="vertical-align: top;">R</td>
2881<td style="vertical-align: top;"><i>1.0</i></td>
2882<td style="vertical-align: top;"> <p>Superelevation
2883factor for the vertical coordinate.&nbsp; </p> <p>For
2884domains with unfavorable ratio between the vertical and
2885the horizontal size
2886(the vertical size is determined by <a href="#nz_do3d">nz_do3d</a>)
2887a <span style="font-weight: bold;">superelevation</span>
2888/= <span style="font-style: italic;">1.0</span> may
2889be used. If e.g. the
2890horizontal size is substantially larger
2891than the vertical size, a <span style="font-weight: bold;">superelevation</span>
2892much larger than <span style="font-style: italic;">1.0</span>
2893should
2894be used, since otherwise the domain appears as a
2895"flat disk" in the visualization and thus the vertical direction is
2896only very poorly resolved.</p> </td> </tr> <tr>
2897<td style="vertical-align: top;"> <p><a name="superelevation_x"></a><b>superelevation_x</b></p>
2898</td> <td style="vertical-align: top;">R<br> </td>
2899<td style="vertical-align: top; font-style: italic;">1.0<br>
2900</td> <td style="vertical-align: top;"> <p>Superelevation
2901factor for the horizontal (x) coordinate.&nbsp; </p> <p>This
2902parameter can be used to stretch the displayed domain
2903along the x-direction. See also <a href="#superelevation">superelevation</a>.</p>
2904</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="superelevation_y"></a><b>superelevation_y</b></p>
2905</td> <td style="vertical-align: top;">R<br> </td>
2906<td style="vertical-align: top; font-style: italic;">1.0<br>
2907</td> <td style="vertical-align: top;">Superelevation
2908factor for the
2909horizontal (y) coordinate.&nbsp; <p>This parameter can be
2910used to
2911stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p> </td>
2912</tr> <tr> <td style="vertical-align: top;">
2913<p><a name="threshold"></a><b>threshold</b></p>
2914</td> <td style="vertical-align: top;">R(10)<br>
2915</td> <td style="vertical-align: top; font-style: italic;">0.0<br>
2916</td> <td style="vertical-align: top;"> <p>Threshold
2917value for which an isosurface is to be created by
2918the <span style="font-weight: bold;">dvrp</span>
2919software.&nbsp; </p> <p>If the creation of
2920isosurfaces is switched on via
2921parameter <a href="#mode_dvrp">mode_dvrp</a>,
2922then the respective threshold value for which the isosurface is to be
2923created can be assigned via <b>threshold</b>. If several
2924isosurfaces
2925are given by <b>mode_dvrp</b>, then an individual
2926threshold value for
2927each isosurface can be assigned. The order of the threshold values
2928refers to the order of the isosurfaces given by <b>mode_dvrp</b>.</p>
2929</td> </tr> </tbody>
2930</table><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
2931</span></span><span style="font-weight: bold;"><span style="font-weight: bold;">Package (<span style="font-weight: bold;">mrun</span>
2932option -p): <span style="font-weight: bold;"><a name="spectra"></a>spectra</span>&nbsp;&nbsp;&nbsp;&nbsp;
2933NAMELIST group name: <span style="font-weight: bold;">spectra_par<br>
2934<br></span></span></span>
2935<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr>
2936<td style="vertical-align: top;"><font size="4"><b>Parameter
2937name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
2938<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
2939<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
2940</tr> <tr> <td style="vertical-align: top;">
2941<p><a name="averaging_interval_sp"></a><b>averaging_interval_sp</b></p>
2942</td> <td style="vertical-align: top;">R<br> </td>
2943<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
2944interval</a></span> </td> <td style="vertical-align: top;"> <p>Averaging interval
2945for spectra output to local
2946file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
2947</font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
2948/ &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
2949(in s).&nbsp; </p> <p>If
2950this parameter is given a non-zero value, temporally
2951averaged spectra data are output. By default, spectra data data are not
2952subject to temporal averaging. The interval length is limited by the
2953parameter <a href="#dt_dosp">dt_dosp</a>. In any
2954case <b>averaging_interval_sp</b> &lt;= <b>dt_dosp
2955</b>must
2956hold.</p>If an interval is defined, then by default the average
2957is calculated
2958from the data values of all timesteps lying within this interval. The
2959number of time levels entering into the average can be reduced with the
2960parameter <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>.
2961<p>If
2962an averaging interval can not be completed at the end of a run, it will
2963be finished at the beginning of the next restart run. Thus for restart
2964runs, averaging intervals do not
2965necessarily begin at the beginning of the run.</p></td> </tr>
2966<tr> <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td>
2967<td style="vertical-align: top;">I(10)</td> <td style="vertical-align: top;"><i>no level</i></td>
2968<td style="vertical-align: top;"> <p>Vertical level
2969for which horizontal spectra are to be
2970calculated and output (gridpoints).<br> </p> <br>
2971Spectra can be calculated for up to ten levels.</td> </tr>
2972<tr><td style="vertical-align: top;"><p><a name="data_output_sp"></a><b>data_output_sp</b></p></td><td style="vertical-align: top;">C*10 (10)</td><td style="vertical-align: top;"><i>10 * ' '</i></td><td style="vertical-align: top;"><p>Quantities for which
2973horizontal spectra are to be calculated
2974and output.</p> <p>Allowed values are:&nbsp; <b>data_output_sp</b>
2975= <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>, <span style="font-style: italic;">'w'</span>, <span style="font-style: italic;">'pt'</span>, <span style="font-style: italic;">'q'</span>.<br> </p>
2976<p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p>
2977<p>By default spectra data are output to the local file <a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>.
2978The file's format is NetCDF.&nbsp; Further details about processing
2979NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>The
2980temporal interval of the output times of profiles is
2981assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>.&nbsp;</p><p>The
2982vertical levels for which spectra are to be computed and output must be
2983given by parameter <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.
2984</p><span style="font-weight: bold;">Note:</span><br>
2985Beside <span style="font-weight: bold;">data_output_sp</span>,
2986values <span style="font-weight: bold;">must</span>
2987be given for each of the
2988parameters,&nbsp; <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>,
2989and <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a></font>,
2990otherwise <span style="font-weight: bold;">no</span>
2991output will be
2992created!<br><br><br>
2993Calculation of spectra requires cyclic boundary conditions
2994along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
2995and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For
2996historical reasons, data can also be output in ASCII-format on local
2997files <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
2998and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
2999(depending on the direction(s) along which spectra are to be
3000calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font>
3001which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See
3002parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
3003for defining the format in which data shall be output.&nbsp;Within
3004these file, the spectra are ordered with respect to their
3005output times. Spectra can also be temporally averaged (see <a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a>
3006).&nbsp;<font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a
3007spectrum is output in a single line (1st column:
3008wavenumber, 2nd column: spectral coefficient). If spectra are to be
3009calculated and output for more than one height (see </font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font><font>),
3010the spectral coefficients for the further heighs can be found in the
3011subsequent columns. </font>The order
3012of the data in the file follows the order used in the assignment for <b>data_output_sp</b>
3013(<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
3014means that the file starts with the spectra of the u-component,
3015followed by the v-component spectra, etc.). Additional to the files
3016PLOTSP_X_DATA and PLOTSP_Y_DATA which contain
3017the data,
3018PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a>
3019and <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_Y_PAR</a>)
3020which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>.
3021Spectra can be directly plotted with <span style="font-weight: bold;">profil</span>
3022using the data and the corresponding parameter file. The
3023plot layout is
3024steered via the parameter input file. The vertical levels for which
3025spectra are to be plotted must be given by <font><a href="chapter_4.2.html#plot_spectra_level"><span lang="en-GB"><font face="Thorndale">plot_spectra_level</font></span></a></font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"></span></a></font>. <span style="font-weight: bold;"></span>Otherwise, no
3026spectra
3027will appear on the plot, although data are available on file. All
3028parameter values can be changed by editing the parameter
3029input
3030file.<span style="font-weight: bold;"><br></span></td></tr><tr>
3031<td style="vertical-align: top;"> <p><a name="dt_dosp"></a><b>dt_dosp</b></p>
3032</td> <td style="vertical-align: top;">R</td>
3033<td style="vertical-align: top;"><i>value of
3034&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
3035<td style="vertical-align: top;"> <p>Temporal
3036interval at which&nbsp;spectra data shall be output
3037(in s).&nbsp; </p> <p><span lang="en-GB"><font face="Thorndale">If output of
3038horizontal spectra is switched on (see </font></span><a href="#data_output_sp"><span lang="en-GB"><font face="Thorndale">data_output_sp</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
3039parameter can be used to
3040assign the temporal interval at which spectral data&nbsp; shall be
3041output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
3042simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>,
3043which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
3044time is the beginning of
3045&nbsp;the simulation, i.e. output takes place at times t = <span style="font-weight: bold;">skip_time_dosp</span> + <b>dt_dosp</b>,
3046<span style="font-weight: bold;">skip_time_dosp</span>
3047+ 2*<b>dt_dosp</b>, skip_time_dosp + 3*<b>dt_dosp</b>,
3048etc. The actual output times can
3049deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).&nbsp;
3050If <b>dt_dosp</b> &lt; </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then
3051spectral data are output
3052after each time step (if this is requested it should be <b>dt_dosp</b>
3053= <i>0</i>).</font></span> </p> </td>
3054</tr> <tr> <td style="vertical-align: top;">
3055<p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p>
3056</td> <td style="vertical-align: top;">I(10)</td>
3057<td style="vertical-align: top;"><i>no level</i></td>
3058<td style="vertical-align: top;"> <p>Vertical
3059level(s) for which horizontal spectra are to be
3060plotted (in gridpoints).&nbsp; </p> <p>This parameter
3061only affects the display of spectra in plots
3062created with <span style="font-weight: bold;">profil</span>.
3063The
3064spectral data created and output to file are exclusively determined via
3065<font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p>
3066</td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td>
3067<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
3068</td> <td style="vertical-align: top;">No output of
3069spectra data before this interval has passed (in s).<br><br>This
3070parameter causes that data output activities are starting not before
3071this interval
3072(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
3073the user has set <a href="#dt_dosp">dt_dosp</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dosp</span> = <span style="font-style: italic;">1800.0</span>, then the
3074first output will be done at t = 5400 s. </td> </tr>
3075<tr> <td style="vertical-align: top;"> <p><a name="spectra_direction"></a><b>spectra_direction</b></p>
3076</td> <td style="vertical-align: top;">C*2 (10)</td>
3077<td style="vertical-align: top;"><i>10 * ' '</i></td>
3078<td style="vertical-align: top;"> <p>Direction(s)
3079along which spectra are to be calculated.&nbsp; </p> <p>Allowed
3080values are <span style="font-style: italic;">'x'</span>,
3081<span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For
3082every quantity given by <a href="#data_output_sp">data_output_sp</a>
3083a corresponding
3084direction<span style="font-weight: bold;"> </span>must
3085be assigned.<br> </p> <p>Calculation of spectra
3086requires cyclic boundary conditions
3087along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
3088and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</p>
3089</td> </tr> </tbody>
3090</table><span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
3091</span></span></span><h3 style="line-height: 100%;"><br>
3092<a href="chapter_4.1.html"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></a><a href="index.html"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></a><a href="chapter_4.3.html"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></a></h3><span style="font-style: italic;">Last change:</span>
309322/08/06 (SR)<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
3094</span></span><br>
3095</body></html>
Note: See TracBrowser for help on using the repository browser.