Home


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

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

Last change on this file since 240 was 240, checked in by letzel, 16 years ago
  • External pressure gradient (check_parameters, init_3d_model, header, modules, parin, prognostic_equations)
  • New topography case 'single_street_canyon'
  • Property svn:keywords set to Id
File size: 266.1 KB
RevLine 
[5]1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
[116]2<html><head>
[108]3
4
5
6 
7 
8  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
9
10
11 
12 
[116]13  <title>PALM chapter 4.2</title></head>
[108]14<body>
15
16
17<h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
[102]18parameters</a>, <a href="#particle_parameters">particle parameters</a>, and <a href="#Paketparameter">package
[5]19parameters</a></h3>
[108]20
21
22
[48]23<h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3>
[108]24
25
26
27<br>
28
29
30<br>
31
32
33<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
34
35
36 <tbody>
37
38
39
40    <tr>
41
42
43
44      <td style="vertical-align: top;"><font size="4"><b>Parameter
45name</b></font></td>
46
47
48 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
49
50
51
52      <td style="vertical-align: top;"> 
53     
54     
55      <p><b><font size="4">Default</font></b> <br>
56
57
58 <b><font size="4">value</font></b></p>
59
60
61 </td>
62
63
64
65      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
66
67
68
69    </tr>
70
71
72 <tr>
73
74
75 <td style="vertical-align: top;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
76
77
78
79      </td>
80
81
82 <td style="vertical-align: top;">R<br>
83
84
85 </td>
86
87
88
89      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
90
91
92 </td>
93
94
95
96      <td style="vertical-align: top;">Averaging interval for
97all&nbsp;output of temporally averaged data (in s).<br>
98
99
100      <br>
101
102
103This
[5]104parameter defines the time interval length for temporally averaged data
105(vertical profiles, spectra, 2d cross-sections, 3d volume data). By
[48]106default,&nbsp;data are not subject to temporal averaging. The
107interval
108length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
109In any case, <span style="font-weight: bold;">averaging_interval</span>
110&lt;= <span style="font-weight: bold;">dt_data_output_av</span>
[108]111must hold.<br>
112
113
114      <br>
115
116
117If
[5]118an interval is defined, then by default the average is calculated from
119the data values of all timesteps lying within this interval. The number
120of time levels entering into the average can be reduced with the
[108]121parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br>
122
123
124      <br>
125
126
127If
[48]128an averaging interval can not be completed at the end of a run, it
[5]129will be finished at the beginning of the next restart run. Thus for
130restart runs, averaging intervals do not
[108]131necessarily begin at the beginning of the run.<br>
132
133
134      <br>
135
136
137Parameters
138      <a href="#averaging_interval_pr">averaging_interval_pr</a>
[48]139and <a href="#averaging_interval_sp">averaging_interval_sp</a>
140can be used to define different averaging intervals for vertical
[108]141profile data and spectra, respectively.<br>
142
143
144 </td>
145
146
147 </tr>
148
149
150
151    <tr>
152
153
154 <td style="vertical-align: top;"> 
155     
156     
157      <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
158
159
160
161      </td>
162
163
164 <td style="vertical-align: top;">R<br>
165
166
167 </td>
168
169
170
171      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
172
173
174
[5]175interval</a><br>
[108]176
177
178
179      </span> </td>
180
181
182 <td style="vertical-align: top;">
183     
184     
185      <p>Averaging
[61]186interval for output of vertical profiles&nbsp;to
[48]187local
188file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
[108]189      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
190(in s).&nbsp; </p>
191
192
193 
194     
195     
196      <p>If
[5]197this parameter is given a non-zero value, temporally
198averaged vertical profile data are output. By default, profile data
199data are not subject to temporal averaging. The interval length is
[48]200limited by the parameter <a href="#dt_dopr">dt_dopr</a>.
201In any case <b>averaging_interval_pr</b> &lt;= <b>dt_dopr
[108]202      </b>must
203hold.</p>
204
205
206If an interval is defined, then by default the average
[48]207is calculated
[5]208from the data values of all timesteps lying within this interval. The
209number of time levels entering into the average can be reduced with the
210parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>.
[108]211     
212     
213      <p>If
[5]214an averaging interval can not be completed at the end of a run, it will
215be finished at the beginning of the next restart run. Thus for restart
216runs, averaging intervals do not
[108]217necessarily begin at the beginning of the run.</p>
218
219
220 </td>
221
222
223 </tr>
224
225
226
227    <tr>
228
229
230 <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
231
232
233
234substeps</span></td>
235
236
237 <td style="vertical-align: top;">L<br>
238
239
240
241      </td>
242
243
244 <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
245
246
247 </td>
248
249
250
251      <td style="vertical-align: top;">Switch
252to steer the call of the pressure solver.<br>
253
254
255 <br>
256
257
258
[5]259In order to speed-up performance, the Poisson equation for perturbation
[48]260pressure (see <a href="#psolver">psolver</a>) can
261be called only at the last substep of multistep Runge-Kutta
262timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>)
263by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span>
264= <span style="font-style: italic;">.F.</span>.
[5]265In many cases, this sufficiently reduces the divergence of the velocity
266field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this
267case and in case
[48]268of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span>
269= <span style="font-style: italic;">.T.</span>
270should be used.&nbsp;<span style="font-weight: bold;"></span></td>
[108]271
272
273
274    </tr>
275
276
277 <tr>
278
279
280 <td style="vertical-align: top;">
281     
282     
283      <p><a name="fcl_factor"></a><b>cfl_factor</b></p>
284
285
286
287      </td>
288
289
290 <td style="vertical-align: top;">R<br>
291
292
293 </td>
294
295
296
297      <td style="vertical-align: top;"> 
298     
299     
300      <p><i>0.1,
3010.8 or 0.9</i> <br>
302
303
304 <i>(see right)</i></p>
305
306
307
308      </td>
309
310
311 <td style="vertical-align: top;"> 
312     
313     
314      <p lang="en-GB">Time step limiting factor.&nbsp; </p>
315
316
317
318     
319     
320      <p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
[48]321allowed </span>time step according to CFL and
322diffusion-criterion
323dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">=
324dt_max * <b>cfl_factor</b>
[5]325in order to avoid stability problems which may arise in the vicinity of
[48]326the maximum allowed timestep. The condition <i>0.0</i>
327&lt; <b>cfl_factor</b>
[108]328&lt; <i>1.0 </i>applies.<br>
329
330
331 </span></p>
332
333
334
335     
336     
337      <p><span lang="en-GB">The default value of
[48]338cfl_factor depends on
[108]339the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br>
340
341
342 </span></p>
343
344
345 
346     
347     
348      <p><span lang="en-GB">For the third order Runge-Kutta scheme it
349is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br>
350
351
352 </span></p>
353
354
355 
356     
357     
358      <p><span lang="en-GB">In case of the leapfrog scheme a quite
[5]359restrictive value of <span style="font-weight: bold;">cfl_factor</span>
[48]360= <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
361divergence
[5]362significantly 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
363be used with the leapfrog scheme but these are to be determined by
364appropriate test runs.<span style="font-family: times new roman;"><br>
[108]365
366
367
368      </span></span></p>
369
370
371 <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
[48]372scheme is <span style="font-weight: bold;">cfl_factor</span>
373= <span style="font-style: italic;">0.8</span> .</font></span></td>
[108]374
375
376
377    </tr>
378
379
380    <tr>
381
382
383 <td style="vertical-align: top;"> 
384     
385     
386      <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
387
388
389
390      </td>
391
392
393 <td style="vertical-align: top;">L<br>
394
395
396 </td>
397
398
399
400      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
401
402
403 </td>
404
405
406
407      <td style="vertical-align: top;"> 
408     
409     
410      <p>Switch to
[48]411impose random perturbations to the horizontal
[108]412velocity field.&nbsp; </p>
413
414
415 
416     
417     
418      <p>With <b>create_disturbances</b>
[48]419= <i>.T.,</i> random
[5]420perturbations can be imposed to the horizontal velocity field at
421certain times e.g. in order to trigger off the onset of convection,
[108]422etc..<br>
423
424
425 </p>
426
427
428 
429     
430     
431      <p>The temporal interval between
[48]432these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
[5]433the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a>
434and <a href="#disturbance_level_t">disturbance_level_t</a>,
435and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>.
436In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
437and <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
438the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a>
439and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>.
440A perturbation is added to each grid point with its individual value
441determined by multiplying the disturbance amplitude with a uniformly
442distributed random number.
443After this, the arrays of u and v are smoothed by applying a
444Shuman-filter twice and made divergence-free by applying the pressure
[108]445solver.<br>
446
447
448 </p>
449
450
451 
452     
453     
454      <p>The random number generator to
[48]455be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br>
[108]456
457
458
459      </p>
460
461
462 
463     
464     
465      <p>As soon as the desired flow features have
[48]466developed
467(e.g.&nbsp; convection has started), further imposing of
468perturbations
[5]469is not necessary and can be omitted (this does not hold for non-cyclic
470lateral boundaries!). This can be steered by assigning
471an upper limit value for the perturbation energy (the perturbation
472energy is defined by the deviation of the velocity from the mean flow)
473using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>.
474As soon as the perturbation energy has exceeded this energy limit, no
475more random perturbations are assigned<br>
[108]476
477
478
[5]479.&nbsp; <br>
[108]480
481
482
[5]483Timesteps where a random perturbation has been imposed are marked in
484the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
485by the character "D" appended to the values of the maximum horizontal
[108]486velocities. </p>
487
488
489 </td>
490
491
492 </tr>
493
494
495 <tr>
496
497
498 <td style="vertical-align: top;"> 
499     
500     
501      <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
502
503
504
505      </td>
506
507
508 <td style="vertical-align: top;">C*10&nbsp;
509      <br>
510
511
512&nbsp;&nbsp; (100)</td>
513
514
515 <td style="vertical-align: top;"><i>100 * ' '</i></td>
516
517
518
519      <td style="vertical-align: top;"> 
520     
521     
522      <p>Type of
[48]523normalization applied to the x-coordinate of vertical
[5]524profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
[108]525
526
527
528     
529     
530      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
531= <span style="font-style: italic;">'profil'</span>.</p>
532
533
534     
535     
536      <p>If
[48]537vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
538local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
[5]539parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
540the x-values of the data points can be normalized with respect to
541certain quantities (e.g. the near-surface heat flux) in order to ensure
542a better comparability. This type of normalization then applies to all
543profiles of one coordinate system (panel). The normalization quantities
544are re-calculated for each output time of each individual profile. If
545temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>),
546then the normalization quantities are also temporally averaged
547accordingly. If the value of a normalization quantity becomes zero,
548then normalization for the total respective coordinate system (panel)
[108]549is switched off automatically (also for the y-axis).<br>
550
551
552 </p>
553
554
555
556     
557     
558      <p>By default, the normalization quantities are calculated as the
[5]559horizontal mean of the total model domain and and these values are also
560used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
561Instead of this, they can be calculated from the data of a certain
562subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a>
563(however, they are used again for all subdomains and even for the total
[108]564domain).&nbsp; </p>
565
566
567 
568     
569     
570      <p>The user can choose between
[48]571the following normalization
[108]572quantities: <br>
573
574
575 </p>
576
577
578 
579     
580     
581      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
582
583
584 <tbody>
585
586
587 <tr>
588
589
590 <td style="vertical-align: top;"><i>'wpt0'</i></td>
591
592
593
594            <td style="vertical-align: top;">Normalization with
[48]595respect
[5]596to the total surface sensible heat
[108]597flux (k=0 ).</td>
598
599
600 </tr>
601
602
603 <tr>
604
605
606 <td style="vertical-align: middle;"><i>'ws2'</i></td>
607
608
609
610            <td style="vertical-align: top;">Normalization with
[48]611respect
[5]612to w<sub>*</sub> <sup>2</sup>
613(square of the characteristic vertical wind speed of the CBL)</td>
[108]614
615
616
617          </tr>
618
619
620 <tr>
621
622
623 <td style="vertical-align: top;"><i>'tsw2'</i></td>
624
625
626
627            <td style="vertical-align: top;">Normalization with
[48]628respect
[5]629to the square of the characteristic
[48]630temperature of the CBL theta<sub>*</sub> (this is defined
631as ratio of
[108]632the surface heat flux and w<sub>*</sub>).</td>
633
634
635 </tr>
636
637
638
639          <tr>
640
641
642 <td style="vertical-align: middle;"><i>'ws3'</i></td>
643
644
645
646            <td style="vertical-align: top;">Normalization with
[48]647respect
[108]648to w<sub>*</sub> <sup>3</sup>.</td>
649
650
651 </tr>
652
653
654
655          <tr>
656
657
658 <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
659
660
661
662            <td style="vertical-align: top;">Normalization with
[48]663respect
[5]664to w<sub>*</sub><sup>2</sup>theta<sub>*</sub>
665(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
[108]666
667
668
669          </tr>
670
671
672 <tr>
673
674
675 <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
676
677
678
679            <td style="vertical-align: top;">Normalization with
[48]680respect
[5]681to w<sub>*</sub><sup>2 </sup>theta<sub>*</sub>
682(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
[108]683
684
685
686          </tr>
687
688
689 
690       
691       
692        </tbody> 
693     
694     
695      </table>
696
697
698 
699     
700     
701      <p>For each
[48]702coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>)
703an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> =
[108]704      <span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
[48]705then the
[5]706x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
[48]707and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>.
708Data
[5]709of the further coordinate systems (if any are to be drawn) are not
[108]710normalized.&nbsp; </p>
711
712
713 
714     
715     
716      <p>Using a normalization
[48]717leaves all vertical profile data on
[5]718local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
[48]719unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the
720normalization is steered
[5]721by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a>
722which may be changed subsequently by the user in the parameter file
723(local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
[108]724
725
726
[5]727&nbsp;<br>
[108]728
729
730
[5]731The assigned normalization quantity is noted in the axes labels of the
732respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
[108]733
734
735
736      </td>
737
738
739 </tr>
740
741
742 <tr>
743
744
745 <td style="vertical-align: top;"> 
746     
747     
748      <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
749
750
751
752      </td>
753
754
755 <td style="vertical-align: top;">C*10&nbsp;
756      <br>
757
758
759&nbsp;&nbsp; (100)</td>
760
761
762 <td style="vertical-align: top;"><i>100 * ' '</i></td>
763
764
765
766      <td style="vertical-align: top;"> 
767     
768     
769      <p>Type of
[48]770normalization applied to the y-coordinate of vertical
[5]771profiles to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;</p>
[108]772
773
774
775     
776     
777      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
778= <span style="font-style: italic;">'profil'</span>.</p>
779
780
781     
782     
783      <p>If
[48]784vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
785local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
[5]786parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
787the y-values of the data points can be normalized with respect to
788certain quantities (at present only the normalization with respect to
789the boundary layer height is possible) in order to ensure a better
[108]790comparability. </p>
791
792
793 
794     
795     
796      <p>The user can choose between the
[48]797following normalization
[108]798quantities: <br>
799
800
801 </p>
802
803
804 
805     
806     
807      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
808
809
810 <tbody>
811
812
813 <tr>
814
815
816 <td style="vertical-align: top;"><i>'z_i'</i></td>
817
818
819
820            <td style="vertical-align: top;">Normalization with
[48]821respect
[5]822to the boundary layer height
823(determined from the height where the heat flux achieves its minimum
[108]824value).</td>
825
826
827 </tr>
828
829
830 
831       
832       
833        </tbody> 
834     
835     
836      </table>
837
838
839 
840     
841     
842      <p>For
[48]843further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p>
[108]844
845
846
847      </td>
848
849
850 </tr>
851
852
853 <tr>
854
855
856 <td style="vertical-align: top;"> 
857     
858     
859      <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
860
861
862
863      </td>
864
865
866 <td style="vertical-align: top;">C*100&nbsp;
867      <br>
868
869
870&nbsp;&nbsp; (100)</td>
871
872
873 <td style="vertical-align: top;">see right<br>
874
875
876 </td>
877
878
879
880      <td style="vertical-align: top;"> 
881     
882     
883      <p>Determines
[48]884which vertical profiles are to be presented in
885which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used.
[108]886&nbsp; </p>
887
888
889 
890     
891     
892      <p>This parameter only applies for
[48]893&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
[108]894= <span style="font-style: italic;">'profil'</span>.</p>
895
896
897     
898     
899      <p>The
900default assignment is:&nbsp; </p>
901
902
903 
904     
905     
906      <p><b>cross_profiles</b>
907=&nbsp; </p>
908
909
910 
911     
912     
913      <ul>
914
915
916 
917       
918       
919        <p><span style="font-family: monospace; font-style: italic;">'
920u v ',</span><br>
921
922
923 <span style="font-family: monospace; font-style: italic;">' pt
924',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
925
926
927 <span style="font-family: monospace; font-style: italic;">'
928w"pt" w*pt* w*pt*BC wpt wptBC ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
929
930
931 <span style="font-family: monospace; font-style: italic;">'
932w"u" w*u* wu w"v"w*v* wv ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
933
934
935 <span style="font-family: monospace; font-style: italic;">' km
936kh ',</span><br style="font-family: monospace; font-style: italic;">
937
938
939 <span style="font-family: monospace; font-style: italic;">' l '
[5]940,</span><br>
[108]941
942
943
[48]94414 * <span style="font-family: monospace; font-style: italic;">'
[108]945'</span></p>
946
947
948 
949     
950     
951      </ul>
952
953
954 
955     
956     
957      <p>If plot output of
[48]958vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
[5]959the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.
960Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
961which describes the layout for a plot to be generated with the plot
[48]962program <span style="font-weight: bold;">profil</span>.
963The parameter <b>cross_profiles</b>
[5]964determines how many coordinate systems (panels) the plot contains and
965which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
966expects a character string (up to 100 characters long) for each
967coordinate system, which consists of the names of the profiles to be
968drawn into this system (all available profiles and their respective
969names are described at parameter <a href="#data_output_pr">data_output_pr</a>).
970The single names have to be separated by one blank (' ') and a blank
[48]971must be spent also at the beginning and at the end of the
[108]972string.&nbsp; </p>
973
974
975 
976     
977     
978      <p>Example:&nbsp; </p>
979
980
981 
982     
983     
984      <ul>
985
986
987
988       
989       
990        <p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
991' pt '</span></p>
992
993
994 
995     
996     
997      </ul>
998
999
1000 
1001     
1002     
1003      <p>In this case the
[48]1004plot consists of two coordinate systems
[5]1005(panels) with the first panel containing the profiles of the horizontal
[48]1006velocity components (<span style="font-style: italic;">'u'</span>
1007and <span style="font-style: italic;">'v'</span>)
1008of all output times (see <a href="#dt_dopr">dt_dopr</a>)
[5]1009and the second one containing the profiles of the potential temperature
1010(<span style="font-style: italic;">'pt'</span>).<br>
[108]1011
1012
1013
1014      </p>
1015
1016
1017 
1018     
1019     
1020      <p>Whether the coordinate systems are actually drawn,
[48]1021depends on
[5]1022whether data of the appropriate profiles were output during the run
1023(profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>).
[48]1024For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned,
1025then
[5]1026the plot only consists of one panel, since no profiles of the potential
1027temperature were output. On the other hand, if profiles were assigned
1028to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>,
1029then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
[108]1030but they are not drawn in the plot. <br>
1031
1032
1033 </p>
1034
1035
1036
[5]1037The arrangement of the panels in the plot can be controlled
1038with the parameters <a href="#profile_columns">profile_columns</a>
1039and <a href="#profile_rows">profile_rows</a>.
1040Up to 100 panels systems are allowed in a plot (however, they may be
[108]1041distributed on several pages).</td>
1042
1043
1044 </tr>
1045
1046
1047 <tr>
1048
1049
1050 <td style="vertical-align: top;"> 
1051     
1052     
1053      <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
1054
1055
1056
1057      </td>
1058
1059
1060 <td style="vertical-align: top;">C*40&nbsp;
1061      <br>
1062
1063
1064&nbsp;&nbsp; (100)</td>
1065
1066
1067 <td style="vertical-align: top;">see right<br>
1068
1069
1070 </td>
1071
1072
1073
1074      <td style="vertical-align: top;"> 
1075     
1076     
1077      <p>x-axis labels
[48]1078of vertical profile coordinate systems to be
1079plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
[108]1080      </p>
1081
1082
1083 
1084     
1085     
1086      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1087= <span style="font-style: italic;">'profil'</span>.</p>
1088
1089
1090     
1091     
1092      <p>The
1093default assignment is:&nbsp; </p>
1094
1095
1096 
1097     
1098     
1099      <p><b>cross_xtext</b>
1100=&nbsp; </p>
1101
1102
1103 
1104     
1105     
1106      <ul>
1107
1108
1109 
1110       
1111       
1112        <p><span style="font-style: italic;">'wind speed in
1113ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1114
1115
1116 <span style="font-style: italic;">'pot. temperature in
[5]1117K',&nbsp; </span><br style="font-style: italic;">
[108]1118
1119
1120
1121        <span style="font-style: italic;">'heat flux in K
1122ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1123
1124
1125 <span style="font-style: italic;">'momentum flux in
1126m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;">
1127
1128
1129 <span style="font-style: italic;">'eddy diffusivity in
1130m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1131
1132
1133 <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
1134        <br>
1135
1136
113714 * <span style="font-style: italic;">' '</span></p>
1138
1139
1140
1141     
1142     
1143      </ul>
1144
1145
1146 
1147     
1148     
1149      <p>This parameter can be used to assign x-axis
[48]1150labels to vertical
1151profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output
1152of vertical
[5]1153profile data see <a href="#data_output_pr">data_output_pr</a>).<br>
[108]1154
1155
1156
[5]1157The labels are assigned to those coordinate systems (panels) defined by
[108]1158      <a href="#cross_profiles">cross_profiles</a>
[5]1159according to their respective order (compare the default values of <b>cross_xtext</b>
[108]1160and <b>cross_profiles</b>). </p>
1161
1162
1163 
1164     
1165     
1166      <p>Umlauts
[48]1167are possible (write &ldquo; in front of, similar to TeX), as
1168well as super- and subscripts (use "&gt;" or "&lt;" in front of
1169each
[5]1170character), special characters etc. (see UNIRAS manuals) when using the
1171plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p>
[108]1172
1173
1174
1175      </td>
1176
1177
1178 </tr>
1179
1180
1181 <tr>
1182
1183
1184 <td style="vertical-align: top;"> 
1185     
1186     
1187      <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
1188
1189
1190
1191      </td>
1192
1193
1194 <td style="vertical-align: top;">C*1</td>
1195
1196
1197
1198      <td style="vertical-align: top;"><i>'w'</i></td>
1199
1200
1201
1202      <td style="vertical-align: top;"> 
1203     
1204     
1205      <p>Type of cycle
1206to be used with the multi-grid method.&nbsp; </p>
1207
1208
1209 
1210     
1211     
1212      <p>This
[48]1213parameter determines which type of cycle is applied in
[5]1214the multi-grid method used for solving the Poisson equation for
1215perturbation pressure (see <a href="#psolver">psolver</a>).
1216It defines in which way it is switched between the fine and coarse
1217grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b>
[48]1218may be assigned the values <i>'v'</i> or <i>'w'</i>).
1219The
[5]1220computational cost of w-cycles is much higher than that of v-cycles,
[108]1221however, w-cycles give a much better convergence. </p>
1222
1223
1224 </td>
1225
1226
1227
1228    </tr>
1229
1230
1231 <tr>
1232
1233
1234 <td style="vertical-align: top;">
1235     
1236     
1237      <p><a name="data_output"></a><b>data_output</b></p>
1238
1239
1240
1241      </td>
1242
1243
1244 <td style="vertical-align: top;">C * 10 (100)<br>
1245
1246
1247
1248      </td>
1249
1250
1251 <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
1252
1253
1254
1255      </td>
1256
1257
1258 <td style="vertical-align: top;">Quantities
1259for which 2d cross section and/or 3d volume data are to be output.<br>
1260
1261
1262      <br>
1263
1264
1265PALM
[5]1266allows the output of instantaneous data as well as of temporally
1267averaged data which is steered by the strings assigned to this
[108]1268parameter (see below).<br>
1269
1270
1271      <br>
1272
1273
1274By default, cross section
[48]1275data are output (depending on the selected cross sections(s), see
1276below)&nbsp; to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>,
[108]1277      <a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
[48]1278and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>.
1279Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>.
1280If the user has switched on the output of temporally averaged data,
1281these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>,
[108]1282      <a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
1283      <a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
[48]1284and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
[108]1285respectively.<br>
1286
1287
1288      <br>
1289
1290
1291The
[5]1292filenames already suggest that all files have NetCDF format.
1293Informations about the file content (kind of quantities, array
1294dimensions and grid coordinates) are part of the self describing NetCDF
1295format and can be extracted from the NetCDF files using the command
[48]1296"ncdump -c &lt;filename&gt;". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing
[108]1297the PALM NetCDF data.<br>
1298
1299
1300      <br>
1301
1302
1303The following quantities are
1304available for output by default (quantity names ending with '*' are only allowed for the output of horizontal cross sections):<br>
1305
1306
1307      <br>
1308
1309
1310     
1311     
1312      <table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2">
1313
1314
1315        <tbody>
1316
1317
1318          <tr>
1319
1320
1321            <td style="width: 106px;"><span style="font-weight: bold;">quantity
1322name</span></td>
1323
1324
1325            <td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td>
1326
1327
1328            <td><span style="font-weight: bold;">unit</span></td>
1329
1330
1331            <td><span style="font-weight: bold;">remarks</span></td>
1332
1333
1334          </tr>
1335
1336
1337          <tr>
1338
1339
1340            <td style="width: 106px;"><span style="font-style: italic;">e</span></td>
1341
1342
1343            <td style="width: 196px;">SGS TKE</td>
1344
1345
1346            <td>m<sup>2</sup>/s<sup>2</sup></td>
1347
1348
1349            <td></td>
1350
1351
1352          </tr>
1353
1354
1355          <tr>
1356
1357
1358            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td>
1359
1360
1361            <td style="width: 196px; vertical-align: top;">liquid water path</td>
1362
1363
1364            <td style="vertical-align: top;">m</td>
1365
1366
1367            <td style="vertical-align: top;">only horizontal cross section
[48]1368is allowed,&nbsp;requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
[108]1369= <span style="font-style: italic;">.TRUE.</span></td>
1370
1371
1372          </tr>
1373
1374
1375          <tr>
1376
1377
1378            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td>
1379
1380
1381            <td style="width: 196px; vertical-align: top;">perturpation
1382pressure</td>
1383
1384
1385            <td style="vertical-align: top;">N/m<sup>2</sup>,
1386Pa</td>
1387
1388
1389            <td style="vertical-align: top;"></td>
1390
1391
1392          </tr>
1393
1394
1395          <tr>
1396
1397
1398            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td>
1399
1400
1401            <td style="width: 196px; vertical-align: top;">particle/droplet
1402concentration</td>
1403
1404
1405            <td style="vertical-align: top;">#/gridbox</td>
1406
1407
1408            <td style="vertical-align: top;">requires that particle
[48]1409advection is switched on by <span style="font-weight: bold;">mrun</span>-option
[108]1410"-p particles"</td>
1411
1412
1413          </tr>
1414
1415
1416          <tr>
1417
1418
1419            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td>
1420
1421
1422            <td style="width: 196px; vertical-align: top;">mean
1423particle/droplet radius </td>
1424
1425
1426            <td style="vertical-align: top;">m</td>
1427
1428
1429            <td style="vertical-align: top;">requires that particle
[48]1430advection is switched on by <span style="font-weight: bold;">mrun</span>-option
[108]1431"-p particles"</td>
1432
1433
1434          </tr>
1435
1436
1437          <tr>
1438
1439
1440            <td style="vertical-align: top;"><span style="font-style: italic;">pra*</span></td>
1441
1442
1443            <td style="vertical-align: top;">precipitation amount</td>
1444
1445
1446            <td style="vertical-align: top;">mm</td>
1447
1448
1449            <td style="vertical-align: top;">only horizontal cross section
[72]1450is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
[108]1451= <span style="font-style: italic;">.TRUE., </span>time interval on which amount refers to is defined by <a href="#precipitation_amount_interval">precipitation_amount_interval</a></td>
1452
1453
1454          </tr>
1455
1456
1457          <tr>
1458
1459
1460            <td style="vertical-align: top;"><span style="font-style: italic;">prr*</span></td>
1461
1462
1463            <td style="vertical-align: top;">precipitation rate</td>
1464
1465
1466            <td style="vertical-align: top;">mm/s</td>
1467
1468
1469            <td style="vertical-align: top;">only horizontal cross section
[72]1470is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
[108]1471= <span style="font-style: italic;">.TRUE.</span></td>
1472
1473
1474          </tr>
1475
1476
1477          <tr>
1478
1479
1480            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td>
1481
1482
1483            <td style="width: 196px; vertical-align: top;">potential
1484temperature<br>
1485
1486
1487            </td>
1488
1489
1490            <td style="vertical-align: top;">K</td>
1491
1492
1493            <td style="vertical-align: top;"></td>
1494
1495
1496          </tr>
1497
1498
1499          <tr>
1500
1501
1502            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td>
1503
1504
1505            <td style="width: 196px; vertical-align: top;">specific humidity
1506(or total water content, if cloud physics is switched on)</td>
1507
1508
1509            <td style="vertical-align: top;">kg/kg</td>
1510
1511
1512            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
1513
1514
1515          </tr>
1516
1517
1518          <tr>
1519
1520
1521            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td>
1522
1523
1524            <td style="width: 196px; vertical-align: top;">liquid water
1525content</td>
1526
1527
1528            <td style="vertical-align: top;">kg/kg</td>
1529
1530
1531            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
[48]1532= <span style="font-style: italic;">.TRUE.</span>
1533or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
[108]1534= <span style="font-style: italic;">.TRUE.</span></td>
1535
1536
1537          </tr>
1538
1539
1540          <tr>
1541
1542
1543            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td>
1544
1545
1546            <td style="width: 196px; vertical-align: top;">change in liquid
1547water content due to condensation/evaporation during last timestep</td>
1548
1549
1550            <td style="vertical-align: top;">kg/kg</td>
1551
1552
1553            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1554= <span style="font-style: italic;">.TRUE.</span></td>
1555
1556
1557          </tr>
1558
1559
1560          <tr>
1561
1562
1563            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td>
1564
1565
1566            <td style="width: 196px; vertical-align: top;">volume of liquid
1567water</td>
1568
1569
1570            <td style="vertical-align: top;">m<sup>3</sup>/gridbox</td>
1571
1572
1573            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1574= <span style="font-style: italic;">.TRUE.</span></td>
1575
1576
1577          </tr>
1578
1579
1580          <tr>
1581
1582
1583            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td>
1584
1585
1586            <td style="width: 196px; vertical-align: top;">weighting factor</td>
1587
1588
1589            <td style="vertical-align: top;"></td>
1590
1591
1592            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1593= <span style="font-style: italic;">.TRUE.</span></td>
1594
1595
1596          </tr>
1597
1598
1599          <tr>
1600
1601
1602            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td>
1603
1604
1605            <td style="width: 196px; vertical-align: top;">water vapor
1606content (specific humidity)</td>
1607
1608
1609            <td style="vertical-align: top;">kg/kg</td>
1610
1611
1612            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
1613= <span style="font-style: italic;">.TRUE.</span></td>
1614
1615
1616          </tr>
1617
1618
1619          <tr>
1620
1621
1622            <td align="undefined" valign="undefined"><span style="font-style: italic;">rho</span></td>
1623
1624
1625            <td align="undefined" valign="undefined">potential density</td>
1626
1627
1628            <td align="undefined" valign="undefined">kg/m<sup>3</sup></td>
1629
1630
1631            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
1632= <span style="font-style: italic;">.TRUE.</span></td>
1633
1634
1635          </tr>
1636
1637
1638          <tr>
1639
1640
1641            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td>
1642
1643
1644            <td style="width: 196px; vertical-align: top;">concentration of
1645the scalar</td>
1646
1647
1648            <td style="vertical-align: top;">1/m<sup>3</sup></td>
1649
1650
1651            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
1652= <span style="font-style: italic;">.TRUE.</span></td>
1653
1654
1655          </tr>
1656
1657
1658          <tr>
1659
1660
1661            <td align="undefined" valign="undefined"><span style="font-style: italic;">sa</span></td>
1662
1663
1664            <td align="undefined" valign="undefined">salinity</td>
1665
1666
1667            <td align="undefined" valign="undefined">psu</td>
1668
1669
1670            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
1671= <span style="font-style: italic;">.TRUE.</span></td>
1672
1673
1674          </tr>
1675
1676
1677          <tr>
1678
1679
1680            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td>
1681
1682
1683            <td style="width: 196px; vertical-align: top;">(near surface)
1684characteristic temperature</td>
1685
1686
1687            <td style="vertical-align: top;">K</td>
1688
1689
1690            <td style="vertical-align: top;">only horizontal cross section
1691is allowed</td>
1692
1693
1694          </tr>
1695
1696
1697          <tr>
1698
1699
1700            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td>
1701
1702
1703            <td style="width: 196px; vertical-align: top;">u-component of
1704the velocity</td>
1705
1706
1707            <td style="vertical-align: top;">m/s</td>
1708
1709
1710            <td style="vertical-align: top;"></td>
1711
1712
1713          </tr>
1714
1715
1716          <tr>
1717
1718
1719            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td>
1720
1721
1722            <td style="width: 196px; vertical-align: top;">(near surface)
1723friction velocity</td>
1724
1725
1726            <td style="vertical-align: top;">m/s</td>
1727
1728
1729            <td style="vertical-align: top;">only horizontal cross section
1730is allowed</td>
1731
1732
1733          </tr>
1734
1735
1736          <tr>
1737
1738
1739            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td>
1740
1741
1742            <td style="width: 196px; vertical-align: top;">v-component of
1743the velocity</td>
1744
1745
1746            <td style="vertical-align: top;">m/s</td>
1747
1748
1749            <td style="vertical-align: top;"></td>
1750
1751
1752          </tr>
1753
1754
1755          <tr>
1756
1757
1758            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td>
1759
1760
1761            <td style="width: 196px; vertical-align: top;">virtual potential
1762temperature</td>
1763
1764
1765            <td style="vertical-align: top;">K</td>
1766
1767
1768            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
1769
1770
1771          </tr>
1772
1773
1774          <tr>
1775
1776
1777            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td>
1778
1779
1780            <td style="width: 196px; vertical-align: top;">w-component of
1781the velocity</td>
1782
1783
1784            <td style="vertical-align: top;">m/s</td>
1785
1786
1787            <td style="vertical-align: top;"></td>
1788
1789
1790          </tr>
1791
1792
1793          <tr>
1794
1795
1796            <td style="vertical-align: top;"><span style="font-style: italic;">z0*</span></td>
1797
1798
1799            <td style="vertical-align: top;">roughness length</td>
1800
1801
1802            <td style="vertical-align: top;">m</td>
1803
1804
1805            <td></td>
1806
1807
1808          </tr>
1809
1810
1811       
1812       
1813        </tbody>
1814     
1815     
1816      </table>
1817
1818
1819      <br>
1820
1821
1822Multiple
[48]1823quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span>
[108]1824= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br>
1825
1826
1827      <br>
1828
1829
1830By
[5]1831assigning the pure strings from the above table, 3d volume data is
[48]1832output. 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
1833respective quantities. Time averaged&nbsp;output is created by
1834appending the string <span style="font-style: italic;">'_av'
[108]1835      </span>(for
[5]1836cross section data, this string must be appended after the cross
1837section string). Cross section data can also be (additionally) averaged
1838along the direction normal to the respective section (see below).
1839Assignments of quantities can be given in arbitrary
[108]1840order:<br>
1841
1842
1843      <br>
1844
1845
1846Example:<br>
1847
1848
1849      <br>
1850
1851
1852     
1853     
1854      <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>
1855
1856
1857      </div>
1858
1859
1860      <br>
1861
1862
1863This
[5]1864example will create the following output: instantaneous 3d volume data
1865of u-velocity component (by default on file DATA_3D_NETCDF), temporally
1866averaged 3d volume data of u-velocity component (by default on file
1867DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of
1868w-velocity component (by default on file DATA_2D_XY_NETCDF), and
1869temporally averaged vertical cross section data of potential
[108]1870temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br>
1871
1872
1873      <br>
1874
1875
1876The
[48]1877user is allowed to extend the above list of quantities by defining his
[108]1878own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br>
1879
1880
1881      <br>
1882
1883
1884The
[48]1885time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
[5]1886This is valid for all types of output quantities by default. Individual
[48]1887time intervals for instantaneous &nbsp;(!) 3d and section data can
1888be
[108]1889declared 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>
1890
1891
1892      <br>
1893
1894
1895Also,
[48]1896an individual time interval for output of temporally averaged data can
1897be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
1898This applies to both 3d volume and cross section data. The length of
[108]1899the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br>
1900
1901
1902      <br>
1903
1904
1905The
[48]1906parameter <a href="#skip_time_data_output">skip_time_data_output</a>
1907can be used to shift data output activities for a given time interval.
1908Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>,
[108]1909      <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>
1910
1911
1912     
1913     
1914      <p>With
[48]1915the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>&nbsp;
[5]1916the output can be limited in the vertical direction up to a certain
[108]1917grid point.<br>
1918
1919
1920 </p>
1921
1922
1923 Cross sections extend through the
[48]1924total model
1925domain. In the two horizontal directions all grid points with 0
1926&lt;= i
[5]1927&lt;= nx+1 and 0 &lt;= j
[48]1928&lt;= ny+1 are output so that in case of cyclic boundary conditions
1929the
1930complete total domain is represented. The location(s) of the cross
1931sections can be defined with parameters <a href="#section_xy">section_xy</a>,
[108]1932      <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>
[48]1933causes&nbsp;the output data to be averaged along the direction
[108]1934normal to the respective section.<br>
1935
1936
1937      <br>
1938
1939
1940      <br>
1941
1942
1943      <span style="font-weight: bold;">Output of user defined quantities:</span><br>
1944
1945
1946      <br>
1947
1948
1949Beside
[5]1950the standard quantities from the above list, the user can output any
1951other quantities. These have to be defined and calculated within the
[48]1952user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>).
1953They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>
1954for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
[5]1955Output of the user defined quantities (time interval, averaging,
1956selection of cross sections, etc.) is controlled with the parameters
1957listed above and data are written to the same file(s) as the standard
[108]1958quantities.<br>
1959
1960
1961      <br>
1962
1963
1964     
1965     
1966      <p style="font-weight: bold;">Output
1967on parallel machines:</p>
1968
1969
1970     
1971     
1972      <p>
[5]1973By default, with parallel runs, processors output only data
1974of their respective subdomains into seperate local files (file names
1975are
1976constructed by appending the four digit processor ID, e.g.
[48]1977&lt;filename&gt;_0000, &lt;filename&gt;_0001, etc.).
1978After PALM has
[5]1979finished, the contents of these individual
[48]1980files are sampled into one final file<span style="font-weight: bold;"></span>
1981using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
[5]1982(to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
[108]1983configuration file).</p>
1984
1985
1986 
1987     
1988     
1989      <p>Alternatively, PALM is able to
[48]1990collect all grid points of a
1991cross section on PE0 before output is done. In this case only
1992one&nbsp;
[5]1993output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
[48]1994does not have to be called. In case of very large numbers of horizontal
1995gridpoints, sufficient
1996memory is required on PE0.&nbsp; This method can be used by
1997assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
[108]1998= <i>.F.</i>.</p>
1999
2000
2001     
2002     
2003      <p>3d volume data output is
[48]2004always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span>
[108]2005has to be called anyway after PALM has been finished.</p>
2006
2007
2008     
2009     
2010      <p><br>
2011
2012
2013      <span style="font-weight: bold;">Old formats:</span></p>
2014
2015
2016
2017     
2018     
2019      <p>Beside
[48]2020the NetCDF format,&nbsp;2d cross section data and 3d volume data
2021can
[5]2022also be output, for historical reasons, in a different (binary) format
[108]2023using parameter <a href="#data_output_format">data_output_format</a>.</p>
2024
2025
2026     
2027     
2028      <p>By
[48]2029assigning <span style="font-weight: bold;">data_output_format
[108]2030      </span>= <span style="font-style: italic;">'avs'</span>,
[48]2031the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
[5]2032Output is in FORTRAN binary format&nbsp;readable by
2033the plot software <span style="font-weight: bold;">AVS</span>.&nbsp;
2034The order of data on the file follows the order used in the assignment
[48]2035for <b>data_output</b> (e.g. <b>data_output</b>
2036= <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,...&nbsp;
[5]2037means that the file starts with the pressure data, followed by the
2038v-component of the velocity, etc.). Both instantaneous and time
2039averaged data are written on this file! Additional to this file, PALM
2040creates
2041a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>)
2042with coordinate information needed by <span style="font-weight: bold;">AVS</span>.
2043As third and
2044fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
2045and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>),
2046which describe the contents of the data file and/or coordinate file
2047and are used by AVS. However, AVS expects the content description in
2048one file. This needs the local file PLOT3D_FLD_COOR to be appended to
2049the file
2050PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
2051configuration file: &ldquo;<span style="font-family: monospace;">cat
[48]2052PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>&rdquo;)
2053after PALM has
2054finished.&nbsp;To reduce the amount of data, output to this file
2055can be done
[5]2056in
[48]2057compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>).
2058Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in
[108]2059      <a href="chapter_4.5.5.html">chapter
20604.5.5</a>.</p>
2061
2062
2063By assigning <span style="font-weight: bold;">data_output_format </span>=
2064      <span style="font-style: italic;">'iso2d'</span>,
[48]2065the 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>.
[5]2066Output is in FORTRAN binary format&nbsp;readable by
2067the plot software&nbsp;<span style="font-weight: bold;">iso2d</span>.&nbsp;
2068The order of data on the files follows the order used in the assignment
[48]2069for <b>data_output</b> (e.g. <b>data_output</b>
2070= <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,...&nbsp;
[5]2071means that the file containing the horizontal cross section data starts
2072with the instantaneous pressure data, followed by the
2073temporally averaged v-component of the velocity, etc.). Both
2074instantaneous and time averaged data are written on this
2075file!Additional to these binary files, PALM
2076creates NAMELIST parameter files
2077(local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>,
[108]2078      <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
2079      <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
2080      <a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
2081      <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
2082      <a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
[5]2083which 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>.
2084That needs local files with suffix _LOCAL to be appended to the
2085respective files with suffix _GLOBAL (by
2086suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span>
2087configuration file, e.g.: &ldquo;<span style="font-family: monospace;">cat
[48]2088PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</span>&rdquo;)
2089after PALM has
2090finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the
2091respective data and
[5]2092parameter file. The plot layout is steered via the parameter input
2093file.
2094The values of these <span style="font-weight: bold;">iso2d</span>
2095parameters are determined by a set of mostly internal PALM parameters
2096(exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>).
2097All parameter values can be changed by editing the parameter input
[48]2098file.&nbsp;Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found
2099in <a href="chapter_4.5.4.html">chapter
[108]21004.5.4</a>.<br>
2101
2102
2103      <br>
2104
2105
2106      <span style="font-weight: bold;">Important:</span><br>
2107
2108
2109There
[48]2110is no guarantee that iso2d- and avs-output will be available in future
[108]2111PALM versions (later than 3.0). </td>
2112
2113
2114 </tr>
2115
2116
2117 <tr>
2118
2119
2120 <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
2121
2122
2123
2124      </td>
2125
2126
2127 <td style="vertical-align: top;">C * 10 (10) </td>
2128
2129
2130
2131      <td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
2132
2133
2134
2135      <td style="vertical-align: top;">Format of output data.<br>
2136
2137
2138      <br>
2139
2140
2141By
[48]2142default, all data (profiles, time
[5]2143series, spectra, particle data, cross sections, volume data) are output
[48]2144in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).
2145Exception: 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>,
[108]2146      <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
2147are always output in FORTRAN binary format.<br>
2148
2149
2150      <br>
2151
2152
2153The
2154numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br>
2155
2156
2157      <br>
2158
2159
2160The
[48]2161maximum file size for NetCDF files is 2 GByte by default. Use the
2162parameter <a href="#netcdf_64bit">netcdf_64bit</a>
[108]2163if larger files have to be created.<br>
2164
2165
2166      <br>
2167
2168
2169For historical
[48]2170reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span>
[108]2171may be assigned the following values:<br>
2172
2173
2174      <br>
2175
2176
2177     
2178     
2179      <table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2">
2180
2181
2182        <tbody>
2183
2184
2185          <tr>
2186
2187
2188            <td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td>
2189
2190
2191            <td>output
[48]2192of profiles,&nbsp;time series and spectra in ASCII format to be
2193read by the graphic software <span style="font-weight: bold;">profil
[108]2194            </span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
2195            <a href="#chapter_4.5.3.html">4.5.3</a>)</td>
2196
2197
2198          </tr>
2199
2200
2201          <tr>
2202
2203
2204            <td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td>
2205
2206
2207            <td>output
[48]2208of 2d cross-sections in FORTRAN binary format to be read by the graphic
2209software <span style="font-weight: bold;">iso2d</span>
[108]2210(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td>
2211
2212
2213          </tr>
2214
2215
2216          <tr>
2217
2218
2219            <td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td>
2220
2221
2222            <td>output
[48]2223of 3d volume data in FORTRAN binary format to be read by the graphic
2224software <span style="font-weight: bold;">AVS</span>
[108]2225(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td>
2226
2227
2228          </tr>
2229
2230
2231       
2232       
2233        </tbody>
2234     
2235     
2236      </table>
2237
2238
2239      <br>
2240
2241
2242Multiple
[48]2243values can be assigned to <span style="font-weight: bold;">data_output_format</span>,
2244i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as
2245cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> =
[108]2246      <span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
2247assigned.<br>
2248
2249
2250      <br>
2251
2252
2253      <span style="font-weight: bold;">Warning:</span>
[48]2254There is no guarantee that the "old" formats will be available in
[108]2255future PALM versions (beyond 3.0)!<br>
2256
2257
2258 </td>
2259
2260
2261 </tr>
2262
2263
2264 <tr>
2265
2266
2267
2268      <td style="vertical-align: top;"> 
2269     
2270     
2271      <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
2272
2273
2274
2275      </td>
2276
2277
2278 <td style="vertical-align: top;">C *
[48]227910&nbsp; <br>
[108]2280
2281
2282
2283(100)</td>
2284
2285
2286 <td style="vertical-align: top;"><i>100
2287* ' '</i></td>
2288
2289
2290 <td style="vertical-align: top;">
2291     
2292     
2293      <p>Quantities for which vertical profiles (horizontally averaged)
2294are to be output.&nbsp; </p>
2295
2296
2297 
2298     
2299     
2300      <p>By default vertical
[48]2301profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>.
2302The file's format is NetCDF.&nbsp; Further details about processing
[108]2303NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
2304
2305
2306     
2307     
2308      <p>For
[48]2309historical reasons, data can also be output in ASCII-format on local
2310file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
2311which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See
2312parameter <a href="#data_output_format">data_output_format</a>
[108]2313for defining the format in which data shall be output.<br>
2314
2315
2316 </p>
2317
2318
2319
2320     
2321     
2322      <p>For horizontally averaged vertical
[48]2323profiles always <span style="font-weight: bold;">all</span>
2324vertical
[5]2325grid points (0 &lt;= k &lt;= nz+1) are output to file. Vertical
2326profile data refers to the total domain but profiles for subdomains can
2327also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).&nbsp;
[108]2328      </p>
2329
2330
2331 
2332     
2333     
2334      <p>The temporal interval of the output times of
[48]2335profiles is
[5]2336assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>.
[48]2337Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
2338the profiles are ordered with respect to their
[108]2339output times.</p>
2340
2341
2342     
2343     
2344      <p>Profiles can also be temporally
[127]2345averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>).<br>
[108]2346
2347
2348
2349      </p>
2350
2351
2352 
2353     
2354     
2355      <p>The following list shows the values which can be
[48]2356assigned to <span style="font-weight: bold;">data_output_pr</span>.
[5]2357The profile data is either defined on
[48]2358u-v-levels (variables marked in <font color="#ff6600">red</font>)
2359or
2360on w-levels (<font color="#33ff33">green</font>).
2361According to this,
[5]2362the
2363z-coordinates of the individual profiles vary. Beyond that, with a
2364Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>)
2365the lowest output
[48]2366level is z = zu(1) instead of z = zw(0) for profiles <i>w''
2367u'',w''v"</i>, <i>wu</i> and <i>wv</i>
[127]2368. Turbulence quantities such as&nbsp;<span style="font-style: italic;">w*u* &nbsp;</span>or <span style="font-style: italic;">u*2</span> are calculated from turbulent fluctuations that are defined as deviations from the instantaneous horizontal average.
[108]2369
2370
2371 </p>
2372
2373
2374 
2375     
2376     
2377      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
2378
2379
2380 <tbody>
2381
2382
2383 <tr>
2384
2385
2386 <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
2387
2388
2389
2390            <td style="vertical-align: top;">u-component of the
2391velocity (in m/s).</td>
2392
2393
2394 </tr>
2395
2396
2397 <tr>
2398
2399
2400 <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
2401
2402
2403
2404            <td style="vertical-align: top;">v-component of the
2405velocity (in m/s).</td>
2406
2407
2408 </tr>
2409
2410
2411 <tr>
2412
2413
2414 <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
2415
2416
2417
2418            <td style="vertical-align: top;">w-component of the
2419velocity (in m/s).</td>
2420
2421
2422 </tr>
2423
2424
2425 <tr>
2426
2427
2428 <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
2429
2430
2431
2432            <td style="vertical-align: top;">Potential temperature (in
2433K).</td>
2434
2435
2436 </tr>
2437
2438
2439 <tr>
2440
2441
2442 <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
2443
2444
2445
2446            <td style="vertical-align: top;">Virtual potential
2447temperature (in K).</td>
2448
2449
2450 </tr>
2451
2452
2453 <tr>
2454
2455
2456 <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
2457
2458
2459
2460            <td style="vertical-align: top;">Potential liquid water
2461temperature (in K).</td>
2462
2463
2464 </tr>
2465
2466
2467 <tr>
2468
2469
2470 <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
2471
2472
2473
2474            <td style="vertical-align: top;">Total water content
2475(in kg/kg).</td>
2476
2477
2478 </tr>
2479
2480
2481 <tr>
2482
2483
2484 <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
2485
2486
2487
2488            <td style="vertical-align: top;">Specific humidity (in
2489kg/kg).</td>
2490
2491
2492 </tr>
2493
2494
2495 <tr>
2496
2497
2498 <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
2499
2500
2501
2502            <td style="vertical-align: top;">Liquid water content
2503(in kg/kg).</td>
2504
2505
2506 </tr>
2507
2508
2509 <tr>
2510
2511
2512            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 102, 0);">rho</span></td>
2513
2514
2515            <td align="undefined" valign="undefined">Potential density (in kg/m<sup>3</sup>).</td>
2516
2517
2518          </tr>
2519
2520
2521          <tr>
2522
2523
2524 <td style="vertical-align: middle; font-style: italic;"><font color="#ff6600">s</font></td>
2525
2526
2527
2528            <td style="vertical-align: top;">Scalar concentration (in
2529kg/m<sup>3</sup>).</td>
2530
2531
2532 </tr>
2533
2534
2535 <tr>
2536
2537
2538            <td align="undefined" valign="undefined"><span style="font-style: italic; background-color: rgb(255, 255, 255); color: rgb(255, 102, 0);">sa</span></td>
2539
2540
2541            <td align="undefined" valign="undefined">Salinity (in psu).</td>
2542
2543
2544          </tr>
2545
2546
2547          <tr>
2548
2549
2550 <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
2551
2552
2553
2554            <td style="vertical-align: top;">Turbulent kinetic energy
[5]2555(TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td>
[108]2556
2557
2558
2559          </tr>
2560
2561
2562 <tr>
2563
2564
2565 <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
2566
2567
2568
2569            <td style="vertical-align: top;">Perturbation energy
[5]2570(resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td>
[108]2571
2572
2573
2574          </tr>
2575
2576
[197]2577 <tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 0, 0);">p</span></td><td align="undefined" valign="undefined">Perturbation pressure (in Pa)</td></tr><tr>
[108]2578
2579
2580 <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
2581
2582
2583
2584            <td style="vertical-align: top;">Eddy diffusivity for
2585momentum (in m<sup>2</sup>/s).</td>
2586
2587
2588 </tr>
2589
2590
2591 <tr>
2592
2593
2594
2595            <td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
2596
2597
2598
2599            <td style="vertical-align: top;">Eddy diffusivity for heat
2600(in m<sup>2</sup>/s).</td>
2601
2602
2603 </tr>
2604
2605
2606 <tr>
2607
2608
2609 <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
2610
2611
2612
2613            <td style="vertical-align: top;">Mixing length (in m).</td>
2614
2615
2616
2617          </tr>
2618
2619
2620 <tr>
2621
2622
2623 <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
2624
2625
2626
2627            <td style="vertical-align: top;">u-component of the
[5]2628subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[108]2629
2630
2631
2632          </tr>
2633
2634
2635 <tr>
2636
2637
2638 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td>
2639
2640
2641
2642            <td style="vertical-align: top;">u-component of the
[5]2643resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[108]2644
2645
2646
2647          </tr>
2648
2649
2650 <tr>
2651
2652
2653 <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
2654
2655
2656
2657            <td style="vertical-align: top;">u-component of the total
[48]2658vertical momentum flux (<i>w"u"</i> + <i>w*u*</i>)
[108]2659(in m<sup>2</sup>/s<sup>2</sup>).</td>
2660
2661
2662 </tr>
2663
2664
2665
2666          <tr>
2667
2668
2669 <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
2670
2671
2672
2673            <td style="vertical-align: top;">v-component of the
[5]2674subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[108]2675
2676
2677
2678          </tr>
2679
2680
2681 <tr>
2682
2683
2684 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td>
2685
2686
2687
2688            <td style="vertical-align: top;">v-component of the
[5]2689resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[108]2690
2691
2692
2693          </tr>
2694
2695
2696 <tr>
2697
2698
2699 <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
2700
2701
2702
2703            <td style="vertical-align: top;">v-component of the total
[48]2704vertical momentum flux (<i>w"v"</i> + <i>w*v*</i>)
[108]2705(in m<sup>2</sup>/s<sup>2</sup>).</td>
2706
2707
2708 </tr>
2709
2710
2711
2712          <tr>
2713
2714
2715 <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
2716
2717
2718
2719            <td style="vertical-align: top;">Subgrid-scale vertical
2720sensible heat flux (in K m/s).</td>
2721
2722
2723 </tr>
2724
2725
2726 <tr>
2727
2728
2729 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
2730
2731
2732
2733            <td style="vertical-align: top;">Resolved vertical
[48]2734sensible
[108]2735heat flux (in K m/s).</td>
2736
2737
2738 </tr>
2739
2740
2741 <tr>
2742
2743
2744 <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
2745
2746
2747
2748            <td style="vertical-align: top;">Total vertical sensible
[5]2749heat flux (<i>w"pt"</i> + <i>w*pt*</i>)
2750(in K
[108]2751m/s).</td>
2752
2753
2754 </tr>
2755
2756
2757 <tr>
2758
2759
2760 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td>
2761
2762
2763
2764            <td style="vertical-align: top;">Subgrid-scale vertical
[5]2765sensible heat flux using the
[108]2766Bott-Chlond scheme (in K m/s).</td>
2767
2768
2769 </tr>
2770
2771
2772 <tr>
2773
2774
2775 <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
2776
2777
2778
2779            <td style="vertical-align: top;">Total vertical sensible
[5]2780heat flux using the Bott-Chlond scheme
2781(<i>w"pt"</i>
[108]2782+ <i>w*pt*BC</i>) (in K m/s).</td>
2783
2784
2785 </tr>
2786
2787
2788 <tr>
2789
2790
2791
2792            <td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
2793
2794
2795
2796            <td style="vertical-align: top;">Subgrid-scale vertical
2797buoyancy flux (in K m/s).</td>
2798
2799
2800 </tr>
2801
2802
2803 <tr>
2804
2805
[127]2806 <td style="vertical-align: top;"><font color="#33ff33"><i>w*vpt*</i></font></td>
[108]2807
2808
2809
2810            <td style="vertical-align: top;">Resolved vertical
[48]2811buoyancy
[108]2812flux (in K m/s).</td>
2813
2814
2815 </tr>
2816
2817
2818 <tr>
2819
2820
2821 <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
2822
2823
2824
2825            <td style="vertical-align: top;">Total vertical buoyancy
2826flux (w"vpt" + w*vpt*) (in K m/s).</td>
2827
2828
2829 </tr>
2830
2831
2832 <tr>
2833
2834
2835 <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
2836
2837
2838
2839            <td style="vertical-align: top;">Subgrid-scale vertical
2840water flux (in kg/kg m/s).</td>
2841
2842
2843 </tr>
2844
2845
2846 <tr>
2847
2848
2849 <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td>
2850
2851
2852
2853            <td style="vertical-align: top;">Resolved vertical water
2854flux (in kg/kg m/s).</td>
2855
2856
2857 </tr>
2858
2859
2860 <tr>
2861
2862
2863 <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
2864
2865
2866
2867            <td style="vertical-align: top;">Total vertical water flux
2868(w"q" + w*q*) (in kg/kg m/s).</td>
2869
2870
2871 </tr>
2872
2873
2874 <tr>
2875
2876
2877 <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
2878
2879
2880
2881            <td style="vertical-align: top;">Subgrid-scale vertical
2882latent heat flux (in kg/kg m/s).</td>
2883
2884
2885 </tr>
2886
2887
2888 <tr>
2889
2890
2891 <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td>
2892
2893
2894
2895            <td style="vertical-align: top;">Resolved vertical latent
2896heat flux (in kg/kg m/s).</td>
2897
2898
2899 </tr>
2900
2901
2902 <tr>
2903
2904
2905 <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
2906
2907
2908
2909            <td style="vertical-align: top;">Total vertical latent
[48]2910heat
[108]2911flux (w"qv" + w*qv*) (in kg/kg m/s).</td>
2912
2913
2914 </tr>
2915
2916
2917 <tr>
2918
2919
2920
2921            <td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
2922
2923
2924
2925            <td style="vertical-align: top;">Subgrid-scale vertical
[5]2926scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td>
[108]2927
2928
2929
2930          </tr>
2931
2932
2933 <tr>
2934
2935
2936 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td>
2937
2938
2939
2940            <td style="vertical-align: top;">Resolved vertical scalar
2941concentration flux (in kg/m<sup>3</sup> m/s).</td>
2942
2943
2944 </tr>
2945
2946
2947
2948          <tr>
2949
2950
2951 <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
2952
2953
2954
2955            <td style="vertical-align: top;">Total vertical scalar
[5]2956concentration flux (w"s" + w*s*) (in kg/m<sup>3 </sup>m/s).</td>
[108]2957
2958
2959
2960          </tr>
2961
2962
2963 <tr>
2964
2965
2966            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w"sa"</span></td>
2967
2968
2969            <td align="undefined" valign="undefined">Subgrid-scale vertical
2970salinity flux (in psu<sup> </sup>m/s).</td>
2971
2972
2973          </tr>
2974
2975
2976          <tr>
2977
2978
2979            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w*sa*</span></td>
2980
2981
2982            <td align="undefined" valign="undefined">Resolved vertical salinity flux (in psu m/s).</td>
2983
2984
2985          </tr>
2986
2987
2988          <tr>
2989
2990
2991            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td>
2992
2993
2994            <td align="undefined" valign="undefined">Total vertical salinity flux (w"sa" + w*sa*) (in psu<sup> </sup>m/s).</td>
2995
2996
2997          </tr>
2998
2999
3000          <tr>
3001
3002
3003 <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td>
3004
3005
3006
3007            <td style="vertical-align: top;">Vertical flux of
3008perturbation energy (resolved)</td>
3009
3010
3011 </tr>
3012
3013
3014 <tr>
3015
3016
3017 <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
3018
3019
3020
3021            <td style="vertical-align: top;">Variance of the
[48]3022u-velocity
[108]3023component (resolved)</td>
3024
3025
3026 </tr>
3027
3028
3029 <tr>
3030
3031
3032 <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
3033
3034
3035
3036            <td style="vertical-align: top;">Variance of the
[48]3037v-velocity
[108]3038component (resolved)</td>
3039
3040
3041 </tr>
3042
3043
3044 <tr>
3045
3046
3047 <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
3048
3049
3050
[127]3051            <td style="vertical-align: top;">Variance of the w-velocity
3052component (resolved)</td>
[108]3053
3054
3055 </tr>
3056
3057
3058 <tr>
3059
3060
3061 <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
3062
3063
3064
3065            <td style="vertical-align: top;">Variance of the potential
3066temperature (resolved)</td>
3067
3068
3069 </tr>
3070
3071
3072 <tr>
3073
3074
3075 <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
3076
3077
3078
3079            <td style="vertical-align: top;">Third moment of the
3080w-velocity component (resolved)</td>
3081
3082
3083 </tr>
3084
3085
3086 <tr>
3087
3088
3089 <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
3090
3091
3092
3093            <td style="vertical-align: top;">Skewness of the
[48]3094w-velocity
[5]3095component (resolved, S<sub>w</sub>
3096= W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td>
[108]3097
3098
3099
3100          </tr>
3101
3102
3103 <tr>
3104
3105
3106 <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td>
3107
3108
3109
3110            <td style="vertical-align: top;">Third moment (resolved)</td>
3111
3112
3113
3114          </tr>
3115
3116
3117 <tr>
3118
3119
3120 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td>
3121
3122
3123
3124            <td style="vertical-align: top;">Third moment (resolved)</td>
3125
3126
3127
3128          </tr>
3129
3130
3131 <tr>
3132
3133
3134 <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*/dz</i></font></td>
3135
3136
3137
3138            <td style="vertical-align: top;">Energy production by
[48]3139shear
[108]3140(resolved)</td>
3141
3142
3143 </tr>
3144
3145
3146 <tr>
3147
3148
3149 <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*/dz</i></font></td>
3150
3151
3152
3153            <td style="vertical-align: top;">Energy production by
[5]3154turbulent transport of pressure
[108]3155fluctuations (resolved)</td>
3156
3157
3158 </tr>
3159
3160
3161 <tr>
3162
3163
3164 <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
3165
3166
3167
3168            <td style="vertical-align: top;">Energy production by
3169transport of resolved-scale TKE</td>
3170
3171
3172 </tr>
3173
3174
3175 
3176       
3177       
3178        </tbody>
3179     
3180     
3181      </table>
3182
3183
3184 <br>
3185
3186
3187Beyond that, initial profiles (t=0) of some
3188variables can additionally be
[5]3189output (this output is only done once
3190with the first plot output and not repeated with the profile output at
3191later
3192times). The names of these profiles result from the ones specified
[108]3193above leaded by a hash "#".&nbsp; Allowed values are:<br>
3194
3195
3196 
3197     
3198     
3199      <ul>
3200
3201
3202
3203       
3204       
3205        <p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
3206        <i>#km</i>, <i>#kh</i>, <i>#l, #lpt, #q, #qv, #s, #sa, #vpt</i></p>
3207
3208
3209
3210     
3211     
3212      </ul>
3213
3214
3215 
3216     
3217     
3218      <p>Profile names preceded by a hash automatically imply that
3219profiles for these variables are also output at later times. It is not
3220necessary and not allowed to specify the same profile name with and
3221without hash simultaneously(this would lead to an NetCDF error). </p>
3222      <p>These initial profiles have been either set by
[48]3223the user or
[108]3224have been calculated by a 1d-model prerun.</p>
3225
3226
3227The
[89]3228user is allowed to extend the above list of quantities by defining his
[108]3229own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>).<br>
3230
3231
3232      <br>
3233
3234
3235In case
[48]3236of ASCII data output to local file PLOT1D_DATA,
[5]3237PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
3238which 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>.
3239Profiles can be directly plotted with <span style="font-weight: bold;">profil</span>
3240using these two files. The
3241plot layout is
[48]3242steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters
3243are determined by
[5]3244a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>,
[108]3245      <a href="chapter_4.2.html#profile_rows">profile_rows</a>,
3246      <a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
3247      <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
[5]3248etc.) All parameter values can be changed by editing the parameter
3249input
[108]3250file. <br>
3251
3252
3253      <br>
3254
3255
3256Further details about plotting vertical
[48]3257profiles with <span style="font-weight: bold;">profil </span>can
3258be found in <a href="chapter_4.5.2.html">chapter
[108]32594.5.2</a></td>
3260
3261
3262 </tr>
3263
3264
3265 <tr>
3266
3267
3268 <td style="vertical-align: top;"> 
3269     
3270     
3271      <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
3272      <br>
3273
3274
3275 <b>_each_pe</b></p>
3276
3277
3278 </td>
3279
3280
3281 <td style="vertical-align: top;">L<br>
3282
3283
3284 </td>
3285
3286
3287 <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
3288
3289
3290 </td>
3291
3292
3293
3294      <td style="vertical-align: top;">Output 2d cross section
[48]3295data by one or
[108]3296all processors.&nbsp; 
3297     
3298     
3299      <p>In runs with several processors, by
[48]3300default, each processor
3301outputs cross section data of its subdomain&nbsp;into an individual
3302file. After PALM
3303has finished, the contents of these files have to be sampled into one
3304file<span style="font-weight: bold;"></span> using
[5]3305the program <tt>combine_plot_fields.x</tt>.&nbsp; </p>
[108]3306
3307
3308
3309     
3310     
3311      <p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
[48]3312= <i>.F.,</i>
[5]3313the respective data is gathered on PE0 and output is done directly
[48]3314into one file, so <tt>combine_plot_fields.x</tt> does not
3315have to be
3316called. However, in case of very large numbers of horizontal
3317gridpoints, sufficient
[108]3318memory is required on PE0. </p>
3319
3320
3321 </td>
3322
3323
3324 </tr>
3325
3326
3327
3328    <tr>
3329
3330
3331 <td style="vertical-align: top;"> 
3332     
3333     
3334      <p><a name="disturbance_amplitude"></a><b>disturbance<br>
3335
3336
3337
3338_amplitude</b></p>
3339
3340
3341 </td>
3342
3343
3344 <td style="vertical-align: top;">R</td>
3345
3346
3347 <td style="vertical-align: top;"><i>0.25</i></td>
3348
3349
3350
3351      <td style="vertical-align: top;"> 
3352     
3353     
3354      <p>Maximum
[48]3355perturbation amplitude of the random perturbations
[5]3356imposed to the horizontal velocity field (in m/s).&nbsp; </p>
[108]3357
3358
3359
3360     
3361     
3362      <p>The parameter <a href="#create_disturbances">create_disturbances</a>
[5]3363describes how to impose random perturbations to the horizontal velocity
3364field. Since the perturbation procedure includes two filter operations,
[48]3365the amplitude assigned by <b>disturbance_amplitude</b> is
3366only an
[108]3367approximate value of the real magnitude of the perturbation.</p>
3368
3369
3370 </td>
3371
3372
3373
3374    </tr>
3375
3376
3377 <tr>
3378
3379
3380 <td style="vertical-align: top;">
3381     
3382     
3383      <p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
3384      <br>
3385
3386
3387 <b>_limit</b></p>
3388
3389
3390 </td>
3391
3392
3393 <td style="vertical-align: top;">R</td>
3394
3395
3396 <td style="vertical-align: top;"><i>0.01</i></td>
3397
3398
3399
[240]3400      <td style="vertical-align: top; font-family: Helvetica,Arial,sans-serif;"> 
[108]3401     
3402     
3403      <p lang="en-GB">Upper
[48]3404limit value of the perturbation energy of
[5]3405the velocity field used as a criterion for imposing random
[48]3406perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
[108]3407      </p>
3408
3409
3410 
3411     
3412     
[240]3413      <p><span lang="en-GB">The parameter </span><a href="#create_disturbances"><span lang="en-GB">create_disturbances</span></a><span lang="en-GB">
[48]3414describes how to impose
[5]3415random perturbations to the horizontal velocity field. The perturbation
3416energy is defined as the volume average (over the total model domain)
3417of the squares of the deviations of the velocity components from the
3418mean flow (horizontal average). If the perturbation energy exceeds the
3419assigned value, random perturbations to the fields of horizontal
3420velocities are imposed no more. The value of this parameter usually
3421must be determined by trial and error (it depends e.g. on the total
[240]3422number of grid points).</span>  </p>
[108]3423
3424
3425 </td>
3426
3427
3428
3429    </tr>
3430
3431
3432 <tr>
3433
3434
3435 <td style="vertical-align: top;">
3436     
3437     
3438      <p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
3439
3440
3441
3442      </td>
3443
3444
3445 <td style="vertical-align: top;">R</td>
3446
3447
3448
3449      <td style="vertical-align: top;"><i>zu(3) or<br>
3450
3451
3452zu(nz*2/3)<br>
3453
3454
3455see right</i></td>
3456
3457
3458
[240]3459      <td style="vertical-align: top; font-family: Helvetica,Arial,sans-serif;"> 
[108]3460     
3461     
[240]3462      <p lang="en-GB"><font size="3">Lower
[5]3463limit of the vertical range for which random perturbations are to be
[240]3464imposed on the horizontal wind field (</font>in <font size="3">m).&nbsp;
3465      </font> </p>
[108]3466
3467
3468 
3469     
3470     
[240]3471      <p><span lang="en-GB">This
[97]3472parameter must hold the condition zu(3) &lt;= <b>disturbance_level_b</b>
[240]3473&lt;= zu(</span><a href="chapter_4.1.html#nz"><span lang="en-GB">nz-2</span></a><span lang="en-GB">)</span><span lang="en-GB">. Additionally, <b>disturbance_level_b</b>
3474&lt;= </span><a href="#disturbance_level_t"><span lang="en-GB">disturbance_level_t</span></a>
3475      <span lang="en-GB">must
3476also hold.</span></p>
[108]3477
3478
3479     
3480     
[240]3481      <p><span lang="en-GB">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </span><span lang="en-GB">the default value is <span style="font-weight: bold;">disturbance_level_b</span> = <span style="font-style: italic;">zu(nz * 2 / 3) </span>(negative).</span><a href="chapter_4.1.html#nz"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"></span></p>
[108]3482
3483
3484 
3485     
3486     
[240]3487      <p><span lang="en-GB">The
3488parameter </span><a href="#create_disturbances"><span lang="en-GB">create_disturbances</span></a><span lang="en-GB">
[48]3489describes how to impose
[240]3490random perturbations to the horizontal velocity field</span><span lang="en-GB">.</span>
3491       </p>
[108]3492
3493
3494 </td>
3495
3496
3497 </tr>
3498
3499
3500 <tr>
3501
3502
3503 <td style="vertical-align: top;"> 
3504     
3505     
3506      <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
3507
3508
3509
3510      </td>
3511
3512
3513 <td style="vertical-align: top;">R</td>
3514
3515
3516
3517      <td style="vertical-align: top;"><i>zu(nz/3) or<br>
3518
3519
3520zu(nzt-3)<br>
3521
3522
3523see right</i></td>
3524
3525
3526
[240]3527      <td style="vertical-align: top; font-family: Helvetica,Arial,sans-serif;"> 
[108]3528     
3529     
[240]3530      <p lang="en-GB"><font size="3">Upper
[5]3531limit of the vertical range for which random perturbations are to be
[240]3532imposed on the horizontal wind field (</font>in <font size="3">m).&nbsp;
3533      </font> </p>
[108]3534
3535
3536 
3537     
3538     
[240]3539      <p><span lang="en-GB">This
[48]3540parameter must hold the condition <b>disturbance_level_t</b>
[240]3541&lt;= zu<i>(</i></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB">nz-2</span></a><span lang="en-GB">)</span></i><span lang="en-GB">.
3542Additionally, </span><a href="#disturbance_level_b"><span lang="en-GB">disturbance_level_b</span></a>
3543      <span lang="en-GB">&lt;=
[108]3544      <b>disturbance_level_t</b>
[240]3545must also hold.</span></p>
[108]3546
3547
[240]3548      <span lang="en-GB">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </span><span lang="en-GB">the default value is <span style="font-weight: bold;">disturbance_level_t</span> = <span style="font-style: italic;">zu(nzt - 3</span>)</span><span lang="en-GB"><span style="font-style: italic;"> </span>(negative)</span><span lang="en-GB">.</span>
[108]3549     
3550     
[240]3551      <p><span lang="en-GB">The
3552parameter </span><a href="#create_disturbances"><span lang="en-GB">create_disturbances</span></a><span lang="en-GB">
[48]3553describes how to impose
[240]3554random perturbations to the horizontal velocity field</span><span lang="en-GB">.</span>
3555       </p>
[108]3556
3557
3558 </td>
3559
3560
3561 </tr>
3562
3563
3564 <tr>
3565
3566
3567 <td style="vertical-align: top;"> 
3568     
3569     
3570      <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
3571
3572
3573
3574      </td>
3575
3576
3577 <td style="vertical-align: top;">L<br>
3578
3579
3580 </td>
3581
3582
3583
[240]3584      <td style="vertical-align: top; font-style: italic;">.F.<br>
[108]3585
3586
3587 </td>
3588
3589
3590
3591      <td style="vertical-align: top;"> 
3592     
3593     
3594      <p>Output of 2d
3595cross section data at the beginning of a run.&nbsp; </p>
3596
3597
3598 
3599     
3600     
3601      <p>The
[48]3602temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>)
3603are 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>
[5]3604and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>.
[48]3605By assigning <b>do2d_at_begin</b> = <i>.T.</i>
3606an additional output
[5]3607will be made at the
3608beginning of a run (thus at the time t = 0 or at the respective
[108]3609starting times of restart runs).</p>
3610
3611
3612 </td>
3613
3614
3615 </tr>
3616
3617
3618 <tr>
3619
3620
3621
3622      <td style="vertical-align: top;"> 
3623     
3624     
3625      <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
3626
3627
3628
3629      </td>
3630
3631
3632 <td style="vertical-align: top;">L<br>
3633
3634
3635 </td>
3636
3637
3638
[240]3639      <td style="vertical-align: top; font-style: italic;">.F.<br>
[108]3640
3641
3642 </td>
3643
3644
3645
3646      <td style="vertical-align: top;">Output of 3d volume data
[48]3647at the beginning
[108]3648of a run.<br>
3649
3650
3651      <br>
3652
3653
3654The temporal intervals of output times of
[48]36553d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
[5]3656is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>.
[48]3657By assigning <b>do3d_at_begin</b> = <i>.T.</i>
3658an additional output
[5]3659will be made at the
3660beginning of a run (thus at the time t = 0 or at the respective
[108]3661starting times of restart runs).</td>
3662
3663
3664 </tr>
3665
3666
3667 <tr>
3668
3669
3670 <td style="vertical-align: top;"> 
3671     
3672     
3673      <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
3674
3675
3676
3677      </td>
3678
3679
3680 <td style="vertical-align: top;">L<br>
3681
3682
3683 </td>
3684
3685
3686
[240]3687      <td style="vertical-align: top; font-style: italic;">.F.<br>
[108]3688
3689
3690 </td>
3691
3692
3693
3694      <td style="vertical-align: top;"> 
3695     
3696     
3697      <p>Output of data
3698for 3d plots in compressed form.&nbsp; </p>
3699
3700
3701 
3702     
3703     
3704      <p>This
[48]3705parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
[108]3706= <span style="font-style: italic;">'avs'</span>.</p>
3707
3708
3709     
3710     
3711      <p>Output
[48]3712of 3d volume data may need huge amounts of disc storage
[5]3713(up to several Terabytes ore more). Data compression can serve to
3714reduce this requirement. PALM is able to output 3d data in compressed
3715form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span>
[48]3716= <span style="font-style: italic;">.T.</span> is
3717assigned. This
[5]3718yields a loss of accuracy, but the file size is clearly reduced. The
[197]3719parameter <a href="chapter_4.2.html#do3d_comp_prec">do3d_comp_prec</a>
[5]3720can be used to separately define the number of significant digits for
[108]3721each quantity.<br>
3722
3723
3724 </p>
3725
3726
3727 
3728     
3729     
3730      <p>So far compressed data
[48]3731output is only possible for Cray-T3E
[5]3732machines. Additional information for
3733handling compressed data is given in <a href="chapter_4.5.6.html">chapter
[108]37344.5.6</a>.</p>
3735
3736
3737 </td>
3738
3739
3740 </tr>
3741
3742
3743 <tr>
3744
3745
3746 <td style="vertical-align: top;"> 
3747     
3748     
[197]3749      <p><a name="do3d_comp_prec"></a><b>do3d_comp_prec</b></p>
[108]3750
3751
3752
3753      </td>
3754
3755
3756 <td style="vertical-align: top;">C *
[48]37577&nbsp; <br>
[108]3758
3759
3760
3761&nbsp; (100)</td>
3762
3763
[240]3764 <td style="vertical-align: top; font-style: italic;">see
[108]3765right<br>
3766
3767
3768 </td>
3769
3770
3771 <td style="vertical-align: top;">
3772     
3773     
3774      <p>Significant digits in case of compressed data
3775output.&nbsp; </p>
3776
3777
3778 
3779     
3780     
3781      <p>This parameter only applies for
[48]3782&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
[108]3783= <span style="font-style: italic;">'avs'</span>.</p>
3784
3785
3786     
3787     
3788      <p>In
[48]3789case that data compression is used for output of 3d data
[5]3790(see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>),
3791this parameter determines the number of significant digits
[108]3792which are to be output.<br>
3793
3794
3795 </p>
3796
3797
3798 
3799     
3800     
3801      <p>Fewer digits
[48]3802clearly reduce the amount
[5]3803of data. Assignments have to be given separately for each individual
[48]3804quantity via a character string of the form <span style="font-style: italic;">'&lt;quantity
3805name&gt;&lt;number of
[5]3806significant digits&gt;'</span>, e.g. <span style="font-style: italic;">'pt2'</span>.
3807Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a>
3808are admitted. Up to 9 significant digits are allowed (but large values
3809are not very reasonable
[108]3810because they do not effect a significant compression).<br>
3811
3812
3813 </p>
3814
3815
3816
3817     
3818     
[197]3819      <p>The default assignment is <span style="font-weight: bold;">do3d_comp_prec</span>
[108]3820= <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>
3821
3822
3823 </td>
3824
3825
3826
3827    </tr>
3828
3829
[240]3830 <tr>
[108]3831
3832
3833 <td style="vertical-align: top;"> 
3834     
3835     
3836      <p><a name="dt_laufparameter"></a><b>dt</b></p>
3837
3838
3839
3840      </td>
3841
3842
3843 <td style="vertical-align: top;">R</td>
3844
3845
3846
3847      <td style="vertical-align: top;"><i>variable</i></td>
3848
3849
3850
3851      <td style="vertical-align: top;"> 
3852     
3853     
[240]3854      <font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><font size="3">Time
3855step to be used by the 3d-model (</font></font><span style="font-family: Helvetica,Arial,sans-serif;">in </span><font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><font size="3">s).&nbsp;
3856      </font></font> 
[108]3857
3858
3859 
3860     
3861     
[240]3862      <p style="font-family: Helvetica,Arial,sans-serif;"><span lang="en-GB">This parameter</span>
3863      <span lang="en-GB">is
[48]3864described in
[240]3865detail with the initialization parameters (see</span><span lang="en-GB"> </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a><span lang="en-GB">).
[48]3866Additionally, it may be
[5]3867used as a run parameter and then applies to all restart runs (until it
3868is changed again). A switch from a constant time step to a variable
[240]3869time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span></p><font face="Thorndale, serif">
3870      </font> 
[108]3871
3872
3873 </td>
3874
3875
3876 </tr>
3877
3878
3879 <tr>
3880
3881
3882 <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
3883
3884
3885
3886      </td>
3887
3888
3889 <td style="vertical-align: top;">R<br>
3890
3891
3892 </td>
3893
3894
3895
3896      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
3897
3898
3899 </td>
3900
3901
3902
3903      <td style="vertical-align: top;">Temporal interval
3904of&nbsp;data which are subject to temporal averaging (in s).<br>
3905
3906
3907      <br>
3908
3909
3910By
[48]3911default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>
3912are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span>
3913&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>,
[5]3914the number of time levels entering the average can be minimized. This
3915reduces the CPU-time of a run but may worsen the quality of the
[108]3916average's statistics.<br>
3917
3918
[240]3919      <br style="font-family: Helvetica,Arial,sans-serif;">
[108]3920
3921
[240]3922      <font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><span lang="en-GB">With
[48]3923variable time step (see <span style="font-weight: bold;">dt</span>),
3924the number of time levels entering the average can vary from one
[240]3925averaging interval to the next (for a more detailed explanation see </span></font><font style="font-family: Helvetica,Arial,sans-serif;"><a href="#averaging_interval"><span lang="en-GB">averaging_interval</span></a>)</font><font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><span lang="en-GB">. It
[48]3926is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> /
3927MAX(<span style="font-weight: bold;"> dt_averaging_input</span>,
[108]3928      <span style="font-weight: bold;">dt</span>) (which
[48]3929gives a more or less exact value if a fixed timestep is used and if
[240]3930this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font><span style="font-family: Helvetica,Arial,sans-serif;">&nbsp;
3931      </span><br style="font-family: Helvetica,Arial,sans-serif;">
[108]3932
3933
3934      <br>
3935
3936
3937      <span style="font-weight: bold;">Example:</span><br>
3938
3939
3940With
[48]3941an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> =
[108]3942      <span style="font-style: italic;">10.0</span>,
[5]3943the time levels entering the average have a (minimum) distance of 10.0
3944s (their distance may of course be larger if the current timestep is
3945larger than 10.0 s), so the average is calculated from the data of
[108]3946(maximum) 10 time levels.<br>
3947
3948
3949      <br>
3950
3951
3952      <font face="Thorndale, serif"><span lang="en-GB">It
[48]3953is allowed
3954to change <b>dt_averaging_input</b> during a job chain. If
3955the last averaging
[5]3956interval of the run previous to the change could not be completed (i.e.
3957has to be finished in the current run), the individual profiles and/or
3958spectra entering the averaging are not uniformly distributed over the
[108]3959averaging interval.<br>
3960
3961
3962      <br>
3963
3964
3965      </span></font>Parameter&nbsp;<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>&nbsp;can
[48]3966be used to define&nbsp;a different temporal interval&nbsp;for
[108]3967vertical profile data and spectra.<br>
3968
3969
3970 </td>
3971
3972
3973 </tr>
3974
3975
3976
3977    <tr>
3978
3979
3980 <td style="vertical-align: top;"> 
3981     
3982     
3983      <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
3984
3985
3986
3987      </td>
3988
3989
3990 <td style="vertical-align: top;">R</td>
3991
3992
3993
3994      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>
3995
3996
3997averaging_<br>
3998
3999
4000input</a></span></td>
4001
4002
4003
4004      <td style="vertical-align: top;"> 
4005     
4006     
4007      <p lang="en-GB">Temporal
[48]4008interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
4009profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
[108]4010      </font></font> </p>
4011
4012
4013 
4014     
4015     
4016      <p>By default, data from
[48]4017each 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
4018used for calculating the temporal average.&nbsp;By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span>
4019&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>,
[5]4020the number of time levels entering the average can be minimized. This
4021reduces the CPU-time of a run but may worsen the quality of the
[108]4022average'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>
4023
4024
4025 </p>
4026
4027
4028     
4029     
4030      <p>For
4031more 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>
4032
4033
4034      </td>
4035
4036
4037
4038    </tr>
4039
4040
4041 <tr>
4042
4043
4044      <td style="vertical-align: top;"><a name="dt_coupling"></a><span style="font-weight: bold;">dt_coupling</span></td>
4045
4046
4047      <td style="vertical-align: top;">R</td>
4048
4049
4050      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
4051
4052
4053      <td style="vertical-align: top;">Temporal interval for the data exchange in case of <a href="chapter_3.8.html">runs with coupled models</a> (e.g. atmosphere - ocean) (in s).<br>
4054
4055
4056      <br>
4057
4058
4059This parameter has an effect only in case of a run with coupled models. It is available starting from version 3.3a. <br>
4060
4061
4062      <br>
4063
4064
4065This parameter specifies the temporal interval at which data are
4066exchanged at the interface between coupled models (currently: interface
4067between atmosphere and ocean). If this parameter is not explicitly
4068specified in the parameter files for both coupled models, or if there
4069is an inconsistency between its values for both coupled models,
4070the&nbsp;execution will terminate and an informative error message will
4071be given.&nbsp;In order to ensure synchronous coupling throughout the simulation, <span style="font-weight: bold;">dt_coupling</span> should be chosen larger than
4072      <a href="#dt_max">dt_max</a>.</td>
4073
4074
4075    </tr>
4076
4077
4078    <tr>
4079
4080
4081 <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
4082
4083
4084
4085      </td>
4086
4087
4088 <td style="vertical-align: top;">R<br>
4089
4090
4091 </td>
4092
4093
4094
4095      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
4096
4097
4098
4099      </td>
4100
4101
4102 <td style="vertical-align: top;">
4103     
4104     
4105      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
[48]4106at which&nbsp;data (3d volume data (instantaneous or time
4107averaged),
[5]4108cross sections (instantaneous or time averaged), vertical profiles,
4109spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
[108]4110
4111
4112
4113      <span lang="en-GB"><font face="Thorndale">If
[48]4114data 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
4115parameter can be used to
[5]4116assign the temporal interval at which these data shall be
[48]4117output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
4118simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>,
4119which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
4120time is the beginning of the simulation, i.e. output
4121takes place at times t = <b>skip_time_data_output +
4122dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
4123+ 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
4124+ 3*<b>dt_data_output</b>,
[5]4125etc. Since output is only done at the discrete time levels given by
[48]4126the&nbsp;timestep used, the actual output times can slightly
4127deviate
[108]4128from 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>
4129
4130
4131      <br>
4132
4133
4134Individual temporal
[48]4135intervals for the different output quantities can be assigned using
4136parameters <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>,
4137and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span>
[108]4138      </td>
4139
4140
4141 </tr>
4142
4143
4144 <tr>
4145
4146
4147 <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
4148
4149
4150
4151      </td>
4152
4153
4154 <td style="vertical-align: top;">R<br>
4155
4156
4157 </td>
4158
4159
4160
4161      <td style="vertical-align: top;"><i>value of
4162&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
4163
4164
4165output</a></i>
4166      </td>
4167
4168
4169 <td style="vertical-align: top;">
4170     
4171     
4172      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
[5]4173at which time averaged 3d volume data and/or 2d cross section data
[108]4174shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
4175
4176
4177      <span lang="en-GB"><font face="Thorndale">If data
[48]4178output 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
4179parameter can be used to
[5]4180assign the temporal interval at which they shall be
[48]4181output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
4182simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>,
4183which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
4184time is the beginning of the simulation, i.e. output
4185takes place at times t = <b>skip_time_data_output_av +
4186dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
4187+ 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
4188+ 3*<b>dt_data_output_av</b>,
[5]4189etc. Since output is only done at the discrete time levels given by
[48]4190the&nbsp;timestep used, the actual output times can slightly
4191deviate from
[108]4192these 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>
4193
4194
4195      <br>
4196
4197
4198      </font></span>The
[48]4199length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td>
[108]4200
4201
4202
4203    </tr>
4204
4205
4206    <tr>
4207
4208
4209 <td style="vertical-align: top;"> 
4210     
4211     
4212      <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
4213
4214
4215
4216      </td>
4217
4218
4219 <td style="vertical-align: top;">R</td>
4220
4221
4222
4223      <td style="vertical-align: top;"><i>9999999.9</i></td>
4224
4225
4226
4227      <td style="vertical-align: top;"> 
4228     
4229     
4230      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]4231interval</font> at which random
[5]4232perturbations are to be imposed on the horizontal velocity field
[48]4233(</font>in <font face="Thorndale">s).&nbsp; </font>
[108]4234      </p>
4235
4236
4237 
4238     
4239     
4240      <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">
[48]4241describes how to impose
4242random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
[108]4243      </font> </p>
4244
4245
4246 </td>
4247
4248
4249 </tr>
4250
4251
4252 <tr>
4253
4254
4255 <td style="vertical-align: top;"> 
4256     
4257     
4258      <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
4259
4260
4261
4262      </td>
4263
4264
4265 <td style="vertical-align: top;">R</td>
4266
4267
4268
4269      <td style="vertical-align: top;"><i>value of
4270&nbsp;<a href="#dt_data_output">dt_data_<br>
4271
4272
4273output</a></i></td>
4274
4275
4276
4277      <td style="vertical-align: top;"> 
4278     
4279     
4280      <p><span lang="en-GB"><font face="Thorndale">Temporal
[48]4281interval at
[5]4282which data&nbsp;of vertical profiles shall be output (to local
[48]4283file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
4284or/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
[108]4285      <span lang="en-GB"><font face="Thorndale">s).&nbsp;
4286      </font></span> </p>
4287
4288
4289 
4290     
4291     
4292      <p><span lang="en-GB"><font face="Thorndale">If output of
[48]4293horizontally 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
4294parameter can be used to
4295assign 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
4296be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has
4297zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
4298time is the beginning
[5]4299of the simulation, thus t = 0,&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">i.e. output
[48]4300takes 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>,
[108]4301      <span style="font-weight: bold;">skip_time_dopr</span>
[48]4302+ 3*<b>dt_dopr</b>,
[5]4303etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
4304profiles can not be calculated for times lying within a time step
4305interval, the output times can deviate from these theoretical values.
4306If a time step ranges from t = 1799.8 to t = 1800.2, then in the
4307example above the output would take place at t = 1800.2. In general,
[48]4308the 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
4309model uses a variable time step, these
[5]4310deviations from the theoretical output times will of course be
[108]4311different for each output time.<br>
4312
4313
4314 </font></span></p>
4315
4316
4317
4318     
4319     
4320      <p><span lang="en-GB"><font face="Thorndale">In
[48]4321order to
4322guarantee 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;
[108]4323      <span style="font-weight: bold;">end_time</span>
[5]4324should be equal or a little bit
4325larger than the respective theoretical output time. For example, if <b>dt_dopr</b>
[48]4326= <i>900.0</i><span style="font-style: italic;">
[108]4327      </span>and 3600.0
[5]4328seconds are to be simulated, then <b>end_time</b>
[48]4329&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>
[108]4330      </p>
4331
4332
4333 
4334     
4335     
4336      <p><span lang="en-GB"><font face="Thorndale">A selection of
[48]4337profiles 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>
[108]4338      </p>
4339
4340
4341 </td>
4342
4343
4344 </tr>
4345
4346
4347 <tr>
4348
4349
4350 <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
4351
4352
4353
4354      </td>
4355
4356
4357 <td style="vertical-align: top;">R<br>
4358
4359
4360 </td>
4361
4362
4363
4364      <td style="vertical-align: top;"><i>9999999.9</i></td>
4365
4366
4367
4368      <td style="vertical-align: top;"> 
4369     
4370     
4371      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
[48]4372interval</font> at which data <font face="Thorndale">of
4373vertical
4374profiles 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
[108]4375      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
4376      </p>
4377
4378
4379 
4380     
4381     
4382      <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
[5]4383parameter can be used to
[48]4384assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
4385time is the beginning
4386of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b>
4387= 1800.0,
[5]4388then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since
4389profiles can not be calculated for times lying within a time step
4390interval, the output times can deviate from these theoretical values.
4391If a time step ranges from t = 1799.8 to t = 1800.2, then in the
4392example above the output would take place at t = 1800.2. In general,
[48]4393the 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
4394are related to
[5]4395the
4396example above). If the model uses a variable time step, these
4397deviations from the theoretical output times will of course be
[108]4398different for each output time.<br>
4399
4400
4401 </font></span></p>
4402
4403
4404
4405     
4406     
4407      <p><span lang="en-GB"><font face="Thorndale">In
[48]4408order to
4409guarantee 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;
[108]4410      <span style="font-weight: bold;">end_time</span>
[5]4411should be a little bit
4412larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b>
[48]4413= <i>900.0</i><span style="font-style: italic;">
[108]4414      </span>and 3600.0
[5]4415seconds are to be simulated, then it should be at least&nbsp; <b>end_time</b>
[48]4416&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
4417variable time steps are used
[5]4418(which is the default), <span style="font-weight: bold;">dt</span>
4419should be properly estimated.&nbsp; </font></span> </p>
[108]4420
4421
4422
4423     
4424     
4425      <p><span lang="en-GB"><font face="Thorndale">Data
[48]4426and output
4427format 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>
[108]4428      <span lang="en-GB"><font face="Thorndale">is
[48]4429internally fixed. In this file
[5]4430the profiles of the most important model variables are arranged in
[108]4431adjacent columns.</font></span> </p>
4432
4433
4434 </td>
4435
4436
4437 </tr>
4438
4439
4440
4441    <tr>
4442
4443
4444 <td style="vertical-align: top;"> 
4445     
4446     
4447      <p><a name="dt_dots"></a><b>dt_dots</b></p>
4448
4449
4450
4451      </td>
4452
4453
4454 <td style="vertical-align: top;">R</td>
4455
4456
4457
4458      <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
4459
4460
4461
4462      <td style="vertical-align: top;"> 
4463     
4464     
4465      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]4466interval</font> at which&nbsp;time series data shall be
4467output (</font>in <font face="Thorndale">s).&nbsp;</font>
[108]4468      </p>
4469
4470
4471 
4472     
4473     
4474      <p>The default interval for the output of timeseries
[48]4475is calculated as shown below (this tries to minimize the number of
[108]4476calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p>
4477
4478
4479     
4480     
4481      <p style="font-family: Courier New,Courier,monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
[48]4482IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
[108]4483== 0.0 )&nbsp; THEN<br>
4484
4485
4486&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4487      <span style="font-weight: bold;">dt_dots</span> =
4488MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
4489
4490
4491&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4492ELSE<br>
4493
4494
4495&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4496      <span style="font-weight: bold;">dt_dots</span> =
[48]4497MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
[108]4498)<br>
4499
4500
4501&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4502ENDIF</p>
4503
4504
4505     
4506     
4507      <p>This parameter can be used to
[48]4508assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
4509time is the beginning of
[5]4510&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
[48]45112*<b>dt_dots</b>, 3*<b>dt_dots</b>, etc. The
4512actual output times can
4513deviate 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;
4514Is <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
4515of the time series are
[5]4516written after each time step (if this is requested it should be <b>dt_dots</b>
[108]4517= <i>0</i>).</font></span></p>
4518
4519
4520     
4521     
4522      <p><span lang="en-GB"><font face="Thorndale">The default
[48]4523value of <span style="font-weight: bold;">dt_dots</span>
[108]4524is calculated as follows:</font></span></p>
4525
4526
4527&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
[48]4528IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
[108]4529== 0.0 )&nbsp; THEN<br>
4530
4531
4532&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4533      <span style="font-weight: bold;">dt_dots</span> =
4534MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
4535
4536
4537&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4538ELSE<br>
4539
4540
4541&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4542      <span style="font-weight: bold;">dt_dots</span> =
[48]4543MIN( <span style="font-weight: bold;">dt_run_control</span>,
[108]4544      <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
4545)<br>
4546
4547
4548&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4549ENDIF<br>
4550
4551
4552      <br>
4553
4554
4555(which minimizes the number of calls of
4556routine flow_statistics).<br>
4557
4558
4559     
4560     
4561      <p>By default time series data
[48]4562is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>.
4563Because of the default settings of <span style="font-weight: bold;">dt_dots</span>,
4564it will&nbsp;generally be created for each model run. The file's
4565format is NetCDF.&nbsp; Further details about processing NetCDF
[108]4566data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
4567
4568
4569The
[48]4570file contains the following timeseries quantities (the first column
[108]4571gives the name of the quantities as used in the NetCDF file):<br>
4572
4573
4574     
4575     
4576      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
4577
4578
4579 <tbody>
4580
4581
4582 <tr>
4583
4584
4585 <td style="font-style: italic; vertical-align: middle;">E<br>
4586
4587
4588
4589            </td>
4590
4591
4592 <td style="vertical-align: top;">Total
[48]4593kinetic energy of
4594the flow (in m<sup>2</sup>/s<sup>2</sup>)
4595(normalized with respect to the total number of grid points).</td>
[108]4596
4597
4598
4599          </tr>
4600
4601
4602 <tr>
4603
4604
4605 <td style="font-style: italic; vertical-align: middle;">E*<br>
4606
4607
4608
4609            </td>
4610
4611
4612 <td style="vertical-align: top;">Perturbation
[48]4613kinetic
4614energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
[108]4615            </sup>(normalized
[48]4616with respect to the total number of grid
[108]4617points)</td>
4618
4619
4620 </tr>
4621
4622
4623 <tr>
4624
4625
4626 <td style="vertical-align: top; font-style: italic;">dt<br>
4627
4628
4629
4630            </td>
4631
4632
4633 <td style="vertical-align: top;">Time step
4634size (in s).</td>
4635
4636
4637 </tr>
4638
4639
4640 <tr>
4641
4642
4643 <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
4644
4645
4646
4647            <td style="vertical-align: top;">Friction velocity (in
[48]4648m/s)
[108]4649(horizontal average).</td>
4650
4651
4652 </tr>
4653
4654
4655 <tr>
4656
4657
4658 <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
4659
4660
4661
4662            <td style="vertical-align: top;">Vertical velocity scale
[48]4663of
[108]4664the CBL (in m/s) (horizontal average)</td>
4665
4666
4667 </tr>
4668
4669
4670 <tr>
4671
4672
4673
4674            <td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
4675
4676
4677
4678            <td style="vertical-align: top;">Temperature
[48]4679scale (Prandtl layer), defined as <i>w"pt"0
4680/&nbsp;</i><i>u<sub>*</sub></i>
4681(horizontal
[108]4682average) (in K).</td>
4683
4684
4685 </tr>
4686
4687
4688 <tr>
4689
4690
4691 <td style="vertical-align: top; font-style: italic;">umax<br>
4692
4693
4694
4695            </td>
4696
4697
4698 <td style="vertical-align: top;">Maximum
[48]4699u-component of the
[108]4700velocity (in m/s).</td>
4701
4702
4703 </tr>
4704
4705
4706 <tr>
4707
4708
4709 <td style="vertical-align: top; font-style: italic;">vmax<br>
4710
4711
4712
4713            </td>
4714
4715
4716 <td style="vertical-align: top;">Maximum
[48]4717v-component of the
[108]4718velocity (in m/s).</td>
4719
4720
4721 </tr>
4722
4723
4724 <tr>
4725
4726
4727 <td style="vertical-align: top; font-style: italic;">wmax<br>
4728
4729
4730
4731            </td>
4732
4733
4734 <td style="vertical-align: top;">Maximum
[48]4735w-component of the
[108]4736velocity (in m/s).</td>
4737
4738
4739 </tr>
4740
4741
4742 <tr>
4743
4744
4745 <td style="vertical-align: top; font-style: italic;">div_old<br>
4746
4747
4748
4749            </td>
4750
4751
4752 <td style="vertical-align: top;">Divergence
[48]4753of the velocity
4754field before the pressure
4755solver has been called (normalized with respect to the total number of
[108]4756grid points) (in 1/s).</td>
4757
4758
4759 </tr>
4760
4761
4762 <tr>
4763
4764
4765 <td style="vertical-align: top; font-style: italic;">div_new</td>
4766
4767
4768
4769            <td style="vertical-align: top;">Divergence of the
[48]4770velocity
4771field after the pressure
4772solver has been called (normalized with respect to the total number of
[108]4773grid points) (in 1/s).</td>
4774
4775
4776 </tr>
4777
4778
4779 <tr>
4780
4781
4782 <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
4783
4784
4785
4786            <td style="vertical-align: top;">Height of the convective
[48]4787boundary layer (horizontal average)
4788determined by the height of the minimum sensible heat flux (in m).</td>
[108]4789
4790
4791
4792          </tr>
4793
4794
4795 <tr>
4796
4797
4798 <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
4799
4800
4801
4802            <td style="vertical-align: top;">Height of the convective
[48]4803boundary layer (horizontal average)
[108]4804determined by the temperature profile (in m).</td>
4805
4806
4807 </tr>
4808
4809
4810 <tr>
4811
4812
4813
4814            <td style="vertical-align: top; font-style: italic;">w"pt"0</td>
4815
4816
4817
4818            <td style="vertical-align: top;">Subgrid-scale sensible
[197]4819heat flux at k=0 (horizontal
4820average), constant within Prandtl-layer (in K m/s).</td>
[108]4821
4822
4823 </tr>
4824
4825
4826 <tr>
4827
4828
4829 <td style="vertical-align: top; font-style: italic;">w"pt"</td>
4830
4831
4832
4833            <td style="vertical-align: top;">Subgrid-scale heat flux
[48]4834(horizontal average) for z = zw(1) (in K
[108]4835m/s).</td>
4836
4837
4838 </tr>
4839
4840
4841 <tr>
4842
4843
4844 <td style="vertical-align: top; font-style: italic;">wpt</td>
4845
4846
4847
4848            <td style="vertical-align: top;">Total heat flux
4849(horizontal average) for z = zw(1) (in K m/s).</td>
4850
4851
4852 </tr>
4853
4854
[197]4855 <tr><td align="undefined" valign="undefined"><span style="font-style: italic;">w"u"0</span></td><td align="undefined" valign="undefined">Subgrid-scale momentum flux (u-component) at k=0 (horizontal average), constant within Prandtl-layer (in m<sup>2</sup>/s<sup>2</sup>).</td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic;">w"v"0</span></td><td align="undefined" valign="undefined">Subgrid-scale momentum flux (v-component) at k=0 (horizontal average), constant within Prandtl-layer (in m<sup>2</sup>/s<sup>2</sup>).</td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic;">w"q"0</span></td><td align="undefined" valign="undefined">Subgrid-scale
4856humidity flux at k=0 (horizontal average), constant within
4857Prandtl-layer (in kg/kg m/s). Zero values are output if humidity is not
4858used.</td></tr><tr>
[108]4859
4860
4861
4862            <td style="vertical-align: top; font-style: italic;">pt(0)</td>
4863
4864
4865
4866            <td style="vertical-align: top;">Potential temperature at
4867the surface (horizontal average) (in K).</td>
4868
4869
4870 </tr>
4871
4872
4873 <tr>
4874
4875
4876
4877            <td style="vertical-align: top; font-style: italic;">pt(zp)</td>
4878
4879
4880
4881            <td style="vertical-align: top;">Potential temperature for
4882z = zu(1) (horizontal average) (in K).</td>
4883
4884
4885 </tr>
4886
4887
[197]4888 
[108]4889
4890
[197]4891 
[108]4892
4893
[197]4894 
[108]4895
4896
4897 <tr>
4898
4899
4900 <td style="vertical-align: top; font-style: italic;">L</td>
4901
4902
4903
4904            <td style="vertical-align: top;">Monin-Obukhov length.</td>
4905
4906
4907
4908          </tr>
4909
4910
4911 
4912       
4913       
4914        </tbody> 
4915     
4916     
4917      </table>
4918
4919
4920      <br>
4921
4922
4923Additionally, the
[48]4924user can add his own timeseries quantities to the file, by using the
4925user-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>.
4926These routines contain (as comment lines) a simple example how to do
[108]4927this.<br>
4928
4929
4930      <br>
4931
4932
4933Time series data refers to the total
[48]4934domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
4935However, the following time series always present the values of the
4936total model domain (even with output for subdomains): <i>umax</i>,
[108]4937      <i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
4938      <i>div_new</i>.</td>
4939
4940
4941 </tr>
4942
4943
4944 <tr>
4945
4946
4947 <td style="vertical-align: top;"> 
4948     
4949     
4950      <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
4951
4952
4953
4954      </td>
4955
4956
4957 <td style="vertical-align: top;">R</td>
4958
4959
4960
4961      <td style="vertical-align: top;"><i>value of
4962&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
4963
4964
4965output</a></i></td>
4966
4967
4968
4969      <td style="vertical-align: top;"> 
4970     
4971     
4972      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]4973interval</font> at which&nbsp;horizontal cross section data
4974shall be output (</font>in <font face="Thorndale">s).&nbsp;
[108]4975      </font> </p>
4976
4977
4978 
4979     
4980     
4981      <p><span lang="en-GB"><font face="Thorndale">If output of
[5]4982horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
[108]4983      <span lang="en-GB"><font face="Thorndale">and
4984      </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
[48]4985parameter can be used to
[5]4986assign the temporal interval at which cross section data shall be
[48]4987output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
4988simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>,
4989which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
4990time is the beginning of the simulation, i.e. output
4991takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>,
[108]4992      <span style="font-weight: bold;">skip_time_do2d_xy</span>
[48]4993+ 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span>
4994+ 3*<b>dt_do2d_xy</b>,
[5]4995etc. The actual output times can deviate from these theoretical values
4996(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>
[108]4997
4998
4999
5000      </font></span></p>
5001
5002
5003 
5004     
5005     
5006      <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>
[48]5007has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5008the time t = 0 or at the
[5]5009respective starting times of restart runs).</font></span> </p>
[108]5010
5011
5012
5013      </td>
5014
5015
5016 </tr>
5017
5018
5019 <tr>
5020
5021
5022 <td style="vertical-align: top;"> 
5023     
5024     
5025      <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
5026
5027
5028
5029      </td>
5030
5031
5032 <td style="vertical-align: top;">R</td>
5033
5034
5035
5036      <td style="vertical-align: top;"><i>value of
5037&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5038
5039
5040output</a></i></td>
5041
5042
5043
5044      <td style="vertical-align: top;"> 
5045     
5046     
5047      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]5048interval</font> at which&nbsp;vertical cross sections data
5049(xz) shall be output (</font>in <font face="Thorndale">s).&nbsp;
[108]5050      </font> </p>
5051
5052
5053 
5054     
5055     
5056      <p><span lang="en-GB"><font face="Thorndale">If output of
[5]5057horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
[108]5058      <span lang="en-GB"><font face="Thorndale">and
5059      </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">),
[5]5060this parameter can be used to assign the temporal interval at which
[48]5061cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
5062be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which
5063has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
5064the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz
5065+ dt_do2d_xz</b>,
[108]5066      <span style="font-weight: bold;">skip_time_do2d_xz</span>
[48]5067+ 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span>
5068+ 3*<b>dt_do2d_xz</b>, etc. The actual output times
[5]5069can 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>
[108]5070
5071
5072
5073      </font></span></p>
5074
5075
5076 
5077     
5078     
5079      <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>
[48]5080has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5081the time t = 0 or at the
[5]5082respective starting times of restart runs).</font></span> </p>
[108]5083
5084
5085
5086      </td>
5087
5088
5089 </tr>
5090
5091
5092 <tr>
5093
5094
5095 <td style="vertical-align: top;"> 
5096     
5097     
5098      <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
5099
5100
5101
5102      </td>
5103
5104
5105 <td style="vertical-align: top;">R</td>
5106
5107
5108
5109      <td style="vertical-align: top;"><i>value of
5110&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5111
5112
5113output</a></i></td>
5114
5115
5116
5117      <td style="vertical-align: top;"> 
5118     
5119     
5120      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]5121interval</font> at which&nbsp;vertical cross section data
5122(yz) shall be output (</font>in s<font face="Thorndale">).&nbsp;
[108]5123      </font> </p>
5124
5125
5126 
5127     
5128     
5129      <p><span lang="en-GB"><font face="Thorndale">If output of
[5]5130horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
[108]5131      <span lang="en-GB"><font face="Thorndale">and
5132      </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">),
[5]5133this parameter can be used to assign the temporal interval at which
[48]5134cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
5135be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which
5136has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
5137time is the beginning of
5138the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz
5139+ dt_do2d_yz</b>,
[108]5140      <span style="font-weight: bold;">skip_time_do2d_yz</span>
[48]5141+ 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz
[108]5142      </span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
[48]5143times
[5]5144can 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>
[108]5145
5146
5147
5148      </font></span></p>
5149
5150
5151 
5152     
5153     
5154      <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>
[48]5155has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5156the time t = 0 or at the
[5]5157respective starting times of restart runs).</font></span> </p>
[108]5158
5159
5160
5161      </td>
5162
5163
5164 </tr>
5165
5166
5167 <tr>
5168
5169
5170 <td style="vertical-align: top;"> 
5171     
5172     
5173      <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
5174
5175
5176
5177      </td>
5178
5179
5180 <td style="vertical-align: top;">R</td>
5181
5182
5183
5184      <td style="vertical-align: top;"><i>value of
5185&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5186
5187
5188output</a></i></td>
5189
5190
5191
5192      <td style="vertical-align: top;"> 
5193     
5194     
5195      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]5196interval</font> at which 3d volume data shall be output (</font>in
[108]5197      <font face="Thorndale">s).&nbsp; </font> </p>
5198
5199
5200
5201     
5202     
5203      <p><span lang="en-GB"><font face="Thorndale">If
[48]5204output of
52053d-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
5206to assign
[5]5207th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
[48]5208interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
5209be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has
5210zero 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
5211time is the
5212beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d
5213+ dt_do3d</b>,
[108]5214      <span style="font-weight: bold;">skip_time_do3d</span>
[48]5215+ 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span>
5216+ 3*<b>dt_do3d</b>, etc. The actual output times can
[5]5217deviate 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>
[108]5218
5219
5220
5221      </font></span></p>
5222
5223
5224 
5225     
5226     
5227      <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>
[48]5228has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5229the time t = 0 or at the
[5]5230respective starting times of restart runs).</font></span> </p>
[108]5231
5232
5233
5234      </td>
5235
5236
5237 </tr>
5238
5239
5240 <tr>
5241
5242
5243      <td style="vertical-align: top;"><a name="dt_max"></a><span style="font-weight: bold;">dt_max</span></td>
5244
5245
5246      <td style="vertical-align: top;">R</td>
5247
5248
5249      <td style="vertical-align: top;"><span style="font-style: italic;">20.0</span></td>
5250
5251
5252      <td>Maximum
5253allowed value of the timestep (in s).<br>
5254
5255
5256      <br>
5257
5258
5259By default,
[61]5260the maximum timestep is restricted to be 20 s. This might be o.k. for
5261simulations of any kind of atmospheric turbulence but may have to be
[108]5262changed for other situations.</td>
5263
5264
5265    </tr>
5266
5267
5268    <tr>
5269
5270
5271 <td style="vertical-align: top;"> 
5272     
5273     
5274      <p><a name="dt_restart"></a><b>dt_restart</b></p>
5275
5276
5277
5278      </td>
5279
5280
5281 <td style="vertical-align: top;">R</td>
5282
5283
5284
5285      <td style="vertical-align: top;"><i>9999999.9</i></td>
5286
5287
5288
5289      <td style="vertical-align: top;"> 
5290     
5291     
5292      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]5293interval</font> at which a new
[108]5294restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p>
5295
5296
5297 
5298     
5299     
5300      <p><span lang="en-GB"><font face="Thorndale">For a
[48]5301description
[5]5302how 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>
5303does not show any effect, if <span style="font-weight: bold;">restart_time</span>
[108]5304has not been set.</font></span></p>
5305
5306     
5307      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
5308and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
5309
5310
5311 </td>
5312
5313
5314 </tr>
5315
5316
5317
5318    <tr>
5319
5320
5321 <td style="vertical-align: top;"> 
5322     
5323     
5324      <p><a name="dt_run_control"></a><b>dt_run_control</b></p>
5325
5326
5327
5328      </td>
5329
5330
5331 <td style="vertical-align: top;">R</td>
5332
5333
5334
5335      <td style="vertical-align: top;"><i>60.0</i></td>
5336
5337
5338
5339      <td style="vertical-align: top;"> 
5340     
5341     
5342      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]5343interval</font> at which run control
5344output is to be made (</font>in <font face="Thorndale">s).&nbsp;
[108]5345      </font> </p>
5346
5347
5348 
5349     
5350     
5351      <p><span lang="en-GB"><font face="Thorndale">Run control
[48]5352information 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
5353output time, one line
[5]5354with information about the size of the time step, maximum speeds, total
5355kinetic energy etc. is written to this file. Reference time is the
5356beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>,
[48]53572*<b>dt_run_control</b>, 3*<b>dt_run_control</b>,
5358etc., and always at
[5]5359the beginning of a model run (thus at the time t = 0 or at the
5360respective starting times of restart runs). The actual output times can
5361deviate 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>
[108]5362
5363
5364
5365      </font></span></p>
5366
5367
5368 
5369     
5370     
5371      <p><span lang="en-GB"><font face="Thorndale">Run control
[5]5372information is output after each time step can be achieved via <b>dt_run_control</b>
[108]5373= <i>0.0</i>.</font></span> </p>
5374
5375
5376 </td>
5377
5378
5379
5380    </tr>
5381
5382
5383 <tr>
5384
5385
5386 <td style="vertical-align: top;">
5387     
5388     
5389      <p><a name="end_time"></a><b>end_time</b></p>
5390
5391
5392
5393      </td>
5394
5395
5396 <td style="vertical-align: top;">R</td>
5397
5398
5399
5400      <td style="vertical-align: top;"><i>0.0</i></td>
5401
5402
5403
5404      <td style="vertical-align: top;"> 
5405     
5406     
5407      <p lang="en-GB"><font face="Thorndale">Simulation time of the 3D
[48]5408model (</font>in <font face="Thorndale">s).&nbsp;
[108]5409      </font> </p>
5410
5411
5412 
5413     
5414     
5415      <p><span lang="en-GB"><font face="Thorndale">The simulation time
[5]5416is starting from the beginning of the initialization run (t = 0), not
[108]5417starting from the beginning of the respective restart run.</font></span></p>
5418
5419     
5420      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
5421and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
5422
5423
5424 </td>
5425
5426
5427 </tr>
5428
5429
5430 <tr>
5431
5432
5433 <td style="vertical-align: top;"> 
5434     
5435     
5436      <p><a name="force_print_header"></a><b>force_print_header</b></p>
5437
5438
5439
5440      </td>
5441
5442
5443 <td style="vertical-align: top;">L</td>
5444
5445
5446
5447      <td style="vertical-align: top;"><i>.F.</i></td>
5448
5449
5450
5451      <td style="vertical-align: top;"> 
5452     
5453     
5454      <p>Steering of
[48]5455header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
[108]5456      </p>
5457
5458
5459 
5460     
5461     
5462      <p>By default, informations about the model
[48]5463parameters in use are
[5]5464output to the beginning of file RUN_CONTROL for initial runs only
5465(these informations are identical to that which are output to the local
5466file <a href="chapter_3.4.html#HEADER">HEADER</a>).
[48]5467With <b>force_print_header</b> = <i>.T.</i>,
5468these informations are
[5]5469also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
[108]5470at restart runs.</p>
5471
5472
5473 </td>
5474
5475
5476 </tr>
5477
5478
5479 <tr>
5480
5481
5482 <td style="vertical-align: top;"> 
5483     
5484     
5485      <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
5486
5487
5488
5489      </td>
5490
5491
5492 <td style="vertical-align: top;">I</td>
5493
5494
5495
5496      <td style="vertical-align: top;"><i>-1</i></td>
5497
5498
5499
5500      <td style="vertical-align: top;"> 
5501     
5502     
5503      <p>Number of
5504cycles to be used with the multi-grid scheme.<br>
5505
5506
5507 <br>
5508
5509
5510
[5]5511This parameter determines the number of cycles to be carried out in the
5512multi-grid method used for solving the Poisson equation for
5513perturbation pressure (see <a href="#psolver">psolver</a>).
5514The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br>
[108]5515
5516
5517
5518      </p>
5519
5520
5521 <br>
5522
5523
5524By default (<b>mg_cyles</b> = <i>-
[61]55251</i>), the
[48]5526number of cycles
[5]5527depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>)
5528and may vary from time step to time step. In this case, the CPU time
5529for a run will be difficult to estimate, since it heavily depends on
[108]5530the total number of the cycles to be carried out.<br>
5531
5532
5533 <br>
5534
5535
5536
[48]5537By assigning <b>mg_cycles</b> a value (&gt;=<span style="font-style: italic;">1</span>), the number of
5538cycles can be
[108]5539fixed so that the CPU time can be clearly estimated. <br>
5540
5541
5542 <br>
5543
5544
5545
5546      <b>Note:</b> When using a fixed number of cycles, the user
[48]5547must
[5]5548examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
5549regularly to check whether the divergence of the velocity field is
5550sufficiently reduced by the pressure solver. It should be reduced at
5551least by two orders of magnitude. For cyclic boundary conditions along
5552both horizontal directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
[48]5553and <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
5554good choice, for
[5]5555non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span>
[48]5556= <span style="font-style: italic;">4</span> may be
[108]5557sufficient.</td>
5558
5559
5560 </tr>
5561
5562
5563 <tr>
5564
5565
5566 <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
5567
5568
5569
5570level</b></td>
5571
5572
5573 <td style="vertical-align: top;">I</td>
5574
5575
5576
5577      <td style="vertical-align: top;"><br>
5578
5579
5580 </td>
5581
5582
5583 <td style="vertical-align: top;">Grid
5584level at which data shall be gathered on PE0.<br>
5585
5586
5587 <br>
5588
5589
5590
[5]5591In case of a run using several PEs and the multigrid method for solving
5592the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
5593the value of this parameter defines on which grid level the data are
5594gathered on PE0 in order to allow for a further coarsening of the grid.
5595The finest grid defines the largest grid level. By default, the
5596gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
5597It is only possible to gather data from a level larger than the one
5598determined automatically. A test run may be neccessary to determine
[197]5599this level.<br><br>Setting of <span style="font-weight: bold;">mg_switch_to_pe0_level</span> = <span style="font-style: italic;">-1</span> prevents that data are collected on PE0 at all, i.e. coarsening of grids is limited by the subdomains.</td>
[108]5600
5601
5602 </tr>
5603
5604
5605 <tr>
5606
5607
5608 <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</span><br>
5609
5610
5611
5612      </td>
5613
5614
5615 <td style="vertical-align: top;">L<br>
5616
5617
5618 </td>
5619
5620
5621
5622      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
5623
5624
5625 </td>
5626
5627
5628
[127]5629      <td style="vertical-align: top;">All NetCDF files - except those containing 3d
5630volume data - will have 64
5631bit offset format if&nbsp;<span style="font-weight: bold;">netcdf_64bit</span>
5632= .TRUE..<br>
[108]5633
5634
5635      <br>
5636
5637
5638By
[5]5639default, the maximum file size of the NetCDF files opened by PALM is 2
[127]5640GByte. Using <span style="font-weight: bold;">netcdf_64bit</span> = .TRUE. allows file sizes larger than 2
[108]5641GByte.<br>
5642
5643
5644      <br>
5645
5646
[127]5647The 64 bit offset format for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
[108]5648      <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>)
[127]5649is controlled independently by the switch <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br>
[108]5650
5651
5652      <br>
5653
5654
5655      <span style="font-weight: bold;">Warning:</span><br>
5656
5657
5658Some
[48]5659(PD or commercial) software may not support the 64 bit offset format.<br>
[108]5660
5661
5662
5663      </td>
5664
5665
5666 </tr>
5667
5668
5669    <tr>
5670
5671
5672      <td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td>
5673
5674
5675      <td style="vertical-align: top;">L</td>
5676
5677
5678      <td style="vertical-align: top;">.T.</td>
5679
5680
5681      <td style="vertical-align: top;">NetCDF files containing 3d
[127]5682volume data will have 64 bit offset format if&nbsp;<span style="font-weight: bold;">netcdf_64bit_3d</span>
5683= .TRUE..<br><br>
[108]5684
5685
[127]5686By
5687default, the maximum file size of the NetCDF files opened by PALM is 2
5688GByte. Using <span style="font-weight: bold;">netcdf_64bit_3d</span> = .TRUE. allows file sizes larger than 2
5689GByte.<br><br>
[108]5690
5691
[127]5692The 64 bit offset format for all other NetCDF files (<span style="font-style: italic;">not</span> containing 3d volume data) is controlled independently by the switch <a href="chapter_4.2.html#netcdf_64bit">netcdf_64bit</a>.<br><br>
[108]5693
5694
[127]5695      <span style="font-weight: bold;">Warning:</span><br>
5696
5697
5698Some
5699(PD or commercial) software may not support the 64 bit offset format.</td>
5700
5701
[108]5702    </tr>
5703
5704
5705    <tr>
5706
5707
5708
5709      <td style="vertical-align: top;"> 
5710     
5711     
5712      <p><a name="ngsrb"></a><b>ngsrb</b></p>
5713
5714
5715 </td>
5716
5717
5718
5719      <td style="vertical-align: top;">I</td>
5720
5721
5722 <td style="vertical-align: top;"><i>2</i></td>
5723
5724
5725
5726      <td style="vertical-align: top;">Grid
5727level at which data shall be gathered on PE0.<br>
5728
5729
5730 <br>
5731
5732
5733
[5]5734In case of a run using several PEs and the multigrid method for solving
5735the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
5736the value of this parameter defines on which grid level the data are
5737gathered on PE0 in order to allow for a further coarsening of the grid.
5738The finest grid defines the largest grid level. By default, the
5739gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
5740It is only possible to gather data from a level larger than the one
5741determined automatically. A test run may be neccessary to determine
[108]5742this level.</td>
5743
5744
5745 </tr>
5746
5747
5748 <tr>
5749
5750
5751 <td style="vertical-align: top;"> 
5752     
5753     
5754      <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
5755
5756
5757
5758      </td>
5759
5760
5761 <td style="vertical-align: top;">I</td>
5762
5763
5764
5765      <td style="vertical-align: top;"><span style="font-style: italic;">0</span><br>
5766
5767
5768 </td>
5769
5770
5771
5772      <td style="vertical-align: top;"> 
5773     
5774     
5775      <p>Determines the
[48]5776subdomain from which the normalization
[108]5777quantities are calculated.&nbsp; </p>
5778
5779
5780 
5781     
5782     
5783      <p>If output
[48]5784data of the horizontally averaged vertical profiles
[5]5785(see <a href="#data_output_pr">data_output_pr</a>)
5786is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>,
[108]5787      <a href="#cross_normalized_y">cross_normalized_y</a>),
[5]5788the respective normalization quantities are by default calculated from
5789the averaged data of the total model domain (<b>normalizing_region</b>
[48]5790= <i>0</i>) and are thus representative for the total
5791domain. Instead
[5]5792of that, normalization quantities can also be calculated for a
[48]5793subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>,
5794where <i>1</i>
5795&lt;= <b>normalizing_region</b> &lt;= <i>9 </i>must
5796hold. These
[5]5797quantities are then used for normalizing of all profiles (even for that
[108]5798of the total domain).</p>
5799
5800
5801 </td>
5802
5803
5804 </tr>
5805
5806
[197]5807 <tr><td style="vertical-align: top;"><a href="npex"><span style="font-weight: bold;"></span></a><span style="font-weight: bold;"><a name="npex"></a>npex</span></td><td style="vertical-align: top;">I</td><td style="vertical-align: top;"></td><td style="vertical-align: top;"><p>Number of processors
5808along x-direction of the virtual
5809processor
5810net.&nbsp; </p>
[108]5811
5812
[197]5813
5814
5815
5816
5817 
5818     
5819     
5820     
5821     
5822     
5823     
5824      <p>For parallel runs, the total
5825number of processors to be used
5826is given by
5827the <span style="font-weight: bold;">mrun</span>
5828option <a href="http://www.muk.uni-hannover.de/software/mrun_beschreibung.html#Opt-X">-X</a>.
5829By default, depending on the type of the parallel computer, PALM
5830generates a 1d processor
5831net (domain decomposition along x, <span style="font-weight: bold;">npey</span>
5832= <span style="font-style: italic;">1</span>) or a
58332d-net (this is
5834favored on machines with fast communication network and/or large number of processors (&gt;256)). In case of a
58352d-net, it is tried to make it more or less square-shaped. If, for
5836example, 16 processors are assigned (-X 16), a 4 * 4 processor net is
5837generated (<span style="font-weight: bold;">npex</span>
5838= <span style="font-style: italic;">4</span>, <span style="font-weight: bold;">npey</span>
5839= <span style="font-style: italic;">4</span>).
5840This choice is optimal for square total domains (<a href="chapter_4.1.html#nx">nx</a>
5841= <a href="chapter_4.1.html#ny">ny</a>),
5842since then the number of ghost points at the lateral boundarys of
5843the subdomains reaches a minimum. If <span style="font-weight: bold;">nx</span>
5844and <span style="font-weight: bold;">ny</span>
5845differ extremely, the
5846processor net should be manually adjusted using adequate values for <span style="font-weight: bold;">npex</span> and <span style="font-weight: bold;">npey</span>.&nbsp; </p>
5847
5848
5849
5850
5851
5852
5853
5854     
5855     
5856     
5857     
5858     
5859     
5860      <p><b>Important:</b> The value of <span style="font-weight: bold;">npex</span> * <span style="font-weight: bold;">npey</span> must exactly match the
5861value assigned by the <span style="font-weight: bold;">mrun</span>-option
5862      <tt>-X</tt>.
5863Otherwise the model run will abort with a corresponding error
5864message.&nbsp; <br>
5865
5866
5867
5868
5869
5870
5871
5872Additionally, the specification of <span style="font-weight: bold;">npex</span>
5873and <span style="font-weight: bold;">npey</span>
5874may of course
5875override the default setting for the domain decomposition (1d or 2d)
5876which may have a significant (negative) effect on the code performance.
5877      </p></td></tr><tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="npey"></a>npey</span></td><td style="vertical-align: top;">I</td><td style="vertical-align: top;"></td><td style="vertical-align: top;"><p>Number of processors
5878along y-direction of the virtual
5879processor
5880net.&nbsp; </p>
5881
5882
5883
5884
5885
5886
5887 
5888     
5889     
5890     
5891     
5892     
5893     
5894      <p>For further information see <a href="chapter_4.2.html#npex">npex</a>.</p></td></tr><tr>
5895
5896
[108]5897 <td style="vertical-align: top;"> 
5898     
5899     
5900      <p><a name="nsor"></a><b>nsor</b></p>
5901
5902
5903
5904      </td>
5905
5906
5907 <td style="vertical-align: top;">I</td>
5908
5909
5910
5911      <td style="vertical-align: top;"><i>20</i></td>
5912
5913
5914
5915      <td style="vertical-align: top;"> 
5916     
5917     
5918      <p>Number of
5919iterations to be used with the SOR-scheme.&nbsp; </p>
5920
5921
5922 
5923     
5924     
5925      <p>This
[48]5926parameter is only effective if the SOR-scheme is selected
[5]5927as pressure solver (<a href="#psolver">psolver</a>
[48]5928= <span style="font-style: italic;">'sor'</span>).
5929The number of
[5]5930iterations necessary for a sufficient convergence of the scheme depends
5931on the grid point numbers and is to be determined by appropriate test
5932runs (the default value will not at all be sufficient for larger grid
5933point numbers). The number of iterations used for the first call of the
5934SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p>
[108]5935
5936
5937
5938      </td>
5939
5940
5941 </tr>
5942
5943
5944 <tr>
5945
5946
5947 <td style="vertical-align: top;"> 
5948     
5949     
5950      <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
5951
5952
5953
5954      </td>
5955
5956
5957 <td style="vertical-align: top;">I</td>
5958
5959
5960
5961      <td style="vertical-align: top;"><i>nz+1</i></td>
5962
5963
5964
5965      <td style="vertical-align: top;"> Limits the output of 3d
5966volume data along the vertical direction (grid point index k).<br>
5967
5968
5969      <br>
5970
5971
5972By
[48]5973default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
[5]5974can be used to limit the output up to a certain vertical grid point
5975(e.g. in order to reduce the amount of output data). It affects all
[48]5976output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output
5977for <span style="font-weight: bold;">dvrp</span>-software,
5978see <a href="#mode_dvrp">mode_dvrp</a>).</td>
[108]5979
5980
5981
5982    </tr>
5983
5984
5985 <tr>
5986
5987
5988 <td style="vertical-align: top;">
5989     
5990     
5991      <p><a name="omega_sor"></a><b>omega_sor</b></p>
5992
5993
5994
5995      </td>
5996
5997
5998 <td style="vertical-align: top;">R</td>
5999
6000
6001
6002      <td style="vertical-align: top;"><i>1.8</i></td>
6003
6004
6005
6006      <td style="vertical-align: top;"> 
6007     
6008     
6009      <p>Convergence
6010factor to be used with the the SOR-scheme.&nbsp; </p>
6011
6012
6013 
6014     
6015     
6016      <p>If
[48]6017the SOR-scheme is selected (<a href="#psolver">psolver</a>
6018= <span style="font-style: italic;">'sor'</span>),
6019this parameter
6020determines the value of the convergence factor, where <i>1.0</i>
6021&lt;= <b>omega_sor</b> &lt; <i>2.0 </i>.
6022The optimum value of <b>omega_sor</b>
[5]6023depends on the number of grid points along the different directions in
6024space. For non-equidistant grids it can only be determined by
[108]6025appropriate test runs.</p>
6026
6027
6028 </td>
6029
6030
6031 </tr>
6032
6033
6034 <tr>
6035
6036
6037 <td style="vertical-align: top;"> 
6038     
6039     
6040      <p><a name="prandtl_number"></a><b>prandtl_number</b></p>
6041
6042
6043
6044      </td>
6045
6046
6047 <td style="vertical-align: top;">R</td>
6048
6049
6050
6051      <td style="vertical-align: top;"><i>1.0</i></td>
6052
6053
6054
6055      <td style="vertical-align: top;"> 
6056     
6057     
6058      <p>Ratio of the
[48]6059eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).&nbsp;
[108]6060      </p>
6061
6062
6063 
6064     
6065     
6066      <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
[5]6067this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub>
[108]6068/ K<sub>h</sub>).</p>
6069
6070
6071 </td>
6072
6073
6074 </tr>
6075
6076
6077 <tr>
6078
6079
6080      <td style="vertical-align: top;"><a name="precipitation_amount_interval"></a><span style="font-weight: bold;">precipitation_amount_</span><br style="font-weight: bold;">
6081
6082
6083      <span style="font-weight: bold;">interval</span></td>
6084
6085
6086      <td style="vertical-align: top;">R</td>
6087
6088
6089      <td style="vertical-align: top;"><i>value of
6090&nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>
6091
6092
6093xy</a></i></td>
6094
6095
6096      <td style="vertical-align: top;">
6097     
6098     
6099      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[72]6100interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;
[108]6101      </font> </p>
6102
6103
6104 
6105     
6106     
6107      <p><span lang="en-GB"></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"></span></a><span lang="en-GB"></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">This
[72]6108parameter requires <a href="chapter_4.1.html#precipitation">precipitation</a> = <span style="font-style: italic;">.TRUE.</span>.&nbsp;</font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>The interval must be smaller or equal than the output interval for 2d horizontal cross sections given by </font></span><a href="chapter_4.2.html#dt_do2d_xy"><span lang="en-GB"><font face="Thorndale">dt_do2d_xy</font></span></a><span lang="en-GB"><font face="Thorndale">). The output of the precipitation amount also requires setting of <a href="chapter_4.2.html#data_output">data_output</a> =<span style="font-style: italic;"> 'pra*'</span>.<br>
[108]6109
6110
6111
6112      </font></span></p>
6113
6114
6115 <span lang="en-GB"></span></td>
6116
6117
6118    </tr>
6119
6120
6121    <tr>
6122
6123
6124
6125      <td style="vertical-align: top;"> 
6126     
6127     
6128      <p><a name="profile_columns"></a><b>profile_columns</b></p>
6129
6130
6131
6132      </td>
6133
6134
6135 <td style="vertical-align: top;">I</td>
6136
6137
6138
6139      <td style="vertical-align: top;"><i>3</i></td>
6140
6141
6142
6143      <td style="vertical-align: top;"> 
6144     
6145     
6146      <p>Number of
[48]6147coordinate systems to be plotted<span style="font-weight: bold;"></span>
6148in one row by <span style="font-weight: bold;">profil</span>.&nbsp;
[108]6149      </p>
6150
6151
6152 
6153     
6154     
6155      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
6156= <span style="font-style: italic;">'profil'</span>.</p>
6157
6158
6159     
6160     
6161      <p>It
[48]6162determines the layout of plots of
[5]6163horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
6164when plotted with the plot software <span style="font-weight: bold;">profil</span>.
6165Generally, the number and sequence of coordinate systems (panels) to be
6166plotted on one page are
[48]6167determined by <a href="#cross_profiles">cross_profiles</a>.
[108]6168      <b>profile_columns</b>
[5]6169determines how many panels are to be
6170arranged next to each other in one row (number of columns). The
6171respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>.
6172According to their order given by <a href="#data_output_pr">data_output_pr</a>,
6173the panels are arranged beginning in the top row from left to right and
[48]6174then continued in the following row. If the number of panels cranz
6175&gt; <b>profile_columns</b> * <b>profile_rows</b>,
6176the remaining
[5]6177panels are drawn on an additional page. If cranz &lt; <b>profile_columns</b>,
[48]6178then <b>profile_columns</b> = cranz is automatically set.
6179If
[5]6180row&nbsp; contains any panel, then the value of <b>profile_rows</b>
[108]6181is reduced automatically.</p>
6182
6183
6184 </td>
6185
6186
6187 </tr>
6188
6189
6190 <tr>
6191
6192
6193
6194      <td style="vertical-align: top;"> 
6195     
6196     
6197      <p><a name="profile_rows"></a><b>profile_rows</b></p>
6198
6199
6200
6201      </td>
6202
6203
6204 <td style="vertical-align: top;">I</td>
6205
6206
6207
6208      <td style="vertical-align: top;"><i>2</i></td>
6209
6210
6211
6212      <td style="vertical-align: top;"> 
6213     
6214     
6215      <p>Number of rows
[48]6216of coordinate systems to be plotted on one page
6217by <span style="font-weight: bold;">profil</span>.&nbsp;
[108]6218      </p>
6219
6220
6221 
6222     
6223     
6224      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
6225= <span style="font-style: italic;">'profil'</span>.</p>
6226
6227
6228     
6229     
6230      <p>It
[48]6231determines the layout of plots of horizontally averaged
[5]6232profiles. See <a href="#profile_columns">profile_columns</a>.</p>
[108]6233
6234
6235
6236      </td>
6237
6238
6239 </tr>
6240
6241
6242 <tr>
6243
6244
6245 <td style="vertical-align: top;"> 
6246     
6247     
6248      <p><a name="psolver"></a><b>psolver</b></p>
6249
6250
6251
6252      </td>
6253
6254
6255 <td style="vertical-align: top;">C * 10</td>
6256
6257
6258
6259      <td style="vertical-align: top;"><i>'poisfft'</i></td>
6260
6261
6262
6263      <td style="vertical-align: top;"> 
6264     
6265     
6266      <p>Scheme to be
[48]6267used to solve the Poisson equation for the
[108]6268perturbation pressure.&nbsp; </p>
6269
6270
6271 <br>
6272
6273
6274
6275The user can choose between the following schemes:<br>
6276
6277
6278 
6279     
6280     
6281      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
6282
6283
6284 <tbody>
6285
6286
6287 <tr>
6288
6289
6290 <td style="vertical-align: top;"><i>poisfft</i></td>
6291
6292
6293
6294            <td style="vertical-align: top;">Direct method using FFT
[5]6295along x and y, solution of a
6296tridiagonal matrix along z, and backward
6297FFT (see Siano, institute reports, volume 54). The FFT routines to be
6298used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
[108]6299
6300
6301
[5]6302This solver is specially optimized for 1d domain decompositions.
6303Vectorization is optimized for domain decompositions along x only.</td>
[108]6304
6305
6306
6307          </tr>
6308
6309
6310 <tr>
6311
6312
6313 <td style="vertical-align: top;">
6314           
6315           
6316            <p><i>poisfft_</i>
6317            <br>
6318
6319
6320 <i>hybrid</i></p>
6321
6322
6323
6324            </td>
6325
6326
6327 <td style="vertical-align: top;">Direct
[48]6328method using FFT
[5]6329along x and y, solution of a
6330tridiagonal matrix along z, and backward
6331FFT (see Siano, institute reports, volume 54). The FFT routines to be
6332used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
[108]6333
6334
6335
[5]6336This solver is specially optimized for 1d domain decompositions.
6337Vectorization is optimized for domain decompositions along x only.</td>
[108]6338
6339
6340
6341          </tr>
6342
6343
6344 <tr>
6345
6346
6347 <td style="vertical-align: top;"><i>multigrid</i></td>
6348
6349
6350
6351            <td style="vertical-align: top;"> 
6352           
6353           
6354            <p>Multi-grid
[48]6355scheme (see Uhlenbrock, diploma thesis). v-
[5]6356and
6357w-cycles (see <a href="#cycle_mg">cycle_mg</a>)
6358are implemented. The convergence of the iterative scheme can be
6359steered by the number of v-/w-cycles to be carried out for each call of
6360the scheme (<a href="#mg_cycles">mg_cycles</a>)
6361and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>)
6362to be carried out on each grid level. Instead the requested accuracy
[48]6363can be given via <a href="#residual_limit">residual_limit</a>.
[108]6364            <span style="font-weight: bold;">This is the default!</span>
[5]6365The
6366smaller this limit is, the more cycles have to be carried out in this
6367case and the number of cycles may vary from timestep to timestep.</p>
[108]6368
6369
6370
6371            <br>
6372
6373
6374If <a href="#mg_cycles">mg_cycles</a>
[5]6375is set to its optimal value, the computing time of the
[48]6376multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
6377the number of
[5]6378grid points in the three directions
6379of space corresponds to a power-of-two (2<sup>n</sup>)
[48]6380where <i>n</i> &gt;= 5 must hold. With large <i>n,
[108]6381            </i>the
[5]6382multi-grid scheme can even be faster than the direct solver (although
6383its accuracy is several orders of magnitude worse, but this does not
6384affect the accuracy of the simulation). Nevertheless, the user should
6385always carry out some test runs in order to find out the optimum value
6386for <a href="#mg_cycles">mg_cycles</a>,
6387because the CPU time of a run very critically depends on this
[108]6388parameter.
6389           
6390           
6391            <p>This scheme requires that the number of grid
[48]6392points of
[5]6393the
6394subdomains (or of the total domain, if only one PE is uesd) along each
6395of the directions can at least be devided once by 2 without rest.</p>
[108]6396
6397
6398
[5]6399With parallel runs, starting from a certain grid level the
6400data of the subdomains are possibly gathered on PE0 in order to allow
6401for a further coarsening of the grid. The grid level for gathering can
6402be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
[108]6403
6404
6405
6406           
6407           
6408            <p>Using this procedure requires the subdomains to be of
[5]6409identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p>
[108]6410
6411
6412
6413            </td>
6414
6415
6416 </tr>
6417
6418
6419 <tr>
6420
6421
6422 <td style="vertical-align: top;"><i>sor</i></td>
6423
6424
6425
6426            <td style="vertical-align: top;">Successive over
[48]6427relaxation
[5]6428method (SOR). The convergence of
6429this
6430iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>,
[108]6431            <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
[48]6432and <a href="chapter_4.1.html#nsor">nsor</a>.&nbsp;
[108]6433            <br>
6434
6435
6436Compared to the direct method and the multi-grid method, this
[48]6437scheme
[5]6438needs substantially
6439more computing time. It should only be used for test runs, e.g. if
[108]6440errors in the other pressure solver methods are assumed.</td>
6441
6442
6443 </tr>
6444
6445
6446
6447       
6448       
6449        </tbody> 
6450     
6451     
6452      </table>
6453
6454
6455 <br>
6456
6457
6458In order to speed-up
[61]6459performance, the Poisson equation is by default
[5]6460only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver
6461at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>).&nbsp;
[108]6462      </td>
6463
6464
6465 </tr>
6466
6467
6468 <tr>
6469
6470
6471 <td style="vertical-align: top;"> 
6472     
6473     
6474      <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
6475      <br>
6476
6477
6478 <b>_factor</b></p>
6479
6480
6481 </td>
6482
6483
6484 <td style="vertical-align: top;">R</td>
6485
6486
6487 <td style="vertical-align: top;"><i>0.0 or</i><br>
6488
6489
6490
6491      <i>0.01</i></td>
6492
6493
6494 <td style="vertical-align: top;">
6495     
6496     
6497      <p>Factor for Rayleigh damping.&nbsp; </p>
6498
6499
6500 
6501     
6502     
6503      <p>A
[48]6504so-called Rayleigh damping is applied to all prognostic
[5]6505variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>.&nbsp;
6506If switched on, variables are forced towards the value of their
6507respective basic states (e.g. the geostrophic wind). The intensity of
6508damping is controlled by the value the <b>rayleigh_damping_factor</b>
6509is assigned to.
6510The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a>
[48]6511and rises according to a sin<sup>2</sup>-function to its
6512maximum value
[5]6513at
[108]6514the top (ocean: bottom) boundary. </p>
6515
6516
6517 
6518     
6519     
6520      <p>This method
[5]6521effectively damps gravity waves, caused by boundary layer convection,
6522which may spread out vertically in the inversion layer and which are
[108]6523reflected&nbsp;at the top (ocean: bottom)
[5]6524boundary. This particularly happens with the upstream-spline scheme
6525switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
6526or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>).
6527Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b>
[48]6528= <i>0.01</i>) by default. Otherwise it remains switched
[108]6529off.&nbsp; </p>
6530
6531
6532 
6533     
6534     
6535      <p>The Rayleigh damping factor must
[48]6536hold the condition <i>0.0</i>
[5]6537&lt;= <b>rayleigh_damping_factor</b>
6538&lt;= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
[108]6539numerical instabilities.</p>
6540
6541
6542 </td>
6543
6544
6545 </tr>
6546
6547
6548 <tr>
6549
6550
6551
6552      <td style="vertical-align: top;"> 
6553     
6554     
6555      <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
6556      <br>
6557
6558
6559 <b>_height</b></p>
6560
6561
6562 </td>
6563
6564
6565 <td style="vertical-align: top;">R</td>
6566
6567
6568 <td style="vertical-align: top;"> 
6569     
6570     
6571      <p><i>2/3 *</i>
6572      <br>
6573
6574
6575      <span style="font-style: italic;">zu</span><i style="font-style: italic;">(nz)</i></p>
6576      <p> (ocean:<i style="font-style: italic;">&nbsp;</i><i>2/3 *</i>
6577      <i style="font-style: italic;"> zu(0)</i>)</p>
6578
6579
6580
6581      </td>
6582
6583
6584 <td style="vertical-align: top;"> 
6585     
6586     
6587      <p>Height above (ocean: below) which the Rayleigh damping starts (in m).&nbsp; </p>
6588
6589
6590 
6591     
6592     
6593      <p>With
[48]6594Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
[5]6595this parameter determines the range where damping is applied. By
[108]6596default, Rayleigh damping will be applied in the upper (ocean: lower) third of the
[5]6597model
[108]6598domain.</p>
6599
6600
6601 </td>
6602
6603
6604 </tr>
6605
6606
6607 <tr>
6608
6609
6610 <td style="vertical-align: top;"> 
6611     
6612     
6613      <p><a name="residual_limit"></a><b>residual_limit</b></p>
6614
6615
6616
6617      </td>
6618
6619
6620 <td style="vertical-align: top;">R</td>
6621
6622
6623
6624      <td style="vertical-align: top;"><i>1.0E-6</i></td>
6625
6626
6627
6628      <td style="vertical-align: top;"> 
6629     
6630     
6631      <p>Largest
[48]6632residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>).&nbsp;
[108]6633      </p>
6634
6635
6636 
6637     
6638     
6639      <p>This is a parameter to steer the accuracy of the
[48]6640multi-grid
[5]6641scheme (see <a href="#psolver">psolver</a>).
6642The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>)
[48]6643is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If
6644this
[5]6645is not the case after 1000 cycles, the PALM aborts with a corresponding
[108]6646error message.</p>
6647
6648
6649 
6650     
6651     
6652      <p>The reciprocal value of this
[48]6653parameter can be interpreted as
[5]6654a factor by the divergence of the provisional
6655velocity field is approximately reduced after the multi-grid scheme has
6656been applied (thus the default value causes a reduction of the
[108]6657divergence by approx. 6 orders of magnitude).&nbsp; </p>
6658
6659
6660 </td>
6661
6662
6663
6664    </tr>
6665
6666
6667 <tr>
6668
6669
6670 <td style="vertical-align: top;">
6671     
6672     
6673      <p><a name="restart_time"></a><b>restart_time</b></p>
6674
6675
6676
6677      </td>
6678
6679
6680 <td style="vertical-align: top;">R</td>
6681
6682
6683
6684      <td style="vertical-align: top;"><i>9999999.9</i></td>
6685
6686
6687
6688      <td style="vertical-align: top;"> 
6689     
6690     
6691      <p>Simulated time
[48]6692after which a restart run is to be carried out
[108]6693(in s). </p>
6694
6695
6696 
6697     
6698     
6699      <p>The simulated time refers to the
[48]6700beginning of the
[5]6701initial run (t = 0), not to the beginning of the respective
6702restart run. Restart runs can additionally be forced to be carried out
[108]6703in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p>
6704
6705
6706 
6707     
6708     
6709      <p><span style="font-weight: bold;">Note:</span><br>
6710
6711
6712
[5]6713A successful operation of this parameter requires additional
6714modifications in the <span style="font-weight: bold;">mrun</span>-call
6715for the respective run (see <a href="chapter_3.3.html">chapter
[108]67163.3</a>).<br>
6717
6718
6719 </p>
6720
6721
6722 
6723     
6724     
6725      <p>The choice of <b>restart_time</b>
[48]6726or <b>dt_restart</b> does
[5]6727not override the automatic start of restart runs in case that the job
[108]6728runs out of CPU time. <br>
6729
6730      </p>
6731
6732     
6733      <p>For <a href="chapter_3.8.html">coupled runs</a> this parameter must be&nbsp;equal in both parameter files <a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2"><span style="font-family: mon;"></span>PARIN</font></a>
6734and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
6735
6736
6737 </td>
6738
6739
6740 </tr>
6741
6742
6743
6744    <tr>
6745
6746
6747 <td style="vertical-align: top;"> 
6748     
6749     
6750      <p><a name="section_xy"></a><b>section_xy</b></p>
6751
6752
6753
6754      </td>
6755
6756
6757 <td style="vertical-align: top;">I(100)<br>
6758
6759
6760
6761      </td>
6762
6763
6764 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
6765
6766
6767
6768      </td>
6769
6770
6771 <td style="vertical-align: top;"> 
6772     
6773     
6774      <p lang="en-GB"><font face="Thorndale">Position
[48]6775of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
[108]6776sections (grid point index k).&nbsp; </font> </p>
6777
6778
6779 
6780     
6781     
6782      <p><span lang="en-GB"><font face="Thorndale">If output
[48]6783of
6784horizontal 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
6785parameter can be used to
[5]6786define the position(s) of the cross section(s). Up to 100 positions of
6787cross sections can be selected by assigning <b>section_xy</b>
6788the
6789corresponding vertical grid point index/indices k of the requested
6790cross section(s). The exact location (height level) of the cross
6791section depends on the variable for which the output is made: zu(k) for
6792scalars and horizontal velocities, zw(k) for the vertical velocity.
6793Information about the exact location of the cross section is contained
6794in the NetCDF output file (if the default NetCDF output is switched on;
[108]6795see <a href="#data_output_format">data_output_format</a>).</font></span></p>
6796
6797
6798     
6799     
6800      <p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
[48]6801creates the output of horizontal cross sections averaged along z. In
6802the
6803NetCDF output file these (averaged) cross sections are given the
[108]6804z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p>
6805
6806
6807     
6808     
6809      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
[5]6810does not effect the output of horizontal cross sections of variable u<sub>*</sub>
[48]6811and theta<sub>*</sub> and the liquid water path lwp*. For
6812these quantities always only one cross
[108]6813section (for z=zu(1)) is output.</font></span></p>
6814
6815
6816      <span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
6817      <span style="font-style: italic;">'iso2d'</span> and
[48]6818if several cross sections are selected (e.g. <b>section_xy</b>
6819= <i>1</i>, <i>10</i>, <i>15</i>),
6820then the respective data are
[5]6821successively written to file. The output order follows the order given
6822by <b>section_xy</b>.&nbsp;</font></span></td>
[108]6823
6824
6825
6826    </tr>
6827
6828
6829 <tr>
6830
6831
6832 <td style="vertical-align: top;">
6833     
6834     
6835      <p><a name="section_xz"></a><b>section_xz</b></p>
6836
6837
6838
6839      </td>
6840
6841
6842 <td style="vertical-align: top;">I(100)<br>
6843
6844
6845
6846      </td>
6847
6848
6849 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
6850
6851
6852
6853      <td style="vertical-align: top;"> 
6854     
6855     
6856      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
[48]6857for&nbsp;output of 2d (xz) vertical cross sections (grid point
[108]6858index j).&nbsp; </font> </p>
6859
6860
6861 <span lang="en-GB"><font face="Thorndale">If output of
[48]6862vertical 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
6863parameter can be used to
[5]6864define the position(s) of the cross section(s). Up to 100 positions of
[48]6865cross sections can be selected by assigning <b>section_xz</b>
6866the
[5]6867corresponding horizontal grid point index/indices j of the requested
6868cross section(s). The exact position (in y-direction) of the cross
[48]6869section 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
6870on which grid the output quantity is defined. However, in
6871the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
6872default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
6873no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all
[108]6874positions.<br>
6875
6876
6877      <br>
6878
6879
6880Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
[5]6881creates the output of vertical cross sections averaged along y. In the
6882NetCDF output file these (averaged) cross sections are given the
[108]6883y-coordinate <span style="font-style: italic;">-1.0</span>.<br>
6884
6885
6886      </font></span><span lang="en-GB"><font face="Thorndale"><br>
6887
6888
6889      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
6890      <span style="font-style: italic;">'iso2d'</span> and
6891      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
[48]6892selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>,
[108]6893      <i>27</i>),
[5]6894then the respective data are successively written to file. The output
6895order follows the order given by <b>section_xz</b>.</font></span></td>
[108]6896
6897
6898
6899    </tr>
6900
6901
6902 <tr>
6903
6904
6905 <td style="vertical-align: top;">
6906     
6907     
6908      <p><a name="section_yz"></a><b>section_yz</b></p>
6909
6910
6911
6912      </td>
6913
6914
6915 <td style="vertical-align: top;">I(100)<br>
6916
6917
6918
6919      </td>
6920
6921
6922 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
6923
6924
6925
6926      <td style="vertical-align: top;"> 
6927     
6928     
6929      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
[48]6930for&nbsp;output of 2d (yz) vertical cross sections (grid point
[108]6931index i).&nbsp; </font> </p>
6932
6933
6934 <span lang="en-GB"><font face="Thorndale">If output of
[5]6935vertical 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">),
6936this parameter can be used to define the position(s) of the cross
6937section(s). Up to 100 positions of cross sections can be selected by
[48]6938assigning <b>section_yz</b> the corresponding horizontal
6939grid point
[5]6940index/indices i of the requested cross section(s). The exact position
[48]6941(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
6942on which grid the output quantity is defined.&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">However, in
6943the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
6944default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
6945no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all
[108]6946positions.<br>
6947
6948
6949      <br>
6950
6951
6952      </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>
[5]6953creates the output of vertical cross sections averaged along x. In the
[48]6954NetCDF output file these (averaged) cross sections are given the
[108]6955x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br>
6956
6957
6958      <span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br>
6959
6960
6961      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
6962      <span style="font-style: italic;">'iso2d'</span> and
6963      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
[48]6964selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the
[5]6965respective data are successively written to file. The output order
6966follows the order given by <b>section_yz</b>.</font></span></td>
[108]6967
6968
6969
6970    </tr>
6971
6972
6973 <tr>
6974
6975
6976 <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
6977
6978
6979
6980      </td>
6981
6982
6983 <td style="vertical-align: top;">R<br>
6984
6985
6986 </td>
6987
6988
6989
6990      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
6991
6992
6993 </td>
6994
6995
6996
6997      <td style="vertical-align: top;">No data output before
6998this interval has passed (in s).<br>
6999
7000
7001      <br>
7002
7003
7004This
[48]7005parameter causes that data output activities are starting not before
7006this interval
7007(counting from the beginning of the simulation, t=0) has passed. By
7008default, this
[5]7009applies for output of instantaneous 3d volume data, cross section data,
7010spectra and vertical profile data as well as for temporally averaged 2d
[108]7011and 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>
7012
7013
7014      <br>
7015
7016
7017      <span style="font-weight: bold;">Example:</span><br>
7018
7019
7020If
[48]7021the user has set <a href="#dt_data_output">dt_data_output</a>
7022= <span style="font-style: italic;">3600.0</span>
7023and <span style="font-weight: bold;">skip_time_data_output</span>
7024= <span style="font-style: italic;">1800.0</span>,
[108]7025then the first output will be done at t = 5400 s.<br>
7026
7027
7028 </td>
7029
7030
7031
7032    </tr>
7033
7034
7035 <tr>
7036
7037
7038      <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>
7039
7040
7041      <td style="vertical-align: top;">R</td>
7042
7043
7044      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>
7045
7046
7047data_output</a></span></td>
7048
7049
7050      <td style="vertical-align: top;">No output of temporally
7051averaged 2d/3d data before this interval has passed (in s).<br>
7052
7053
7054      <br>
7055
7056
7057This
[48]7058parameter causes that data output activities are starting not before
7059this interval
[108]7060(counting from the beginning of the simulation, t=0) has passed. <br>
7061
7062
7063      <br>
7064
7065
7066      <span style="font-weight: bold;">Example:</span><br>
7067
7068
7069If
[48]7070the user has set <a href="#dt_data_output_av">dt_data_output_av</a>
7071= <span style="font-style: italic;">3600.0</span>
7072and <span style="font-weight: bold;">skip_time_data_output_av</span>
7073= <span style="font-style: italic;">1800.0</span>,
[108]7074then the first output will be done at t = 5400 s.</td>
7075
7076
7077    </tr>
7078
7079
7080    <tr>
7081
7082
7083
7084      <td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
7085
7086
7087
7088      </td>
7089
7090
7091 <td style="vertical-align: top;">R<br>
7092
7093
7094 </td>
7095
7096
7097
7098      <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>
7099
7100
7101data_output</a></span>
7102      </td>
7103
7104
7105 <td style="vertical-align: top;">No output of
7106vertical profile data before this interval has passed (in s).<br>
7107
7108
7109      <br>
7110
7111
7112This
[48]7113parameter causes that data output activities are starting not before
7114this interval
[108]7115(counting from the beginning of the simulation, t=0) has passed. <br>
7116
7117
7118      <br>
7119
7120
7121      <span style="font-weight: bold;">Example:</span><br>
7122
7123
7124If
[48]7125the 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
[108]7126first output will be done at t = 5400 s. </td>
7127
7128
7129 </tr>
7130
7131
7132 <tr>
7133
7134
7135
7136      <td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
7137
7138
7139
7140      </td>
7141
7142
7143 <td style="vertical-align: top;">R<br>
7144
7145
7146 </td>
7147
7148
7149
7150      <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>
7151
7152
7153data_output</a></span>
7154      </td>
7155
7156
7157 <td style="vertical-align: top;">No output of
[48]7158instantaneous horizontal cross section data before this interval has
[108]7159passed (in s).<br>
7160
7161
7162      <br>
7163
7164
7165This
[48]7166parameter causes that data output activities are starting not before
7167this interval
[108]7168(counting from the beginning of the simulation, t=0) has passed. <br>
7169
7170
7171      <br>
7172
7173
7174      <span style="font-weight: bold;">Example:</span><br>
7175
7176
7177If
[48]7178the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a>
7179= <span style="font-style: italic;">3600.0</span>
7180and <span style="font-weight: bold;">skip_time_do2d_xy</span>
7181= <span style="font-style: italic;">1800.0</span>,
[108]7182then the first output will be done at t = 5400 s. </td>
7183
7184
7185 </tr>
7186
7187
7188
7189    <tr>
7190
7191
7192 <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
7193
7194
7195
7196      </td>
7197
7198
7199 <td style="vertical-align: top;">R<br>
7200
7201
7202 </td>
7203
7204
7205
7206      <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>
7207
7208
7209data_output</a></span>
7210      </td>
7211
7212
7213 <td style="vertical-align: top;">No output of
[48]7214instantaneous vertical (xz) cross section data before this interval has
[108]7215passed (in s).<br>
7216
7217
7218      <br>
7219
7220
7221This
[48]7222parameter causes that data output activities are starting not before
7223this interval
[108]7224(counting from the beginning of the simulation, t=0) has passed. <br>
7225
7226
7227      <br>
7228
7229
7230      <span style="font-weight: bold;">Example:</span><br>
7231
7232
7233If
[48]7234the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a>
7235= <span style="font-style: italic;">3600.0</span>
7236and <span style="font-weight: bold;">skip_time_do2d_xz</span>
7237= <span style="font-style: italic;">1800.0</span>,
[108]7238then the first output will be done at t = 5400 s. </td>
7239
7240
7241 </tr>
7242
7243
7244
7245    <tr>
7246
7247
7248 <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
7249
7250
7251
7252      </td>
7253
7254
7255 <td style="vertical-align: top;">R<br>
7256
7257
7258 </td>
7259
7260
7261
7262      <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>
7263
7264
7265data_output</a></span>
7266      </td>
7267
7268
7269 <td style="vertical-align: top;">No output of
[48]7270instantaneous vertical (yz) cross section data before this interval has
[108]7271passed (in s).<br>
7272
7273
7274      <br>
7275
7276
7277This
[48]7278parameter causes that data output activities are starting not before
7279this interval
[108]7280(counting from the beginning of the simulation, t=0) has passed. <br>
7281
7282
7283      <br>
7284
7285
7286      <span style="font-weight: bold;">Example:</span><br>
7287
7288
7289If
[48]7290the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a>
7291= <span style="font-style: italic;">3600.0</span>
7292and <span style="font-weight: bold;">skip_time_do2d_yz</span>
7293= <span style="font-style: italic;">1800.0</span>,
[108]7294then the first output will be done at t = 5400 s. </td>
7295
7296
7297 </tr>
7298
7299
7300
7301    <tr>
7302
7303
7304 <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
7305
7306
7307
7308      </td>
7309
7310
7311 <td style="vertical-align: top;">R<br>
7312
7313
7314 </td>
7315
7316
7317
7318      <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>
7319
7320
7321data_output</a></span>
7322      </td>
7323
7324
7325 <td style="vertical-align: top;">No output of
7326instantaneous 3d volume data before this interval has passed (in s).<br>
7327
7328
7329      <br>
7330
7331
7332This
[48]7333parameter causes that data output activities are starting not before
7334this interval
[108]7335(counting from the beginning of the simulation, t=0) has passed. <br>
7336
7337
7338      <br>
7339
7340
7341      <span style="font-weight: bold;">Example:</span><br>
7342
7343
7344If
[48]7345the 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
[108]7346first output will be done at t = 5400 s. </td>
7347
7348
7349 </tr>
7350
7351
7352
7353    <tr>
7354
7355
7356 <td style="vertical-align: top;"> 
7357     
7358     
7359      <p><a name="termination_time_needed"></a><b>termination_time</b>
7360      <br>
7361
7362
7363 <b>_needed</b></p>
7364
7365
7366 </td>
7367
7368
7369 <td style="vertical-align: top;">R<br>
7370
7371
7372 </td>
7373
7374
7375 <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br>
7376
7377
7378 </td>
7379
7380
7381
7382      <td style="vertical-align: top;"> 
7383     
7384     
7385      <p>CPU time
[48]7386needed for terminal actions at the end of a run in
[108]7387batch mode (in s).<br>
7388
7389
7390 </p>
7391
7392
7393 
7394     
7395     
7396      <p>If the environment
[48]7397variable <b>write_binary </b>is
[5]7398set <i>true</i> (see <a href="chapter_3.3.html">chapter
[48]73993.3</a>), PALM checks the remaining CPU time of the job after
7400each
[5]7401timestep. Time integration must not consume the CPU time completely,
7402since several actions still have to be carried out after time
7403integration has finished (e.g. writing of binary data for the restart
7404run, carrying out output commands, copying of local files to their
7405permanent destinations, etc.) which also takes some time. The maximum
7406possible time needed for these activities plus a reserve is to be given
[48]7407with the parameter <b>termination_time_needed</b>. Among
7408other things,
[5]7409it depends on
7410the number of grid points used. If its value is selected too small,
7411then the
7412respective job will be prematurely aborted by the queuing system, which
7413may result in a data loss and will possibly interrupt the job chain.<br>
[108]7414
7415
7416
7417      </p>
7418
7419
7420 
7421     
7422     
7423      <p>An abort happens in any way, if the environment
[48]7424variable <span style="font-weight: bold;">write_binary</span>
7425is not set to <span style="font-style: italic;">true</span>
7426and if moreover the job has
7427been assigned an insufficient CPU time by <b>mrun</b>
7428option <tt><tt>-t</tt></tt>. <i><br>
[108]7429
7430
7431
7432      </i> </p>
7433
7434
7435 
7436     
7437     
7438      <p><span style="font-weight: bold;">Note:</span><br>
7439
7440
7441
[48]7442On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of
7443PALM
[5]7444have also to be accounted for (e.g. for
[108]7445compilation and copying of input files).</p>
7446
7447
7448 </td>
7449
7450
7451 </tr>
7452
7453
7454
7455    <tr>
7456
7457
7458 <td style="vertical-align: top;"> 
7459     
7460     
7461      <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
7462      <br>
7463
7464
7465 <b>_parameters</b></p>
7466
7467
7468 </td>
7469
7470
7471 <td style="vertical-align: top;">L</td>
7472
7473
7474 <td style="vertical-align: top;"><i>.F.</i></td>
7475
7476
7477
7478      <td style="vertical-align: top;"> 
7479     
7480     
7481      <p>Additional
[48]7482plot of vertical profile data with <span style="font-weight: bold;">profil</span>
7483from preceding runs of the
[108]7484job chain.&nbsp; </p>
7485
7486
7487 
7488     
7489     
7490      <p>This parameter only applies
[48]7491for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
[108]7492= <span style="font-style: italic;">'profil'</span>.</p>
7493
7494
7495     
7496     
7497      <p>By
[48]7498default, plots of horizontally averaged vertical profiles
[5]7499(see <a href="#data_output_pr">data_output_pr</a>)
7500only contain profiles of data produced by the model
7501run. If profiles of prior times (i.e. data of preceding jobs of a
7502job chain) shall be plotted additionally (e.g. for comparison
[48]7503purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>.
7504must be
[108]7505set.<br>
7506
7507
7508 </p>
7509
7510
7511 
7512     
7513     
7514      <p>For further explanation see <a href="chapter_4.5.2.html">chapter
75154.5.2</a>.</p>
7516
7517
7518 </td>
7519
7520
7521 </tr>
7522
7523
7524 <tr>
7525
7526
7527 <td style="vertical-align: top;"> 
7528     
7529     
7530      <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
7531
7532
7533
7534      </td>
7535
7536
7537 <td style="vertical-align: top;">R</td>
7538
7539
7540
7541      <td style="vertical-align: top;"><i>zu(nzt+1) (model
7542top)</i></td>
7543
7544
7545 <td style="vertical-align: top;">
7546     
7547     
7548      <p>Height level up to which horizontally averaged profiles are to
[5]7549be
[48]7550plotted with <span style="font-weight: bold;">profil</span>
7551(in
[108]7552m).&nbsp; </p>
7553
7554
7555 
7556     
7557     
7558      <p>This parameter only applies for
[48]7559&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
[108]7560= <span style="font-style: italic;">'profil'</span>.</p>
7561
7562
7563     
7564     
7565      <p>It
[48]7566affects plots of horizontally averaged profiles
[5]7567(<a href="#data_output_pr">data_output_pr</a>)
7568when plotted with the plot software <span style="font-weight: bold;">profil</span>.
7569By default, profiles are plotted up to the top boundary. The height
[48]7570level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller
7571value.
7572Nevertheless, <span style="font-weight: bold;">all</span>
7573vertical
[5]7574grid points (0 &lt;= k &lt;= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p>
[108]7575
7576
7577
7578     
7579     
7580      <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>
[5]7581has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a>
[108]7582must be used.</p>
7583
7584
7585 </td>
7586
7587
7588 </tr>
7589
7590
7591 <tr>
7592
7593
7594 <td style="vertical-align: top;"> 
7595     
7596     
7597      <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
7598      <br>
7599
7600
7601 <b>_normalized</b></p>
7602
7603
7604 </td>
7605
7606
7607 <td style="vertical-align: top;">R</td>
7608
7609
7610 <td style="vertical-align: top;"><i>determined by plot</i>
7611      <br>
7612
7613
7614 <i>data</i> <br>
7615
7616
7617 </td>
7618
7619
7620 <td style="vertical-align: top;"> 
7621     
7622     
7623      <p>Normalized height
[48]7624level up to which horizontally averaged
[5]7625profiles are to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
[108]7626      </p>
7627
7628
7629 
7630     
7631     
7632      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
7633= <span style="font-style: italic;">'profil'</span>.</p>
7634
7635
7636     
7637     
7638      <p>It
[48]7639affects plots of horizontally averaged profiles
[5]7640(<a href="#data_output_pr">data_output_pr</a>)
7641when plotted with the plot software <span style="font-weight: bold;">profil</span>,
7642if a normalization for the vertical axis is selected
7643(see <a href="#cross_normalized_y">cross_normalized_y</a>).
7644If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b>
[48]7645= <i>1.5</i> means that all profiles up to the height
7646level of z =
[108]76471.5* z<sub>i </sub>are plotted.</p>
7648
7649
7650 </td>
7651
7652
7653 </tr>
7654
7655
7656
7657    <tr>
7658
7659
7660 <td style="vertical-align: top;"> 
7661     
7662     
7663      <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
7664
7665
7666
7667      </td>
7668
7669
7670 <td style="vertical-align: top;">R<br>
7671
7672
7673 </td>
7674
7675
7676
7677      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br>
7678
7679
7680 </td>
7681
7682
7683
7684      <td style="vertical-align: top;"> 
7685     
7686     
7687      <p>Height level
[48]7688up to which 2d cross sections are to be plotted
[5]7689with <span style="font-weight: bold;">iso2d</span>
[108]7690(in m).&nbsp; </p>
7691
7692
7693 
7694     
7695     
7696      <p>This parameter only applies for
[48]7697&nbsp;<a href="#data_output_format">data_output_format</a>
[108]7698= <span style="font-style: italic;">'iso2d'</span>.</p>
7699
7700
7701     
7702     
7703      <p>It
[48]7704affects plots of&nbsp; 2d vertical cross
[5]7705sections (<a href="#data_output">data_output</a>)
[48]7706when plotted with <span style="font-weight: bold;">iso2d</span>.
7707By
7708default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d
[108]7709      </b>the
[5]7710visualization within
[48]7711the plot can be limited to a certain height level (0 &lt;= z
7712&lt;= <b>z_max_do2d</b>).
7713Nevertheless, <span style="font-weight: bold;">all</span>
7714grid points
[5]7715of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>
7716or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
7717The level up to which the section is visualized can later be changed by
7718manually editing the
7719file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>
7720or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>
7721(the respective <span style="font-weight: bold;">iso2d</span>-parameter
7722is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p>
[108]7723
7724
7725
7726      </td>
7727
7728
7729 </tr>
7730
7731
7732 
7733 
7734 
7735  </tbody>
7736</table>
7737
7738
7739<br>
7740
7741
7742
7743<br>
7744
7745
7746<h3 style="line-height: 100%;"><a name="particle_parameters"></a>Particle
[5]7747parameters: </h3>
[108]7748
7749
7750
[102]7751<span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>NAMELIST group name: <span style="font-weight: bold;">particles_par<br>
[108]7752
7753
7754
7755</span>
7756<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
7757
7758
7759 <tbody>
7760
7761
7762    <tr>
7763
7764
7765
7766      <td style="vertical-align: top;"><font size="4"><b>Parameter
[61]7767name</b></font></td>
[108]7768
7769
7770
7771      <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
7772
7773
7774
7775      <td style="vertical-align: top;"> 
7776     
7777     
7778      <p><b><font size="4">Default</font></b> <br>
7779
7780
7781 <b><font size="4">value</font></b></p>
7782
7783
7784 </td>
7785
7786
7787
7788      <td style="vertical-align: top;"> 
7789     
7790     
7791      <p><font size="4"><b>Explanation</b></font></p>
7792
7793
7794
7795      </td>
7796
7797
7798 </tr>
7799
7800
7801 <tr>
7802
7803
7804 <td style="vertical-align: top;"> 
7805     
7806     
7807      <p><a name="dt_prel"></a><b>dt_prel</b></p>
7808
7809
7810
7811      </td>
7812
7813
7814 <td style="vertical-align: top;">R</td>
7815
7816
7817
7818      <td style="vertical-align: top;"><i>9999999.9</i></td>
7819
7820
7821
7822      <td style="vertical-align: top;"> 
7823     
7824     
7825      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
[5]7826interval at
[48]7827which particles are to be released <span lang="en-GB">from
7828a particle
7829source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;
[108]7830      </font> </p>
7831
7832
7833 
7834     
7835     
7836      <p><span lang="en-GB"><font face="Thorndale, serif">By default
[5]7837particles are released only at the beginning of a simulation
7838(t_init=0). The time of the first release (t_init) can be changed with
7839package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>.
[108]7840      </font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
[48]7841set with the package parameter <a href="#end_time_prel">end_time_prel</a>.
7842If <span style="font-weight: bold;">dt_prel</span>
7843has been set, additional
[5]7844releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>,
[48]7845t_init+2*<span style="font-weight: bold;">dt_prel</span>,
7846t_init+3*<span style="font-weight: bold;">dt_prel</span>,
7847etc.. Actual release times
7848may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see
7849e.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>
[108]7850
7851
7852
7853     
7854     
7855      <p><span lang="en-GB"><font face="Thorndale, serif"> The domain
[48]7856of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as
7857well as the distance of&nbsp; released particles
7858within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package
7859parameters </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>
[108]7860      <span lang="en-GB"><font face="Thorndale, serif">and
7861      </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
[48]7862default, one particle is released at all points defined by these
7863parameters. The package parameter <a href="#particles_per_point">particles_per_point</a>
7864can be used to start more than one particle per point.<br>
[108]7865
7866
7867
7868      </font></span></p>
7869
7870
7871 
7872     
7873     
7874      <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
[48]7875different 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">)
7876where each group may have a different source. All particles belonging
7877to one group have the same density ratio and the same radius. All other
7878particle features (e.g. location of the source) are
[108]7879identical for all groups of particles.</font></span></p>
7880
7881
7882Subgrid
[5]7883scale velocities can (optionally) be included for calculating the
7884particle advection, using the method of Weil et al. (2004, JAS, 61,
78852877-2887). This method is switched on by the package
[48]7886parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.
7887This also forces the Euler/upstream method to be used for time
7888advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>).
7889The minimum timestep during the sub-timesteps is controlled by package
[108]7890parameter <a href="#dt_min_part">dt_min_part</a>.
7891     
7892     
7893      <p><span lang="en-GB"><font face="Thorndale, serif">By
[5]7894default, particles are weightless and transported passively with the
7895resolved scale flow. Particles can be given a mass and thus an inertia
7896by assigning the
[48]7897package 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
7898non-zero value (it
[5]7899defines the ratio of the density of the fluid and the density of the
7900particles). 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">
7901must 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>
[108]7902
7903
7904
7905     
7906     
7907      <p><span lang="en-GB"><font face="Thorndale, serif">Boundary
[5]7908conditions for the particle transport can be defined with package
7909parameters </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>
[108]7910      <span lang="en-GB"><font face="Thorndale, serif">and
7911      </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>
7912
7913
7914      <span lang="en-GB"><font face="Thorndale, serif">Timeseries
[48]7915of 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>
[108]7916by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br>
7917
7918
7919      </font></span>
7920     
7921     
7922      <p>For
[48]7923analysis, additional output of
[5]7924particle
7925information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a>
7926(file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br>
[108]7927
7928
7929
7930      </p>
7931
7932
7933 
7934     
7935     
7936      <p><span style="font-family: thorndale,serif;">Statistical
[5]7937informations</span> (e.g. the total number of particles used, the
7938number of particles exchanged between the PEs, etc.) are output to the
7939local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>,
7940if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>.
[108]7941      <br>
7942
7943
7944 </p>
7945
7946
7947 
7948     
7949     
7950      <p><span lang="en-GB"><font face="Thorndale, serif">If a job
[5]7951chain is to be carried out, particle
[48]7952informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
7953location of
[5]7954all
7955particles at the end of the
7956run) is output to
[48]7957the 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>,
[108]7958      <span lang="en-GB"><font face="Thorndale, serif">which
[48]7959must be saved at the
7960end of the run <tt><span lang="en-GB"></span></tt>and
7961given as an
[5]7962input file to the restart run
7963under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>
[48]7964u<span lang="en-GB"><font face="Thorndale, serif">sing
7965respective file
[5]7966connection statements in the <span style="font-weight: bold;">mrun</span>
[108]7967configuration file. </font></span> <span lang="en-GB"></span></p>
7968
7969
7970     
7971     
7972      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
[48]7973particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by
7974the package
7975parameter </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">.
7976For visualization
[5]7977purposes particles can be given a
7978diameter by the parameter <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a>
7979(this diameter only affects the visualization). All particles have the
7980same size. Alternatively, particles can be given an individual size and
[48]7981a </span>color <span lang="en-GB">by modifying the
7982user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">.
7983Particles can pull a
7984&ldquo;tail&rdquo; behind themselves to improve their
7985visualization.
[108]7986This 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>
7987
7988
7989 <span lang="en-GB"></span>
7990     
7991     
7992      <p><b>So far, the
[48]7993particle transport realized in PALM does only
[5]7994work
[108]7995duly in case of a constant vertical grid spacing!</b></p>
7996
7997
7998 </td>
7999
8000
8001
8002    </tr>
8003
8004
8005 <tr>
8006
8007
8008 <td style="vertical-align: top;">
8009     
8010     
8011      <p><a name="bc_par_b"></a><b>bc_par_b</b></p>
8012
8013
8014
8015      </td>
8016
8017
8018 <td style="vertical-align: top;">C*15</td>
8019
8020
8021
8022      <td style="vertical-align: top;"><i>&acute;reflect&acute;</i></td>
8023
8024
8025
8026      <td style="vertical-align: top;"> 
8027     
8028     
8029      <p>Bottom
8030boundary condition for particle transport. </p>
8031
8032
8033 
8034     
8035     
8036      <p>By
[48]8037default, particles are reflected at the bottom boundary.
[5]8038Alternatively, a particle absorption can set by <b>bc_par_b</b>
[108]8039= <i>&acute;absorb&acute;</i>.</p>
8040
8041
8042 </td>
8043
8044
8045
8046    </tr>
8047
8048
8049 <tr>
8050
8051
8052 <td style="vertical-align: top;">
8053     
8054     
8055      <p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
8056
8057
8058
8059      </td>
8060
8061
8062 <td style="vertical-align: top;">C*15</td>
8063
8064
8065
8066      <td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
8067
8068
8069
8070      <td style="vertical-align: top;"> 
8071     
8072     
8073      <p>Lateral
[48]8074boundary condition (x-direction) for particle
[108]8075transport. </p>
8076
8077
8078 
8079     
8080     
8081      <p>By default, cyclic boundary conditions
[48]8082are used along x.
[5]8083Alternatively, reflection (<b>bc_par_lr</b>
[48]8084= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_lr</b>
8085= <i>&acute;absorb&acute;</i>)
[108]8086can be set. <br>
8087
8088
8089 </p>
8090
8091
8092 
8093     
8094     
8095      <p>This lateral boundary
[48]8096conditions should correspond to the
[108]8097lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p>
8098
8099
8100 </td>
8101
8102
8103
8104    </tr>
8105
8106
8107 <tr>
8108
8109
8110 <td style="vertical-align: top;">
8111     
8112     
8113      <p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
8114
8115
8116
8117      </td>
8118
8119
8120 <td style="vertical-align: top;">C*15</td>
8121
8122
8123
8124      <td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
8125
8126
8127
8128      <td style="vertical-align: top;"> 
8129     
8130     
8131      <p>Lateral
[48]8132boundary condition (y-direction) for particle
[108]8133transport. </p>
8134
8135
8136 
8137     
8138     
8139      <p>By default, cyclic boundary conditions
[48]8140are used along y.
[5]8141Alternatively, reflection (<b>bc_par_ns</b>
[48]8142= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_ns</b>
8143= <i>&acute;absorb&acute;</i>)
[108]8144can be set.<br>
8145
8146
8147 </p>
8148
8149
8150
[5]8151This lateral boundary conditions should correspond to the lateral
[108]8152boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td>
8153
8154
8155 </tr>
8156
8157
8158
8159    <tr>
8160
8161
8162 <td style="vertical-align: top;"> 
8163     
8164     
8165      <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
8166
8167
8168
8169      </td>
8170
8171
8172 <td style="vertical-align: top;">C*15</td>
8173
8174
8175
8176      <td style="vertical-align: top;"><i>&acute;absorb&acute;</i></td>
8177
8178
8179
8180      <td style="vertical-align: top;"> 
8181     
8182     
8183      <p>Top boundary
8184condition for particle transport. </p>
8185
8186
8187 
8188     
8189     
8190      <p>By default,
[48]8191particles are absorbed at the top boundary.
[5]8192Alternatively, a reflection condition can be set by <b>bc_par_t</b>
[108]8193= <i>&acute;reflect&acute;</i>.</p>
8194
8195
8196 </td>
8197
8198
8199
8200    </tr>
8201
8202
8203 <tr>
8204
8205
8206 <td style="vertical-align: top;">
8207     
8208     
8209      <p><a name="density_ratio"></a><b>density_ratio</b></p>
8210
8211
8212
8213      </td>
8214
8215
8216 <td style="vertical-align: top;">R (10)</td>
8217
8218
8219
8220      <td style="vertical-align: top;"> 
8221     
8222     
8223      <p><i>0.0, 9</i>
8224*<br>
8225
8226
8227 <i>9999999.9</i></p>
8228
8229
8230 </td>
8231
8232
8233 <td style="vertical-align: top;"> 
8234     
8235     
8236      <p>Ratio of the density
[48]8237of the fluid and the density of the
[108]8238particles. </p>
8239
8240
8241 
8242     
8243     
8244      <p>With the default value<i> </i>the
[5]8245particles are weightless and transported passively with the resolved
8246scale flow.
[48]8247In case of <span style="font-weight: bold;">density_ratio</span>
8248/=
[5]82490.0 particles have a mass and hence inertia so that their velocity
8250deviates more or less from the velocity of the surrounding flow.
8251Particle velocity is calculated analytically and depends on (besides
8252the density ratio and the current velocity difference between particles
8253and surrounding fluid) the
8254particle radius which is determined via <a href="#radius">radius</a>
8255as well as on the molecular viscosity (assumed as 1.461E-5 m<sup>2</sup>/s).
[108]8256      </p>
8257
8258
8259 
8260     
8261     
8262      <p>If <b>density_ratio</b> = <i>1.0</i>,
[48]8263the particle density
[5]8264corresponds to the density of the surrounding fluid and the particles
8265do not feel any buoyancy. Otherwise, particles will be accelerated
8266upwards (<b>density_ratio</b> &gt; <i>1.0</i>)
8267or downwards (<b>density_ratio</b> &lt; <i>1.0</i>).<br>
[108]8268
8269
8270
8271      </p>
8272
8273
8274 
8275     
8276     
8277      <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
[48]8278each group can be assigned a different value. If the number of values
8279given for <span style="font-weight: bold;">density_ratio</span>
8280is less than the number of
[5]8281groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
8282then the last assigned value is used for all remaining groups. This
[48]8283means that by default the particle density ratio for all groups will be
[108]8284      <span style="font-style: italic;">0.0</span>.</p>
8285
8286
8287
8288      </td>
8289
8290
8291 </tr>
8292
8293
8294 <tr>
8295
8296
8297      <td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td>
8298
8299
8300      <td align="left" valign="top">R</td>
8301
8302
8303      <td align="left" valign="top"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
8304
8305
8306output</a></i></td>
8307
8308
8309      <td align="left" valign="top">
8310     
8311     
8312      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
[48]8313interval</font> at which time series data of particle quantities
8314shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
[108]8315
8316
8317
8318      <span lang="en-GB"><font face="Thorndale">If
[48]8319particle advection is switched on (see</font></span><font><span style="font-family: thorndale;"> <a href="#dt_prel">dt_prel</a>)
8320this parameter can be used to assign
[5]8321th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
[48]8322interval at which time series of particle quantities shall be output.
[108]8323Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br>
8324
8325
8326      <br>
8327
8328
8329The
[5]8330following list gives a short description of the&nbsp;quantities
8331available. Most quantities are averages over all particles. The
8332quantity name given in the first column is identical to the respective
[48]8333name of the variable on the NetCDF file (see section <a href="chapter_4.5.1.html">4.5.1</a> for a general
[108]8334description of the NetCDF files).<br>
8335
8336
8337      <br>
8338
8339
8340In case of using
[48]8341more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
[5]8342seperate time series are output for each of the groups. The long names
8343of the variables in the NetCDF file containing the respective
[48]8344timeseries 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
[108]8345group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
8346
8347
8348&nbsp;</font></span>
8349     
8350     
8351      <table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2">
8352
8353
8354        <tbody>
8355
8356
8357          <tr>
8358
8359
8360            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td>
8361
8362
8363            <td align="undefined" valign="undefined">total number of
8364particles</td>
8365
8366
8367          </tr>
8368
8369
8370          <tr>
8371
8372
8373            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td>
8374
8375
8376            <td align="undefined" valign="undefined">particle
8377x-coordinate&nbsp;with respect to the particle origin (in m)</td>
8378
8379
8380          </tr>
8381
8382
8383          <tr>
8384
8385
8386            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td>
8387
8388
8389            <td align="undefined" valign="undefined">particle
8390y-coordinate&nbsp;with respect to the particle origin (in m)</td>
8391
8392
8393          </tr>
8394
8395
8396          <tr>
8397
8398
8399            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td>
8400
8401
8402            <td align="undefined" valign="undefined">particle
8403z-coordinate&nbsp;with respect to the particle origin (in m)</td>
8404
8405
8406          </tr>
8407
8408
8409          <tr>
8410
8411
8412            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td>
8413
8414
8415            <td align="undefined" valign="undefined">absolute
8416particle z-coordinate (in m)</td>
8417
8418
8419          </tr>
8420
8421
8422          <tr>
8423
8424
8425            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td>
8426
8427
8428            <td align="undefined" valign="undefined">u particle
8429velocity component (in m/s)</td>
8430
8431
8432          </tr>
8433
8434
8435          <tr>
8436
8437
8438            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td>
8439
8440
8441            <td align="undefined" valign="undefined">v particle
8442velocity component (in m/s)</td>
8443
8444
8445          </tr>
8446
8447
8448          <tr>
8449
8450
8451            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td>
8452
8453
8454            <td align="undefined" valign="undefined">w particle
8455velocity component (in m/s)</td>
8456
8457
8458          </tr>
8459
8460
8461          <tr>
8462
8463
8464            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td>
8465
8466
8467            <td align="undefined" valign="undefined">subgrid-scale u
8468particle velocity component (in m/s)</td>
8469
8470
8471          </tr>
8472
8473
8474          <tr>
8475
8476
8477            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td>
8478
8479
8480            <td align="undefined" valign="undefined">subgrid-scale v
8481particle velocity component (in m/s)</td>
8482
8483
8484          </tr>
8485
8486
8487          <tr>
8488
8489
8490            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td>
8491
8492
8493            <td align="undefined" valign="undefined">subgrid-scale w
8494particle velocity component (in m/s)</td>
8495
8496
8497          </tr>
8498
8499
8500          <tr>
8501
8502
8503            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td>
8504
8505
8506            <td align="undefined" valign="undefined">total number of
8507upward moving particles</td>
8508
8509
8510          </tr>
8511
8512
8513          <tr>
8514
8515
8516            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td>
8517
8518
8519            <td align="undefined" valign="undefined">vertical
8520velocity of the upward moving particles (in m/s)</td>
8521
8522
8523          </tr>
8524
8525
8526          <tr>
8527
8528
8529            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td>
8530
8531
8532            <td align="undefined" valign="undefined">vertical
8533velocity of the downward moving particles (in m/s)</td>
8534
8535
8536          </tr>
8537
8538
8539          <tr>
8540
8541
8542            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td>
8543
8544
8545            <td align="undefined" valign="undefined">maximum number
8546of particles in a subdomain (=tnpt for non-parallel runs)</td>
8547
8548
8549          </tr>
8550
8551
8552          <tr>
8553
8554
8555            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td>
8556
8557
8558            <td align="undefined" valign="undefined">minimum number
8559of particles in a subdomain (=tnpt for non-parallel runs)</td>
8560
8561
8562          </tr>
8563
8564
8565          <tr>
8566
8567
8568            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td>
8569
8570
8571            <td align="undefined" valign="undefined">variance of the
8572particle x-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td>
8573
8574
8575          </tr>
8576
8577
8578          <tr>
8579
8580
8581            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td>
8582
8583
8584            <td align="undefined" valign="undefined">variance of the
8585particle y-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td>
8586
8587
8588          </tr>
8589
8590
8591          <tr>
8592
8593
8594            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td>
8595
8596
8597            <td align="undefined" valign="undefined">variance of the
8598particle z-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td>
8599
8600
8601          </tr>
8602
8603
8604          <tr>
8605
8606
8607            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td>
8608
8609
8610            <td align="undefined" valign="undefined">variance of the
8611u 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>
8612
8613
8614          </tr>
8615
8616
8617          <tr>
8618
8619
8620            <td align="undefined" valign="undefined">v*2</td>
8621
8622
8623            <td align="undefined" valign="undefined">variance of the
8624v 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>
8625
8626
8627          </tr>
8628
8629
8630          <tr>
8631
8632
8633            <td align="undefined" valign="undefined">w*2</td>
8634
8635
8636            <td align="undefined" valign="undefined">variance of the
8637w 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>
8638
8639
8640          </tr>
8641
8642
8643          <tr>
8644
8645
8646            <td align="undefined" valign="undefined">u"2</td>
8647
8648
8649            <td align="undefined" valign="undefined">variance of the
8650subgrid-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>
8651
8652
8653          </tr>
8654
8655
8656          <tr>
8657
8658
8659            <td align="undefined" valign="undefined">v"2</td>
8660
8661
8662            <td align="undefined" valign="undefined">variance of the
8663subgrid-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>
8664
8665
8666          </tr>
8667
8668
8669          <tr>
8670
8671
8672            <td align="undefined" valign="undefined">w"2</td>
8673
8674
8675            <td align="undefined" valign="undefined">variance of the
8676subgrid-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>
8677
8678
8679          </tr>
8680
8681
8682          <tr>
8683
8684
8685            <td align="undefined" valign="undefined">npt*2</td>
8686
8687
8688            <td align="undefined" valign="undefined">variance of the
[48]8689number of particles with respect to the average number of particles per
[108]8690subdomain</td>
8691
8692
8693          </tr>
8694
8695
8696       
8697       
8698        </tbody>
8699     
8700     
8701      </table>
8702
8703
8704      <span lang="en-GB"></span><span lang="en-GB"></span></td>
8705
8706
8707    </tr>
8708
8709
8710    <tr>
8711
8712
8713      <td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td>
8714
8715
8716      <td align="left" valign="top">R</td>
8717
8718
8719      <td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td>
8720
8721
8722      <td align="left" valign="top">Minimum value for the
8723particle timestep when SGS velocities are used (in s).<br>
8724
8725
8726      <br>
8727
8728
8729For
8730a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td>
8731
8732
8733    </tr>
8734
8735
[116]8736    <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="dt_sort_particles"></a>dt_sort_particles</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td><td style="vertical-align: top;">Temporal interval for sorting particles (in s).<br><br>By
8737default, particles are sorted in memory in a way that their order
8738follows the order in which the gridpoint values are stored. This may
8739improve cache coherence in case of larger numbers of particles and
8740gridpoints. However, since the sorting itself is time consuming and
8741since the requirement of sorting depends on the strength of mixing in
8742the flow, performance can be improved if the sorting is applied only
8743after certain time intervals. The proper length of this interval <span style="font-weight: bold;">dt_sort_particles</span> must be determined empirically by carrying out test runs with different intervals. Check file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> to find the value of <span style="font-weight: bold;">dt_sort_particles</span> which gives the best performance.<br><br><span style="font-weight: bold;">Note:</span><br>In case of <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.T.</span>, any given non-zero value of <span style="font-weight: bold;">dt_sort_particles</span> will be reset to zero and a corresponding warning message will appear in the job protocol.</td></tr><tr>
[108]8744
8745
8746
8747      <td style="vertical-align: top;"> 
8748     
8749     
8750      <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b>
8751      <b>data</b></p>
8752
8753
8754 </td>
8755
8756
8757 <td style="vertical-align: top;">R<br>
8758
8759
8760 </td>
8761
8762
8763 <td style="vertical-align: top;"><i>9999999.9</i></td>
8764
8765
8766
8767      <td style="vertical-align: top;"> 
8768     
8769     
8770      <p>Temporal
8771interval for output of particle data (in s). </p>
8772
8773
8774 
8775     
8776     
8777      <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
[5]8778parameter can be used to
8779assign the temporal interval at which particle data shall be output.</font></span>
8780Data are output to
8781the local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>.
[108]8782      <span style="font-family: mon;">See the file description
[48]8783for more
[108]8784details about its format</span>. </p>
8785
8786
8787 
8788     
8789     
8790      <p>By
8791default, no particle data are output.</p>
8792
8793
8794 </td>
8795
8796
8797 </tr>
8798
8799
8800
8801    <tr>
8802
8803
8804 <td style="vertical-align: top;"> 
8805     
8806     
8807      <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p>
8808
8809
8810
8811      </td>
8812
8813
8814 <td style="vertical-align: top;">R<br>
8815
8816
8817 </td>
8818
8819
8820
8821      <td style="vertical-align: top;">0.2 * dx<br>
8822
8823
8824 </td>
8825
8826
8827
8828      <td style="vertical-align: top;"> 
8829     
8830     
8831      <p>Diameter that
[48]8832the particles is given in visualizations with
8833the <span style="font-weight: bold;">dvrp</span>
8834software (in
[108]8835m).&nbsp; </p>
8836
8837
8838 
8839     
8840     
8841      <p>In case that particles are
[48]8842visualized with the <span style="font-weight: bold;">dvrp</span>
8843software (see <a href="chapter_4.5.7.html">chapter
88444.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>.
8845All
[108]8846particles are displayed with this same size.<br>
8847
8848
8849 </p>
8850
8851
8852 
8853     
8854     
8855      <p>Alternatively,
[48]8856the particle diameters can be set with the
[5]8857user-interface in routine <span style="font-family: monospace;">user_init_particles</span>
8858(at the beginning of the simulation) and/or can be redefined after each
8859timestep in routine <tt>user<font style="font-size: 11pt;" size="2">_particle_attributes</font></tt>
8860(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>
[108]8861
8862
8863
8864     
8865     
8866      <p><b>Note:</b> This parameter determines exclusively
[48]8867the size
[5]8868under which particles appear in the <span style="font-weight: bold;">dvrp</span>
[48]8869visualization. The flow relevant particle radius is determined via the
8870particle package parameter <a href="#radius">radius</a>!</p>
[108]8871
8872
8873
8874      </td>
8875
8876
8877 </tr>
8878
8879
8880 <tr>
8881
8882
8883      <td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td>
8884
8885
8886      <td align="left" valign="top">R</td>
8887
8888
8889      <td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td>
8890
8891
8892      <td align="left" valign="top">Time of the last release of
8893particles (in s).<br>
8894
8895
8896      <br>
8897
8898
8899See also <a href="#particle_advection_start">particle_advection_start</a>.</td>
8900
8901
8902    </tr>
8903
8904
8905    <tr>
8906
8907
8908
8909      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td>
8910
8911
8912
8913      <td style="vertical-align: top;">R<br>
8914
8915
8916 </td>
8917
8918
8919 <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br>
8920
8921
8922 </td>
8923
8924
8925
8926      <td style="vertical-align: top;">Factor to define the real
8927number of initial droplets in a grid box.<br>
8928
8929
8930 <br>
8931
8932
8933
[5]8934In case of explicitly simulating cloud droplets (see <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>),
8935the real number of initial droplets in a grid box is equal to the
8936initial number of droplets in this box (defined by the particle source
8937parameters <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>
[108]8938      <span lang="en-GB"><font face="Thorndale, serif">and
8939      </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>)
[48]8940times the <span style="font-weight: bold;">initial_weighting_factor</span>.</td>
[108]8941
8942
8943
8944    </tr>
8945
8946
8947    <tr>
8948
8949
8950 <td style="vertical-align: top;"> 
8951     
8952     
8953      <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b>
8954      <br>
8955
8956
8957 <b>particles</b></p>
8958
8959
8960 </td>
8961
8962
8963 <td style="vertical-align: top;">I</td>
8964
8965
8966 <td style="vertical-align: top;"><i>1000</i></td>
8967
8968
8969
8970      <td style="vertical-align: top;"> 
8971     
8972     
8973      <p>Maximum number
8974of particles (on a PE).&nbsp; </p>
8975
8976
8977 
8978     
8979     
8980      <p>This parameter
[48]8981allows to set the number of particles for which
[5]8982memory must be allocated at the beginning of the run.
8983If this memory becomes insufficient during the run, due to the
8984release of further particles (see <a href="#dt_prel">dt_prel</a>),
[108]8985then more memory is automatically allocated.<br>
8986
8987
8988 </p>
8989
8990
8991
[5]8992For runs on several processors, <span style="font-weight: bold;">maximum_number_of_particles</span>
8993defines
8994the maximum number on each PE. This number must be larger than the
8995maximum number of particles initially released in a subdomain.</td>
[108]8996
8997
8998
8999    </tr>
9000
9001
9002 <tr>
9003
9004
9005 <td style="vertical-align: top;">
9006     
9007     
9008      <p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b>
9009      <br>
9010
9011
9012 <b>tailpoints</b></p>
9013
9014
9015 </td>
9016
9017
9018 <td style="vertical-align: top;">I</td>
9019
9020
9021 <td style="vertical-align: top;"><i>100</i></td>
9022
9023
9024
9025      <td style="vertical-align: top;"> 
9026     
9027     
9028      <p>Maximum number
[48]9029of tailpoints that a particle tail can
[108]9030have.&nbsp; </p>
9031
9032
9033 
9034     
9035     
9036      <p>&nbsp;<b>maximum_number_of_tailpoints</b>
[5]9037sets the number of descrete points the tail consists of. A new point is
9038added to the particle tails after each time step. If the maximum number
9039of tail
9040points is reached after the corresponding number of timesteps, the
9041oldest respective tail points is deleted within the following
[108]9042timestep.&nbsp; </p>
9043
9044
9045 
9046     
9047     
9048      <p>All particle tails have the
[48]9049same number of points. The maximum
[5]9050length of
9051these
9052tails is determined by the value of <b>maximum_number_of_tailpoints</b>
9053and by the minimum distance between each of the adjoining
9054tailpoints,&nbsp; which can be set by <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.
9055Additionally, it can be determined that the temporal displacement
9056between the current position of the particle and the oldest point of
9057the tail may become not larger than a value to be assigned by <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>.</p>
[108]9058
9059
9060
9061      </td>
9062
9063
9064 </tr>
9065
9066
9067 <tr>
9068
9069
9070 <td style="vertical-align: top;"> 
9071     
9072     
9073      <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b>
9074      <br>
9075
9076
9077 <b>age</b></p>
9078
9079
9080 </td>
9081
9082
9083 <td style="vertical-align: top;">R</td>
9084
9085
9086 <td style="vertical-align: top;">100000.0</td>
9087
9088
9089 <td style="vertical-align: top;"> 
9090     
9091     
9092      <p>Maximum age that the
[48]9093end point of a particle tail is allowed to have (in s).&nbsp; </p>
[108]9094
9095
9096
9097     
9098     
9099      <p>If the temporal displacement between the oldest point of a
[5]9100particle tail and the current position of the particle becomes larger
[48]9101than the value given by <b>maximum_tailpoint_age</b>, this
9102oldest
[5]9103point (which defines the end of the tail) is
9104removed. If this time is so small that the number of points defining
9105the particle tail do not exceed the value given by <b>maximum_number_of_tailpoints</b>,
9106then the length the particle tails is a measure for the distance the
9107particle travelled along during the time interval defined via <b>maximum_tailpoint_age</b>,
9108i.e. for the
9109particle velocity. Fast particles will have long tails, slow particles
9110shorter ones (note: this will not neccessarily hold if <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>
[108]9111= <i>0.0</i>).</p>
9112
9113
9114 </td>
9115
9116
9117 </tr>
9118
9119
9120 <tr>
9121
9122
9123
9124      <td style="vertical-align: top;"> 
9125     
9126     
9127      <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</b></p>
9128
9129
9130
9131      </td>
9132
9133
9134 <td style="vertical-align: top;">R</td>
9135
9136
9137
9138      <td style="vertical-align: top;"><i>0.0</i></td>
9139
9140
9141
9142      <td style="vertical-align: top;"> 
9143     
9144     
9145      <p>Minimum
[48]9146distance allowed between two adjacent points of a
[108]9147particle tail (in m).&nbsp; </p>
9148
9149
9150 
9151     
9152     
9153      <p>In case of <b>minimum_tailpoint_distance</b>
[48]9154&gt; <i>0.0 </i>the
[5]9155particle tail is extended by a new point only if the distance between
9156its current position and the most recent tail point exceed the
9157distance given via <b>minimum_tailpoint_distance</b>.<br>
[108]9158
9159
9160
9161      </p>
9162
9163
9164 
9165     
9166     
9167      <p>If the length of the particle tails shall be
[48]9168proportional to
[5]9169the respective particle velocity, the parameter <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>
[108]9170must also be set appropriately. </p>
9171
9172
9173 <b>Note:</b><br>
9174
9175
9176
[5]9177A suitable choice of <b>minimum_tailpoint_distance</b>
[48]9178&gt; <i>0.0</i> is recommended, because then the tail
9179coordinates of
[5]9180slowly moving particles require less memory and can also be drawn
9181faster. The upper limit of <b>minimum_tailpoint_distance</b>
9182should be chosen in a way that the visualized particle
9183tails still appear as smooth lines. Example: with a model domain of
91841000 m and a monitor resolution of 1280 * 1024 pixels it
[48]9185should be sufficient to set <b>minimum_tailpoint_distance</b>
9186= <i>5.0</i>
[108]9187(m). </td>
9188
9189
9190 </tr>
9191
9192
9193 <tr>
9194
9195
9196 <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br>
9197
9198
9199
9200      </td>
9201
9202
9203 <td style="vertical-align: top;">I<br>
9204
9205
9206 </td>
9207
9208
9209
9210      <td style="vertical-align: top;">1<br>
9211
9212
9213 </td>
9214
9215
9216 <td style="vertical-align: top;">Number of particle groups to be
9217used.<br>
9218
9219
9220 <br>
9221
9222
9223
[48]9224Each particle group can be assigned its own source region (see <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
[108]9225      <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>
9226
9227
9228      <br>
9229
9230
9231If
[48]9232less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
[5]9233etc. than the number of particle groups, then the last value is used
9234for the remaining values (or the default value, if the user did not set
[108]9235the parameter).<br>
9236
9237
9238 <br>
9239
9240
9241
9242The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br>
9243
9244
9245 </td>
9246
9247
9248
9249    </tr>
9250
9251
9252    <tr>
9253
9254
9255      <td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td>
9256
9257
9258      <td align="left" valign="top">I</td>
9259
9260
9261      <td align="left" valign="top">1</td>
9262
9263
9264      <td align="left" valign="top">Number of particles to be
9265started per point.<br>
9266
9267
9268      <br>
9269
9270
9271By default, one particle is
[48]9272started 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
9273parameters </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>
[108]9274      <span lang="en-GB"><font face="Thorndale, serif">and
9275      </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>
9276
9277
9278    </tr>
9279
9280
9281    <tr>
9282
9283
9284 <td style="vertical-align: top;"> 
9285     
9286     
9287      <p><a name="particle_advection_start"></a><b>particle_advection_</b>
9288      <br>
9289
9290
9291 <b>start</b></p>
9292
9293
9294 </td>
9295
9296
9297 <td style="vertical-align: top;">R </td>
9298
9299
9300 <td style="vertical-align: top;">0.0 </td>
9301
9302
9303 <td style="vertical-align: top;"> 
9304     
9305     
9306      <p>Time of the first
9307release of particles (in s). </p>
9308
9309
9310 
9311     
9312     
9313      <p>If particles are not
[48]9314to be released at the beginning of the
[5]9315run, the release time can be set via <b>particle_advection_start</b>.<br>
[108]9316
9317
9318
[5]9319If particle transport is switched on in a restart run, then <a href="#read_particles_from_restartfile">read_particles_from_restartfile</a>
[48]9320= <span style="font-style: italic;">.F.</span> is
[108]9321also required.</p>
9322
9323
9324     
9325     
9326      <p>See also <a href="#end_time_prel">end_time_prel</a>.
9327      </p>
9328
9329
9330 </td>
9331
9332
9333 </tr>
9334
9335
9336 <tr>
9337
9338
9339 <td style="vertical-align: top;"> 
9340     
9341     
9342      <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p>
9343
9344
9345
9346      </td>
9347
9348
9349 <td style="vertical-align: top;">R </td>
9350
9351
9352
9353      <td style="vertical-align: top;"><i>9999999.9</i>
9354      </td>
9355
9356
9357 <td style="vertical-align: top;"> 
9358     
9359     
9360      <p>Maximum
9361allowed age of particles (in s).&nbsp; </p>
9362
9363
9364 
9365     
9366     
9367      <p>If the
[48]9368age of a particle exceeds the time set by <b>particle_maximum_age</b>,
[108]9369the particle as well as its tail is deleted.</p>
9370
9371
9372 </td>
9373
9374
9375 </tr>
9376
9377
9378
9379    <tr>
9380
9381
9382 <td style="vertical-align: top;"> 
9383     
9384     
9385      <p><a name="pdx"></a><b>pdx</b></p>
9386
9387
9388 </td>
9389
9390
9391
9392      <td style="vertical-align: top;">R (10)<br>
9393
9394
9395 </td>
9396
9397
9398
9399      <td style="vertical-align: top;"><i>10 * dx</i>
9400      </td>
9401
9402
9403 <td style="vertical-align: top;"> 
9404     
9405     
9406      <p>Distance
[48]9407along x between particles within a particle source
[108]9408(in m).&nbsp; </p>
9409
9410
9411 
9412     
9413     
9414      <p>If the particle source shall be
[48]9415confined to one grid point,
9416the distances given by <span style="font-weight: bold;">pdx</span>,
[108]9417      <a href="#pdy">pdy</a>
[5]9418and <a href="#pdz">pdz</a>
[48]9419must be set larger than the respective domain size or <a href="#psl">psl</a>
9420= <a href="#psr">psr</a> has to be set
9421alternatively.<br>
[108]9422
9423
9424
9425      </p>
9426
9427
9428 
9429     
9430     
9431      <p><span style="font-weight: bold;">pdx</span>
[48]9432can be assigned a different value for each particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>).<br>
[108]9433
9434
9435
9436      </p>
9437
9438
9439 </td>
9440
9441
9442 </tr>
9443
9444
9445 <tr>
9446
9447
9448 <td style="vertical-align: top;"> 
9449     
9450     
9451      <p><a name="pdy"></a><b>pdy</b></p>
9452
9453
9454
9455      </td>
9456
9457
9458 <td style="vertical-align: top;">R (10)<br>
9459
9460
9461
9462      </td>
9463
9464
9465 <td style="vertical-align: top;"><i>10
9466* dy</i> </td>
9467
9468
9469 <td style="vertical-align: top;">Distance
[48]9470along y between
[5]9471particles within a
[108]9472particle source (in m).&nbsp; </td>
9473
9474
9475 </tr>
9476
9477
9478 <tr>
9479
9480
9481
9482      <td style="vertical-align: top;"> 
9483     
9484     
9485      <p><a name="pdz"></a><b>pdz</b></p>
9486
9487
9488 </td>
9489
9490
9491
9492      <td style="vertical-align: top;">R (10)<br>
9493
9494
9495
9496      </td>
9497
9498
9499 <td style="vertical-align: top;"><i>10
9500* ( zu(2) - zu(1) )</i> </td>
9501
9502
9503 <td style="vertical-align: top;">Distance along z between
[5]9504particles within a particle source
[108]9505(in m). </td>
9506
9507
9508 </tr>
9509
9510
9511 <tr>
9512
9513
9514 <td style="vertical-align: top;"> 
9515     
9516     
9517      <p><a name="psb"></a><b>psb</b></p>
9518
9519
9520
9521      </td>
9522
9523
9524 <td style="vertical-align: top;">R (10)<br>
9525
9526
9527
9528      </td>
9529
9530
9531 <td style="vertical-align: top;"><i>10&nbsp;
9532* zu(nz/2)</i> </td>
9533
9534
9535 <td style="vertical-align: top;">Bottom
[48]9536edge of a particle
[108]9537source (in m). </td>
9538
9539
9540 </tr>
9541
9542
9543 <tr>
9544
9545
9546 <td style="vertical-align: top;"> 
9547     
9548     
9549      <p><a name="psl"></a><b>psl</b></p>
9550
9551
9552
9553      </td>
9554
9555
9556 <td style="vertical-align: top;">R (10)<br>
9557
9558
9559
9560      </td>
9561
9562
9563 <td style="vertical-align: top;"><i>10
9564* 0.0</i> </td>
9565
9566
9567 <td style="vertical-align: top;">Left
[48]9568edge of a particle source
[108]9569(in m). </td>
9570
9571
9572 </tr>
9573
9574
9575 <tr>
9576
9577
9578 <td style="vertical-align: top;"> 
9579     
9580     
9581      <p><a name="psn"></a><b>psn</b></p>
9582
9583
9584
9585      </td>
9586
9587
9588 <td style="vertical-align: top;">R (10)<br>
9589
9590
9591
9592      </td>
9593
9594
9595 <td style="vertical-align: top;"><i>10
9596* (ny * dy)</i> </td>
9597
9598
9599 <td style="vertical-align: top;">Rear
[48]9600(&ldquo;north&rdquo;) edge of a
[108]9601particle source (in m). </td>
9602
9603
9604 </tr>
9605
9606
9607 <tr>
9608
9609
9610 <td style="vertical-align: top;"> 
9611     
9612     
9613      <p><a name="psr"></a><b>psr</b></p>
9614
9615
9616
9617      </td>
9618
9619
9620 <td style="vertical-align: top;">R (10)<br>
9621
9622
9623
9624      </td>
9625
9626
9627 <td style="vertical-align: top;"><i>10
9628* (nx * dx)</i> </td>
9629
9630
9631 <td style="vertical-align: top;">Right
[48]9632edge of a particle
[108]9633source (in m). </td>
9634
9635
9636 </tr>
9637
9638
9639 <tr>
9640
9641
9642 <td style="vertical-align: top;"> 
9643     
9644     
9645      <p><a name="pss"></a><b>pss</b></p>
9646
9647
9648
9649      </td>
9650
9651
9652 <td style="vertical-align: top;">R (10)<br>
9653
9654
9655
9656      </td>
9657
9658
9659 <td style="vertical-align: top;"><i>10
9660* 0.0</i> </td>
9661
9662
9663 <td style="vertical-align: top;">Front
[48]9664(&ldquo;south&rdquo;) edge of a
[108]9665particle source (in m). </td>
9666
9667
9668 </tr>
9669
9670
9671 <tr>
9672
9673
9674 <td style="vertical-align: top;"> 
9675     
9676     
9677      <p><a name="pst"></a><b>pst</b></p>
9678
9679
9680
9681      </td>
9682
9683
9684 <td style="vertical-align: top;">R (10)<br>
9685
9686
9687
9688      </td>
9689
9690
9691 <td style="vertical-align: top;"><i>10
9692* zu(nz/2)</i> </td>
9693
9694
9695 <td style="vertical-align: top;">Top
[48]9696edge of a particle source
[108]9697(in m). </td>
9698
9699
9700 </tr>
9701
9702
9703 <tr>
9704
9705
9706 <td style="vertical-align: top;"> 
9707     
9708     
9709      <p><a name="radius"></a><b>radius</b></p>
9710
9711
9712
9713      </td>
9714
9715
9716 <td style="vertical-align: top;">R (10)</td>
9717
9718
9719
9720      <td style="vertical-align: top;"><i>0.0, 9</i>*<br>
9721
9722
9723
9724      <i>9999999.9</i></td>
9725
9726
9727 <td style="vertical-align: top;">Particle radius (in m).<br>
9728
9729
9730
9731      <br>
9732
9733
9734The viscous friction (in case of a velocity difference
[61]9735between
[5]9736particles and surrounding fluid) depends on the particle radius which
9737must be assigned as soon as <a href="chapter_4.2.html#density_ratio">density_ratio</a>
[108]9738/= <i>0.0</i>.<br>
9739
9740
9741 <br>
9742
9743
9744
[48]9745With several groups of particles (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
9746each group can be assigned a different value. If the number of values
9747given for <span style="font-weight: bold;">radius</span>
9748is less than the number of
[5]9749groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
9750then the last assigned value is used for all remaining groups. This
[108]9751means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br>
9752
9753
9754 </td>
9755
9756
9757
9758    </tr>
9759
9760
9761    <tr>
9762
9763
9764 <td style="vertical-align: top;"> 
9765     
9766     
9767      <p><a name="random_start_position"></a><b>random_start_position</b></p>
9768
9769
9770
9771      </td>
9772
9773
9774 <td style="vertical-align: top;">L<br>
9775
9776
9777 </td>
9778
9779
9780
9781      <td style="vertical-align: top;"><i>.F.</i> </td>
9782
9783
9784
9785      <td style="vertical-align: top;"> 
9786     
9787     
9788      <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>
[48]9789particles is
[108]9790varied randomly within certain limits.&nbsp; </p>
9791
9792
9793 
9794     
9795     
9796      <p>By
[48]9797default, the initial positions of particles within the
[5]9798source excatly correspond with the positions given by <a href="#psl">psl</a>,
[108]9799      <a href="#psr">psr</a>, <a href="#psn">psn</a>,
9800      <a href="#pss">pss</a>, <a href="#psb">psb</a>,
9801      <a href="#pst">pst</a>, <a href="#pdx">pdx</a>,
9802      <a href="#pdy">pdy</a>,
[5]9803and<a href="#pdz">
[48]9804pdz</a>. With <b>random_start_position</b> = <i>.T.
[108]9805      </i>the initial
[5]9806positions of the particles are allowed to randomly vary from these
[108]9807positions within certain limits.&nbsp; </p>
9808
9809
9810 
9811     
9812     
9813      <p><b>Very
9814important:<br>
9815
9816
9817 </b>In case of <b>random_start_position</b>
[48]9818= <i>.T.</i>, the
[5]9819random-number generators on the individual PEs no longer&nbsp;
9820run synchronously. If random disturbances are applied to the velocity
9821field
[48]9822(see <a href="#create_disturbances">create_disturbances</a>),
[108]9823      <font color="#000000">then as consequence for parallel
[48]9824runs the
[5]9825realizations of the turbulent flow
9826fields will deviate between runs which used different numbers of PEs!</font></p>
[108]9827
9828
9829
9830      </td>
9831
9832
9833 </tr>
9834
9835
9836 <tr>
9837
9838
9839 <td style="vertical-align: top;"> 
9840     
9841     
9842      <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b>
9843      <br>
9844
9845
9846 <b>restartfile</b></p>
9847
9848
9849 </td>
9850
9851
9852 <td style="vertical-align: top;">L<br>
9853
9854
9855 </td>
9856
9857
9858 <td style="vertical-align: top;"><i>.T.</i> </td>
9859
9860
9861
9862      <td style="vertical-align: top;"> 
9863     
9864     
9865      <p>Read particle
9866data from the previous run.&nbsp; </p>
9867
9868
9869 
9870     
9871     
9872      <p>By default,
[48]9873with restart runs particle data is read
[5]9874from file <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
9875which is created by the preceding run. If this is not requested or if
9876in a restart run particle transport is switched on for the
9877first time (see <a href="#particle_advection_start">particle_advection_start</a>),
9878then <b>read_particles_from_restartfile</b> = <i>.F.</i>
[108]9879is required.</p>
9880
9881
9882 </td>
9883
9884
9885 </tr>
9886
9887
9888 <tr>
9889
9890
9891 <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br>
9892
9893
9894
9895      </td>
9896
9897
9898 <td style="vertical-align: top;">I<br>
9899
9900
9901 </td>
9902
9903
9904
9905      <td style="vertical-align: top;"><span style="font-style: italic;">1</span><br>
9906
9907
9908 </td>
9909
9910
9911
9912      <td style="vertical-align: top;">Limit the number of
9913particle tails.<br>
9914
9915
9916 <br>
9917
9918
9919
[48]9920If particle tails are switched on (see <a href="#use_particle_tails">use_particle_tails</a>),
9921every particle is given a tail by default. <span style="font-weight: bold;">skip_particles_for_tail </span>can
[108]9922be used to give only every n'th particle a tail.<br>
9923
9924
9925 <br>
9926
9927
9928 <span style="font-weight: bold;">Example:</span><br>
9929
9930
9931 <span style="font-weight: bold;">skip_particles_for_tail</span>
[48]9932= <span style="font-style: italic;">10</span> means
[108]9933that only every 10th particle will be given a tail.<br>
9934
9935
9936 </td>
9937
9938
9939
9940    </tr>
9941
9942
9943 <tr>
9944
9945
9946 <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</span><br>
9947
9948
9949
9950      </td>
9951
9952
9953 <td style="vertical-align: top;">L<br>
9954
9955
9956 </td>
9957
9958
9959
9960      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
9961
9962
9963 </td>
9964
9965
9966
9967      <td style="vertical-align: top;">Give particles a tail.<br>
9968
9969
9970
9971      <br>
9972
9973
9974A particle tail is defined by the path a particle has moved
[5]9975along starting from some point of time in the past. It consists of a
9976set of descrete points in space which may e.g. be connected by a line
[108]9977in order visualize how the particle has moved.<br>
9978
9979
9980 <br>
9981
9982
9983
[48]9984By default, particles have no tail. Parameter&nbsp;<a href="#skip_particles_for_tail">skip_particles_for_tail</a>
[108]9985can be used to give only every n'th particle a tail.<br>
9986
9987
9988 <br>
9989
9990
9991
[48]9992The 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>,
9993and <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.<br>
[108]9994
9995
9996
9997      </td>
9998
9999
10000 </tr>
10001
10002
10003    <tr>
10004
10005
10006      <td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</span></td>
10007
10008
10009      <td align="left" valign="top">L</td>
10010
10011
10012      <td align="left" valign="top"><span style="font-style: italic;">.F.</span></td>
10013
10014
10015      <td align="left" valign="top">Use subgrid-scale
10016velocities for particle advection.<br>
10017
10018
10019      <br>
10020
10021
10022These
[5]10023velocities are calculated from the resolved and subgrid-scale TKE using
10024the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
1002561,
100262877-2887). When using this method, the timestep for the advancement of
10027the particles is limited by the so-called Lagrangian time scale. This
10028may be smaller than the current LES timestep so that several particle
10029(sub-) timesteps have to be carried out within one LES timestep. In
10030order to limit the number of sub-timesteps (and to limit the CPU-time),
10031the minimum value for the particle timestep is defined by the package
[108]10032parameter <a href="#dt_min_part">dt_min_part</a>.<br>
10033
10034
10035      <br>
10036
10037
10038Setting
10039      <span style="font-weight: bold;">use_sgs_for_particles</span>
[48]10040= <span style="font-style: italic;">.TRUE.</span>
10041automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>
10042= <span style="font-style: italic;">.TRUE.</span>.
[5]10043This inhibits the occurrence of large (artificial) spatial gradients of
10044the subgrid-scale TKE which otherwise would lead to wrong results for
[108]10045the particle advection.</td>
10046
10047
10048    </tr>
10049
10050
10051    <tr>
10052
10053
10054 <td style="vertical-align: top;"> 
10055     
10056     
10057      <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b>
10058      <br>
10059
10060
10061 <b>advection</b></p>
10062
10063
10064 </td>
10065
10066
10067 <td style="vertical-align: top;">L<br>
10068
10069
10070 </td>
10071
10072
10073 <td style="vertical-align: top;"><i>.T.</i> </td>
10074
10075
10076
10077      <td style="vertical-align: top;"> 
10078     
10079     
10080      <p>Switch on/off
10081vertical particle transport. </p>
10082
10083
10084 
10085     
10086     
10087      <p>By default,
[48]10088particles are transported along all three
10089directions in space. With <b>vertical_particle_advection</b>
10090= <i>.F., </i>the
[108]10091particles will only be transported horizontally.</p>
10092
10093
10094 </td>
10095
10096
10097
10098    </tr>
10099
10100
10101 <tr>
10102
10103
10104 <td style="vertical-align: top;">
10105     
10106     
10107      <p><a name="write_particle_statistics"></a><b>write_particle_</b>
10108      <br>
10109
10110
10111 <b>statistics</b></p>
10112
10113
10114 </td>
10115
10116
10117 <td style="vertical-align: top;">L<br>
10118
10119
10120 </td>
10121
10122
10123 <td style="vertical-align: top;"><i>.F.</i> </td>
10124
10125
10126
10127      <td style="vertical-align: top;"> 
10128     
10129     
10130      <p>Switch on/off
10131output of particle informations.<br>
10132
10133
10134 </p>
10135
10136
10137 
10138     
10139     
10140      <p><br>
10141
10142
10143
[5]10144For <span style="font-weight: bold;">write_particle_statistics</span>
10145= <span style="font-style: italic;">.T.</span> s<span style="font-family: thorndale,serif;">tatistical
10146informations</span> (e.g. the total number of particles used, the
10147number of particles exchanged between the PEs, etc.) which may be used
10148for debugging are output to the
10149local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>.&nbsp;
[108]10150      </p>
10151
10152
10153 
10154     
10155     
10156      <p><b>Note:</b> For parallel runs files
[48]10157may become very large
[108]10158and performance of PALM may decrease.</p>
10159
10160
10161 </td>
10162
10163
10164 </tr>
10165
10166
10167
10168 
10169 
10170  </tbody>
10171</table>
10172
10173
10174<span style="font-weight: bold;"><br>
10175
10176
10177
10178</span><br>
10179
10180
10181<h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
10182parameters: </h3>
10183
10184
10185<br>
10186
10187
10188<span style="font-weight: bold;">Package
[48]10189(<span style="font-weight: bold;">mrun</span> option
10190-p): <span style="font-weight: bold;"><a name="dvrp_graphics"></a>dvrp_graphics</span>
[5]10191&nbsp;&nbsp;&nbsp;
10192NAMELIST group name: <span style="font-weight: bold;">dvrp_graphics_par<br>
[108]10193
10194
10195
10196<br>
10197
10198
10199</span></span>
10200<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
10201
10202
10203 <tbody>
10204
10205
10206 <tr>
10207
10208
10209
10210      <td style="vertical-align: top;"><font size="4"><b>Parameter
10211name</b></font></td>
10212
10213
10214 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
10215
10216
10217
10218      <td style="vertical-align: top;"> 
10219     
10220     
10221      <p><b><font size="4">Default</font></b> <br>
10222
10223
10224 <b><font size="4">value</font></b></p>
10225
10226
10227 </td>
10228
10229
10230
10231      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
10232
10233
10234
10235    </tr>
10236
10237
[237]10238 <tr><td style="vertical-align: top;"><a name="cluster_size"></a><span style="font-weight: bold;">cluster_size</span></td><td style="vertical-align: top;">I</td><td style="vertical-align: top;"><span style="font-style: italic;">1</span></td><td>Vertex cluster size for polygon reduction of topography.<br><br>This
10239parameter can be used to reduce the number of polygones which form the
10240topography isosurface. In case of large numerical grids (large number
10241of gridpoints) and /or complex topography, cluster_size &gt; 1 may
10242speed up the animation significantly. Disadvantage: buildings may loose
10243their strict rectangular shape.<br><br>The allowed range of values is 1 &lt;= <span style="font-weight: bold;">cluster_size</span> &lt;= 5.<br><br> <span style="font-weight: bold;">Warning:</span> The allowed range of values is not checked. Wrong values may lead to unforseen effects or even aborts! </td></tr><tr>
[108]10244
10245
10246 <td style="vertical-align: top;">
10247     
10248     
10249      <p><a name="dt_dvrp"></a><b>dt_dvrp</b></p>
10250
10251
10252
10253      </td>
10254
10255
10256 <td style="vertical-align: top;">R</td>
10257
10258
10259
10260      <td style="vertical-align: top;"><i>9999999.9</i></td>
10261
10262
10263
10264      <td style="vertical-align: top;"> 
10265     
10266     
10267      <p>Temporal
[48]10268interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
[108]10269s).&nbsp; </p>
10270
10271
10272 
10273     
10274     
10275      <p>Isosurfaces, cross sections and
[48]10276particles can be displayed
[5]10277simultaneous. The display of particles requires that the particle
10278transport is switched on (see <a href="#dt_prel">dt_prel</a>).
[108]10279Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p>
10280
10281
10282 
10283     
10284     
10285      <p>If
[48]10286output of scenes created by dvrp software is switched on
[5]10287(see <a href="#mode_dvrp">mode_dvrp</a>),
10288this parameter can be used to assign the temporal interval at which
[48]10289scenes are to be created (and the respective&nbsp; graphical data
10290is to
[5]10291be output to the streaming server). <span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
10292&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dvrp</b>,
[48]102932*<b>dt_dvrp</b>, 3*<b>dt_dvrp</b>, etc. The
10294actual output times can
10295deviate 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;
10296Is <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
10297scenes are created and
[5]10298output after each time step (if this is requested it should be <b>dt_dvrp</b>
[108]10299= <i>0</i>).</font></span> </p>
10300
10301
10302 </td>
10303
10304
10305
10306    </tr>
10307
10308
10309 <tr>
10310
10311
10312 <td style="vertical-align: top;">
10313     
10314     
10315      <p><a name="dvrp_directory"></a><b>dvrp_directory</b></p>
10316
10317
10318
10319      </td>
10320
10321
10322 <td style="vertical-align: top;">C*80</td>
10323
10324
10325
10326      <td style="vertical-align: top;"><i>'default'</i></td>
10327
10328
10329
10330      <td style="vertical-align: top;"> 
10331     
10332     
10333      <p>Name of the
[48]10334directory into which data created by the <span style="font-weight: bold;">dvrp</span>
[108]10335software shall be saved.&nbsp; </p>
10336
10337
10338 
10339     
10340     
10341      <p>By default,
[48]10342the directory name is generated from the user
[5]10343name
10344(see package parameter <a href="#dvrp_username">dvrp_username</a>)
[48]10345and 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
[108]10346name&gt;/&lt;base file name&gt;'</span>.</p>
10347
10348
10349 </td>
10350
10351
10352
10353    </tr>
10354
10355
10356 <tr>
10357
10358
10359 <td style="vertical-align: top;">
10360     
10361     
10362      <p><a name="dvrp_file"></a><b>dvrp_file</b></p>
10363
10364
10365
10366      </td>
10367
10368
10369 <td style="vertical-align: top;">C*80</td>
10370
10371
10372
10373      <td style="vertical-align: top;"><i>'default'</i></td>
10374
10375
10376
10377      <td style="vertical-align: top;"> 
10378     
10379     
10380      <p>Name of the
[48]10381file into which data created by the <span style="font-weight: bold;">dvrp</span>
[108]10382software shall be output.&nbsp; </p>
10383
10384
10385 
10386     
10387     
10388      <p>This
[48]10389parameter can be given a value only in case of <a href="#dvrp_output">dvrp_output</a>
10390= <span style="font-style: italic;">'local'</span><i>
[108]10391      </i>which
[5]10392determines that the data created by <span style="font-weight: bold;">dvrp</span>
10393is output to a local file (on the machine where PALM is executed).
10394Apart from the default, it is only allowed to assign <span style="font-style: italic;">'/dev/null'</span> (which
10395means that no output is really stored). This can be used for special
10396runtime measurements of the <span style="font-weight: bold;">dvrp</span>
[108]10397software.</p>
10398
10399
10400 </td>
10401
10402
10403 </tr>
10404
10405
10406 <tr>
10407
10408
10409 <td style="vertical-align: top;"> 
10410     
10411     
10412      <p><a name="dvrp_host"></a><b>dvrp_host</b></p>
10413
10414
10415
10416      </td>
10417
10418
10419 <td style="vertical-align: top;">C*80</td>
10420
10421
10422
10423      <td style="vertical-align: top;"> 
10424     
10425     
10426      <p><i>'origin.rvs.</i>
10427      <br>
10428
10429
10430u<i>ni- hanover.de'</i></p>
10431
10432
10433 </td>
10434
10435
10436 <td style="vertical-align: top;"> 
10437     
10438     
10439      <p>Name of the computer
[48]10440to which data created by the <span style="font-weight: bold;">dvrp</span>
10441software shall be
[108]10442transferred.&nbsp; </p>
10443
10444
10445 
10446     
10447     
10448      <p>In case of <a href="#dvrp_output">dvrp_output</a>
[48]10449= <span style="font-style: italic;">'rtsp'</span>
10450only the default
[5]10451value is allowed (streaming server of
10452the RRZN). For <a href="#dvrp_output">dvrp_output</a>
[48]10453= <span style="font-style: italic;">'local'</span><i>
[108]10454      </i>the
10455assigned value is ignored.</p>
10456
10457
10458 </td>
10459
10460
10461 </tr>
10462
10463
10464 <tr>
10465
10466
10467
10468      <td style="vertical-align: top;"> 
10469     
10470     
10471      <p><a name="dvrp_output"></a><b>dvrp_output</b></p>
10472
10473
10474
10475      </td>
10476
10477
10478 <td style="vertical-align: top;">C*10</td>
10479
10480
10481
10482      <td style="vertical-align: top;"><i>'rtsp'</i></td>
10483
10484
10485
10486      <td style="vertical-align: top;"> 
10487     
10488     
10489      <p>Output mode
[48]10490for the <span style="font-weight: bold;">dvrp</span>
[108]10491software. <br>
10492
10493
10494 <br>
10495
10496
10497 </p>
10498
10499
10500
10501The following settings are allowed:<br>
10502
10503
10504 <br>
10505
10506
10507 
10508     
10509     
10510      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
10511
10512
10513 <tbody>
10514
10515
10516 <tr>
10517
10518
10519 <td style="vertical-align: top;"><i>'rtsp'</i></td>
10520
10521
10522
10523            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
[5]10524software is transferred using
10525a special transmission protocol to a so-called streaming server, which
10526is able to continuously transfer visualization data with a
10527high transmission rate.&nbsp; <br>
[108]10528
10529
10530
[5]10531Additionally, with this output mode a
10532set of files is generated automatically
10533within a directory on the streaming server (beside the visualization
10534data e.g. some html-files) which can be used to
10535visualize the data via an internet-browser plugin. Host
10536(streaming-server) and directory can be defined by the user with <a href="#dvrp_host">dvrp_host</a>
10537and <a href="#dvrp_directory">dvrp_directory</a>.</td>
[108]10538
10539
10540
10541          </tr>
10542
10543
10544 <tr>
10545
10546
10547 <td style="vertical-align: top;"><i>'ftp'</i></td>
10548
10549
10550
10551            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
[5]10552software is transferred to the destination host (see <a href="#dvrp_host">dvrp_host</a>
10553and <a href="#dvrp_directory">dvrp_directory</a>)
[108]10554using ftp.</td>
10555
10556
10557 </tr>
10558
10559
10560 <tr>
10561
10562
10563 <td style="vertical-align: top;"><i>'local'</i></td>
10564
10565
10566
10567            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
[5]10568software is output locally on a file defined by <a href="#dvrp_file">dvrp_file
[108]10569            </a>.</td>
10570
10571
10572 </tr>
10573
10574
10575 
10576       
10577       
10578        </tbody> 
10579     
10580     
10581      </table>
10582
10583
10584 <br>
10585
10586
10587
10588      </td>
10589
10590
10591 </tr>
10592
10593
10594 <tr>
10595
10596
10597 <td style="vertical-align: top;"> 
10598     
10599     
10600      <p><a name="dvrp_password"></a><b>dvrp_password</b></p>
10601
10602
10603
10604      </td>
10605
10606
10607 <td style="vertical-align: top;">C*80</td>
10608
10609
10610
10611      <td style="vertical-align: top;">'********'</td>
10612
10613
10614 <td style="vertical-align: top;"> 
10615     
10616     
10617      <p>Password for the
[48]10618computer to which data created by the <span style="font-weight: bold;">dvrp</span> software is to
10619be
[108]10620transferred.&nbsp; </p>
10621
10622
10623 
10624     
10625     
10626      <p>Assigning a password is
[48]10627only necessary in case of <a href="#dvrp_output">dvrp_output</a>
10628= <span style="font-style: italic;">'ftp'</span>.
10629For <a href="#dvrp_output">dvrp_output</a>
10630= <span style="font-style: italic;">'rtsp'</span><i>
[108]10631      </i>the default
10632value must not be changed!</p>
10633
10634
10635 </td>
10636
10637
10638 </tr>
10639
10640
10641 <tr>
10642
10643
10644
10645      <td style="vertical-align: top;"> 
10646     
10647     
10648      <p><a name="dvrp_username"></a><b>dvrp_username</b></p>
10649
10650
10651
10652      </td>
10653
10654
10655 <td style="vertical-align: top;">C*80</td>
10656
10657
10658
10659      <td style="vertical-align: top;"><br>
10660
10661
10662 </td>
10663
10664
10665 <td style="vertical-align: top;"> 
10666     
10667     
10668      <p>User name of a valid
[48]10669account on the computer to which data
10670created by the <span style="font-weight: bold;">dvrp</span>
10671software
[5]10672is to be
[108]10673transferred.&nbsp; </p>
10674
10675
10676 
10677     
10678     
10679      <p>Assigning a value to this
[48]10680parameter is required in case of <a href="#dvrp_output">dvrp_output</a>
10681= <span style="font-style: italic;">'rtsp'</span>
10682or <span style="font-style: italic;">'ftp'</span>.</p>
[108]10683
10684
10685
10686      </td>
10687
10688
10689 </tr>
10690
10691
10692 <tr>
10693
10694
10695 <td style="vertical-align: top;"> 
10696     
10697     
10698      <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p>
10699
10700
10701
10702      </td>
10703
10704
10705 <td style="vertical-align: top;">C*20&nbsp;
10706      <br>
10707
10708
10709(10)</td>
10710
10711
10712 <td style="vertical-align: top;"><i>10
10713* ''</i></td>
10714
10715
10716 <td style="vertical-align: top;">
10717     
10718     
10719      <p>Graphical objects (isosurfaces, slicers, particles) which are
[5]10720to be created by the <span style="font-weight: bold;">dvrp</span>
[108]10721software.&nbsp; </p>
10722
10723
10724 
10725     
10726     
10727      <p>Several different objects can
[48]10728be assigned simultaneously and
[130]10729will 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>
10730(isosurface), <span style="font-style: italic;">'slicer##'</span>
[5]10731(cross sections), and <span style="font-style: italic;">'particles'</span>.
[130]10732Within the strings the hash characters ("##") have to be replaced by two
10733digits 01&le;##&le;99. Up to 10 objects
[129]10734can be assigned at the same time, e.g.:&nbsp; </p>
[108]10735
10736
10737 
10738     
10739     
10740      <blockquote><b>mode_dvrp</b>
[130]10741= <span style="font-style: italic;">'isosurface02'</span><i>,
10742'slicer01',
10743'particles', 'slicer02'</i></blockquote>
[108]10744
10745
10746 
10747     
10748     
10749      <p>In this
[48]10750case one isosurface, two cross sections, and particles
[129]10751will be created. The quantities for which isosurfaces or cross sections are to be
[5]10752created have to be selected with
[129]10753the parameter <a href="#data_output">data_output</a> (<span style="font-weight: bold;">data_output</span>
[48]10754also determines the
[129]10755orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> <span style="font-weight: bold;"></span>lists of
[48]10756variables may be
[130]10757assigned, the digits at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string
10758select the quantity, which is given
10759at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface02'</span>
[129]10760selects the second 3D quantity
[130]10761of <span style="font-weight: bold;">data_output</span>,  <span style="font-style: italic;">'slicer01'</span> selects the first 2D quantity
[129]10762of <span style="font-weight: bold;">data_output</span>).
10763If e.g. <span style="font-weight: bold;">data_output</span> is assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
10764'w_xz', 'v_yz'</i>, <span style="font-style: italic;">'pt'</span><i>,
10765'u', 'w'</i>, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
[48]10766isosurface of u, a
[5]10767horizontal cross section of u and
[129]10768a vertical cross section (xz) of w are created. For locations of the
[5]10769cross sections see <a href="#data_output">data_output</a>.
10770The theshold value for which the isosurface is
10771to be created can be defined with parameter <a href="#threshold">threshold</a>.<br>
[108]10772
10773
10774
10775      </p>
10776
10777
10778 
10779     
10780     
10781      <p>The vertical extension of the displayed domain is
[130]10782given by <a href="#nz_do3d">nz_do3d</a>.</p><p>If user-defined dvrp objects exist (see <a href="chapter_3.5.4.html">chapter 3.5.4</a>), then&nbsp;<span style="font-weight: bold;">mode_dvrp</span> may also refer to quantities selected with the parameter&nbsp;<a href="chapter_4.3.html#data_output_user">data_output_user</a> (internally PALM appends them to those selected&nbsp;with
10783the parameter <a href="chapter_4.2.html#data_output">data_output</a>).
[108]10784
10785
[129]10786 </p><p><b>Assignments
[48]10787of mode_dvrp must correspond to those of data_output
[5]10788and
[130]10789data_output_user! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>,<span style="font-style: italic;"> 'w'</span><i> </i>was set, then only the digits "01" are allowed
[48]10790for <b>mode_dvrp</b>,
[130]10791thus <span style="font-style: italic;">'isosurface01'</span>
10792and/or <span style="font-style: italic;">'slicer01'</span><i>.</i>
[108]10793      </p>
10794
10795
10796 
10797     
10798     
10799      <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are
[48]10800given in <a href="chapter_4.5.7.html">chapter
[108]108014.5.7</a>.<br>
10802
10803
10804 </p>
10805
10806
10807 <b>Note:</b><br>
10808
10809
10810
[5]10811The declaration color charts to be
[130]10812used still have to be given "manually" in subroutine <a href="chapter_3.4.html#user_dvrp_coltab"><span style="font-family: monospace;">user_dvrp_coltab</span></a>
[48]10813(file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;
[108]10814      <br>
10815
10816
10817A change of particle colors and/or particle diameters (e.g.
[48]10818according
[5]10819to the local characteristics of the flow field) to be used for the
10820visualization, must be carried out by adding respective code extensions
[130]10821to <a href="chapter_3.4.html#user_particle_attributes"><tt><font style="font-size: 11pt;" size="2">user_particle_attributes</font></tt></a>
[5]10822(in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).&nbsp;</td>
[108]10823
10824
10825
10826    </tr>
10827
10828
10829 <tr>
10830
10831
10832 <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br>
10833
10834
10835
10836dvrp</span></td>
10837
10838
10839 <td style="vertical-align: top;">R(2,10)</td>
10840
10841
10842
10843      <td style="vertical-align: top;"><span style="font-style: italic;">10
10844* (-1,1)</span></td>
10845
10846
10847 <td style="vertical-align: top;">Ranges
[5]10848of values to which a color table has to be mapped (units of the
[108]10849respective quantity).<br>
10850
10851
10852 <br>
10853
10854
10855
[5]10856In case that slicers have to be displayed (see <a href="#threshold">mode_dvrp</a>),
10857this parameter defines the ranges of values of the respective
10858quantities to which the colortable in use has to be mapped. If e.g. a
10859temperature slice shall be displayed, the colortable defines colors
10860from blue to red, and <span style="font-weight: bold;">slicer_range_limits_dvrp</span>
10861= 290.0, 305.0 then areas with temperature of 290 K are displayed in
10862dark blue and those with 305.0 are displayed in dark red. Temperatures
10863within these limits will be displayed by a continuous color gradient
10864from blue to red and Temperatures outside the limits will
[108]10865be displayed either in dark blue or in dark red.<br>
10866
10867
10868 <br>
10869
10870
10871
[5]10872Up to ten different ranges can be assigned in case that more than one
[108]10873slicer has to be displayed.<br>
10874
10875
10876 <br>
10877
10878
10879
[5]10880See <a href="#threshold">mode_dvrp</a>
[108]10881for the declaration of color charts.</td>
10882
10883
10884 </tr>
10885
10886
10887 <tr>
10888
10889
10890
10891      <td style="vertical-align: top;"> 
10892     
10893     
10894      <p><a name="superelevation"></a><b>superelevation</b></p>
10895
10896
10897
10898      </td>
10899
10900
10901 <td style="vertical-align: top;">R</td>
10902
10903
10904
10905      <td style="vertical-align: top;"><i>1.0</i></td>
10906
10907
10908
10909      <td style="vertical-align: top;"> 
10910     
10911     
10912      <p>Superelevation
10913factor for the vertical coordinate.&nbsp; </p>
10914
10915
10916 
10917     
10918     
10919      <p>For
[48]10920domains with unfavorable ratio between the vertical and
[5]10921the horizontal size
10922(the vertical size is determined by <a href="#nz_do3d">nz_do3d</a>)
[48]10923a <span style="font-weight: bold;">superelevation</span>
10924/= <span style="font-style: italic;">1.0</span> may
10925be used. If e.g. the
[5]10926horizontal size is substantially larger
10927than the vertical size, a <span style="font-weight: bold;">superelevation</span>
[48]10928much larger than <span style="font-style: italic;">1.0</span>
10929should
[5]10930be used, since otherwise the domain appears as a
10931"flat disk" in the visualization and thus the vertical direction is
[108]10932only very poorly resolved.</p>
10933
10934
10935 </td>
10936
10937
10938 </tr>
10939
10940
10941 <tr>
10942
10943
10944
10945      <td style="vertical-align: top;"> 
10946     
10947     
10948      <p><a name="superelevation_x"></a><b>superelevation_x</b></p>
10949
10950
10951
10952      </td>
10953
10954
10955 <td style="vertical-align: top;">R<br>
10956
10957
10958 </td>
10959
10960
10961
10962      <td style="vertical-align: top; font-style: italic;">1.0<br>
10963
10964
10965
10966      </td>
10967
10968
10969 <td style="vertical-align: top;"> 
10970     
10971     
10972      <p>Superelevation
10973factor for the horizontal (x) coordinate.&nbsp; </p>
10974
10975
10976 
10977     
10978     
10979      <p>This
[48]10980parameter can be used to stretch the displayed domain
[5]10981along the x-direction. See also <a href="#superelevation">superelevation</a>.</p>
[108]10982
10983
10984
10985      </td>
10986
10987
10988 </tr>
10989
10990
10991 <tr>
10992
10993
10994 <td style="vertical-align: top;"> 
10995     
10996     
10997      <p><a name="superelevation_y"></a><b>superelevation_y</b></p>
10998
10999
11000
11001      </td>
11002
11003
11004 <td style="vertical-align: top;">R<br>
11005
11006
11007 </td>
11008
11009
11010
11011      <td style="vertical-align: top; font-style: italic;">1.0<br>
11012
11013
11014
11015      </td>
11016
11017
11018 <td style="vertical-align: top;">Superelevation
[48]11019factor for the
[108]11020horizontal (y) coordinate.&nbsp; 
11021     
11022     
11023      <p>This parameter can be
[48]11024used to
[108]11025stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p>
11026
11027
11028 </td>
11029
11030
11031
11032    </tr>
11033
11034
11035 <tr>
11036
11037
11038 <td style="vertical-align: top;">
11039     
11040     
11041      <p><a name="threshold"></a><b>threshold</b></p>
11042
11043
11044
11045      </td>
11046
11047
11048 <td style="vertical-align: top;">R(10)<br>
11049
11050
11051
11052      </td>
11053
11054
11055 <td style="vertical-align: top; font-style: italic;">0.0<br>
11056
11057
11058
11059      </td>
11060
11061
11062 <td style="vertical-align: top;"> 
11063     
11064     
11065      <p>Threshold
[48]11066value for which an isosurface is to be created by
11067the <span style="font-weight: bold;">dvrp</span>
[108]11068software.&nbsp; </p>
11069
11070
11071 
11072     
11073     
11074      <p>If the creation of
[48]11075isosurfaces is switched on via
[5]11076parameter <a href="#mode_dvrp">mode_dvrp</a>,
11077then the respective threshold value for which the isosurface is to be
[48]11078created can be assigned via <b>threshold</b>. If several
11079isosurfaces
11080are given by <b>mode_dvrp</b>, then an individual
11081threshold value for
[5]11082each isosurface can be assigned. The order of the threshold values
11083refers to the order of the isosurfaces given by <b>mode_dvrp</b>.</p>
[108]11084
11085
11086
11087      </td>
11088
11089
11090 </tr>
11091
11092
11093 
11094 
11095 
11096  </tbody>
11097</table>
11098
11099
11100<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
11101
11102
11103
[5]11104</span></span><span style="font-weight: bold;"><span style="font-weight: bold;">Package (<span style="font-weight: bold;">mrun</span>
11105option -p): <span style="font-weight: bold;"><a name="spectra"></a>spectra</span>&nbsp;&nbsp;&nbsp;&nbsp;
11106NAMELIST group name: <span style="font-weight: bold;">spectra_par<br>
[108]11107
11108
11109
11110<br>
11111
11112
11113</span></span></span>
11114<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
11115
11116
11117 <tbody>
11118
11119
11120 <tr>
11121
11122
11123
11124      <td style="vertical-align: top;"><font size="4"><b>Parameter
11125name</b></font></td>
11126
11127
11128 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
11129
11130
11131
11132      <td style="vertical-align: top;"> 
11133     
11134     
11135      <p><b><font size="4">Default</font></b> <br>
11136
11137
11138 <b><font size="4">value</font></b></p>
11139
11140
11141 </td>
11142
11143
11144
11145      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
11146
11147
11148
11149    </tr>
11150
11151
11152 <tr>
11153
11154
11155 <td style="vertical-align: top;">
11156     
11157     
11158      <p><a name="averaging_interval_sp"></a><b>averaging_interval_sp</b></p>
11159
11160
11161
11162      </td>
11163
11164
11165 <td style="vertical-align: top;">R<br>
11166
11167
11168 </td>
11169
11170
11171
11172      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
11173
11174
11175
11176interval</a></span> </td>
11177
11178
11179 <td style="vertical-align: top;"> 
11180     
11181     
11182      <p>Averaging interval
[48]11183for spectra output to local
11184file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
[108]11185      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
[48]11186/ &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
[108]11187(in s).&nbsp; </p>
11188
11189
11190 
11191     
11192     
11193      <p>If
[5]11194this parameter is given a non-zero value, temporally
11195averaged spectra data are output. By default, spectra data data are not
11196subject to temporal averaging. The interval length is limited by the
[48]11197parameter <a href="#dt_dosp">dt_dosp</a>. In any
11198case <b>averaging_interval_sp</b> &lt;= <b>dt_dosp
[108]11199      </b>must
11200hold.</p>
11201
11202
11203If an interval is defined, then by default the average
[48]11204is calculated
[5]11205from the data values of all timesteps lying within this interval. The
11206number of time levels entering into the average can be reduced with the
11207parameter <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>.
[108]11208     
11209     
11210      <p>If
[5]11211an averaging interval can not be completed at the end of a run, it will
11212be finished at the beginning of the next restart run. Thus for restart
11213runs, averaging intervals do not
[108]11214necessarily begin at the beginning of the run.</p>
11215
11216
11217      </td>
11218
11219
11220 </tr>
11221
11222
11223
11224    <tr>
11225
11226
11227 <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td>
11228
11229
11230
[189]11231      <td style="vertical-align: top;">I(100)</td>
[108]11232
11233
11234 <td style="vertical-align: top;"><i>no level</i></td>
11235
11236
11237
11238      <td style="vertical-align: top;"> 
11239     
11240     
11241      <p>Vertical level
[48]11242for which horizontal spectra are to be
[108]11243calculated and output (gridpoints).<br>
11244
11245
11246 </p>
11247
11248
11249 <br>
11250
11251
11252
[189]11253Spectra can be calculated for up to 100 levels.</td>
[108]11254
11255
11256 </tr>
11257
11258
11259
11260    <tr>
11261
11262
11263      <td style="vertical-align: top;">
11264     
11265     
11266      <p><a name="data_output_sp"></a><b>data_output_sp</b></p>
11267
11268
11269      </td>
11270
11271
11272      <td style="vertical-align: top;">C*10 (10)</td>
11273
11274
11275      <td style="vertical-align: top;"><i>10 * ' '</i></td>
11276
11277
11278      <td style="vertical-align: top;">
11279     
11280     
11281      <p>Quantities for which
[48]11282horizontal spectra are to be calculated
[108]11283and output.</p>
11284
11285
11286 
11287     
11288     
[144]11289      <p>Allowed standard values are:&nbsp; <b>data_output_sp</b>
11290= <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>. The user may define further quantities (see <a href="chapter_3.5.4#spectra">chapter 3.5.4 part 5</a>).<br>
[108]11291
11292
11293 </p>
11294
11295
11296
11297     
11298     
11299      <p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p>
11300
11301
11302
11303     
11304     
11305      <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>.
[48]11306The file's format is NetCDF.&nbsp; Further details about processing
[108]11307NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
11308
11309
11310     
11311     
11312      <p>The
[48]11313temporal interval of the output times of profiles is
[108]11314assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>.&nbsp;</p>
11315
11316
11317     
11318     
11319      <p>The
[48]11320vertical levels for which spectra are to be computed and output must be
11321given 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>.
[108]11322      </p>
11323
11324
11325      <span style="font-weight: bold;">Note:</span><br>
11326
11327
11328
[48]11329Beside <span style="font-weight: bold;">data_output_sp</span>,
11330values <span style="font-weight: bold;">must</span>
11331be given for each of the
[5]11332parameters,&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>,
11333and <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a></font>,
[48]11334otherwise <span style="font-weight: bold;">no</span>
11335output will be
[108]11336created!<br>
11337
11338
11339      <br>
11340
11341
11342      <br>
11343
11344
11345
[5]11346Calculation of spectra requires cyclic boundary conditions
11347along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
[48]11348and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For
11349historical reasons, data can also be output in ASCII-format on local
11350files <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
11351and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
11352(depending on the direction(s) along which spectra are to be
11353calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font>
11354which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See
11355parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
11356for defining the format in which data shall be output.&nbsp;Within
11357these file, the spectra are ordered with respect to their
[5]11358output times. Spectra can also be temporally averaged (see <a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a>
[48]11359).&nbsp;<font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a
11360spectrum is output in a single line (1st column:
[5]11361wavenumber, 2nd column: spectral coefficient). If spectra are to be
11362calculated 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>),
11363the spectral coefficients for the further heighs can be found in the
11364subsequent columns. </font>The order
11365of the data in the file follows the order used in the assignment for <b>data_output_sp</b>
11366(<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
11367means that the file starts with the spectra of the u-component,
[48]11368followed by the v-component spectra, etc.). Additional to the files
11369PLOTSP_X_DATA and PLOTSP_Y_DATA which contain
[5]11370the data,
11371PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a>
11372and <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_Y_PAR</a>)
11373which 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>.
11374Spectra can be directly plotted with <span style="font-weight: bold;">profil</span>
11375using the data and the corresponding parameter file. The
11376plot layout is
11377steered via the parameter input file. The vertical levels for which
[48]11378spectra 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
11379spectra
[5]11380will appear on the plot, although data are available on file. All
11381parameter values can be changed by editing the parameter
11382input
[108]11383file.<span style="font-weight: bold;"><br>
11384
11385
11386      </span></td>
11387
11388
11389    </tr>
11390
11391
11392    <tr>
11393
11394
11395
11396      <td style="vertical-align: top;"> 
11397     
11398     
11399      <p><a name="dt_dosp"></a><b>dt_dosp</b></p>
11400
11401
11402
11403      </td>
11404
11405
11406 <td style="vertical-align: top;">R</td>
11407
11408
11409
11410      <td style="vertical-align: top;"><i>value of
11411&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
11412
11413
11414output</a></i></td>
11415
11416
11417
11418      <td style="vertical-align: top;"> 
11419     
11420     
11421      <p>Temporal
[48]11422interval at which&nbsp;spectra data shall be output
[108]11423(in s).&nbsp; </p>
11424
11425
11426 
11427     
11428     
11429      <p><span lang="en-GB"><font face="Thorndale">If output of
[48]11430horizontal 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
11431parameter can be used to
[5]11432assign the temporal interval at which spectral data&nbsp; shall be
[48]11433output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
11434simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>,
11435which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
[5]11436time is the beginning of
11437&nbsp;the simulation, i.e. output takes place at times t = <span style="font-weight: bold;">skip_time_dosp</span> + <b>dt_dosp</b>,
[108]11438      <span style="font-weight: bold;">skip_time_dosp</span>
[48]11439+ 2*<b>dt_dosp</b>, skip_time_dosp + 3*<b>dt_dosp</b>,
11440etc. The actual output times can
11441deviate 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;
11442If <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
11443spectral data are output
[5]11444after each time step (if this is requested it should be <b>dt_dosp</b>
[108]11445= <i>0</i>).</font></span> </p>
11446
11447
11448 </td>
11449
11450
11451
11452    </tr>
11453
11454
11455 <tr>
11456
11457
11458 <td style="vertical-align: top;">
11459     
11460     
11461      <p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p>
11462
11463
11464
11465      </td>
11466
11467
[189]11468 <td style="vertical-align: top;">I(100)</td>
[108]11469
11470
11471
11472      <td style="vertical-align: top;"><i>no level</i></td>
11473
11474
11475
11476      <td style="vertical-align: top;"> 
11477     
11478     
11479      <p>Vertical
[48]11480level(s) for which horizontal spectra are to be
[108]11481plotted (in gridpoints).&nbsp; </p>
11482
11483
11484 
11485     
11486     
11487      <p>This parameter
[48]11488only affects the display of spectra in plots
11489created with <span style="font-weight: bold;">profil</span>.
11490The
[5]11491spectral data created and output to file are exclusively determined via
[108]11492      <font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p>
11493
11494
11495
11496      </td>
11497
11498
11499 </tr>
11500
11501
11502 <tr>
11503
11504
11505 <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td>
11506
11507
11508
11509      <td style="vertical-align: top;">R<br>
11510
11511
11512 </td>
11513
11514
11515 <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>
11516
11517
11518data_output</a></span>
11519      </td>
11520
11521
11522 <td style="vertical-align: top;">No output of
11523spectra data before this interval has passed (in s).<br>
11524
11525
11526      <br>
11527
11528
11529This
[48]11530parameter causes that data output activities are starting not before
11531this interval
[108]11532(counting from the beginning of the simulation, t=0) has passed. <br>
11533
11534
11535      <br>
11536
11537
11538      <span style="font-weight: bold;">Example:</span><br>
11539
11540
11541If
[48]11542the 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
[108]11543first output will be done at t = 5400 s. </td>
11544
11545
11546 </tr>
11547
11548
11549
11550    <tr>
11551
11552
11553 <td style="vertical-align: top;"> 
11554     
11555     
11556      <p><a name="spectra_direction"></a><b>spectra_direction</b></p>
11557
11558
11559
11560      </td>
11561
11562
11563 <td style="vertical-align: top;">C*2 (10)</td>
11564
11565
11566
11567      <td style="vertical-align: top;"><i>10 * ' '</i></td>
11568
11569
11570
11571      <td style="vertical-align: top;"> 
11572     
11573     
11574      <p>Direction(s)
11575along which spectra are to be calculated.&nbsp; </p>
11576
11577
11578 
11579     
11580     
11581      <p>Allowed
[48]11582values are <span style="font-style: italic;">'x'</span>,
[108]11583      <span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For
[5]11584every quantity given by <a href="#data_output_sp">data_output_sp</a>
11585a corresponding
[48]11586direction<span style="font-weight: bold;"> </span>must
[108]11587be assigned.<br>
11588
11589
11590 </p>
11591
11592
11593 
11594     
11595     
11596      <p>Calculation of spectra
[48]11597requires cyclic boundary conditions
[5]11598along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
11599and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</p>
[108]11600
11601
11602
11603      </td>
11604
11605
11606 </tr>
11607
11608
11609 
11610 
11611 
11612  </tbody>
11613</table>
11614
11615
11616<span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
11617
11618
11619
11620</span></span></span>
11621<h3 style="line-height: 100%;"><br>
11622
11623
11624<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>
11625
11626
11627<span style="font-style: italic;">Last change:</span>
[61]11628$Id: chapter_4.2.html 240 2009-02-18 17:50:38Z letzel $ <span style="font-weight: bold;"><span style="font-weight: bold;"><br>
[108]11629
11630
11631
11632</span></span><br>
11633
11634
[116]11635</body></html>
Note: See TracBrowser for help on using the repository browser.
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |