source: palm/tags/release-3.4/DOC/app/chapter_4.2.html @ 546

Last change on this file since 546 was 108, checked in by letzel, 17 years ago
  • Improved coupler: evaporation - salinity-flux coupling for humidity = .T.,

avoid MPI hangs when coupled runs terminate, add DOC/app/chapter_3.8;

  • Optional calculation of km and kh from initial TKE e_init;
  • Default initialization of km,kh = 0.00001 for ocean = .T.;
  • Allow data_output_pr= q, wq, w"q", w*q* for humidity = .T.;
  • Bugfix: Rayleigh damping for ocean fixed.
  • Property svn:keywords set to Id
File size: 260.0 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html>
3<head>
4
5
6
7 
8 
9  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
10
11
12 
13 
14  <title>PALM chapter 4.2</title>
15</head>
16
17
18<body>
19
20
21<h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
22parameters</a>, <a href="#particle_parameters">particle parameters</a>, and <a href="#Paketparameter">package
23parameters</a></h3>
24
25
26
27<h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3>
28
29
30
31<br>
32
33
34<br>
35
36
37<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
38
39
40 <tbody>
41
42
43
44    <tr>
45
46
47
48      <td style="vertical-align: top;"><font size="4"><b>Parameter
49name</b></font></td>
50
51
52 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
53
54
55
56      <td style="vertical-align: top;"> 
57     
58     
59      <p><b><font size="4">Default</font></b> <br>
60
61
62 <b><font size="4">value</font></b></p>
63
64
65 </td>
66
67
68
69      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
70
71
72
73    </tr>
74
75
76 <tr>
77
78
79 <td style="vertical-align: top;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
80
81
82
83      </td>
84
85
86 <td style="vertical-align: top;">R<br>
87
88
89 </td>
90
91
92
93      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
94
95
96 </td>
97
98
99
100      <td style="vertical-align: top;">Averaging interval for
101all&nbsp;output of temporally averaged data (in s).<br>
102
103
104      <br>
105
106
107This
108parameter defines the time interval length for temporally averaged data
109(vertical profiles, spectra, 2d cross-sections, 3d volume data). By
110default,&nbsp;data are not subject to temporal averaging. The
111interval
112length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
113In any case, <span style="font-weight: bold;">averaging_interval</span>
114&lt;= <span style="font-weight: bold;">dt_data_output_av</span>
115must hold.<br>
116
117
118      <br>
119
120
121If
122an interval is defined, then by default the average is calculated from
123the data values of all timesteps lying within this interval. The number
124of time levels entering into the average can be reduced with the
125parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br>
126
127
128      <br>
129
130
131If
132an averaging interval can not be completed at the end of a run, it
133will be finished at the beginning of the next restart run. Thus for
134restart runs, averaging intervals do not
135necessarily begin at the beginning of the run.<br>
136
137
138      <br>
139
140
141Parameters
142      <a href="#averaging_interval_pr">averaging_interval_pr</a>
143and <a href="#averaging_interval_sp">averaging_interval_sp</a>
144can be used to define different averaging intervals for vertical
145profile data and spectra, respectively.<br>
146
147
148 </td>
149
150
151 </tr>
152
153
154
155    <tr>
156
157
158 <td style="vertical-align: top;"> 
159     
160     
161      <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
162
163
164
165      </td>
166
167
168 <td style="vertical-align: top;">R<br>
169
170
171 </td>
172
173
174
175      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
176
177
178
179interval</a><br>
180
181
182
183      </span> </td>
184
185
186 <td style="vertical-align: top;">
187     
188     
189      <p>Averaging
190interval for output of vertical profiles&nbsp;to
191local
192file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
193      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
194(in s).&nbsp; </p>
195
196
197 
198     
199     
200      <p>If
201this parameter is given a non-zero value, temporally
202averaged vertical profile data are output. By default, profile data
203data are not subject to temporal averaging. The interval length is
204limited by the parameter <a href="#dt_dopr">dt_dopr</a>.
205In any case <b>averaging_interval_pr</b> &lt;= <b>dt_dopr
206      </b>must
207hold.</p>
208
209
210If an interval is defined, then by default the average
211is calculated
212from the data values of all timesteps lying within this interval. The
213number of time levels entering into the average can be reduced with the
214parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>.
215     
216     
217      <p>If
218an averaging interval can not be completed at the end of a run, it will
219be finished at the beginning of the next restart run. Thus for restart
220runs, averaging intervals do not
221necessarily begin at the beginning of the run.</p>
222
223
224 </td>
225
226
227 </tr>
228
229
230
231    <tr>
232
233
234 <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
235
236
237
238substeps</span></td>
239
240
241 <td style="vertical-align: top;">L<br>
242
243
244
245      </td>
246
247
248 <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
249
250
251 </td>
252
253
254
255      <td style="vertical-align: top;">Switch
256to steer the call of the pressure solver.<br>
257
258
259 <br>
260
261
262
263In order to speed-up performance, the Poisson equation for perturbation
264pressure (see <a href="#psolver">psolver</a>) can
265be called only at the last substep of multistep Runge-Kutta
266timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>)
267by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span>
268= <span style="font-style: italic;">.F.</span>.
269In many cases, this sufficiently reduces the divergence of the velocity
270field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this
271case and in case
272of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span>
273= <span style="font-style: italic;">.T.</span>
274should be used.&nbsp;<span style="font-weight: bold;"></span></td>
275
276
277
278    </tr>
279
280
281 <tr>
282
283
284 <td style="vertical-align: top;">
285     
286     
287      <p><a name="fcl_factor"></a><b>cfl_factor</b></p>
288
289
290
291      </td>
292
293
294 <td style="vertical-align: top;">R<br>
295
296
297 </td>
298
299
300
301      <td style="vertical-align: top;"> 
302     
303     
304      <p><i>0.1,
3050.8 or 0.9</i> <br>
306
307
308 <i>(see right)</i></p>
309
310
311
312      </td>
313
314
315 <td style="vertical-align: top;"> 
316     
317     
318      <p lang="en-GB">Time step limiting factor.&nbsp; </p>
319
320
321
322     
323     
324      <p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
325allowed </span>time step according to CFL and
326diffusion-criterion
327dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">=
328dt_max * <b>cfl_factor</b>
329in order to avoid stability problems which may arise in the vicinity of
330the maximum allowed timestep. The condition <i>0.0</i>
331&lt; <b>cfl_factor</b>
332&lt; <i>1.0 </i>applies.<br>
333
334
335 </span></p>
336
337
338
339     
340     
341      <p><span lang="en-GB">The default value of
342cfl_factor depends on
343the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br>
344
345
346 </span></p>
347
348
349 
350     
351     
352      <p><span lang="en-GB">For the third order Runge-Kutta scheme it
353is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br>
354
355
356 </span></p>
357
358
359 
360     
361     
362      <p><span lang="en-GB">In case of the leapfrog scheme a quite
363restrictive value of <span style="font-weight: bold;">cfl_factor</span>
364= <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
365divergence
366significantly 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
367be used with the leapfrog scheme but these are to be determined by
368appropriate test runs.<span style="font-family: times new roman;"><br>
369
370
371
372      </span></span></p>
373
374
375 <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
376scheme is <span style="font-weight: bold;">cfl_factor</span>
377= <span style="font-style: italic;">0.8</span> .</font></span></td>
378
379
380
381    </tr>
382
383
384    <tr>
385
386
387 <td style="vertical-align: top;"> 
388     
389     
390      <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
391
392
393
394      </td>
395
396
397 <td style="vertical-align: top;">L<br>
398
399
400 </td>
401
402
403
404      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
405
406
407 </td>
408
409
410
411      <td style="vertical-align: top;"> 
412     
413     
414      <p>Switch to
415impose random perturbations to the horizontal
416velocity field.&nbsp; </p>
417
418
419 
420     
421     
422      <p>With <b>create_disturbances</b>
423= <i>.T.,</i> random
424perturbations can be imposed to the horizontal velocity field at
425certain times e.g. in order to trigger off the onset of convection,
426etc..<br>
427
428
429 </p>
430
431
432 
433     
434     
435      <p>The temporal interval between
436these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
437the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a>
438and <a href="#disturbance_level_t">disturbance_level_t</a>,
439and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>.
440In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
441and <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
442the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a>
443and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>.
444A perturbation is added to each grid point with its individual value
445determined by multiplying the disturbance amplitude with a uniformly
446distributed random number.
447After this, the arrays of u and v are smoothed by applying a
448Shuman-filter twice and made divergence-free by applying the pressure
449solver.<br>
450
451
452 </p>
453
454
455 
456     
457     
458      <p>The random number generator to
459be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br>
460
461
462
463      </p>
464
465
466 
467     
468     
469      <p>As soon as the desired flow features have
470developed
471(e.g.&nbsp; convection has started), further imposing of
472perturbations
473is not necessary and can be omitted (this does not hold for non-cyclic
474lateral boundaries!). This can be steered by assigning
475an upper limit value for the perturbation energy (the perturbation
476energy is defined by the deviation of the velocity from the mean flow)
477using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>.
478As soon as the perturbation energy has exceeded this energy limit, no
479more random perturbations are assigned<br>
480
481
482
483.&nbsp; <br>
484
485
486
487Timesteps where a random perturbation has been imposed are marked in
488the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
489by the character "D" appended to the values of the maximum horizontal
490velocities. </p>
491
492
493 </td>
494
495
496 </tr>
497
498
499 <tr>
500
501
502 <td style="vertical-align: top;"> 
503     
504     
505      <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
506
507
508
509      </td>
510
511
512 <td style="vertical-align: top;">C*10&nbsp;
513      <br>
514
515
516&nbsp;&nbsp; (100)</td>
517
518
519 <td style="vertical-align: top;"><i>100 * ' '</i></td>
520
521
522
523      <td style="vertical-align: top;"> 
524     
525     
526      <p>Type of
527normalization applied to the x-coordinate of vertical
528profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
529
530
531
532     
533     
534      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
535= <span style="font-style: italic;">'profil'</span>.</p>
536
537
538     
539     
540      <p>If
541vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
542local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
543parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
544the x-values of the data points can be normalized with respect to
545certain quantities (e.g. the near-surface heat flux) in order to ensure
546a better comparability. This type of normalization then applies to all
547profiles of one coordinate system (panel). The normalization quantities
548are re-calculated for each output time of each individual profile. If
549temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>),
550then the normalization quantities are also temporally averaged
551accordingly. If the value of a normalization quantity becomes zero,
552then normalization for the total respective coordinate system (panel)
553is switched off automatically (also for the y-axis).<br>
554
555
556 </p>
557
558
559
560     
561     
562      <p>By default, the normalization quantities are calculated as the
563horizontal mean of the total model domain and and these values are also
564used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
565Instead of this, they can be calculated from the data of a certain
566subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a>
567(however, they are used again for all subdomains and even for the total
568domain).&nbsp; </p>
569
570
571 
572     
573     
574      <p>The user can choose between
575the following normalization
576quantities: <br>
577
578
579 </p>
580
581
582 
583     
584     
585      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
586
587
588 <tbody>
589
590
591 <tr>
592
593
594 <td style="vertical-align: top;"><i>'wpt0'</i></td>
595
596
597
598            <td style="vertical-align: top;">Normalization with
599respect
600to the total surface sensible heat
601flux (k=0 ).</td>
602
603
604 </tr>
605
606
607 <tr>
608
609
610 <td style="vertical-align: middle;"><i>'ws2'</i></td>
611
612
613
614            <td style="vertical-align: top;">Normalization with
615respect
616to w<sub>*</sub> <sup>2</sup>
617(square of the characteristic vertical wind speed of the CBL)</td>
618
619
620
621          </tr>
622
623
624 <tr>
625
626
627 <td style="vertical-align: top;"><i>'tsw2'</i></td>
628
629
630
631            <td style="vertical-align: top;">Normalization with
632respect
633to the square of the characteristic
634temperature of the CBL theta<sub>*</sub> (this is defined
635as ratio of
636the surface heat flux and w<sub>*</sub>).</td>
637
638
639 </tr>
640
641
642
643          <tr>
644
645
646 <td style="vertical-align: middle;"><i>'ws3'</i></td>
647
648
649
650            <td style="vertical-align: top;">Normalization with
651respect
652to w<sub>*</sub> <sup>3</sup>.</td>
653
654
655 </tr>
656
657
658
659          <tr>
660
661
662 <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
663
664
665
666            <td style="vertical-align: top;">Normalization with
667respect
668to w<sub>*</sub><sup>2</sup>theta<sub>*</sub>
669(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
670
671
672
673          </tr>
674
675
676 <tr>
677
678
679 <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
680
681
682
683            <td style="vertical-align: top;">Normalization with
684respect
685to w<sub>*</sub><sup>2 </sup>theta<sub>*</sub>
686(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
687
688
689
690          </tr>
691
692
693 
694       
695       
696        </tbody> 
697     
698     
699      </table>
700
701
702 
703     
704     
705      <p>For each
706coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>)
707an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> =
708      <span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
709then the
710x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
711and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>.
712Data
713of the further coordinate systems (if any are to be drawn) are not
714normalized.&nbsp; </p>
715
716
717 
718     
719     
720      <p>Using a normalization
721leaves all vertical profile data on
722local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
723unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the
724normalization is steered
725by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a>
726which may be changed subsequently by the user in the parameter file
727(local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
728
729
730
731&nbsp;<br>
732
733
734
735The assigned normalization quantity is noted in the axes labels of the
736respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
737
738
739
740      </td>
741
742
743 </tr>
744
745
746 <tr>
747
748
749 <td style="vertical-align: top;"> 
750     
751     
752      <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
753
754
755
756      </td>
757
758
759 <td style="vertical-align: top;">C*10&nbsp;
760      <br>
761
762
763&nbsp;&nbsp; (100)</td>
764
765
766 <td style="vertical-align: top;"><i>100 * ' '</i></td>
767
768
769
770      <td style="vertical-align: top;"> 
771     
772     
773      <p>Type of
774normalization applied to the y-coordinate of vertical
775profiles to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;</p>
776
777
778
779     
780     
781      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
782= <span style="font-style: italic;">'profil'</span>.</p>
783
784
785     
786     
787      <p>If
788vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
789local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
790parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
791the y-values of the data points can be normalized with respect to
792certain quantities (at present only the normalization with respect to
793the boundary layer height is possible) in order to ensure a better
794comparability. </p>
795
796
797 
798     
799     
800      <p>The user can choose between the
801following normalization
802quantities: <br>
803
804
805 </p>
806
807
808 
809     
810     
811      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
812
813
814 <tbody>
815
816
817 <tr>
818
819
820 <td style="vertical-align: top;"><i>'z_i'</i></td>
821
822
823
824            <td style="vertical-align: top;">Normalization with
825respect
826to the boundary layer height
827(determined from the height where the heat flux achieves its minimum
828value).</td>
829
830
831 </tr>
832
833
834 
835       
836       
837        </tbody> 
838     
839     
840      </table>
841
842
843 
844     
845     
846      <p>For
847further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p>
848
849
850
851      </td>
852
853
854 </tr>
855
856
857 <tr>
858
859
860 <td style="vertical-align: top;"> 
861     
862     
863      <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
864
865
866
867      </td>
868
869
870 <td style="vertical-align: top;">C*100&nbsp;
871      <br>
872
873
874&nbsp;&nbsp; (100)</td>
875
876
877 <td style="vertical-align: top;">see right<br>
878
879
880 </td>
881
882
883
884      <td style="vertical-align: top;"> 
885     
886     
887      <p>Determines
888which vertical profiles are to be presented in
889which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used.
890&nbsp; </p>
891
892
893 
894     
895     
896      <p>This parameter only applies for
897&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
898= <span style="font-style: italic;">'profil'</span>.</p>
899
900
901     
902     
903      <p>The
904default assignment is:&nbsp; </p>
905
906
907 
908     
909     
910      <p><b>cross_profiles</b>
911=&nbsp; </p>
912
913
914 
915     
916     
917      <ul>
918
919
920 
921       
922       
923        <p><span style="font-family: monospace; font-style: italic;">'
924u v ',</span><br>
925
926
927 <span style="font-family: monospace; font-style: italic;">' pt
928',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
929
930
931 <span style="font-family: monospace; font-style: italic;">'
932w"pt" w*pt* w*pt*BC wpt wptBC ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
933
934
935 <span style="font-family: monospace; font-style: italic;">'
936w"u" w*u* wu w"v"w*v* wv ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
937
938
939 <span style="font-family: monospace; font-style: italic;">' km
940kh ',</span><br style="font-family: monospace; font-style: italic;">
941
942
943 <span style="font-family: monospace; font-style: italic;">' l '
944,</span><br>
945
946
947
94814 * <span style="font-family: monospace; font-style: italic;">'
949'</span></p>
950
951
952 
953     
954     
955      </ul>
956
957
958 
959     
960     
961      <p>If plot output of
962vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
963the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.
964Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
965which describes the layout for a plot to be generated with the plot
966program <span style="font-weight: bold;">profil</span>.
967The parameter <b>cross_profiles</b>
968determines how many coordinate systems (panels) the plot contains and
969which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
970expects a character string (up to 100 characters long) for each
971coordinate system, which consists of the names of the profiles to be
972drawn into this system (all available profiles and their respective
973names are described at parameter <a href="#data_output_pr">data_output_pr</a>).
974The single names have to be separated by one blank (' ') and a blank
975must be spent also at the beginning and at the end of the
976string.&nbsp; </p>
977
978
979 
980     
981     
982      <p>Example:&nbsp; </p>
983
984
985 
986     
987     
988      <ul>
989
990
991
992       
993       
994        <p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
995' pt '</span></p>
996
997
998 
999     
1000     
1001      </ul>
1002
1003
1004 
1005     
1006     
1007      <p>In this case the
1008plot consists of two coordinate systems
1009(panels) with the first panel containing the profiles of the horizontal
1010velocity components (<span style="font-style: italic;">'u'</span>
1011and <span style="font-style: italic;">'v'</span>)
1012of all output times (see <a href="#dt_dopr">dt_dopr</a>)
1013and the second one containing the profiles of the potential temperature
1014(<span style="font-style: italic;">'pt'</span>).<br>
1015
1016
1017
1018      </p>
1019
1020
1021 
1022     
1023     
1024      <p>Whether the coordinate systems are actually drawn,
1025depends on
1026whether data of the appropriate profiles were output during the run
1027(profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>).
1028For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned,
1029then
1030the plot only consists of one panel, since no profiles of the potential
1031temperature were output. On the other hand, if profiles were assigned
1032to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>,
1033then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
1034but they are not drawn in the plot. <br>
1035
1036
1037 </p>
1038
1039
1040
1041The arrangement of the panels in the plot can be controlled
1042with the parameters <a href="#profile_columns">profile_columns</a>
1043and <a href="#profile_rows">profile_rows</a>.
1044Up to 100 panels systems are allowed in a plot (however, they may be
1045distributed on several pages).</td>
1046
1047
1048 </tr>
1049
1050
1051 <tr>
1052
1053
1054 <td style="vertical-align: top;"> 
1055     
1056     
1057      <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
1058
1059
1060
1061      </td>
1062
1063
1064 <td style="vertical-align: top;">C*40&nbsp;
1065      <br>
1066
1067
1068&nbsp;&nbsp; (100)</td>
1069
1070
1071 <td style="vertical-align: top;">see right<br>
1072
1073
1074 </td>
1075
1076
1077
1078      <td style="vertical-align: top;"> 
1079     
1080     
1081      <p>x-axis labels
1082of vertical profile coordinate systems to be
1083plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
1084      </p>
1085
1086
1087 
1088     
1089     
1090      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1091= <span style="font-style: italic;">'profil'</span>.</p>
1092
1093
1094     
1095     
1096      <p>The
1097default assignment is:&nbsp; </p>
1098
1099
1100 
1101     
1102     
1103      <p><b>cross_xtext</b>
1104=&nbsp; </p>
1105
1106
1107 
1108     
1109     
1110      <ul>
1111
1112
1113 
1114       
1115       
1116        <p><span style="font-style: italic;">'wind speed in
1117ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1118
1119
1120 <span style="font-style: italic;">'pot. temperature in
1121K',&nbsp; </span><br style="font-style: italic;">
1122
1123
1124
1125        <span style="font-style: italic;">'heat flux in K
1126ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1127
1128
1129 <span style="font-style: italic;">'momentum flux in
1130m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;">
1131
1132
1133 <span style="font-style: italic;">'eddy diffusivity in
1134m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1135
1136
1137 <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
1138        <br>
1139
1140
114114 * <span style="font-style: italic;">' '</span></p>
1142
1143
1144
1145     
1146     
1147      </ul>
1148
1149
1150 
1151     
1152     
1153      <p>This parameter can be used to assign x-axis
1154labels to vertical
1155profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output
1156of vertical
1157profile data see <a href="#data_output_pr">data_output_pr</a>).<br>
1158
1159
1160
1161The labels are assigned to those coordinate systems (panels) defined by
1162      <a href="#cross_profiles">cross_profiles</a>
1163according to their respective order (compare the default values of <b>cross_xtext</b>
1164and <b>cross_profiles</b>). </p>
1165
1166
1167 
1168     
1169     
1170      <p>Umlauts
1171are possible (write &ldquo; in front of, similar to TeX), as
1172well as super- and subscripts (use "&gt;" or "&lt;" in front of
1173each
1174character), special characters etc. (see UNIRAS manuals) when using the
1175plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p>
1176
1177
1178
1179      </td>
1180
1181
1182 </tr>
1183
1184
1185 <tr>
1186
1187
1188 <td style="vertical-align: top;"> 
1189     
1190     
1191      <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
1192
1193
1194
1195      </td>
1196
1197
1198 <td style="vertical-align: top;">C*1</td>
1199
1200
1201
1202      <td style="vertical-align: top;"><i>'w'</i></td>
1203
1204
1205
1206      <td style="vertical-align: top;"> 
1207     
1208     
1209      <p>Type of cycle
1210to be used with the multi-grid method.&nbsp; </p>
1211
1212
1213 
1214     
1215     
1216      <p>This
1217parameter determines which type of cycle is applied in
1218the multi-grid method used for solving the Poisson equation for
1219perturbation pressure (see <a href="#psolver">psolver</a>).
1220It defines in which way it is switched between the fine and coarse
1221grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b>
1222may be assigned the values <i>'v'</i> or <i>'w'</i>).
1223The
1224computational cost of w-cycles is much higher than that of v-cycles,
1225however, w-cycles give a much better convergence. </p>
1226
1227
1228 </td>
1229
1230
1231
1232    </tr>
1233
1234
1235 <tr>
1236
1237
1238 <td style="vertical-align: top;">
1239     
1240     
1241      <p><a name="data_output"></a><b>data_output</b></p>
1242
1243
1244
1245      </td>
1246
1247
1248 <td style="vertical-align: top;">C * 10 (100)<br>
1249
1250
1251
1252      </td>
1253
1254
1255 <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
1256
1257
1258
1259      </td>
1260
1261
1262 <td style="vertical-align: top;">Quantities
1263for which 2d cross section and/or 3d volume data are to be output.<br>
1264
1265
1266      <br>
1267
1268
1269PALM
1270allows the output of instantaneous data as well as of temporally
1271averaged data which is steered by the strings assigned to this
1272parameter (see below).<br>
1273
1274
1275      <br>
1276
1277
1278By default, cross section
1279data are output (depending on the selected cross sections(s), see
1280below)&nbsp; to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>,
1281      <a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
1282and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>.
1283Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>.
1284If the user has switched on the output of temporally averaged data,
1285these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>,
1286      <a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
1287      <a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
1288and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
1289respectively.<br>
1290
1291
1292      <br>
1293
1294
1295The
1296filenames already suggest that all files have NetCDF format.
1297Informations about the file content (kind of quantities, array
1298dimensions and grid coordinates) are part of the self describing NetCDF
1299format and can be extracted from the NetCDF files using the command
1300"ncdump -c &lt;filename&gt;". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing
1301the PALM NetCDF data.<br>
1302
1303
1304      <br>
1305
1306
1307The following quantities are
1308available for output by default (quantity names ending with '*' are only allowed for the output of horizontal cross sections):<br>
1309
1310
1311      <br>
1312
1313
1314     
1315     
1316      <table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2">
1317
1318
1319        <tbody>
1320
1321
1322          <tr>
1323
1324
1325            <td style="width: 106px;"><span style="font-weight: bold;">quantity
1326name</span></td>
1327
1328
1329            <td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td>
1330
1331
1332            <td><span style="font-weight: bold;">unit</span></td>
1333
1334
1335            <td><span style="font-weight: bold;">remarks</span></td>
1336
1337
1338          </tr>
1339
1340
1341          <tr>
1342
1343
1344            <td style="width: 106px;"><span style="font-style: italic;">e</span></td>
1345
1346
1347            <td style="width: 196px;">SGS TKE</td>
1348
1349
1350            <td>m<sup>2</sup>/s<sup>2</sup></td>
1351
1352
1353            <td></td>
1354
1355
1356          </tr>
1357
1358
1359          <tr>
1360
1361
1362            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td>
1363
1364
1365            <td style="width: 196px; vertical-align: top;">liquid water path</td>
1366
1367
1368            <td style="vertical-align: top;">m</td>
1369
1370
1371            <td style="vertical-align: top;">only horizontal cross section
1372is allowed,&nbsp;requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
1373= <span style="font-style: italic;">.TRUE.</span></td>
1374
1375
1376          </tr>
1377
1378
1379          <tr>
1380
1381
1382            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td>
1383
1384
1385            <td style="width: 196px; vertical-align: top;">perturpation
1386pressure</td>
1387
1388
1389            <td style="vertical-align: top;">N/m<sup>2</sup>,
1390Pa</td>
1391
1392
1393            <td style="vertical-align: top;"></td>
1394
1395
1396          </tr>
1397
1398
1399          <tr>
1400
1401
1402            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td>
1403
1404
1405            <td style="width: 196px; vertical-align: top;">particle/droplet
1406concentration</td>
1407
1408
1409            <td style="vertical-align: top;">#/gridbox</td>
1410
1411
1412            <td style="vertical-align: top;">requires that particle
1413advection is switched on by <span style="font-weight: bold;">mrun</span>-option
1414"-p particles"</td>
1415
1416
1417          </tr>
1418
1419
1420          <tr>
1421
1422
1423            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td>
1424
1425
1426            <td style="width: 196px; vertical-align: top;">mean
1427particle/droplet radius </td>
1428
1429
1430            <td style="vertical-align: top;">m</td>
1431
1432
1433            <td style="vertical-align: top;">requires that particle
1434advection is switched on by <span style="font-weight: bold;">mrun</span>-option
1435"-p particles"</td>
1436
1437
1438          </tr>
1439
1440
1441          <tr>
1442
1443
1444            <td style="vertical-align: top;"><span style="font-style: italic;">pra*</span></td>
1445
1446
1447            <td style="vertical-align: top;">precipitation amount</td>
1448
1449
1450            <td style="vertical-align: top;">mm</td>
1451
1452
1453            <td style="vertical-align: top;">only horizontal cross section
1454is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
1455= <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>
1456
1457
1458          </tr>
1459
1460
1461          <tr>
1462
1463
1464            <td style="vertical-align: top;"><span style="font-style: italic;">prr*</span></td>
1465
1466
1467            <td style="vertical-align: top;">precipitation rate</td>
1468
1469
1470            <td style="vertical-align: top;">mm/s</td>
1471
1472
1473            <td style="vertical-align: top;">only horizontal cross section
1474is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
1475= <span style="font-style: italic;">.TRUE.</span></td>
1476
1477
1478          </tr>
1479
1480
1481          <tr>
1482
1483
1484            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td>
1485
1486
1487            <td style="width: 196px; vertical-align: top;">potential
1488temperature<br>
1489
1490
1491            </td>
1492
1493
1494            <td style="vertical-align: top;">K</td>
1495
1496
1497            <td style="vertical-align: top;"></td>
1498
1499
1500          </tr>
1501
1502
1503          <tr>
1504
1505
1506            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td>
1507
1508
1509            <td style="width: 196px; vertical-align: top;">specific humidity
1510(or total water content, if cloud physics is switched on)</td>
1511
1512
1513            <td style="vertical-align: top;">kg/kg</td>
1514
1515
1516            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
1517
1518
1519          </tr>
1520
1521
1522          <tr>
1523
1524
1525            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td>
1526
1527
1528            <td style="width: 196px; vertical-align: top;">liquid water
1529content</td>
1530
1531
1532            <td style="vertical-align: top;">kg/kg</td>
1533
1534
1535            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
1536= <span style="font-style: italic;">.TRUE.</span>
1537or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1538= <span style="font-style: italic;">.TRUE.</span></td>
1539
1540
1541          </tr>
1542
1543
1544          <tr>
1545
1546
1547            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td>
1548
1549
1550            <td style="width: 196px; vertical-align: top;">change in liquid
1551water content due to condensation/evaporation during last timestep</td>
1552
1553
1554            <td style="vertical-align: top;">kg/kg</td>
1555
1556
1557            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1558= <span style="font-style: italic;">.TRUE.</span></td>
1559
1560
1561          </tr>
1562
1563
1564          <tr>
1565
1566
1567            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td>
1568
1569
1570            <td style="width: 196px; vertical-align: top;">volume of liquid
1571water</td>
1572
1573
1574            <td style="vertical-align: top;">m<sup>3</sup>/gridbox</td>
1575
1576
1577            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1578= <span style="font-style: italic;">.TRUE.</span></td>
1579
1580
1581          </tr>
1582
1583
1584          <tr>
1585
1586
1587            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td>
1588
1589
1590            <td style="width: 196px; vertical-align: top;">weighting factor</td>
1591
1592
1593            <td style="vertical-align: top;"></td>
1594
1595
1596            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
1597= <span style="font-style: italic;">.TRUE.</span></td>
1598
1599
1600          </tr>
1601
1602
1603          <tr>
1604
1605
1606            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td>
1607
1608
1609            <td style="width: 196px; vertical-align: top;">water vapor
1610content (specific humidity)</td>
1611
1612
1613            <td style="vertical-align: top;">kg/kg</td>
1614
1615
1616            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
1617= <span style="font-style: italic;">.TRUE.</span></td>
1618
1619
1620          </tr>
1621
1622
1623          <tr>
1624
1625
1626            <td align="undefined" valign="undefined"><span style="font-style: italic;">rho</span></td>
1627
1628
1629            <td align="undefined" valign="undefined">potential density</td>
1630
1631
1632            <td align="undefined" valign="undefined">kg/m<sup>3</sup></td>
1633
1634
1635            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
1636= <span style="font-style: italic;">.TRUE.</span></td>
1637
1638
1639          </tr>
1640
1641
1642          <tr>
1643
1644
1645            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td>
1646
1647
1648            <td style="width: 196px; vertical-align: top;">concentration of
1649the scalar</td>
1650
1651
1652            <td style="vertical-align: top;">1/m<sup>3</sup></td>
1653
1654
1655            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
1656= <span style="font-style: italic;">.TRUE.</span></td>
1657
1658
1659          </tr>
1660
1661
1662          <tr>
1663
1664
1665            <td align="undefined" valign="undefined"><span style="font-style: italic;">sa</span></td>
1666
1667
1668            <td align="undefined" valign="undefined">salinity</td>
1669
1670
1671            <td align="undefined" valign="undefined">psu</td>
1672
1673
1674            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
1675= <span style="font-style: italic;">.TRUE.</span></td>
1676
1677
1678          </tr>
1679
1680
1681          <tr>
1682
1683
1684            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td>
1685
1686
1687            <td style="width: 196px; vertical-align: top;">(near surface)
1688characteristic temperature</td>
1689
1690
1691            <td style="vertical-align: top;">K</td>
1692
1693
1694            <td style="vertical-align: top;">only horizontal cross section
1695is allowed</td>
1696
1697
1698          </tr>
1699
1700
1701          <tr>
1702
1703
1704            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td>
1705
1706
1707            <td style="width: 196px; vertical-align: top;">u-component of
1708the velocity</td>
1709
1710
1711            <td style="vertical-align: top;">m/s</td>
1712
1713
1714            <td style="vertical-align: top;"></td>
1715
1716
1717          </tr>
1718
1719
1720          <tr>
1721
1722
1723            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td>
1724
1725
1726            <td style="width: 196px; vertical-align: top;">(near surface)
1727friction velocity</td>
1728
1729
1730            <td style="vertical-align: top;">m/s</td>
1731
1732
1733            <td style="vertical-align: top;">only horizontal cross section
1734is allowed</td>
1735
1736
1737          </tr>
1738
1739
1740          <tr>
1741
1742
1743            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td>
1744
1745
1746            <td style="width: 196px; vertical-align: top;">v-component of
1747the velocity</td>
1748
1749
1750            <td style="vertical-align: top;">m/s</td>
1751
1752
1753            <td style="vertical-align: top;"></td>
1754
1755
1756          </tr>
1757
1758
1759          <tr>
1760
1761
1762            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td>
1763
1764
1765            <td style="width: 196px; vertical-align: top;">virtual potential
1766temperature</td>
1767
1768
1769            <td style="vertical-align: top;">K</td>
1770
1771
1772            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
1773
1774
1775          </tr>
1776
1777
1778          <tr>
1779
1780
1781            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td>
1782
1783
1784            <td style="width: 196px; vertical-align: top;">w-component of
1785the velocity</td>
1786
1787
1788            <td style="vertical-align: top;">m/s</td>
1789
1790
1791            <td style="vertical-align: top;"></td>
1792
1793
1794          </tr>
1795
1796
1797          <tr>
1798
1799
1800            <td style="vertical-align: top;"><span style="font-style: italic;">z0*</span></td>
1801
1802
1803            <td style="vertical-align: top;">roughness length</td>
1804
1805
1806            <td style="vertical-align: top;">m</td>
1807
1808
1809            <td></td>
1810
1811
1812          </tr>
1813
1814
1815       
1816       
1817        </tbody>
1818     
1819     
1820      </table>
1821
1822
1823      <br>
1824
1825
1826Multiple
1827quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span>
1828= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br>
1829
1830
1831      <br>
1832
1833
1834By
1835assigning the pure strings from the above table, 3d volume data is
1836output. 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
1837respective quantities. Time averaged&nbsp;output is created by
1838appending the string <span style="font-style: italic;">'_av'
1839      </span>(for
1840cross section data, this string must be appended after the cross
1841section string). Cross section data can also be (additionally) averaged
1842along the direction normal to the respective section (see below).
1843Assignments of quantities can be given in arbitrary
1844order:<br>
1845
1846
1847      <br>
1848
1849
1850Example:<br>
1851
1852
1853      <br>
1854
1855
1856     
1857     
1858      <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>
1859
1860
1861      </div>
1862
1863
1864      <br>
1865
1866
1867This
1868example will create the following output: instantaneous 3d volume data
1869of u-velocity component (by default on file DATA_3D_NETCDF), temporally
1870averaged 3d volume data of u-velocity component (by default on file
1871DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of
1872w-velocity component (by default on file DATA_2D_XY_NETCDF), and
1873temporally averaged vertical cross section data of potential
1874temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br>
1875
1876
1877      <br>
1878
1879
1880The
1881user is allowed to extend the above list of quantities by defining his
1882own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br>
1883
1884
1885      <br>
1886
1887
1888The
1889time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
1890This is valid for all types of output quantities by default. Individual
1891time intervals for instantaneous &nbsp;(!) 3d and section data can
1892be
1893declared 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>
1894
1895
1896      <br>
1897
1898
1899Also,
1900an individual time interval for output of temporally averaged data can
1901be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
1902This applies to both 3d volume and cross section data. The length of
1903the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br>
1904
1905
1906      <br>
1907
1908
1909The
1910parameter <a href="#skip_time_data_output">skip_time_data_output</a>
1911can be used to shift data output activities for a given time interval.
1912Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>,
1913      <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>
1914
1915
1916     
1917     
1918      <p>With
1919the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>&nbsp;
1920the output can be limited in the vertical direction up to a certain
1921grid point.<br>
1922
1923
1924 </p>
1925
1926
1927 Cross sections extend through the
1928total model
1929domain. In the two horizontal directions all grid points with 0
1930&lt;= i
1931&lt;= nx+1 and 0 &lt;= j
1932&lt;= ny+1 are output so that in case of cyclic boundary conditions
1933the
1934complete total domain is represented. The location(s) of the cross
1935sections can be defined with parameters <a href="#section_xy">section_xy</a>,
1936      <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>
1937causes&nbsp;the output data to be averaged along the direction
1938normal to the respective section.<br>
1939
1940
1941      <br>
1942
1943
1944      <br>
1945
1946
1947      <span style="font-weight: bold;">Output of user defined quantities:</span><br>
1948
1949
1950      <br>
1951
1952
1953Beside
1954the standard quantities from the above list, the user can output any
1955other quantities. These have to be defined and calculated within the
1956user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>).
1957They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>
1958for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
1959Output of the user defined quantities (time interval, averaging,
1960selection of cross sections, etc.) is controlled with the parameters
1961listed above and data are written to the same file(s) as the standard
1962quantities.<br>
1963
1964
1965      <br>
1966
1967
1968     
1969     
1970      <p style="font-weight: bold;">Output
1971on parallel machines:</p>
1972
1973
1974     
1975     
1976      <p>
1977By default, with parallel runs, processors output only data
1978of their respective subdomains into seperate local files (file names
1979are
1980constructed by appending the four digit processor ID, e.g.
1981&lt;filename&gt;_0000, &lt;filename&gt;_0001, etc.).
1982After PALM has
1983finished, the contents of these individual
1984files are sampled into one final file<span style="font-weight: bold;"></span>
1985using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
1986(to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
1987configuration file).</p>
1988
1989
1990 
1991     
1992     
1993      <p>Alternatively, PALM is able to
1994collect all grid points of a
1995cross section on PE0 before output is done. In this case only
1996one&nbsp;
1997output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
1998does not have to be called. In case of very large numbers of horizontal
1999gridpoints, sufficient
2000memory is required on PE0.&nbsp; This method can be used by
2001assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
2002= <i>.F.</i>.</p>
2003
2004
2005     
2006     
2007      <p>3d volume data output is
2008always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span>
2009has to be called anyway after PALM has been finished.</p>
2010
2011
2012     
2013     
2014      <p><br>
2015
2016
2017      <span style="font-weight: bold;">Old formats:</span></p>
2018
2019
2020
2021     
2022     
2023      <p>Beside
2024the NetCDF format,&nbsp;2d cross section data and 3d volume data
2025can
2026also be output, for historical reasons, in a different (binary) format
2027using parameter <a href="#data_output_format">data_output_format</a>.</p>
2028
2029
2030     
2031     
2032      <p>By
2033assigning <span style="font-weight: bold;">data_output_format
2034      </span>= <span style="font-style: italic;">'avs'</span>,
2035the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
2036Output is in FORTRAN binary format&nbsp;readable by
2037the plot software <span style="font-weight: bold;">AVS</span>.&nbsp;
2038The order of data on the file follows the order used in the assignment
2039for <b>data_output</b> (e.g. <b>data_output</b>
2040= <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,...&nbsp;
2041means that the file starts with the pressure data, followed by the
2042v-component of the velocity, etc.). Both instantaneous and time
2043averaged data are written on this file! Additional to this file, PALM
2044creates
2045a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>)
2046with coordinate information needed by <span style="font-weight: bold;">AVS</span>.
2047As third and
2048fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
2049and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>),
2050which describe the contents of the data file and/or coordinate file
2051and are used by AVS. However, AVS expects the content description in
2052one file. This needs the local file PLOT3D_FLD_COOR to be appended to
2053the file
2054PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
2055configuration file: &ldquo;<span style="font-family: monospace;">cat
2056PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>&rdquo;)
2057after PALM has
2058finished.&nbsp;To reduce the amount of data, output to this file
2059can be done
2060in
2061compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>).
2062Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in
2063      <a href="chapter_4.5.5.html">chapter
20644.5.5</a>.</p>
2065
2066
2067By assigning <span style="font-weight: bold;">data_output_format </span>=
2068      <span style="font-style: italic;">'iso2d'</span>,
2069the 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>.
2070Output is in FORTRAN binary format&nbsp;readable by
2071the plot software&nbsp;<span style="font-weight: bold;">iso2d</span>.&nbsp;
2072The order of data on the files follows the order used in the assignment
2073for <b>data_output</b> (e.g. <b>data_output</b>
2074= <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,...&nbsp;
2075means that the file containing the horizontal cross section data starts
2076with the instantaneous pressure data, followed by the
2077temporally averaged v-component of the velocity, etc.). Both
2078instantaneous and time averaged data are written on this
2079file!Additional to these binary files, PALM
2080creates NAMELIST parameter files
2081(local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>,
2082      <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
2083      <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
2084      <a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
2085      <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
2086      <a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
2087which 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>.
2088That needs local files with suffix _LOCAL to be appended to the
2089respective files with suffix _GLOBAL (by
2090suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span>
2091configuration file, e.g.: &ldquo;<span style="font-family: monospace;">cat
2092PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</span>&rdquo;)
2093after PALM has
2094finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the
2095respective data and
2096parameter file. The plot layout is steered via the parameter input
2097file.
2098The values of these <span style="font-weight: bold;">iso2d</span>
2099parameters are determined by a set of mostly internal PALM parameters
2100(exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>).
2101All parameter values can be changed by editing the parameter input
2102file.&nbsp;Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found
2103in <a href="chapter_4.5.4.html">chapter
21044.5.4</a>.<br>
2105
2106
2107      <br>
2108
2109
2110      <span style="font-weight: bold;">Important:</span><br>
2111
2112
2113There
2114is no guarantee that iso2d- and avs-output will be available in future
2115PALM versions (later than 3.0). </td>
2116
2117
2118 </tr>
2119
2120
2121 <tr>
2122
2123
2124 <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
2125
2126
2127
2128      </td>
2129
2130
2131 <td style="vertical-align: top;">C * 10 (10) </td>
2132
2133
2134
2135      <td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
2136
2137
2138
2139      <td style="vertical-align: top;">Format of output data.<br>
2140
2141
2142      <br>
2143
2144
2145By
2146default, all data (profiles, time
2147series, spectra, particle data, cross sections, volume data) are output
2148in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).
2149Exception: 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>,
2150      <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
2151are always output in FORTRAN binary format.<br>
2152
2153
2154      <br>
2155
2156
2157The
2158numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br>
2159
2160
2161      <br>
2162
2163
2164The
2165maximum file size for NetCDF files is 2 GByte by default. Use the
2166parameter <a href="#netcdf_64bit">netcdf_64bit</a>
2167if larger files have to be created.<br>
2168
2169
2170      <br>
2171
2172
2173For historical
2174reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span>
2175may be assigned the following values:<br>
2176
2177
2178      <br>
2179
2180
2181     
2182     
2183      <table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2">
2184
2185
2186        <tbody>
2187
2188
2189          <tr>
2190
2191
2192            <td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td>
2193
2194
2195            <td>output
2196of profiles,&nbsp;time series and spectra in ASCII format to be
2197read by the graphic software <span style="font-weight: bold;">profil
2198            </span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
2199            <a href="#chapter_4.5.3.html">4.5.3</a>)</td>
2200
2201
2202          </tr>
2203
2204
2205          <tr>
2206
2207
2208            <td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td>
2209
2210
2211            <td>output
2212of 2d cross-sections in FORTRAN binary format to be read by the graphic
2213software <span style="font-weight: bold;">iso2d</span>
2214(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td>
2215
2216
2217          </tr>
2218
2219
2220          <tr>
2221
2222
2223            <td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td>
2224
2225
2226            <td>output
2227of 3d volume data in FORTRAN binary format to be read by the graphic
2228software <span style="font-weight: bold;">AVS</span>
2229(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td>
2230
2231
2232          </tr>
2233
2234
2235       
2236       
2237        </tbody>
2238     
2239     
2240      </table>
2241
2242
2243      <br>
2244
2245
2246Multiple
2247values can be assigned to <span style="font-weight: bold;">data_output_format</span>,
2248i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as
2249cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> =
2250      <span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
2251assigned.<br>
2252
2253
2254      <br>
2255
2256
2257      <span style="font-weight: bold;">Warning:</span>
2258There is no guarantee that the "old" formats will be available in
2259future PALM versions (beyond 3.0)!<br>
2260
2261
2262 </td>
2263
2264
2265 </tr>
2266
2267
2268 <tr>
2269
2270
2271
2272      <td style="vertical-align: top;"> 
2273     
2274     
2275      <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
2276
2277
2278
2279      </td>
2280
2281
2282 <td style="vertical-align: top;">C *
228310&nbsp; <br>
2284
2285
2286
2287(100)</td>
2288
2289
2290 <td style="vertical-align: top;"><i>100
2291* ' '</i></td>
2292
2293
2294 <td style="vertical-align: top;">
2295     
2296     
2297      <p>Quantities for which vertical profiles (horizontally averaged)
2298are to be output.&nbsp; </p>
2299
2300
2301 
2302     
2303     
2304      <p>By default vertical
2305profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>.
2306The file's format is NetCDF.&nbsp; Further details about processing
2307NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
2308
2309
2310     
2311     
2312      <p>For
2313historical reasons, data can also be output in ASCII-format on local
2314file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
2315which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See
2316parameter <a href="#data_output_format">data_output_format</a>
2317for defining the format in which data shall be output.<br>
2318
2319
2320 </p>
2321
2322
2323
2324     
2325     
2326      <p>For horizontally averaged vertical
2327profiles always <span style="font-weight: bold;">all</span>
2328vertical
2329grid points (0 &lt;= k &lt;= nz+1) are output to file. Vertical
2330profile data refers to the total domain but profiles for subdomains can
2331also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).&nbsp;
2332      </p>
2333
2334
2335 
2336     
2337     
2338      <p>The temporal interval of the output times of
2339profiles is
2340assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>.
2341Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
2342the profiles are ordered with respect to their
2343output times.</p>
2344
2345
2346     
2347     
2348      <p>Profiles can also be temporally
2349averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>).&nbsp;<br>
2350
2351
2352
2353      </p>
2354
2355
2356 
2357     
2358     
2359      <p>The following list shows the values which can be
2360assigned to <span style="font-weight: bold;">data_output_pr</span>.
2361The profile data is either defined on
2362u-v-levels (variables marked in <font color="#ff6600">red</font>)
2363or
2364on w-levels (<font color="#33ff33">green</font>).
2365According to this,
2366the
2367z-coordinates of the individual profiles vary. Beyond that, with a
2368Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>)
2369the lowest output
2370level is z = zu(1) instead of z = zw(0) for profiles <i>w''
2371u'',w''v"</i>, <i>wu</i> and <i>wv</i>
2372.&nbsp; <br>
2373
2374
2375 </p>
2376
2377
2378 
2379     
2380     
2381      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
2382
2383
2384 <tbody>
2385
2386
2387 <tr>
2388
2389
2390 <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
2391
2392
2393
2394            <td style="vertical-align: top;">u-component of the
2395velocity (in m/s).</td>
2396
2397
2398 </tr>
2399
2400
2401 <tr>
2402
2403
2404 <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
2405
2406
2407
2408            <td style="vertical-align: top;">v-component of the
2409velocity (in m/s).</td>
2410
2411
2412 </tr>
2413
2414
2415 <tr>
2416
2417
2418 <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
2419
2420
2421
2422            <td style="vertical-align: top;">w-component of the
2423velocity (in m/s).</td>
2424
2425
2426 </tr>
2427
2428
2429 <tr>
2430
2431
2432 <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
2433
2434
2435
2436            <td style="vertical-align: top;">Potential temperature (in
2437K).</td>
2438
2439
2440 </tr>
2441
2442
2443 <tr>
2444
2445
2446 <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
2447
2448
2449
2450            <td style="vertical-align: top;">Virtual potential
2451temperature (in K).</td>
2452
2453
2454 </tr>
2455
2456
2457 <tr>
2458
2459
2460 <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
2461
2462
2463
2464            <td style="vertical-align: top;">Potential liquid water
2465temperature (in K).</td>
2466
2467
2468 </tr>
2469
2470
2471 <tr>
2472
2473
2474 <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
2475
2476
2477
2478            <td style="vertical-align: top;">Total water content
2479(in kg/kg).</td>
2480
2481
2482 </tr>
2483
2484
2485 <tr>
2486
2487
2488 <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
2489
2490
2491
2492            <td style="vertical-align: top;">Specific humidity (in
2493kg/kg).</td>
2494
2495
2496 </tr>
2497
2498
2499 <tr>
2500
2501
2502 <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
2503
2504
2505
2506            <td style="vertical-align: top;">Liquid water content
2507(in kg/kg).</td>
2508
2509
2510 </tr>
2511
2512
2513 <tr>
2514
2515
2516            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 102, 0);">rho</span></td>
2517
2518
2519            <td align="undefined" valign="undefined">Potential density (in kg/m<sup>3</sup>).</td>
2520
2521
2522          </tr>
2523
2524
2525          <tr>
2526
2527
2528 <td style="vertical-align: middle; font-style: italic;"><font color="#ff6600">s</font></td>
2529
2530
2531
2532            <td style="vertical-align: top;">Scalar concentration (in
2533kg/m<sup>3</sup>).</td>
2534
2535
2536 </tr>
2537
2538
2539 <tr>
2540
2541
2542            <td align="undefined" valign="undefined"><span style="font-style: italic; background-color: rgb(255, 255, 255); color: rgb(255, 102, 0);">sa</span></td>
2543
2544
2545            <td align="undefined" valign="undefined">Salinity (in psu).</td>
2546
2547
2548          </tr>
2549
2550
2551          <tr>
2552
2553
2554 <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
2555
2556
2557
2558            <td style="vertical-align: top;">Turbulent kinetic energy
2559(TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td>
2560
2561
2562
2563          </tr>
2564
2565
2566 <tr>
2567
2568
2569 <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
2570
2571
2572
2573            <td style="vertical-align: top;">Perturbation energy
2574(resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td>
2575
2576
2577
2578          </tr>
2579
2580
2581 <tr>
2582
2583
2584 <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
2585
2586
2587
2588            <td style="vertical-align: top;">Eddy diffusivity for
2589momentum (in m<sup>2</sup>/s).</td>
2590
2591
2592 </tr>
2593
2594
2595 <tr>
2596
2597
2598
2599            <td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
2600
2601
2602
2603            <td style="vertical-align: top;">Eddy diffusivity for heat
2604(in m<sup>2</sup>/s).</td>
2605
2606
2607 </tr>
2608
2609
2610 <tr>
2611
2612
2613 <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
2614
2615
2616
2617            <td style="vertical-align: top;">Mixing length (in m).</td>
2618
2619
2620
2621          </tr>
2622
2623
2624 <tr>
2625
2626
2627 <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
2628
2629
2630
2631            <td style="vertical-align: top;">u-component of the
2632subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
2633
2634
2635
2636          </tr>
2637
2638
2639 <tr>
2640
2641
2642 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td>
2643
2644
2645
2646            <td style="vertical-align: top;">u-component of the
2647resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
2648
2649
2650
2651          </tr>
2652
2653
2654 <tr>
2655
2656
2657 <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
2658
2659
2660
2661            <td style="vertical-align: top;">u-component of the total
2662vertical momentum flux (<i>w"u"</i> + <i>w*u*</i>)
2663(in m<sup>2</sup>/s<sup>2</sup>).</td>
2664
2665
2666 </tr>
2667
2668
2669
2670          <tr>
2671
2672
2673 <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
2674
2675
2676
2677            <td style="vertical-align: top;">v-component of the
2678subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
2679
2680
2681
2682          </tr>
2683
2684
2685 <tr>
2686
2687
2688 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td>
2689
2690
2691
2692            <td style="vertical-align: top;">v-component of the
2693resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
2694
2695
2696
2697          </tr>
2698
2699
2700 <tr>
2701
2702
2703 <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
2704
2705
2706
2707            <td style="vertical-align: top;">v-component of the total
2708vertical momentum flux (<i>w"v"</i> + <i>w*v*</i>)
2709(in m<sup>2</sup>/s<sup>2</sup>).</td>
2710
2711
2712 </tr>
2713
2714
2715
2716          <tr>
2717
2718
2719 <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
2720
2721
2722
2723            <td style="vertical-align: top;">Subgrid-scale vertical
2724sensible heat flux (in K m/s).</td>
2725
2726
2727 </tr>
2728
2729
2730 <tr>
2731
2732
2733 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
2734
2735
2736
2737            <td style="vertical-align: top;">Resolved vertical
2738sensible
2739heat flux (in K m/s).</td>
2740
2741
2742 </tr>
2743
2744
2745 <tr>
2746
2747
2748 <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
2749
2750
2751
2752            <td style="vertical-align: top;">Total vertical sensible
2753heat flux (<i>w"pt"</i> + <i>w*pt*</i>)
2754(in K
2755m/s).</td>
2756
2757
2758 </tr>
2759
2760
2761 <tr>
2762
2763
2764 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td>
2765
2766
2767
2768            <td style="vertical-align: top;">Subgrid-scale vertical
2769sensible heat flux using the
2770Bott-Chlond scheme (in K m/s).</td>
2771
2772
2773 </tr>
2774
2775
2776 <tr>
2777
2778
2779 <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
2780
2781
2782
2783            <td style="vertical-align: top;">Total vertical sensible
2784heat flux using the Bott-Chlond scheme
2785(<i>w"pt"</i>
2786+ <i>w*pt*BC</i>) (in K m/s).</td>
2787
2788
2789 </tr>
2790
2791
2792 <tr>
2793
2794
2795
2796            <td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
2797
2798
2799
2800            <td style="vertical-align: top;">Subgrid-scale vertical
2801buoyancy flux (in K m/s).</td>
2802
2803
2804 </tr>
2805
2806
2807 <tr>
2808
2809
2810 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
2811
2812
2813
2814            <td style="vertical-align: top;">Resolved vertical
2815buoyancy
2816flux (in K m/s).</td>
2817
2818
2819 </tr>
2820
2821
2822 <tr>
2823
2824
2825 <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
2826
2827
2828
2829            <td style="vertical-align: top;">Total vertical buoyancy
2830flux (w"vpt" + w*vpt*) (in K m/s).</td>
2831
2832
2833 </tr>
2834
2835
2836 <tr>
2837
2838
2839 <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
2840
2841
2842
2843            <td style="vertical-align: top;">Subgrid-scale vertical
2844water flux (in kg/kg m/s).</td>
2845
2846
2847 </tr>
2848
2849
2850 <tr>
2851
2852
2853 <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td>
2854
2855
2856
2857            <td style="vertical-align: top;">Resolved vertical water
2858flux (in kg/kg m/s).</td>
2859
2860
2861 </tr>
2862
2863
2864 <tr>
2865
2866
2867 <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
2868
2869
2870
2871            <td style="vertical-align: top;">Total vertical water flux
2872(w"q" + w*q*) (in kg/kg m/s).</td>
2873
2874
2875 </tr>
2876
2877
2878 <tr>
2879
2880
2881 <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
2882
2883
2884
2885            <td style="vertical-align: top;">Subgrid-scale vertical
2886latent heat flux (in kg/kg m/s).</td>
2887
2888
2889 </tr>
2890
2891
2892 <tr>
2893
2894
2895 <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td>
2896
2897
2898
2899            <td style="vertical-align: top;">Resolved vertical latent
2900heat flux (in kg/kg m/s).</td>
2901
2902
2903 </tr>
2904
2905
2906 <tr>
2907
2908
2909 <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
2910
2911
2912
2913            <td style="vertical-align: top;">Total vertical latent
2914heat
2915flux (w"qv" + w*qv*) (in kg/kg m/s).</td>
2916
2917
2918 </tr>
2919
2920
2921 <tr>
2922
2923
2924
2925            <td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
2926
2927
2928
2929            <td style="vertical-align: top;">Subgrid-scale vertical
2930scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td>
2931
2932
2933
2934          </tr>
2935
2936
2937 <tr>
2938
2939
2940 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td>
2941
2942
2943
2944            <td style="vertical-align: top;">Resolved vertical scalar
2945concentration flux (in kg/m<sup>3</sup> m/s).</td>
2946
2947
2948 </tr>
2949
2950
2951
2952          <tr>
2953
2954
2955 <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
2956
2957
2958
2959            <td style="vertical-align: top;">Total vertical scalar
2960concentration flux (w"s" + w*s*) (in kg/m<sup>3 </sup>m/s).</td>
2961
2962
2963
2964          </tr>
2965
2966
2967 <tr>
2968
2969
2970            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w"sa"</span></td>
2971
2972
2973            <td align="undefined" valign="undefined">Subgrid-scale vertical
2974salinity flux (in psu<sup> </sup>m/s).</td>
2975
2976
2977          </tr>
2978
2979
2980          <tr>
2981
2982
2983            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w*sa*</span></td>
2984
2985
2986            <td align="undefined" valign="undefined">Resolved vertical salinity flux (in psu m/s).</td>
2987
2988
2989          </tr>
2990
2991
2992          <tr>
2993
2994
2995            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td>
2996
2997
2998            <td align="undefined" valign="undefined">Total vertical salinity flux (w"sa" + w*sa*) (in psu<sup> </sup>m/s).</td>
2999
3000
3001          </tr>
3002
3003
3004          <tr>
3005
3006
3007 <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td>
3008
3009
3010
3011            <td style="vertical-align: top;">Vertical flux of
3012perturbation energy (resolved)</td>
3013
3014
3015 </tr>
3016
3017
3018 <tr>
3019
3020
3021 <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
3022
3023
3024
3025            <td style="vertical-align: top;">Variance of the
3026u-velocity
3027component (resolved)</td>
3028
3029
3030 </tr>
3031
3032
3033 <tr>
3034
3035
3036 <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
3037
3038
3039
3040            <td style="vertical-align: top;">Variance of the
3041v-velocity
3042component (resolved)</td>
3043
3044
3045 </tr>
3046
3047
3048 <tr>
3049
3050
3051 <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
3052
3053
3054
3055            <td style="vertical-align: top;">Variance of the potential
3056temperature (resolved)</td>
3057
3058
3059 </tr>
3060
3061
3062 <tr>
3063
3064
3065 <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
3066
3067
3068
3069            <td style="vertical-align: top;">Variance of the potential
3070temperature (resolved)</td>
3071
3072
3073 </tr>
3074
3075
3076 <tr>
3077
3078
3079 <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
3080
3081
3082
3083            <td style="vertical-align: top;">Third moment of the
3084w-velocity component (resolved)</td>
3085
3086
3087 </tr>
3088
3089
3090 <tr>
3091
3092
3093 <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
3094
3095
3096
3097            <td style="vertical-align: top;">Skewness of the
3098w-velocity
3099component (resolved, S<sub>w</sub>
3100= W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td>
3101
3102
3103
3104          </tr>
3105
3106
3107 <tr>
3108
3109
3110 <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td>
3111
3112
3113
3114            <td style="vertical-align: top;">Third moment (resolved)</td>
3115
3116
3117
3118          </tr>
3119
3120
3121 <tr>
3122
3123
3124 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td>
3125
3126
3127
3128            <td style="vertical-align: top;">Third moment (resolved)</td>
3129
3130
3131
3132          </tr>
3133
3134
3135 <tr>
3136
3137
3138 <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*/dz</i></font></td>
3139
3140
3141
3142            <td style="vertical-align: top;">Energy production by
3143shear
3144(resolved)</td>
3145
3146
3147 </tr>
3148
3149
3150 <tr>
3151
3152
3153 <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*/dz</i></font></td>
3154
3155
3156
3157            <td style="vertical-align: top;">Energy production by
3158turbulent transport of pressure
3159fluctuations (resolved)</td>
3160
3161
3162 </tr>
3163
3164
3165 <tr>
3166
3167
3168 <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
3169
3170
3171
3172            <td style="vertical-align: top;">Energy production by
3173transport of resolved-scale TKE</td>
3174
3175
3176 </tr>
3177
3178
3179 
3180       
3181       
3182        </tbody>
3183     
3184     
3185      </table>
3186
3187
3188 <br>
3189
3190
3191Beyond that, initial profiles (t=0) of some
3192variables can additionally be
3193output (this output is only done once
3194with the first plot output and not repeated with the profile output at
3195later
3196times). The names of these profiles result from the ones specified
3197above leaded by a hash "#".&nbsp; Allowed values are:<br>
3198
3199
3200 
3201     
3202     
3203      <ul>
3204
3205
3206
3207       
3208       
3209        <p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
3210        <i>#km</i>, <i>#kh</i>, <i>#l, #lpt, #q, #qv, #s, #sa, #vpt</i></p>
3211
3212
3213
3214     
3215     
3216      </ul>
3217
3218
3219 
3220     
3221     
3222      <p>Profile names preceded by a hash automatically imply that
3223profiles for these variables are also output at later times. It is not
3224necessary and not allowed to specify the same profile name with and
3225without hash simultaneously(this would lead to an NetCDF error). </p>
3226      <p>These initial profiles have been either set by
3227the user or
3228have been calculated by a 1d-model prerun.</p>
3229
3230
3231The
3232user is allowed to extend the above list of quantities by defining his
3233own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>).<br>
3234
3235
3236      <br>
3237
3238
3239In case
3240of ASCII data output to local file PLOT1D_DATA,
3241PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
3242which 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>.
3243Profiles can be directly plotted with <span style="font-weight: bold;">profil</span>
3244using these two files. The
3245plot layout is
3246steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters
3247are determined by
3248a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>,
3249      <a href="chapter_4.2.html#profile_rows">profile_rows</a>,
3250      <a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
3251      <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
3252etc.) All parameter values can be changed by editing the parameter
3253input
3254file. <br>
3255
3256
3257      <br>
3258
3259
3260Further details about plotting vertical
3261profiles with <span style="font-weight: bold;">profil </span>can
3262be found in <a href="chapter_4.5.2.html">chapter
32634.5.2</a></td>
3264
3265
3266 </tr>
3267
3268
3269 <tr>
3270
3271
3272 <td style="vertical-align: top;"> 
3273     
3274     
3275      <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
3276      <br>
3277
3278
3279 <b>_each_pe</b></p>
3280
3281
3282 </td>
3283
3284
3285 <td style="vertical-align: top;">L<br>
3286
3287
3288 </td>
3289
3290
3291 <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
3292
3293
3294 </td>
3295
3296
3297
3298      <td style="vertical-align: top;">Output 2d cross section
3299data by one or
3300all processors.&nbsp; 
3301     
3302     
3303      <p>In runs with several processors, by
3304default, each processor
3305outputs cross section data of its subdomain&nbsp;into an individual
3306file. After PALM
3307has finished, the contents of these files have to be sampled into one
3308file<span style="font-weight: bold;"></span> using
3309the program <tt>combine_plot_fields.x</tt>.&nbsp; </p>
3310
3311
3312
3313     
3314     
3315      <p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
3316= <i>.F.,</i>
3317the respective data is gathered on PE0 and output is done directly
3318into one file, so <tt>combine_plot_fields.x</tt> does not
3319have to be
3320called. However, in case of very large numbers of horizontal
3321gridpoints, sufficient
3322memory is required on PE0. </p>
3323
3324
3325 </td>
3326
3327
3328 </tr>
3329
3330
3331
3332    <tr>
3333
3334
3335 <td style="vertical-align: top;"> 
3336     
3337     
3338      <p><a name="disturbance_amplitude"></a><b>disturbance<br>
3339
3340
3341
3342_amplitude</b></p>
3343
3344
3345 </td>
3346
3347
3348 <td style="vertical-align: top;">R</td>
3349
3350
3351 <td style="vertical-align: top;"><i>0.25</i></td>
3352
3353
3354
3355      <td style="vertical-align: top;"> 
3356     
3357     
3358      <p>Maximum
3359perturbation amplitude of the random perturbations
3360imposed to the horizontal velocity field (in m/s).&nbsp; </p>
3361
3362
3363
3364     
3365     
3366      <p>The parameter <a href="#create_disturbances">create_disturbances</a>
3367describes how to impose random perturbations to the horizontal velocity
3368field. Since the perturbation procedure includes two filter operations,
3369the amplitude assigned by <b>disturbance_amplitude</b> is
3370only an
3371approximate value of the real magnitude of the perturbation.</p>
3372
3373
3374 </td>
3375
3376
3377
3378    </tr>
3379
3380
3381 <tr>
3382
3383
3384 <td style="vertical-align: top;">
3385     
3386     
3387      <p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
3388      <br>
3389
3390
3391 <b>_limit</b></p>
3392
3393
3394 </td>
3395
3396
3397 <td style="vertical-align: top;">R</td>
3398
3399
3400 <td style="vertical-align: top;"><i>0.01</i></td>
3401
3402
3403
3404      <td style="vertical-align: top;"> 
3405     
3406     
3407      <p lang="en-GB">Upper
3408limit value of the perturbation energy of
3409the velocity field used as a criterion for imposing random
3410perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
3411      </p>
3412
3413
3414 
3415     
3416     
3417      <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">
3418describes how to impose
3419random perturbations to the horizontal velocity field. The perturbation
3420energy is defined as the volume average (over the total model domain)
3421of the squares of the deviations of the velocity components from the
3422mean flow (horizontal average). If the perturbation energy exceeds the
3423assigned value, random perturbations to the fields of horizontal
3424velocities are imposed no more. The value of this parameter usually
3425must be determined by trial and error (it depends e.g. on the total
3426number of grid points).</span> </font> </p>
3427
3428
3429 </td>
3430
3431
3432
3433    </tr>
3434
3435
3436 <tr>
3437
3438
3439 <td style="vertical-align: top;">
3440     
3441     
3442      <p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
3443
3444
3445
3446      </td>
3447
3448
3449 <td style="vertical-align: top;">R</td>
3450
3451
3452
3453      <td style="vertical-align: top;"><i>zu(3) or<br>
3454
3455
3456zu(nz*2/3)<br>
3457
3458
3459see right</i></td>
3460
3461
3462
3463      <td style="vertical-align: top;"> 
3464     
3465     
3466      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
3467limit of the vertical range for which random perturbations are to be
3468imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
3469      </font></font> </p>
3470
3471
3472 
3473     
3474     
3475      <p><span lang="en-GB"><font face="Thorndale, serif">This
3476parameter must hold the condition zu(3) &lt;= <b>disturbance_level_b</b>
3477&lt;= zu(</font></span><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-2</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span><span lang="en-GB"><font face="Thorndale, serif">. Additionally, <b>disturbance_level_b</b>
3478&lt;= </font></span><a href="#disturbance_level_t"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_t</font></span></a>
3479      <span lang="en-GB"><font face="Thorndale, serif">must
3480also hold.</font></span></p>
3481
3482
3483     
3484     
3485      <p><span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">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></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>
3486
3487
3488 
3489     
3490     
3491      <p><span lang="en-GB"><font face="Thorndale, serif">The
3492parameter </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">
3493describes how to impose
3494random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
3495      </font> </p>
3496
3497
3498 </td>
3499
3500
3501 </tr>
3502
3503
3504 <tr>
3505
3506
3507 <td style="vertical-align: top;"> 
3508     
3509     
3510      <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
3511
3512
3513
3514      </td>
3515
3516
3517 <td style="vertical-align: top;">R</td>
3518
3519
3520
3521      <td style="vertical-align: top;"><i>zu(nz/3) or<br>
3522
3523
3524zu(nzt-3)<br>
3525
3526
3527see right</i></td>
3528
3529
3530
3531      <td style="vertical-align: top;"> 
3532     
3533     
3534      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
3535limit of the vertical range for which random perturbations are to be
3536imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).&nbsp;
3537      </font></font> </p>
3538
3539
3540 
3541     
3542     
3543      <p><span lang="en-GB"><font face="Thorndale, serif">This
3544parameter must hold the condition <b>disturbance_level_t</b>
3545&lt;= zu<i>(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-2</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">.
3546Additionally, </font></span><a href="#disturbance_level_b"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_b</font></span></a>
3547      <span lang="en-GB"><font face="Thorndale, serif">&lt;=
3548      <b>disturbance_level_t</b>
3549must also hold.</font></span></p>
3550
3551
3552      <span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_t</span> = <span style="font-style: italic;">zu(nzt - 3</span>)</span></span><span lang="en-GB"><span style="font-family: Thorndale,serif;"><span style="font-style: italic;"> </span>(negative)</span></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">.</span></span>
3553     
3554     
3555      <p><span lang="en-GB"><font face="Thorndale, serif">The
3556parameter </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">
3557describes how to impose
3558random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
3559      </font> </p>
3560
3561
3562 </td>
3563
3564
3565 </tr>
3566
3567
3568 <tr>
3569
3570
3571 <td style="vertical-align: top;"> 
3572     
3573     
3574      <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
3575
3576
3577
3578      </td>
3579
3580
3581 <td style="vertical-align: top;">L<br>
3582
3583
3584 </td>
3585
3586
3587
3588      <td style="vertical-align: top;">.F.<br>
3589
3590
3591 </td>
3592
3593
3594
3595      <td style="vertical-align: top;"> 
3596     
3597     
3598      <p>Output of 2d
3599cross section data at the beginning of a run.&nbsp; </p>
3600
3601
3602 
3603     
3604     
3605      <p>The
3606temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>)
3607are 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>
3608and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>.
3609By assigning <b>do2d_at_begin</b> = <i>.T.</i>
3610an additional output
3611will be made at the
3612beginning of a run (thus at the time t = 0 or at the respective
3613starting times of restart runs).</p>
3614
3615
3616 </td>
3617
3618
3619 </tr>
3620
3621
3622 <tr>
3623
3624
3625
3626      <td style="vertical-align: top;"> 
3627     
3628     
3629      <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
3630
3631
3632
3633      </td>
3634
3635
3636 <td style="vertical-align: top;">L<br>
3637
3638
3639 </td>
3640
3641
3642
3643      <td style="vertical-align: top;">.F.<br>
3644
3645
3646 </td>
3647
3648
3649
3650      <td style="vertical-align: top;">Output of 3d volume data
3651at the beginning
3652of a run.<br>
3653
3654
3655      <br>
3656
3657
3658The temporal intervals of output times of
36593d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
3660is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>.
3661By assigning <b>do3d_at_begin</b> = <i>.T.</i>
3662an additional output
3663will be made at the
3664beginning of a run (thus at the time t = 0 or at the respective
3665starting times of restart runs).</td>
3666
3667
3668 </tr>
3669
3670
3671 <tr>
3672
3673
3674 <td style="vertical-align: top;"> 
3675     
3676     
3677      <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
3678
3679
3680
3681      </td>
3682
3683
3684 <td style="vertical-align: top;">L<br>
3685
3686
3687 </td>
3688
3689
3690
3691      <td style="vertical-align: top;">.F.<br>
3692
3693
3694 </td>
3695
3696
3697
3698      <td style="vertical-align: top;"> 
3699     
3700     
3701      <p>Output of data
3702for 3d plots in compressed form.&nbsp; </p>
3703
3704
3705 
3706     
3707     
3708      <p>This
3709parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
3710= <span style="font-style: italic;">'avs'</span>.</p>
3711
3712
3713     
3714     
3715      <p>Output
3716of 3d volume data may need huge amounts of disc storage
3717(up to several Terabytes ore more). Data compression can serve to
3718reduce this requirement. PALM is able to output 3d data in compressed
3719form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span>
3720= <span style="font-style: italic;">.T.</span> is
3721assigned. This
3722yields a loss of accuracy, but the file size is clearly reduced. The
3723parameter <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>
3724can be used to separately define the number of significant digits for
3725each quantity.<br>
3726
3727
3728 </p>
3729
3730
3731 
3732     
3733     
3734      <p>So far compressed data
3735output is only possible for Cray-T3E
3736machines. Additional information for
3737handling compressed data is given in <a href="chapter_4.5.6.html">chapter
37384.5.6</a>.</p>
3739
3740
3741 </td>
3742
3743
3744 </tr>
3745
3746
3747 <tr>
3748
3749
3750 <td style="vertical-align: top;"> 
3751     
3752     
3753      <p><a name="do3d_precision"></a><b>do3d_precision</b></p>
3754
3755
3756
3757      </td>
3758
3759
3760 <td style="vertical-align: top;">C *
37617&nbsp; <br>
3762
3763
3764
3765&nbsp; (100)</td>
3766
3767
3768 <td style="vertical-align: top;">see
3769right<br>
3770
3771
3772 </td>
3773
3774
3775 <td style="vertical-align: top;">
3776     
3777     
3778      <p>Significant digits in case of compressed data
3779output.&nbsp; </p>
3780
3781
3782 
3783     
3784     
3785      <p>This parameter only applies for
3786&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
3787= <span style="font-style: italic;">'avs'</span>.</p>
3788
3789
3790     
3791     
3792      <p>In
3793case that data compression is used for output of 3d data
3794(see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>),
3795this parameter determines the number of significant digits
3796which are to be output.<br>
3797
3798
3799 </p>
3800
3801
3802 
3803     
3804     
3805      <p>Fewer digits
3806clearly reduce the amount
3807of data. Assignments have to be given separately for each individual
3808quantity via a character string of the form <span style="font-style: italic;">'&lt;quantity
3809name&gt;&lt;number of
3810significant digits&gt;'</span>, e.g. <span style="font-style: italic;">'pt2'</span>.
3811Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a>
3812are admitted. Up to 9 significant digits are allowed (but large values
3813are not very reasonable
3814because they do not effect a significant compression).<br>
3815
3816
3817 </p>
3818
3819
3820
3821     
3822     
3823      <p>The default assignment is <span style="font-weight: bold;">do3d_precision</span>
3824= <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>
3825
3826
3827 </td>
3828
3829
3830
3831    </tr>
3832
3833
3834    <tr>
3835
3836
3837 <td style="vertical-align: top;"> 
3838     
3839     
3840      <p><a name="dt_laufparameter"></a><b>dt</b></p>
3841
3842
3843
3844      </td>
3845
3846
3847 <td style="vertical-align: top;">R</td>
3848
3849
3850
3851      <td style="vertical-align: top;"><i>variable</i></td>
3852
3853
3854
3855      <td style="vertical-align: top;"> 
3856     
3857     
3858      <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Time
3859step to be used by the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
3860      </font></font> </p>
3861
3862
3863 
3864     
3865     
3866      <p><span lang="en-GB"><font face="Thorndale, serif">This parameter</font></span>
3867      <font face="Thorndale, serif"><span lang="en-GB">is
3868described in
3869detail with the initialization parameters (see</span></font><span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB">).
3870Additionally, it may be
3871used as a run parameter and then applies to all restart runs (until it
3872is changed again). A switch from a constant time step to a variable
3873time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span>
3874      </font> </p>
3875
3876
3877 </td>
3878
3879
3880 </tr>
3881
3882
3883 <tr>
3884
3885
3886 <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
3887
3888
3889
3890      </td>
3891
3892
3893 <td style="vertical-align: top;">R<br>
3894
3895
3896 </td>
3897
3898
3899
3900      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
3901
3902
3903 </td>
3904
3905
3906
3907      <td style="vertical-align: top;">Temporal interval
3908of&nbsp;data which are subject to temporal averaging (in s).<br>
3909
3910
3911      <br>
3912
3913
3914By
3915default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>
3916are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span>
3917&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>,
3918the number of time levels entering the average can be minimized. This
3919reduces the CPU-time of a run but may worsen the quality of the
3920average's statistics.<br>
3921
3922
3923      <br>
3924
3925
3926      <font face="Thorndale, serif"><span lang="en-GB">With
3927variable time step (see <span style="font-weight: bold;">dt</span>),
3928the number of time levels entering the average can vary from one
3929averaging interval to the next (for a more detailed explanation see </span></font><font><a href="#averaging_interval"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval</font></span></a>)</font><font face="Thorndale, serif"><span lang="en-GB">. It
3930is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> /
3931MAX(<span style="font-weight: bold;"> dt_averaging_input</span>,
3932      <span style="font-weight: bold;">dt</span>) (which
3933gives a more or less exact value if a fixed timestep is used and if
3934this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font>&nbsp;
3935      <br>
3936
3937
3938      <br>
3939
3940
3941      <span style="font-weight: bold;">Example:</span><br>
3942
3943
3944With
3945an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> =
3946      <span style="font-style: italic;">10.0</span>,
3947the time levels entering the average have a (minimum) distance of 10.0
3948s (their distance may of course be larger if the current timestep is
3949larger than 10.0 s), so the average is calculated from the data of
3950(maximum) 10 time levels.<br>
3951
3952
3953      <br>
3954
3955
3956      <font face="Thorndale, serif"><span lang="en-GB">It
3957is allowed
3958to change <b>dt_averaging_input</b> during a job chain. If
3959the last averaging
3960interval of the run previous to the change could not be completed (i.e.
3961has to be finished in the current run), the individual profiles and/or
3962spectra entering the averaging are not uniformly distributed over the
3963averaging interval.<br>
3964
3965
3966      <br>
3967
3968
3969      </span></font>Parameter&nbsp;<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>&nbsp;can
3970be used to define&nbsp;a different temporal interval&nbsp;for
3971vertical profile data and spectra.<br>
3972
3973
3974 </td>
3975
3976
3977 </tr>
3978
3979
3980
3981    <tr>
3982
3983
3984 <td style="vertical-align: top;"> 
3985     
3986     
3987      <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
3988
3989
3990
3991      </td>
3992
3993
3994 <td style="vertical-align: top;">R</td>
3995
3996
3997
3998      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>
3999
4000
4001averaging_<br>
4002
4003
4004input</a></span></td>
4005
4006
4007
4008      <td style="vertical-align: top;"> 
4009     
4010     
4011      <p lang="en-GB">Temporal
4012interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
4013profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
4014      </font></font> </p>
4015
4016
4017 
4018     
4019     
4020      <p>By default, data from
4021each 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
4022used for calculating the temporal average.&nbsp;By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span>
4023&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>,
4024the number of time levels entering the average can be minimized. This
4025reduces the CPU-time of a run but may worsen the quality of the
4026average'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>
4027
4028
4029 </p>
4030
4031
4032     
4033     
4034      <p>For
4035more 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>
4036
4037
4038      </td>
4039
4040
4041
4042    </tr>
4043
4044
4045 <tr>
4046
4047
4048      <td style="vertical-align: top;"><a name="dt_coupling"></a><span style="font-weight: bold;">dt_coupling</span></td>
4049
4050
4051      <td style="vertical-align: top;">R</td>
4052
4053
4054      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
4055
4056
4057      <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>
4058
4059
4060      <br>
4061
4062
4063This parameter has an effect only in case of a run with coupled models. It is available starting from version 3.3a. <br>
4064
4065
4066      <br>
4067
4068
4069This parameter specifies the temporal interval at which data are
4070exchanged at the interface between coupled models (currently: interface
4071between atmosphere and ocean). If this parameter is not explicitly
4072specified in the parameter files for both coupled models, or if there
4073is an inconsistency between its values for both coupled models,
4074the&nbsp;execution will terminate and an informative error message will
4075be given.&nbsp;In order to ensure synchronous coupling throughout the simulation, <span style="font-weight: bold;">dt_coupling</span> should be chosen larger than
4076      <a href="#dt_max">dt_max</a>.</td>
4077
4078
4079    </tr>
4080
4081
4082    <tr>
4083
4084
4085 <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
4086
4087
4088
4089      </td>
4090
4091
4092 <td style="vertical-align: top;">R<br>
4093
4094
4095 </td>
4096
4097
4098
4099      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
4100
4101
4102
4103      </td>
4104
4105
4106 <td style="vertical-align: top;">
4107     
4108     
4109      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
4110at which&nbsp;data (3d volume data (instantaneous or time
4111averaged),
4112cross sections (instantaneous or time averaged), vertical profiles,
4113spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
4114
4115
4116
4117      <span lang="en-GB"><font face="Thorndale">If
4118data 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
4119parameter can be used to
4120assign the temporal interval at which these data shall be
4121output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
4122simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>,
4123which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
4124time is the beginning of the simulation, i.e. output
4125takes place at times t = <b>skip_time_data_output +
4126dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
4127+ 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
4128+ 3*<b>dt_data_output</b>,
4129etc. Since output is only done at the discrete time levels given by
4130the&nbsp;timestep used, the actual output times can slightly
4131deviate
4132from 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>
4133
4134
4135      <br>
4136
4137
4138Individual temporal
4139intervals for the different output quantities can be assigned using
4140parameters <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>,
4141and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span>
4142      </td>
4143
4144
4145 </tr>
4146
4147
4148 <tr>
4149
4150
4151 <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
4152
4153
4154
4155      </td>
4156
4157
4158 <td style="vertical-align: top;">R<br>
4159
4160
4161 </td>
4162
4163
4164
4165      <td style="vertical-align: top;"><i>value of
4166&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
4167
4168
4169output</a></i>
4170      </td>
4171
4172
4173 <td style="vertical-align: top;">
4174     
4175     
4176      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
4177at which time averaged 3d volume data and/or 2d cross section data
4178shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
4179
4180
4181      <span lang="en-GB"><font face="Thorndale">If data
4182output 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
4183parameter can be used to
4184assign the temporal interval at which they shall be
4185output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
4186simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>,
4187which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
4188time is the beginning of the simulation, i.e. output
4189takes place at times t = <b>skip_time_data_output_av +
4190dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
4191+ 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
4192+ 3*<b>dt_data_output_av</b>,
4193etc. Since output is only done at the discrete time levels given by
4194the&nbsp;timestep used, the actual output times can slightly
4195deviate from
4196these 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>
4197
4198
4199      <br>
4200
4201
4202      </font></span>The
4203length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td>
4204
4205
4206
4207    </tr>
4208
4209
4210    <tr>
4211
4212
4213 <td style="vertical-align: top;"> 
4214     
4215     
4216      <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
4217
4218
4219
4220      </td>
4221
4222
4223 <td style="vertical-align: top;">R</td>
4224
4225
4226
4227      <td style="vertical-align: top;"><i>9999999.9</i></td>
4228
4229
4230
4231      <td style="vertical-align: top;"> 
4232     
4233     
4234      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
4235interval</font> at which random
4236perturbations are to be imposed on the horizontal velocity field
4237(</font>in <font face="Thorndale">s).&nbsp; </font>
4238      </p>
4239
4240
4241 
4242     
4243     
4244      <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">
4245describes how to impose
4246random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
4247      </font> </p>
4248
4249
4250 </td>
4251
4252
4253 </tr>
4254
4255
4256 <tr>
4257
4258
4259 <td style="vertical-align: top;"> 
4260     
4261     
4262      <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
4263
4264
4265
4266      </td>
4267
4268
4269 <td style="vertical-align: top;">R</td>
4270
4271
4272
4273      <td style="vertical-align: top;"><i>value of
4274&nbsp;<a href="#dt_data_output">dt_data_<br>
4275
4276
4277output</a></i></td>
4278
4279
4280
4281      <td style="vertical-align: top;"> 
4282     
4283     
4284      <p><span lang="en-GB"><font face="Thorndale">Temporal
4285interval at
4286which data&nbsp;of vertical profiles shall be output (to local
4287file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
4288or/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
4289      <span lang="en-GB"><font face="Thorndale">s).&nbsp;
4290      </font></span> </p>
4291
4292
4293 
4294     
4295     
4296      <p><span lang="en-GB"><font face="Thorndale">If output of
4297horizontally 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
4298parameter can be used to
4299assign 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
4300be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has
4301zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
4302time is the beginning
4303of the simulation, thus t = 0,&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">i.e. output
4304takes 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>,
4305      <span style="font-weight: bold;">skip_time_dopr</span>
4306+ 3*<b>dt_dopr</b>,
4307etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
4308profiles can not be calculated for times lying within a time step
4309interval, the output times can deviate from these theoretical values.
4310If a time step ranges from t = 1799.8 to t = 1800.2, then in the
4311example above the output would take place at t = 1800.2. In general,
4312the 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
4313model uses a variable time step, these
4314deviations from the theoretical output times will of course be
4315different for each output time.<br>
4316
4317
4318 </font></span></p>
4319
4320
4321
4322     
4323     
4324      <p><span lang="en-GB"><font face="Thorndale">In
4325order to
4326guarantee 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;
4327      <span style="font-weight: bold;">end_time</span>
4328should be equal or a little bit
4329larger than the respective theoretical output time. For example, if <b>dt_dopr</b>
4330= <i>900.0</i><span style="font-style: italic;">
4331      </span>and 3600.0
4332seconds are to be simulated, then <b>end_time</b>
4333&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>
4334      </p>
4335
4336
4337 
4338     
4339     
4340      <p><span lang="en-GB"><font face="Thorndale">A selection of
4341profiles 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>
4342      </p>
4343
4344
4345 </td>
4346
4347
4348 </tr>
4349
4350
4351 <tr>
4352
4353
4354 <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
4355
4356
4357
4358      </td>
4359
4360
4361 <td style="vertical-align: top;">R<br>
4362
4363
4364 </td>
4365
4366
4367
4368      <td style="vertical-align: top;"><i>9999999.9</i></td>
4369
4370
4371
4372      <td style="vertical-align: top;"> 
4373     
4374     
4375      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
4376interval</font> at which data <font face="Thorndale">of
4377vertical
4378profiles 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
4379      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
4380      </p>
4381
4382
4383 
4384     
4385     
4386      <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
4387parameter can be used to
4388assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
4389time is the beginning
4390of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b>
4391= 1800.0,
4392then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since
4393profiles can not be calculated for times lying within a time step
4394interval, the output times can deviate from these theoretical values.
4395If a time step ranges from t = 1799.8 to t = 1800.2, then in the
4396example above the output would take place at t = 1800.2. In general,
4397the 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
4398are related to
4399the
4400example above). If the model uses a variable time step, these
4401deviations from the theoretical output times will of course be
4402different for each output time.<br>
4403
4404
4405 </font></span></p>
4406
4407
4408
4409     
4410     
4411      <p><span lang="en-GB"><font face="Thorndale">In
4412order to
4413guarantee 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;
4414      <span style="font-weight: bold;">end_time</span>
4415should be a little bit
4416larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b>
4417= <i>900.0</i><span style="font-style: italic;">
4418      </span>and 3600.0
4419seconds are to be simulated, then it should be at least&nbsp; <b>end_time</b>
4420&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
4421variable time steps are used
4422(which is the default), <span style="font-weight: bold;">dt</span>
4423should be properly estimated.&nbsp; </font></span> </p>
4424
4425
4426
4427     
4428     
4429      <p><span lang="en-GB"><font face="Thorndale">Data
4430and output
4431format 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>
4432      <span lang="en-GB"><font face="Thorndale">is
4433internally fixed. In this file
4434the profiles of the most important model variables are arranged in
4435adjacent columns.</font></span> </p>
4436
4437
4438 </td>
4439
4440
4441 </tr>
4442
4443
4444
4445    <tr>
4446
4447
4448 <td style="vertical-align: top;"> 
4449     
4450     
4451      <p><a name="dt_dots"></a><b>dt_dots</b></p>
4452
4453
4454
4455      </td>
4456
4457
4458 <td style="vertical-align: top;">R</td>
4459
4460
4461
4462      <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
4463
4464
4465
4466      <td style="vertical-align: top;"> 
4467     
4468     
4469      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
4470interval</font> at which&nbsp;time series data shall be
4471output (</font>in <font face="Thorndale">s).&nbsp;</font>
4472      </p>
4473
4474
4475 
4476     
4477     
4478      <p>The default interval for the output of timeseries
4479is calculated as shown below (this tries to minimize the number of
4480calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p>
4481
4482
4483     
4484     
4485      <p style="font-family: Courier New,Courier,monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4486IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
4487== 0.0 )&nbsp; THEN<br>
4488
4489
4490&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4491      <span style="font-weight: bold;">dt_dots</span> =
4492MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
4493
4494
4495&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4496ELSE<br>
4497
4498
4499&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4500      <span style="font-weight: bold;">dt_dots</span> =
4501MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
4502)<br>
4503
4504
4505&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4506ENDIF</p>
4507
4508
4509     
4510     
4511      <p>This parameter can be used to
4512assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
4513time is the beginning of
4514&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
45152*<b>dt_dots</b>, 3*<b>dt_dots</b>, etc. The
4516actual output times can
4517deviate 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;
4518Is <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
4519of the time series are
4520written after each time step (if this is requested it should be <b>dt_dots</b>
4521= <i>0</i>).</font></span></p>
4522
4523
4524     
4525     
4526      <p><span lang="en-GB"><font face="Thorndale">The default
4527value of <span style="font-weight: bold;">dt_dots</span>
4528is calculated as follows:</font></span></p>
4529
4530
4531&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4532IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
4533== 0.0 )&nbsp; THEN<br>
4534
4535
4536&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4537      <span style="font-weight: bold;">dt_dots</span> =
4538MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
4539
4540
4541&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4542ELSE<br>
4543
4544
4545&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4546      <span style="font-weight: bold;">dt_dots</span> =
4547MIN( <span style="font-weight: bold;">dt_run_control</span>,
4548      <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
4549)<br>
4550
4551
4552&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4553ENDIF<br>
4554
4555
4556      <br>
4557
4558
4559(which minimizes the number of calls of
4560routine flow_statistics).<br>
4561
4562
4563     
4564     
4565      <p>By default time series data
4566is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>.
4567Because of the default settings of <span style="font-weight: bold;">dt_dots</span>,
4568it will&nbsp;generally be created for each model run. The file's
4569format is NetCDF.&nbsp; Further details about processing NetCDF
4570data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
4571
4572
4573The
4574file contains the following timeseries quantities (the first column
4575gives the name of the quantities as used in the NetCDF file):<br>
4576
4577
4578     
4579     
4580      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
4581
4582
4583 <tbody>
4584
4585
4586 <tr>
4587
4588
4589 <td style="font-style: italic; vertical-align: middle;">E<br>
4590
4591
4592
4593            </td>
4594
4595
4596 <td style="vertical-align: top;">Total
4597kinetic energy of
4598the flow (in m<sup>2</sup>/s<sup>2</sup>)
4599(normalized with respect to the total number of grid points).</td>
4600
4601
4602
4603          </tr>
4604
4605
4606 <tr>
4607
4608
4609 <td style="font-style: italic; vertical-align: middle;">E*<br>
4610
4611
4612
4613            </td>
4614
4615
4616 <td style="vertical-align: top;">Perturbation
4617kinetic
4618energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
4619            </sup>(normalized
4620with respect to the total number of grid
4621points)</td>
4622
4623
4624 </tr>
4625
4626
4627 <tr>
4628
4629
4630 <td style="vertical-align: top; font-style: italic;">dt<br>
4631
4632
4633
4634            </td>
4635
4636
4637 <td style="vertical-align: top;">Time step
4638size (in s).</td>
4639
4640
4641 </tr>
4642
4643
4644 <tr>
4645
4646
4647 <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
4648
4649
4650
4651            <td style="vertical-align: top;">Friction velocity (in
4652m/s)
4653(horizontal average).</td>
4654
4655
4656 </tr>
4657
4658
4659 <tr>
4660
4661
4662 <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
4663
4664
4665
4666            <td style="vertical-align: top;">Vertical velocity scale
4667of
4668the CBL (in m/s) (horizontal average)</td>
4669
4670
4671 </tr>
4672
4673
4674 <tr>
4675
4676
4677
4678            <td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
4679
4680
4681
4682            <td style="vertical-align: top;">Temperature
4683scale (Prandtl layer), defined as <i>w"pt"0
4684/&nbsp;</i><i>u<sub>*</sub></i>
4685(horizontal
4686average) (in K).</td>
4687
4688
4689 </tr>
4690
4691
4692 <tr>
4693
4694
4695 <td style="vertical-align: top; font-style: italic;">umax<br>
4696
4697
4698
4699            </td>
4700
4701
4702 <td style="vertical-align: top;">Maximum
4703u-component of the
4704velocity (in m/s).</td>
4705
4706
4707 </tr>
4708
4709
4710 <tr>
4711
4712
4713 <td style="vertical-align: top; font-style: italic;">vmax<br>
4714
4715
4716
4717            </td>
4718
4719
4720 <td style="vertical-align: top;">Maximum
4721v-component of the
4722velocity (in m/s).</td>
4723
4724
4725 </tr>
4726
4727
4728 <tr>
4729
4730
4731 <td style="vertical-align: top; font-style: italic;">wmax<br>
4732
4733
4734
4735            </td>
4736
4737
4738 <td style="vertical-align: top;">Maximum
4739w-component of the
4740velocity (in m/s).</td>
4741
4742
4743 </tr>
4744
4745
4746 <tr>
4747
4748
4749 <td style="vertical-align: top; font-style: italic;">div_old<br>
4750
4751
4752
4753            </td>
4754
4755
4756 <td style="vertical-align: top;">Divergence
4757of the velocity
4758field before the pressure
4759solver has been called (normalized with respect to the total number of
4760grid points) (in 1/s).</td>
4761
4762
4763 </tr>
4764
4765
4766 <tr>
4767
4768
4769 <td style="vertical-align: top; font-style: italic;">div_new</td>
4770
4771
4772
4773            <td style="vertical-align: top;">Divergence of the
4774velocity
4775field after the pressure
4776solver has been called (normalized with respect to the total number of
4777grid points) (in 1/s).</td>
4778
4779
4780 </tr>
4781
4782
4783 <tr>
4784
4785
4786 <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
4787
4788
4789
4790            <td style="vertical-align: top;">Height of the convective
4791boundary layer (horizontal average)
4792determined by the height of the minimum sensible heat flux (in m).</td>
4793
4794
4795
4796          </tr>
4797
4798
4799 <tr>
4800
4801
4802 <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
4803
4804
4805
4806            <td style="vertical-align: top;">Height of the convective
4807boundary layer (horizontal average)
4808determined by the temperature profile (in m).</td>
4809
4810
4811 </tr>
4812
4813
4814 <tr>
4815
4816
4817
4818            <td style="vertical-align: top; font-style: italic;">w"pt"0</td>
4819
4820
4821
4822            <td style="vertical-align: top;">Subgrid-scale sensible
4823heat flux near the surface (horizontal
4824average)
4825between z = 0 and z = z<sub>p</sub> = zu(1) (there it
4826corresponds to
4827the total heat flux) (in K m/s).</td>
4828
4829
4830 </tr>
4831
4832
4833 <tr>
4834
4835
4836 <td style="vertical-align: top; font-style: italic;">w"pt"</td>
4837
4838
4839
4840            <td style="vertical-align: top;">Subgrid-scale heat flux
4841(horizontal average) for z = zw(1) (in K
4842m/s).</td>
4843
4844
4845 </tr>
4846
4847
4848 <tr>
4849
4850
4851 <td style="vertical-align: top; font-style: italic;">wpt</td>
4852
4853
4854
4855            <td style="vertical-align: top;">Total heat flux
4856(horizontal average) for z = zw(1) (in K m/s).</td>
4857
4858
4859 </tr>
4860
4861
4862 <tr>
4863
4864
4865
4866            <td style="vertical-align: top; font-style: italic;">pt(0)</td>
4867
4868
4869
4870            <td style="vertical-align: top;">Potential temperature at
4871the surface (horizontal average) (in K).</td>
4872
4873
4874 </tr>
4875
4876
4877 <tr>
4878
4879
4880
4881            <td style="vertical-align: top; font-style: italic;">pt(zp)</td>
4882
4883
4884
4885            <td style="vertical-align: top;">Potential temperature for
4886z = zu(1) (horizontal average) (in K).</td>
4887
4888
4889 </tr>
4890
4891
4892 <tr>
4893
4894
4895
4896            <td style="vertical-align: top; font-style: italic;">splptx</td>
4897
4898
4899
4900            <td style="vertical-align: top;">Percentage of grid points
4901using upstream scheme along x with
4902upstream-spline advection switched on.</td>
4903
4904
4905 </tr>
4906
4907
4908 <tr>
4909
4910
4911
4912            <td style="vertical-align: top; font-style: italic;">splpty</td>
4913
4914
4915
4916            <td style="vertical-align: top;">Percentage of grid points
4917using upstream scheme along y with
4918upstream-spline
4919advection switched on.</td>
4920
4921
4922 </tr>
4923
4924
4925 <tr>
4926
4927
4928 <td style="vertical-align: top; font-style: italic;">splptz</td>
4929
4930
4931
4932            <td style="vertical-align: top;">Percentage of grid points
4933using upstream scheme along z with
4934upstream-spline
4935advection switched on.<br>
4936
4937
4938 </td>
4939
4940
4941 </tr>
4942
4943
4944 <tr>
4945
4946
4947 <td style="vertical-align: top; font-style: italic;">L</td>
4948
4949
4950
4951            <td style="vertical-align: top;">Monin-Obukhov length.</td>
4952
4953
4954
4955          </tr>
4956
4957
4958 
4959       
4960       
4961        </tbody> 
4962     
4963     
4964      </table>
4965
4966
4967      <br>
4968
4969
4970Additionally, the
4971user can add his own timeseries quantities to the file, by using the
4972user-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>.
4973These routines contain (as comment lines) a simple example how to do
4974this.<br>
4975
4976
4977      <br>
4978
4979
4980Time series data refers to the total
4981domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
4982However, the following time series always present the values of the
4983total model domain (even with output for subdomains): <i>umax</i>,
4984      <i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
4985      <i>div_new</i>.</td>
4986
4987
4988 </tr>
4989
4990
4991 <tr>
4992
4993
4994 <td style="vertical-align: top;"> 
4995     
4996     
4997      <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
4998
4999
5000
5001      </td>
5002
5003
5004 <td style="vertical-align: top;">R</td>
5005
5006
5007
5008      <td style="vertical-align: top;"><i>value of
5009&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5010
5011
5012output</a></i></td>
5013
5014
5015
5016      <td style="vertical-align: top;"> 
5017     
5018     
5019      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
5020interval</font> at which&nbsp;horizontal cross section data
5021shall be output (</font>in <font face="Thorndale">s).&nbsp;
5022      </font> </p>
5023
5024
5025 
5026     
5027     
5028      <p><span lang="en-GB"><font face="Thorndale">If output of
5029horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
5030      <span lang="en-GB"><font face="Thorndale">and
5031      </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
5032parameter can be used to
5033assign the temporal interval at which cross section data shall be
5034output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
5035simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>,
5036which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
5037time is the beginning of the simulation, i.e. output
5038takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>,
5039      <span style="font-weight: bold;">skip_time_do2d_xy</span>
5040+ 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span>
5041+ 3*<b>dt_do2d_xy</b>,
5042etc. The actual output times can deviate from these theoretical values
5043(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>
5044
5045
5046
5047      </font></span></p>
5048
5049
5050 
5051     
5052     
5053      <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>
5054has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5055the time t = 0 or at the
5056respective starting times of restart runs).</font></span> </p>
5057
5058
5059
5060      </td>
5061
5062
5063 </tr>
5064
5065
5066 <tr>
5067
5068
5069 <td style="vertical-align: top;"> 
5070     
5071     
5072      <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
5073
5074
5075
5076      </td>
5077
5078
5079 <td style="vertical-align: top;">R</td>
5080
5081
5082
5083      <td style="vertical-align: top;"><i>value of
5084&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5085
5086
5087output</a></i></td>
5088
5089
5090
5091      <td style="vertical-align: top;"> 
5092     
5093     
5094      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
5095interval</font> at which&nbsp;vertical cross sections data
5096(xz) shall be output (</font>in <font face="Thorndale">s).&nbsp;
5097      </font> </p>
5098
5099
5100 
5101     
5102     
5103      <p><span lang="en-GB"><font face="Thorndale">If output of
5104horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
5105      <span lang="en-GB"><font face="Thorndale">and
5106      </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">),
5107this parameter can be used to assign the temporal interval at which
5108cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
5109be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which
5110has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
5111the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz
5112+ dt_do2d_xz</b>,
5113      <span style="font-weight: bold;">skip_time_do2d_xz</span>
5114+ 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span>
5115+ 3*<b>dt_do2d_xz</b>, etc. The actual output times
5116can 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>
5117
5118
5119
5120      </font></span></p>
5121
5122
5123 
5124     
5125     
5126      <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>
5127has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5128the time t = 0 or at the
5129respective starting times of restart runs).</font></span> </p>
5130
5131
5132
5133      </td>
5134
5135
5136 </tr>
5137
5138
5139 <tr>
5140
5141
5142 <td style="vertical-align: top;"> 
5143     
5144     
5145      <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
5146
5147
5148
5149      </td>
5150
5151
5152 <td style="vertical-align: top;">R</td>
5153
5154
5155
5156      <td style="vertical-align: top;"><i>value of
5157&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5158
5159
5160output</a></i></td>
5161
5162
5163
5164      <td style="vertical-align: top;"> 
5165     
5166     
5167      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
5168interval</font> at which&nbsp;vertical cross section data
5169(yz) shall be output (</font>in s<font face="Thorndale">).&nbsp;
5170      </font> </p>
5171
5172
5173 
5174     
5175     
5176      <p><span lang="en-GB"><font face="Thorndale">If output of
5177horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
5178      <span lang="en-GB"><font face="Thorndale">and
5179      </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">),
5180this parameter can be used to assign the temporal interval at which
5181cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
5182be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which
5183has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
5184time is the beginning of
5185the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz
5186+ dt_do2d_yz</b>,
5187      <span style="font-weight: bold;">skip_time_do2d_yz</span>
5188+ 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz
5189      </span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
5190times
5191can 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>
5192
5193
5194
5195      </font></span></p>
5196
5197
5198 
5199     
5200     
5201      <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>
5202has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5203the time t = 0 or at the
5204respective starting times of restart runs).</font></span> </p>
5205
5206
5207
5208      </td>
5209
5210
5211 </tr>
5212
5213
5214 <tr>
5215
5216
5217 <td style="vertical-align: top;"> 
5218     
5219     
5220      <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
5221
5222
5223
5224      </td>
5225
5226
5227 <td style="vertical-align: top;">R</td>
5228
5229
5230
5231      <td style="vertical-align: top;"><i>value of
5232&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
5233
5234
5235output</a></i></td>
5236
5237
5238
5239      <td style="vertical-align: top;"> 
5240     
5241     
5242      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
5243interval</font> at which 3d volume data shall be output (</font>in
5244      <font face="Thorndale">s).&nbsp; </font> </p>
5245
5246
5247
5248     
5249     
5250      <p><span lang="en-GB"><font face="Thorndale">If
5251output of
52523d-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
5253to assign
5254th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
5255interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
5256be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has
5257zero 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
5258time is the
5259beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d
5260+ dt_do3d</b>,
5261      <span style="font-weight: bold;">skip_time_do3d</span>
5262+ 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span>
5263+ 3*<b>dt_do3d</b>, etc. The actual output times can
5264deviate 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>
5265
5266
5267
5268      </font></span></p>
5269
5270
5271 
5272     
5273     
5274      <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>
5275has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
5276the time t = 0 or at the
5277respective starting times of restart runs).</font></span> </p>
5278
5279
5280
5281      </td>
5282
5283
5284 </tr>
5285
5286
5287 <tr>
5288
5289
5290      <td style="vertical-align: top;"><a name="dt_max"></a><span style="font-weight: bold;">dt_max</span></td>
5291
5292
5293      <td style="vertical-align: top;">R</td>
5294
5295
5296      <td style="vertical-align: top;"><span style="font-style: italic;">20.0</span></td>
5297
5298
5299      <td>Maximum
5300allowed value of the timestep (in s).<br>
5301
5302
5303      <br>
5304
5305
5306By default,
5307the maximum timestep is restricted to be 20 s. This might be o.k. for
5308simulations of any kind of atmospheric turbulence but may have to be
5309changed for other situations.</td>
5310
5311
5312    </tr>
5313
5314
5315    <tr>
5316
5317
5318 <td style="vertical-align: top;"> 
5319     
5320     
5321      <p><a name="dt_restart"></a><b>dt_restart</b></p>
5322
5323
5324
5325      </td>
5326
5327
5328 <td style="vertical-align: top;">R</td>
5329
5330
5331
5332      <td style="vertical-align: top;"><i>9999999.9</i></td>
5333
5334
5335
5336      <td style="vertical-align: top;"> 
5337     
5338     
5339      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
5340interval</font> at which a new
5341restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p>
5342
5343
5344 
5345     
5346     
5347      <p><span lang="en-GB"><font face="Thorndale">For a
5348description
5349how 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>
5350does not show any effect, if <span style="font-weight: bold;">restart_time</span>
5351has not been set.</font></span></p>
5352
5353     
5354      <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>
5355and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
5356
5357
5358 </td>
5359
5360
5361 </tr>
5362
5363
5364
5365    <tr>
5366
5367
5368 <td style="vertical-align: top;"> 
5369     
5370     
5371      <p><a name="dt_run_control"></a><b>dt_run_control</b></p>
5372
5373
5374
5375      </td>
5376
5377
5378 <td style="vertical-align: top;">R</td>
5379
5380
5381
5382      <td style="vertical-align: top;"><i>60.0</i></td>
5383
5384
5385
5386      <td style="vertical-align: top;"> 
5387     
5388     
5389      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
5390interval</font> at which run control
5391output is to be made (</font>in <font face="Thorndale">s).&nbsp;
5392      </font> </p>
5393
5394
5395 
5396     
5397     
5398      <p><span lang="en-GB"><font face="Thorndale">Run control
5399information 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
5400output time, one line
5401with information about the size of the time step, maximum speeds, total
5402kinetic energy etc. is written to this file. Reference time is the
5403beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>,
54042*<b>dt_run_control</b>, 3*<b>dt_run_control</b>,
5405etc., and always at
5406the beginning of a model run (thus at the time t = 0 or at the
5407respective starting times of restart runs). The actual output times can
5408deviate 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>
5409
5410
5411
5412      </font></span></p>
5413
5414
5415 
5416     
5417     
5418      <p><span lang="en-GB"><font face="Thorndale">Run control
5419information is output after each time step can be achieved via <b>dt_run_control</b>
5420= <i>0.0</i>.</font></span> </p>
5421
5422
5423 </td>
5424
5425
5426
5427    </tr>
5428
5429
5430 <tr>
5431
5432
5433 <td style="vertical-align: top;">
5434     
5435     
5436      <p><a name="end_time"></a><b>end_time</b></p>
5437
5438
5439
5440      </td>
5441
5442
5443 <td style="vertical-align: top;">R</td>
5444
5445
5446
5447      <td style="vertical-align: top;"><i>0.0</i></td>
5448
5449
5450
5451      <td style="vertical-align: top;"> 
5452     
5453     
5454      <p lang="en-GB"><font face="Thorndale">Simulation time of the 3D
5455model (</font>in <font face="Thorndale">s).&nbsp;
5456      </font> </p>
5457
5458
5459 
5460     
5461     
5462      <p><span lang="en-GB"><font face="Thorndale">The simulation time
5463is starting from the beginning of the initialization run (t = 0), not
5464starting from the beginning of the respective restart run.</font></span></p>
5465
5466     
5467      <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>
5468and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
5469
5470
5471 </td>
5472
5473
5474 </tr>
5475
5476
5477 <tr>
5478
5479
5480 <td style="vertical-align: top;"> 
5481     
5482     
5483      <p><a name="force_print_header"></a><b>force_print_header</b></p>
5484
5485
5486
5487      </td>
5488
5489
5490 <td style="vertical-align: top;">L</td>
5491
5492
5493
5494      <td style="vertical-align: top;"><i>.F.</i></td>
5495
5496
5497
5498      <td style="vertical-align: top;"> 
5499     
5500     
5501      <p>Steering of
5502header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
5503      </p>
5504
5505
5506 
5507     
5508     
5509      <p>By default, informations about the model
5510parameters in use are
5511output to the beginning of file RUN_CONTROL for initial runs only
5512(these informations are identical to that which are output to the local
5513file <a href="chapter_3.4.html#HEADER">HEADER</a>).
5514With <b>force_print_header</b> = <i>.T.</i>,
5515these informations are
5516also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
5517at restart runs.</p>
5518
5519
5520 </td>
5521
5522
5523 </tr>
5524
5525
5526 <tr>
5527
5528
5529 <td style="vertical-align: top;"> 
5530     
5531     
5532      <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
5533
5534
5535
5536      </td>
5537
5538
5539 <td style="vertical-align: top;">I</td>
5540
5541
5542
5543      <td style="vertical-align: top;"><i>-1</i></td>
5544
5545
5546
5547      <td style="vertical-align: top;"> 
5548     
5549     
5550      <p>Number of
5551cycles to be used with the multi-grid scheme.<br>
5552
5553
5554 <br>
5555
5556
5557
5558This parameter determines the number of cycles to be carried out in the
5559multi-grid method used for solving the Poisson equation for
5560perturbation pressure (see <a href="#psolver">psolver</a>).
5561The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br>
5562
5563
5564
5565      </p>
5566
5567
5568 <br>
5569
5570
5571By default (<b>mg_cyles</b> = <i>-
55721</i>), the
5573number of cycles
5574depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>)
5575and may vary from time step to time step. In this case, the CPU time
5576for a run will be difficult to estimate, since it heavily depends on
5577the total number of the cycles to be carried out.<br>
5578
5579
5580 <br>
5581
5582
5583
5584By assigning <b>mg_cycles</b> a value (&gt;=<span style="font-style: italic;">1</span>), the number of
5585cycles can be
5586fixed so that the CPU time can be clearly estimated. <br>
5587
5588
5589 <br>
5590
5591
5592
5593      <b>Note:</b> When using a fixed number of cycles, the user
5594must
5595examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
5596regularly to check whether the divergence of the velocity field is
5597sufficiently reduced by the pressure solver. It should be reduced at
5598least by two orders of magnitude. For cyclic boundary conditions along
5599both horizontal directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
5600and <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
5601good choice, for
5602non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span>
5603= <span style="font-style: italic;">4</span> may be
5604sufficient.</td>
5605
5606
5607 </tr>
5608
5609
5610 <tr>
5611
5612
5613 <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
5614
5615
5616
5617level</b></td>
5618
5619
5620 <td style="vertical-align: top;">I</td>
5621
5622
5623
5624      <td style="vertical-align: top;"><br>
5625
5626
5627 </td>
5628
5629
5630 <td style="vertical-align: top;">Grid
5631level at which data shall be gathered on PE0.<br>
5632
5633
5634 <br>
5635
5636
5637
5638In case of a run using several PEs and the multigrid method for solving
5639the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
5640the value of this parameter defines on which grid level the data are
5641gathered on PE0 in order to allow for a further coarsening of the grid.
5642The finest grid defines the largest grid level. By default, the
5643gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
5644It is only possible to gather data from a level larger than the one
5645determined automatically. A test run may be neccessary to determine
5646this level.</td>
5647
5648
5649 </tr>
5650
5651
5652 <tr>
5653
5654
5655 <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</span><br>
5656
5657
5658
5659      </td>
5660
5661
5662 <td style="vertical-align: top;">L<br>
5663
5664
5665 </td>
5666
5667
5668
5669      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
5670
5671
5672 </td>
5673
5674
5675
5676      <td style="vertical-align: top;">NetCDF files will have 64
5677bit offset format.<br>
5678
5679
5680      <br>
5681
5682
5683By
5684default, the maximum file size of the NetCDF files opened by PALM is 2
5685GByte. Using netcdf_64bit = .TRUE. allows file sizes larger than 2
5686GByte.<br>
5687
5688
5689      <br>
5690
5691
5692The 64 bit offset format can be separately
5693switched off for those NetCDF files containing 3d volume date (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
5694      <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>)
5695using <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br>
5696
5697
5698      <br>
5699
5700
5701      <span style="font-weight: bold;">Warning:</span><br>
5702
5703
5704Some
5705(PD or commercial) software may not support the 64 bit offset format.<br>
5706
5707
5708
5709      </td>
5710
5711
5712 </tr>
5713
5714
5715    <tr>
5716
5717
5718      <td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td>
5719
5720
5721      <td style="vertical-align: top;">L</td>
5722
5723
5724      <td style="vertical-align: top;">.T.</td>
5725
5726
5727      <td style="vertical-align: top;">NetCDF files containing 3d
5728volume data will have 64 bit offset format.<br>
5729
5730
5731      <br>
5732
5733
5734This
5735switch&nbsp;only comes into effect if <a href="#netcdf_64bit">netcdf_64bit</a>
5736= .TRUE.. It allows to switch off separately the 64 bit offset format
5737for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
5738      <span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>).</td>
5739
5740
5741    </tr>
5742
5743
5744    <tr>
5745
5746
5747
5748      <td style="vertical-align: top;"> 
5749     
5750     
5751      <p><a name="ngsrb"></a><b>ngsrb</b></p>
5752
5753
5754 </td>
5755
5756
5757
5758      <td style="vertical-align: top;">I</td>
5759
5760
5761 <td style="vertical-align: top;"><i>2</i></td>
5762
5763
5764
5765      <td style="vertical-align: top;">Grid
5766level at which data shall be gathered on PE0.<br>
5767
5768
5769 <br>
5770
5771
5772
5773In case of a run using several PEs and the multigrid method for solving
5774the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
5775the value of this parameter defines on which grid level the data are
5776gathered on PE0 in order to allow for a further coarsening of the grid.
5777The finest grid defines the largest grid level. By default, the
5778gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
5779It is only possible to gather data from a level larger than the one
5780determined automatically. A test run may be neccessary to determine
5781this level.</td>
5782
5783
5784 </tr>
5785
5786
5787 <tr>
5788
5789
5790 <td style="vertical-align: top;"> 
5791     
5792     
5793      <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
5794
5795
5796
5797      </td>
5798
5799
5800 <td style="vertical-align: top;">I</td>
5801
5802
5803
5804      <td style="vertical-align: top;"><span style="font-style: italic;">0</span><br>
5805
5806
5807 </td>
5808
5809
5810
5811      <td style="vertical-align: top;"> 
5812     
5813     
5814      <p>Determines the
5815subdomain from which the normalization
5816quantities are calculated.&nbsp; </p>
5817
5818
5819 
5820     
5821     
5822      <p>If output
5823data of the horizontally averaged vertical profiles
5824(see <a href="#data_output_pr">data_output_pr</a>)
5825is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>,
5826      <a href="#cross_normalized_y">cross_normalized_y</a>),
5827the respective normalization quantities are by default calculated from
5828the averaged data of the total model domain (<b>normalizing_region</b>
5829= <i>0</i>) and are thus representative for the total
5830domain. Instead
5831of that, normalization quantities can also be calculated for a
5832subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>,
5833where <i>1</i>
5834&lt;= <b>normalizing_region</b> &lt;= <i>9 </i>must
5835hold. These
5836quantities are then used for normalizing of all profiles (even for that
5837of the total domain).</p>
5838
5839
5840 </td>
5841
5842
5843 </tr>
5844
5845
5846 <tr>
5847
5848
5849 <td style="vertical-align: top;"> 
5850     
5851     
5852      <p><a name="nsor"></a><b>nsor</b></p>
5853
5854
5855
5856      </td>
5857
5858
5859 <td style="vertical-align: top;">I</td>
5860
5861
5862
5863      <td style="vertical-align: top;"><i>20</i></td>
5864
5865
5866
5867      <td style="vertical-align: top;"> 
5868     
5869     
5870      <p>Number of
5871iterations to be used with the SOR-scheme.&nbsp; </p>
5872
5873
5874 
5875     
5876     
5877      <p>This
5878parameter is only effective if the SOR-scheme is selected
5879as pressure solver (<a href="#psolver">psolver</a>
5880= <span style="font-style: italic;">'sor'</span>).
5881The number of
5882iterations necessary for a sufficient convergence of the scheme depends
5883on the grid point numbers and is to be determined by appropriate test
5884runs (the default value will not at all be sufficient for larger grid
5885point numbers). The number of iterations used for the first call of the
5886SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p>
5887
5888
5889
5890      </td>
5891
5892
5893 </tr>
5894
5895
5896 <tr>
5897
5898
5899 <td style="vertical-align: top;"> 
5900     
5901     
5902      <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
5903
5904
5905
5906      </td>
5907
5908
5909 <td style="vertical-align: top;">I</td>
5910
5911
5912
5913      <td style="vertical-align: top;"><i>nz+1</i></td>
5914
5915
5916
5917      <td style="vertical-align: top;"> Limits the output of 3d
5918volume data along the vertical direction (grid point index k).<br>
5919
5920
5921      <br>
5922
5923
5924By
5925default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
5926can be used to limit the output up to a certain vertical grid point
5927(e.g. in order to reduce the amount of output data). It affects all
5928output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output
5929for <span style="font-weight: bold;">dvrp</span>-software,
5930see <a href="#mode_dvrp">mode_dvrp</a>).</td>
5931
5932
5933
5934    </tr>
5935
5936
5937 <tr>
5938
5939
5940 <td style="vertical-align: top;">
5941     
5942     
5943      <p><a name="omega_sor"></a><b>omega_sor</b></p>
5944
5945
5946
5947      </td>
5948
5949
5950 <td style="vertical-align: top;">R</td>
5951
5952
5953
5954      <td style="vertical-align: top;"><i>1.8</i></td>
5955
5956
5957
5958      <td style="vertical-align: top;"> 
5959     
5960     
5961      <p>Convergence
5962factor to be used with the the SOR-scheme.&nbsp; </p>
5963
5964
5965 
5966     
5967     
5968      <p>If
5969the SOR-scheme is selected (<a href="#psolver">psolver</a>
5970= <span style="font-style: italic;">'sor'</span>),
5971this parameter
5972determines the value of the convergence factor, where <i>1.0</i>
5973&lt;= <b>omega_sor</b> &lt; <i>2.0 </i>.
5974The optimum value of <b>omega_sor</b>
5975depends on the number of grid points along the different directions in
5976space. For non-equidistant grids it can only be determined by
5977appropriate test runs.</p>
5978
5979
5980 </td>
5981
5982
5983 </tr>
5984
5985
5986 <tr>
5987
5988
5989 <td style="vertical-align: top;"> 
5990     
5991     
5992      <p><a name="prandtl_number"></a><b>prandtl_number</b></p>
5993
5994
5995
5996      </td>
5997
5998
5999 <td style="vertical-align: top;">R</td>
6000
6001
6002
6003      <td style="vertical-align: top;"><i>1.0</i></td>
6004
6005
6006
6007      <td style="vertical-align: top;"> 
6008     
6009     
6010      <p>Ratio of the
6011eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).&nbsp;
6012      </p>
6013
6014
6015 
6016     
6017     
6018      <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
6019this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub>
6020/ K<sub>h</sub>).</p>
6021
6022
6023 </td>
6024
6025
6026 </tr>
6027
6028
6029 <tr>
6030
6031
6032      <td style="vertical-align: top;"><a name="precipitation_amount_interval"></a><span style="font-weight: bold;">precipitation_amount_</span><br style="font-weight: bold;">
6033
6034
6035      <span style="font-weight: bold;">interval</span></td>
6036
6037
6038      <td style="vertical-align: top;">R</td>
6039
6040
6041      <td style="vertical-align: top;"><i>value of
6042&nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>
6043
6044
6045xy</a></i></td>
6046
6047
6048      <td style="vertical-align: top;">
6049     
6050     
6051      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
6052interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;
6053      </font> </p>
6054
6055
6056 
6057     
6058     
6059      <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
6060parameter 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>
6061
6062
6063
6064      </font></span></p>
6065
6066
6067 <span lang="en-GB"></span></td>
6068
6069
6070    </tr>
6071
6072
6073    <tr>
6074
6075
6076
6077      <td style="vertical-align: top;"> 
6078     
6079     
6080      <p><a name="profile_columns"></a><b>profile_columns</b></p>
6081
6082
6083
6084      </td>
6085
6086
6087 <td style="vertical-align: top;">I</td>
6088
6089
6090
6091      <td style="vertical-align: top;"><i>3</i></td>
6092
6093
6094
6095      <td style="vertical-align: top;"> 
6096     
6097     
6098      <p>Number of
6099coordinate systems to be plotted<span style="font-weight: bold;"></span>
6100in one row by <span style="font-weight: bold;">profil</span>.&nbsp;
6101      </p>
6102
6103
6104 
6105     
6106     
6107      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
6108= <span style="font-style: italic;">'profil'</span>.</p>
6109
6110
6111     
6112     
6113      <p>It
6114determines the layout of plots of
6115horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
6116when plotted with the plot software <span style="font-weight: bold;">profil</span>.
6117Generally, the number and sequence of coordinate systems (panels) to be
6118plotted on one page are
6119determined by <a href="#cross_profiles">cross_profiles</a>.
6120      <b>profile_columns</b>
6121determines how many panels are to be
6122arranged next to each other in one row (number of columns). The
6123respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>.
6124According to their order given by <a href="#data_output_pr">data_output_pr</a>,
6125the panels are arranged beginning in the top row from left to right and
6126then continued in the following row. If the number of panels cranz
6127&gt; <b>profile_columns</b> * <b>profile_rows</b>,
6128the remaining
6129panels are drawn on an additional page. If cranz &lt; <b>profile_columns</b>,
6130then <b>profile_columns</b> = cranz is automatically set.
6131If
6132row&nbsp; contains any panel, then the value of <b>profile_rows</b>
6133is reduced automatically.</p>
6134
6135
6136 </td>
6137
6138
6139 </tr>
6140
6141
6142 <tr>
6143
6144
6145
6146      <td style="vertical-align: top;"> 
6147     
6148     
6149      <p><a name="profile_rows"></a><b>profile_rows</b></p>
6150
6151
6152
6153      </td>
6154
6155
6156 <td style="vertical-align: top;">I</td>
6157
6158
6159
6160      <td style="vertical-align: top;"><i>2</i></td>
6161
6162
6163
6164      <td style="vertical-align: top;"> 
6165     
6166     
6167      <p>Number of rows
6168of coordinate systems to be plotted on one page
6169by <span style="font-weight: bold;">profil</span>.&nbsp;
6170      </p>
6171
6172
6173 
6174     
6175     
6176      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
6177= <span style="font-style: italic;">'profil'</span>.</p>
6178
6179
6180     
6181     
6182      <p>It
6183determines the layout of plots of horizontally averaged
6184profiles. See <a href="#profile_columns">profile_columns</a>.</p>
6185
6186
6187
6188      </td>
6189
6190
6191 </tr>
6192
6193
6194 <tr>
6195
6196
6197 <td style="vertical-align: top;"> 
6198     
6199     
6200      <p><a name="psolver"></a><b>psolver</b></p>
6201
6202
6203
6204      </td>
6205
6206
6207 <td style="vertical-align: top;">C * 10</td>
6208
6209
6210
6211      <td style="vertical-align: top;"><i>'poisfft'</i></td>
6212
6213
6214
6215      <td style="vertical-align: top;"> 
6216     
6217     
6218      <p>Scheme to be
6219used to solve the Poisson equation for the
6220perturbation pressure.&nbsp; </p>
6221
6222
6223 <br>
6224
6225
6226
6227The user can choose between the following schemes:<br>
6228
6229
6230 
6231     
6232     
6233      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
6234
6235
6236 <tbody>
6237
6238
6239 <tr>
6240
6241
6242 <td style="vertical-align: top;"><i>poisfft</i></td>
6243
6244
6245
6246            <td style="vertical-align: top;">Direct method using FFT
6247along x and y, solution of a
6248tridiagonal matrix along z, and backward
6249FFT (see Siano, institute reports, volume 54). The FFT routines to be
6250used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
6251
6252
6253
6254This solver is specially optimized for 1d domain decompositions.
6255Vectorization is optimized for domain decompositions along x only.</td>
6256
6257
6258
6259          </tr>
6260
6261
6262 <tr>
6263
6264
6265 <td style="vertical-align: top;">
6266           
6267           
6268            <p><i>poisfft_</i>
6269            <br>
6270
6271
6272 <i>hybrid</i></p>
6273
6274
6275
6276            </td>
6277
6278
6279 <td style="vertical-align: top;">Direct
6280method using FFT
6281along x and y, solution of a
6282tridiagonal matrix along z, and backward
6283FFT (see Siano, institute reports, volume 54). The FFT routines to be
6284used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
6285
6286
6287
6288This solver is specially optimized for 1d domain decompositions.
6289Vectorization is optimized for domain decompositions along x only.</td>
6290
6291
6292
6293          </tr>
6294
6295
6296 <tr>
6297
6298
6299 <td style="vertical-align: top;"><i>multigrid</i></td>
6300
6301
6302
6303            <td style="vertical-align: top;"> 
6304           
6305           
6306            <p>Multi-grid
6307scheme (see Uhlenbrock, diploma thesis). v-
6308and
6309w-cycles (see <a href="#cycle_mg">cycle_mg</a>)
6310are implemented. The convergence of the iterative scheme can be
6311steered by the number of v-/w-cycles to be carried out for each call of
6312the scheme (<a href="#mg_cycles">mg_cycles</a>)
6313and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>)
6314to be carried out on each grid level. Instead the requested accuracy
6315can be given via <a href="#residual_limit">residual_limit</a>.
6316            <span style="font-weight: bold;">This is the default!</span>
6317The
6318smaller this limit is, the more cycles have to be carried out in this
6319case and the number of cycles may vary from timestep to timestep.</p>
6320
6321
6322
6323            <br>
6324
6325
6326If <a href="#mg_cycles">mg_cycles</a>
6327is set to its optimal value, the computing time of the
6328multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
6329the number of
6330grid points in the three directions
6331of space corresponds to a power-of-two (2<sup>n</sup>)
6332where <i>n</i> &gt;= 5 must hold. With large <i>n,
6333            </i>the
6334multi-grid scheme can even be faster than the direct solver (although
6335its accuracy is several orders of magnitude worse, but this does not
6336affect the accuracy of the simulation). Nevertheless, the user should
6337always carry out some test runs in order to find out the optimum value
6338for <a href="#mg_cycles">mg_cycles</a>,
6339because the CPU time of a run very critically depends on this
6340parameter.
6341           
6342           
6343            <p>This scheme requires that the number of grid
6344points of
6345the
6346subdomains (or of the total domain, if only one PE is uesd) along each
6347of the directions can at least be devided once by 2 without rest.</p>
6348
6349
6350
6351With parallel runs, starting from a certain grid level the
6352data of the subdomains are possibly gathered on PE0 in order to allow
6353for a further coarsening of the grid. The grid level for gathering can
6354be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
6355
6356
6357
6358           
6359           
6360            <p>Using this procedure requires the subdomains to be of
6361identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p>
6362
6363
6364
6365            </td>
6366
6367
6368 </tr>
6369
6370
6371 <tr>
6372
6373
6374 <td style="vertical-align: top;"><i>sor</i></td>
6375
6376
6377
6378            <td style="vertical-align: top;">Successive over
6379relaxation
6380method (SOR). The convergence of
6381this
6382iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>,
6383            <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
6384and <a href="chapter_4.1.html#nsor">nsor</a>.&nbsp;
6385            <br>
6386
6387
6388Compared to the direct method and the multi-grid method, this
6389scheme
6390needs substantially
6391more computing time. It should only be used for test runs, e.g. if
6392errors in the other pressure solver methods are assumed.</td>
6393
6394
6395 </tr>
6396
6397
6398
6399       
6400       
6401        </tbody> 
6402     
6403     
6404      </table>
6405
6406
6407 <br>
6408
6409
6410In order to speed-up
6411performance, the Poisson equation is by default
6412only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver
6413at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>).&nbsp;
6414      </td>
6415
6416
6417 </tr>
6418
6419
6420 <tr>
6421
6422
6423 <td style="vertical-align: top;"> 
6424     
6425     
6426      <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
6427      <br>
6428
6429
6430 <b>_factor</b></p>
6431
6432
6433 </td>
6434
6435
6436 <td style="vertical-align: top;">R</td>
6437
6438
6439 <td style="vertical-align: top;"><i>0.0 or</i><br>
6440
6441
6442
6443      <i>0.01</i></td>
6444
6445
6446 <td style="vertical-align: top;">
6447     
6448     
6449      <p>Factor for Rayleigh damping.&nbsp; </p>
6450
6451
6452 
6453     
6454     
6455      <p>A
6456so-called Rayleigh damping is applied to all prognostic
6457variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>.&nbsp;
6458If switched on, variables are forced towards the value of their
6459respective basic states (e.g. the geostrophic wind). The intensity of
6460damping is controlled by the value the <b>rayleigh_damping_factor</b>
6461is assigned to.
6462The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a>
6463and rises according to a sin<sup>2</sup>-function to its
6464maximum value
6465at
6466the top (ocean: bottom) boundary. </p>
6467
6468
6469 
6470     
6471     
6472      <p>This method
6473effectively damps gravity waves, caused by boundary layer convection,
6474which may spread out vertically in the inversion layer and which are
6475reflected&nbsp;at the top (ocean: bottom)
6476boundary. This particularly happens with the upstream-spline scheme
6477switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
6478or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>).
6479Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b>
6480= <i>0.01</i>) by default. Otherwise it remains switched
6481off.&nbsp; </p>
6482
6483
6484 
6485     
6486     
6487      <p>The Rayleigh damping factor must
6488hold the condition <i>0.0</i>
6489&lt;= <b>rayleigh_damping_factor</b>
6490&lt;= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
6491numerical instabilities.</p>
6492
6493
6494 </td>
6495
6496
6497 </tr>
6498
6499
6500 <tr>
6501
6502
6503
6504      <td style="vertical-align: top;"> 
6505     
6506     
6507      <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
6508      <br>
6509
6510
6511 <b>_height</b></p>
6512
6513
6514 </td>
6515
6516
6517 <td style="vertical-align: top;">R</td>
6518
6519
6520 <td style="vertical-align: top;"> 
6521     
6522     
6523      <p><i>2/3 *</i>
6524      <br>
6525
6526
6527      <span style="font-style: italic;">zu</span><i style="font-style: italic;">(nz)</i></p>
6528      <p> (ocean:<i style="font-style: italic;">&nbsp;</i><i>2/3 *</i>
6529      <i style="font-style: italic;"> zu(0)</i>)</p>
6530
6531
6532
6533      </td>
6534
6535
6536 <td style="vertical-align: top;"> 
6537     
6538     
6539      <p>Height above (ocean: below) which the Rayleigh damping starts (in m).&nbsp; </p>
6540
6541
6542 
6543     
6544     
6545      <p>With
6546Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
6547this parameter determines the range where damping is applied. By
6548default, Rayleigh damping will be applied in the upper (ocean: lower) third of the
6549model
6550domain.</p>
6551
6552
6553 </td>
6554
6555
6556 </tr>
6557
6558
6559 <tr>
6560
6561
6562 <td style="vertical-align: top;"> 
6563     
6564     
6565      <p><a name="residual_limit"></a><b>residual_limit</b></p>
6566
6567
6568
6569      </td>
6570
6571
6572 <td style="vertical-align: top;">R</td>
6573
6574
6575
6576      <td style="vertical-align: top;"><i>1.0E-6</i></td>
6577
6578
6579
6580      <td style="vertical-align: top;"> 
6581     
6582     
6583      <p>Largest
6584residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>).&nbsp;
6585      </p>
6586
6587
6588 
6589     
6590     
6591      <p>This is a parameter to steer the accuracy of the
6592multi-grid
6593scheme (see <a href="#psolver">psolver</a>).
6594The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>)
6595is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If
6596this
6597is not the case after 1000 cycles, the PALM aborts with a corresponding
6598error message.</p>
6599
6600
6601 
6602     
6603     
6604      <p>The reciprocal value of this
6605parameter can be interpreted as
6606a factor by the divergence of the provisional
6607velocity field is approximately reduced after the multi-grid scheme has
6608been applied (thus the default value causes a reduction of the
6609divergence by approx. 6 orders of magnitude).&nbsp; </p>
6610
6611
6612 </td>
6613
6614
6615
6616    </tr>
6617
6618
6619 <tr>
6620
6621
6622 <td style="vertical-align: top;">
6623     
6624     
6625      <p><a name="restart_time"></a><b>restart_time</b></p>
6626
6627
6628
6629      </td>
6630
6631
6632 <td style="vertical-align: top;">R</td>
6633
6634
6635
6636      <td style="vertical-align: top;"><i>9999999.9</i></td>
6637
6638
6639
6640      <td style="vertical-align: top;"> 
6641     
6642     
6643      <p>Simulated time
6644after which a restart run is to be carried out
6645(in s). </p>
6646
6647
6648 
6649     
6650     
6651      <p>The simulated time refers to the
6652beginning of the
6653initial run (t = 0), not to the beginning of the respective
6654restart run. Restart runs can additionally be forced to be carried out
6655in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p>
6656
6657
6658 
6659     
6660     
6661      <p><span style="font-weight: bold;">Note:</span><br>
6662
6663
6664
6665A successful operation of this parameter requires additional
6666modifications in the <span style="font-weight: bold;">mrun</span>-call
6667for the respective run (see <a href="chapter_3.3.html">chapter
66683.3</a>).<br>
6669
6670
6671 </p>
6672
6673
6674 
6675     
6676     
6677      <p>The choice of <b>restart_time</b>
6678or <b>dt_restart</b> does
6679not override the automatic start of restart runs in case that the job
6680runs out of CPU time. <br>
6681
6682      </p>
6683
6684     
6685      <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>
6686and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
6687
6688
6689 </td>
6690
6691
6692 </tr>
6693
6694
6695
6696    <tr>
6697
6698
6699 <td style="vertical-align: top;"> 
6700     
6701     
6702      <p><a name="section_xy"></a><b>section_xy</b></p>
6703
6704
6705
6706      </td>
6707
6708
6709 <td style="vertical-align: top;">I(100)<br>
6710
6711
6712
6713      </td>
6714
6715
6716 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
6717
6718
6719
6720      </td>
6721
6722
6723 <td style="vertical-align: top;"> 
6724     
6725     
6726      <p lang="en-GB"><font face="Thorndale">Position
6727of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
6728sections (grid point index k).&nbsp; </font> </p>
6729
6730
6731 
6732     
6733     
6734      <p><span lang="en-GB"><font face="Thorndale">If output
6735of
6736horizontal 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
6737parameter can be used to
6738define the position(s) of the cross section(s). Up to 100 positions of
6739cross sections can be selected by assigning <b>section_xy</b>
6740the
6741corresponding vertical grid point index/indices k of the requested
6742cross section(s). The exact location (height level) of the cross
6743section depends on the variable for which the output is made: zu(k) for
6744scalars and horizontal velocities, zw(k) for the vertical velocity.
6745Information about the exact location of the cross section is contained
6746in the NetCDF output file (if the default NetCDF output is switched on;
6747see <a href="#data_output_format">data_output_format</a>).</font></span></p>
6748
6749
6750     
6751     
6752      <p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
6753creates the output of horizontal cross sections averaged along z. In
6754the
6755NetCDF output file these (averaged) cross sections are given the
6756z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p>
6757
6758
6759     
6760     
6761      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
6762does not effect the output of horizontal cross sections of variable u<sub>*</sub>
6763and theta<sub>*</sub> and the liquid water path lwp*. For
6764these quantities always only one cross
6765section (for z=zu(1)) is output.</font></span></p>
6766
6767
6768      <span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
6769      <span style="font-style: italic;">'iso2d'</span> and
6770if several cross sections are selected (e.g. <b>section_xy</b>
6771= <i>1</i>, <i>10</i>, <i>15</i>),
6772then the respective data are
6773successively written to file. The output order follows the order given
6774by <b>section_xy</b>.&nbsp;</font></span></td>
6775
6776
6777
6778    </tr>
6779
6780
6781 <tr>
6782
6783
6784 <td style="vertical-align: top;">
6785     
6786     
6787      <p><a name="section_xz"></a><b>section_xz</b></p>
6788
6789
6790
6791      </td>
6792
6793
6794 <td style="vertical-align: top;">I(100)<br>
6795
6796
6797
6798      </td>
6799
6800
6801 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
6802
6803
6804
6805      <td style="vertical-align: top;"> 
6806     
6807     
6808      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
6809for&nbsp;output of 2d (xz) vertical cross sections (grid point
6810index j).&nbsp; </font> </p>
6811
6812
6813 <span lang="en-GB"><font face="Thorndale">If output of
6814vertical 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
6815parameter can be used to
6816define the position(s) of the cross section(s). Up to 100 positions of
6817cross sections can be selected by assigning <b>section_xz</b>
6818the
6819corresponding horizontal grid point index/indices j of the requested
6820cross section(s). The exact position (in y-direction) of the cross
6821section 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
6822on which grid the output quantity is defined. However, in
6823the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
6824default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
6825no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all
6826positions.<br>
6827
6828
6829      <br>
6830
6831
6832Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
6833creates the output of vertical cross sections averaged along y. In the
6834NetCDF output file these (averaged) cross sections are given the
6835y-coordinate <span style="font-style: italic;">-1.0</span>.<br>
6836
6837
6838      </font></span><span lang="en-GB"><font face="Thorndale"><br>
6839
6840
6841      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
6842      <span style="font-style: italic;">'iso2d'</span> and
6843      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
6844selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>,
6845      <i>27</i>),
6846then the respective data are successively written to file. The output
6847order follows the order given by <b>section_xz</b>.</font></span></td>
6848
6849
6850
6851    </tr>
6852
6853
6854 <tr>
6855
6856
6857 <td style="vertical-align: top;">
6858     
6859     
6860      <p><a name="section_yz"></a><b>section_yz</b></p>
6861
6862
6863
6864      </td>
6865
6866
6867 <td style="vertical-align: top;">I(100)<br>
6868
6869
6870
6871      </td>
6872
6873
6874 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
6875
6876
6877
6878      <td style="vertical-align: top;"> 
6879     
6880     
6881      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
6882for&nbsp;output of 2d (yz) vertical cross sections (grid point
6883index i).&nbsp; </font> </p>
6884
6885
6886 <span lang="en-GB"><font face="Thorndale">If output of
6887vertical 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">),
6888this parameter can be used to define the position(s) of the cross
6889section(s). Up to 100 positions of cross sections can be selected by
6890assigning <b>section_yz</b> the corresponding horizontal
6891grid point
6892index/indices i of the requested cross section(s). The exact position
6893(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
6894on which grid the output quantity is defined.&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">However, in
6895the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
6896default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
6897no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all
6898positions.<br>
6899
6900
6901      <br>
6902
6903
6904      </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>
6905creates the output of vertical cross sections averaged along x. In the
6906NetCDF output file these (averaged) cross sections are given the
6907x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br>
6908
6909
6910      <span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br>
6911
6912
6913      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
6914      <span style="font-style: italic;">'iso2d'</span> and
6915      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
6916selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the
6917respective data are successively written to file. The output order
6918follows the order given by <b>section_yz</b>.</font></span></td>
6919
6920
6921
6922    </tr>
6923
6924
6925 <tr>
6926
6927
6928 <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
6929
6930
6931
6932      </td>
6933
6934
6935 <td style="vertical-align: top;">R<br>
6936
6937
6938 </td>
6939
6940
6941
6942      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
6943
6944
6945 </td>
6946
6947
6948
6949      <td style="vertical-align: top;">No data output before
6950this interval has passed (in s).<br>
6951
6952
6953      <br>
6954
6955
6956This
6957parameter causes that data output activities are starting not before
6958this interval
6959(counting from the beginning of the simulation, t=0) has passed. By
6960default, this
6961applies for output of instantaneous 3d volume data, cross section data,
6962spectra and vertical profile data as well as for temporally averaged 2d
6963and 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>
6964
6965
6966      <br>
6967
6968
6969      <span style="font-weight: bold;">Example:</span><br>
6970
6971
6972If
6973the user has set <a href="#dt_data_output">dt_data_output</a>
6974= <span style="font-style: italic;">3600.0</span>
6975and <span style="font-weight: bold;">skip_time_data_output</span>
6976= <span style="font-style: italic;">1800.0</span>,
6977then the first output will be done at t = 5400 s.<br>
6978
6979
6980 </td>
6981
6982
6983
6984    </tr>
6985
6986
6987 <tr>
6988
6989
6990      <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>
6991
6992
6993      <td style="vertical-align: top;">R</td>
6994
6995
6996      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>
6997
6998
6999data_output</a></span></td>
7000
7001
7002      <td style="vertical-align: top;">No output of temporally
7003averaged 2d/3d data before this interval has passed (in s).<br>
7004
7005
7006      <br>
7007
7008
7009This
7010parameter causes that data output activities are starting not before
7011this interval
7012(counting from the beginning of the simulation, t=0) has passed. <br>
7013
7014
7015      <br>
7016
7017
7018      <span style="font-weight: bold;">Example:</span><br>
7019
7020
7021If
7022the user has set <a href="#dt_data_output_av">dt_data_output_av</a>
7023= <span style="font-style: italic;">3600.0</span>
7024and <span style="font-weight: bold;">skip_time_data_output_av</span>
7025= <span style="font-style: italic;">1800.0</span>,
7026then the first output will be done at t = 5400 s.</td>
7027
7028
7029    </tr>
7030
7031
7032    <tr>
7033
7034
7035
7036      <td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
7037
7038
7039
7040      </td>
7041
7042
7043 <td style="vertical-align: top;">R<br>
7044
7045
7046 </td>
7047
7048
7049
7050      <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>
7051
7052
7053data_output</a></span>
7054      </td>
7055
7056
7057 <td style="vertical-align: top;">No output of
7058vertical profile data before this interval has passed (in s).<br>
7059
7060
7061      <br>
7062
7063
7064This
7065parameter causes that data output activities are starting not before
7066this interval
7067(counting from the beginning of the simulation, t=0) has passed. <br>
7068
7069
7070      <br>
7071
7072
7073      <span style="font-weight: bold;">Example:</span><br>
7074
7075
7076If
7077the 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
7078first output will be done at t = 5400 s. </td>
7079
7080
7081 </tr>
7082
7083
7084 <tr>
7085
7086
7087
7088      <td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
7089
7090
7091
7092      </td>
7093
7094
7095 <td style="vertical-align: top;">R<br>
7096
7097
7098 </td>
7099
7100
7101
7102      <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>
7103
7104
7105data_output</a></span>
7106      </td>
7107
7108
7109 <td style="vertical-align: top;">No output of
7110instantaneous horizontal cross section data before this interval has
7111passed (in s).<br>
7112
7113
7114      <br>
7115
7116
7117This
7118parameter causes that data output activities are starting not before
7119this interval
7120(counting from the beginning of the simulation, t=0) has passed. <br>
7121
7122
7123      <br>
7124
7125
7126      <span style="font-weight: bold;">Example:</span><br>
7127
7128
7129If
7130the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a>
7131= <span style="font-style: italic;">3600.0</span>
7132and <span style="font-weight: bold;">skip_time_do2d_xy</span>
7133= <span style="font-style: italic;">1800.0</span>,
7134then the first output will be done at t = 5400 s. </td>
7135
7136
7137 </tr>
7138
7139
7140
7141    <tr>
7142
7143
7144 <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
7145
7146
7147
7148      </td>
7149
7150
7151 <td style="vertical-align: top;">R<br>
7152
7153
7154 </td>
7155
7156
7157
7158      <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>
7159
7160
7161data_output</a></span>
7162      </td>
7163
7164
7165 <td style="vertical-align: top;">No output of
7166instantaneous vertical (xz) cross section data before this interval has
7167passed (in s).<br>
7168
7169
7170      <br>
7171
7172
7173This
7174parameter causes that data output activities are starting not before
7175this interval
7176(counting from the beginning of the simulation, t=0) has passed. <br>
7177
7178
7179      <br>
7180
7181
7182      <span style="font-weight: bold;">Example:</span><br>
7183
7184
7185If
7186the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a>
7187= <span style="font-style: italic;">3600.0</span>
7188and <span style="font-weight: bold;">skip_time_do2d_xz</span>
7189= <span style="font-style: italic;">1800.0</span>,
7190then the first output will be done at t = 5400 s. </td>
7191
7192
7193 </tr>
7194
7195
7196
7197    <tr>
7198
7199
7200 <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
7201
7202
7203
7204      </td>
7205
7206
7207 <td style="vertical-align: top;">R<br>
7208
7209
7210 </td>
7211
7212
7213
7214      <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>
7215
7216
7217data_output</a></span>
7218      </td>
7219
7220
7221 <td style="vertical-align: top;">No output of
7222instantaneous vertical (yz) cross section data before this interval has
7223passed (in s).<br>
7224
7225
7226      <br>
7227
7228
7229This
7230parameter causes that data output activities are starting not before
7231this interval
7232(counting from the beginning of the simulation, t=0) has passed. <br>
7233
7234
7235      <br>
7236
7237
7238      <span style="font-weight: bold;">Example:</span><br>
7239
7240
7241If
7242the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a>
7243= <span style="font-style: italic;">3600.0</span>
7244and <span style="font-weight: bold;">skip_time_do2d_yz</span>
7245= <span style="font-style: italic;">1800.0</span>,
7246then the first output will be done at t = 5400 s. </td>
7247
7248
7249 </tr>
7250
7251
7252
7253    <tr>
7254
7255
7256 <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
7257
7258
7259
7260      </td>
7261
7262
7263 <td style="vertical-align: top;">R<br>
7264
7265
7266 </td>
7267
7268
7269
7270      <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>
7271
7272
7273data_output</a></span>
7274      </td>
7275
7276
7277 <td style="vertical-align: top;">No output of
7278instantaneous 3d volume data before this interval has passed (in s).<br>
7279
7280
7281      <br>
7282
7283
7284This
7285parameter causes that data output activities are starting not before
7286this interval
7287(counting from the beginning of the simulation, t=0) has passed. <br>
7288
7289
7290      <br>
7291
7292
7293      <span style="font-weight: bold;">Example:</span><br>
7294
7295
7296If
7297the 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
7298first output will be done at t = 5400 s. </td>
7299
7300
7301 </tr>
7302
7303
7304
7305    <tr>
7306
7307
7308 <td style="vertical-align: top;"> 
7309     
7310     
7311      <p><a name="termination_time_needed"></a><b>termination_time</b>
7312      <br>
7313
7314
7315 <b>_needed</b></p>
7316
7317
7318 </td>
7319
7320
7321 <td style="vertical-align: top;">R<br>
7322
7323
7324 </td>
7325
7326
7327 <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br>
7328
7329
7330 </td>
7331
7332
7333
7334      <td style="vertical-align: top;"> 
7335     
7336     
7337      <p>CPU time
7338needed for terminal actions at the end of a run in
7339batch mode (in s).<br>
7340
7341
7342 </p>
7343
7344
7345 
7346     
7347     
7348      <p>If the environment
7349variable <b>write_binary </b>is
7350set <i>true</i> (see <a href="chapter_3.3.html">chapter
73513.3</a>), PALM checks the remaining CPU time of the job after
7352each
7353timestep. Time integration must not consume the CPU time completely,
7354since several actions still have to be carried out after time
7355integration has finished (e.g. writing of binary data for the restart
7356run, carrying out output commands, copying of local files to their
7357permanent destinations, etc.) which also takes some time. The maximum
7358possible time needed for these activities plus a reserve is to be given
7359with the parameter <b>termination_time_needed</b>. Among
7360other things,
7361it depends on
7362the number of grid points used. If its value is selected too small,
7363then the
7364respective job will be prematurely aborted by the queuing system, which
7365may result in a data loss and will possibly interrupt the job chain.<br>
7366
7367
7368
7369      </p>
7370
7371
7372 
7373     
7374     
7375      <p>An abort happens in any way, if the environment
7376variable <span style="font-weight: bold;">write_binary</span>
7377is not set to <span style="font-style: italic;">true</span>
7378and if moreover the job has
7379been assigned an insufficient CPU time by <b>mrun</b>
7380option <tt><tt>-t</tt></tt>. <i><br>
7381
7382
7383
7384      </i> </p>
7385
7386
7387 
7388     
7389     
7390      <p><span style="font-weight: bold;">Note:</span><br>
7391
7392
7393
7394On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of
7395PALM
7396have also to be accounted for (e.g. for
7397compilation and copying of input files).</p>
7398
7399
7400 </td>
7401
7402
7403 </tr>
7404
7405
7406
7407    <tr>
7408
7409
7410 <td style="vertical-align: top;"> 
7411     
7412     
7413      <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
7414      <br>
7415
7416
7417 <b>_parameters</b></p>
7418
7419
7420 </td>
7421
7422
7423 <td style="vertical-align: top;">L</td>
7424
7425
7426 <td style="vertical-align: top;"><i>.F.</i></td>
7427
7428
7429
7430      <td style="vertical-align: top;"> 
7431     
7432     
7433      <p>Additional
7434plot of vertical profile data with <span style="font-weight: bold;">profil</span>
7435from preceding runs of the
7436job chain.&nbsp; </p>
7437
7438
7439 
7440     
7441     
7442      <p>This parameter only applies
7443for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
7444= <span style="font-style: italic;">'profil'</span>.</p>
7445
7446
7447     
7448     
7449      <p>By
7450default, plots of horizontally averaged vertical profiles
7451(see <a href="#data_output_pr">data_output_pr</a>)
7452only contain profiles of data produced by the model
7453run. If profiles of prior times (i.e. data of preceding jobs of a
7454job chain) shall be plotted additionally (e.g. for comparison
7455purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>.
7456must be
7457set.<br>
7458
7459
7460 </p>
7461
7462
7463 
7464     
7465     
7466      <p>For further explanation see <a href="chapter_4.5.2.html">chapter
74674.5.2</a>.</p>
7468
7469
7470 </td>
7471
7472
7473 </tr>
7474
7475
7476 <tr>
7477
7478
7479 <td style="vertical-align: top;"> 
7480     
7481     
7482      <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
7483
7484
7485
7486      </td>
7487
7488
7489 <td style="vertical-align: top;">R</td>
7490
7491
7492
7493      <td style="vertical-align: top;"><i>zu(nzt+1) (model
7494top)</i></td>
7495
7496
7497 <td style="vertical-align: top;">
7498     
7499     
7500      <p>Height level up to which horizontally averaged profiles are to
7501be
7502plotted with <span style="font-weight: bold;">profil</span>
7503(in
7504m).&nbsp; </p>
7505
7506
7507 
7508     
7509     
7510      <p>This parameter only applies for
7511&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
7512= <span style="font-style: italic;">'profil'</span>.</p>
7513
7514
7515     
7516     
7517      <p>It
7518affects plots of horizontally averaged profiles
7519(<a href="#data_output_pr">data_output_pr</a>)
7520when plotted with the plot software <span style="font-weight: bold;">profil</span>.
7521By default, profiles are plotted up to the top boundary. The height
7522level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller
7523value.
7524Nevertheless, <span style="font-weight: bold;">all</span>
7525vertical
7526grid points (0 &lt;= k &lt;= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p>
7527
7528
7529
7530     
7531     
7532      <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>
7533has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a>
7534must be used.</p>
7535
7536
7537 </td>
7538
7539
7540 </tr>
7541
7542
7543 <tr>
7544
7545
7546 <td style="vertical-align: top;"> 
7547     
7548     
7549      <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
7550      <br>
7551
7552
7553 <b>_normalized</b></p>
7554
7555
7556 </td>
7557
7558
7559 <td style="vertical-align: top;">R</td>
7560
7561
7562 <td style="vertical-align: top;"><i>determined by plot</i>
7563      <br>
7564
7565
7566 <i>data</i> <br>
7567
7568
7569 </td>
7570
7571
7572 <td style="vertical-align: top;"> 
7573     
7574     
7575      <p>Normalized height
7576level up to which horizontally averaged
7577profiles are to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
7578      </p>
7579
7580
7581 
7582     
7583     
7584      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
7585= <span style="font-style: italic;">'profil'</span>.</p>
7586
7587
7588     
7589     
7590      <p>It
7591affects plots of horizontally averaged profiles
7592(<a href="#data_output_pr">data_output_pr</a>)
7593when plotted with the plot software <span style="font-weight: bold;">profil</span>,
7594if a normalization for the vertical axis is selected
7595(see <a href="#cross_normalized_y">cross_normalized_y</a>).
7596If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b>
7597= <i>1.5</i> means that all profiles up to the height
7598level of z =
75991.5* z<sub>i </sub>are plotted.</p>
7600
7601
7602 </td>
7603
7604
7605 </tr>
7606
7607
7608
7609    <tr>
7610
7611
7612 <td style="vertical-align: top;"> 
7613     
7614     
7615      <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
7616
7617
7618
7619      </td>
7620
7621
7622 <td style="vertical-align: top;">R<br>
7623
7624
7625 </td>
7626
7627
7628
7629      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br>
7630
7631
7632 </td>
7633
7634
7635
7636      <td style="vertical-align: top;"> 
7637     
7638     
7639      <p>Height level
7640up to which 2d cross sections are to be plotted
7641with <span style="font-weight: bold;">iso2d</span>
7642(in m).&nbsp; </p>
7643
7644
7645 
7646     
7647     
7648      <p>This parameter only applies for
7649&nbsp;<a href="#data_output_format">data_output_format</a>
7650= <span style="font-style: italic;">'iso2d'</span>.</p>
7651
7652
7653     
7654     
7655      <p>It
7656affects plots of&nbsp; 2d vertical cross
7657sections (<a href="#data_output">data_output</a>)
7658when plotted with <span style="font-weight: bold;">iso2d</span>.
7659By
7660default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d
7661      </b>the
7662visualization within
7663the plot can be limited to a certain height level (0 &lt;= z
7664&lt;= <b>z_max_do2d</b>).
7665Nevertheless, <span style="font-weight: bold;">all</span>
7666grid points
7667of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>
7668or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
7669The level up to which the section is visualized can later be changed by
7670manually editing the
7671file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>
7672or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>
7673(the respective <span style="font-weight: bold;">iso2d</span>-parameter
7674is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p>
7675
7676
7677
7678      </td>
7679
7680
7681 </tr>
7682
7683
7684 
7685 
7686 
7687  </tbody>
7688</table>
7689
7690
7691<br>
7692
7693
7694
7695<br>
7696
7697
7698<h3 style="line-height: 100%;"><a name="particle_parameters"></a>Particle
7699parameters: </h3>
7700
7701
7702
7703<span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>NAMELIST group name: <span style="font-weight: bold;">particles_par<br>
7704
7705
7706
7707</span>
7708<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
7709
7710
7711 <tbody>
7712
7713
7714    <tr>
7715
7716
7717
7718      <td style="vertical-align: top;"><font size="4"><b>Parameter
7719name</b></font></td>
7720
7721
7722
7723      <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
7724
7725
7726
7727      <td style="vertical-align: top;"> 
7728     
7729     
7730      <p><b><font size="4">Default</font></b> <br>
7731
7732
7733 <b><font size="4">value</font></b></p>
7734
7735
7736 </td>
7737
7738
7739
7740      <td style="vertical-align: top;"> 
7741     
7742     
7743      <p><font size="4"><b>Explanation</b></font></p>
7744
7745
7746
7747      </td>
7748
7749
7750 </tr>
7751
7752
7753 <tr>
7754
7755
7756 <td style="vertical-align: top;"> 
7757     
7758     
7759      <p><a name="dt_prel"></a><b>dt_prel</b></p>
7760
7761
7762
7763      </td>
7764
7765
7766 <td style="vertical-align: top;">R</td>
7767
7768
7769
7770      <td style="vertical-align: top;"><i>9999999.9</i></td>
7771
7772
7773
7774      <td style="vertical-align: top;"> 
7775     
7776     
7777      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
7778interval at
7779which particles are to be released <span lang="en-GB">from
7780a particle
7781source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;
7782      </font> </p>
7783
7784
7785 
7786     
7787     
7788      <p><span lang="en-GB"><font face="Thorndale, serif">By default
7789particles are released only at the beginning of a simulation
7790(t_init=0). The time of the first release (t_init) can be changed with
7791package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>.
7792      </font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
7793set with the package parameter <a href="#end_time_prel">end_time_prel</a>.
7794If <span style="font-weight: bold;">dt_prel</span>
7795has been set, additional
7796releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>,
7797t_init+2*<span style="font-weight: bold;">dt_prel</span>,
7798t_init+3*<span style="font-weight: bold;">dt_prel</span>,
7799etc.. Actual release times
7800may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see
7801e.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>
7802
7803
7804
7805     
7806     
7807      <p><span lang="en-GB"><font face="Thorndale, serif"> The domain
7808of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as
7809well as the distance of&nbsp; released particles
7810within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package
7811parameters </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>
7812      <span lang="en-GB"><font face="Thorndale, serif">and
7813      </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
7814default, one particle is released at all points defined by these
7815parameters. The package parameter <a href="#particles_per_point">particles_per_point</a>
7816can be used to start more than one particle per point.<br>
7817
7818
7819
7820      </font></span></p>
7821
7822
7823 
7824     
7825     
7826      <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
7827different 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">)
7828where each group may have a different source. All particles belonging
7829to one group have the same density ratio and the same radius. All other
7830particle features (e.g. location of the source) are
7831identical for all groups of particles.</font></span></p>
7832
7833
7834Subgrid
7835scale velocities can (optionally) be included for calculating the
7836particle advection, using the method of Weil et al. (2004, JAS, 61,
78372877-2887). This method is switched on by the package
7838parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.
7839This also forces the Euler/upstream method to be used for time
7840advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>).
7841The minimum timestep during the sub-timesteps is controlled by package
7842parameter <a href="#dt_min_part">dt_min_part</a>.
7843     
7844     
7845      <p><span lang="en-GB"><font face="Thorndale, serif">By
7846default, particles are weightless and transported passively with the
7847resolved scale flow. Particles can be given a mass and thus an inertia
7848by assigning the
7849package 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
7850non-zero value (it
7851defines the ratio of the density of the fluid and the density of the
7852particles). 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">
7853must 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>
7854
7855
7856
7857     
7858     
7859      <p><span lang="en-GB"><font face="Thorndale, serif">Boundary
7860conditions for the particle transport can be defined with package
7861parameters </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>
7862      <span lang="en-GB"><font face="Thorndale, serif">and
7863      </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>
7864
7865
7866      <span lang="en-GB"><font face="Thorndale, serif">Timeseries
7867of 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>
7868by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br>
7869
7870
7871      </font></span>
7872     
7873     
7874      <p>For
7875analysis, additional output of
7876particle
7877information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a>
7878(file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br>
7879
7880
7881
7882      </p>
7883
7884
7885 
7886     
7887     
7888      <p><span style="font-family: thorndale,serif;">Statistical
7889informations</span> (e.g. the total number of particles used, the
7890number of particles exchanged between the PEs, etc.) are output to the
7891local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>,
7892if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>.
7893      <br>
7894
7895
7896 </p>
7897
7898
7899 
7900     
7901     
7902      <p><span lang="en-GB"><font face="Thorndale, serif">If a job
7903chain is to be carried out, particle
7904informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
7905location of
7906all
7907particles at the end of the
7908run) is output to
7909the 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>,
7910      <span lang="en-GB"><font face="Thorndale, serif">which
7911must be saved at the
7912end of the run <tt><span lang="en-GB"></span></tt>and
7913given as an
7914input file to the restart run
7915under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>
7916u<span lang="en-GB"><font face="Thorndale, serif">sing
7917respective file
7918connection statements in the <span style="font-weight: bold;">mrun</span>
7919configuration file. </font></span> <span lang="en-GB"></span></p>
7920
7921
7922     
7923     
7924      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
7925particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by
7926the package
7927parameter </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">.
7928For visualization
7929purposes particles can be given a
7930diameter by the parameter <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a>
7931(this diameter only affects the visualization). All particles have the
7932same size. Alternatively, particles can be given an individual size and
7933a </span>color <span lang="en-GB">by modifying the
7934user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">.
7935Particles can pull a
7936&ldquo;tail&rdquo; behind themselves to improve their
7937visualization.
7938This 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>
7939
7940
7941 <span lang="en-GB"></span>
7942     
7943     
7944      <p><b>So far, the
7945particle transport realized in PALM does only
7946work
7947duly in case of a constant vertical grid spacing!</b></p>
7948
7949
7950 </td>
7951
7952
7953
7954    </tr>
7955
7956
7957 <tr>
7958
7959
7960 <td style="vertical-align: top;">
7961     
7962     
7963      <p><a name="bc_par_b"></a><b>bc_par_b</b></p>
7964
7965
7966
7967      </td>
7968
7969
7970 <td style="vertical-align: top;">C*15</td>
7971
7972
7973
7974      <td style="vertical-align: top;"><i>&acute;reflect&acute;</i></td>
7975
7976
7977
7978      <td style="vertical-align: top;"> 
7979     
7980     
7981      <p>Bottom
7982boundary condition for particle transport. </p>
7983
7984
7985 
7986     
7987     
7988      <p>By
7989default, particles are reflected at the bottom boundary.
7990Alternatively, a particle absorption can set by <b>bc_par_b</b>
7991= <i>&acute;absorb&acute;</i>.</p>
7992
7993
7994 </td>
7995
7996
7997
7998    </tr>
7999
8000
8001 <tr>
8002
8003
8004 <td style="vertical-align: top;">
8005     
8006     
8007      <p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
8008
8009
8010
8011      </td>
8012
8013
8014 <td style="vertical-align: top;">C*15</td>
8015
8016
8017
8018      <td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
8019
8020
8021
8022      <td style="vertical-align: top;"> 
8023     
8024     
8025      <p>Lateral
8026boundary condition (x-direction) for particle
8027transport. </p>
8028
8029
8030 
8031     
8032     
8033      <p>By default, cyclic boundary conditions
8034are used along x.
8035Alternatively, reflection (<b>bc_par_lr</b>
8036= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_lr</b>
8037= <i>&acute;absorb&acute;</i>)
8038can be set. <br>
8039
8040
8041 </p>
8042
8043
8044 
8045     
8046     
8047      <p>This lateral boundary
8048conditions should correspond to the
8049lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p>
8050
8051
8052 </td>
8053
8054
8055
8056    </tr>
8057
8058
8059 <tr>
8060
8061
8062 <td style="vertical-align: top;">
8063     
8064     
8065      <p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
8066
8067
8068
8069      </td>
8070
8071
8072 <td style="vertical-align: top;">C*15</td>
8073
8074
8075
8076      <td style="vertical-align: top;"><i>&acute;cyclic&acute;</i></td>
8077
8078
8079
8080      <td style="vertical-align: top;"> 
8081     
8082     
8083      <p>Lateral
8084boundary condition (y-direction) for particle
8085transport. </p>
8086
8087
8088 
8089     
8090     
8091      <p>By default, cyclic boundary conditions
8092are used along y.
8093Alternatively, reflection (<b>bc_par_ns</b>
8094= <i>&acute;reflect&acute;</i>) or absorption (<b>bc_par_ns</b>
8095= <i>&acute;absorb&acute;</i>)
8096can be set.<br>
8097
8098
8099 </p>
8100
8101
8102
8103This lateral boundary conditions should correspond to the lateral
8104boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td>
8105
8106
8107 </tr>
8108
8109
8110
8111    <tr>
8112
8113
8114 <td style="vertical-align: top;"> 
8115     
8116     
8117      <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
8118
8119
8120
8121      </td>
8122
8123
8124 <td style="vertical-align: top;">C*15</td>
8125
8126
8127
8128      <td style="vertical-align: top;"><i>&acute;absorb&acute;</i></td>
8129
8130
8131
8132      <td style="vertical-align: top;"> 
8133     
8134     
8135      <p>Top boundary
8136condition for particle transport. </p>
8137
8138
8139 
8140     
8141     
8142      <p>By default,
8143particles are absorbed at the top boundary.
8144Alternatively, a reflection condition can be set by <b>bc_par_t</b>
8145= <i>&acute;reflect&acute;</i>.</p>
8146
8147
8148 </td>
8149
8150
8151
8152    </tr>
8153
8154
8155 <tr>
8156
8157
8158 <td style="vertical-align: top;">
8159     
8160     
8161      <p><a name="density_ratio"></a><b>density_ratio</b></p>
8162
8163
8164
8165      </td>
8166
8167
8168 <td style="vertical-align: top;">R (10)</td>
8169
8170
8171
8172      <td style="vertical-align: top;"> 
8173     
8174     
8175      <p><i>0.0, 9</i>
8176*<br>
8177
8178
8179 <i>9999999.9</i></p>
8180
8181
8182 </td>
8183
8184
8185 <td style="vertical-align: top;"> 
8186     
8187     
8188      <p>Ratio of the density
8189of the fluid and the density of the
8190particles. </p>
8191
8192
8193 
8194     
8195     
8196      <p>With the default value<i> </i>the
8197particles are weightless and transported passively with the resolved
8198scale flow.
8199In case of <span style="font-wei