Home

Context Navigation

chapter_4.2.html @ 108

Last change on this file since 108 was 108, checked in by letzel, 17 years ago

Improved coupler: evaporation - salinity-flux coupling for humidity = .T.,

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

Optional calculation of km and kh from initial TKE e_init;
Default initialization of km,kh = 0.00001 for ocean = .T.;
Allow data_output_pr= q, wq, w"q", w*q* for humidity = .T.;
Bugfix: Rayleigh damping for ocean fixed.

Property svn:keywords set to Id

File size: 260.0 KB

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