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

Last change on this file since 1550 was 555, checked in by raasch, 15 years ago

New:
---

Changed:


Documentation for surface_heatflux in case of prandtl_layer = .F. improved.

bugfix for wrong netcdf/3.6.3 module on lcsgi (mbuild, mrun)

Errors:


Bugfix in if statement (disturb_heatflux)

Bugfix: in 2201 statement: closing " was missing (interpret_config)

Bugfix: default setting of nzb_local for flat topography (init_grid)

Bugfix: wrong dimension used for ts_value_l (user_statistics)

disturb_heatflux, init_grid, interpret_config, user_statistics

  • Property svn:keywords set to Id
File size: 289.2 KB
Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html><head>
3
4
5
6
7
8
9
10
11
12
13 
14 
15 
16 
17  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>PALM chapter 4.2</title></head><body>
18
19
20
21
22<h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
23parameters</a>, <a href="#particle_parameters">particle parameters</a>, and <a href="#Paketparameter">package
24parameters</a></h3>
25
26
27
28
29
30<h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3>
31
32
33
34
35
36<br>
37
38
39
40
41<br>
42
43
44
45
46<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
47
48
49
50
51 <tbody>
52
53
54
55
56
57    <tr>
58
59
60
61
62
63      <td style="vertical-align: top;"><font size="4"><b>Parameter
64name</b></font></td>
65
66
67
68
69 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
70
71
72
73
74
75      <td style="vertical-align: top;"> 
76     
77     
78     
79     
80      <p><b><font size="4">Default</font></b> <br>
81
82
83
84
85 <b><font size="4">value</font></b></p>
86
87
88
89
90 </td>
91
92
93
94
95
96      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
97
98
99
100
101
102    </tr>
103
104
105
106
107 <tr>
108
109
110
111
112 <td style="vertical-align: top;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
113
114
115
116
117
118      </td>
119
120
121
122
123 <td style="vertical-align: top;">R<br>
124
125
126
127
128 </td>
129
130
131
132
133
134      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
135
136
137
138
139 </td>
140
141
142
143
144
145      <td style="vertical-align: top;">Averaging interval for
146all&nbsp;output of temporally averaged data (in s).<br>
147
148
149
150
151      <br>
152
153
154
155
156This
157parameter defines the time interval length for temporally averaged data
158(vertical profiles, spectra, 2d cross-sections, 3d volume data). By
159default,&nbsp;data are not subject to temporal averaging. The
160interval
161length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
162In any case, <span style="font-weight: bold;">averaging_interval</span>
163&lt;= <span style="font-weight: bold;">dt_data_output_av</span>
164must hold.<br>
165
166
167
168
169      <br>
170
171
172
173
174If
175an interval is defined, then by default the average is calculated from
176the data values of all timesteps lying within this interval. The number
177of time levels entering into the average can be reduced with the
178parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br>
179
180
181
182
183      <br>
184
185
186
187
188If
189an averaging interval can not be completed at the end of a run, it
190will be finished at the beginning of the next restart run. Thus for
191restart runs, averaging intervals do not
192necessarily begin at the beginning of the run.<br>
193
194
195
196
197      <br>
198
199
200
201
202Parameters
203      <a href="#averaging_interval_pr">averaging_interval_pr</a>
204and <a href="#averaging_interval_sp">averaging_interval_sp</a>
205can be used to define different averaging intervals for vertical
206profile data and spectra, respectively.<br>
207
208
209
210
211 </td>
212
213
214
215
216 </tr>
217
218
219
220
221
222    <tr>
223
224
225
226
227 <td style="vertical-align: top;"> 
228     
229     
230     
231     
232      <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
233
234
235
236
237
238      </td>
239
240
241
242
243 <td style="vertical-align: top;">R<br>
244
245
246
247
248 </td>
249
250
251
252
253
254      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
255
256
257
258
259
260interval</a><br>
261
262
263
264
265
266      </span> </td>
267
268
269
270
271 <td style="vertical-align: top;">
272     
273     
274     
275     
276      <p>Averaging
277interval for output of vertical profiles&nbsp;to
278local
279file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
280      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
281(in s).&nbsp; </p>
282
283
284
285
286 
287     
288     
289     
290     
291      <p>If
292this parameter is given a non-zero value, temporally
293averaged vertical profile data are output. By default, profile data
294data are not subject to temporal averaging. The interval length is
295limited by the parameter <a href="#dt_dopr">dt_dopr</a>.
296In any case <b>averaging_interval_pr</b> &lt;= <b>dt_dopr
297      </b>must
298hold.</p>
299
300
301
302
303If an interval is defined, then by default the average
304is calculated
305from the data values of all timesteps lying within this interval. The
306number of time levels entering into the average can be reduced with the
307parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>.
308     
309     
310     
311     
312      <p>If
313an averaging interval can not be completed at the end of a run, it will
314be finished at the beginning of the next restart run. Thus for restart
315runs, averaging intervals do not
316necessarily begin at the beginning of the run.</p>
317
318
319
320
321 </td>
322
323
324
325
326 </tr>
327
328
329
330
331
332    <tr>
333
334
335
336
337 <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
338
339
340
341
342
343substeps</span></td>
344
345
346
347
348 <td style="vertical-align: top;">L<br>
349
350
351
352
353
354      </td>
355
356
357
358
359 <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
360
361
362
363
364 </td>
365
366
367
368
369
370      <td style="vertical-align: top;">Switch
371to steer the call of the pressure solver.<br>
372
373
374
375
376 <br>
377
378
379
380
381
382In order to speed-up performance, the Poisson equation for perturbation
383pressure (see <a href="#psolver">psolver</a>) can
384be called only at the last substep of multistep Runge-Kutta
385timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>)
386by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span>
387= <span style="font-style: italic;">.F.</span>.
388In many cases, this sufficiently reduces the divergence of the velocity
389field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this
390case and in case
391of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span>
392= <span style="font-style: italic;">.T.</span>
393should be used.&nbsp;<span style="font-weight: bold;"></span></td>
394
395
396
397
398
399    </tr>
400
401
402
403
404 <tr>
405
406
407
408
409 <td style="vertical-align: top;">
410     
411     
412     
413     
414      <p><a name="fcl_factor"></a><b>cfl_factor</b></p>
415
416
417
418
419
420      </td>
421
422
423
424
425 <td style="vertical-align: top;">R<br>
426
427
428
429
430 </td>
431
432
433
434
435
436      <td style="vertical-align: top;"> 
437     
438     
439     
440     
441      <p><i>0.1,
4420.8 or 0.9</i> <br>
443
444
445
446
447 <i>(see right)</i></p>
448
449
450
451
452
453      </td>
454
455
456
457
458 <td style="vertical-align: top;"> 
459     
460     
461     
462     
463      <p lang="en-GB">Time step limiting factor.&nbsp; </p>
464
465
466
467
468
469     
470     
471     
472     
473      <p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
474allowed </span>time step according to CFL and
475diffusion-criterion
476dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">=
477dt_max * <b>cfl_factor</b>
478in order to avoid stability problems which may arise in the vicinity of
479the maximum allowed timestep. The condition <i>0.0</i>
480&lt; <b>cfl_factor</b>
481&lt; <i>1.0 </i>applies.<br>
482
483
484
485
486 </span></p>
487
488
489
490
491
492     
493     
494     
495     
496      <p><span lang="en-GB">The default value of
497cfl_factor depends on
498the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br>
499
500
501
502
503 </span></p>
504
505
506
507
508 
509     
510     
511     
512     
513      <p><span lang="en-GB">For the third order Runge-Kutta scheme it
514is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br>
515
516
517
518
519 </span></p>
520
521
522
523
524 
525     
526     
527     
528     
529      <p><span lang="en-GB">In case of the leapfrog scheme a quite
530restrictive value of <span style="font-weight: bold;">cfl_factor</span>
531= <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
532divergence
533significantly 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
534be used with the leapfrog scheme but these are to be determined by
535appropriate test runs.<span style="font-family: times new roman;"><br>
536
537
538
539
540
541      </span></span></p>
542
543
544
545
546 <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
547scheme is <span style="font-weight: bold;">cfl_factor</span>
548= <span style="font-style: italic;">0.8</span> .</font></span></td>
549
550
551
552
553
554    </tr>
555
556
557
558
559    <tr>
560
561
562
563
564 <td style="vertical-align: top;"> 
565     
566     
567     
568     
569      <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
570
571
572
573
574
575      </td>
576
577
578
579
580 <td style="vertical-align: top;">L<br>
581
582
583
584
585 </td>
586
587
588
589
590
591      <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
592
593
594
595
596 </td>
597
598
599
600
601
602      <td style="vertical-align: top;"> 
603     
604     
605     
606     
607      <p>Switch to
608impose random perturbations to the horizontal
609velocity field.&nbsp; </p>
610
611
612
613
614 
615     
616     
617     
618     
619      <p>With <b>create_disturbances</b>
620= <i>.T.,</i> random
621perturbations can be imposed to the horizontal velocity field at
622certain times e.g. in order to trigger off the onset of convection,
623etc..<br>
624
625
626
627
628 </p>
629
630
631
632
633 
634     
635     
636     
637     
638      <p>The temporal interval between
639these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
640the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a>
641and <a href="#disturbance_level_t">disturbance_level_t</a>,
642and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>.
643In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
644and <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
645the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a>
646and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>.
647A perturbation is added to each grid point with its individual value
648determined by multiplying the disturbance amplitude with a uniformly
649distributed random number.
650After this, the arrays of u and v are smoothed by applying a
651Shuman-filter twice and made divergence-free by applying the pressure
652solver.<br>
653
654
655
656
657 </p>
658
659
660
661
662 
663     
664     
665     
666     
667      <p>The random number generator to
668be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br>
669
670
671
672
673
674      </p>
675
676
677
678
679 
680     
681     
682     
683     
684      <p>As soon as the desired flow features have
685developed
686(e.g.&nbsp; convection has started), further imposing of
687perturbations
688is not necessary and can be omitted (this does not hold for non-cyclic
689lateral boundaries!). This can be steered by assigning
690an upper limit value for the perturbation energy (the perturbation
691energy is defined by the deviation of the velocity from the mean flow)
692using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>.
693As soon as the perturbation energy has exceeded this energy limit, no
694more random perturbations are assigned<br>
695
696
697
698
699
700.&nbsp; <br>
701
702
703
704
705
706Timesteps where a random perturbation has been imposed are marked in
707the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
708by the character "D" appended to the values of the maximum horizontal
709velocities. </p>
710
711
712
713
714 </td>
715
716
717
718
719 </tr>
720
721
722
723
724 <tr>
725
726
727
728
729 <td style="vertical-align: top;"> 
730     
731     
732     
733     
734      <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
735
736
737
738
739
740      </td>
741
742
743
744
745 <td style="vertical-align: top;">C*10&nbsp;
746      <br>
747
748
749
750
751&nbsp;&nbsp; (100)</td>
752
753
754
755
756 <td style="vertical-align: top;"><i>100 * ' '</i></td>
757
758
759
760
761
762      <td style="vertical-align: top;"> 
763     
764     
765     
766     
767      <p>Type of
768normalization applied to the x-coordinate of vertical
769profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
770
771
772
773
774
775     
776     
777     
778     
779      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
780= <span style="font-style: italic;">'profil'</span>.</p>
781
782
783
784
785     
786     
787     
788     
789      <p>If
790vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
791local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
792parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
793the x-values of the data points can be normalized with respect to
794certain quantities (e.g. the near-surface heat flux) in order to ensure
795a better comparability. This type of normalization then applies to all
796profiles of one coordinate system (panel). The normalization quantities
797are re-calculated for each output time of each individual profile. If
798temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>),
799then the normalization quantities are also temporally averaged
800accordingly. If the value of a normalization quantity becomes zero,
801then normalization for the total respective coordinate system (panel)
802is switched off automatically (also for the y-axis).<br>
803
804
805
806
807 </p>
808
809
810
811
812
813     
814     
815     
816     
817      <p>By default, the normalization quantities are calculated as the
818horizontal mean of the total model domain and and these values are also
819used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
820Instead of this, they can be calculated from the data of a certain
821subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a>
822(however, they are used again for all subdomains and even for the total
823domain).&nbsp; </p>
824
825
826
827
828 
829     
830     
831     
832     
833      <p>The user can choose between
834the following normalization
835quantities: <br>
836
837
838
839
840 </p>
841
842
843
844
845 
846     
847     
848     
849     
850      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
851
852
853
854
855 <tbody>
856
857
858
859
860 <tr>
861
862
863
864
865 <td style="vertical-align: top;"><i>'wpt0'</i></td>
866
867
868
869
870
871            <td style="vertical-align: top;">Normalization with
872respect
873to the total surface sensible heat
874flux (k=0 ).</td>
875
876
877
878
879 </tr>
880
881
882
883
884 <tr>
885
886
887
888
889 <td style="vertical-align: middle;"><i>'ws2'</i></td>
890
891
892
893
894
895            <td style="vertical-align: top;">Normalization with
896respect
897to w<sub>*</sub> <sup>2</sup>
898(square of the characteristic vertical wind speed of the CBL)</td>
899
900
901
902
903
904          </tr>
905
906
907
908
909 <tr>
910
911
912
913
914 <td style="vertical-align: top;"><i>'tsw2'</i></td>
915
916
917
918
919
920            <td style="vertical-align: top;">Normalization with
921respect
922to the square of the characteristic
923temperature of the CBL theta<sub>*</sub> (this is defined
924as ratio of
925the surface heat flux and w<sub>*</sub>).</td>
926
927
928
929
930 </tr>
931
932
933
934
935
936          <tr>
937
938
939
940
941 <td style="vertical-align: middle;"><i>'ws3'</i></td>
942
943
944
945
946
947            <td style="vertical-align: top;">Normalization with
948respect
949to w<sub>*</sub> <sup>3</sup>.</td>
950
951
952
953
954 </tr>
955
956
957
958
959
960          <tr>
961
962
963
964
965 <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
966
967
968
969
970
971            <td style="vertical-align: top;">Normalization with
972respect
973to w<sub>*</sub><sup>2</sup>theta<sub>*</sub>
974(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
975
976
977
978
979
980          </tr>
981
982
983
984
985 <tr>
986
987
988
989
990 <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
991
992
993
994
995
996            <td style="vertical-align: top;">Normalization with
997respect
998to w<sub>*</sub><sup>2 </sup>theta<sub>*</sub>
999(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
1000
1001
1002
1003
1004
1005          </tr>
1006
1007
1008
1009
1010 
1011       
1012       
1013       
1014       
1015        </tbody> 
1016     
1017     
1018     
1019     
1020      </table>
1021
1022
1023
1024
1025 
1026     
1027     
1028     
1029     
1030      <p>For each
1031coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>)
1032an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> =
1033      <span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
1034then the
1035x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
1036and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>.
1037Data
1038of the further coordinate systems (if any are to be drawn) are not
1039normalized.&nbsp; </p>
1040
1041
1042
1043
1044 
1045     
1046     
1047     
1048     
1049      <p>Using a normalization
1050leaves all vertical profile data on
1051local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
1052unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the
1053normalization is steered
1054by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a>
1055which may be changed subsequently by the user in the parameter file
1056(local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
1057
1058
1059
1060
1061
1062&nbsp;<br>
1063
1064
1065
1066
1067
1068The assigned normalization quantity is noted in the axes labels of the
1069respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
1070
1071
1072
1073
1074
1075      </td>
1076
1077
1078
1079
1080 </tr>
1081
1082
1083
1084
1085 <tr>
1086
1087
1088
1089
1090 <td style="vertical-align: top;"> 
1091     
1092     
1093     
1094     
1095      <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
1096
1097
1098
1099
1100
1101      </td>
1102
1103
1104
1105
1106 <td style="vertical-align: top;">C*10&nbsp;
1107      <br>
1108
1109
1110
1111
1112&nbsp;&nbsp; (100)</td>
1113
1114
1115
1116
1117 <td style="vertical-align: top;"><i>100 * ' '</i></td>
1118
1119
1120
1121
1122
1123      <td style="vertical-align: top;"> 
1124     
1125     
1126     
1127     
1128      <p>Type of
1129normalization applied to the y-coordinate of vertical
1130profiles to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;</p>
1131
1132
1133
1134
1135
1136     
1137     
1138     
1139     
1140      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1141= <span style="font-style: italic;">'profil'</span>.</p>
1142
1143
1144
1145
1146     
1147     
1148     
1149     
1150      <p>If
1151vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
1152local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
1153parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
1154the y-values of the data points can be normalized with respect to
1155certain quantities (at present only the normalization with respect to
1156the boundary layer height is possible) in order to ensure a better
1157comparability. </p>
1158
1159
1160
1161
1162 
1163     
1164     
1165     
1166     
1167      <p>The user can choose between the
1168following normalization
1169quantities: <br>
1170
1171
1172
1173
1174 </p>
1175
1176
1177
1178
1179 
1180     
1181     
1182     
1183     
1184      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
1185
1186
1187
1188
1189 <tbody>
1190
1191
1192
1193
1194 <tr>
1195
1196
1197
1198
1199 <td style="vertical-align: top;"><i>'z_i'</i></td>
1200
1201
1202
1203
1204
1205            <td style="vertical-align: top;">Normalization with
1206respect
1207to the boundary layer height
1208(determined from the height where the heat flux achieves its minimum
1209value).</td>
1210
1211
1212
1213
1214 </tr>
1215
1216
1217
1218
1219 
1220       
1221       
1222       
1223       
1224        </tbody> 
1225     
1226     
1227     
1228     
1229      </table>
1230
1231
1232
1233
1234 
1235     
1236     
1237     
1238     
1239      <p>For
1240further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p>
1241
1242
1243
1244
1245
1246      </td>
1247
1248
1249
1250
1251 </tr>
1252
1253
1254
1255
1256 <tr>
1257
1258
1259
1260
1261 <td style="vertical-align: top;"> 
1262     
1263     
1264     
1265     
1266      <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
1267
1268
1269
1270
1271
1272      </td>
1273
1274
1275
1276
1277 <td style="vertical-align: top;">C*100&nbsp;
1278      <br>
1279
1280
1281
1282
1283&nbsp;&nbsp; (100)</td>
1284
1285
1286
1287
1288 <td style="vertical-align: top;">see right<br>
1289
1290
1291
1292
1293 </td>
1294
1295
1296
1297
1298
1299      <td style="vertical-align: top;"> 
1300     
1301     
1302     
1303     
1304      <p>Determines
1305which vertical profiles are to be presented in
1306which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used.
1307&nbsp; </p>
1308
1309
1310
1311
1312 
1313     
1314     
1315     
1316     
1317      <p>This parameter only applies for
1318&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1319= <span style="font-style: italic;">'profil'</span>.</p>
1320
1321
1322
1323
1324     
1325     
1326     
1327     
1328      <p>The
1329default assignment is:&nbsp; </p>
1330
1331
1332
1333
1334 
1335     
1336     
1337     
1338     
1339      <p><b>cross_profiles</b>
1340=&nbsp; </p>
1341
1342
1343
1344
1345 
1346     
1347     
1348     
1349     
1350      <ul>
1351
1352
1353
1354
1355 
1356       
1357       
1358       
1359       
1360        <p><span style="font-family: monospace; font-style: italic;">'
1361u v ',</span><br>
1362
1363
1364
1365
1366 <span style="font-family: monospace; font-style: italic;">' pt
1367',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
1368
1369
1370
1371
1372 <span style="font-family: monospace; font-style: italic;">'
1373w"pt" w*pt* w*pt*BC wpt wptBC ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
1374
1375
1376
1377
1378 <span style="font-family: monospace; font-style: italic;">'
1379w"u" w*u* wu w"v"w*v* wv ',&nbsp; </span><br style="font-family: monospace; font-style: italic;">
1380
1381
1382
1383
1384 <span style="font-family: monospace; font-style: italic;">' km
1385kh ',</span><br style="font-family: monospace; font-style: italic;">
1386
1387
1388
1389
1390 <span style="font-family: monospace; font-style: italic;">' l '
1391,</span><br>
1392
1393
1394
1395
1396
139714 * <span style="font-family: monospace; font-style: italic;">'
1398'</span></p>
1399
1400
1401
1402
1403 
1404     
1405     
1406     
1407     
1408      </ul>
1409
1410
1411
1412
1413 
1414     
1415     
1416     
1417     
1418      <p>If plot output of
1419vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
1420the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.
1421Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
1422which describes the layout for a plot to be generated with the plot
1423program <span style="font-weight: bold;">profil</span>.
1424The parameter <b>cross_profiles</b>
1425determines how many coordinate systems (panels) the plot contains and
1426which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
1427expects a character string (up to 100 characters long) for each
1428coordinate system, which consists of the names of the profiles to be
1429drawn into this system (all available profiles and their respective
1430names are described at parameter <a href="#data_output_pr">data_output_pr</a>).
1431The single names have to be separated by one blank (' ') and a blank
1432must be spent also at the beginning and at the end of the
1433string.&nbsp; </p>
1434
1435
1436
1437
1438 
1439     
1440     
1441     
1442     
1443      <p>Example:&nbsp; </p>
1444
1445
1446
1447
1448 
1449     
1450     
1451     
1452     
1453      <ul>
1454
1455
1456
1457
1458
1459       
1460       
1461       
1462       
1463        <p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
1464' pt '</span></p>
1465
1466
1467
1468
1469 
1470     
1471     
1472     
1473     
1474      </ul>
1475
1476
1477
1478
1479 
1480     
1481     
1482     
1483     
1484      <p>In this case the
1485plot consists of two coordinate systems
1486(panels) with the first panel containing the profiles of the horizontal
1487velocity components (<span style="font-style: italic;">'u'</span>
1488and <span style="font-style: italic;">'v'</span>)
1489of all output times (see <a href="#dt_dopr">dt_dopr</a>)
1490and the second one containing the profiles of the potential temperature
1491(<span style="font-style: italic;">'pt'</span>).<br>
1492
1493
1494
1495
1496
1497      </p>
1498
1499
1500
1501
1502 
1503     
1504     
1505     
1506     
1507      <p>Whether the coordinate systems are actually drawn,
1508depends on
1509whether data of the appropriate profiles were output during the run
1510(profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>).
1511For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned,
1512then
1513the plot only consists of one panel, since no profiles of the potential
1514temperature were output. On the other hand, if profiles were assigned
1515to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>,
1516then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
1517but they are not drawn in the plot. <br>
1518
1519
1520
1521
1522 </p>
1523
1524
1525
1526
1527
1528The arrangement of the panels in the plot can be controlled
1529with the parameters <a href="#profile_columns">profile_columns</a>
1530and <a href="#profile_rows">profile_rows</a>.
1531Up to 100 panels systems are allowed in a plot (however, they may be
1532distributed on several pages).</td>
1533
1534
1535
1536
1537 </tr>
1538
1539
1540
1541
1542 <tr>
1543
1544
1545
1546
1547 <td style="vertical-align: top;"> 
1548     
1549     
1550     
1551     
1552      <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
1553
1554
1555
1556
1557
1558      </td>
1559
1560
1561
1562
1563 <td style="vertical-align: top;">C*40&nbsp;
1564      <br>
1565
1566
1567
1568
1569&nbsp;&nbsp; (100)</td>
1570
1571
1572
1573
1574 <td style="vertical-align: top;">see right<br>
1575
1576
1577
1578
1579 </td>
1580
1581
1582
1583
1584
1585      <td style="vertical-align: top;"> 
1586     
1587     
1588     
1589     
1590      <p>x-axis labels
1591of vertical profile coordinate systems to be
1592plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
1593      </p>
1594
1595
1596
1597
1598 
1599     
1600     
1601     
1602     
1603      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
1604= <span style="font-style: italic;">'profil'</span>.</p>
1605
1606
1607
1608
1609     
1610     
1611     
1612     
1613      <p>The
1614default assignment is:&nbsp; </p>
1615
1616
1617
1618
1619 
1620     
1621     
1622     
1623     
1624      <p><b>cross_xtext</b>
1625=&nbsp; </p>
1626
1627
1628
1629
1630 
1631     
1632     
1633     
1634     
1635      <ul>
1636
1637
1638
1639
1640 
1641       
1642       
1643       
1644       
1645        <p><span style="font-style: italic;">'wind speed in
1646ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1647
1648
1649
1650
1651 <span style="font-style: italic;">'pot. temperature in
1652K',&nbsp; </span><br style="font-style: italic;">
1653
1654
1655
1656
1657
1658        <span style="font-style: italic;">'heat flux in K
1659ms&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1660
1661
1662
1663
1664 <span style="font-style: italic;">'momentum flux in
1665m&gt;2s&gt;2',&nbsp; </span><br style="font-style: italic;">
1666
1667
1668
1669
1670 <span style="font-style: italic;">'eddy diffusivity in
1671m&gt;2s&gt;-&gt;1',&nbsp; </span><br style="font-style: italic;">
1672
1673
1674
1675
1676 <span style="font-style: italic;">'mixing length in m',</span>&nbsp;
1677        <br>
1678
1679
1680
1681
168214 * <span style="font-style: italic;">' '</span></p>
1683
1684
1685
1686
1687
1688     
1689     
1690     
1691     
1692      </ul>
1693
1694
1695
1696
1697 
1698     
1699     
1700     
1701     
1702      <p>This parameter can be used to assign x-axis
1703labels to vertical
1704profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output
1705of vertical
1706profile data see <a href="#data_output_pr">data_output_pr</a>).<br>
1707
1708
1709
1710
1711
1712The labels are assigned to those coordinate systems (panels) defined by
1713      <a href="#cross_profiles">cross_profiles</a>
1714according to their respective order (compare the default values of <b>cross_xtext</b>
1715and <b>cross_profiles</b>). </p>
1716
1717
1718
1719
1720 
1721     
1722     
1723     
1724     
1725      <p>Umlauts
1726are possible (write &#8220; in front of, similar to TeX), as
1727well as super- and subscripts (use "&gt;" or "&lt;" in front of
1728each
1729character), special characters etc. (see UNIRAS manuals) when using the
1730plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p>
1731
1732
1733
1734
1735
1736      </td>
1737
1738
1739
1740
1741 </tr>
1742
1743
1744
1745
1746 <tr>
1747
1748
1749
1750
1751 <td style="vertical-align: top;"> 
1752     
1753     
1754     
1755     
1756      <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
1757
1758
1759
1760
1761
1762      </td>
1763
1764
1765
1766
1767 <td style="vertical-align: top;">C*1</td>
1768
1769
1770
1771
1772
1773      <td style="vertical-align: top;"><i>'w'</i></td>
1774
1775
1776
1777
1778
1779      <td style="vertical-align: top;"> 
1780     
1781     
1782     
1783     
1784      <p>Type of cycle
1785to be used with the multi-grid method.&nbsp; </p>
1786
1787
1788
1789
1790 
1791     
1792     
1793     
1794     
1795      <p>This
1796parameter determines which type of cycle is applied in
1797the multi-grid method used for solving the Poisson equation for
1798perturbation pressure (see <a href="#psolver">psolver</a>).
1799It defines in which way it is switched between the fine and coarse
1800grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b>
1801may be assigned the values <i>'v'</i> or <i>'w'</i>).
1802The
1803computational cost of w-cycles is much higher than that of v-cycles,
1804however, w-cycles give a much better convergence. </p>
1805
1806
1807
1808
1809 </td>
1810
1811
1812
1813
1814
1815    </tr>
1816
1817
1818
1819
1820 <tr>
1821
1822
1823
1824
1825 <td style="vertical-align: top;">
1826     
1827     
1828     
1829     
1830      <p><a name="data_output"></a><b>data_output</b></p>
1831
1832
1833
1834
1835
1836      </td>
1837
1838
1839
1840
1841 <td style="vertical-align: top;">C * 10 (100)<br>
1842
1843
1844
1845
1846
1847      </td>
1848
1849
1850
1851
1852 <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
1853
1854
1855
1856
1857
1858      </td>
1859
1860
1861
1862
1863 <td style="vertical-align: top;">Quantities
1864for which 2d cross section and/or 3d volume data are to be output.<br>
1865
1866
1867
1868
1869      <br>
1870
1871
1872
1873
1874PALM
1875allows the output of instantaneous data as well as of temporally
1876averaged data which is steered by the strings assigned to this
1877parameter (see below).<br>
1878
1879
1880
1881
1882      <br>
1883
1884
1885
1886
1887By default, cross section
1888data are output (depending on the selected cross sections(s), see
1889below)&nbsp; to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>,
1890      <a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
1891and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>.
1892Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>.
1893If the user has switched on the output of temporally averaged data,
1894these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>,
1895      <a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
1896      <a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
1897and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
1898respectively.<br>
1899
1900
1901
1902
1903      <br>
1904
1905
1906
1907
1908The
1909filenames already suggest that all files have NetCDF format.
1910Informations about the file content (kind of quantities, array
1911dimensions and grid coordinates) are part of the self describing NetCDF
1912format and can be extracted from the NetCDF files using the command
1913"ncdump -c &lt;filename&gt;". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing
1914the PALM NetCDF data.<br>
1915
1916
1917
1918
1919      <br>
1920
1921
1922
1923
1924The following quantities are
1925available for output by default (quantity names ending with '*' are only allowed for the output of horizontal cross sections):<br>
1926
1927
1928
1929
1930      <br>
1931
1932
1933
1934
1935     
1936     
1937     
1938     
1939      <table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2">
1940
1941
1942
1943
1944        <tbody>
1945
1946
1947
1948
1949          <tr>
1950
1951
1952
1953
1954            <td style="width: 106px;"><span style="font-weight: bold;">quantity
1955name</span></td>
1956
1957
1958
1959
1960            <td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td>
1961
1962
1963
1964
1965            <td><span style="font-weight: bold;">unit</span></td>
1966
1967
1968
1969
1970            <td><span style="font-weight: bold;">remarks</span></td>
1971
1972
1973
1974
1975          </tr>
1976
1977
1978
1979
1980          <tr>
1981
1982
1983
1984
1985            <td style="width: 106px;"><span style="font-style: italic;">e</span></td>
1986
1987
1988
1989
1990            <td style="width: 196px;">SGS TKE</td>
1991
1992
1993
1994
1995            <td>m<sup>2</sup>/s<sup>2</sup></td>
1996
1997
1998
1999
2000            <td><br>
2001</td>
2002
2003
2004
2005
2006          </tr>
2007
2008
2009
2010
2011          <tr>
2012
2013
2014
2015
2016            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td>
2017
2018
2019
2020
2021            <td style="width: 196px; vertical-align: top;">liquid water path</td>
2022
2023
2024
2025
2026            <td style="vertical-align: top;">m</td>
2027
2028
2029
2030
2031            <td style="vertical-align: top;">only horizontal cross section
2032is allowed,&nbsp;requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
2033= <span style="font-style: italic;">.TRUE.</span></td>
2034
2035
2036
2037
2038          </tr>
2039
2040
2041
2042
2043          <tr>
2044
2045
2046
2047
2048            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td>
2049
2050
2051
2052
2053            <td style="width: 196px; vertical-align: top;">perturpation
2054pressure</td>
2055
2056
2057
2058
2059            <td style="vertical-align: top;">N/m<sup>2</sup>,
2060Pa</td>
2061
2062
2063
2064
2065            <td style="vertical-align: top;"><br>
2066</td>
2067
2068
2069
2070
2071          </tr>
2072
2073
2074
2075
2076          <tr>
2077
2078
2079
2080
2081            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td>
2082
2083
2084
2085
2086            <td style="width: 196px; vertical-align: top;">particle/droplet
2087concentration</td>
2088
2089
2090
2091
2092            <td style="vertical-align: top;">#/gridbox</td>
2093
2094
2095
2096
2097            <td style="vertical-align: top;">requires that particle
2098advection is switched on by <span style="font-weight: bold;">mrun</span>-option
2099"-p particles"</td>
2100
2101
2102
2103
2104          </tr>
2105
2106
2107
2108
2109          <tr>
2110
2111
2112
2113
2114            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td>
2115
2116
2117
2118
2119            <td style="width: 196px; vertical-align: top;">mean
2120particle/droplet radius </td>
2121
2122
2123
2124
2125            <td style="vertical-align: top;">m</td>
2126
2127
2128
2129
2130            <td style="vertical-align: top;">requires that particle
2131advection is switched on by <span style="font-weight: bold;">mrun</span>-option
2132"-p particles"</td>
2133
2134
2135
2136
2137          </tr>
2138
2139
2140
2141
2142          <tr>
2143
2144
2145
2146
2147            <td style="vertical-align: top;"><span style="font-style: italic;">pra*</span></td>
2148
2149
2150
2151
2152            <td style="vertical-align: top;">precipitation amount</td>
2153
2154
2155
2156
2157            <td style="vertical-align: top;">mm</td>
2158
2159
2160
2161
2162            <td style="vertical-align: top;">only horizontal cross section
2163is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
2164= <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>
2165
2166
2167
2168
2169          </tr>
2170
2171
2172
2173
2174          <tr>
2175
2176
2177
2178
2179            <td style="vertical-align: top;"><span style="font-style: italic;">prr*</span></td>
2180
2181
2182
2183
2184            <td style="vertical-align: top;">precipitation rate</td>
2185
2186
2187
2188
2189            <td style="vertical-align: top;">mm/s</td>
2190
2191
2192
2193
2194            <td style="vertical-align: top;">only horizontal cross section
2195is allowed,&nbsp;requires&nbsp;<a href="chapter_4.1.html#precipitation">precipitation</a>
2196= <span style="font-style: italic;">.TRUE.</span></td>
2197
2198
2199
2200
2201          </tr>
2202
2203
2204
2205
2206          <tr>
2207
2208
2209
2210
2211            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td>
2212
2213
2214
2215
2216            <td style="width: 196px; vertical-align: top;">potential
2217temperature<br>
2218
2219
2220
2221
2222            </td>
2223
2224
2225
2226
2227            <td style="vertical-align: top;">K</td>
2228
2229
2230
2231
2232            <td style="vertical-align: top;"><br>
2233</td>
2234
2235
2236
2237
2238          </tr>
2239
2240
2241
2242
2243          <tr>
2244
2245
2246
2247
2248            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td>
2249
2250
2251
2252
2253            <td style="width: 196px; vertical-align: top;">specific humidity
2254(or total water content, if cloud physics is switched on)</td>
2255
2256
2257
2258
2259            <td style="vertical-align: top;">kg/kg</td>
2260
2261
2262
2263
2264            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
2265
2266
2267
2268
2269          </tr>
2270
2271
2272
2273
2274          <tr>
2275
2276
2277
2278
2279            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td>
2280
2281
2282
2283
2284            <td style="width: 196px; vertical-align: top;">liquid water
2285content</td>
2286
2287
2288
2289
2290            <td style="vertical-align: top;">kg/kg</td>
2291
2292
2293
2294
2295            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
2296= <span style="font-style: italic;">.TRUE.</span>
2297or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
2298= <span style="font-style: italic;">.TRUE.</span></td>
2299
2300
2301
2302
2303          </tr>
2304
2305
2306
2307
2308          <tr>
2309
2310
2311
2312
2313            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td>
2314
2315
2316
2317
2318            <td style="width: 196px; vertical-align: top;">change in liquid
2319water content due to condensation/evaporation during last timestep</td>
2320
2321
2322
2323
2324            <td style="vertical-align: top;">kg/kg</td>
2325
2326
2327
2328
2329            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
2330= <span style="font-style: italic;">.TRUE.</span></td>
2331
2332
2333
2334
2335          </tr>
2336
2337
2338
2339
2340          <tr>
2341
2342
2343
2344
2345            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td>
2346
2347
2348
2349
2350            <td style="width: 196px; vertical-align: top;">volume of liquid
2351water</td>
2352
2353
2354
2355
2356            <td style="vertical-align: top;">m<sup>3</sup>/gridbox</td>
2357
2358
2359
2360
2361            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
2362= <span style="font-style: italic;">.TRUE.</span></td>
2363
2364
2365
2366
2367          </tr>
2368
2369
2370
2371
2372          <tr>
2373
2374
2375
2376
2377            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td>
2378
2379
2380
2381
2382            <td style="width: 196px; vertical-align: top;">weighting factor</td>
2383
2384
2385
2386
2387            <td style="vertical-align: top;"><br>
2388</td>
2389
2390
2391
2392
2393            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
2394= <span style="font-style: italic;">.TRUE.</span></td>
2395
2396
2397
2398
2399          </tr>
2400
2401
2402
2403
2404          <tr>
2405
2406            <td>qsws*</td>
2407
2408            <td>latent&nbsp;surface heatflux</td>
2409
2410            <td>kg/kg * m/s</td>
2411
2412            <td>only horizontal cross section is allowed, requires humidity = .TRUE. </td>
2413
2414          </tr>
2415
2416          <tr>
2417
2418
2419
2420
2421            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td>
2422
2423
2424
2425
2426            <td style="width: 196px; vertical-align: top;">water vapor
2427content (specific humidity)</td>
2428
2429
2430
2431
2432            <td style="vertical-align: top;">kg/kg</td>
2433
2434
2435
2436
2437            <td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
2438= <span style="font-style: italic;">.TRUE.</span></td>
2439
2440
2441
2442
2443          </tr>
2444
2445
2446
2447
2448          <tr>
2449
2450
2451
2452
2453            <td align="undefined" valign="undefined"><span style="font-style: italic;">rho</span></td>
2454
2455
2456
2457
2458            <td align="undefined" valign="undefined">potential density</td>
2459
2460
2461
2462
2463            <td align="undefined" valign="undefined">kg/m<sup>3</sup></td>
2464
2465
2466
2467
2468            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
2469= <span style="font-style: italic;">.TRUE.</span></td>
2470
2471
2472
2473
2474          </tr>
2475
2476
2477
2478
2479          <tr>
2480
2481
2482
2483
2484            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td>
2485
2486
2487
2488
2489            <td style="width: 196px; vertical-align: top;">concentration of
2490the scalar</td>
2491
2492
2493
2494
2495            <td style="vertical-align: top;">1/m<sup>3</sup></td>
2496
2497
2498
2499
2500            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
2501= <span style="font-style: italic;">.TRUE.</span></td>
2502
2503
2504
2505
2506          </tr>
2507
2508
2509
2510
2511          <tr>
2512
2513
2514
2515
2516            <td align="undefined" valign="undefined"><span style="font-style: italic;">sa</span></td>
2517
2518
2519
2520
2521            <td align="undefined" valign="undefined">salinity</td>
2522
2523
2524
2525
2526            <td align="undefined" valign="undefined">psu</td>
2527
2528
2529
2530
2531            <td align="undefined" valign="undefined">requires&nbsp;<a href="chapter_4.1.html#ocean">ocean</a>
2532= <span style="font-style: italic;">.TRUE.</span></td>
2533
2534
2535
2536
2537          </tr>
2538
2539
2540
2541
2542          <tr>
2543
2544            <td>shf*</td>
2545
2546            <td>sensible surface heatflux</td>
2547
2548            <td>K m/s</td>
2549
2550            <td>only horizontal cross section is allowed</td>
2551
2552          </tr>
2553
2554          <tr>
2555
2556
2557
2558
2559            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td>
2560
2561
2562
2563
2564            <td style="width: 196px; vertical-align: top;">(near surface)
2565characteristic temperature</td>
2566
2567
2568
2569
2570            <td style="vertical-align: top;">K</td>
2571
2572
2573
2574
2575            <td style="vertical-align: top;">only horizontal cross section
2576is allowed</td>
2577
2578
2579
2580
2581          </tr>
2582
2583
2584
2585
2586          <tr>
2587
2588
2589
2590
2591            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td>
2592
2593
2594
2595
2596            <td style="width: 196px; vertical-align: top;">u-component of
2597the velocity</td>
2598
2599
2600
2601
2602            <td style="vertical-align: top;">m/s</td>
2603
2604
2605
2606
2607            <td style="vertical-align: top;"><br>
2608</td>
2609
2610
2611
2612
2613          </tr>
2614
2615
2616
2617
2618          <tr>
2619
2620
2621
2622
2623            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td>
2624
2625
2626
2627
2628            <td style="width: 196px; vertical-align: top;">(near surface)
2629friction velocity</td>
2630
2631
2632
2633
2634            <td style="vertical-align: top;">m/s</td>
2635
2636
2637
2638
2639            <td style="vertical-align: top;">only horizontal cross section
2640is allowed</td>
2641
2642
2643
2644
2645          </tr>
2646
2647
2648
2649
2650          <tr>
2651
2652
2653
2654
2655            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td>
2656
2657
2658
2659
2660            <td style="width: 196px; vertical-align: top;">v-component of
2661the velocity</td>
2662
2663
2664
2665
2666            <td style="vertical-align: top;">m/s</td>
2667
2668
2669
2670
2671            <td style="vertical-align: top;"><br>
2672</td>
2673
2674
2675
2676
2677          </tr>
2678
2679
2680
2681
2682          <tr>
2683
2684
2685
2686
2687            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td>
2688
2689
2690
2691
2692            <td style="width: 196px; vertical-align: top;">virtual potential
2693temperature</td>
2694
2695
2696
2697
2698            <td style="vertical-align: top;">K</td>
2699
2700
2701
2702
2703            <td style="vertical-align: top;">requires&nbsp;<a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td>
2704
2705
2706
2707
2708          </tr>
2709
2710
2711
2712
2713          <tr>
2714
2715
2716
2717
2718            <td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td>
2719
2720
2721
2722
2723            <td style="width: 196px; vertical-align: top;">w-component of
2724the velocity</td>
2725
2726
2727
2728
2729            <td style="vertical-align: top;">m/s</td>
2730
2731
2732
2733
2734            <td style="vertical-align: top;"><br>
2735</td>
2736
2737
2738
2739
2740          </tr>
2741
2742
2743
2744
2745          <tr>
2746
2747
2748
2749
2750            <td style="vertical-align: top;"><span style="font-style: italic;">z0*</span></td>
2751
2752
2753
2754
2755            <td style="vertical-align: top;">roughness length</td>
2756
2757
2758
2759
2760            <td style="vertical-align: top;">m</td>
2761
2762
2763
2764
2765            <td><br>
2766</td>
2767
2768
2769
2770
2771          </tr>
2772
2773
2774
2775
2776       
2777       
2778       
2779       
2780        </tbody>
2781     
2782     
2783     
2784     
2785      </table>
2786
2787
2788
2789
2790      <br>
2791
2792
2793
2794
2795Multiple
2796quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span>
2797= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br>
2798
2799
2800
2801
2802      <br>
2803
2804
2805
2806
2807By
2808assigning the pure strings from the above table, 3d volume data is
2809output. 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
2810respective quantities. Time averaged&nbsp;output is created by
2811appending the string <span style="font-style: italic;">'_av'
2812      </span>(for
2813cross section data, this string must be appended after the cross
2814section string). Cross section data can also be (additionally) averaged
2815along the direction normal to the respective section (see below).
2816Assignments of quantities can be given in arbitrary
2817order:<br>
2818
2819
2820
2821
2822      <br>
2823
2824
2825
2826
2827Example:<br>
2828
2829
2830
2831
2832      <br>
2833
2834
2835
2836
2837     
2838     
2839     
2840     
2841      <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>
2842
2843
2844
2845
2846      </div>
2847
2848
2849
2850
2851      <br>
2852
2853
2854
2855
2856This
2857example will create the following output: instantaneous 3d volume data
2858of u-velocity component (by default on file DATA_3D_NETCDF), temporally
2859averaged 3d volume data of u-velocity component (by default on file
2860DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of
2861w-velocity component (by default on file DATA_2D_XY_NETCDF), and
2862temporally averaged vertical cross section data of potential
2863temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br>
2864
2865
2866
2867
2868      <br>
2869
2870
2871
2872
2873The
2874user is allowed to extend the above list of quantities by defining his
2875own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br>
2876
2877
2878
2879
2880      <br>
2881
2882
2883
2884
2885The
2886time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
2887This is valid for all types of output quantities by default. Individual
2888time intervals for instantaneous &nbsp;(!) 3d and section data can
2889be
2890declared 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>
2891
2892
2893
2894
2895      <br>
2896
2897
2898
2899
2900Also,
2901an individual time interval for output of temporally averaged data can
2902be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
2903This applies to both 3d volume and cross section data. The length of
2904the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br>
2905
2906
2907
2908
2909      <br>
2910
2911
2912
2913
2914The
2915parameter <a href="#skip_time_data_output">skip_time_data_output</a>
2916can be used to shift data output activities for a given time interval.
2917Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>,
2918      <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>
2919
2920
2921
2922
2923     
2924     
2925     
2926     
2927      <p>With
2928the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>&nbsp;
2929the output can be limited in the vertical direction up to a certain
2930grid point.<br>
2931
2932
2933
2934
2935 </p>
2936
2937
2938
2939
2940 Cross sections extend through the
2941total model
2942domain. In the two horizontal directions all grid points with 0
2943&lt;= i
2944&lt;= nx+1 and 0 &lt;= j
2945&lt;= ny+1 are output so that in case of cyclic boundary conditions
2946the
2947complete total domain is represented. The location(s) of the cross
2948sections can be defined with parameters <a href="#section_xy">section_xy</a>,
2949      <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>
2950causes&nbsp;the output data to be averaged along the direction
2951normal to the respective section.<br>
2952
2953
2954
2955
2956      <br>
2957
2958
2959
2960
2961      <br>
2962
2963
2964
2965
2966      <span style="font-weight: bold;">Output of user defined quantities:</span><br>
2967
2968
2969
2970
2971      <br>
2972
2973
2974
2975
2976Beside
2977the standard quantities from the above list, the user can output any
2978other quantities. These have to be defined and calculated within the
2979user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>).
2980They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>
2981for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
2982Output of the user defined quantities (time interval, averaging,
2983selection of cross sections, etc.) is controlled with the parameters
2984listed above and data are written to the same file(s) as the standard
2985quantities.<br>
2986
2987
2988
2989
2990      <br>
2991
2992
2993
2994
2995     
2996     
2997     
2998     
2999      <p style="font-weight: bold;">Output
3000on parallel machines:</p>
3001
3002
3003
3004
3005     
3006     
3007     
3008     
3009      <p>
3010By default, with parallel runs, processors output only data
3011of their respective subdomains into seperate local files (file names
3012are
3013constructed by appending the four digit processor ID, e.g.
3014&lt;filename&gt;_0000, &lt;filename&gt;_0001, etc.).
3015After PALM has
3016finished, the contents of these individual
3017files are sampled into one final file<span style="font-weight: bold;"></span>
3018using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
3019(to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
3020configuration file).</p>
3021
3022
3023
3024
3025 
3026     
3027     
3028     
3029     
3030      <p>Alternatively, PALM is able to
3031collect all grid points of a
3032cross section on PE0 before output is done. In this case only
3033one&nbsp;
3034output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
3035does not have to be called. In case of very large numbers of horizontal
3036gridpoints, sufficient
3037memory is required on PE0.&nbsp; This method can be used by
3038assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
3039= <i>.F.</i>.</p>
3040
3041
3042
3043
3044     
3045     
3046     
3047     
3048      <p>3d volume data output is
3049always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span>
3050has to be called anyway after PALM has been finished.</p>
3051
3052
3053
3054
3055     
3056     
3057     
3058     
3059      <p><br>
3060
3061
3062
3063
3064      <span style="font-weight: bold;">Old formats:</span></p>
3065
3066
3067
3068
3069
3070     
3071     
3072     
3073     
3074      <p>Beside
3075the NetCDF format,&nbsp;2d cross section data and 3d volume data
3076can
3077also be output, for historical reasons, in a different (binary) format
3078using parameter <a href="#data_output_format">data_output_format</a>.</p>
3079
3080
3081
3082
3083     
3084     
3085     
3086     
3087      <p>By
3088assigning <span style="font-weight: bold;">data_output_format
3089      </span>= <span style="font-style: italic;">'avs'</span>,
3090the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
3091Output is in FORTRAN binary format&nbsp;readable by
3092the plot software <span style="font-weight: bold;">AVS</span>.&nbsp;
3093The order of data on the file follows the order used in the assignment
3094for <b>data_output</b> (e.g. <b>data_output</b>
3095= <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,...&nbsp;
3096means that the file starts with the pressure data, followed by the
3097v-component of the velocity, etc.). Both instantaneous and time
3098averaged data are written on this file! Additional to this file, PALM
3099creates
3100a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>)
3101with coordinate information needed by <span style="font-weight: bold;">AVS</span>.
3102As third and
3103fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
3104and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>),
3105which describe the contents of the data file and/or coordinate file
3106and are used by AVS. However, AVS expects the content description in
3107one file. This needs the local file PLOT3D_FLD_COOR to be appended to
3108the file
3109PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
3110configuration file: &#8220;<span style="font-family: monospace;">cat
3111PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>&#8221;)
3112after PALM has
3113finished.&nbsp;To reduce the amount of data, output to this file
3114can be done
3115in
3116compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>).
3117Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in
3118      <a href="chapter_4.5.5.html">chapter
31194.5.5</a>.</p>
3120
3121
3122
3123
3124By assigning <span style="font-weight: bold;">data_output_format </span>=
3125      <span style="font-style: italic;">'iso2d'</span>,
3126the 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>.
3127Output is in FORTRAN binary format&nbsp;readable by
3128the plot software&nbsp;<span style="font-weight: bold;">iso2d</span>.&nbsp;
3129The order of data on the files follows the order used in the assignment
3130for <b>data_output</b> (e.g. <b>data_output</b>
3131= <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,...&nbsp;
3132means that the file containing the horizontal cross section data starts
3133with the instantaneous pressure data, followed by the
3134temporally averaged v-component of the velocity, etc.). Both
3135instantaneous and time averaged data are written on this
3136file!Additional to these binary files, PALM
3137creates NAMELIST parameter files
3138(local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>,
3139      <a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
3140      <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
3141      <a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
3142      <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
3143      <a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
3144which 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>.
3145That needs local files with suffix _LOCAL to be appended to the
3146respective files with suffix _GLOBAL (by
3147suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span>
3148configuration file, e.g.: &#8220;<span style="font-family: monospace;">cat
3149PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL</span>&#8221;)
3150after PALM has
3151finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the
3152respective data and
3153parameter file. The plot layout is steered via the parameter input
3154file.
3155The values of these <span style="font-weight: bold;">iso2d</span>
3156parameters are determined by a set of mostly internal PALM parameters
3157(exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>).
3158All parameter values can be changed by editing the parameter input
3159file.&nbsp;Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found
3160in <a href="chapter_4.5.4.html">chapter
31614.5.4</a>.<br>
3162
3163
3164
3165
3166      <br>
3167
3168
3169
3170
3171      <span style="font-weight: bold;">Important:</span><br>
3172
3173
3174
3175
3176There
3177is no guarantee that iso2d- and avs-output will be available in future
3178PALM versions (later than 3.0). </td>
3179
3180
3181
3182
3183 </tr>
3184
3185
3186
3187
3188 <tr>
3189
3190
3191
3192
3193 <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
3194
3195
3196
3197
3198
3199      </td>
3200
3201
3202
3203
3204 <td style="vertical-align: top;">C * 10 (10) </td>
3205
3206
3207
3208
3209
3210      <td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
3211
3212
3213
3214
3215
3216      <td style="vertical-align: top;">Format of output data.<br>
3217
3218
3219
3220
3221      <br>
3222
3223
3224
3225
3226By
3227default, all data (profiles, time
3228series, spectra, particle data, cross sections, volume data) are output
3229in NetCDF 64bit-offset format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).
3230Exception: 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>,
3231      <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
3232are always output in FORTRAN binary format.<br>
3233
3234
3235
3236
3237      <br>
3238
3239
3240
3241
3242The
3243numerical precision of the NetCDF output is determined with parameter <a href="chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br>
3244
3245
3246
3247
3248      <br>Other NetCDF formats (classic, NetCDF4/HDF5) can be selected with parameter <a href="#netcdf_data_format">netcdf_data_format</a>.<br>
3249
3250
3251
3252
3253      <br>
3254
3255
3256
3257
3258For historical
3259reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span>
3260may be assigned the following values:<br>
3261
3262
3263
3264
3265      <br>
3266
3267
3268
3269
3270     
3271     
3272     
3273     
3274      <table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2">
3275
3276
3277
3278
3279        <tbody>
3280
3281
3282
3283
3284          <tr>
3285
3286
3287
3288
3289            <td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td>
3290
3291
3292
3293
3294            <td>output
3295of profiles,&nbsp;time series and spectra in ASCII format to be
3296read by the graphic software <span style="font-weight: bold;">profil
3297            </span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
3298            <a href="#chapter_4.5.3.html">4.5.3</a>)</td>
3299
3300
3301
3302
3303          </tr>
3304
3305
3306
3307
3308          <tr>
3309
3310
3311
3312
3313            <td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td>
3314
3315
3316
3317
3318            <td>output
3319of 2d cross-sections in FORTRAN binary format to be read by the graphic
3320software <span style="font-weight: bold;">iso2d</span>
3321(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td>
3322
3323
3324
3325
3326          </tr>
3327
3328
3329
3330
3331          <tr>
3332
3333
3334
3335
3336            <td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td>
3337
3338
3339
3340
3341            <td>output
3342of 3d volume data in FORTRAN binary format to be read by the graphic
3343software <span style="font-weight: bold;">AVS</span>
3344(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td>
3345
3346
3347
3348
3349          </tr>
3350
3351
3352
3353
3354       
3355       
3356       
3357       
3358        </tbody>
3359     
3360     
3361     
3362     
3363      </table>
3364
3365
3366
3367
3368      <br>
3369
3370
3371
3372
3373Multiple
3374values can be assigned to <span style="font-weight: bold;">data_output_format</span>,
3375i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as
3376cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> =
3377      <span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
3378assigned.<br>
3379
3380
3381
3382
3383      <br>
3384
3385
3386
3387
3388      <span style="font-weight: bold;">Warning:</span>
3389There is no guarantee that the "old" formats will be available in
3390future PALM versions (beyond 3.0)!<br>
3391
3392
3393
3394
3395 </td>
3396
3397
3398
3399
3400 </tr>
3401
3402
3403
3404
3405 <tr>
3406
3407
3408
3409
3410
3411      <td style="vertical-align: top;"> 
3412     
3413     
3414     
3415     
3416      <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
3417
3418
3419
3420
3421
3422      </td>
3423
3424
3425
3426
3427 <td style="vertical-align: top;">C *
342810&nbsp; <br>
3429
3430
3431
3432
3433
3434(100)</td>
3435
3436
3437
3438
3439 <td style="vertical-align: top;"><i>100
3440* ' '</i></td>
3441
3442
3443
3444
3445 <td style="vertical-align: top;">
3446     
3447     
3448     
3449     
3450      <p>Quantities for which vertical profiles (horizontally averaged)
3451are to be output.&nbsp; </p>
3452
3453
3454
3455
3456 
3457     
3458     
3459     
3460     
3461      <p>By default vertical
3462profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>.
3463The file's format is NetCDF.&nbsp; Further details about processing
3464NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
3465
3466
3467
3468
3469     
3470     
3471     
3472     
3473      <p>For
3474historical reasons, data can also be output in ASCII-format on local
3475file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
3476which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See
3477parameter <a href="#data_output_format">data_output_format</a>
3478for defining the format in which data shall be output.<br>
3479
3480
3481
3482
3483 </p>
3484
3485
3486
3487
3488
3489     
3490     
3491     
3492     
3493      <p>For horizontally averaged vertical
3494profiles always <span style="font-weight: bold;">all</span>
3495vertical
3496grid points (0 &lt;= k &lt;= nz+1) are output to file. Vertical
3497profile data refers to the total domain but profiles for subdomains can
3498also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).&nbsp;
3499      </p>
3500
3501
3502
3503
3504 
3505     
3506     
3507     
3508     
3509      <p>The temporal interval of the output times of
3510profiles is
3511assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>.
3512Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
3513the profiles are ordered with respect to their
3514output times.</p>
3515
3516
3517
3518
3519     
3520     
3521     
3522     
3523      <p>Profiles can also be temporally
3524averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>).<br>
3525
3526
3527
3528
3529
3530      </p>
3531
3532
3533
3534
3535 
3536     
3537     
3538     
3539     
3540      <p>The following list shows the values which can be
3541assigned to <span style="font-weight: bold;">data_output_pr</span>.
3542The profile data is either defined on
3543u-v-levels (variables marked in <font color="#ff6600">red</font>)
3544or
3545on w-levels (<font color="#33ff33">green</font>).
3546According to this,
3547the
3548z-coordinates of the individual profiles vary. Beyond that, with a
3549Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>)
3550the lowest output
3551level is z = zu(1) instead of z = zw(0) for profiles <i>w''
3552u'',w''v"</i>, <i>wu</i> and <i>wv</i>
3553. Turbulence quantities such as&nbsp;<span style="font-style: italic;">w*u* &nbsp;</span>or <span style="font-style: italic;">u*2</span> are calculated from turbulent fluctuations that are defined as deviations from the instantaneous horizontal average.
3554
3555
3556 </p>
3557
3558
3559
3560
3561 
3562     
3563     
3564     
3565     
3566      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
3567
3568
3569
3570
3571 <tbody>
3572
3573
3574
3575
3576 <tr>
3577
3578
3579
3580
3581 <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
3582
3583
3584
3585
3586
3587            <td style="vertical-align: top;">u-component of the
3588velocity (in m/s).</td>
3589
3590
3591
3592
3593 </tr>
3594
3595
3596
3597
3598 <tr>
3599
3600
3601
3602
3603 <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
3604
3605
3606
3607
3608
3609            <td style="vertical-align: top;">v-component of the
3610velocity (in m/s).</td>
3611
3612
3613
3614
3615 </tr>
3616
3617
3618
3619
3620 <tr>
3621
3622
3623
3624
3625 <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
3626
3627
3628
3629
3630
3631            <td style="vertical-align: top;">w-component of the
3632velocity (in m/s).</td>
3633
3634
3635
3636
3637 </tr>
3638
3639
3640
3641
3642 <tr>
3643
3644
3645
3646
3647 <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
3648
3649
3650
3651
3652
3653            <td style="vertical-align: top;">Potential temperature (in
3654K).</td>
3655
3656
3657
3658
3659 </tr>
3660
3661
3662
3663
3664 <tr>
3665
3666
3667
3668
3669 <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
3670
3671
3672
3673
3674
3675            <td style="vertical-align: top;">Virtual potential
3676temperature (in K).</td>
3677
3678
3679
3680
3681 </tr>
3682
3683
3684
3685
3686 <tr>
3687
3688
3689
3690
3691 <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
3692
3693
3694
3695
3696
3697            <td style="vertical-align: top;">Potential liquid water
3698temperature (in K).</td>
3699
3700
3701
3702
3703 </tr>
3704
3705
3706
3707
3708 <tr>
3709
3710
3711
3712
3713 <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
3714
3715
3716
3717
3718
3719            <td style="vertical-align: top;">Total water content
3720(in kg/kg).</td>
3721
3722
3723
3724
3725 </tr>
3726
3727
3728
3729
3730 <tr>
3731
3732
3733
3734
3735 <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
3736
3737
3738
3739
3740
3741            <td style="vertical-align: top;">Specific humidity (in
3742kg/kg).</td>
3743
3744
3745
3746
3747 </tr>
3748
3749
3750
3751
3752 <tr>
3753
3754
3755
3756
3757 <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
3758
3759
3760
3761
3762
3763            <td style="vertical-align: top;">Liquid water content
3764(in kg/kg).</td>
3765
3766
3767
3768
3769 </tr>
3770
3771
3772
3773
3774 <tr>
3775
3776
3777
3778
3779            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 102, 0);">rho</span></td>
3780
3781
3782
3783
3784            <td align="undefined" valign="undefined">Potential density (in kg/m<sup>3</sup>).</td>
3785
3786
3787
3788
3789          </tr>
3790
3791
3792
3793
3794          <tr>
3795
3796
3797
3798
3799 <td style="vertical-align: middle; font-style: italic;"><font color="#ff6600">s</font></td>
3800
3801
3802
3803
3804
3805            <td style="vertical-align: top;">Scalar concentration (in
3806kg/m<sup>3</sup>).</td>
3807
3808
3809
3810
3811 </tr>
3812
3813
3814
3815
3816 <tr>
3817
3818
3819
3820
3821            <td align="undefined" valign="undefined"><span style="font-style: italic; background-color: rgb(255, 255, 255); color: rgb(255, 102, 0);">sa</span></td>
3822
3823
3824
3825
3826            <td align="undefined" valign="undefined">Salinity (in psu).</td>
3827
3828
3829
3830
3831          </tr>
3832
3833
3834
3835
3836          <tr>
3837
3838
3839
3840
3841 <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
3842
3843
3844
3845
3846
3847            <td style="vertical-align: top;">Turbulent kinetic energy
3848(TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td>
3849
3850
3851
3852
3853
3854          </tr>
3855
3856
3857
3858
3859 <tr>
3860
3861
3862
3863
3864 <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
3865
3866
3867
3868
3869
3870            <td style="vertical-align: top;">Perturbation energy
3871(resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td>
3872
3873
3874
3875
3876
3877          </tr>
3878
3879
3880
3881
3882 <tr>
3883
3884            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 0, 0);">p</span></td>
3885
3886            <td align="undefined" valign="undefined">Perturbation pressure (in Pa)</td>
3887
3888          </tr>
3889
3890          <tr>
3891
3892
3893
3894
3895 <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
3896
3897
3898
3899
3900
3901            <td style="vertical-align: top;">Eddy diffusivity for
3902momentum (in m<sup>2</sup>/s).</td>
3903
3904
3905
3906
3907 </tr>
3908
3909
3910
3911
3912 <tr>
3913
3914
3915
3916
3917
3918            <td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
3919
3920
3921
3922
3923
3924            <td style="vertical-align: top;">Eddy diffusivity for heat
3925(in m<sup>2</sup>/s).</td>
3926
3927
3928
3929
3930 </tr>
3931
3932
3933
3934
3935 <tr>
3936
3937
3938
3939
3940 <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
3941
3942
3943
3944
3945
3946            <td style="vertical-align: top;">Mixing length (in m).</td>
3947
3948
3949
3950
3951
3952          </tr>
3953
3954
3955
3956
3957 <tr>
3958
3959
3960
3961
3962 <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
3963
3964
3965
3966
3967
3968            <td style="vertical-align: top;">u-component of the
3969subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
3970
3971
3972
3973
3974
3975          </tr>
3976
3977
3978
3979
3980 <tr>
3981
3982
3983
3984
3985 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*u*</i></font></td>
3986
3987
3988
3989
3990
3991            <td style="vertical-align: top;">u-component of the
3992resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
3993
3994
3995
3996
3997
3998          </tr>
3999
4000
4001
4002
4003 <tr>
4004
4005
4006
4007
4008 <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
4009
4010
4011
4012
4013
4014            <td style="vertical-align: top;">u-component of the total
4015vertical momentum flux (<i>w"u"</i> + <i>w*u*</i>)
4016(in m<sup>2</sup>/s<sup>2</sup>).</td>
4017
4018
4019
4020
4021 </tr>
4022
4023
4024
4025
4026
4027          <tr>
4028
4029
4030
4031
4032 <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
4033
4034
4035
4036
4037
4038            <td style="vertical-align: top;">v-component of the
4039subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
4040
4041
4042
4043
4044
4045          </tr>
4046
4047
4048
4049
4050 <tr>
4051
4052
4053
4054
4055 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*v*</i></font></td>
4056
4057
4058
4059
4060
4061            <td style="vertical-align: top;">v-component of the
4062resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
4063
4064
4065
4066
4067
4068          </tr>
4069
4070
4071
4072
4073 <tr>
4074
4075
4076
4077
4078 <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
4079
4080
4081
4082
4083
4084            <td style="vertical-align: top;">v-component of the total
4085vertical momentum flux (<i>w"v"</i> + <i>w*v*</i>)
4086(in m<sup>2</sup>/s<sup>2</sup>).</td>
4087
4088
4089
4090
4091 </tr>
4092
4093
4094
4095
4096
4097          <tr>
4098
4099
4100
4101
4102 <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
4103
4104
4105
4106
4107
4108            <td style="vertical-align: top;">Subgrid-scale vertical
4109sensible heat flux (in K m/s).</td>
4110
4111
4112
4113
4114 </tr>
4115
4116
4117
4118
4119 <tr>
4120
4121
4122
4123
4124 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*</i></font></td>
4125
4126
4127
4128
4129
4130            <td style="vertical-align: top;">Resolved vertical
4131sensible
4132heat flux (in K m/s).</td>
4133
4134
4135
4136
4137 </tr>
4138
4139
4140
4141
4142 <tr>
4143
4144
4145
4146
4147 <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
4148
4149
4150
4151
4152
4153            <td style="vertical-align: top;">Total vertical sensible
4154heat flux (<i>w"pt"</i> + <i>w*pt*</i>)
4155(in K
4156m/s).</td>
4157
4158
4159
4160
4161 </tr>
4162
4163
4164
4165
4166 <tr>
4167
4168
4169
4170
4171 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*BC</i></font></td>
4172
4173
4174
4175
4176
4177            <td style="vertical-align: top;">Subgrid-scale vertical
4178sensible heat flux using the
4179Bott-Chlond scheme (in K m/s).</td>
4180
4181
4182
4183
4184 </tr>
4185
4186
4187
4188
4189 <tr>
4190
4191
4192
4193
4194 <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
4195
4196
4197
4198
4199
4200            <td style="vertical-align: top;">Total vertical sensible
4201heat flux using the Bott-Chlond scheme
4202(<i>w"pt"</i>
4203+ <i>w*pt*BC</i>) (in K m/s).</td>
4204
4205
4206
4207
4208 </tr>
4209
4210
4211
4212
4213 <tr>
4214
4215
4216
4217
4218
4219            <td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
4220
4221
4222
4223
4224
4225            <td style="vertical-align: top;">Subgrid-scale vertical
4226buoyancy flux (in K m/s).</td>
4227
4228
4229
4230
4231 </tr>
4232
4233
4234
4235
4236 <tr>
4237
4238
4239
4240
4241 <td style="vertical-align: top;"><font color="#33ff33"><i>w*vpt*</i></font></td>
4242
4243
4244
4245
4246
4247            <td style="vertical-align: top;">Resolved vertical
4248buoyancy
4249flux (in K m/s).</td>
4250
4251
4252
4253
4254 </tr>
4255
4256
4257
4258
4259 <tr>
4260
4261
4262
4263
4264 <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
4265
4266
4267
4268
4269
4270            <td style="vertical-align: top;">Total vertical buoyancy
4271flux (w"vpt" + w*vpt*) (in K m/s).</td>
4272
4273
4274
4275
4276 </tr>
4277
4278
4279
4280
4281 <tr>
4282
4283
4284
4285
4286 <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
4287
4288
4289
4290
4291
4292            <td style="vertical-align: top;">Subgrid-scale vertical
4293water flux (in kg/kg m/s).</td>
4294
4295
4296
4297
4298 </tr>
4299
4300
4301
4302
4303 <tr>
4304
4305
4306
4307
4308 <td style="vertical-align: top;"><font color="#33ff33"><i>w*q*</i></font></td>
4309
4310
4311
4312
4313
4314            <td style="vertical-align: top;">Resolved vertical water
4315flux (in kg/kg m/s).</td>
4316
4317
4318
4319
4320 </tr>
4321
4322
4323
4324
4325 <tr>
4326
4327
4328
4329
4330 <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
4331
4332
4333
4334
4335
4336            <td style="vertical-align: top;">Total vertical water flux
4337(w"q" + w*q*) (in kg/kg m/s).</td>
4338
4339
4340
4341
4342 </tr>
4343
4344
4345
4346
4347 <tr>
4348
4349
4350
4351
4352 <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
4353
4354
4355
4356
4357
4358            <td style="vertical-align: top;">Subgrid-scale vertical
4359latent heat flux (in kg/kg m/s).</td>
4360
4361
4362
4363
4364 </tr>
4365
4366
4367
4368
4369 <tr>
4370
4371
4372
4373
4374 <td style="vertical-align: top;"><font color="#33ff33"><i>w*qv*</i></font></td>
4375
4376
4377
4378
4379
4380            <td style="vertical-align: top;">Resolved vertical latent
4381heat flux (in kg/kg m/s).</td>
4382
4383
4384
4385
4386 </tr>
4387
4388
4389
4390
4391 <tr>
4392
4393
4394
4395
4396 <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
4397
4398
4399
4400
4401
4402            <td style="vertical-align: top;">Total vertical latent
4403heat
4404flux (w"qv" + w*qv*) (in kg/kg m/s).</td>
4405
4406
4407
4408
4409 </tr>
4410
4411
4412
4413
4414 <tr>
4415
4416
4417
4418
4419
4420            <td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
4421
4422
4423
4424
4425
4426            <td style="vertical-align: top;">Subgrid-scale vertical
4427scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td>
4428
4429
4430
4431
4432
4433          </tr>
4434
4435
4436
4437
4438 <tr>
4439
4440
4441
4442
4443 <td style="vertical-align: middle;"><font color="#33ff33"><i>w*s*</i></font></td>
4444
4445
4446
4447
4448
4449            <td style="vertical-align: top;">Resolved vertical scalar
4450concentration flux (in kg/m<sup>3</sup> m/s).</td>
4451
4452
4453
4454
4455 </tr>
4456
4457
4458
4459
4460
4461          <tr>
4462
4463
4464
4465
4466 <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
4467
4468
4469
4470
4471
4472            <td style="vertical-align: top;">Total vertical scalar
4473concentration flux (w"s" + w*s*) (in kg/m<sup>3 </sup>m/s).</td>
4474
4475
4476
4477
4478
4479          </tr>
4480
4481
4482
4483
4484 <tr>
4485
4486
4487
4488
4489            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w"sa"</span></td>
4490
4491
4492
4493
4494            <td align="undefined" valign="undefined">Subgrid-scale vertical
4495salinity flux (in psu<sup> </sup>m/s).</td>
4496
4497
4498
4499
4500          </tr>
4501
4502
4503
4504
4505          <tr>
4506
4507
4508
4509
4510            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w*sa*</span></td>
4511
4512
4513
4514
4515            <td align="undefined" valign="undefined">Resolved vertical salinity flux (in psu m/s).</td>
4516
4517
4518
4519
4520          </tr>
4521
4522
4523
4524
4525          <tr>
4526
4527
4528
4529
4530            <td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td>
4531
4532
4533
4534
4535            <td align="undefined" valign="undefined">Total vertical salinity flux (w"sa" + w*sa*) (in psu<sup> </sup>m/s).</td>
4536
4537
4538
4539
4540          </tr>
4541
4542
4543
4544
4545          <tr>
4546
4547
4548
4549
4550 <td style="vertical-align: top;"><font color="#33ff33"><i>w*e*</i></font></td>
4551
4552
4553
4554
4555
4556            <td style="vertical-align: top;">Vertical flux of
4557perturbation energy (resolved)</td>
4558
4559
4560
4561
4562 </tr>
4563
4564
4565
4566
4567 <tr>
4568
4569
4570
4571
4572 <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
4573
4574
4575
4576
4577
4578            <td style="vertical-align: top;">Variance of the
4579u-velocity
4580component (resolved)</td>
4581
4582
4583
4584
4585 </tr>
4586
4587
4588
4589
4590 <tr>
4591
4592
4593
4594
4595 <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
4596
4597
4598
4599
4600
4601            <td style="vertical-align: top;">Variance of the
4602v-velocity
4603component (resolved)</td>
4604
4605
4606
4607
4608 </tr>
4609
4610
4611
4612
4613 <tr>
4614
4615
4616
4617
4618 <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
4619
4620
4621
4622
4623
4624            <td style="vertical-align: top;">Variance of the w-velocity
4625component (resolved)</td>
4626
4627
4628
4629
4630 </tr>
4631
4632
4633
4634
4635 <tr>
4636
4637
4638
4639
4640 <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
4641
4642
4643
4644
4645
4646            <td style="vertical-align: top;">Variance of the potential
4647temperature (resolved)</td>
4648
4649
4650
4651
4652 </tr>
4653
4654
4655
4656
4657 <tr>
4658
4659
4660
4661
4662 <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
4663
4664
4665
4666
4667
4668            <td style="vertical-align: top;">Third moment of the
4669w-velocity component (resolved)</td>
4670
4671
4672
4673
4674 </tr>
4675
4676
4677
4678
4679 <tr>
4680
4681
4682
4683
4684 <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
4685
4686
4687
4688
4689
4690            <td style="vertical-align: top;">Skewness of the
4691w-velocity
4692component (resolved, S<sub>w</sub>
4693= W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td>
4694
4695
4696
4697
4698
4699          </tr>
4700
4701
4702
4703
4704 <tr>
4705
4706
4707
4708
4709 <td style="vertical-align: top;"><font color="#33ff33"><i>w*2pt*</i></font></td>
4710
4711
4712
4713
4714
4715            <td style="vertical-align: top;">Third moment (resolved)</td>
4716
4717
4718
4719
4720
4721          </tr>
4722
4723
4724
4725
4726 <tr>
4727
4728
4729
4730
4731 <td style="vertical-align: top;"><font color="#33ff33"><i>w*pt*2</i></font></td>
4732
4733
4734
4735
4736
4737            <td style="vertical-align: top;">Third moment (resolved)</td>
4738
4739
4740
4741
4742
4743          </tr>
4744
4745
4746
4747
4748 <tr>
4749
4750
4751
4752
4753 <td style="vertical-align: top;"><font color="#ff6666"><i>w*u*u*:dz</i></font></td>
4754
4755
4756
4757
4758
4759            <td style="vertical-align: top;">Energy production by
4760shear
4761(resolved)</td>
4762
4763
4764
4765
4766 </tr>
4767
4768
4769
4770
4771 <tr>
4772
4773
4774
4775
4776 <td style="vertical-align: top;"><font color="#ff6666"><i>w*p*:dz</i></font></td>
4777
4778
4779
4780
4781
4782            <td style="vertical-align: top;">Energy production by
4783turbulent transport of pressure
4784fluctuations (resolved)</td>
4785
4786
4787
4788
4789 </tr>
4790
4791
4792
4793
4794 <tr>
4795
4796
4797
4798
4799 <td style="vertical-align: top;"><font color="#ff6666"><i>w"e:dz</i></font></td>
4800
4801
4802
4803
4804
4805            <td style="vertical-align: top;">Energy production by
4806transport of resolved-scale TKE</td>
4807
4808
4809
4810
4811 </tr><tr>
4812            <td style="vertical-align: top;"><font color="#ff6666"><i>hyp</i></font></td>
4813            <td style="vertical-align: top;">Hydrostatic pressure (in dbar)<br>
4814            </td>
4815          </tr>
4816
4817
4818
4819
4820
4821 
4822       
4823       
4824       
4825       
4826        </tbody>
4827     
4828     
4829     
4830     
4831      </table>
4832
4833
4834
4835
4836 <br>
4837
4838
4839
4840
4841Beyond that, initial profiles (t=0) of some
4842variables can additionally be
4843output (this output is only done once
4844with the first plot output and not repeated with the profile output at
4845later
4846times). The names of these profiles result from the ones specified
4847above leaded by a hash "#".&nbsp; Allowed values are:<br>
4848
4849
4850
4851
4852 
4853     
4854     
4855     
4856     
4857      <ul>
4858
4859
4860
4861
4862
4863       
4864       
4865       
4866       
4867        <p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
4868        <i>#km</i>, <i>#kh</i>, <i>#l, #lpt, #q, #qv, #s, #sa, #vpt</i></p>
4869
4870
4871
4872
4873
4874     
4875     
4876     
4877     
4878      </ul>
4879
4880
4881
4882
4883 
4884     
4885     
4886     
4887     
4888      <p>Profile names preceded by a hash automatically imply that
4889profiles for these variables are also output at later times. It is not
4890necessary and not allowed to specify the same profile name with and
4891without hash simultaneously(this would lead to an NetCDF error). </p>
4892
4893
4894     
4895     
4896      <p>These initial profiles have been either set by
4897the user or
4898have been calculated by a 1d-model prerun.</p>
4899
4900
4901
4902
4903The
4904user is allowed to extend the above list of quantities by defining his
4905own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>).<br>
4906
4907
4908
4909
4910      <br>
4911
4912
4913
4914
4915In case
4916of ASCII data output to local file PLOT1D_DATA,
4917PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
4918which 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>.
4919Profiles can be directly plotted with <span style="font-weight: bold;">profil</span>
4920using these two files. The
4921plot layout is
4922steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters
4923are determined by
4924a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>,
4925      <a href="chapter_4.2.html#profile_rows">profile_rows</a>,
4926      <a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
4927      <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
4928etc.) All parameter values can be changed by editing the parameter
4929input
4930file. <br>
4931
4932
4933
4934
4935      <br>
4936
4937
4938
4939
4940Further details about plotting vertical
4941profiles with <span style="font-weight: bold;">profil </span>can
4942be found in <a href="chapter_4.5.2.html">chapter
49434.5.2</a></td>
4944
4945
4946
4947
4948 </tr>
4949
4950
4951
4952
4953 <tr>
4954
4955
4956
4957
4958 <td style="vertical-align: top;"> 
4959     
4960     
4961     
4962     
4963      <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
4964      <br>
4965
4966
4967
4968
4969 <b>_each_pe</b></p>
4970
4971
4972
4973
4974 </td>
4975
4976
4977
4978
4979 <td style="vertical-align: top;">L<br>
4980
4981
4982
4983
4984 </td>
4985
4986
4987
4988
4989 <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br>
4990
4991
4992
4993
4994 </td>
4995
4996
4997
4998
4999
5000      <td style="vertical-align: top;">Output 2d cross section
5001data by one or
5002all processors.&nbsp; 
5003     
5004     
5005     
5006     
5007      <p>In runs with several processors, by
5008default, each processor
5009outputs cross section data of its subdomain&nbsp;into an individual
5010file. After PALM
5011has finished, the contents of these files have to be sampled into one
5012file<span style="font-weight: bold;"></span> using
5013the program <tt>combine_plot_fields.x</tt>.&nbsp; </p>
5014
5015
5016
5017
5018
5019     
5020     
5021     
5022     
5023      <p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
5024= <i>.F.,</i>
5025the respective data is gathered on PE0 and output is done directly
5026into one file, so <tt>combine_plot_fields.x</tt> does not
5027have to be
5028called. However, in case of very large numbers of horizontal
5029gridpoints, sufficient
5030memory is required on PE0. </p>
5031
5032
5033
5034
5035 </td>
5036
5037
5038
5039
5040 </tr>
5041
5042
5043
5044
5045
5046    <tr>
5047
5048
5049
5050
5051 <td style="vertical-align: top;"> 
5052     
5053     
5054     
5055     
5056      <p><a name="disturbance_amplitude"></a><b>disturbance<br>
5057
5058
5059
5060
5061
5062_amplitude</b></p>
5063
5064
5065
5066
5067 </td>
5068
5069
5070
5071
5072 <td style="vertical-align: top;">R</td>
5073
5074
5075
5076
5077 <td style="vertical-align: top;"><i>0.25</i></td>
5078
5079
5080
5081
5082
5083      <td style="vertical-align: top;"> 
5084     
5085     
5086     
5087     
5088      <p>Maximum
5089perturbation amplitude of the random perturbations
5090imposed to the horizontal velocity field (in m/s).&nbsp; </p>
5091
5092
5093
5094
5095
5096     
5097     
5098     
5099     
5100      <p>The parameter <a href="#create_disturbances">create_disturbances</a>
5101describes how to impose random perturbations to the horizontal velocity
5102field. Since the perturbation procedure includes two filter operations,
5103the amplitude assigned by <b>disturbance_amplitude</b> is
5104only an
5105approximate value of the real magnitude of the perturbation.</p>
5106
5107
5108
5109
5110 </td>
5111
5112
5113
5114
5115
5116    </tr>
5117
5118
5119
5120
5121 <tr>
5122
5123
5124
5125
5126 <td style="vertical-align: top;">
5127     
5128     
5129     
5130     
5131      <p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
5132      <br>
5133
5134
5135
5136
5137 <b>_limit</b></p>
5138
5139
5140
5141
5142 </td>
5143
5144
5145
5146
5147 <td style="vertical-align: top;">R</td>
5148
5149
5150
5151
5152 <td style="vertical-align: top;"><i>0.01</i></td>
5153
5154
5155
5156
5157
5158      <td style="vertical-align: top; font-family: Helvetica,Arial,sans-serif;"> 
5159     
5160     
5161     
5162     
5163      <p lang="en-GB">Upper
5164limit value of the perturbation energy of
5165the velocity field used as a criterion for imposing random
5166perturbations (in m<sup>2</sup>/s<sup>2</sup>).&nbsp;
5167      </p>
5168
5169
5170
5171
5172 
5173     
5174     
5175     
5176     
5177      <p><span lang="en-GB">The parameter </span><a href="#create_disturbances"><span lang="en-GB">create_disturbances</span></a><span lang="en-GB">
5178describes how to impose
5179random perturbations to the horizontal velocity field. The perturbation
5180energy is defined as the volume average (over the total model domain)
5181of the squares of the deviations of the velocity components from the
5182mean flow (horizontal average). If the perturbation energy exceeds the
5183assigned value, random perturbations to the fields of horizontal
5184velocities are imposed no more. The value of this parameter usually
5185must be determined by trial and error (it depends e.g. on the total
5186number of grid points).</span>  </p>
5187
5188
5189
5190
5191 </td>
5192
5193
5194
5195
5196
5197    </tr>
5198
5199
5200
5201
5202 <tr>
5203
5204
5205
5206
5207 <td style="vertical-align: top;">
5208     
5209     
5210     
5211     
5212      <p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
5213
5214
5215
5216
5217
5218      </td>
5219
5220
5221
5222
5223 <td style="vertical-align: top;">R</td>
5224
5225
5226
5227
5228
5229      <td style="vertical-align: top;"><i>zu(3) or<br>
5230
5231
5232
5233
5234zu(nz*2/3)<br>
5235
5236
5237
5238
5239see right</i></td>
5240
5241
5242
5243
5244
5245      <td style="vertical-align: top; font-family: Helvetica,Arial,sans-serif;"> 
5246     
5247     
5248     
5249     
5250      <p lang="en-GB"><font size="3">Lower
5251limit of the vertical range for which random perturbations are to be
5252imposed on the horizontal wind field (</font>in <font size="3">m).&nbsp;
5253      </font> </p>
5254
5255
5256
5257
5258 
5259     
5260     
5261     
5262     
5263      <p><span lang="en-GB">This
5264parameter must hold the condition zu(3) &lt;= <b>disturbance_level_b</b>
5265&lt;= zu(</span><a href="chapter_4.1.html#nz"><span lang="en-GB">nz-2</span></a><span lang="en-GB">)</span><span lang="en-GB">. Additionally, <b>disturbance_level_b</b>
5266&lt;= </span><a href="#disturbance_level_t"><span lang="en-GB">disturbance_level_t</span></a>
5267      <span lang="en-GB">must
5268also hold.</span></p>
5269
5270
5271
5272
5273     
5274     
5275     
5276     
5277      <p><span lang="en-GB">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </span><span lang="en-GB">the default value is <span style="font-weight: bold;">disturbance_level_b</span> = <span style="font-style: italic;">zu(nz * 2 / 3) </span>(negative).</span><a href="chapter_4.1.html#nz"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"></span></p>
5278
5279
5280
5281
5282 
5283     
5284     
5285     
5286     
5287      <p><span lang="en-GB">The
5288parameter </span><a href="#create_disturbances"><span lang="en-GB">create_disturbances</span></a><span lang="en-GB">
5289describes how to impose
5290random perturbations to the horizontal velocity field</span><span lang="en-GB">.</span>
5291       </p>
5292
5293
5294
5295
5296 </td>
5297
5298
5299
5300
5301 </tr>
5302
5303
5304
5305
5306 <tr>
5307
5308
5309
5310
5311 <td style="vertical-align: top;"> 
5312     
5313     
5314     
5315     
5316      <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
5317
5318
5319
5320
5321
5322      </td>
5323
5324
5325
5326
5327 <td style="vertical-align: top;">R</td>
5328
5329
5330
5331
5332
5333      <td style="vertical-align: top;"><i>zu(nz/3) or<br>
5334
5335
5336
5337
5338zu(nzt-3)<br>
5339
5340
5341
5342
5343see right</i></td>
5344
5345
5346
5347
5348
5349      <td style="vertical-align: top; font-family: Helvetica,Arial,sans-serif;"> 
5350     
5351     
5352     
5353     
5354      <p lang="en-GB"><font size="3">Upper
5355limit of the vertical range for which random perturbations are to be
5356imposed on the horizontal wind field (</font>in <font size="3">m).&nbsp;
5357      </font> </p>
5358
5359
5360
5361
5362 
5363     
5364     
5365     
5366     
5367      <p><span lang="en-GB">This
5368parameter must hold the condition <b>disturbance_level_t</b>
5369&lt;= zu<i>(</i></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB">nz-2</span></a><span lang="en-GB">)</span></i><span lang="en-GB">.
5370Additionally, </span><a href="#disturbance_level_b"><span lang="en-GB">disturbance_level_b</span></a>
5371      <span lang="en-GB">&lt;=
5372      <b>disturbance_level_t</b>
5373must also hold.</span></p>
5374
5375
5376
5377
5378      <span lang="en-GB">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </span><span lang="en-GB">the default value is <span style="font-weight: bold;">disturbance_level_t</span> = <span style="font-style: italic;">zu(nzt - 3</span>)</span><span lang="en-GB"><span style="font-style: italic;"> </span>(negative)</span><span lang="en-GB">.</span>
5379     
5380     
5381     
5382     
5383      <p><span lang="en-GB">The
5384parameter </span><a href="#create_disturbances"><span lang="en-GB">create_disturbances</span></a><span lang="en-GB">
5385describes how to impose
5386random perturbations to the horizontal velocity field</span><span lang="en-GB">.</span>
5387       </p>
5388
5389
5390
5391
5392 </td>
5393
5394
5395
5396
5397 </tr>
5398
5399
5400
5401
5402 <tr>
5403
5404
5405
5406
5407 <td style="vertical-align: top;"> 
5408     
5409     
5410     
5411     
5412      <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
5413
5414
5415
5416
5417
5418      </td>
5419
5420
5421
5422
5423 <td style="vertical-align: top;">L<br>
5424
5425
5426
5427
5428 </td>
5429
5430
5431
5432
5433
5434      <td style="vertical-align: top; font-style: italic;">.F.<br>
5435
5436
5437
5438
5439 </td>
5440
5441
5442
5443
5444
5445      <td style="vertical-align: top;"> 
5446     
5447     
5448     
5449     
5450      <p>Output of 2d
5451cross section data at the beginning of a run.&nbsp; </p>
5452
5453
5454
5455
5456 
5457     
5458     
5459     
5460     
5461      <p>The
5462temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>)
5463are 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>
5464and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>.
5465By assigning <b>do2d_at_begin</b> = <i>.T.</i>
5466an additional output
5467will be made at the
5468beginning of a run (thus at the time t = 0 or at the respective
5469starting times of restart runs).</p>
5470
5471
5472
5473
5474 </td>
5475
5476
5477
5478
5479 </tr>
5480
5481
5482
5483
5484 <tr>
5485
5486
5487
5488
5489
5490      <td style="vertical-align: top;"> 
5491     
5492     
5493     
5494     
5495      <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
5496
5497
5498
5499
5500
5501      </td>
5502
5503
5504
5505
5506 <td style="vertical-align: top;">L<br>
5507
5508
5509
5510
5511 </td>
5512
5513
5514
5515
5516
5517      <td style="vertical-align: top; font-style: italic;">.F.<br>
5518
5519
5520
5521
5522 </td>
5523
5524
5525
5526
5527
5528      <td style="vertical-align: top;">Output of 3d volume data
5529at the beginning
5530of a run.<br>
5531
5532
5533
5534
5535      <br>
5536
5537
5538
5539
5540The temporal intervals of output times of
55413d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
5542is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>.
5543By assigning <b>do3d_at_begin</b> = <i>.T.</i>
5544an additional output
5545will be made at the
5546beginning of a run (thus at the time t = 0 or at the respective
5547starting times of restart runs).</td>
5548
5549
5550
5551
5552 </tr>
5553
5554
5555
5556
5557 <tr>
5558
5559
5560
5561
5562 <td style="vertical-align: top;"> 
5563     
5564     
5565     
5566     
5567      <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
5568
5569
5570
5571
5572
5573      </td>
5574
5575
5576
5577
5578 <td style="vertical-align: top;">L<br>
5579
5580
5581
5582
5583 </td>
5584
5585
5586
5587
5588
5589      <td style="vertical-align: top; font-style: italic;">.F.<br>
5590
5591
5592
5593
5594 </td>
5595
5596
5597
5598
5599
5600      <td style="vertical-align: top;"> 
5601     
5602     
5603     
5604     
5605      <p>Output of data
5606for 3d plots in compressed form.&nbsp; </p>
5607
5608
5609
5610
5611 
5612     
5613     
5614     
5615     
5616      <p>This
5617parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
5618= <span style="font-style: italic;">'avs'</span>.</p>
5619
5620
5621
5622
5623     
5624     
5625     
5626     
5627      <p>Output
5628of 3d volume data may need huge amounts of disc storage
5629(up to several Terabytes ore more). Data compression can serve to
5630reduce this requirement. PALM is able to output 3d data in compressed
5631form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span>
5632= <span style="font-style: italic;">.T.</span> is
5633assigned. This
5634yields a loss of accuracy, but the file size is clearly reduced. The
5635parameter <a href="chapter_4.2.html#do3d_comp_prec">do3d_comp_prec</a>
5636can be used to separately define the number of significant digits for
5637each quantity.<br>
5638
5639
5640
5641
5642 </p>
5643
5644
5645
5646
5647 
5648     
5649     
5650     
5651     
5652      <p>So far compressed data
5653output is only possible for Cray-T3E
5654machines. Additional information for
5655handling compressed data is given in <a href="chapter_4.5.6.html">chapter
56564.5.6</a>.</p>
5657
5658
5659
5660
5661 </td>
5662
5663
5664
5665
5666 </tr>
5667
5668
5669
5670
5671 <tr>
5672
5673
5674
5675
5676 <td style="vertical-align: top;"> 
5677     
5678     
5679     
5680     
5681      <p><a name="do3d_comp_prec"></a><b>do3d_comp_prec</b></p>
5682
5683
5684
5685
5686
5687      </td>
5688
5689
5690
5691
5692 <td style="vertical-align: top;">C *
56937&nbsp; <br>
5694
5695
5696
5697
5698
5699&nbsp; (100)</td>
5700
5701
5702
5703
5704 <td style="vertical-align: top; font-style: italic;">see
5705right<br>
5706
5707
5708
5709
5710 </td>
5711
5712
5713
5714
5715 <td style="vertical-align: top;">
5716     
5717     
5718     
5719     
5720      <p>Significant digits in case of compressed data
5721output.&nbsp; </p>
5722
5723
5724
5725
5726 
5727     
5728     
5729     
5730     
5731      <p>This parameter only applies for
5732&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
5733= <span style="font-style: italic;">'avs'</span>.</p>
5734
5735
5736
5737
5738     
5739     
5740     
5741     
5742      <p>In
5743case that data compression is used for output of 3d data
5744(see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>),
5745this parameter determines the number of significant digits
5746which are to be output.<br>
5747
5748
5749
5750
5751 </p>
5752
5753
5754
5755
5756 
5757     
5758     
5759     
5760     
5761      <p>Fewer digits
5762clearly reduce the amount
5763of data. Assignments have to be given separately for each individual
5764quantity via a character string of the form <span style="font-style: italic;">'&lt;quantity
5765name&gt;&lt;number of
5766significant digits&gt;'</span>, e.g. <span style="font-style: italic;">'pt2'</span>.
5767Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a>
5768are admitted. Up to 9 significant digits are allowed (but large values
5769are not very reasonable
5770because they do not effect a significant compression).<br>
5771
5772
5773
5774
5775 </p>
5776
5777
5778
5779
5780
5781     
5782     
5783     
5784     
5785      <p>The default assignment is <span style="font-weight: bold;">do3d_comp_prec</span>
5786= <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>
5787
5788
5789
5790
5791 </td>
5792
5793
5794
5795
5796
5797    </tr>
5798
5799
5800
5801
5802 <tr>
5803
5804
5805
5806
5807 <td style="vertical-align: top;"> 
5808     
5809     
5810     
5811     
5812      <p><a name="dt_laufparameter"></a><b>dt</b></p>
5813
5814
5815
5816
5817
5818      </td>
5819
5820
5821
5822
5823 <td style="vertical-align: top;">R</td>
5824
5825
5826
5827
5828
5829      <td style="vertical-align: top;"><i>variable</i></td>
5830
5831
5832
5833
5834
5835      <td style="vertical-align: top;"> 
5836     
5837     
5838      <font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><font size="3">Time
5839step to be used by the 3d-model (</font></font><span style="font-family: Helvetica,Arial,sans-serif;">in </span><font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><font size="3">s).&nbsp;
5840      </font></font> 
5841
5842
5843 
5844     
5845     
5846     
5847     
5848      <p style="font-family: Helvetica,Arial,sans-serif;"><span lang="en-GB">This parameter</span>
5849      <span lang="en-GB">is
5850described in
5851detail with the initialization parameters (see</span><span lang="en-GB"> </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a><span lang="en-GB">).
5852Additionally, it may be
5853used as a run parameter and then applies to all restart runs (until it
5854is changed again). A switch from a constant time step to a variable
5855time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span></p>
5856
5857      <font face="Thorndale, serif">
5858      </font> 
5859
5860
5861 </td>
5862
5863
5864
5865
5866 </tr>
5867
5868
5869
5870
5871 <tr>
5872
5873
5874
5875
5876 <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
5877
5878
5879
5880
5881
5882      </td>
5883
5884
5885
5886
5887 <td style="vertical-align: top;">R<br>
5888
5889
5890
5891
5892 </td>
5893
5894
5895
5896
5897
5898      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
5899
5900
5901
5902
5903 </td>
5904
5905
5906
5907
5908
5909      <td style="vertical-align: top;">Temporal interval
5910of&nbsp;data which are subject to temporal averaging (in s).<br>
5911
5912
5913
5914
5915      <br>
5916
5917
5918
5919
5920By
5921default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>
5922are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span>
5923&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>,
5924the number of time levels entering the average can be minimized. This
5925reduces the CPU-time of a run but may worsen the quality of the
5926average's statistics.<br>
5927
5928
5929
5930
5931      <br style="font-family: Helvetica,Arial,sans-serif;">
5932
5933
5934
5935
5936      <font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><span lang="en-GB">With
5937variable time step (see <span style="font-weight: bold;">dt</span>),
5938the number of time levels entering the average can vary from one
5939averaging interval to the next (for a more detailed explanation see </span></font><font style="font-family: Helvetica,Arial,sans-serif;"><a href="#averaging_interval"><span lang="en-GB">averaging_interval</span></a>)</font><font style="font-family: Helvetica,Arial,sans-serif;" face="Thorndale, serif"><span lang="en-GB">. It
5940is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> /
5941MAX(<span style="font-weight: bold;"> dt_averaging_input</span>,
5942      <span style="font-weight: bold;">dt</span>) (which
5943gives a more or less exact value if a fixed timestep is used and if
5944this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font><span style="font-family: Helvetica,Arial,sans-serif;">&nbsp;
5945      </span><br style="font-family: Helvetica,Arial,sans-serif;">
5946
5947
5948
5949
5950      <br>
5951
5952
5953
5954
5955      <span style="font-weight: bold;">Example:</span><br>
5956
5957
5958
5959
5960With
5961an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> =
5962      <span style="font-style: italic;">10.0</span>,
5963the time levels entering the average have a (minimum) distance of 10.0
5964s (their distance may of course be larger if the current timestep is
5965larger than 10.0 s), so the average is calculated from the data of
5966(maximum) 10 time levels.<br>
5967
5968
5969
5970
5971      <br>
5972
5973
5974
5975
5976      <font face="Thorndale, serif"><span lang="en-GB">It
5977is allowed
5978to change <b>dt_averaging_input</b> during a job chain. If
5979the last averaging
5980interval of the run previous to the change could not be completed (i.e.
5981has to be finished in the current run), the individual profiles and/or
5982spectra entering the averaging are not uniformly distributed over the
5983averaging interval.<br>
5984
5985
5986
5987
5988      <br>
5989
5990
5991
5992
5993      </span></font>Parameter&nbsp;<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>&nbsp;can
5994be used to define&nbsp;a different temporal interval&nbsp;for
5995vertical profile data and spectra.<br>
5996
5997
5998
5999
6000 </td>
6001
6002
6003
6004
6005 </tr>
6006
6007
6008
6009
6010
6011    <tr>
6012
6013
6014
6015
6016 <td style="vertical-align: top;"> 
6017     
6018     
6019     
6020     
6021      <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
6022
6023
6024
6025
6026
6027      </td>
6028
6029
6030
6031
6032 <td style="vertical-align: top;">R</td>
6033
6034
6035
6036
6037
6038      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>
6039
6040
6041
6042
6043averaging_<br>
6044
6045
6046
6047
6048input</a></span></td>
6049
6050
6051
6052
6053
6054      <td style="vertical-align: top;"> 
6055     
6056     
6057     
6058     
6059      <p lang="en-GB">Temporal
6060interval of&nbsp;data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
6061profiles and/or spectra&nbsp;(</font></font>in <font face="Thorndale, serif"><font size="3">s).&nbsp;
6062      </font></font> </p>
6063
6064
6065
6066
6067 
6068     
6069     
6070     
6071     
6072      <p>By default, data from
6073each 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
6074used for calculating the temporal average.&nbsp;By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span>
6075&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>,
6076the number of time levels entering the average can be minimized. This
6077reduces the CPU-time of a run but may worsen the quality of the
6078average'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>
6079
6080
6081
6082
6083 </p>
6084
6085
6086
6087
6088     
6089     
6090     
6091     
6092      <p>For
6093more 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>
6094
6095
6096
6097
6098      </td>
6099
6100
6101
6102
6103
6104    </tr>
6105
6106
6107
6108
6109 <tr>
6110
6111
6112
6113
6114      <td style="vertical-align: top;"><a name="dt_coupling"></a><span style="font-weight: bold;">dt_coupling</span></td>
6115
6116
6117
6118
6119      <td style="vertical-align: top;">R</td>
6120
6121
6122
6123
6124      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td>
6125
6126
6127
6128
6129      <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>
6130
6131
6132
6133
6134      <br>
6135
6136
6137
6138
6139This parameter has an effect only in case of a run with coupled models. It is available starting from version 3.3a. <br>
6140
6141
6142
6143
6144      <br>
6145
6146
6147
6148
6149This parameter specifies the temporal interval at which data are
6150exchanged at the interface between coupled models (currently: interface
6151between atmosphere and ocean). If this parameter is not explicitly
6152specified in the parameter files for both coupled models, or if there
6153is an inconsistency between its values for both coupled models,
6154the&nbsp;execution will terminate and an informative error message will
6155be given.&nbsp;In order to ensure synchronous coupling throughout the simulation, <span style="font-weight: bold;">dt_coupling</span> should be chosen larger than
6156      <a href="#dt_max">dt_max</a>.</td>
6157
6158
6159
6160
6161    </tr>
6162
6163
6164
6165
6166    <tr>
6167
6168
6169
6170
6171 <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
6172
6173
6174
6175
6176
6177      </td>
6178
6179
6180
6181
6182 <td style="vertical-align: top;">R<br>
6183
6184
6185
6186
6187 </td>
6188
6189
6190
6191
6192
6193      <td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
6194
6195
6196
6197
6198
6199      </td>
6200
6201
6202
6203
6204 <td style="vertical-align: top;">
6205     
6206     
6207     
6208     
6209      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
6210at which&nbsp;data (3d volume data (instantaneous or time
6211averaged),
6212cross sections (instantaneous or time averaged), vertical profiles,
6213spectra) shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
6214
6215
6216
6217
6218
6219      <span lang="en-GB"><font face="Thorndale">If
6220data 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
6221parameter can be used to
6222assign the temporal interval at which these data shall be
6223output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
6224simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>,
6225which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
6226time is the beginning of the simulation, i.e. output
6227takes place at times t = <b>skip_time_data_output +
6228dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
6229+ 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
6230+ 3*<b>dt_data_output</b>,
6231etc. Since output is only done at the discrete time levels given by
6232the&nbsp;timestep used, the actual output times can slightly
6233deviate
6234from 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>
6235
6236
6237
6238
6239      <br>
6240
6241
6242
6243
6244Individual temporal
6245intervals for the different output quantities can be assigned using
6246parameters <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>,
6247and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span>
6248      </td>
6249
6250
6251
6252
6253 </tr>
6254
6255
6256
6257
6258 <tr>
6259
6260
6261
6262
6263 <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
6264
6265
6266
6267
6268
6269      </td>
6270
6271
6272
6273
6274 <td style="vertical-align: top;">R<br>
6275
6276
6277
6278
6279 </td>
6280
6281
6282
6283
6284
6285      <td style="vertical-align: top;"><i>value of
6286&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
6287
6288
6289
6290
6291output</a></i>
6292      </td>
6293
6294
6295
6296
6297 <td style="vertical-align: top;">
6298     
6299     
6300     
6301     
6302      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
6303at which time averaged 3d volume data and/or 2d cross section data
6304shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
6305
6306
6307
6308
6309      <span lang="en-GB"><font face="Thorndale">If data
6310output 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
6311parameter can be used to
6312assign the temporal interval at which they shall be
6313output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
6314simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>,
6315which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
6316time is the beginning of the simulation, i.e. output
6317takes place at times t = <b>skip_time_data_output_av +
6318dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
6319+ 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
6320+ 3*<b>dt_data_output_av</b>,
6321etc. Since output is only done at the discrete time levels given by
6322the&nbsp;timestep used, the actual output times can slightly
6323deviate from
6324these 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>
6325
6326
6327
6328
6329      <br>
6330
6331
6332
6333
6334      </font></span>The
6335length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td>
6336
6337
6338
6339
6340
6341    </tr>
6342
6343
6344
6345
6346    <tr>
6347
6348
6349
6350
6351 <td style="vertical-align: top;"> 
6352     
6353     
6354     
6355     
6356      <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
6357
6358
6359
6360
6361
6362      </td>
6363
6364
6365
6366
6367 <td style="vertical-align: top;">R</td>
6368
6369
6370
6371
6372
6373      <td style="vertical-align: top;"><i>9999999.9</i></td>
6374
6375
6376
6377
6378
6379      <td style="vertical-align: top;"> 
6380     
6381     
6382     
6383     
6384      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
6385interval</font> at which random
6386perturbations are to be imposed on the horizontal velocity field
6387(</font>in <font face="Thorndale">s).&nbsp; </font>
6388      </p>
6389
6390
6391
6392
6393 
6394     
6395     
6396     
6397     
6398      <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">
6399describes how to impose
6400random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
6401      </font> </p>
6402
6403
6404
6405
6406 </td>
6407
6408
6409
6410
6411 </tr>
6412
6413
6414
6415
6416 <tr>
6417
6418
6419
6420
6421 <td style="vertical-align: top;"> 
6422     
6423     
6424     
6425     
6426      <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
6427
6428
6429
6430
6431
6432      </td>
6433
6434
6435
6436
6437 <td style="vertical-align: top;">R</td>
6438
6439
6440
6441
6442
6443      <td style="vertical-align: top;"><i>value of
6444&nbsp;<a href="#dt_data_output">dt_data_<br>
6445
6446
6447
6448
6449output</a></i></td>
6450
6451
6452
6453
6454
6455      <td style="vertical-align: top;"> 
6456     
6457     
6458     
6459     
6460      <p><span lang="en-GB"><font face="Thorndale">Temporal
6461interval at
6462which data&nbsp;of vertical profiles shall be output (to local
6463file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
6464or/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
6465      <span lang="en-GB"><font face="Thorndale">s).&nbsp;
6466      </font></span> </p>
6467
6468
6469
6470
6471 
6472     
6473     
6474     
6475     
6476      <p><span lang="en-GB"><font face="Thorndale">If output of
6477horizontally 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
6478parameter can be used to
6479assign 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
6480be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has
6481zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
6482time is the beginning
6483of the simulation, thus t = 0,&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">i.e. output
6484takes 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>,
6485      <span style="font-weight: bold;">skip_time_dopr</span>
6486+ 3*<b>dt_dopr</b>,
6487etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
6488profiles can not be calculated for times lying within a time step
6489interval, the output times can deviate from these theoretical values.
6490If a time step ranges from t = 1799.8 to t = 1800.2, then in the
6491example above the output would take place at t = 1800.2. In general,
6492the 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
6493model uses a variable time step, these
6494deviations from the theoretical output times will of course be
6495different for each output time.<br>
6496
6497
6498
6499
6500 </font></span></p>
6501
6502
6503
6504
6505
6506     
6507     
6508     
6509     
6510      <p><span lang="en-GB"><font face="Thorndale">In
6511order to
6512guarantee 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;
6513      <span style="font-weight: bold;">end_time</span>
6514should be equal or a little bit
6515larger than the respective theoretical output time. For example, if <b>dt_dopr</b>
6516= <i>900.0</i><span style="font-style: italic;">
6517      </span>and 3600.0
6518seconds are to be simulated, then <b>end_time</b>
6519&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>
6520      </p>
6521
6522
6523
6524
6525 
6526     
6527     
6528     
6529     
6530      <p><span lang="en-GB"><font face="Thorndale">A selection of
6531profiles 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>
6532      </p>
6533
6534
6535
6536
6537 </td>
6538
6539
6540
6541
6542 </tr>
6543
6544
6545
6546
6547 <tr>
6548
6549
6550
6551
6552 <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
6553
6554
6555
6556
6557
6558      </td>
6559
6560
6561
6562
6563 <td style="vertical-align: top;">R<br>
6564
6565
6566
6567
6568 </td>
6569
6570
6571
6572
6573
6574      <td style="vertical-align: top;"><i>9999999.9</i></td>
6575
6576
6577
6578
6579
6580      <td style="vertical-align: top;"> 
6581     
6582     
6583     
6584     
6585      <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
6586interval</font> at which data <font face="Thorndale">of
6587vertical
6588profiles 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
6589      <span lang="en-GB"><font face="Thorndale">s).&nbsp;</font></span>
6590      </p>
6591
6592
6593
6594
6595 
6596     
6597     
6598     
6599     
6600      <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
6601parameter can be used to
6602assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
6603time is the beginning
6604of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b>
6605= 1800.0,
6606then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since
6607profiles can not be calculated for times lying within a time step
6608interval, the output times can deviate from these theoretical values.
6609If a time step ranges from t = 1799.8 to t = 1800.2, then in the
6610example above the output would take place at t = 1800.2. In general,
6611the 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
6612are related to
6613the
6614example above). If the model uses a variable time step, these
6615deviations from the theoretical output times will of course be
6616different for each output time.<br>
6617
6618
6619
6620
6621 </font></span></p>
6622
6623
6624
6625
6626
6627     
6628     
6629     
6630     
6631      <p><span lang="en-GB"><font face="Thorndale">In
6632order to
6633guarantee 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;
6634      <span style="font-weight: bold;">end_time</span>
6635should be a little bit
6636larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b>
6637= <i>900.0</i><span style="font-style: italic;">
6638      </span>and 3600.0
6639seconds are to be simulated, then it should be at least&nbsp; <b>end_time</b>
6640&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
6641variable time steps are used
6642(which is the default), <span style="font-weight: bold;">dt</span>
6643should be properly estimated.&nbsp; </font></span> </p>
6644
6645
6646
6647
6648
6649     
6650     
6651     
6652     
6653      <p><span lang="en-GB"><font face="Thorndale">Data
6654and output
6655format 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>
6656      <span lang="en-GB"><font face="Thorndale">is
6657internally fixed. In this file
6658the profiles of the most important model variables are arranged in
6659adjacent columns.</font></span> </p>
6660
6661
6662
6663
6664 </td>
6665
6666
6667
6668
6669 </tr>
6670
6671
6672
6673
6674
6675    <tr>
6676
6677
6678
6679
6680 <td style="vertical-align: top;"> 
6681     
6682     
6683     
6684     
6685      <p><a name="dt_dots"></a><b>dt_dots</b></p>
6686
6687
6688
6689
6690
6691      </td>
6692
6693
6694
6695
6696 <td style="vertical-align: top;">R</td>
6697
6698
6699
6700
6701
6702      <td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
6703
6704
6705
6706
6707
6708      <td style="vertical-align: top;"> 
6709     
6710     
6711     
6712     
6713      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
6714interval</font> at which&nbsp;time series data shall be
6715output (</font>in <font face="Thorndale">s).&nbsp;</font>
6716      </p>
6717
6718
6719
6720
6721 
6722     
6723     
6724     
6725     
6726      <p>The default interval for the output of timeseries
6727is calculated as shown below (this tries to minimize the number of
6728calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p>
6729
6730
6731
6732
6733     
6734     
6735     
6736     
6737      <p style="font-family: Courier New,Courier,monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6738IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
6739== 0.0 )&nbsp; THEN<br>
6740
6741
6742
6743
6744&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6745      <span style="font-weight: bold;">dt_dots</span> =
6746MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
6747
6748
6749
6750
6751&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6752ELSE<br>
6753
6754
6755
6756
6757&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6758      <span style="font-weight: bold;">dt_dots</span> =
6759MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
6760)<br>
6761
6762
6763
6764
6765&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6766ENDIF</p>
6767
6768
6769
6770
6771     
6772     
6773     
6774     
6775      <p>This parameter can be used to
6776assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
6777time is the beginning of
6778&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
67792*<b>dt_dots</b>, 3*<b>dt_dots</b>, etc. The
6780actual output times can
6781deviate 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;
6782Is <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
6783of the time series are
6784written after each time step (if this is requested it should be <b>dt_dots</b>
6785= <i>0</i>).</font></span></p>
6786
6787
6788
6789
6790     
6791     
6792     
6793     
6794      <p><span lang="en-GB"><font face="Thorndale">The default
6795value of <span style="font-weight: bold;">dt_dots</span>
6796is calculated as follows:</font></span></p>
6797
6798
6799
6800
6801&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6802IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
6803== 0.0 )&nbsp; THEN<br>
6804
6805
6806
6807
6808&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6809      <span style="font-weight: bold;">dt_dots</span> =
6810MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
6811
6812
6813
6814
6815&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6816ELSE<br>
6817
6818
6819
6820
6821&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6822      <span style="font-weight: bold;">dt_dots</span> =
6823MIN( <span style="font-weight: bold;">dt_run_control</span>,
6824      <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
6825)<br>
6826
6827
6828
6829
6830&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6831ENDIF<br>
6832
6833
6834
6835
6836      <br>
6837
6838
6839
6840
6841(which minimizes the number of calls of
6842routine flow_statistics).<br>
6843
6844
6845
6846
6847     
6848     
6849     
6850     
6851      <p>By default time series data
6852is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>.
6853Because of the default settings of <span style="font-weight: bold;">dt_dots</span>,
6854it will&nbsp;generally be created for each model run. The file's
6855format is NetCDF.&nbsp; Further details about processing NetCDF
6856data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
6857
6858
6859
6860
6861The
6862file contains the following timeseries quantities (the first column
6863gives the name of the quantities as used in the NetCDF file):<br>
6864
6865
6866
6867
6868     
6869     
6870     
6871     
6872      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
6873
6874
6875
6876
6877 <tbody>
6878
6879
6880
6881
6882 <tr>
6883
6884
6885
6886
6887 <td style="font-style: italic; vertical-align: middle;">E<br>
6888
6889
6890
6891
6892
6893            </td>
6894
6895
6896
6897
6898 <td style="vertical-align: top;">Total (resolved and subgrid-scale)
6899kinetic energy of
6900the flow (in m<sup>2</sup>/s<sup>2</sup>)
6901(normalized with respect to the total number of grid points).</td>
6902
6903
6904
6905
6906
6907          </tr>
6908
6909
6910
6911
6912 <tr>
6913
6914
6915
6916
6917 <td style="font-style: italic; vertical-align: middle;">E*<br>
6918
6919
6920
6921
6922
6923            </td>
6924
6925
6926
6927
6928 <td style="vertical-align: top;">Resolved-scale kinetic
6929energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
6930            </sup>(normalized
6931with respect to the total number of grid
6932points)</td>
6933
6934
6935
6936
6937 </tr>
6938
6939
6940
6941
6942 <tr>
6943
6944
6945
6946
6947 <td style="vertical-align: top; font-style: italic;">dt<br>
6948
6949
6950
6951
6952
6953            </td>
6954
6955
6956
6957
6958 <td style="vertical-align: top;">Time step
6959size (in s).</td>
6960
6961
6962
6963
6964 </tr>
6965
6966
6967
6968
6969 <tr>
6970
6971
6972
6973
6974 <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
6975
6976
6977
6978
6979
6980            <td style="vertical-align: top;">Friction velocity (in
6981m/s)
6982(horizontal average).</td>
6983
6984
6985
6986
6987 </tr>
6988
6989
6990
6991
6992 <tr>
6993
6994
6995
6996
6997 <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
6998
6999
7000
7001
7002
7003            <td style="vertical-align: top;">Vertical velocity scale
7004of
7005the CBL (in m/s) (horizontal average)</td>
7006
7007
7008
7009
7010 </tr>
7011
7012
7013
7014
7015 <tr>
7016
7017
7018
7019
7020
7021            <td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
7022
7023
7024
7025
7026
7027            <td style="vertical-align: top;">Temperature
7028scale (Prandtl layer), defined as <i>w"pt"0
7029/&nbsp;</i><i>u<sub>*</sub></i>
7030(horizontal
7031average) (in K).</td>
7032
7033
7034
7035
7036 </tr>
7037
7038
7039
7040
7041 <tr>
7042
7043
7044
7045
7046 <td style="vertical-align: top; font-style: italic;">umax<br>
7047
7048
7049
7050
7051
7052            </td>
7053
7054
7055
7056
7057 <td style="vertical-align: top;">Maximum
7058u-component of the
7059velocity (in m/s).</td>
7060
7061
7062
7063
7064 </tr>
7065
7066
7067
7068
7069 <tr>
7070
7071
7072
7073
7074 <td style="vertical-align: top; font-style: italic;">vmax<br>
7075
7076
7077
7078
7079
7080            </td>
7081
7082
7083
7084
7085 <td style="vertical-align: top;">Maximum
7086v-component of the
7087velocity (in m/s).</td>
7088
7089
7090
7091
7092 </tr>
7093
7094
7095
7096
7097 <tr>
7098
7099
7100
7101
7102 <td style="vertical-align: top; font-style: italic;">wmax<br>
7103
7104
7105
7106
7107
7108            </td>
7109
7110
7111
7112
7113 <td style="vertical-align: top;">Maximum
7114w-component of the
7115velocity (in m/s).</td>
7116
7117
7118
7119
7120 </tr>
7121
7122
7123
7124
7125 <tr>
7126
7127
7128
7129
7130 <td style="vertical-align: top; font-style: italic;">div_old<br>
7131
7132
7133
7134
7135
7136            </td>
7137
7138
7139
7140
7141 <td style="vertical-align: top;">Divergence
7142of the velocity
7143field before the pressure
7144solver has been called (normalized with respect to the total number of
7145grid points) (in 1/s).</td>
7146
7147
7148
7149
7150 </tr>
7151
7152
7153
7154
7155 <tr>
7156
7157
7158
7159
7160 <td style="vertical-align: top; font-style: italic;">div_new</td>
7161
7162
7163
7164
7165
7166            <td style="vertical-align: top;">Divergence of the
7167velocity
7168field after the pressure
7169solver has been called (normalized with respect to the total number of
7170grid points) (in 1/s).</td>
7171
7172
7173
7174
7175 </tr>
7176
7177
7178
7179
7180 <tr>
7181
7182
7183
7184
7185 <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
7186
7187
7188
7189
7190
7191            <td style="vertical-align: top;">Height of the convective
7192boundary layer (horizontal average)
7193determined by the height of the minimum sensible heat flux (in m).</td>
7194
7195
7196
7197
7198
7199          </tr>
7200
7201
7202
7203
7204 <tr>
7205
7206
7207
7208
7209 <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
7210
7211
7212
7213
7214
7215            <td style="vertical-align: top;">Height of the convective
7216boundary layer (horizontal average)
7217determined by the temperature profile, following the criterion of Sullivan et al. (1998) (in m).</td>
7218
7219
7220
7221
7222 </tr>
7223
7224
7225
7226
7227 <tr>
7228
7229
7230
7231
7232
7233            <td style="vertical-align: top; font-style: italic;">w"pt"0</td>
7234
7235
7236
7237
7238
7239            <td style="vertical-align: top;">Subgrid-scale sensible
7240heat flux at k=0 (horizontal
7241average), constant within Prandtl-layer (in K m/s).</td>
7242
7243
7244
7245
7246 </tr>
7247
7248
7249
7250
7251 <tr>
7252
7253
7254
7255
7256 <td style="vertical-align: top; font-style: italic;">w"pt"</td>
7257
7258
7259
7260
7261
7262            <td style="vertical-align: top;">Subgrid-scale heat flux
7263(horizontal average) for z = zw(1) (in K
7264m/s).</td>
7265
7266
7267
7268
7269 </tr>
7270
7271
7272
7273
7274 <tr>
7275
7276
7277
7278
7279 <td style="vertical-align: top; font-style: italic;">wpt</td>
7280
7281
7282
7283
7284
7285            <td style="vertical-align: top;">Total heat flux
7286(horizontal average) for z = zw(1) (in K m/s).</td>
7287
7288
7289
7290
7291 </tr>
7292
7293
7294
7295
7296 <tr>
7297
7298            <td align="undefined" valign="undefined"><span style="font-style: italic;">w"u"0</span></td>
7299
7300            <td align="undefined" valign="undefined">Subgrid-scale momentum flux (u-component) at k=0 (horizontal average), constant within Prandtl-layer (in m<sup>2</sup>/s<sup>2</sup>).</td>
7301
7302          </tr>
7303
7304          <tr>
7305
7306            <td align="undefined" valign="undefined"><span style="font-style: italic;">w"v"0</span></td>
7307
7308            <td align="undefined" valign="undefined">Subgrid-scale momentum flux (v-component) at k=0 (horizontal average), constant within Prandtl-layer (in m<sup>2</sup>/s<sup>2</sup>).</td>
7309
7310          </tr>
7311
7312          <tr>
7313
7314            <td align="undefined" valign="undefined"><span style="font-style: italic;">w"q"0</span></td>
7315
7316            <td align="undefined" valign="undefined">Subgrid-scale
7317humidity flux at k=0 (horizontal average), constant within
7318Prandtl-layer (in kg/kg m/s). Zero values are output if humidity is not
7319used.</td>
7320
7321          </tr>
7322
7323          <tr>
7324
7325
7326
7327
7328
7329            <td style="vertical-align: top; font-style: italic;">pt(0)</td>
7330
7331
7332
7333
7334
7335            <td style="vertical-align: top;">Potential temperature at
7336the surface (horizontal average) (in K).</td>
7337
7338
7339
7340
7341 </tr>
7342
7343
7344
7345
7346 <tr>
7347
7348
7349
7350
7351
7352            <td style="vertical-align: top; font-style: italic;">pt(zp)</td>
7353
7354
7355
7356
7357
7358            <td style="vertical-align: top;">Potential temperature for
7359z = zu(1) (horizontal average) (in K).</td>
7360
7361
7362
7363
7364 </tr>
7365
7366
7367
7368
7369 
7370
7371
7372 
7373
7374
7375 
7376
7377
7378 <tr>
7379
7380
7381
7382
7383 <td style="vertical-align: top; font-style: italic;">L</td>
7384
7385
7386
7387
7388
7389            <td style="vertical-align: top;">Monin-Obukhov length.</td>
7390
7391
7392
7393
7394
7395          </tr>
7396
7397
7398
7399
7400 
7401       
7402       
7403       
7404       
7405        </tbody> 
7406     
7407     
7408     
7409     
7410      </table>
7411
7412
7413
7414
7415      <br>
7416
7417
7418
7419
7420Additionally, the
7421user can add his own timeseries quantities to the file, by using the
7422user-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>.
7423These routines contain (as comment lines) a simple example how to do
7424this.<br>
7425
7426
7427
7428
7429      <br>
7430
7431
7432
7433
7434Time series data refers to the total
7435domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
7436However, the following time series always present the values of the
7437total model domain (even with output for subdomains): <i>umax</i>,
7438      <i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
7439      <i>div_new</i>.</td>
7440
7441
7442
7443
7444 </tr>
7445
7446
7447
7448
7449 <tr>
7450
7451
7452
7453
7454 <td style="vertical-align: top;"> 
7455     
7456     
7457     
7458     
7459      <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
7460
7461
7462
7463
7464
7465      </td>
7466
7467
7468
7469
7470 <td style="vertical-align: top;">R</td>
7471
7472
7473
7474
7475
7476      <td style="vertical-align: top;"><i>value of
7477&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
7478
7479
7480
7481
7482output</a></i></td>
7483
7484
7485
7486
7487
7488      <td style="vertical-align: top;"> 
7489     
7490     
7491     
7492     
7493      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
7494interval</font> at which&nbsp;horizontal cross section data
7495shall be output (</font>in <font face="Thorndale">s).&nbsp;
7496      </font> </p>
7497
7498
7499
7500
7501 
7502     
7503     
7504     
7505     
7506      <p><span lang="en-GB"><font face="Thorndale">If output of
7507horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
7508      <span lang="en-GB"><font face="Thorndale">and
7509      </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
7510parameter can be used to
7511assign the temporal interval at which cross section data shall be
7512output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
7513simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>,
7514which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
7515time is the beginning of the simulation, i.e. output
7516takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>,
7517      <span style="font-weight: bold;">skip_time_do2d_xy</span>
7518+ 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span>
7519+ 3*<b>dt_do2d_xy</b>,
7520etc. The actual output times can deviate from these theoretical values
7521(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>
7522
7523
7524
7525
7526
7527      </font></span></p>
7528
7529
7530
7531
7532 
7533     
7534     
7535     
7536     
7537      <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>
7538has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
7539the time t = 0 or at the
7540respective starting times of restart runs).</font></span> </p>
7541
7542
7543
7544
7545
7546      </td>
7547
7548
7549
7550
7551 </tr>
7552
7553
7554
7555
7556 <tr>
7557
7558
7559
7560
7561 <td style="vertical-align: top;"> 
7562     
7563     
7564     
7565     
7566      <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
7567
7568
7569
7570
7571
7572      </td>
7573
7574
7575
7576
7577 <td style="vertical-align: top;">R</td>
7578
7579
7580
7581
7582
7583      <td style="vertical-align: top;"><i>value of
7584&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
7585
7586
7587
7588
7589output</a></i></td>
7590
7591
7592
7593
7594
7595      <td style="vertical-align: top;"> 
7596     
7597     
7598     
7599     
7600      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
7601interval</font> at which&nbsp;vertical cross sections data
7602(xz) shall be output (</font>in <font face="Thorndale">s).&nbsp;
7603      </font> </p>
7604
7605
7606
7607
7608 
7609     
7610     
7611     
7612     
7613      <p><span lang="en-GB"><font face="Thorndale">If output of
7614horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
7615      <span lang="en-GB"><font face="Thorndale">and
7616      </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">),
7617this parameter can be used to assign the temporal interval at which
7618cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
7619be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which
7620has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
7621the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz
7622+ dt_do2d_xz</b>,
7623      <span style="font-weight: bold;">skip_time_do2d_xz</span>
7624+ 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span>
7625+ 3*<b>dt_do2d_xz</b>, etc. The actual output times
7626can 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>
7627
7628
7629
7630
7631
7632      </font></span></p>
7633
7634
7635
7636
7637 
7638     
7639     
7640     
7641     
7642      <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>
7643has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
7644the time t = 0 or at the
7645respective starting times of restart runs).</font></span> </p>
7646
7647
7648
7649
7650
7651      </td>
7652
7653
7654
7655
7656 </tr>
7657
7658
7659
7660
7661 <tr>
7662
7663
7664
7665
7666 <td style="vertical-align: top;"> 
7667     
7668     
7669     
7670     
7671      <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
7672
7673
7674
7675
7676
7677      </td>
7678
7679
7680
7681
7682 <td style="vertical-align: top;">R</td>
7683
7684
7685
7686
7687
7688      <td style="vertical-align: top;"><i>value of
7689&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
7690
7691
7692
7693
7694output</a></i></td>
7695
7696
7697
7698
7699
7700      <td style="vertical-align: top;"> 
7701     
7702     
7703     
7704     
7705      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
7706interval</font> at which&nbsp;vertical cross section data
7707(yz) shall be output (</font>in s<font face="Thorndale">).&nbsp;
7708      </font> </p>
7709
7710
7711
7712
7713 
7714     
7715     
7716     
7717     
7718      <p><span lang="en-GB"><font face="Thorndale">If output of
7719horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
7720      <span lang="en-GB"><font face="Thorndale">and
7721      </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">),
7722this parameter can be used to assign the temporal interval at which
7723cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
7724be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which
7725has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
7726time is the beginning of
7727the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz
7728+ dt_do2d_yz</b>,
7729      <span style="font-weight: bold;">skip_time_do2d_yz</span>
7730+ 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz
7731      </span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
7732times
7733can 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>
7734
7735
7736
7737
7738
7739      </font></span></p>
7740
7741
7742
7743
7744 
7745     
7746     
7747     
7748     
7749      <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>
7750has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
7751the time t = 0 or at the
7752respective starting times of restart runs).</font></span> </p>
7753
7754
7755
7756
7757
7758      </td>
7759
7760
7761
7762
7763 </tr>
7764
7765
7766
7767
7768 <tr>
7769
7770
7771
7772
7773 <td style="vertical-align: top;"> 
7774     
7775     
7776     
7777     
7778      <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
7779
7780
7781
7782
7783
7784      </td>
7785
7786
7787
7788
7789 <td style="vertical-align: top;">R</td>
7790
7791
7792
7793
7794
7795      <td style="vertical-align: top;"><i>value of
7796&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
7797
7798
7799
7800
7801output</a></i></td>
7802
7803
7804
7805
7806
7807      <td style="vertical-align: top;"> 
7808     
7809     
7810     
7811     
7812      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
7813interval</font> at which 3d volume data shall be output (</font>in
7814      <font face="Thorndale">s).&nbsp; </font> </p>
7815
7816
7817
7818
7819
7820     
7821     
7822     
7823     
7824      <p><span lang="en-GB"><font face="Thorndale">If
7825output of
78263d-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
7827to assign
7828th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
7829interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
7830be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has
7831zero 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
7832time is the
7833beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d
7834+ dt_do3d</b>,
7835      <span style="font-weight: bold;">skip_time_do3d</span>
7836+ 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span>
7837+ 3*<b>dt_do3d</b>, etc. The actual output times can
7838deviate 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>
7839
7840
7841
7842
7843
7844      </font></span></p>
7845
7846
7847
7848
7849 
7850     
7851     
7852     
7853     
7854      <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>
7855has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
7856the time t = 0 or at the
7857respective starting times of restart runs).</font></span> </p>
7858
7859
7860
7861
7862
7863      </td>
7864
7865
7866
7867
7868 </tr>
7869
7870
7871
7872
7873 <tr>
7874
7875
7876
7877
7878      <td style="vertical-align: top;"><a name="dt_max"></a><span style="font-weight: bold;">dt_max</span></td>
7879
7880
7881
7882
7883      <td style="vertical-align: top;">R</td>
7884
7885
7886
7887
7888      <td style="vertical-align: top;"><span style="font-style: italic;">20.0</span></td>
7889
7890
7891
7892
7893      <td>Maximum
7894allowed value of the timestep (in s).<br>
7895
7896
7897
7898
7899      <br>
7900
7901
7902
7903
7904By default,
7905the maximum timestep is restricted to be 20 s. This might be o.k. for
7906simulations of any kind of atmospheric turbulence but may have to be
7907changed for other situations.</td>
7908
7909
7910
7911
7912    </tr>
7913
7914
7915
7916
7917    <tr>
7918
7919
7920
7921
7922 <td style="vertical-align: top;"> 
7923     
7924     
7925     
7926     
7927      <p><a name="dt_restart"></a><b>dt_restart</b></p>
7928
7929
7930
7931
7932
7933      </td>
7934
7935
7936
7937
7938 <td style="vertical-align: top;">R</td>
7939
7940
7941
7942
7943
7944      <td style="vertical-align: top;"><i>9999999.9</i></td>
7945
7946
7947
7948
7949
7950      <td style="vertical-align: top;"> 
7951     
7952     
7953     
7954     
7955      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
7956interval</font> at which a new
7957restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p>
7958
7959
7960
7961
7962 
7963     
7964     
7965     
7966     
7967      <p><span lang="en-GB"><font face="Thorndale">For a
7968description
7969how 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>
7970does not show any effect, if <span style="font-weight: bold;">restart_time</span>
7971has not been set.</font></span></p>
7972
7973
7974
7975     
7976     
7977     
7978      <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>
7979and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
7980
7981
7982
7983
7984 </td>
7985
7986
7987
7988
7989 </tr>
7990
7991
7992
7993
7994
7995    <tr>
7996
7997
7998
7999
8000 <td style="vertical-align: top;"> 
8001     
8002     
8003     
8004     
8005      <p><a name="dt_run_control"></a><b>dt_run_control</b></p>
8006
8007
8008
8009
8010
8011      </td>
8012
8013
8014
8015
8016 <td style="vertical-align: top;">R</td>
8017
8018
8019
8020
8021
8022      <td style="vertical-align: top;"><i>60.0</i></td>
8023
8024
8025
8026
8027
8028      <td style="vertical-align: top;"> 
8029     
8030     
8031     
8032     
8033      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
8034interval</font> at which run control
8035output is to be made (</font>in <font face="Thorndale">s).&nbsp;
8036      </font> </p>
8037
8038
8039
8040
8041 
8042     
8043     
8044     
8045     
8046      <p><span lang="en-GB"><font face="Thorndale">Run control
8047information 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
8048output time, one line
8049with information about the size of the time step, maximum speeds, total
8050kinetic energy etc. is written to this file. Reference time is the
8051beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>,
80522*<b>dt_run_control</b>, 3*<b>dt_run_control</b>,
8053etc., and always at
8054the beginning of a model run (thus at the time t = 0 or at the
8055respective starting times of restart runs). The actual output times can
8056deviate 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>
8057
8058
8059
8060
8061
8062      </font></span></p>
8063
8064
8065
8066
8067 
8068     
8069     
8070     
8071     
8072      <p><span lang="en-GB"><font face="Thorndale">Run control
8073information is output after each time step can be achieved via <b>dt_run_control</b>
8074= <i>0.0</i>.</font></span> </p>
8075
8076
8077
8078
8079 </td>
8080
8081
8082
8083
8084
8085    </tr>
8086
8087
8088
8089
8090 <tr>
8091
8092
8093
8094
8095 <td style="vertical-align: top;">
8096     
8097     
8098     
8099     
8100      <p><a name="end_time"></a><b>end_time</b></p>
8101
8102
8103
8104
8105
8106      </td>
8107
8108
8109
8110
8111 <td style="vertical-align: top;">R</td>
8112
8113
8114
8115
8116
8117      <td style="vertical-align: top;"><i>0.0</i></td>
8118
8119
8120
8121
8122
8123      <td style="vertical-align: top;"> 
8124     
8125     
8126     
8127     
8128      <p lang="en-GB"><font face="Thorndale">Simulation time of the 3D
8129model (</font>in <font face="Thorndale">s).&nbsp;
8130      </font> </p>
8131
8132
8133
8134
8135 
8136     
8137     
8138     
8139     
8140      <p><span lang="en-GB"><font face="Thorndale">The simulation time
8141is starting from the beginning of the initialization run (t = 0), not
8142starting from the beginning of the respective restart run.</font></span></p>
8143
8144
8145
8146     
8147     
8148     
8149      <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>
8150and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
8151
8152
8153
8154
8155 </td>
8156
8157
8158
8159
8160 </tr>
8161
8162
8163
8164
8165 <tr>
8166
8167
8168
8169
8170 <td style="vertical-align: top;"> 
8171     
8172     
8173     
8174     
8175      <p><a name="force_print_header"></a><b>force_print_header</b></p>
8176
8177
8178
8179
8180
8181      </td>
8182
8183
8184
8185
8186 <td style="vertical-align: top;">L</td>
8187
8188
8189
8190
8191
8192      <td style="vertical-align: top;"><i>.F.</i></td>
8193
8194
8195
8196
8197
8198      <td style="vertical-align: top;"> 
8199     
8200     
8201     
8202     
8203      <p>Steering of
8204header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.&nbsp;
8205      </p>
8206
8207
8208
8209
8210 
8211     
8212     
8213     
8214     
8215      <p>By default, informations about the model
8216parameters in use are
8217output to the beginning of file RUN_CONTROL for initial runs only
8218(these informations are identical to that which are output to the local
8219file <a href="chapter_3.4.html#HEADER">HEADER</a>).
8220With <b>force_print_header</b> = <i>.T.</i>,
8221these informations are
8222also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
8223at restart runs.</p>
8224
8225
8226
8227
8228 </td>
8229
8230
8231
8232
8233 </tr>
8234
8235
8236
8237
8238 <tr>
8239
8240
8241
8242
8243 <td style="vertical-align: top;"> 
8244     
8245     
8246     
8247     
8248      <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
8249
8250
8251
8252
8253
8254      </td>
8255
8256
8257
8258
8259 <td style="vertical-align: top;">I</td>
8260
8261
8262
8263
8264
8265      <td style="vertical-align: top;"><i>-1</i></td>
8266
8267
8268
8269
8270
8271      <td style="vertical-align: top;"> 
8272     
8273     
8274     
8275     
8276      <p>Number of
8277cycles to be used with the multi-grid scheme.<br>
8278
8279
8280
8281
8282 <br>
8283
8284
8285
8286
8287
8288This parameter determines the number of cycles to be carried out in the
8289multi-grid method used for solving the Poisson equation for
8290perturbation pressure (see <a href="#psolver">psolver</a>).
8291The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br>
8292
8293
8294
8295
8296
8297      </p>
8298
8299
8300
8301
8302 <br>
8303
8304
8305
8306
8307By default (<b>mg_cyles</b> = <i>-
83081</i>), the
8309number of cycles
8310depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>)
8311and may vary from time step to time step. In this case, the CPU time
8312for a run will be difficult to estimate, since it heavily depends on
8313the total number of the cycles to be carried out.<br>
8314
8315
8316
8317
8318 <br>
8319
8320
8321
8322
8323
8324By assigning <b>mg_cycles</b> a value (&gt;=<span style="font-style: italic;">1</span>), the number of
8325cycles can be
8326fixed so that the CPU time can be clearly estimated. <br>
8327
8328
8329
8330
8331 <br>
8332
8333
8334
8335
8336
8337      <b>Note:</b> When using a fixed number of cycles, the user
8338must
8339examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
8340regularly to check whether the divergence of the velocity field is
8341sufficiently reduced by the pressure solver. It should be reduced at
8342least by two orders of magnitude. For cyclic boundary conditions along
8343both horizontal directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
8344and <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
8345good choice, for
8346non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span>
8347= <span style="font-style: italic;">4</span> may be
8348sufficient.</td>
8349
8350
8351
8352
8353 </tr>
8354
8355
8356
8357
8358 <tr>
8359
8360
8361
8362
8363 <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
8364
8365
8366
8367
8368
8369level</b></td>
8370
8371
8372
8373
8374 <td style="vertical-align: top;">I</td>
8375
8376
8377
8378
8379
8380      <td style="vertical-align: top;"><br>
8381
8382
8383
8384
8385 </td>
8386
8387
8388
8389
8390 <td style="vertical-align: top;">Grid
8391level at which data shall be gathered on PE0.<br>
8392
8393
8394
8395
8396 <br>
8397
8398
8399
8400
8401
8402In case of a run using several PEs and the multigrid method for solving
8403the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
8404the value of this parameter defines on which grid level the data are
8405gathered on PE0 in order to allow for a further coarsening of the grid.
8406The finest grid defines the largest grid level. By default, the
8407gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
8408It is only possible to gather data from a level larger than the one
8409determined automatically. A test run may be neccessary to determine
8410this level.<br>
8411
8412      <br>
8413
8414Setting of <span style="font-weight: bold;">mg_switch_to_pe0_level</span> = <span style="font-style: italic;">-1</span> prevents that data are collected on PE0 at all, i.e. coarsening of grids is limited by the subdomains.</td>
8415
8416
8417
8418
8419 </tr>
8420
8421
8422
8423
8424 <tr>
8425      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="netcdf_data_format"></a>netcdf_data_format</span><br>
8426      </td>
8427      <td style="vertical-align: top;">I<br>
8428      </td>
8429      <td style="vertical-align: top;"><span style="font-style: italic;">2</span><br>
8430      </td>
8431      <td style="vertical-align: top;">Data format for NetCDF files.<br>
8432      <br>
8433This variable defines the format of the NetCDF files. Following values are allowed:<br>
8434      <br>
8435      <table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
8436        <tbody>
8437          <tr>
8438            <td style="vertical-align: top;"><span style="font-style: italic;">1</span><br>
8439            </td>
8440            <td style="vertical-align: top;">NetCDF classic format (filesize limited to 2GB)<br>
8441            </td>
8442          </tr>
8443          <tr>
8444            <td style="vertical-align: top;"><span style="font-style: italic;">2</span><br>
8445            </td>
8446            <td style="vertical-align: top;">NetCDF 64-bit-offset format (large file support, but single variable still limited to 2GB)<br>
8447            </td>
8448          </tr>
8449          <tr>
8450            <td style="vertical-align: top;"><span style="font-style: italic;">3</span><br>
8451            </td>
8452            <td style="vertical-align: top;">NetCDF-4 (HDF5) format (files can be as large as file system supports; unlimited variable size; allows parallel I/O)<br>
8453            </td>
8454          </tr>
8455          <tr>
8456            <td style="vertical-align: top;"><span style="font-style: italic;">4</span><br>
8457            </td>
8458            <td style="vertical-align: top;">NetCDF-4 format, but with NF90_CLASSIC_MODEL bit set (some new features of NetCDF4 are not available)<br>
8459            </td>
8460          </tr>
8461        </tbody>
8462      </table>
8463      <br>
8464      <span style="font-weight: bold;">Important:</span><br>
8465Setting <span style="font-weight: bold;">netcdf_data_format </span>&gt; <span style="font-style: italic;">2 </span>requires a NetCDF4 library (set <span style="font-family: Courier New,Courier,monospace;">-I</span>, <span style="font-family: Courier New,Courier,monospace;">-L</span>, and<span style="font-family: Courier New,Courier,monospace;"> -l </span>options for compiling and linking appropriately in configuration file). Also, preprocessor switch <span style="font-family: Courier New,Courier,monospace;">__netcdf4 </span>has to be set (see line starting with <span style="font-family: Courier New,Courier,monospace;">%cpp_opts </span>in the configuration file).<br>
8466      <br>
8467Files with NetCDF4 format cannot be read with NetCDF3 libraries.<br>
8468      </td>
8469    </tr>
8470
8471
8472
8473
8474
8475   
8476
8477
8478
8479
8480    <tr>
8481
8482
8483
8484
8485
8486      <td style="vertical-align: top;"> 
8487     
8488     
8489     
8490     
8491      <p><a name="ngsrb"></a><b>ngsrb</b></p>
8492
8493
8494
8495
8496 </td>
8497
8498
8499
8500
8501
8502      <td style="vertical-align: top;">I</td>
8503
8504
8505
8506
8507 <td style="vertical-align: top;"><i>2</i></td>
8508
8509
8510
8511
8512
8513      <td style="vertical-align: top;">Grid
8514level at which data shall be gathered on PE0.<br>
8515
8516
8517
8518
8519 <br>
8520
8521
8522
8523
8524
8525In case of a run using several PEs and the multigrid method for solving
8526the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
8527the value of this parameter defines on which grid level the data are
8528gathered on PE0 in order to allow for a further coarsening of the grid.
8529The finest grid defines the largest grid level. By default, the
8530gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
8531It is only possible to gather data from a level larger than the one
8532determined automatically. A test run may be neccessary to determine
8533this level.</td>
8534
8535
8536
8537
8538 </tr>
8539
8540
8541
8542
8543 <tr>
8544
8545
8546
8547
8548 <td style="vertical-align: top;"> 
8549     
8550     
8551     
8552     
8553      <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
8554
8555
8556
8557
8558
8559      </td>
8560
8561
8562
8563
8564 <td style="vertical-align: top;">I</td>
8565
8566
8567
8568
8569
8570      <td style="vertical-align: top;"><span style="font-style: italic;">0</span><br>
8571
8572
8573
8574
8575 </td>
8576
8577
8578
8579
8580
8581      <td style="vertical-align: top;"> 
8582     
8583     
8584     
8585     
8586      <p>Determines the
8587subdomain from which the normalization
8588quantities are calculated.&nbsp; </p>
8589
8590
8591
8592
8593 
8594     
8595     
8596     
8597     
8598      <p>If output
8599data of the horizontally averaged vertical profiles
8600(see <a href="#data_output_pr">data_output_pr</a>)
8601is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>,
8602      <a href="#cross_normalized_y">cross_normalized_y</a>),
8603the respective normalization quantities are by default calculated from
8604the averaged data of the total model domain (<b>normalizing_region</b>
8605= <i>0</i>) and are thus representative for the total
8606domain. Instead
8607of that, normalization quantities can also be calculated for a
8608subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>,
8609where <i>1</i>
8610&lt;= <b>normalizing_region</b> &lt;= <i>9 </i>must
8611hold. These
8612quantities are then used for normalizing of all profiles (even for that
8613of the total domain).</p>
8614
8615
8616
8617
8618 </td>
8619
8620
8621
8622
8623 </tr>
8624
8625
8626
8627
8628 <tr>
8629
8630      <td style="vertical-align: top;"><a href="npex"><span style="font-weight: bold;"></span></a><span style="font-weight: bold;"><a name="npex"></a>npex</span></td>
8631
8632      <td style="vertical-align: top;">I</td>
8633
8634      <td style="vertical-align: top;"><br>
8635</td>
8636
8637      <td style="vertical-align: top;">
8638     
8639      <p>Number of processors
8640along x-direction of the virtual
8641processor
8642net.&nbsp; </p>
8643
8644
8645
8646
8647
8648
8649
8650
8651 
8652     
8653     
8654     
8655     
8656     
8657     
8658     
8659     
8660      <p>For parallel runs, the total
8661number of processors to be used
8662is given by
8663the <span style="font-weight: bold;">mrun</span>
8664option <a href="http://www.muk.uni-hannover.de/software/mrun_beschreibung.html#Opt-X">-X</a>.
8665By default, depending on the type of the parallel computer, PALM
8666generates a 1d processor
8667net (domain decomposition along x, <span style="font-weight: bold;">npey</span>
8668= <span style="font-style: italic;">1</span>) or a
86692d-net (this is
8670favored on machines with fast communication network and/or large number of processors (&gt;256)). In case of a
86712d-net, it is tried to make it more or less square-shaped. If, for
8672example, 16 processors are assigned (-X 16), a 4 * 4 processor net is
8673generated (<span style="font-weight: bold;">npex</span>
8674= <span style="font-style: italic;">4</span>, <span style="font-weight: bold;">npey</span>
8675= <span style="font-style: italic;">4</span>).
8676This choice is optimal for square total domains (<a href="chapter_4.1.html#nx">nx</a>
8677= <a href="chapter_4.1.html#ny">ny</a>),
8678since then the number of ghost points at the lateral boundarys of
8679the subdomains reaches a minimum. If <span style="font-weight: bold;">nx</span>
8680and <span style="font-weight: bold;">ny</span>
8681differ extremely, the
8682processor net should be manually adjusted using adequate values for <span style="font-weight: bold;">npex</span> and <span style="font-weight: bold;">npey</span>.&nbsp; </p>
8683
8684
8685
8686
8687
8688
8689
8690
8691
8692     
8693     
8694     
8695     
8696     
8697     
8698     
8699     
8700      <p><b>Important:</b> The value of <span style="font-weight: bold;">npex</span> * <span style="font-weight: bold;">npey</span> must exactly match the
8701value assigned by the <span style="font-weight: bold;">mrun</span>-option
8702      <tt>-X</tt>.
8703Otherwise the model run will abort with a corresponding error
8704message.&nbsp; <br>
8705
8706
8707
8708
8709
8710
8711
8712
8713
8714Additionally, the specification of <span style="font-weight: bold;">npex</span>
8715and <span style="font-weight: bold;">npey</span>
8716may of course
8717override the default setting for the domain decomposition (1d or 2d)
8718which may have a significant (negative) effect on the code performance.
8719      </p>
8720
8721      </td>
8722
8723    </tr>
8724
8725    <tr>
8726
8727      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="npey"></a>npey</span></td>
8728
8729      <td style="vertical-align: top;">I</td>
8730
8731      <td style="vertical-align: top;"><br>
8732</td>
8733
8734      <td style="vertical-align: top;">
8735     
8736      <p>Number of processors
8737along y-direction of the virtual
8738processor
8739net.&nbsp; </p>
8740
8741
8742
8743
8744
8745
8746
8747
8748 
8749     
8750     
8751     
8752     
8753     
8754     
8755     
8756     
8757      <p>For further information see <a href="chapter_4.2.html#npex">npex</a>.</p>
8758
8759      </td>
8760
8761    </tr>
8762
8763    <tr>
8764
8765
8766
8767
8768 <td style="vertical-align: top;"> 
8769     
8770     
8771     
8772     
8773      <p><a name="nsor"></a><b>nsor</b></p>
8774
8775
8776
8777
8778
8779      </td>
8780
8781
8782
8783
8784 <td style="vertical-align: top;">I</td>
8785
8786
8787
8788
8789
8790      <td style="vertical-align: top;"><i>20</i></td>
8791
8792
8793
8794
8795
8796      <td style="vertical-align: top;"> 
8797     
8798     
8799     
8800     
8801      <p>Number of
8802iterations to be used with the SOR-scheme.&nbsp; </p>
8803
8804
8805
8806
8807 
8808     
8809     
8810     
8811     
8812      <p>This
8813parameter is only effective if the SOR-scheme is selected
8814as pressure solver (<a href="#psolver">psolver</a>
8815= <span style="font-style: italic;">'sor'</span>).
8816The number of
8817iterations necessary for a sufficient convergence of the scheme depends
8818on the grid point numbers and is to be determined by appropriate test
8819runs (the default value will not at all be sufficient for larger grid
8820point numbers). The number of iterations used for the first call of the
8821SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p>
8822
8823
8824
8825
8826
8827      </td>
8828
8829
8830
8831
8832 </tr>
8833
8834
8835
8836
8837 <tr>
8838
8839
8840
8841
8842 <td style="vertical-align: top;"> 
8843     
8844     
8845     
8846     
8847      <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
8848
8849
8850
8851
8852
8853      </td>
8854
8855
8856
8857
8858 <td style="vertical-align: top;">I</td>
8859
8860
8861
8862
8863
8864      <td style="vertical-align: top;"><i>nz+1</i></td>
8865
8866
8867
8868
8869
8870      <td style="vertical-align: top;"> Limits the output of 3d
8871volume data along the vertical direction (grid point index k).<br>
8872
8873
8874
8875
8876      <br>
8877
8878
8879
8880
8881By
8882default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
8883can be used to limit the output up to a certain vertical grid point
8884(e.g. in order to reduce the amount of output data). It affects all
8885output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output
8886for <span style="font-weight: bold;">dvrp</span>-software,
8887see <a href="#mode_dvrp">mode_dvrp</a>).</td>
8888
8889
8890
8891
8892
8893    </tr>
8894
8895
8896
8897
8898 <tr>
8899
8900
8901
8902
8903 <td style="vertical-align: top;">
8904     
8905     
8906     
8907     
8908      <p><a name="omega_sor"></a><b>omega_sor</b></p>
8909
8910
8911
8912
8913
8914      </td>
8915
8916
8917
8918
8919 <td style="vertical-align: top;">R</td>
8920
8921
8922
8923
8924
8925      <td style="vertical-align: top;"><i>1.8</i></td>
8926
8927
8928
8929
8930
8931      <td style="vertical-align: top;"> 
8932     
8933     
8934     
8935     
8936      <p>Convergence
8937factor to be used with the the SOR-scheme.&nbsp; </p>
8938
8939
8940
8941
8942 
8943     
8944     
8945     
8946     
8947      <p>If
8948the SOR-scheme is selected (<a href="#psolver">psolver</a>
8949= <span style="font-style: italic;">'sor'</span>),
8950this parameter
8951determines the value of the convergence factor, where <i>1.0</i>
8952&lt;= <b>omega_sor</b> &lt; <i>2.0 </i>.
8953The optimum value of <b>omega_sor</b>
8954depends on the number of grid points along the different directions in
8955space. For non-equidistant grids it can only be determined by
8956appropriate test runs.</p>
8957
8958
8959
8960
8961 </td>
8962
8963
8964
8965
8966 </tr>
8967
8968
8969
8970
8971 <tr>
8972
8973
8974
8975
8976 <td style="vertical-align: top;"> 
8977     
8978     
8979     
8980     
8981      <p><a name="prandtl_number"></a><b>prandtl_number</b></p>
8982
8983
8984
8985
8986
8987      </td>
8988
8989
8990
8991
8992 <td style="vertical-align: top;">R</td>
8993
8994
8995
8996
8997
8998      <td style="vertical-align: top;"><i>1.0</i></td>
8999
9000
9001
9002
9003
9004      <td style="vertical-align: top;"> 
9005     
9006     
9007     
9008     
9009      <p>Ratio of the
9010eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).&nbsp;
9011      </p>
9012
9013
9014
9015
9016 
9017     
9018     
9019     
9020     
9021      <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
9022this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub>
9023/ K<sub>h</sub>).</p>
9024
9025
9026
9027
9028 </td>
9029
9030
9031
9032
9033 </tr>
9034
9035
9036
9037
9038 <tr>
9039
9040
9041
9042
9043      <td style="vertical-align: top;"><a name="precipitation_amount_interval"></a><span style="font-weight: bold;">precipitation_amount_</span><br style="font-weight: bold;">
9044
9045
9046
9047
9048      <span style="font-weight: bold;">interval</span></td>
9049
9050
9051
9052
9053      <td style="vertical-align: top;">R</td>
9054
9055
9056
9057
9058      <td style="vertical-align: top;"><i>value of
9059&nbsp;<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>
9060
9061
9062
9063
9064xy</a></i></td>
9065
9066
9067
9068
9069      <td style="vertical-align: top;">
9070     
9071     
9072     
9073     
9074      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
9075interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).&nbsp;
9076      </font> </p>
9077
9078
9079
9080
9081 
9082     
9083     
9084     
9085     
9086      <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
9087parameter 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>
9088
9089
9090
9091
9092
9093      </font></span></p>
9094
9095
9096
9097
9098 <span lang="en-GB"></span></td>
9099
9100
9101
9102
9103    </tr>
9104
9105
9106
9107
9108    <tr>
9109
9110
9111
9112
9113
9114      <td style="vertical-align: top;"> 
9115     
9116     
9117     
9118     
9119      <p><a name="profile_columns"></a><b>profile_columns</b></p>
9120
9121
9122
9123
9124
9125      </td>
9126
9127
9128
9129
9130 <td style="vertical-align: top;">I</td>
9131
9132
9133
9134
9135
9136      <td style="vertical-align: top;"><i>3</i></td>
9137
9138
9139
9140
9141
9142      <td style="vertical-align: top;"> 
9143     
9144     
9145     
9146     
9147      <p>Number of
9148coordinate systems to be plotted<span style="font-weight: bold;"></span>
9149in one row by <span style="font-weight: bold;">profil</span>.&nbsp;
9150      </p>
9151
9152
9153
9154
9155 
9156     
9157     
9158     
9159     
9160      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
9161= <span style="font-style: italic;">'profil'</span>.</p>
9162
9163
9164
9165
9166     
9167     
9168     
9169     
9170      <p>It
9171determines the layout of plots of
9172horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
9173when plotted with the plot software <span style="font-weight: bold;">profil</span>.
9174Generally, the number and sequence of coordinate systems (panels) to be
9175plotted on one page are
9176determined by <a href="#cross_profiles">cross_profiles</a>.
9177      <b>profile_columns</b>
9178determines how many panels are to be
9179arranged next to each other in one row (number of columns). The
9180respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>.
9181According to their order given by <a href="#data_output_pr">data_output_pr</a>,
9182the panels are arranged beginning in the top row from left to right and
9183then continued in the following row. If the number of panels cranz
9184&gt; <b>profile_columns</b> * <b>profile_rows</b>,
9185the remaining
9186panels are drawn on an additional page. If cranz &lt; <b>profile_columns</b>,
9187then <b>profile_columns</b> = cranz is automatically set.
9188If
9189row&nbsp; contains any panel, then the value of <b>profile_rows</b>
9190is reduced automatically.</p>
9191
9192
9193
9194
9195 </td>
9196
9197
9198
9199
9200 </tr>
9201
9202
9203
9204
9205 <tr>
9206
9207
9208
9209
9210
9211      <td style="vertical-align: top;"> 
9212     
9213     
9214     
9215     
9216      <p><a name="profile_rows"></a><b>profile_rows</b></p>
9217
9218
9219
9220
9221
9222      </td>
9223
9224
9225
9226
9227 <td style="vertical-align: top;">I</td>
9228
9229
9230
9231
9232
9233      <td style="vertical-align: top;"><i>2</i></td>
9234
9235
9236
9237
9238
9239      <td style="vertical-align: top;"> 
9240     
9241     
9242     
9243     
9244      <p>Number of rows
9245of coordinate systems to be plotted on one page
9246by <span style="font-weight: bold;">profil</span>.&nbsp;
9247      </p>
9248
9249
9250
9251
9252 
9253     
9254     
9255     
9256     
9257      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
9258= <span style="font-style: italic;">'profil'</span>.</p>
9259
9260
9261
9262
9263     
9264     
9265     
9266     
9267      <p>It
9268determines the layout of plots of horizontally averaged
9269profiles. See <a href="#profile_columns">profile_columns</a>.</p>
9270
9271
9272
9273
9274
9275      </td>
9276
9277
9278
9279
9280 </tr>
9281
9282
9283
9284
9285 <tr>
9286
9287
9288
9289
9290 <td style="vertical-align: top;"> 
9291     
9292     
9293     
9294     
9295      <p><a name="psolver"></a><b>psolver</b></p>
9296
9297
9298
9299
9300
9301      </td>
9302
9303
9304
9305
9306 <td style="vertical-align: top;">C * 10</td>
9307
9308
9309
9310
9311
9312      <td style="vertical-align: top;"><i>'poisfft'</i></td>
9313
9314
9315
9316
9317
9318      <td style="vertical-align: top;"> 
9319     
9320     
9321     
9322     
9323      <p>Scheme to be
9324used to solve the Poisson equation for the
9325perturbation pressure.&nbsp; </p>
9326
9327
9328
9329
9330 <br>
9331
9332
9333
9334
9335
9336The user can choose between the following schemes:<br>
9337
9338
9339
9340
9341 
9342     
9343     
9344     
9345     
9346      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
9347
9348
9349
9350
9351 <tbody>
9352
9353
9354
9355
9356 <tr>
9357
9358
9359
9360
9361 <td style="vertical-align: top;"><i>poisfft</i></td>
9362
9363
9364
9365
9366
9367            <td style="vertical-align: top;">Direct method using FFT
9368along x and y, solution of a
9369tridiagonal matrix along z, and backward
9370FFT (see Siano, institute reports, volume 54). The FFT routines to be
9371used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
9372
9373
9374
9375
9376
9377This solver is specially optimized for 1d domain decompositions.
9378Vectorization is optimized for domain decompositions along x only.</td>
9379
9380
9381
9382
9383
9384          </tr>
9385
9386
9387
9388
9389 <tr>
9390
9391
9392
9393
9394 <td style="vertical-align: top;">
9395           
9396           
9397           
9398           
9399            <p><i>poisfft_</i>
9400            <br>
9401
9402
9403
9404
9405 <i>hybrid</i></p>
9406
9407
9408
9409
9410
9411            </td>
9412
9413
9414
9415
9416 <td style="vertical-align: top;">Direct
9417method using FFT
9418along x and y, solution of a
9419tridiagonal matrix along z, and backward
9420FFT (see Siano, institute reports, volume 54). The FFT routines to be
9421used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
9422
9423
9424
9425
9426
9427This solver is specially optimized for 1d domain decompositions.
9428Vectorization is optimized for domain decompositions along x only.</td>
9429
9430
9431
9432
9433
9434          </tr>
9435
9436
9437
9438
9439 <tr>
9440
9441
9442
9443
9444 <td style="vertical-align: top;"><i>multigrid</i></td>
9445
9446
9447
9448
9449
9450            <td style="vertical-align: top;"> 
9451           
9452           
9453           
9454           
9455            <p>Multi-grid
9456scheme (see Uhlenbrock, diploma thesis). v-
9457and
9458w-cycles (see <a href="#cycle_mg">cycle_mg</a>)
9459are implemented. The convergence of the iterative scheme can be
9460steered by the number of v-/w-cycles to be carried out for each call of
9461the scheme (<a href="#mg_cycles">mg_cycles</a>)
9462and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>)
9463to be carried out on each grid level. Instead the requested accuracy
9464can be given via <a href="#residual_limit">residual_limit</a>.
9465            <span style="font-weight: bold;">This is the default!</span>
9466The
9467smaller this limit is, the more cycles have to be carried out in this
9468case and the number of cycles may vary from timestep to timestep.</p>
9469
9470
9471
9472
9473
9474            <br>
9475
9476
9477
9478
9479If <a href="#mg_cycles">mg_cycles</a>
9480is set to its optimal value, the computing time of the
9481multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
9482the number of
9483grid points in the three directions
9484of space corresponds to a power-of-two (2<sup>n</sup>)
9485where <i>n</i> &gt;= 5 must hold. With large <i>n,
9486            </i>the
9487multi-grid scheme can even be faster than the direct solver (although
9488its accuracy is several orders of magnitude worse, but this does not
9489affect the accuracy of the simulation). Nevertheless, the user should
9490always carry out some test runs in order to find out the optimum value
9491for <a href="#mg_cycles">mg_cycles</a>,
9492because the CPU time of a run very critically depends on this
9493parameter.
9494           
9495           
9496           
9497           
9498            <p>This scheme requires that the number of grid
9499points of
9500the
9501subdomains (or of the total domain, if only one PE is uesd) along each
9502of the directions can at least be devided once by 2 without rest.</p>
9503
9504
9505
9506
9507
9508With parallel runs, starting from a certain grid level the
9509data of the subdomains are possibly gathered on PE0 in order to allow
9510for a further coarsening of the grid. The grid level for gathering can
9511be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
9512
9513
9514
9515
9516
9517           
9518           
9519           
9520           
9521            <p>Using this procedure requires the subdomains to be of
9522identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p>
9523
9524
9525
9526
9527
9528            </td>
9529
9530
9531
9532
9533 </tr>
9534
9535
9536
9537
9538 <tr>
9539
9540
9541
9542
9543 <td style="vertical-align: top;"><i>sor</i></td>
9544
9545
9546
9547
9548
9549            <td style="vertical-align: top;">Successive over
9550relaxation
9551method (SOR). The convergence of
9552this
9553iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>,
9554            <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
9555and <a href="chapter_4.1.html#nsor">nsor</a>.&nbsp;
9556            <br>
9557
9558
9559
9560
9561Compared to the direct method and the multi-grid method, this
9562scheme
9563needs substantially
9564more computing time. It should only be used for test runs, e.g. if
9565errors in the other pressure solver methods are assumed.</td>
9566
9567
9568
9569
9570 </tr>
9571
9572
9573
9574
9575
9576       
9577       
9578       
9579       
9580        </tbody> 
9581     
9582     
9583     
9584     
9585      </table>
9586
9587
9588
9589
9590 <br>
9591
9592
9593
9594
9595In order to speed-up
9596performance, the Poisson equation is by default
9597only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver
9598at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>).&nbsp;
9599      </td>
9600
9601
9602
9603
9604 </tr>
9605
9606
9607
9608
9609 <tr>
9610
9611
9612
9613
9614 <td style="vertical-align: top;"> 
9615     
9616     
9617     
9618     
9619      <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
9620      <br>
9621
9622
9623
9624
9625 <b>_factor</b></p>
9626
9627
9628
9629
9630 </td>
9631
9632
9633
9634
9635 <td style="vertical-align: top;">R</td>
9636
9637
9638
9639
9640 <td style="vertical-align: top;"><i>0.0 or</i><br>
9641
9642
9643
9644
9645
9646      <i>0.01</i></td>
9647
9648
9649
9650
9651 <td style="vertical-align: top;">
9652     
9653     
9654     
9655     
9656      <p>Factor for Rayleigh damping.&nbsp; </p>
9657
9658
9659
9660
9661 
9662     
9663     
9664     
9665     
9666      <p>A
9667so-called Rayleigh damping is applied to all prognostic
9668variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>.&nbsp;
9669If switched on, variables are forced towards the value of their
9670respective basic states (e.g. the geostrophic wind). The intensity of
9671damping is controlled by the value the <b>rayleigh_damping_factor</b>
9672is assigned to.
9673The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a>
9674and rises according to a sin<sup>2</sup>-function to its
9675maximum value
9676at
9677the top (ocean: bottom) boundary. </p>
9678
9679
9680
9681
9682 
9683     
9684     
9685     
9686     
9687      <p>This method
9688effectively damps gravity waves, caused by boundary layer convection,
9689which may spread out vertically in the inversion layer and which are
9690reflected&nbsp;at the top (ocean: bottom)
9691boundary. This particularly happens with the upstream-spline scheme
9692switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
9693or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>).
9694Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b>
9695= <i>0.01</i>) by default. Otherwise it remains switched
9696off.&nbsp; </p>
9697
9698
9699
9700
9701 
9702     
9703     
9704     
9705     
9706      <p>The Rayleigh damping factor must
9707hold the condition <i>0.0</i>
9708&lt;= <b>rayleigh_damping_factor</b>
9709&lt;= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
9710numerical instabilities.</p>
9711
9712
9713
9714
9715 </td>
9716
9717
9718
9719
9720 </tr>
9721
9722
9723
9724
9725 <tr>
9726
9727
9728
9729
9730
9731      <td style="vertical-align: top;"> 
9732     
9733     
9734     
9735     
9736      <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
9737      <br>
9738
9739
9740
9741
9742 <b>_height</b></p>
9743
9744
9745
9746
9747 </td>
9748
9749
9750
9751
9752 <td style="vertical-align: top;">R</td>
9753
9754
9755
9756
9757 <td style="vertical-align: top;"> 
9758     
9759     
9760     
9761     
9762      <p><i>2/3 *</i>
9763      <br>
9764
9765
9766
9767
9768      <span style="font-style: italic;">zu</span><i style="font-style: italic;">(nz)</i></p>
9769
9770
9771     
9772     
9773      <p> (ocean:<i style="font-style: italic;">&nbsp;</i><i>2/3 *</i>
9774      <i style="font-style: italic;"> zu(0)</i>)</p>
9775
9776
9777
9778
9779
9780      </td>
9781
9782
9783
9784
9785 <td style="vertical-align: top;"> 
9786     
9787     
9788     
9789     
9790      <p>Height above (ocean: below) which the Rayleigh damping starts (in m).&nbsp; </p>
9791
9792
9793
9794
9795 
9796     
9797     
9798     
9799     
9800      <p>With
9801Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
9802this parameter determines the range where damping is applied. By
9803default, Rayleigh damping will be applied in the upper (ocean: lower) third of the
9804model
9805domain.</p>
9806
9807
9808
9809
9810 </td>
9811
9812
9813
9814
9815 </tr>
9816
9817
9818
9819
9820 <tr>
9821
9822
9823
9824
9825 <td style="vertical-align: top;"> 
9826     
9827     
9828     
9829     
9830      <p><a name="residual_limit"></a><b>residual_limit</b></p>
9831
9832
9833
9834
9835
9836      </td>
9837
9838
9839
9840
9841 <td style="vertical-align: top;">R</td>
9842
9843
9844
9845
9846
9847      <td style="vertical-align: top;"><i>1.0E-6</i></td>
9848
9849
9850
9851
9852
9853      <td style="vertical-align: top;"> 
9854     
9855     
9856     
9857     
9858      <p>Largest
9859residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>).&nbsp;
9860      </p>
9861
9862
9863
9864
9865 
9866     
9867     
9868     
9869     
9870      <p>This is a parameter to steer the accuracy of the
9871multi-grid
9872scheme (see <a href="#psolver">psolver</a>).
9873The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>)
9874is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If
9875this
9876is not the case after 1000 cycles, the PALM aborts with a corresponding
9877error message.</p>
9878
9879
9880
9881
9882 
9883     
9884     
9885     
9886     
9887      <p>The reciprocal value of this
9888parameter can be interpreted as
9889a factor by the divergence of the provisional
9890velocity field is approximately reduced after the multi-grid scheme has
9891been applied (thus the default value causes a reduction of the
9892divergence by approx. 6 orders of magnitude).&nbsp; </p>
9893
9894
9895
9896
9897 </td>
9898
9899
9900
9901
9902
9903    </tr>
9904
9905
9906
9907
9908 <tr>
9909
9910
9911
9912
9913 <td style="vertical-align: top;">
9914     
9915     
9916     
9917     
9918      <p><a name="restart_time"></a><b>restart_time</b></p>
9919
9920
9921
9922
9923
9924      </td>
9925
9926
9927
9928
9929 <td style="vertical-align: top;">R</td>
9930
9931
9932
9933
9934
9935      <td style="vertical-align: top;"><i>9999999.9</i></td>
9936
9937
9938
9939
9940
9941      <td style="vertical-align: top;"> 
9942     
9943     
9944     
9945     
9946      <p>Simulated time
9947after which a restart run is to be carried out
9948(in s). </p>
9949
9950
9951
9952
9953 
9954     
9955     
9956     
9957     
9958      <p>The simulated time refers to the
9959beginning of the
9960initial run (t = 0), not to the beginning of the respective
9961restart run. Restart runs can additionally be forced to be carried out
9962in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p>
9963
9964
9965
9966
9967 
9968     
9969     
9970     
9971     
9972      <p><span style="font-weight: bold;">Note:</span><br>
9973
9974
9975
9976
9977
9978A successful operation of this parameter requires additional
9979modifications in the <span style="font-weight: bold;">mrun</span>-call
9980for the respective run (see <a href="chapter_3.3.html">chapter
99813.3</a>).<br>
9982
9983
9984
9985
9986 </p>
9987
9988
9989
9990
9991 
9992     
9993     
9994     
9995     
9996      <p>The choice of <b>restart_time</b>
9997or <b>dt_restart</b> does
9998not override the automatic start of restart runs in case that the job
9999runs out of CPU time. <br>
10000
10001
10002
10003      </p>
10004
10005
10006
10007     
10008     
10009     
10010      <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>
10011and&nbsp;<a href="chapter_3.4.html#PARIN"><font style="font-size: 10pt;" size="2">PARIN_O</font></a>.</p>
10012
10013
10014
10015
10016 </td>
10017
10018
10019
10020
10021 </tr>
10022
10023
10024
10025
10026
10027    <tr>
10028
10029
10030
10031
10032 <td style="vertical-align: top;"> 
10033     
10034     
10035     
10036     
10037      <p><a name="section_xy"></a><b>section_xy</b></p>
10038
10039
10040
10041
10042
10043      </td>
10044
10045
10046
10047
10048 <td style="vertical-align: top;">I(100)<br>
10049
10050
10051
10052
10053
10054      </td>
10055
10056
10057
10058
10059 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
10060
10061
10062
10063
10064
10065      </td>
10066
10067
10068
10069
10070 <td style="vertical-align: top;"> 
10071     
10072     
10073     
10074     
10075      <p lang="en-GB"><font face="Thorndale">Position
10076of&nbsp;cross section(s) for&nbsp;output of 2d horizontal cross
10077sections (grid point index k).&nbsp; </font> </p>
10078
10079
10080
10081
10082 
10083     
10084     
10085     
10086     
10087      <p><span lang="en-GB"><font face="Thorndale">If output
10088of
10089horizontal 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
10090parameter can be used to
10091define the position(s) of the cross section(s). Up to 100 positions of
10092cross sections can be selected by assigning <b>section_xy</b>
10093the
10094corresponding vertical grid point index/indices k of the requested
10095cross section(s). The exact location (height level) of the cross
10096section depends on the variable for which the output is made: zu(k) for
10097scalars and horizontal velocities, zw(k) for the vertical velocity.
10098Information about the exact location of the cross section is contained
10099in the NetCDF output file (if the default NetCDF output is switched on;
10100see <a href="#data_output_format">data_output_format</a>).</font></span></p>
10101
10102
10103
10104
10105     
10106     
10107     
10108     
10109      <p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
10110creates the output of horizontal cross sections averaged along z. In
10111the
10112NetCDF output file these (averaged) cross sections are given the
10113z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p>
10114
10115
10116
10117
10118     
10119     
10120     
10121     
10122      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
10123does not effect the output of horizontal cross sections of variable u<sub>*</sub>
10124and theta<sub>*</sub> and the liquid water path lwp*. For
10125these quantities always only one cross
10126section (for z=zu(1)) is output.</font></span></p>
10127
10128
10129
10130
10131      <span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
10132      <span style="font-style: italic;">'iso2d'</span> and
10133if several cross sections are selected (e.g. <b>section_xy</b>
10134= <i>1</i>, <i>10</i>, <i>15</i>),
10135then the respective data are
10136successively written to file. The output order follows the order given
10137by <b>section_xy</b>.&nbsp;</font></span></td>
10138
10139
10140
10141
10142
10143    </tr>
10144
10145
10146
10147
10148 <tr>
10149
10150
10151
10152
10153 <td style="vertical-align: top;">
10154     
10155     
10156     
10157     
10158      <p><a name="section_xz"></a><b>section_xz</b></p>
10159
10160
10161
10162
10163
10164      </td>
10165
10166
10167
10168
10169 <td style="vertical-align: top;">I(100)<br>
10170
10171
10172
10173
10174
10175      </td>
10176
10177
10178
10179
10180 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
10181
10182
10183
10184
10185
10186      <td style="vertical-align: top;"> 
10187     
10188     
10189     
10190     
10191      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
10192for&nbsp;output of 2d (xz) vertical cross sections (grid point
10193index j).&nbsp; </font> </p>
10194
10195
10196
10197
10198 <span lang="en-GB"><font face="Thorndale">If output of
10199vertical 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
10200parameter can be used to
10201define the position(s) of the cross section(s). Up to 100 positions of
10202cross sections can be selected by assigning <b>section_xz</b>
10203the
10204corresponding horizontal grid point index/indices j of the requested
10205cross section(s). The exact position (in y-direction) of the cross
10206section 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
10207on which grid the output quantity is defined. However, in
10208the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
10209default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
10210no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all
10211positions.<br>
10212
10213
10214
10215
10216      <br>
10217
10218
10219
10220
10221Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
10222creates the output of vertical cross sections averaged along y. In the
10223NetCDF output file these (averaged) cross sections are given the
10224y-coordinate <span style="font-style: italic;">-1.0</span>.<br>
10225
10226
10227
10228
10229      </font></span><span lang="en-GB"><font face="Thorndale"><br>
10230
10231
10232
10233
10234      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
10235      <span style="font-style: italic;">'iso2d'</span> and
10236      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
10237selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>,
10238      <i>27</i>),
10239then the respective data are successively written to file. The output
10240order follows the order given by <b>section_xz</b>.</font></span></td>
10241
10242
10243
10244
10245
10246    </tr>
10247
10248
10249
10250
10251 <tr>
10252
10253
10254
10255
10256 <td style="vertical-align: top;">
10257     
10258     
10259     
10260     
10261      <p><a name="section_yz"></a><b>section_yz</b></p>
10262
10263
10264
10265
10266
10267      </td>
10268
10269
10270
10271
10272 <td style="vertical-align: top;">I(100)<br>
10273
10274
10275
10276
10277
10278      </td>
10279
10280
10281
10282
10283 <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
10284
10285
10286
10287
10288
10289      <td style="vertical-align: top;"> 
10290     
10291     
10292     
10293     
10294      <p lang="en-GB"><font face="Thorndale">Position of&nbsp;cross section(s)
10295for&nbsp;output of 2d (yz) vertical cross sections (grid point
10296index i).&nbsp; </font> </p>
10297
10298
10299
10300
10301 <span lang="en-GB"><font face="Thorndale">If output of
10302vertical 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">),
10303this parameter can be used to define the position(s) of the cross
10304section(s). Up to 100 positions of cross sections can be selected by
10305assigning <b>section_yz</b> the corresponding horizontal
10306grid point
10307index/indices i of the requested cross section(s). The exact position
10308(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
10309on which grid the output quantity is defined.&nbsp;</font></span><span lang="en-GB"><font face="Thorndale">However, in
10310the&nbsp;NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
10311default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
10312no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all
10313positions.<br>
10314
10315
10316
10317
10318      <br>
10319
10320
10321
10322
10323      </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>
10324creates the output of vertical cross sections averaged along x. In the
10325NetCDF output file these (averaged) cross sections are given the
10326x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br>
10327
10328
10329
10330
10331      <span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br>
10332
10333
10334
10335
10336      </font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
10337      <span style="font-style: italic;">'iso2d'</span> and
10338      </font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
10339selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the
10340respective data are successively written to file. The output order
10341follows the order given by <b>section_yz</b>.</font></span></td>
10342
10343
10344
10345
10346
10347    </tr>
10348
10349
10350
10351
10352 <tr>
10353
10354
10355
10356
10357 <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
10358
10359
10360
10361
10362
10363      </td>
10364
10365
10366
10367
10368 <td style="vertical-align: top;">R<br>
10369
10370
10371
10372
10373 </td>
10374
10375
10376
10377
10378
10379      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br>
10380
10381
10382
10383
10384 </td>
10385
10386
10387
10388
10389
10390      <td style="vertical-align: top;">No data output before
10391this interval has passed (in s).<br>
10392
10393
10394
10395
10396      <br>
10397
10398
10399
10400
10401This
10402parameter causes that data output activities are starting not before
10403this interval
10404(counting from the beginning of the simulation, t=0) has passed. By
10405default, this
10406applies for output of instantaneous 3d volume data, cross section data,
10407spectra and vertical profile data as well as for temporally averaged 2d
10408and 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>
10409
10410
10411
10412
10413      <br>
10414
10415
10416
10417
10418      <span style="font-weight: bold;">Example:</span><br>
10419
10420
10421
10422
10423If
10424the user has set <a href="#dt_data_output">dt_data_output</a>
10425= <span style="font-style: italic;">3600.0</span>
10426and <span style="font-weight: bold;">skip_time_data_output</span>
10427= <span style="font-style: italic;">1800.0</span>,
10428then the first output will be done at t = 5400 s.<br>
10429
10430
10431
10432
10433 </td>
10434
10435
10436
10437
10438
10439    </tr>
10440
10441
10442
10443
10444 <tr>
10445
10446
10447
10448
10449      <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>
10450
10451
10452
10453
10454      <td style="vertical-align: top;">R</td>
10455
10456
10457
10458
10459      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>
10460
10461
10462
10463
10464data_output</a></span></td>
10465
10466
10467
10468
10469      <td style="vertical-align: top;">No output of temporally
10470averaged 2d/3d data before this interval has passed (in s).<br>
10471
10472
10473
10474
10475      <br>
10476
10477
10478
10479
10480This
10481parameter causes that data output activities are starting not before
10482this interval
10483(counting from the beginning of the simulation, t=0) has passed. <br>
10484
10485
10486
10487
10488      <br>
10489
10490
10491
10492
10493      <span style="font-weight: bold;">Example:</span><br>
10494
10495
10496
10497
10498If
10499the user has set <a href="#dt_data_output_av">dt_data_output_av</a>
10500= <span style="font-style: italic;">3600.0</span>
10501and <span style="font-weight: bold;">skip_time_data_output_av</span>
10502= <span style="font-style: italic;">1800.0</span>,
10503then the first output will be done at t = 5400 s.</td>
10504
10505
10506
10507
10508    </tr>
10509
10510
10511
10512
10513    <tr>
10514
10515
10516
10517
10518
10519      <td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
10520
10521
10522
10523
10524
10525      </td>
10526
10527
10528
10529
10530 <td style="vertical-align: top;">R<br>
10531
10532
10533
10534
10535 </td>
10536
10537
10538
10539
10540
10541      <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>
10542
10543
10544
10545
10546data_output</a></span>
10547      </td>
10548
10549
10550
10551
10552 <td style="vertical-align: top;">No output of
10553vertical profile data before this interval has passed (in s).<br>
10554
10555
10556
10557
10558      <br>
10559
10560
10561
10562
10563This
10564parameter causes that data output activities are starting not before
10565this interval
10566(counting from the beginning of the simulation, t=0) has passed. <br>
10567
10568
10569
10570
10571      <br>
10572
10573
10574
10575
10576      <span style="font-weight: bold;">Example:</span><br>
10577
10578
10579
10580
10581If
10582the 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
10583first output will be done at t = 5400 s. </td>
10584
10585
10586
10587
10588 </tr>
10589
10590
10591
10592
10593 <tr>
10594
10595
10596
10597
10598
10599      <td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
10600
10601
10602
10603
10604
10605      </td>
10606
10607
10608
10609
10610 <td style="vertical-align: top;">R<br>
10611
10612
10613
10614
10615 </td>
10616
10617
10618
10619
10620
10621      <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>
10622
10623
10624
10625
10626data_output</a></span>
10627      </td>
10628
10629
10630
10631
10632 <td style="vertical-align: top;">No output of
10633instantaneous horizontal cross section data before this interval has
10634passed (in s).<br>
10635
10636
10637
10638
10639      <br>
10640
10641
10642
10643
10644This
10645parameter causes that data output activities are starting not before
10646this interval
10647(counting from the beginning of the simulation, t=0) has passed. <br>
10648
10649
10650
10651
10652      <br>
10653
10654
10655
10656
10657      <span style="font-weight: bold;">Example:</span><br>
10658
10659
10660
10661
10662If
10663the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a>
10664= <span style="font-style: italic;">3600.0</span>
10665and <span style="font-weight: bold;">skip_time_do2d_xy</span>
10666= <span style="font-style: italic;">1800.0</span>,
10667then the first output will be done at t = 5400 s. </td>
10668
10669
10670
10671
10672 </tr>
10673
10674
10675
10676
10677
10678    <tr>
10679
10680
10681
10682
10683 <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
10684
10685
10686
10687
10688
10689      </td>
10690
10691
10692
10693
10694 <td style="vertical-align: top;">R<br>
10695
10696
10697
10698
10699 </td>
10700
10701
10702
10703
10704
10705      <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>
10706
10707
10708
10709
10710data_output</a></span>
10711      </td>
10712
10713
10714
10715
10716 <td style="vertical-align: top;">No output of
10717instantaneous vertical (xz) cross section data before this interval has
10718passed (in s).<br>
10719
10720
10721
10722
10723      <br>
10724
10725
10726
10727
10728This
10729parameter causes that data output activities are starting not before
10730this interval
10731(counting from the beginning of the simulation, t=0) has passed. <br>
10732
10733
10734
10735
10736      <br>
10737
10738
10739
10740
10741      <span style="font-weight: bold;">Example:</span><br>
10742
10743
10744
10745
10746If
10747the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a>
10748= <span style="font-style: italic;">3600.0</span>
10749and <span style="font-weight: bold;">skip_time_do2d_xz</span>
10750= <span style="font-style: italic;">1800.0</span>,
10751then the first output will be done at t = 5400 s. </td>
10752
10753
10754
10755
10756 </tr>
10757
10758
10759
10760
10761
10762    <tr>
10763
10764
10765
10766
10767 <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
10768
10769
10770
10771
10772
10773      </td>
10774
10775
10776
10777
10778 <td style="vertical-align: top;">R<br>
10779
10780
10781
10782
10783 </td>
10784
10785
10786
10787
10788
10789      <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>
10790
10791
10792
10793
10794data_output</a></span>
10795      </td>
10796
10797
10798
10799
10800 <td style="vertical-align: top;">No output of
10801instantaneous vertical (yz) cross section data before this interval has
10802passed (in s).<br>
10803
10804
10805
10806
10807      <br>
10808
10809
10810
10811
10812This
10813parameter causes that data output activities are starting not before
10814this interval
10815(counting from the beginning of the simulation, t=0) has passed. <br>
10816
10817
10818
10819
10820      <br>
10821
10822
10823
10824
10825      <span style="font-weight: bold;">Example:</span><br>
10826
10827
10828
10829
10830If
10831the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a>
10832= <span style="font-style: italic;">3600.0</span>
10833and <span style="font-weight: bold;">skip_time_do2d_yz</span>
10834= <span style="font-style: italic;">1800.0</span>,
10835then the first output will be done at t = 5400 s. </td>
10836
10837
10838
10839
10840 </tr>
10841
10842
10843
10844
10845
10846    <tr>
10847
10848
10849
10850
10851 <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
10852
10853
10854
10855
10856
10857      </td>
10858
10859
10860
10861
10862 <td style="vertical-align: top;">R<br>
10863
10864
10865
10866
10867 </td>
10868
10869
10870
10871
10872
10873      <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>
10874
10875
10876
10877
10878data_output</a></span>
10879      </td>
10880
10881
10882
10883
10884 <td style="vertical-align: top;">No output of
10885instantaneous 3d volume data before this interval has passed (in s).<br>
10886
10887
10888
10889
10890      <br>
10891
10892
10893
10894
10895This
10896parameter causes that data output activities are starting not before
10897this interval
10898(counting from the beginning of the simulation, t=0) has passed. <br>
10899
10900
10901
10902
10903      <br>
10904
10905
10906
10907
10908      <span style="font-weight: bold;">Example:</span><br>
10909
10910
10911
10912
10913If
10914the 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
10915first output will be done at t = 5400 s. </td>
10916
10917
10918
10919
10920 </tr>
10921
10922
10923
10924
10925
10926    <tr>
10927
10928
10929
10930
10931 <td style="vertical-align: top;"> 
10932     
10933     
10934     
10935     
10936      <p><a name="termination_time_needed"></a><b>termination_time</b>
10937      <br>
10938
10939
10940
10941
10942 <b>_needed</b></p>
10943
10944
10945
10946
10947 </td>
10948
10949
10950
10951
10952 <td style="vertical-align: top;">R<br>
10953
10954
10955
10956
10957 </td>
10958
10959
10960
10961
10962 <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br>
10963
10964
10965
10966
10967 </td>
10968
10969
10970
10971
10972
10973      <td style="vertical-align: top;"> 
10974     
10975     
10976     
10977     
10978      <p>CPU time
10979needed for terminal actions at the end of a run in
10980batch mode (in s).<br>
10981
10982
10983
10984
10985 </p>
10986
10987
10988
10989
10990 
10991     
10992     
10993     
10994     
10995      <p>If the environment
10996variable <b>write_binary </b>is
10997set <i>true</i> (see <a href="chapter_3.3.html">chapter
109983.3</a>), PALM checks the remaining CPU time of the job after
10999each
11000timestep. Time integration must not consume the CPU time completely,
11001since several actions still have to be carried out after time
11002integration has finished (e.g. writing of binary data for the restart
11003run, carrying out output commands, copying of local files to their
11004permanent destinations, etc.) which also takes some time. The maximum
11005possible time needed for these activities plus a reserve is to be given
11006with the parameter <b>termination_time_needed</b>. Among
11007other things,
11008it depends on
11009the number of grid points used. If its value is selected too small,
11010then the
11011respective job will be prematurely aborted by the queuing system, which
11012may result in a data loss and will possibly interrupt the job chain.<br>
11013
11014
11015
11016
11017
11018      </p>
11019
11020
11021
11022
11023 
11024     
11025     
11026     
11027     
11028      <p>An abort happens in any way, if the environment
11029variable <span style="font-weight: bold;">write_binary</span>
11030is not set to <span style="font-style: italic;">true</span>
11031and if moreover the job has
11032been assigned an insufficient CPU time by <b>mrun</b>
11033option <tt><tt>-t</tt></tt>. <i><br>
11034
11035
11036
11037
11038
11039      </i> </p>
11040
11041
11042
11043
11044 
11045     
11046     
11047     
11048     
11049      <p><span style="font-weight: bold;">Note:</span><br>
11050
11051
11052
11053
11054
11055On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of
11056PALM
11057have also to be accounted for (e.g. for
11058compilation and copying of input files).</p>
11059
11060
11061
11062
11063 </td>
11064
11065
11066
11067
11068 </tr>
11069
11070
11071
11072
11073
11074    <tr>
11075
11076
11077
11078
11079 <td style="vertical-align: top;"> 
11080     
11081     
11082     
11083     
11084      <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
11085      <br>
11086
11087
11088
11089
11090 <b>_parameters</b></p>
11091
11092
11093
11094
11095 </td>
11096
11097
11098
11099
11100 <td style="vertical-align: top;">L</td>
11101
11102
11103
11104
11105 <td style="vertical-align: top;"><i>.F.</i></td>
11106
11107
11108
11109
11110
11111      <td style="vertical-align: top;"> 
11112     
11113     
11114     
11115     
11116      <p>Additional
11117plot of vertical profile data with <span style="font-weight: bold;">profil</span>
11118from preceding runs of the
11119job chain.&nbsp; </p>
11120
11121
11122
11123
11124 
11125     
11126     
11127     
11128     
11129      <p>This parameter only applies
11130for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
11131= <span style="font-style: italic;">'profil'</span>.</p>
11132
11133
11134
11135
11136     
11137     
11138     
11139     
11140      <p>By
11141default, plots of horizontally averaged vertical profiles
11142(see <a href="#data_output_pr">data_output_pr</a>)
11143only contain profiles of data produced by the model
11144run. If profiles of prior times (i.e. data of preceding jobs of a
11145job chain) shall be plotted additionally (e.g. for comparison
11146purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>.
11147must be
11148set.<br>
11149
11150
11151
11152
11153 </p>
11154
11155
11156
11157
11158 
11159     
11160     
11161     
11162     
11163      <p>For further explanation see <a href="chapter_4.5.2.html">chapter
111644.5.2</a>.</p>
11165
11166
11167
11168
11169 </td>
11170
11171
11172
11173
11174 </tr>
11175
11176
11177
11178
11179 <tr>
11180
11181
11182
11183
11184 <td style="vertical-align: top;"> 
11185     
11186     
11187     
11188     
11189      <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
11190
11191
11192
11193
11194
11195      </td>
11196
11197
11198
11199
11200 <td style="vertical-align: top;">R</td>
11201
11202
11203
11204
11205
11206      <td style="vertical-align: top;"><i>zu(nzt+1) (model
11207top)</i></td>
11208
11209
11210
11211
11212 <td style="vertical-align: top;">
11213     
11214     
11215     
11216     
11217      <p>Height level up to which horizontally averaged profiles are to
11218be
11219plotted with <span style="font-weight: bold;">profil</span>
11220(in
11221m).&nbsp; </p>
11222
11223
11224
11225
11226 
11227     
11228     
11229     
11230     
11231      <p>This parameter only applies for
11232&nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
11233= <span style="font-style: italic;">'profil'</span>.</p>
11234
11235
11236
11237
11238     
11239     
11240     
11241     
11242      <p>It
11243affects plots of horizontally averaged profiles
11244(<a href="#data_output_pr">data_output_pr</a>)
11245when plotted with the plot software <span style="font-weight: bold;">profil</span>.
11246By default, profiles are plotted up to the top boundary. The height
11247level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller
11248value.
11249Nevertheless, <span style="font-weight: bold;">all</span>
11250vertical
11251grid points (0 &lt;= k &lt;= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p>
11252
11253
11254
11255
11256
11257     
11258     
11259     
11260     
11261      <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>
11262has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a>
11263must be used.</p>
11264
11265
11266
11267
11268 </td>
11269
11270
11271
11272
11273 </tr>
11274
11275
11276
11277
11278 <tr>
11279
11280
11281
11282
11283 <td style="vertical-align: top;"> 
11284     
11285     
11286     
11287     
11288      <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
11289      <br>
11290
11291
11292
11293
11294 <b>_normalized</b></p>
11295
11296
11297
11298
11299 </td>
11300
11301
11302
11303
11304 <td style="vertical-align: top;">R</td>
11305
11306
11307
11308
11309 <td style="vertical-align: top;"><i>determined by plot</i>
11310      <br>
11311
11312
11313
11314
11315 <i>data</i> <br>
11316
11317
11318
11319
11320 </td>
11321
11322
11323
11324
11325 <td style="vertical-align: top;"> 
11326     
11327     
11328     
11329     
11330      <p>Normalized height
11331level up to which horizontally averaged
11332profiles are to be plotted with <span style="font-weight: bold;">profil</span>.&nbsp;
11333      </p>
11334
11335
11336
11337
11338 
11339     
11340     
11341     
11342     
11343      <p>This parameter only applies for &nbsp;<a href="chapter_4.2.html#data_output_format">data_output_format</a>
11344= <span style="font-style: italic;">'profil'</span>.</p>
11345
11346
11347
11348
11349     
11350     
11351     
11352     
11353      <p>It
11354affects plots of horizontally averaged profiles
11355(<a href="#data_output_pr">data_output_pr</a>)
11356when plotted with the plot software <span style="font-weight: bold;">profil</span>,
11357if a normalization for the vertical axis is selected
11358(see <a href="#cross_normalized_y">cross_normalized_y</a>).
11359If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b>
11360= <i>1.5</i> means that all profiles up to the height
11361level of z =
113621.5* z<sub>i </sub>are plotted.</p>
11363
11364
11365
11366
11367 </td>
11368
11369
11370
11371
11372 </tr>
11373
11374
11375
11376
11377
11378    <tr>
11379
11380
11381
11382
11383 <td style="vertical-align: top;"> 
11384     
11385     
11386     
11387     
11388      <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
11389
11390
11391
11392
11393
11394      </td>
11395
11396
11397
11398
11399 <td style="vertical-align: top;">R<br>
11400
11401
11402
11403
11404 </td>
11405
11406
11407
11408
11409
11410      <td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br>
11411
11412
11413
11414
11415 </td>
11416
11417
11418
11419
11420
11421      <td style="vertical-align: top;"> 
11422     
11423     
11424     
11425     
11426      <p>Height level
11427up to which 2d cross sections are to be plotted
11428with <span style="font-weight: bold;">iso2d</span>
11429(in m).&nbsp; </p>
11430
11431
11432
11433
11434 
11435     
11436     
11437     
11438     
11439      <p>This parameter only applies for
11440&nbsp;<a href="#data_output_format">data_output_format</a>
11441= <span style="font-style: italic;">'iso2d'</span>.</p>
11442
11443
11444
11445
11446     
11447     
11448     
11449     
11450      <p>It
11451affects plots of&nbsp; 2d vertical cross
11452sections (<a href="#data_output">data_output</a>)
11453when plotted with <span style="font-weight: bold;">iso2d</span>.
11454By
11455default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d
11456      </b>the
11457visualization within
11458the plot can be limited to a certain height level (0 &lt;= z
11459&lt;= <b>z_max_do2d</b>).
11460Nevertheless, <span style="font-weight: bold;">all</span>
11461grid points
11462of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>
11463or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
11464The level up to which the section is visualized can later be changed by
11465manually editing the
11466file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>
11467or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>
11468(the respective <span style="font-weight: bold;">iso2d</span>-parameter
11469is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p>
11470
11471
11472
11473
11474
11475      </td>
11476
11477
11478
11479
11480 </tr>
11481
11482
11483
11484
11485 
11486 
11487 
11488 
11489 
11490  </tbody>
11491</table>
11492
11493
11494
11495
11496<br>
11497
11498
11499
11500
11501
11502<br>
11503
11504
11505
11506
11507<h3 style="line-height: 100%;"><a name="particle_parameters"></a>Particle
11508parameters: </h3>
11509
11510
11511
11512
11513
11514<span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>NAMELIST group name: <span style="font-weight: bold;">particles_par<br>
11515
11516
11517
11518
11519
11520</span>
11521<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
11522
11523
11524
11525
11526 <tbody>
11527
11528
11529
11530
11531    <tr>
11532
11533
11534
11535
11536
11537      <td style="vertical-align: top;"><font size="4"><b>Parameter
11538name</b></font></td>
11539
11540
11541
11542
11543
11544      <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
11545
11546
11547
11548
11549
11550      <td style="vertical-align: top;"> 
11551     
11552     
11553     
11554     
11555      <p><b><font size="4">Default</font></b> <br>
11556
11557
11558
11559
11560 <b><font size="4">value</font></b></p>
11561
11562
11563
11564
11565 </td>
11566
11567
11568
11569
11570
11571      <td style="vertical-align: top;"> 
11572     
11573     
11574     
11575     
11576      <p><font size="4"><b>Explanation</b></font></p>
11577
11578
11579
11580
11581
11582      </td>
11583
11584
11585
11586
11587 </tr>
11588
11589
11590
11591
11592 <tr>
11593
11594
11595
11596
11597 <td style="vertical-align: top;"> 
11598     
11599     
11600     
11601     
11602      <p><a name="dt_prel"></a><b>dt_prel</b></p>
11603
11604
11605
11606
11607
11608      </td>
11609
11610
11611
11612
11613 <td style="vertical-align: top;">R</td>
11614
11615
11616
11617
11618
11619      <td style="vertical-align: top;"><i>9999999.9</i></td>
11620
11621
11622
11623
11624
11625      <td style="vertical-align: top;"> 
11626     
11627     
11628     
11629     
11630      <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
11631interval at
11632which particles are to be released <span lang="en-GB">from
11633a particle
11634source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>&nbsp;
11635      </font> </p>
11636
11637
11638
11639
11640 
11641     
11642     
11643     
11644     
11645      <p><span lang="en-GB"><font face="Thorndale, serif">By default
11646particles are released only at the beginning of a simulation
11647(t_init=0). The time of the first release (t_init) can be changed with
11648package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>.
11649      </font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
11650set with the package parameter <a href="#end_time_prel">end_time_prel</a>.
11651If <span style="font-weight: bold;">dt_prel</span>
11652has been set, additional
11653releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>,
11654t_init+2*<span style="font-weight: bold;">dt_prel</span>,
11655t_init+3*<span style="font-weight: bold;">dt_prel</span>,
11656etc.. Actual release times
11657may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see
11658e.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>
11659
11660
11661
11662
11663
11664     
11665     
11666     
11667     
11668      <p><span lang="en-GB"><font face="Thorndale, serif"> The domain
11669of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as
11670well as the distance of&nbsp; released particles
11671within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package
11672parameters </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>
11673      <span lang="en-GB"><font face="Thorndale, serif">and
11674      </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
11675default, one particle is released at all points defined by these
11676parameters. The package parameter <a href="#particles_per_point">particles_per_point</a>
11677can be used to start more than one particle per point.<br>
11678
11679
11680
11681
11682
11683      </font></span></p>
11684
11685
11686
11687
11688 
11689     
11690     
11691     
11692     
11693      <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
11694different 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">)
11695where each group may have a different source. All particles belonging
11696to one group have the same density ratio and the same radius. All other
11697particle features (e.g. location of the source) are
11698identical for all groups of particles.</font></span></p>
11699
11700
11701
11702
11703Subgrid
11704scale velocities can (optionally) be included for calculating the
11705particle advection, using the method of Weil et al. (2004, JAS, 61,
117062877-2887). This method is switched on by the package
11707parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.
11708This also forces the Euler/upstream method to be used for time
11709advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>).
11710The minimum timestep during the sub-timesteps is controlled by package
11711parameter <a href="#dt_min_part">dt_min_part</a>.
11712     
11713     
11714     
11715     
11716      <p><span lang="en-GB"><font face="Thorndale, serif">By
11717default, particles are weightless and transported passively with the
11718resolved scale flow. Particles can be given a mass and thus an inertia
11719by assigning the
11720package 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
11721non-zero value (it
11722defines the ratio of the density of the fluid and the density of the
11723particles). 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">
11724must 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>
11725
11726
11727
11728
11729
11730     
11731     
11732     
11733     
11734      <p><span lang="en-GB"><font face="Thorndale, serif">Boundary
11735conditions for the particle transport can be defined with package
11736parameters </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>
11737      <span lang="en-GB"><font face="Thorndale, serif">and
11738      </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>
11739
11740
11741
11742
11743      <span lang="en-GB"><font face="Thorndale, serif">Timeseries
11744of 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>
11745by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br>
11746
11747
11748
11749
11750      </font></span>
11751     
11752     
11753     
11754     
11755      <p>For
11756analysis, additional output of
11757particle
11758information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a>
11759(file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br>
11760
11761
11762
11763
11764
11765      </p>
11766
11767
11768
11769
11770 
11771     
11772     
11773     
11774     
11775      <p><span style="font-family: thorndale,serif;">Statistical
11776informations</span> (e.g. the total number of particles used, the
11777number of particles exchanged between the PEs, etc.) are output to the
11778local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>,
11779if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>.
11780      <br>
11781
11782
11783
11784
11785 </p>
11786
11787
11788
11789
11790 
11791     
11792     
11793     
11794     
11795      <p><span lang="en-GB"><font face="Thorndale, serif">If a job
11796chain is to be carried out, particle
11797informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
11798location of
11799all
11800particles at the end of the
11801run) is output to
11802the 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>,
11803      <span lang="en-GB"><font face="Thorndale, serif">which
11804must be saved at the
11805end of the run <tt><span lang="en-GB"></span></tt>and
11806given as an
11807input file to the restart run
11808under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>
11809u<span lang="en-GB"><font face="Thorndale, serif">sing
11810respective file
11811connection statements in the <span style="font-weight: bold;">mrun</span>
11812configuration file. </font></span> <span lang="en-GB"></span></p>
11813
11814
11815
11816
11817     
11818     
11819     
11820     
11821      <p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
11822particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by
11823the package
11824parameter </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">.
11825For visualization
11826purposes particles can be given a
11827diameter using the parameters <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a>
11828and <a href="#particle_dvrpsize">particle_dvrpsize</a> (this diameter only affects the visualization). All particles have the
11829same size. Alternatively, particles can be given an individual size and
11830a </span>color <span lang="en-GB">by modifying the
11831user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">.
11832Particles can pull a
11833&#8220;tail&#8221; behind themselves to improve their
11834visualization.
11835This 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>
11836
11837
11838
11839
11840 <span lang="en-GB"></span>
11841     
11842     
11843     
11844     
11845      <p><b>So far, the
11846particle transport realized in PALM does only
11847work
11848duly in case of a constant vertical grid spacing!</b></p>
11849
11850
11851
11852
11853 </td>
11854
11855
11856
11857
11858
11859    </tr>
11860
11861
11862
11863
11864 <tr>
11865
11866
11867
11868
11869 <td style="vertical-align: top;">
11870     
11871     
11872     
11873     
11874      <p><a name="bc_par_b"></a><b>bc_par_b</b></p>
11875
11876
11877
11878
11879
11880      </td>
11881
11882
11883
11884
11885 <td style="vertical-align: top;">C*15</td>
11886
11887
11888
11889
11890
11891      <td style="vertical-align: top;"><i>ï¿œreflectï¿œ</i></td>
11892
11893
11894
11895
11896
11897      <td style="vertical-align: top;"> 
11898     
11899     
11900     
11901     
11902      <p>Bottom
11903boundary condition for particle transport. </p>
11904
11905
11906
11907
11908 
11909     
11910     
11911     
11912     
11913      <p>By
11914default, particles are reflected at the bottom boundary.
11915Alternatively, a particle absorption can set by <b>bc_par_b</b>
11916= <i>ᅵabsorbᅵ</i>.</p>
11917
11918
11919
11920
11921 </td>
11922
11923
11924
11925
11926
11927    </tr>
11928
11929
11930
11931
11932 <tr>
11933
11934
11935
11936
11937 <td style="vertical-align: top;">
11938     
11939     
11940     
11941     
11942      <p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
11943
11944
11945
11946
11947
11948      </td>
11949
11950
11951
11952
11953 <td style="vertical-align: top;">C*15</td>
11954
11955
11956
11957
11958
11959      <td style="vertical-align: top;"><i>ï¿œcyclicï¿œ</i></td>
11960
11961
11962
11963
11964
11965      <td style="vertical-align: top;"> 
11966     
11967     
11968     
11969     
11970      <p>Lateral
11971boundary condition (x-direction) for particle
11972transport. </p>
11973
11974
11975
11976
11977 
11978     
11979     
11980     
11981     
11982      <p>By default, cyclic boundary conditions
11983are used along x.
11984Alternatively, reflection (<b>bc_par_lr</b>
11985= <i>ᅵreflectᅵ</i>) or absorption (<b>bc_par_lr</b>
11986= <i>ᅵabsorbᅵ</i>)
11987can be set. <br>
11988
11989
11990
11991
11992 </p>
11993
11994
11995
11996
11997 
11998     
11999     
12000     
12001     
12002      <p>This lateral boundary
12003conditions should correspond to the
12004lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p>
12005
12006
12007
12008
12009 </td>
12010
12011
12012
12013
12014
12015    </tr>
12016
12017
12018
12019
12020 <tr>
12021
12022
12023
12024
12025 <td style="vertical-align: top;">
12026     
12027     
12028     
12029     
12030      <p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
12031
12032
12033
12034
12035
12036      </td>
12037
12038
12039
12040
12041 <td style="vertical-align: top;">C*15</td>
12042
12043
12044
12045
12046
12047      <td style="vertical-align: top;"><i>ï¿œcyclicï¿œ</i></td>
12048
12049
12050
12051
12052
12053      <td style="vertical-align: top;"> 
12054     
12055     
12056     
12057     
12058      <p>Lateral
12059boundary condition (y-direction) for particle
12060transport. </p>
12061
12062
12063
12064
12065 
12066     
12067     
12068     
12069     
12070      <p>By default, cyclic boundary conditions
12071are used along y.
12072Alternatively, reflection (<b>bc_par_ns</b>
12073= <i>ᅵreflectᅵ</i>) or absorption (<b>bc_par_ns</b>
12074= <i>ᅵabsorbᅵ</i>)
12075can be set.<br>
12076
12077
12078
12079
12080 </p>
12081
12082
12083
12084
12085
12086This lateral boundary conditions should correspond to the lateral
12087boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td>
12088
12089
12090
12091
12092 </tr>
12093
12094
12095
12096
12097
12098    <tr>
12099
12100
12101
12102
12103 <td style="vertical-align: top;"> 
12104     
12105     
12106     
12107     
12108      <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
12109
12110
12111
12112
12113
12114      </td>
12115
12116
12117
12118
12119 <td style="vertical-align: top;">C*15</td>
12120
12121
12122
12123
12124
12125      <td style="vertical-align: top;"><i>ï¿œabsorbï¿œ</i></td>
12126
12127
12128
12129
12130
12131      <td style="vertical-align: top;"> 
12132     
12133     
12134     
12135     
12136      <p>Top boundary
12137condition for particle transport. </p>
12138
12139
12140
12141
12142 
12143     
12144     
12145     
12146     
12147      <p>By default,
12148particles are absorbed at the top boundary.
12149Alternatively, a reflection condition can be set by <b>bc_par_t</b>
12150= <i>ᅵreflectᅵ</i>.</p>
12151
12152
12153
12154
12155 </td>
12156
12157
12158
12159
12160
12161    </tr>
12162
12163
12164
12165
12166 <tr>
12167
12168
12169
12170
12171 <td style="vertical-align: top;">
12172     
12173     
12174     
12175     
12176      <p><a name="density_ratio"></a><b>density_ratio</b></p>
12177
12178
12179
12180
12181
12182      </td>
12183
12184
12185
12186
12187 <td style="vertical-align: top;">R (10)</td>
12188
12189
12190
12191
12192
12193      <td style="vertical-align: top;"> 
12194     
12195     
12196     
12197     
12198      <p><i>0.0, 9</i>
12199*<br>
12200
12201
12202
12203
12204 <i>9999999.9</i></p>
12205
12206
12207
12208
12209 </td>
12210
12211
12212
12213
12214 <td style="vertical-align: top;"> 
12215     
12216     
12217     
12218     
12219      <p>Ratio of the density
12220of the fluid and the density of the
12221particles. </p>
12222
12223
12224
12225
12226 
12227     
12228     
12229     
12230     
12231      <p>With the default value<i> </i>the
12232particles are weightless and transported passively with the resolved
12233scale flow.
12234In case of <span style="font-weight: bold;">density_ratio</span>
12235/=
122360.0 particles have a mass and hence inertia so that their velocity
12237deviates more or less from the velocity of the surrounding flow.
12238Particle velocity is calculated analytically and depends on (besides
12239the density ratio and the current velocity difference between particles
12240and surrounding fluid) the
12241particle radius which is determined via <a href="#radius">radius</a>
12242as well as on the molecular viscosity (assumed as 1.461E-5 m<sup>2</sup>/s).
12243      </p>
12244
12245
12246
12247
12248 
12249     
12250     
12251     
12252     
12253      <p>If <b>density_ratio</b> = <i>1.0</i>,
12254the particle density
12255corresponds to the density of the surrounding fluid and the particles
12256do not feel any buoyancy. Otherwise, particles will be accelerated
12257upwards (<b>density_ratio</b> &gt; <i>1.0</i>)
12258or downwards (<b>density_ratio</b> &lt; <i>1.0</i>).<br>
12259
12260
12261
12262
12263
12264      </p>
12265
12266
12267
12268
12269 
12270     
12271     
12272     
12273     
12274      <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
12275each group can be assigned a different value. If the number of values
12276given for <span style="font-weight: bold;">density_ratio</span>
12277is less than the number of
12278groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
12279then the last assigned value is used for all remaining groups. This
12280means that by default the particle density ratio for all groups will be
12281      <span style="font-style: italic;">0.0</span>.</p>
12282
12283
12284
12285
12286
12287      </td>
12288
12289
12290
12291
12292 </tr>
12293
12294
12295
12296
12297 <tr>
12298
12299
12300
12301
12302      <td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td>
12303
12304
12305
12306
12307      <td align="left" valign="top">R</td>
12308
12309
12310
12311
12312      <td align="left" valign="top"><i>value of &nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
12313
12314
12315
12316
12317output</a></i></td>
12318
12319
12320
12321
12322      <td align="left" valign="top">
12323     
12324     
12325     
12326     
12327      <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
12328interval</font> at which time series data of particle quantities
12329shall be output (</font>in <font face="Thorndale">s).&nbsp;</font></p>
12330
12331
12332
12333
12334
12335      <span lang="en-GB"><font face="Thorndale">If
12336particle advection is switched on (see</font></span><font><span style="font-family: thorndale;"> <a href="#dt_prel">dt_prel</a>)
12337this parameter can be used to assign
12338th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
12339interval at which time series of particle quantities shall be output.
12340Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br>
12341
12342
12343
12344
12345      <br>
12346
12347
12348
12349
12350The
12351following list gives a short description of the&nbsp;quantities
12352available. Most quantities are averages over all particles. The
12353quantity name given in the first column is identical to the respective
12354name of the variable on the NetCDF file (see section <a href="chapter_4.5.1.html">4.5.1</a> for a general
12355description of the NetCDF files).<br>
12356
12357
12358
12359
12360      <br>
12361
12362
12363
12364
12365In case of using
12366more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
12367seperate time series are output for each of the groups. The long names
12368of the variables in the NetCDF file containing the respective
12369timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle
12370group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
12371
12372
12373
12374
12375&nbsp;</font></span>
12376     
12377     
12378     
12379     
12380      <table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2">
12381
12382
12383
12384
12385        <tbody>
12386
12387
12388
12389
12390          <tr>
12391
12392
12393
12394
12395            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td>
12396
12397
12398
12399
12400            <td align="undefined" valign="undefined">total number of
12401particles</td>
12402
12403
12404
12405
12406          </tr>
12407
12408
12409
12410
12411          <tr>
12412
12413
12414
12415
12416            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td>
12417
12418
12419
12420
12421            <td align="undefined" valign="undefined">particle
12422x-coordinate&nbsp;with respect to the particle origin (in m)</td>
12423
12424
12425
12426
12427          </tr>
12428
12429
12430
12431
12432          <tr>
12433
12434
12435
12436
12437            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td>
12438
12439
12440
12441
12442            <td align="undefined" valign="undefined">particle
12443y-coordinate&nbsp;with respect to the particle origin (in m)</td>
12444
12445
12446
12447
12448          </tr>
12449
12450
12451
12452
12453          <tr>
12454
12455
12456
12457
12458            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td>
12459
12460
12461
12462
12463            <td align="undefined" valign="undefined">particle
12464z-coordinate&nbsp;with respect to the particle origin (in m)</td>
12465
12466
12467
12468
12469          </tr>
12470
12471
12472
12473
12474          <tr>
12475
12476
12477
12478
12479            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td>
12480
12481
12482
12483
12484            <td align="undefined" valign="undefined">absolute
12485particle z-coordinate (in m)</td>
12486
12487
12488
12489
12490          </tr>
12491
12492
12493
12494
12495          <tr>
12496
12497
12498
12499
12500            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td>
12501
12502
12503
12504
12505            <td align="undefined" valign="undefined">u particle
12506velocity component (in m/s)</td>
12507
12508
12509
12510
12511          </tr>
12512
12513
12514
12515
12516          <tr>
12517
12518
12519
12520
12521            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td>
12522
12523
12524
12525
12526            <td align="undefined" valign="undefined">v particle
12527velocity component (in m/s)</td>
12528
12529
12530
12531
12532          </tr>
12533
12534
12535
12536
12537          <tr>
12538
12539
12540
12541
12542            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td>
12543
12544
12545
12546
12547            <td align="undefined" valign="undefined">w particle
12548velocity component (in m/s)</td>
12549
12550
12551
12552
12553          </tr>
12554
12555
12556
12557
12558          <tr>
12559
12560
12561
12562
12563            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td>
12564
12565
12566
12567
12568            <td align="undefined" valign="undefined">subgrid-scale u
12569particle velocity component (in m/s)</td>
12570
12571
12572
12573
12574          </tr>
12575
12576
12577
12578
12579          <tr>
12580
12581
12582
12583
12584            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td>
12585
12586
12587
12588
12589            <td align="undefined" valign="undefined">subgrid-scale v
12590particle velocity component (in m/s)</td>
12591
12592
12593
12594
12595          </tr>
12596
12597
12598
12599
12600          <tr>
12601
12602
12603
12604
12605            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td>
12606
12607
12608
12609
12610            <td align="undefined" valign="undefined">subgrid-scale w
12611particle velocity component (in m/s)</td>
12612
12613
12614
12615
12616          </tr>
12617
12618
12619
12620
12621          <tr>
12622
12623
12624
12625
12626            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td>
12627
12628
12629
12630
12631            <td align="undefined" valign="undefined">total number of
12632upward moving particles</td>
12633
12634
12635
12636
12637          </tr>
12638
12639
12640
12641
12642          <tr>
12643
12644
12645
12646
12647            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td>
12648
12649
12650
12651
12652            <td align="undefined" valign="undefined">vertical
12653velocity of the upward moving particles (in m/s)</td>
12654
12655
12656
12657
12658          </tr>
12659
12660
12661
12662
12663          <tr>
12664
12665
12666
12667
12668            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td>
12669
12670
12671
12672
12673            <td align="undefined" valign="undefined">vertical
12674velocity of the downward moving particles (in m/s)</td>
12675
12676
12677
12678
12679          </tr>
12680
12681
12682
12683
12684          <tr>
12685
12686
12687
12688
12689            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td>
12690
12691
12692
12693
12694            <td align="undefined" valign="undefined">maximum number
12695of particles in a subdomain (=tnpt for non-parallel runs)</td>
12696
12697
12698
12699
12700          </tr>
12701
12702
12703
12704
12705          <tr>
12706
12707
12708
12709
12710            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td>
12711
12712
12713
12714
12715            <td align="undefined" valign="undefined">minimum number
12716of particles in a subdomain (=tnpt for non-parallel runs)</td>
12717
12718
12719
12720
12721          </tr>
12722
12723
12724
12725
12726          <tr>
12727
12728
12729
12730
12731            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td>
12732
12733
12734
12735
12736            <td align="undefined" valign="undefined">variance of the
12737particle x-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td>
12738
12739
12740
12741
12742          </tr>
12743
12744
12745
12746
12747          <tr>
12748
12749
12750
12751
12752            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td>
12753
12754
12755
12756
12757            <td align="undefined" valign="undefined">variance of the
12758particle y-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td>
12759
12760
12761
12762
12763          </tr>
12764
12765
12766
12767
12768          <tr>
12769
12770
12771
12772
12773            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td>
12774
12775
12776
12777
12778            <td align="undefined" valign="undefined">variance of the
12779particle z-coordinate&nbsp;with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td>
12780
12781
12782
12783
12784          </tr>
12785
12786
12787
12788
12789          <tr>
12790
12791
12792
12793
12794            <td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td>
12795
12796
12797
12798
12799            <td align="undefined" valign="undefined">variance of the
12800u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
12801
12802
12803
12804
12805          </tr>
12806
12807
12808
12809
12810          <tr>
12811
12812
12813
12814
12815            <td align="undefined" valign="undefined">v*2</td>
12816
12817
12818
12819
12820            <td align="undefined" valign="undefined">variance of the
12821v particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">v </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
12822
12823
12824
12825
12826          </tr>
12827
12828
12829
12830
12831          <tr>
12832
12833
12834
12835
12836            <td align="undefined" valign="undefined">w*2</td>
12837
12838
12839
12840
12841            <td align="undefined" valign="undefined">variance of the
12842w particle velocity component with respect to&nbsp;<span style="color: rgb(255, 0, 0);">w </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
12843
12844
12845
12846
12847          </tr>
12848
12849
12850
12851
12852          <tr>
12853
12854
12855
12856
12857            <td align="undefined" valign="undefined">u"2</td>
12858
12859
12860
12861
12862            <td align="undefined" valign="undefined">variance of the
12863subgrid-scale u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
12864
12865
12866
12867
12868          </tr>
12869
12870
12871
12872
12873          <tr>
12874
12875
12876
12877
12878            <td align="undefined" valign="undefined">v"2</td>
12879
12880
12881
12882
12883            <td align="undefined" valign="undefined">variance of the
12884subgrid-scale v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
12885
12886
12887
12888
12889          </tr>
12890
12891
12892
12893
12894          <tr>
12895
12896
12897
12898
12899            <td align="undefined" valign="undefined">w"2</td>
12900
12901
12902
12903
12904            <td align="undefined" valign="undefined">variance of the
12905subgrid-scale w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td>
12906
12907
12908
12909
12910          </tr>
12911
12912
12913
12914
12915          <tr>
12916
12917
12918
12919
12920            <td align="undefined" valign="undefined">npt*2</td>
12921
12922
12923
12924
12925            <td align="undefined" valign="undefined">variance of the
12926number of particles with respect to the average number of particles per
12927subdomain</td>
12928
12929
12930
12931
12932          </tr>
12933
12934
12935
12936
12937       
12938       
12939       
12940       
12941        </tbody>
12942     
12943     
12944     
12945     
12946      </table>
12947
12948
12949
12950
12951      <span lang="en-GB"></span><span lang="en-GB"></span></td>
12952
12953
12954
12955
12956    </tr>
12957
12958
12959
12960
12961    <tr>
12962
12963
12964
12965
12966      <td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td>
12967
12968
12969
12970
12971      <td align="left" valign="top">R</td>
12972
12973
12974
12975
12976      <td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td>
12977
12978
12979
12980
12981      <td align="left" valign="top">Minimum value for the
12982particle timestep when SGS velocities are used (in s).<br>
12983
12984
12985
12986
12987      <br>
12988
12989
12990
12991
12992For
12993a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td>
12994
12995
12996
12997
12998    </tr>
12999
13000
13001
13002
13003    <tr>
13004
13005      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="dt_sort_particles"></a>dt_sort_particles</span></td>
13006
13007      <td style="vertical-align: top;">R</td>
13008
13009      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
13010
13011      <td style="vertical-align: top;">Temporal interval for sorting particles (in s).<br>
13012
13013      <br>
13014
13015By
13016default, particles are sorted in memory in a way that their order
13017follows the order in which the gridpoint values are stored. This may
13018improve cache coherence in case of larger numbers of particles and
13019gridpoints. However, since the sorting itself is time consuming and
13020since the requirement of sorting depends on the strength of mixing in
13021the flow, performance can be improved if the sorting is applied only
13022after certain time intervals. The proper length of this interval <span style="font-weight: bold;">dt_sort_particles</span> must be determined empirically by carrying out test runs with different intervals. Check file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> to find the value of <span style="font-weight: bold;">dt_sort_particles</span> which gives the best performance.<br>
13023
13024      <br>
13025
13026      <span style="font-weight: bold;">Note:</span><br>
13027
13028In case of <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.T.</span>, any given non-zero value of <span style="font-weight: bold;">dt_sort_particles</span> will be reset to zero and a corresponding warning message will appear in the job protocol.</td>
13029
13030    </tr>
13031
13032    <tr>
13033
13034
13035
13036
13037
13038      <td style="vertical-align: top;"> 
13039     
13040     
13041     
13042     
13043      <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b>
13044      <b>data</b></p>
13045
13046
13047
13048
13049 </td>
13050
13051
13052
13053
13054 <td style="vertical-align: top;">R<br>
13055
13056
13057
13058
13059 </td>
13060
13061
13062
13063
13064 <td style="vertical-align: top;"><i>9999999.9</i></td>
13065
13066
13067
13068
13069
13070      <td style="vertical-align: top;"> 
13071     
13072     
13073     
13074     
13075      <p>Temporal
13076interval for output of particle data (in s). </p>
13077
13078
13079
13080
13081 
13082     
13083     
13084     
13085     
13086      <p>T<span lang="en-GB"></span><a href="#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
13087parameter can be used to
13088assign the temporal interval at which particle data shall be output.</font></span>
13089Data are output to
13090the local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>.
13091      <span style="font-family: mon;">See the file description
13092for more
13093details about its format</span>. </p>
13094
13095
13096
13097
13098 
13099     
13100     
13101     
13102     
13103      <p>By
13104default, no particle data are output.</p>
13105
13106
13107
13108
13109 </td>
13110
13111
13112
13113
13114 </tr>
13115
13116
13117
13118
13119
13120   
13121
13122
13123 <tr>
13124
13125
13126
13127
13128      <td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td>
13129
13130
13131
13132
13133      <td align="left" valign="top">R</td>
13134
13135
13136
13137
13138      <td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td>
13139
13140
13141
13142
13143      <td align="left" valign="top">Time of the last release of
13144particles (in s).<br>
13145
13146
13147
13148
13149      <br>
13150
13151
13152
13153
13154See also <a href="#particle_advection_start">particle_advection_start</a>.</td>
13155
13156
13157
13158
13159    </tr>
13160
13161
13162
13163
13164    <tr>
13165
13166
13167
13168
13169
13170      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td>
13171
13172
13173
13174
13175
13176      <td style="vertical-align: top;">R<br>
13177
13178
13179
13180
13181 </td>
13182
13183
13184
13185
13186 <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br>
13187
13188
13189
13190
13191 </td>
13192
13193
13194
13195
13196
13197      <td style="vertical-align: top;">Factor to define the real
13198number of initial droplets in a grid box.<br>
13199
13200
13201
13202
13203 <br>
13204
13205
13206
13207
13208
13209In case of explicitly simulating cloud droplets (see <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>),
13210the real number of initial droplets in a grid box is equal to the
13211initial number of droplets in this box (defined by the particle source
13212parameters <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
13213      <span lang="en-GB"><font face="Thorndale, serif">and
13214      </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>)
13215times the <span style="font-weight: bold;">initial_weighting_factor</span>.</td>
13216
13217
13218
13219
13220
13221    </tr>
13222
13223
13224
13225
13226    <tr>
13227
13228
13229
13230
13231 <td style="vertical-align: top;"> 
13232     
13233     
13234     
13235     
13236      <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b>
13237      <br>
13238
13239
13240
13241
13242 <b>particles</b></p>
13243
13244
13245
13246
13247 </td>
13248
13249
13250
13251
13252 <td style="vertical-align: top;">I</td>
13253
13254
13255
13256
13257 <td style="vertical-align: top;"><i>1000</i></td>
13258
13259
13260
13261
13262
13263      <td style="vertical-align: top;"> 
13264     
13265     
13266     
13267     
13268      <p>Maximum number
13269of particles (on a PE).&nbsp; </p>
13270
13271
13272
13273
13274 
13275     
13276     
13277     
13278     
13279      <p>This parameter
13280allows to set the number of particles for which
13281memory must be allocated at the beginning of the run.
13282If this memory becomes insufficient during the run, due to the
13283release of further particles (see <a href="#dt_prel">dt_prel</a>),
13284then more memory is automatically allocated.<br>
13285
13286
13287
13288
13289 </p>
13290
13291
13292
13293
13294
13295For runs on several processors, <span style="font-weight: bold;">maximum_number_of_particles</span>
13296defines
13297the maximum number on each PE. This number must be larger than the
13298maximum number of particles initially released in a subdomain.</td>
13299
13300
13301
13302
13303
13304    </tr>
13305
13306
13307
13308
13309 <tr>
13310
13311
13312
13313
13314 <td style="vertical-align: top;">
13315     
13316     
13317     
13318     
13319      <p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b>
13320      <br>
13321
13322
13323
13324
13325 <b>tailpoints</b></p>
13326
13327
13328
13329
13330 </td>
13331
13332
13333
13334
13335 <td style="vertical-align: top;">I</td>
13336
13337
13338
13339
13340 <td style="vertical-align: top;"><i>100</i></td>
13341
13342
13343
13344
13345
13346      <td style="vertical-align: top;"> 
13347     
13348     
13349     
13350     
13351      <p>Maximum number
13352of tailpoints that a particle tail can
13353have.&nbsp; </p>
13354
13355
13356
13357
13358 
13359     
13360     
13361     
13362     
13363      <p>&nbsp;<b>maximum_number_of_tailpoints</b>
13364sets the number of descrete points the tail consists of. A new point is
13365added to the particle tails after each time step. If the maximum number
13366of tail
13367points is reached after the corresponding number of timesteps, the
13368oldest respective tail points is deleted within the following
13369timestep.&nbsp; </p>
13370
13371
13372
13373
13374 
13375     
13376     
13377     
13378     
13379      <p>All particle tails have the
13380same number of points. The maximum
13381length of
13382these
13383tails is determined by the value of <b>maximum_number_of_tailpoints</b>
13384and by the minimum distance between each of the adjoining
13385tailpoints,&nbsp; which can be set by <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.
13386Additionally, it can be determined that the temporal displacement
13387between the current position of the particle and the oldest point of
13388the tail may become not larger than a value to be assigned by <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>.</p>
13389
13390
13391
13392
13393
13394      </td>
13395
13396
13397
13398
13399 </tr>
13400
13401
13402
13403
13404 <tr>
13405
13406
13407
13408
13409 <td style="vertical-align: top;"> 
13410     
13411     
13412     
13413     
13414      <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b>
13415      <br>
13416
13417
13418
13419
13420 <b>age</b></p>
13421
13422
13423
13424
13425 </td>
13426
13427
13428
13429
13430 <td style="vertical-align: top;">R</td>
13431
13432
13433
13434
13435 <td style="vertical-align: top;">100000.0</td>
13436
13437
13438
13439
13440 <td style="vertical-align: top;"> 
13441     
13442     
13443     
13444     
13445      <p>Maximum age that the
13446end point of a particle tail is allowed to have (in s).&nbsp; </p>
13447
13448
13449
13450
13451
13452     
13453     
13454     
13455     
13456      <p>If the temporal displacement between the oldest point of a
13457particle tail and the current position of the particle becomes larger
13458than the value given by <b>maximum_tailpoint_age</b>, this
13459oldest
13460point (which defines the end of the tail) is
13461removed. If this time is so small that the number of points defining
13462the particle tail do not exceed the value given by <b>maximum_number_of_tailpoints</b>,
13463then the length the particle tails is a measure for the distance the
13464particle travelled along during the time interval defined via <b>maximum_tailpoint_age</b>,
13465i.e. for the
13466particle velocity. Fast particles will have long tails, slow particles
13467shorter ones (note: this will not neccessarily hold if <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>
13468= <i>0.0</i>).</p>
13469
13470
13471
13472
13473 </td>
13474
13475
13476
13477
13478 </tr>
13479
13480
13481
13482
13483 <tr>
13484
13485
13486
13487
13488
13489      <td style="vertical-align: top;"> 
13490     
13491     
13492     
13493     
13494      <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</b></p>
13495
13496
13497
13498
13499
13500      </td>
13501
13502
13503
13504
13505 <td style="vertical-align: top;">R</td>
13506
13507
13508
13509
13510
13511      <td style="vertical-align: top;"><i>0.0</i></td>
13512
13513
13514
13515
13516
13517      <td style="vertical-align: top;"> 
13518     
13519     
13520     
13521     
13522      <p>Minimum
13523distance allowed between two adjacent points of a
13524particle tail (in m).&nbsp; </p>
13525
13526
13527
13528
13529 
13530     
13531     
13532     
13533     
13534      <p>In case of <b>minimum_tailpoint_distance</b>
13535&gt; <i>0.0 </i>the
13536particle tail is extended by a new point only if the distance between
13537its current position and the most recent tail point exceed the
13538distance given via <b>minimum_tailpoint_distance</b>.<br>
13539
13540
13541
13542
13543
13544      </p>
13545
13546
13547
13548
13549 
13550     
13551     
13552     
13553     
13554      <p>If the length of the particle tails shall be
13555proportional to
13556the respective particle velocity, the parameter <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>
13557must also be set appropriately. </p>
13558
13559
13560
13561
13562 <b>Note:</b><br>
13563
13564
13565
13566
13567
13568A suitable choice of <b>minimum_tailpoint_distance</b>
13569&gt; <i>0.0</i> is recommended, because then the tail
13570coordinates of
13571slowly moving particles require less memory and can also be drawn
13572faster. The upper limit of <b>minimum_tailpoint_distance</b>
13573should be chosen in a way that the visualized particle
13574tails still appear as smooth lines. Example: with a model domain of
135751000 m and a monitor resolution of 1280 * 1024 pixels it
13576should be sufficient to set <b>minimum_tailpoint_distance</b>
13577= <i>5.0</i>
13578(m). </td>
13579
13580
13581
13582
13583 </tr>
13584
13585
13586
13587
13588 <tr>
13589
13590
13591
13592
13593 <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br>
13594
13595
13596
13597
13598
13599      </td>
13600
13601
13602
13603
13604 <td style="vertical-align: top;">I<br>
13605
13606
13607
13608
13609 </td>
13610
13611
13612
13613
13614
13615      <td style="vertical-align: top;">1<br>
13616
13617
13618
13619
13620 </td>
13621
13622
13623
13624
13625 <td style="vertical-align: top;">Number of particle groups to be
13626used.<br>
13627
13628
13629
13630
13631 <br>
13632
13633
13634
13635
13636
13637Each particle group can be assigned its own source region (see <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
13638      <a href="#psr">psr</a>, etc.), particle diameter (<a href="#radius">radius</a>) and particle density ratio (<a href="density_ratio">density_ratio</a>).<br>
13639
13640
13641
13642
13643      <br>
13644
13645
13646
13647
13648If
13649less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
13650etc. than the number of particle groups, then the last value is used
13651for the remaining values (or the default value, if the user did not set
13652the parameter).<br>
13653
13654
13655
13656
13657 <br>
13658
13659
13660
13661
13662
13663The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br>
13664
13665
13666
13667
13668 </td>
13669
13670
13671
13672
13673
13674    </tr>
13675
13676
13677
13678
13679    <tr>
13680
13681
13682
13683
13684      <td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td>
13685
13686
13687
13688
13689      <td align="left" valign="top">I</td>
13690
13691
13692
13693
13694      <td align="left" valign="top">1</td>
13695
13696
13697
13698
13699      <td align="left" valign="top">Number of particles to be
13700started per point.<br>
13701
13702
13703
13704
13705      <br>
13706
13707
13708
13709
13710By default, one particle is
13711started at all points of the particle source,&nbsp;defined by <span style="font-family: Thorndale,serif;">the </span><span lang="en-GB"><font face="Thorndale, serif">package
13712parameters </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
13713      <span lang="en-GB"><font face="Thorndale, serif">and
13714      </font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"></span></td>
13715
13716
13717
13718
13719    </tr>
13720
13721
13722
13723
13724    <tr>
13725
13726
13727
13728
13729 <td style="vertical-align: top;"> 
13730     
13731     
13732     
13733     
13734      <p><a name="particle_advection_start"></a><b>particle_advection_</b>
13735      <br>
13736
13737
13738
13739
13740 <b>start</b></p>
13741
13742
13743
13744
13745 </td>
13746
13747
13748
13749
13750 <td style="vertical-align: top;">R </td>
13751
13752
13753
13754
13755 <td style="vertical-align: top;">0.0 </td>
13756
13757
13758
13759
13760 <td style="vertical-align: top;"> 
13761     
13762     
13763     
13764     
13765      <p>Time of the first
13766release of particles (in s). </p>
13767
13768
13769
13770
13771 
13772     
13773     
13774     
13775     
13776      <p>If particles are not
13777to be released at the beginning of the
13778run, the release time can be set via <b>particle_advection_start</b>.<br>
13779
13780
13781
13782
13783
13784If particle transport is switched on in a restart run, then <a href="#read_particles_from_restartfile">read_particles_from_restartfile</a>
13785= <span style="font-style: italic;">.F.</span> is
13786also required.</p>
13787
13788
13789
13790
13791     
13792     
13793     
13794     
13795      <p>See also <a href="#end_time_prel">end_time_prel</a>.
13796      </p>
13797
13798
13799
13800
13801 </td>
13802
13803
13804
13805
13806 </tr>
13807
13808
13809
13810
13811 <tr>
13812
13813
13814
13815
13816 <td style="vertical-align: top;"> 
13817     
13818     
13819     
13820     
13821      <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p>
13822
13823
13824
13825
13826
13827      </td>
13828
13829
13830
13831
13832 <td style="vertical-align: top;">R </td>
13833
13834
13835
13836
13837
13838      <td style="vertical-align: top;"><i>9999999.9</i>
13839      </td>
13840
13841
13842
13843
13844 <td style="vertical-align: top;"> 
13845     
13846     
13847     
13848     
13849      <p>Maximum
13850allowed age of particles (in s).&nbsp; </p>
13851
13852
13853
13854
13855 
13856     
13857     
13858     
13859     
13860      <p>If the
13861age of a particle exceeds the time set by <b>particle_maximum_age</b>,
13862the particle as well as its tail is deleted.</p>
13863
13864
13865
13866
13867 </td>
13868
13869
13870
13871
13872 </tr>
13873
13874
13875
13876
13877
13878    <tr>
13879
13880
13881
13882
13883 <td style="vertical-align: top;"> 
13884     
13885     
13886     
13887     
13888      <p><a name="pdx"></a><b>pdx</b></p>
13889
13890
13891
13892
13893 </td>
13894
13895
13896
13897
13898
13899      <td style="vertical-align: top;">R (10)<br>
13900
13901
13902
13903
13904 </td>
13905
13906
13907
13908
13909
13910      <td style="vertical-align: top;"><i>10 * dx</i>
13911      </td>
13912
13913
13914
13915
13916 <td style="vertical-align: top;"> 
13917     
13918     
13919     
13920     
13921      <p>Distance
13922along x between particles within a particle source
13923(in m).&nbsp; </p>
13924
13925
13926
13927
13928 
13929     
13930     
13931     
13932     
13933      <p>If the particle source shall be
13934confined to one grid point,
13935the distances given by <span style="font-weight: bold;">pdx</span>,
13936      <a href="#pdy">pdy</a>
13937and <a href="#pdz">pdz</a>
13938must be set larger than the respective domain size or <a href="#psl">psl</a>
13939= <a href="#psr">psr</a> has to be set
13940alternatively.<br>
13941
13942
13943
13944
13945
13946      </p>
13947
13948
13949
13950
13951 
13952     
13953     
13954     
13955     
13956      <p><span style="font-weight: bold;">pdx</span>
13957can be assigned a different value for each particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>).<br>
13958
13959
13960
13961
13962
13963      </p>
13964
13965
13966
13967
13968 </td>
13969
13970
13971
13972
13973 </tr>
13974
13975
13976
13977
13978 <tr>
13979
13980
13981
13982
13983 <td style="vertical-align: top;"> 
13984     
13985     
13986     
13987     
13988      <p><a name="pdy"></a><b>pdy</b></p>
13989
13990
13991
13992
13993
13994      </td>
13995
13996
13997
13998
13999 <td style="vertical-align: top;">R (10)<br>
14000
14001
14002
14003
14004
14005      </td>
14006
14007
14008
14009
14010 <td style="vertical-align: top;"><i>10
14011* dy</i> </td>
14012
14013
14014
14015
14016 <td style="vertical-align: top;">Distance
14017along y between
14018particles within a
14019particle source (in m).&nbsp; </td>
14020
14021
14022
14023
14024 </tr>
14025
14026
14027
14028
14029 <tr>
14030
14031
14032
14033
14034
14035      <td style="vertical-align: top;"> 
14036     
14037     
14038     
14039     
14040      <p><a name="pdz"></a><b>pdz</b></p>
14041
14042
14043
14044
14045 </td>
14046
14047
14048
14049
14050
14051      <td style="vertical-align: top;">R (10)<br>
14052
14053
14054
14055
14056
14057      </td>
14058
14059
14060
14061
14062 <td style="vertical-align: top;"><i>10
14063* ( zu(2) - zu(1) )</i> </td>
14064
14065
14066
14067
14068 <td style="vertical-align: top;">Distance along z between
14069particles within a particle source
14070(in m). </td>
14071
14072
14073
14074
14075 </tr>
14076
14077
14078
14079
14080 <tr>
14081
14082
14083
14084
14085 <td style="vertical-align: top;"> 
14086     
14087     
14088     
14089     
14090      <p><a name="psb"></a><b>psb</b></p>
14091
14092
14093
14094
14095
14096      </td>
14097
14098
14099
14100
14101 <td style="vertical-align: top;">R (10)<br>
14102
14103
14104
14105
14106
14107      </td>
14108
14109
14110
14111
14112 <td style="vertical-align: top;"><i>10&nbsp;
14113* zu(nz/2)</i> </td>
14114
14115
14116
14117
14118 <td style="vertical-align: top;">Bottom
14119edge of a particle
14120source (in m). </td>
14121
14122
14123
14124
14125 </tr>
14126
14127
14128
14129
14130 <tr>
14131
14132
14133
14134
14135 <td style="vertical-align: top;"> 
14136     
14137     
14138     
14139     
14140      <p><a name="psl"></a><b>psl</b></p>
14141
14142
14143
14144
14145
14146      </td>
14147
14148
14149
14150
14151 <td style="vertical-align: top;">R (10)<br>
14152
14153
14154
14155
14156
14157      </td>
14158
14159
14160
14161
14162 <td style="vertical-align: top;"><i>10
14163* 0.0</i> </td>
14164
14165
14166
14167
14168 <td style="vertical-align: top;">Left
14169edge of a particle source
14170(in m). </td>
14171
14172
14173
14174
14175 </tr>
14176
14177
14178
14179
14180 <tr>
14181
14182
14183
14184
14185 <td style="vertical-align: top;"> 
14186     
14187     
14188     
14189     
14190      <p><a name="psn"></a><b>psn</b></p>
14191
14192
14193
14194
14195
14196      </td>
14197
14198
14199
14200
14201 <td style="vertical-align: top;">R (10)<br>
14202
14203
14204
14205
14206
14207      </td>
14208
14209
14210
14211
14212 <td style="vertical-align: top;"><i>10
14213* (ny * dy)</i> </td>
14214
14215
14216
14217
14218 <td style="vertical-align: top;">Rear
14219(&#8220;north&#8221;) edge of a
14220particle source (in m). </td>
14221
14222
14223
14224
14225 </tr>
14226
14227
14228
14229
14230 <tr>
14231
14232
14233
14234
14235 <td style="vertical-align: top;"> 
14236     
14237     
14238     
14239     
14240      <p><a name="psr"></a><b>psr</b></p>
14241
14242
14243
14244
14245
14246      </td>
14247
14248
14249
14250
14251 <td style="vertical-align: top;">R (10)<br>
14252
14253
14254
14255
14256
14257      </td>
14258
14259
14260
14261
14262 <td style="vertical-align: top;"><i>10
14263* (nx * dx)</i> </td>
14264
14265
14266
14267
14268 <td style="vertical-align: top;">Right
14269edge of a particle
14270source (in m). </td>
14271
14272
14273
14274
14275 </tr>
14276
14277
14278
14279
14280 <tr>
14281
14282
14283
14284
14285 <td style="vertical-align: top;"> 
14286     
14287     
14288     
14289     
14290      <p><a name="pss"></a><b>pss</b></p>
14291
14292
14293
14294
14295
14296      </td>
14297
14298
14299
14300
14301 <td style="vertical-align: top;">R (10)<br>
14302
14303
14304
14305
14306
14307      </td>
14308
14309
14310
14311
14312 <td style="vertical-align: top;"><i>10
14313* 0.0</i> </td>
14314
14315
14316
14317
14318 <td style="vertical-align: top;">Front
14319(&#8220;south&#8221;) edge of a
14320particle source (in m). </td>
14321
14322
14323
14324
14325 </tr>
14326
14327
14328
14329
14330 <tr>
14331
14332
14333
14334
14335 <td style="vertical-align: top;"> 
14336     
14337     
14338     
14339     
14340      <p><a name="pst"></a><b>pst</b></p>
14341
14342
14343
14344
14345
14346      </td>
14347
14348
14349
14350
14351 <td style="vertical-align: top;">R (10)<br>
14352
14353
14354
14355
14356
14357      </td>
14358
14359
14360
14361
14362 <td style="vertical-align: top;"><i>10
14363* zu(nz/2)</i> </td>
14364
14365
14366
14367
14368 <td style="vertical-align: top;">Top
14369edge of a particle source
14370(in m). </td>
14371
14372
14373
14374
14375 </tr>
14376
14377
14378
14379
14380 <tr>
14381
14382
14383
14384
14385 <td style="vertical-align: top;"> 
14386     
14387     
14388     
14389     
14390      <p><a name="radius"></a><b>radius</b></p>
14391
14392
14393
14394
14395
14396      </td>
14397
14398
14399
14400
14401 <td style="vertical-align: top;">R (10)</td>
14402
14403
14404
14405
14406
14407      <td style="vertical-align: top;"><i>0.0, 9</i>*<br>
14408
14409
14410
14411
14412
14413      <i>9999999.9</i></td>
14414
14415
14416
14417
14418 <td style="vertical-align: top;">Particle radius (in m).<br>
14419
14420
14421
14422
14423
14424      <br>
14425
14426
14427
14428
14429The viscous friction (in case of a velocity difference
14430between
14431particles and surrounding fluid) depends on the particle radius which
14432must be assigned as soon as <a href="chapter_4.2.html#density_ratio">density_ratio</a>
14433/= <i>0.0</i>.<br>
14434
14435
14436
14437
14438 <br>
14439
14440
14441
14442
14443
14444With several groups of particles (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
14445each group can be assigned a different value. If the number of values
14446given for <span style="font-weight: bold;">radius</span>
14447is less than the number of
14448groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
14449then the last assigned value is used for all remaining groups. This
14450means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br>
14451
14452
14453
14454
14455 </td>
14456
14457
14458
14459
14460
14461    </tr>
14462
14463
14464
14465
14466    <tr>
14467
14468
14469
14470
14471 <td style="vertical-align: top;"> 
14472     
14473     
14474     
14475     
14476      <p><a name="random_start_position"></a><b>random_start_position</b></p>
14477
14478
14479
14480
14481
14482      </td>
14483
14484
14485
14486
14487 <td style="vertical-align: top;">L<br>
14488
14489
14490
14491
14492 </td>
14493
14494
14495
14496
14497
14498      <td style="vertical-align: top;"><i>.F.</i> </td>
14499
14500
14501
14502
14503
14504      <td style="vertical-align: top;"> 
14505     
14506     
14507     
14508     
14509      <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"><font color="#000000">Initial position of the</font></span>
14510particles is
14511varied randomly within certain limits.&nbsp; </p>
14512
14513
14514
14515
14516 
14517     
14518     
14519     
14520     
14521      <p>By
14522default, the initial positions of particles within the
14523source excatly correspond with the positions given by <a href="#psl">psl</a>,
14524      <a href="#psr">psr</a>, <a href="#psn">psn</a>,
14525      <a href="#pss">pss</a>, <a href="#psb">psb</a>,
14526      <a href="#pst">pst</a>, <a href="#pdx">pdx</a>,
14527      <a href="#pdy">pdy</a>,
14528and<a href="#pdz">
14529pdz</a>. With <b>random_start_position</b> = <i>.T.
14530      </i>the initial
14531positions of the particles are allowed to randomly vary from these
14532positions within certain limits.&nbsp; </p>
14533
14534
14535
14536
14537 
14538     
14539     
14540     
14541     
14542      <p><b>Very
14543important:<br>
14544
14545
14546
14547
14548 </b>In case of <b>random_start_position</b>
14549= <i>.T.</i>, the
14550random-number generators on the individual PEs no longer&nbsp;
14551run synchronously. If random disturbances are applied to the velocity
14552field
14553(see <a href="#create_disturbances">create_disturbances</a>),
14554      <font color="#000000">then as consequence for parallel
14555runs the
14556realizations of the turbulent flow
14557fields will deviate between runs which used different numbers of PEs!</font></p>
14558
14559
14560
14561
14562
14563      </td>
14564
14565
14566
14567
14568 </tr>
14569
14570
14571
14572
14573 <tr>
14574
14575
14576
14577
14578 <td style="vertical-align: top;"> 
14579     
14580     
14581     
14582     
14583      <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b>
14584      <br>
14585
14586
14587
14588
14589 <b>restartfile</b></p>
14590
14591
14592
14593
14594 </td>
14595
14596
14597
14598
14599 <td style="vertical-align: top;">L<br>
14600
14601
14602
14603
14604 </td>
14605
14606
14607
14608
14609 <td style="vertical-align: top;"><i>.T.</i> </td>
14610
14611
14612
14613
14614
14615      <td style="vertical-align: top;"> 
14616     
14617     
14618     
14619     
14620      <p>Read particle
14621data from the previous run.&nbsp; </p>
14622
14623
14624
14625
14626 
14627     
14628     
14629     
14630     
14631      <p>By default,
14632with restart runs particle data is read
14633from file <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
14634which is created by the preceding run. If this is not requested or if
14635in a restart run particle transport is switched on for the
14636first time (see <a href="#particle_advection_start">particle_advection_start</a>),
14637then <b>read_particles_from_restartfile</b> = <i>.F.</i>
14638is required.</p>
14639
14640
14641
14642
14643 </td>
14644
14645
14646
14647
14648 </tr>
14649
14650
14651
14652
14653 <tr>
14654
14655
14656
14657
14658 <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br>
14659
14660
14661
14662
14663
14664      </td>
14665
14666
14667
14668
14669 <td style="vertical-align: top;">I<br>
14670
14671
14672
14673
14674 </td>
14675
14676
14677
14678
14679
14680      <td style="vertical-align: top;"><span style="font-style: italic;">100</span><br>
14681
14682
14683
14684
14685 </td>
14686
14687
14688
14689
14690
14691      <td style="vertical-align: top;">Limit the number of
14692particle tails.<br>
14693
14694
14695
14696
14697 <br>
14698
14699
14700
14701
14702
14703If particle tails are switched on (see <a href="#use_particle_tails">use_particle_tails</a>),
14704every particle is given a tail by default. <span style="font-weight: bold;">skip_particles_for_tail </span>can
14705be used to give only every n'th particle a tail.<br>
14706
14707
14708
14709
14710 <br>
14711
14712
14713
14714
14715 <span style="font-weight: bold;">Example:</span><br>
14716
14717
14718
14719
14720 <span style="font-weight: bold;">skip_particles_for_tail</span>
14721= <span style="font-style: italic;">10</span> means
14722that only every 10th particle will be given a tail.<br>
14723
14724
14725
14726
14727 </td>
14728
14729
14730
14731
14732
14733    </tr>
14734
14735
14736
14737
14738 <tr>
14739
14740
14741
14742
14743 <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</span><br>
14744
14745
14746
14747
14748
14749      </td>
14750
14751
14752
14753
14754 <td style="vertical-align: top;">L<br>
14755
14756
14757
14758
14759 </td>
14760
14761
14762
14763
14764
14765      <td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br>
14766
14767
14768
14769
14770 </td>
14771
14772
14773
14774
14775
14776      <td style="vertical-align: top;">Give particles a tail.<br>
14777
14778
14779
14780
14781
14782      <br>
14783
14784
14785
14786
14787A particle tail is defined by the path a particle has moved
14788along starting from some point of time in the past. It consists of a
14789set of descrete points in space which may e.g. be connected by a line
14790in order visualize how the particle has moved.<br>
14791
14792
14793
14794
14795 <br>
14796
14797
14798
14799
14800
14801By default, particles have no tail. Parameter&nbsp;<a href="#skip_particles_for_tail">skip_particles_for_tail</a>
14802can be used to give only every n'th particle a tail.<br>
14803
14804
14805
14806
14807 <br>
14808
14809
14810
14811
14812
14813The length of the tail is controlled by parameters&nbsp;<a href="#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>,&nbsp;<a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>,
14814and <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.<br>
14815
14816
14817
14818
14819
14820      </td>
14821
14822
14823
14824
14825 </tr>
14826
14827
14828
14829
14830    <tr>
14831
14832
14833
14834
14835      <td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</span></td>
14836
14837
14838
14839
14840      <td align="left" valign="top">L</td>
14841
14842
14843
14844
14845      <td align="left" valign="top"><span style="font-style: italic;">.F.</span></td>
14846
14847
14848
14849
14850      <td align="left" valign="top">Use subgrid-scale
14851velocities for particle advection.<br>
14852
14853
14854
14855
14856      <br>
14857
14858
14859
14860
14861These
14862velocities are calculated from the resolved and subgrid-scale TKE using
14863the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
1486461,
148652877-2887). When using this method, the timestep for the advancement of
14866the particles is limited by the so-called Lagrangian time scale. This
14867may be smaller than the current LES timestep so that several particle
14868(sub-) timesteps have to be carried out within one LES timestep. In
14869order to limit the number of sub-timesteps (and to limit the CPU-time),
14870the minimum value for the particle timestep is defined by the package
14871parameter <a href="#dt_min_part">dt_min_part</a>.<br>
14872
14873
14874
14875
14876      <br>
14877
14878
14879
14880
14881Setting
14882      <span style="font-weight: bold;">use_sgs_for_particles</span>
14883= <span style="font-style: italic;">.TRUE.</span>
14884automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>
14885= <span style="font-style: italic;">.TRUE.</span>.
14886This inhibits the occurrence of large (artificial) spatial gradients of
14887the subgrid-scale TKE which otherwise would lead to wrong results for
14888the particle advection.</td>
14889
14890
14891
14892
14893    </tr>
14894
14895
14896
14897
14898    <tr>
14899
14900
14901
14902
14903 <td style="vertical-align: top;"> 
14904     
14905     
14906     
14907     
14908      <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b>
14909      <br>
14910
14911
14912
14913
14914 <b>advection</b></p>
14915
14916
14917
14918
14919 </td>
14920
14921
14922
14923
14924 <td style="vertical-align: top;">L<br>
14925
14926
14927
14928
14929 </td>
14930
14931
14932
14933
14934 <td style="vertical-align: top;"><i>.T.</i> </td>
14935
14936
14937
14938
14939
14940      <td style="vertical-align: top;"> 
14941     
14942     
14943     
14944     
14945      <p>Switch on/off
14946vertical particle transport. </p>
14947
14948
14949
14950
14951 
14952     
14953     
14954     
14955     
14956      <p>By default,
14957particles are transported along all three
14958directions in space. With <b>vertical_particle_advection</b>
14959= <i>.F., </i>the
14960particles will only be transported horizontally.</p>
14961
14962
14963
14964
14965 </td>
14966
14967
14968
14969
14970
14971    </tr>
14972
14973
14974
14975
14976 <tr>
14977
14978
14979
14980
14981 <td style="vertical-align: top;">
14982     
14983     
14984     
14985     
14986      <p><a name="write_particle_statistics"></a><b>write_particle_</b>
14987      <br>
14988
14989
14990
14991
14992 <b>statistics</b></p>
14993
14994
14995
14996
14997 </td>
14998
14999
15000
15001
15002 <td style="vertical-align: top;">L<br>
15003
15004
15005
15006
15007 </td>
15008
15009
15010
15011
15012 <td style="vertical-align: top;"><i>.F.</i> </td>
15013
15014
15015
15016
15017
15018      <td style="vertical-align: top;"> 
15019     
15020     
15021     
15022     
15023      <p>Switch on/off
15024output of particle informations.<br>
15025
15026
15027
15028
15029 </p>
15030
15031
15032
15033
15034 
15035     
15036     
15037     
15038     
15039      <p><br>
15040
15041
15042
15043
15044
15045For <span style="font-weight: bold;">write_particle_statistics</span>
15046= <span style="font-style: italic;">.T.</span> s<span style="font-family: thorndale,serif;">tatistical
15047informations</span> (e.g. the total number of particles used, the
15048number of particles exchanged between the PEs, etc.) which may be used
15049for debugging are output to the
15050local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>.&nbsp;
15051      </p>
15052
15053
15054
15055
15056 
15057     
15058     
15059     
15060     
15061      <p><b>Note:</b> For parallel runs files
15062may become very large
15063and performance of PALM may decrease.</p>
15064
15065
15066
15067
15068 </td>
15069
15070
15071
15072
15073 </tr>
15074
15075
15076
15077
15078
15079 
15080 
15081 
15082 
15083  </tbody>
15084</table>
15085
15086
15087
15088
15089<span style="font-weight: bold;"><br>
15090
15091
15092
15093
15094
15095</span><br>
15096
15097
15098
15099
15100<h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
15101parameters: </h3>
15102
15103
15104
15105
15106<br>
15107
15108
15109
15110
15111<span style="font-weight: bold;">Package
15112(<span style="font-weight: bold;">mrun</span> option
15113-p): <span style="font-weight: bold;"><a name="dvrp_graphics"></a>dvrp_graphics</span>
15114&nbsp;&nbsp;&nbsp;
15115NAMELIST group name: <span style="font-weight: bold;">dvrp_graphics_par<br>
15116
15117
15118
15119
15120
15121<br>
15122
15123
15124
15125
15126</span></span>
15127<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
15128
15129
15130
15131
15132 <tbody>
15133
15134
15135
15136
15137 <tr>
15138
15139
15140
15141
15142
15143      <td style="vertical-align: top;"><font size="4"><b>Parameter
15144name</b></font></td>
15145
15146
15147
15148
15149 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
15150
15151
15152
15153
15154
15155      <td style="vertical-align: top;"> 
15156     
15157     
15158     
15159     
15160      <p><b><font size="4">Default</font></b> <br>
15161
15162
15163
15164
15165 <b><font size="4">value</font></b></p>
15166
15167
15168
15169
15170 </td>
15171
15172
15173
15174
15175
15176      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
15177
15178
15179
15180
15181
15182    </tr>
15183
15184
15185
15186
15187 <tr>
15188
15189      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="clip_dvrp_l"></a>clip_dvrp_l</span></td>
15190
15191      <td style="vertical-align: top;">R</td>
15192
15193      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
15194
15195      <td style="vertical-align: top;">Left boundary of the displayed domain (in m).<br>
15196
15197      <br>
15198
15199This
15200parameter can be used to restrict the display of the total horizontal
15201domain, e.g. to reduce the data size of the dvr-output in order to
15202speed-up&nbsp;the animated sequence.</td>
15203
15204    </tr>
15205
15206    <tr>
15207
15208      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="clip_dvrp_n"></a>clip_dvrp_n</span></td>
15209
15210      <td style="vertical-align: top;">R</td>
15211
15212      <td style="vertical-align: top;"><span style="font-style: italic;">(<a href="chapter_4.1.html#ny">ny</a>+1)*<a href="chapter_4.1.html#dy">dy</a></span></td>
15213
15214      <td style="vertical-align: top;">North boundary of the displayed domain (in m).<br>
15215
15216      <br>
15217
15218This parameter can
15219be used to restrict the display of the total horizontal domain, e.g. to
15220reduce the data size of the dvr-output in order to speed-up&nbsp;the
15221animated sequence.</td>
15222
15223    </tr>
15224
15225    <tr>
15226
15227      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="clip_dvrp_r"></a>clip_dvrp_r</span></td>
15228
15229      <td style="vertical-align: top;">R</td>
15230
15231      <td style="vertical-align: top;"><span style="font-style: italic;">(<a href="chapter_4.1.html#nx">nx</a>+1)*<a href="chapter_4.1.html#dx">dx</a></span></td>
15232
15233      <td style="vertical-align: top;">Right boundary of the displayed domain (in m).<br>
15234
15235      <br>
15236
15237This parameter can
15238be used to restrict the display of the total horizontal domain, e.g. to
15239reduce the data size of the dvr-output in order to speed-up&nbsp;the
15240animated sequence.</td>
15241
15242    </tr>
15243
15244    <tr>
15245
15246      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="clip_dvrp_s"></a>clip_dvrp_s</span></td>
15247
15248      <td style="vertical-align: top;">R</td>
15249
15250      <td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td>
15251
15252      <td style="vertical-align: top;">South boundary of the displayed domain (in m).<br>
15253
15254      <br>
15255
15256This parameter can
15257be used to restrict the display of the total horizontal domain, e.g. to
15258reduce the data size of the dvr-output in order to speed-up&nbsp;the
15259animated sequence.</td>
15260
15261    </tr>
15262
15263    <tr>
15264
15265      <td style="vertical-align: top;"><a name="cluster_size"></a><span style="font-weight: bold;">cluster_size</span></td>
15266
15267      <td style="vertical-align: top;">I</td>
15268
15269      <td style="vertical-align: top;"><span style="font-style: italic;">1</span></td>
15270
15271      <td>Vertex cluster size for polygon reduction of topography.<br>
15272
15273      <br>
15274
15275This
15276parameter can be used to reduce the number of polygones which form the
15277topography isosurface. In case of large numerical grids (large number
15278of gridpoints) and /or complex topography, cluster_size &gt; 1 may
15279speed up the animation significantly. Disadvantage: buildings may loose
15280their strict rectangular shape.<br>
15281
15282      <br>
15283
15284The allowed range of values is 1 &lt;= <span style="font-weight: bold;">cluster_size</span> &lt;= 5.<br>
15285
15286      <br>
15287
15288 <span style="font-weight: bold;">Warning:</span> The allowed range of values is not checked. Wrong values may lead to unforseen effects or even aborts! </td>
15289
15290    </tr>
15291
15292    <tr>
15293
15294      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="color_interval"></a>color_interval</span></td>
15295
15296      <td style="vertical-align: top;">R(2)</td>
15297
15298      <td style="vertical-align: top;"><span style="font-style: italic;">0.0, 1.0</span></td>
15299
15300      <td style="vertical-align: top;">Interval of values used for determining the particle color displayed in the animation.<br>
15301
15302      <br>
15303
15304See <a href="#particle_color">particle_color</a> for further explanation.</td>
15305
15306    </tr>
15307
15308    <tr>
15309
15310
15311
15312
15313 <td style="vertical-align: top;">
15314     
15315     
15316     
15317     
15318      <p><a name="dt_dvrp"></a><b>dt_dvrp</b></p>
15319
15320
15321
15322
15323
15324      </td>
15325
15326
15327
15328
15329 <td style="vertical-align: top;">R</td>
15330
15331
15332
15333
15334
15335      <td style="vertical-align: top;"><i>9999999.9</i></td>
15336
15337
15338
15339
15340
15341      <td style="vertical-align: top;"> 
15342     
15343     
15344     
15345     
15346      <p>Temporal
15347interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
15348s).&nbsp; </p>
15349
15350
15351
15352
15353 
15354     
15355     
15356     
15357     
15358      <p>Isosurfaces, cross sections and
15359particles can be displayed
15360simultaneous. The display of particles requires that the particle
15361transport is switched on (see <a href="#dt_prel">dt_prel</a>).
15362Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p>
15363
15364
15365
15366
15367 
15368     
15369     
15370     
15371     
15372      <p>If
15373output of scenes created by dvrp software is switched on
15374(see <a href="#mode_dvrp">mode_dvrp</a>),
15375this parameter can be used to assign the temporal interval at which
15376scenes are to be created (and the respective&nbsp; graphical data
15377is to
15378be output to the streaming server). <span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
15379&nbsp;the simulation, i.e. output takes place at times t = <b>dt_dvrp</b>,
153802*<b>dt_dvrp</b>, 3*<b>dt_dvrp</b>, etc. The
15381actual output times can
15382deviate 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;
15383Is <b>dt_dvrp</b> &lt; </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then
15384scenes are created and
15385output after each time step (if this is requested it should be <b>dt_dvrp</b>
15386= <i>0</i>).</font></span> </p>
15387
15388
15389
15390
15391 </td>
15392
15393
15394
15395
15396
15397    </tr>
15398
15399
15400
15401
15402 <tr>
15403
15404      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="dvrpsize_interval"></a>dvrpsize_interval</span></td>
15405
15406      <td style="vertical-align: top;">R(2)</td>
15407
15408      <td style="vertical-align: top;"><span style="font-style: italic;">0.0, 1.0</span></td>
15409
15410      <td style="vertical-align: top;">Interval of values used for determining the particle size displayed in the animation.<br>
15411
15412      <br>
15413
15414See <a href="#particle_dvrpsize">particle_dvrpsize</a> for further explanation.</td>
15415
15416    </tr>
15417
15418    <tr>
15419
15420
15421
15422
15423 <td style="vertical-align: top;">
15424     
15425     
15426     
15427     
15428      <p><a name="dvrp_directory"></a><b>dvrp_directory</b></p>
15429
15430
15431
15432
15433
15434      </td>
15435
15436
15437
15438
15439 <td style="vertical-align: top;">C*80</td>
15440
15441
15442
15443
15444
15445      <td style="vertical-align: top;"><i>'default'</i></td>
15446
15447
15448
15449
15450
15451      <td style="vertical-align: top;"> 
15452     
15453     
15454     
15455     
15456      <p>Name of the
15457directory into which data created by the <span style="font-weight: bold;">dvrp</span>
15458software shall be saved.&nbsp; </p>
15459
15460
15461
15462
15463 
15464     
15465     
15466     
15467     
15468      <p>By default,
15469the directory name is generated from the user
15470name
15471(see package parameter <a href="#dvrp_username">dvrp_username</a>)
15472and the base file name (given as the argument of <span style="font-weight: bold;">mrun</span> option -d) as <span style="font-style: italic;">'&lt;user
15473name&gt;/&lt;base file name&gt;'</span>.</p>
15474
15475
15476
15477
15478 </td>
15479
15480
15481
15482
15483
15484    </tr>
15485
15486
15487
15488
15489 <tr>
15490
15491
15492
15493
15494 <td style="vertical-align: top;">
15495     
15496     
15497     
15498     
15499      <p><a name="dvrp_file"></a><b>dvrp_file</b></p>
15500
15501
15502
15503
15504
15505      </td>
15506
15507
15508
15509
15510 <td style="vertical-align: top;">C*80</td>
15511
15512
15513
15514
15515
15516      <td style="vertical-align: top;"><i>'default'</i></td>
15517
15518
15519
15520
15521
15522      <td style="vertical-align: top;"> 
15523     
15524     
15525     
15526     
15527      <p>Name of the
15528file into which data created by the <span style="font-weight: bold;">dvrp</span>
15529software shall be output.&nbsp; </p>
15530
15531
15532
15533
15534 
15535     
15536     
15537     
15538     
15539      <p>This
15540parameter can be given a value only in case of <a href="#dvrp_output">dvrp_output</a>
15541= <span style="font-style: italic;">'local'</span><i>
15542      </i>which
15543determines that the data created by <span style="font-weight: bold;">dvrp</span>
15544is output to a local file (on the machine where PALM is executed).
15545Apart from the default, it is only allowed to assign <span style="font-style: italic;">'/dev/null'</span> (which
15546means that no output is really stored). This can be used for special
15547runtime measurements of the <span style="font-weight: bold;">dvrp</span>
15548software.</p>
15549
15550
15551
15552
15553 </td>
15554
15555
15556
15557
15558 </tr>
15559
15560
15561
15562
15563 <tr>
15564
15565
15566
15567
15568 <td style="vertical-align: top;"> 
15569     
15570     
15571     
15572     
15573      <p><a name="dvrp_host"></a><b>dvrp_host</b></p>
15574
15575
15576
15577
15578
15579      </td>
15580
15581
15582
15583
15584 <td style="vertical-align: top;">C*80</td>
15585
15586
15587
15588
15589
15590      <td style="vertical-align: top;"> 
15591     
15592     
15593     
15594     
15595      <p><i>'origin.rvs.</i>
15596      <br>
15597
15598
15599
15600
15601u<i>ni- hanover.de'</i></p>
15602
15603
15604
15605
15606 </td>
15607
15608
15609
15610
15611 <td style="vertical-align: top;"> 
15612     
15613     
15614     
15615     
15616      <p>Name of the computer
15617to which data created by the <span style="font-weight: bold;">dvrp</span>
15618software shall be
15619transferred.&nbsp; </p>
15620
15621
15622
15623
15624 
15625     
15626     
15627     
15628     
15629      <p>In case of <a href="#dvrp_output">dvrp_output</a>
15630= <span style="font-style: italic;">'rtsp'</span>
15631only the default
15632value is allowed (streaming server of
15633the RRZN). For <a href="#dvrp_output">dvrp_output</a>
15634= <span style="font-style: italic;">'local'</span><i>
15635      </i>the
15636assigned value is ignored.</p>
15637
15638
15639
15640
15641 </td>
15642
15643
15644
15645
15646 </tr>
15647
15648
15649
15650
15651 <tr>
15652
15653
15654
15655
15656
15657      <td style="vertical-align: top;"> 
15658     
15659     
15660     
15661     
15662      <p><a name="dvrp_output"></a><b>dvrp_output</b></p>
15663
15664
15665
15666
15667
15668      </td>
15669
15670
15671
15672
15673 <td style="vertical-align: top;">C*10</td>
15674
15675
15676
15677
15678
15679      <td style="vertical-align: top;"><i>'rtsp'</i></td>
15680
15681
15682
15683
15684
15685      <td style="vertical-align: top;"> 
15686     
15687     
15688     
15689     
15690      <p>Output mode
15691for the <span style="font-weight: bold;">dvrp</span>
15692software. <br>
15693
15694
15695
15696
15697 <br>
15698
15699
15700
15701
15702 </p>
15703
15704
15705
15706
15707
15708The following settings are allowed:<br>
15709
15710
15711
15712
15713 <br>
15714
15715
15716
15717
15718 
15719     
15720     
15721     
15722     
15723      <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2">
15724
15725
15726
15727
15728 <tbody>
15729
15730
15731
15732
15733 <tr>
15734
15735
15736
15737
15738 <td style="vertical-align: top;"><i>'rtsp'</i></td>
15739
15740
15741
15742
15743
15744            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
15745software is transferred using
15746a special transmission protocol to a so-called streaming server, which
15747is able to continuously transfer visualization data with a
15748high transmission rate.&nbsp; <br>
15749
15750
15751
15752
15753
15754Additionally, with this output mode a
15755set of files is generated automatically
15756within a directory on the streaming server (beside the visualization
15757data e.g. some html-files) which can be used to
15758visualize the data via an internet-browser plugin. Host
15759(streaming-server) and directory can be defined by the user with <a href="#dvrp_host">dvrp_host</a>
15760and <a href="#dvrp_directory">dvrp_directory</a>.</td>
15761
15762
15763
15764
15765
15766          </tr>
15767
15768
15769
15770
15771 <tr>
15772
15773
15774
15775
15776 <td style="vertical-align: top;"><i>'ftp'</i></td>
15777
15778
15779
15780
15781
15782            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
15783software is transferred to the destination host (see <a href="#dvrp_host">dvrp_host</a>
15784and <a href="#dvrp_directory">dvrp_directory</a>)
15785using ftp.</td>
15786
15787
15788
15789
15790 </tr>
15791
15792
15793
15794
15795 <tr>
15796
15797
15798
15799
15800 <td style="vertical-align: top;"><i>'local'</i></td>
15801
15802
15803
15804
15805
15806            <td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
15807software is output locally on a file defined by <a href="#dvrp_file">dvrp_file
15808            </a>.</td>
15809
15810
15811
15812
15813 </tr>
15814
15815
15816
15817
15818 
15819       
15820       
15821       
15822       
15823        </tbody> 
15824     
15825     
15826     
15827     
15828      </table>
15829
15830
15831
15832
15833 <br>
15834
15835
15836
15837
15838
15839      </td>
15840
15841
15842
15843
15844 </tr>
15845
15846
15847
15848
15849 <tr>
15850
15851
15852
15853
15854 <td style="vertical-align: top;"> 
15855     
15856     
15857     
15858     
15859      <p><a name="dvrp_password"></a><b>dvrp_password</b></p>
15860
15861
15862
15863
15864
15865      </td>
15866
15867
15868
15869
15870 <td style="vertical-align: top;">C*80</td>
15871
15872
15873
15874
15875
15876      <td style="vertical-align: top;">'********'</td>
15877
15878
15879
15880
15881 <td style="vertical-align: top;"> 
15882     
15883     
15884     
15885     
15886      <p>Password for the
15887computer to which data created by the <span style="font-weight: bold;">dvrp</span> software is to
15888be
15889transferred.&nbsp; </p>
15890
15891
15892
15893
15894 
15895     
15896     
15897     
15898     
15899      <p>Assigning a password is
15900only necessary in case of <a href="#dvrp_output">dvrp_output</a>
15901= <span style="font-style: italic;">'ftp'</span>.
15902For <a href="#dvrp_output">dvrp_output</a>
15903= <span style="font-style: italic;">'rtsp'</span><i>
15904      </i>the default
15905value must not be changed!</p>
15906
15907
15908
15909
15910 </td>
15911
15912
15913
15914
15915 </tr>
15916
15917
15918
15919
15920 <tr>
15921
15922      <td style="vertical-align: top;">
15923     
15924      <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p>
15925
15926      </td>
15927
15928      <td style="vertical-align: top;">R</td>
15929
15930      <td style="vertical-align: top;"><span style="font-style: italic;">0.2 * <a href="chapter_4.1.html#dx">dx</a></span></td>
15931
15932      <td style="vertical-align: top;">
15933     
15934      <p>Diameter that particles are given in visualizations with
15935the <span style="font-weight: bold;">dvrp</span>
15936software (in
15937m).&nbsp; </p>
15938
15939
15940
15941
15942 
15943     
15944     
15945     
15946     
15947      <p>In case that particles are
15948visualized with the <span style="font-weight: bold;">dvrp</span>
15949software (see <a href="chapter_4.5.7.html">chapter
159504.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>.
15951All
15952particles are displayed with this same size.<br>
15953
15954
15955
15956
15957 </p>
15958
15959
15960
15961
15962 
15963     
15964     
15965     
15966     
15967      <p>Alternatively, the particle size can be controlled by certain flow parameters using parameter <a href="#particle_dvrpsize">particle_dvrpsize</a>.</p>
15968
15969     
15970      <p>Another way to control
15971the particles diameter is to set it with the
15972user-interface in routine <span style="font-family: monospace;">user_init_particles</span>
15973(at the beginning of the simulation) and/or to redefine it after each
15974timestep in routine <tt>user<font style="font-size: 11pt;" size="2">_particle_attributes</font></tt>.&nbsp;</p>
15975
15976
15977
15978
15979
15980     
15981     
15982     
15983     
15984      <p><b>Note:</b> This parameter determines exclusively
15985the size
15986under which particles appear in the <span style="font-weight: bold;">dvrp</span>
15987visualization. The flow relevant particle radius is determined via the
15988particle parameter <a href="chapter_4.2.html#radius">radius</a>!</p>
15989
15990      </td>
15991
15992    </tr>
15993
15994    <tr>
15995
15996
15997
15998
15999
16000      <td style="vertical-align: top;"> 
16001     
16002     
16003     
16004     
16005      <p><a name="dvrp_username"></a><b>dvrp_username</b></p>
16006
16007
16008
16009
16010
16011      </td>
16012
16013
16014
16015
16016 <td style="vertical-align: top;">C*80</td>
16017
16018
16019
16020
16021
16022      <td style="vertical-align: top;"><br>
16023
16024
16025
16026
16027 </td>
16028
16029
16030
16031
16032 <td style="vertical-align: top;"> 
16033     
16034     
16035     
16036     
16037      <p>User name of a valid
16038account on the computer to which data
16039created by the <span style="font-weight: bold;">dvrp</span>
16040software
16041is to be
16042transferred.&nbsp; </p>
16043
16044
16045
16046
16047 
16048     
16049     
16050     
16051     
16052      <p>Assigning a value to this
16053parameter is required in case of <a href="#dvrp_output">dvrp_output</a>
16054= <span style="font-style: italic;">'rtsp'</span>
16055or <span style="font-style: italic;">'ftp'</span>.</p>
16056
16057
16058
16059
16060
16061      </td>
16062
16063
16064
16065
16066 </tr>
16067
16068
16069
16070
16071 <tr>
16072
16073      <td style="vertical-align: top;"><a name="groundplate_color"></a><span style="font-weight: bold;">groundplate_color</span></td>
16074
16075      <td style="vertical-align: top;">R(3)</td>
16076
16077      <td style="vertical-align: top;"><span style="font-style: italic;">0.0, 0.6, 0.0</span></td>
16078
16079      <td style="vertical-align: top;">Color of the ground plate.<br>
16080
16081      <br>
16082
16083The color is given in RGB (red/green/blue) portions. The default color of the ground plate is green.</td>
16084
16085    </tr>
16086
16087    <tr>
16088
16089      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="isosurface_color"></a>isosurface_color</span></td>
16090
16091      <td style="vertical-align: top;">R(3,10)</td>
16092
16093      <td style="vertical-align: top;"><span style="font-style: italic;">0.9, 0.9, 0.9</span><br style="font-style: italic;">
16094
16095      <span style="font-style: italic;">0.8, 0.1, 0.1</span><br style="font-style: italic;">
16096
16097      <span style="font-style: italic;">0.1, 0.1, 0.8<br>
16098
160990.1, 0.8, 0.1<br>
16100
161010.6, 0.1, 0.1<br>
16102
161030.1, 0.1, 0.6<br>
16104
161050.1, 0.6, 0.1<br>
16106
161070.4, 0.1, 0.1<br>
16108
161090.1, 0.1, 0.4<br>
16110
161110.1, 0.4, 0.1</span></td>
16112
16113      <td style="vertical-align: top;">Color of the isosurface(s).<br>
16114
16115      <br>
16116
16117Colors
16118are given in RGB (red/green/blue) portions. By default, the first
16119isosurface has a gray color, the second a red color, the third a blue
16120color, etc.</td>
16121
16122    </tr>
16123
16124    <tr>
16125
16126
16127
16128
16129 <td style="vertical-align: top;"> 
16130     
16131     
16132     
16133     
16134      <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p>
16135
16136
16137
16138
16139
16140      </td>
16141
16142
16143
16144
16145 <td style="vertical-align: top;">C*20&nbsp;
16146      <br>
16147
16148
16149
16150
16151(10)</td>
16152
16153
16154
16155
16156 <td style="vertical-align: top;"><i>10
16157* ''</i></td>
16158
16159
16160
16161
16162 <td style="vertical-align: top;">
16163     
16164     
16165     
16166     
16167      <p>Graphical objects (isosurfaces, slicers, particles) which are
16168to be created by the <span style="font-weight: bold;">dvrp</span>
16169software.&nbsp; </p>
16170
16171
16172
16173
16174 
16175     
16176     
16177     
16178     
16179      <p>Several different objects can
16180be assigned simultaneously and
16181will be displayed in the same scene. Allowed values for <span style="font-weight: bold;">mode_dvrp</span> are <span style="font-style: italic;">'isosurface##'</span>
16182(isosurface), <span style="font-style: italic;">'slicer##'</span>
16183(cross sections), and <span style="font-style: italic;">'particles'</span>.
16184Within the strings the hash characters ("##") have to be replaced by two
16185digits 01&#8804;##&#8804;99. Up to 10 objects
16186can be assigned at the same time, e.g.:&nbsp; </p>
16187
16188
16189
16190
16191 
16192     
16193     
16194     
16195     
16196      <blockquote><b>mode_dvrp</b>
16197= <span style="font-style: italic;">'isosurface02'</span><i>,
16198'slicer01',
16199'particles', 'slicer02'</i></blockquote>
16200
16201
16202
16203
16204 
16205     
16206     
16207     
16208     
16209      <p>In this
16210case one isosurface, two cross sections, and particles
16211will be created. The quantities for which isosurfaces or cross sections are to be
16212created have to be selected with
16213the parameter <a href="#data_output">data_output</a> (<span style="font-weight: bold;">data_output</span>
16214also determines the
16215orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> <span style="font-weight: bold;"></span>lists of
16216variables may be
16217assigned, the digits at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string
16218select the quantity, which is given
16219at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface02'</span>
16220selects the second 3D quantity
16221of <span style="font-weight: bold;">data_output</span><span style="font-style: italic;">'slicer01'</span> selects the first 2D quantity
16222of <span style="font-weight: bold;">data_output</span>).
16223If e.g. <span style="font-weight: bold;">data_output</span> is assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
16224'w_xz', 'v_yz'</i>, <span style="font-style: italic;">'pt'</span><i>,
16225'u', 'w'</i>, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
16226isosurface of u, a
16227horizontal cross section of u and
16228a vertical cross section (xz) of w are created. For locations of the
16229cross sections see <a href="#data_output">data_output</a>.
16230The theshold value for which the isosurface is
16231to be created can be defined with parameter <a href="#threshold">threshold</a>. The isosurface color is controlled by parameter <a href="#isosurface_color">isosurface_color</a>.<br>
16232
16233
16234
16235
16236
16237      </p>
16238
16239
16240
16241
16242 
16243     
16244     
16245     
16246     
16247      <p>The particles color and size can be set using parameters <a href="#particle_color">particle_color</a> and <a href="#particle_dvrpsize">particle_dvrpsize</a>.</p>
16248
16249     
16250      <p>The vertical extension of the displayed domain is
16251given by <a href="#nz_do3d">nz_do3d</a>.</p>
16252
16253     
16254      <p>The displayed horizontal domain can be restricted using parameters <a href="#clip_dvrp_l">clip_dvrp_l</a>, <a href="#clip_dvrp_r">clip_dvrp_r</a>, <a href="#clip_dvrp_n">clip_dvrp_n</a>, <a href="#clip_dvrp_s">clip_dvrp_s</a>.</p>
16255
16256     
16257      <p>If user-defined dvrp objects exist (see <a href="chapter_3.5.4.html">chapter 3.5.4</a>), then&nbsp;<span style="font-weight: bold;">mode_dvrp</span> may also refer to quantities selected with the parameter&nbsp;<a href="chapter_4.3.html#data_output_user">data_output_user</a> (internally PALM appends them to those selected&nbsp;with
16258the parameter <a href="chapter_4.2.html#data_output">data_output</a>).
16259
16260
16261 </p>
16262
16263     
16264      <p><b>Assignments
16265of mode_dvrp must correspond to those of data_output
16266and
16267data_output_user! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>,<span style="font-style: italic;"> 'w'</span><i> </i>was set, then only the digits "01" are allowed
16268for <b>mode_dvrp</b>,
16269thus <span style="font-style: italic;">'isosurface01'</span>
16270and/or <span style="font-style: italic;">'slicer01'</span><i>.</i>
16271      </p>
16272
16273
16274
16275
16276 
16277     
16278     
16279     
16280     
16281      <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are
16282given in <a href="chapter_4.5.7.html">chapter
162834.5.7</a>.<br>
16284
16285
16286
16287
16288 </p>
16289
16290
16291
16292
16293 <b>Note:</b><br>
16294
16295
16296
16297
16298
16299The declaration of color charts to be
16300used still have to be given "manually" in subroutine <a href="chapter_3.4.html#user_dvrp_coltab"><span style="font-family: monospace;">user_dvrp_coltab</span></a>
16301(file <tt><font style="font-size: 11pt;" size="2">user_dvrp_coltab.f90</font></tt>).&nbsp;
16302
16303
16304      </td>
16305
16306
16307
16308
16309
16310    </tr>
16311
16312
16313
16314
16315 <tr>
16316
16317      <td style="vertical-align: top;"><a style="font-weight: bold;" name="particle_color"></a><span style="font-weight: bold;">particle_color</span></td>
16318
16319      <td style="vertical-align: top;">C*10</td>
16320
16321      <td style="vertical-align: top;"><span style="font-style: italic;">'none'</span></td>
16322
16323      <td style="vertical-align: top;">Parameter, which allows to bind the displayed particle color to certain flow quantities.<br>
16324
16325      <br>
16326
16327By default, particles have a black color.<br>
16328
16329      <br>
16330
16331Allowed values for <span style="font-weight: bold;">particle_color</span> are:<br>
16332
16333      <br>
16334
16335     
16336      <table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
16337
16338        <tbody>
16339
16340          <tr>
16341
16342            <td style="vertical-align: top;"><span style="font-style: italic;">'absuv'</span></td>
16343
16344            <td style="vertical-align: top;">Particle color depends on the absolute value of the resolved-scale horizontal velocity (SQRT(u<sup>2</sup>+v<sup>2</sup>) at the particle position.</td>
16345
16346          </tr>
16347
16348          <tr>
16349
16350            <td style="vertical-align: top;"><span style="font-style: italic;">'pt*'</span></td>
16351
16352            <td style="vertical-align: top;">Particle
16353color depends on the deviation of the resolved-scale potential
16354temperature at the particle position from the horizontally averaged
16355potential temperature (total domain).</td>
16356
16357          </tr>
16358
16359          <tr>
16360
16361            <td style="vertical-align: top;"><span style="font-style: italic;">'z'</span></td>
16362
16363            <td style="vertical-align: top;">Particle color depends on the height of the particle with respect to the bottom boundary (z=0).</td>
16364
16365          </tr>
16366
16367       
16368        </tbody>
16369     
16370      </table>
16371
16372      <br>
16373
16374The
16375colortable used for particles ranges from deep blue to deep red with
16376yellow in between. The interval of values from the above listed
16377quantities to be mapped to these colors is defined by parameter <a href="#color_interval">color_interval</a>.<br>
16378
16379      <br>
16380
16381      <span style="font-weight: bold;">Example:<br>
16382
16383      </span>If <span style="font-weight: bold;">particle_color</span> = <span style="font-style: italic;">'pt*'</span> and <a href="#color_interval">color_interval</a> = <span style="font-style: italic;">-0.5</span>, <span style="font-style: italic;">+0.5</span>, then all particles at positions with <span style="font-style: italic;">pt* </span>&lt;=<span style="font-style: italic;"> -0.5 K</span> will have a deep blue color and those at positions with <span style="font-style: italic;">pt*</span> &gt;= <span style="font-style: italic;">+0.5 K</span> will have a deep red color, while those with <span style="font-style: italic;">-0.5</span> &lt; <span style="font-style: italic;">pt*</span> &lt; <span style="font-style: italic;">+0.5</span> will vary in color from deep blue to deep red and transition from yellow to blue indicate <span style="font-style: italic;">pt*</span> ~ <span style="font-style: italic;">0.0</span>.</td>
16384
16385    </tr>
16386
16387    <tr>
16388
16389      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="particle_dvrpsize"></a>particle_dvrpsize</span></td>
16390
16391      <td style="vertical-align: top;">C*10</td>
16392
16393      <td style="vertical-align: top;"><span style="font-style: italic;">'none'</span></td>
16394
16395      <td style="vertical-align: top;">Parameter, which allows to bind the displayed particle size to certain flow quantities.<br>
16396
16397      <br>
16398
16399The default particle size (diameter) is determined with parameter <a href="#dvrp_psize">dvrp_psize</a>.<br>
16400
16401      <br>
16402
16403Allowed values for <span style="font-weight: bold;">particle_dvrpsize</span> are:<br>
16404
16405     
16406      <table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
16407
16408        <tbody>
16409
16410          <tr>
16411
16412            <td style="vertical-align: top;"><span style="font-style: italic;">'absw'</span></td>
16413
16414            <td style="vertical-align: top;">The particle size depends on the absolute value of the resolved-scale vertical velocity w at the particle position.</td>
16415
16416          </tr>
16417
16418       
16419        </tbody>
16420     
16421      </table>
16422
16423      <br>
16424
16425The particle sizes ranges from 0.25*<a href="chapter_4.1.html#dx">dx</a> m to 0.85*<a href="chapter_4.1.html#dx">dx</a> m. The interval of values from the above listed quantities to be mapped to these sizes is defined by parameter <a href="#dvrpsize_interval">dvrpsize_interval</a>.<br>
16426
16427      <br>
16428
16429      <span style="font-weight: bold;">Example:</span><br>
16430
16431If <span style="font-weight: bold;">particle_dvrpsize</span> = <span style="font-style: italic;">'absw'</span> and <a href="#dvrpsize_interval">dvrpsize_interval</a> = <span style="font-style: italic;">1.0</span>, <span style="font-style: italic;">2.0</span>, then all particles at positions where the absolute value of w is &lt;= <span style="font-style: italic;">1.0</span> m/s will have a size of <span style="font-style: italic;">0.25*dx</span> m and those at positions with |w| &gt;= <span style="font-style: italic;">2.0</span> m/s will have a size of <span style="font-style: italic;">0.85*dx</span> m, while those with <span style="font-style: italic;">1.0</span> m/s &lt; |w| &lt; <span style="font-style: italic;">2.0</span> m/s will linearly vary in size from <span style="font-style: italic;">0.25*dx</span> m to <span style="font-style: italic;">0.85*dx</span> m.</td>
16432
16433    </tr>
16434
16435    <tr>
16436
16437
16438
16439
16440 <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br>
16441
16442
16443
16444
16445
16446dvrp</span></td>
16447
16448
16449
16450
16451 <td style="vertical-align: top;">R(2,10)</td>
16452
16453
16454
16455
16456
16457      <td style="vertical-align: top;"><span style="font-style: italic;">10
16458* (-1,1)</span></td>
16459
16460
16461
16462
16463 <td style="vertical-align: top;">Ranges
16464of values to which a color table has to be mapped (units of the
16465respective quantity).<br>
16466
16467
16468
16469
16470 <br>
16471
16472
16473
16474
16475
16476In case that slicers have to be displayed (see <a href="#threshold">mode_dvrp</a>),
16477this parameter defines the ranges of values of the respective
16478quantities to which the colortable in use has to be mapped. If e.g. a
16479temperature slice shall be displayed, the colortable defines colors
16480from blue to red, and <span style="font-weight: bold;">slicer_range_limits_dvrp</span>
16481= 290.0, 305.0 then areas with temperature of 290 K are displayed in
16482dark blue and those with 305.0 are displayed in dark red. Temperatures
16483within these limits will be displayed by a continuous color gradient
16484from blue to red and Temperatures outside the limits will
16485be displayed either in dark blue or in dark red.<br>
16486
16487
16488
16489
16490 <br>
16491
16492
16493
16494
16495
16496Up to ten different ranges can be assigned in case that more than one
16497slicer has to be displayed.<br>
16498
16499
16500
16501
16502 <br>
16503
16504
16505
16506
16507
16508See <a href="#threshold">mode_dvrp</a>
16509for the declaration of color charts.</td>
16510
16511
16512
16513
16514 </tr>
16515
16516
16517
16518
16519 <tr>
16520
16521
16522
16523
16524
16525      <td style="vertical-align: top;"> 
16526     
16527     
16528     
16529     
16530      <p><a name="superelevation"></a><b>superelevation</b></p>
16531
16532
16533
16534
16535
16536      </td>
16537
16538
16539
16540
16541 <td style="vertical-align: top;">R</td>
16542
16543
16544
16545
16546
16547      <td style="vertical-align: top;"><i>1.0</i></td>
16548
16549
16550
16551
16552
16553      <td style="vertical-align: top;"> 
16554     
16555     
16556     
16557     
16558      <p>Superelevation
16559factor for the vertical coordinate.&nbsp; </p>
16560
16561
16562
16563
16564 
16565     
16566     
16567     
16568     
16569      <p>For
16570domains with unfavorable ratio between the vertical and
16571the horizontal size
16572(the vertical size is determined by <a href="#nz_do3d">nz_do3d</a>)
16573a <span style="font-weight: bold;">superelevation</span>
16574/= <span style="font-style: italic;">1.0</span> may
16575be used. If e.g. the
16576horizontal size is substantially larger
16577than the vertical size, a <span style="font-weight: bold;">superelevation</span>
16578much larger than <span style="font-style: italic;">1.0</span>
16579should
16580be used, since otherwise the domain appears as a
16581"flat disk" in the visualization and thus the vertical direction is
16582only very poorly resolved.</p>
16583
16584
16585
16586
16587 </td>
16588
16589
16590
16591
16592 </tr>
16593
16594
16595
16596
16597 <tr>
16598
16599
16600
16601
16602
16603      <td style="vertical-align: top;"> 
16604     
16605     
16606     
16607     
16608      <p><a name="superelevation_x"></a><b>superelevation_x</b></p>
16609
16610
16611
16612
16613
16614      </td>
16615
16616
16617
16618
16619 <td style="vertical-align: top;">R<br>
16620
16621
16622
16623
16624 </td>
16625
16626
16627
16628
16629
16630      <td style="vertical-align: top; font-style: italic;">1.0<br>
16631
16632
16633
16634
16635
16636      </td>
16637
16638
16639
16640
16641 <td style="vertical-align: top;"> 
16642     
16643     
16644     
16645     
16646      <p>Superelevation
16647factor for the horizontal (x) coordinate.&nbsp; </p>
16648
16649
16650
16651
16652 
16653     
16654     
16655     
16656     
16657      <p>This
16658parameter can be used to stretch the displayed domain
16659along the x-direction. See also <a href="#superelevation">superelevation</a>.</p>
16660
16661
16662
16663
16664
16665      </td>
16666
16667
16668
16669
16670 </tr>
16671
16672
16673
16674
16675 <tr>
16676
16677
16678
16679
16680 <td style="vertical-align: top;"> 
16681     
16682     
16683     
16684     
16685      <p><a name="superelevation_y"></a><b>superelevation_y</b></p>
16686
16687
16688
16689
16690
16691      </td>
16692
16693
16694
16695
16696 <td style="vertical-align: top;">R<br>
16697
16698
16699
16700
16701 </td>
16702
16703
16704
16705
16706
16707      <td style="vertical-align: top; font-style: italic;">1.0<br>
16708
16709
16710
16711
16712
16713      </td>
16714
16715
16716
16717
16718 <td style="vertical-align: top;">Superelevation
16719factor for the
16720horizontal (y) coordinate.&nbsp; 
16721     
16722     
16723     
16724     
16725      <p>This parameter can be
16726used to
16727stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p>
16728
16729
16730
16731
16732 </td>
16733
16734
16735
16736
16737
16738    </tr>
16739
16740
16741
16742
16743 <tr>
16744
16745
16746
16747
16748 <td style="vertical-align: top;">
16749     
16750     
16751     
16752     
16753      <p><a name="threshold"></a><b>threshold</b></p>
16754
16755
16756
16757
16758
16759      </td>
16760
16761
16762
16763
16764 <td style="vertical-align: top;">R(10)<br>
16765
16766
16767
16768
16769
16770      </td>
16771
16772
16773
16774
16775 <td style="vertical-align: top; font-style: italic;">0.0<br>
16776
16777
16778
16779
16780
16781      </td>
16782
16783
16784
16785
16786 <td style="vertical-align: top;"> 
16787     
16788     
16789     
16790     
16791      <p>Threshold
16792value for which an isosurface is to be created by
16793the <span style="font-weight: bold;">dvrp</span>
16794software.&nbsp; </p>
16795
16796
16797
16798
16799 
16800     
16801     
16802     
16803     
16804      <p>If the creation of
16805isosurfaces is switched on via
16806parameter <a href="#mode_dvrp">mode_dvrp</a>,
16807then the respective threshold value for which the isosurface is to be
16808created can be assigned via <b>threshold</b>. If several
16809isosurfaces
16810are given by <b>mode_dvrp</b>, then an individual
16811threshold value for
16812each isosurface can be assigned. The order of the threshold values
16813refers to the order of the isosurfaces given by <b>mode_dvrp</b>.</p>
16814
16815
16816
16817
16818
16819      </td>
16820
16821
16822
16823
16824 </tr>
16825
16826    <tr>
16827
16828      <td style="vertical-align: top;"><span style="font-weight: bold;"><a name="topography_color"></a>topography_color</span></td>
16829
16830      <td style="vertical-align: top;">R(3)</td>
16831
16832      <td style="vertical-align: top;"><span style="font-style: italic;">0.8, 0.7, 0.6</span></td>
16833
16834      <td style="vertical-align: top;">Color of the topography.<br>
16835
16836      <br>
16837
16838The color is given in RGB (red/green/blue) portions. If topograpy is switched on (see <a href="chapter_4.1.html#topography">topography</a>), its default color is a kind of gray.</td>
16839
16840    </tr>
16841
16842
16843
16844
16845 
16846 
16847 
16848 
16849 
16850  </tbody>
16851</table>
16852
16853
16854
16855
16856<span style="font-weight: bold;"><span style="font-weight: bold;"><br>
16857
16858
16859
16860
16861
16862</span></span><span style="font-weight: bold;"><span style="font-weight: bold;">Package (<span style="font-weight: bold;">mrun</span>
16863option -p): <span style="font-weight: bold;"><a name="spectra"></a>spectra</span>&nbsp;&nbsp;&nbsp;&nbsp;
16864NAMELIST group name: <span style="font-weight: bold;">spectra_par<br>
16865
16866
16867
16868
16869
16870<br>
16871
16872
16873
16874
16875</span></span></span>
16876<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
16877
16878
16879
16880
16881 <tbody>
16882
16883
16884
16885
16886 <tr>
16887
16888
16889
16890
16891
16892      <td style="vertical-align: top;"><font size="4"><b>Parameter
16893name</b></font></td>
16894
16895
16896
16897
16898 <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
16899
16900
16901
16902
16903
16904      <td style="vertical-align: top;"> 
16905     
16906     
16907     
16908     
16909      <p><b><font size="4">Default</font></b> <br>
16910
16911
16912
16913
16914 <b><font size="4">value</font></b></p>
16915
16916
16917
16918
16919 </td>
16920
16921
16922
16923
16924
16925      <td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
16926
16927
16928
16929
16930
16931    </tr>
16932
16933
16934
16935
16936 <tr>
16937
16938
16939
16940
16941 <td style="vertical-align: top;">
16942     
16943     
16944     
16945     
16946      <p><a name="averaging_interval_sp"></a><b>averaging_interval_sp</b></p>
16947
16948
16949
16950
16951
16952      </td>
16953
16954
16955
16956
16957 <td style="vertical-align: top;">R<br>
16958
16959
16960
16961
16962 </td>
16963
16964
16965
16966
16967
16968      <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
16969
16970
16971
16972
16973
16974interval</a></span> </td>
16975
16976
16977
16978
16979 <td style="vertical-align: top;"> 
16980     
16981     
16982     
16983     
16984      <p>Averaging interval
16985for spectra output to local
16986file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
16987      </font></font>and/or&nbsp; <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
16988/ &nbsp;&nbsp; <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
16989(in s).&nbsp; </p>
16990
16991
16992
16993
16994 
16995     
16996     
16997     
16998     
16999      <p>If
17000this parameter is given a non-zero value, temporally
17001averaged spectra data are output. By default, spectra data data are not
17002subject to temporal averaging. The interval length is limited by the
17003parameter <a href="#dt_dosp">dt_dosp</a>. In any
17004case <b>averaging_interval_sp</b> &lt;= <b>dt_dosp
17005      </b>must
17006hold.</p>
17007
17008
17009
17010
17011If an interval is defined, then by default the average
17012is calculated
17013from the data values of all timesteps lying within this interval. The
17014number of time levels entering into the average can be reduced with the
17015parameter <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>.
17016     
17017     
17018     
17019     
17020      <p>If
17021an averaging interval can not be completed at the end of a run, it will
17022be finished at the beginning of the next restart run. Thus for restart
17023runs, averaging intervals do not
17024necessarily begin at the beginning of the run.</p>
17025
17026
17027
17028
17029      </td>
17030
17031
17032
17033
17034 </tr>
17035
17036
17037
17038
17039
17040    <tr>
17041
17042
17043
17044
17045 <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td>
17046
17047
17048
17049
17050
17051      <td style="vertical-align: top;">I(100)</td>
17052
17053
17054
17055
17056 <td style="vertical-align: top;"><i>no level</i></td>
17057
17058
17059
17060
17061
17062      <td style="vertical-align: top;"> 
17063     
17064     
17065     
17066     
17067      <p>Vertical level
17068for which horizontal spectra are to be
17069calculated and output (gridpoints).<br>
17070
17071
17072
17073
17074 </p>
17075
17076
17077
17078
17079 <br>
17080
17081
17082
17083
17084
17085Spectra can be calculated for up to 100 levels.</td>
17086
17087
17088
17089
17090 </tr>
17091
17092
17093
17094
17095
17096    <tr>
17097
17098
17099
17100
17101      <td style="vertical-align: top;">
17102     
17103     
17104     
17105     
17106      <p><a name="data_output_sp"></a><b>data_output_sp</b></p>
17107
17108
17109
17110
17111      </td>
17112
17113
17114
17115
17116      <td style="vertical-align: top;">C*10 (10)</td>
17117
17118
17119
17120
17121      <td style="vertical-align: top;"><i>10 * ' '</i></td>
17122
17123
17124
17125
17126      <td style="vertical-align: top;">
17127     
17128     
17129     
17130     
17131      <p>Quantities for which
17132horizontal spectra are to be calculated
17133and output.</p>
17134
17135
17136
17137
17138 
17139     
17140     
17141     
17142     
17143      <p>Allowed standard values are:&nbsp; <b>data_output_sp</b>
17144= <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>, <span style="font-style: italic;">'w'</span>, <span style="font-style: italic;">'pt'</span>, <span style="font-style: italic;">'q'</span>. The user may define further quantities (see <a href="chapter_3.5.4#spectra">chapter 3.5.4 part 5</a>).<br>
17145
17146
17147
17148
17149 </p>
17150
17151
17152
17153
17154
17155     
17156     
17157     
17158     
17159      <p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p>
17160
17161
17162
17163
17164
17165     
17166     
17167     
17168     
17169      <p>By default spectra data are output to the local file <a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>.
17170The file's format is NetCDF.&nbsp; Further details about processing
17171NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>
17172
17173
17174
17175
17176     
17177     
17178     
17179     
17180      <p>The
17181temporal interval of the output times of profiles is
17182assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>.&nbsp;</p>
17183
17184
17185
17186
17187     
17188     
17189     
17190     
17191      <p>The
17192vertical levels for which spectra are to be computed and output must be
17193given by parameter <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.
17194      </p>
17195
17196
17197
17198
17199      <span style="font-weight: bold;">Note:</span><br>
17200
17201
17202
17203
17204
17205Beside <span style="font-weight: bold;">data_output_sp</span>,
17206values <span style="font-weight: bold;">must</span>
17207be given for each of the
17208parameters,&nbsp; <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>,
17209and <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a></font>,
17210otherwise <span style="font-weight: bold;">no</span>
17211output will be
17212created!<br>
17213
17214
17215
17216
17217      <br>
17218
17219
17220
17221
17222      <br>
17223
17224
17225
17226
17227
17228Calculation of spectra requires cyclic boundary conditions
17229along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
17230and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For
17231historical reasons, data can also be output in ASCII-format on local
17232files <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
17233and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
17234(depending on the direction(s) along which spectra are to be
17235calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font>
17236which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See
17237parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
17238for defining the format in which data shall be output.&nbsp;Within
17239these file, the spectra are ordered with respect to their
17240output times. Spectra can also be temporally averaged (see <a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a>
17241).&nbsp;<font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a
17242spectrum is output in a single line (1st column:
17243wavenumber, 2nd column: spectral coefficient). If spectra are to be
17244calculated and output for more than one height (see </font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font><font>),
17245the spectral coefficients for the further heighs can be found in the
17246subsequent columns. </font>The order
17247of the data in the file follows the order used in the assignment for <b>data_output_sp</b>
17248(<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&#8230;
17249means that the file starts with the spectra of the u-component,
17250followed by the v-component spectra, etc.). Additional to the files
17251PLOTSP_X_DATA and PLOTSP_Y_DATA which contain
17252the data,
17253PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a>
17254and <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_Y_PAR</a>)
17255which 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>.
17256Spectra can be directly plotted with <span style="font-weight: bold;">profil</span>
17257using the data and the corresponding parameter file. The
17258plot layout is
17259steered via the parameter input file. The vertical levels for which
17260spectra are to be plotted must be given by <font><a href="chapter_4.2.html#plot_spectra_level"><span lang="en-GB"><font face="Thorndale">plot_spectra_level</font></span></a></font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"></span></a></font>. <span style="font-weight: bold;"></span>Otherwise, no
17261spectra
17262will appear on the plot, although data are available on file. All
17263parameter values can be changed by editing the parameter
17264input
17265file.<span style="font-weight: bold;"><br>
17266
17267
17268
17269
17270      </span></td>
17271
17272
17273
17274
17275    </tr>
17276
17277
17278
17279
17280    <tr>
17281
17282
17283
17284
17285
17286      <td style="vertical-align: top;"> 
17287     
17288     
17289     
17290     
17291      <p><a name="dt_dosp"></a><b>dt_dosp</b></p>
17292
17293
17294
17295
17296
17297      </td>
17298
17299
17300
17301
17302 <td style="vertical-align: top;">R</td>
17303
17304
17305
17306
17307
17308      <td style="vertical-align: top;"><i>value of
17309&nbsp;<a href="chapter_4.2.html#dt_data_output">dt_data_<br>
17310
17311
17312
17313
17314output</a></i></td>
17315
17316
17317
17318
17319
17320      <td style="vertical-align: top;"> 
17321     
17322     
17323     
17324     
17325      <p>Temporal
17326interval at which&nbsp;spectra data shall be output
17327(in s).&nbsp; </p>
17328
17329
17330
17331
17332 
17333     
17334     
17335     
17336     
17337      <p><span lang="en-GB"><font face="Thorndale">If output of
17338horizontal spectra is switched on (see </font></span><a href="#data_output_sp"><span lang="en-GB"><font face="Thorndale">data_output_sp</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
17339parameter can be used to
17340assign the temporal interval at which spectral data&nbsp; shall be
17341output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
17342simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>,
17343which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
17344time is the beginning of
17345&nbsp;the simulation, i.e. output takes place at times t = <span style="font-weight: bold;">skip_time_dosp</span> + <b>dt_dosp</b>,
17346      <span style="font-weight: bold;">skip_time_dosp</span>
17347+ 2*<b>dt_dosp</b>, skip_time_dosp + 3*<b>dt_dosp</b>,
17348etc. The actual output times can
17349deviate 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;
17350If <b>dt_dosp</b> &lt; </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then
17351spectral data are output
17352after each time step (if this is requested it should be <b>dt_dosp</b>
17353= <i>0</i>).</font></span> </p>
17354
17355
17356
17357
17358 </td>
17359
17360
17361
17362
17363
17364    </tr>
17365
17366
17367
17368
17369 <tr>
17370
17371
17372
17373
17374 <td style="vertical-align: top;">
17375     
17376     
17377     
17378     
17379      <p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p>
17380
17381
17382
17383
17384
17385      </td>
17386
17387
17388
17389
17390 <td style="vertical-align: top;">I(100)</td>
17391
17392
17393
17394
17395
17396      <td style="vertical-align: top;"><i>no level</i></td>
17397
17398
17399
17400
17401
17402      <td style="vertical-align: top;"> 
17403     
17404     
17405     
17406     
17407      <p>Vertical
17408level(s) for which horizontal spectra are to be
17409plotted (in gridpoints).&nbsp; </p>
17410
17411
17412
17413
17414 
17415     
17416     
17417     
17418     
17419      <p>This parameter
17420only affects the display of spectra in plots
17421created with <span style="font-weight: bold;">profil</span>.
17422The
17423spectral data created and output to file are exclusively determined via
17424      <font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p>
17425
17426
17427
17428
17429
17430      </td>
17431
17432
17433
17434
17435 </tr>
17436
17437
17438
17439
17440 <tr>
17441
17442
17443
17444
17445 <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td>
17446
17447
17448
17449
17450
17451      <td style="vertical-align: top;">R<br>
17452
17453
17454
17455
17456 </td>
17457
17458
17459
17460
17461 <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>
17462
17463
17464
17465
17466data_output</a></span>
17467      </td>
17468
17469
17470
17471
17472 <td style="vertical-align: top;">No output of
17473spectra data before this interval has passed (in s).<br>
17474
17475
17476
17477
17478      <br>
17479
17480
17481
17482
17483This
17484parameter causes that data output activities are starting not before
17485this interval
17486(counting from the beginning of the simulation, t=0) has passed. <br>
17487
17488
17489
17490
17491      <br>
17492
17493
17494
17495
17496      <span style="font-weight: bold;">Example:</span><br>
17497
17498
17499
17500
17501If
17502the user has set <a href="#dt_dosp">dt_dosp</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dosp</span> = <span style="font-style: italic;">1800.0</span>, then the
17503first output will be done at t = 5400 s. </td>
17504
17505
17506
17507
17508 </tr>
17509
17510
17511
17512
17513
17514    <tr>
17515
17516
17517
17518
17519 <td style="vertical-align: top;"> 
17520     
17521     
17522     
17523     
17524      <p><a name="spectra_direction"></a><b>spectra_direction</b></p>
17525
17526
17527
17528
17529
17530      </td>
17531
17532
17533
17534
17535 <td style="vertical-align: top;">C*2 (10)</td>
17536
17537
17538
17539
17540
17541      <td style="vertical-align: top;"><i>10 * ' '</i></td>
17542
17543
17544
17545
17546
17547      <td style="vertical-align: top;"> 
17548     
17549     
17550     
17551     
17552      <p>Direction(s)
17553along which spectra are to be calculated.&nbsp; </p>
17554
17555
17556
17557
17558 
17559     
17560     
17561     
17562     
17563      <p>Allowed
17564values are <span style="font-style: italic;">'x'</span>,
17565      <span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For
17566every quantity given by <a href="#data_output_sp">data_output_sp</a>
17567a corresponding
17568direction<span style="font-weight: bold;"> </span>must
17569be assigned.<br>
17570
17571
17572
17573
17574 </p>
17575
17576
17577
17578
17579 
17580     
17581     
17582     
17583     
17584      <p>Calculation of spectra
17585requires cyclic boundary conditions
17586along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
17587and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</p>
17588
17589
17590
17591
17592
17593      </td>
17594
17595
17596
17597
17598 </tr>
17599
17600
17601
17602
17603 
17604 
17605 
17606 
17607 
17608  </tbody>
17609</table>
17610
17611
17612
17613
17614<span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
17615
17616
17617
17618
17619
17620</span></span></span>
17621<h3 style="line-height: 100%;"><br>
17622
17623
17624
17625
17626<a href="chapter_4.1.html"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></a><a href="index.html"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></a><a href="chapter_4.3.html"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></a></h3>
17627
17628
17629
17630
17631<span style="font-style: italic;">Last change:</span>
17632$Id: chapter_4.2.html 555 2010-09-07 07:32:53Z suehring $ <span style="font-weight: bold;"><span style="font-weight: bold;"><br>
17633
17634
17635
17636
17637
17638</span></span><br>
17639
17640
17641
17642
17643
17644</body></html>
Note: See TracBrowser for help on using the repository browser.