Home

Context Navigation

source: palm/trunk/DOC/app/chapter_3.4.html @ 189

Last change on this file since 189 was 134, checked in by letzel, 17 years ago
Redefine initial nzb_local as the actual total size of topography (later the extent of topography in nzb_local is reduced by 1dx at the E topography walls and by 1dy at the N topography walls to form the basis for nzb_s_inner); for consistency redefine 'single_building' case.
Property svn:keywords set to `Id`
File size: 107.9 KB

Line
1	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2	<html><head>
3
4
5
6	<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
7
8
9	<title>PALM chapter 3.4</title></head>
10
11	<body>
12
13
14	<h3 style="line-height: 100%;"><font color="#000000">3.4
15	Input and
16	output files</font></h3>
17
18
19	<p style="line-height: 100%;"></p>
20
21
22	<p style="line-height: 100%;"><font color="#000000">The
23	model works
24	with a set of files, which are all located in the temporary working
25	directory and which are either expected at the beginning of the run
26	(the so-called input files) or which are
27	produced during the run and/or at the end of the simulation (output
28	files).</font><font color="#800000">
29	<font color="#000000">The following table lists all
30	default files
31	addressed by the model. They are arranged according to the
32	associated FORTRAN unit (unit number).</font> </font><font color="#000000">The
33	unit 90 is used for different files, which are opened only briefly
34	and uniquely in the model and closed directly afterwards.
35	Unit numbers 101 - 109, 111 - 113, and 116 refer to data files
36	which have NetCDF format.
37	These are not opened by a FORTRAN-OPEN-statement but by a corresponding
38	NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on
39	machines where a NetCDF library is available.<br>
40
41
42	</font></p>
43
44
45	<p style="line-height: 100%;"><font color="#000000">The
46	file
47	names described in the list correspond to the names indicated in the
48	respective OPEN instruction, i.e. the files are expected and saved
49	under these names in the temporary working directory of the model. By
50	default, file names are always written in capital letters. The
51	third column indicates whether it is an input or output file (I
52	and/or O). The NetCDF files can be both input and output files (I/O).
53	If restart jobs shall append data to an existing NetCDF file (created
54	by a previous job of the job chain), the respective file has to be
55	given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter
56	4.5.1</a> which gives more details about the PALM-NetCDF-output).</font>
57	</p>
58
59
60	<p style="line-height: 100%;"> </p>
61
62
63	<p style="line-height: 100%;"><font color="#000000">On
64	parallel
65	computers many of the files are read and/or written by the central
66	processing element 0 (PE0) only. These files have processor-independent
67	content (and therefore they can be read or written by other
68	PEs just as well). However, certain files have processor-dependent
69	content. For the binary output of data for restart runs (local file
70	<a href="#BINOUT">BINOUT</a>),
71	for example, <font color="#000000">each PE outputs only
72	the data of
73	its subdomain. So each processing element writes
74	into its own file with its own file name. These files lie in a
75	subdirectory of the temporary working directory. Their names are build
76	off from the underline ("_ ") and the four digit
77	processor ID. The data written for restart runs would be e.g. on the
78	files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc.
79	Such files, which have processor-dependent content on parallel
80	computers, are marked in the following list by the fact, that to the
81	file name a line (”/“) is attached. If appropriate
82	output
83	files are to be copied through <b>mrun</b> to permanent
84	files, and/or
85	files with processor-dependent content are supposed to be copied as
86	input files into the temporary working directory of the model, you have
87	to indicate a special file attribute in the appropriate file
88	connection statement </font>(see <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#arpe">arpe</a>,
89	<a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#flpe">flpe</a>
90	<font color="#000000">in the <b>mrun </b>description).</font><font color="#800000">
91	</font><font color="#000000">Then the permanent file
92	name will be
93	interpreted as a directory name, in which the input files are
94	expected and/or to which output files are written. The file names in
95	these directories are always named _0000, _0001, _0002 etc. </font>
96	</font></p>
97
98
99	<p><font color="#000000"><font color="#000000">For
100	internal use,
101	the model may open a set of further files, which are not
102	defined by the user but contain no usable information and
103	therefore are not included in this list.</font></font></p>
104	<p><font color="#000000"><font color="#000000">
105
106	<a name="coupled"></a>In case of <a href="chapter_3.8.html">coupled</a> atmosphere-ocean
107	runs (see <a href="chapter_3.8.html">chapter 3.8</a>),
108	both the atmosphere and the </font></font><font color="#000000"><font color="#000000"><a href="chapter_4.1.html#ocean">ocean</a> executable use
109	the same temporary working directory. However, each executable requires its own, unique set of files for I/O. In order to
110	distinguish between atmosphere and ocean files, coupled </font></font><font color="#000000"><font color="#000000">atmosphere-ocean
111	</font></font><font color="#000000"><font color="#000000">runs use the </font></font><font color="#000000"><font color="#000000">following
112	filename convention</font></font><font color="#000000"><font color="#000000">. </font></font><font color="#000000"><font color="#000000">The
113	atmosphere executable uses the set of normal filenames given in the
114	table below. The ocean executable uses a set of modified filenames that
115	have the string '_O' added to their normal name. The coupled
116	ocean filenames are given in brackets in the table below where
117	applicable. The string '_O' is simply appended </font></font><font color="#000000"><font color="#000000">to most
118	filenames</font></font><font color="#000000"><font color="#000000">; exceptions are highlighted in bold face. (<span style="font-weight: bold;">Note:</span> uncoupled
119	ocean runs use the normal set of filenames without '_O'.)</font></font></p>
120	<p></p>
121	<font color="#000000"><font color="#000000">
122
123	<br>
124
125
126	</font>
127	<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
128
129
130	<tbody>
131
132
133	<tr valign="top">
134
135
136	<td width="8%">
137
138	<p><font size="4"><b>Unit</b></font></p>
139
140
141	</td>
142
143
144	<td width="12%">
145
146	<p><font size="4"><b>Name</b></font></p>
147
148
149	</td>
150
151
152	<td width="4%">
153
154	<p><font size="4"><b>I/O</b></font></p>
155
156
157	</td>
158
159
160	<td width="9%">
161
162	<p><font size="4"><b>Format</b></font></p>
163
164
165	</td>
166
167
168	<td colspan="1" width="67%">
169
170	<p><font size="4"><b>Description/contents</b></font></p>
171
172
173	</td>
174
175
176	</tr>
177
178
179	<tr valign="top">
180
181
182	<td style="text-align: center;" width="8%"> 11<br>
183
184
185	</td>
186
187
188	<td width="12%">
189
190	<p><a name="PARIN"></a>PARIN<br>
191
192
193	(PARIN_O)</p>
194
195
196	</td>
197
198
199	<td width="4%">
200
201	<p align="center">I</p>
202
203
204	</td>
205
206
207	<td style="width: 9%;">
208
209	<p>ASCII/  <br>
210
211
212	NAMELIST</p>
213
214
215	</td>
216
217
218	<td colspan="1" width="67%">
219
220	<p><font color="#000000">Parameter
221	for model steering. This file
222	is needed by the model in each case. Its content and structure is
223	described in detail in</font> <a href="chapter_4.0.html">chapter
224	4.0</a>. <a href="chapter_4.4.1.html">Chapter
225	4.4.1</a> <font color="#000000">shows a simple
226	example. </font> </p>
227
228
229	</td>
230
231
232	</tr>
233
234
235	<tr valign="top">
236
237
238	<td style="text-align: center;" width="8%">
239
240	<p align="center">13</p>
241
242
243	</td>
244
245
246	<td width="12%">
247
248	<p><a name="BININ"></a>BININ/<br>
249
250
251	(BININ<span style="font-weight: bold;">_O</span>/)</p>
252
253
254	</td>
255
256
257	<td width="4%">
258
259	<p align="center">I</p>
260
261
262	</td>
263
264
265	<td width="9%">
266
267	<p>Binary</p>
268
269
270	</td>
271
272
273	<td colspan="1" width="67%">
274
275	<p>Binary data,
276	which are read in by the model at the beginning
277	of a restart run (see <a href="chapter_3.3.html">chapter
278	3.3</a>). The appropriate file must have been written by the
279	preceding
280	job of the job chain (see <a href="#BINOUT">BINOUT</a>).
281	This file contains the initial parameters (see <a href="chapter_4.1.html">chapter
282	4.1</a>) of the job chain, arrays of the prognostic and
283	diagnostic
284	variables as well as those parameters and variables for plots of
285	horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>),
286	which have been determined by the job chain so far. Concerning runs on
287	several processors it has to be noted that each processing element
288	reads its own file and the file content is processor-dependent. The
289	number of processors which can be used must not be changed during a job
290	chain and/or if a job chain is continued.  </p>
291
292
293
294	<p>Knowledge
295	of the file structure is usually not necessary,
296	because the file is produced and also read again by the model, but it
297	can be useful for error determination in case of read errors .
298	Therefore the file structure is described in the following.  </p>
299
300
301
302	<p>The first record of this file contains a version number
303	(ten
304	character string) of the subroutine, which, which output the data that
305	follows (write_var_list.f90). This number has to
306	agree with the version number subroutine which is reading the file
307	(read_var_list.f90) in case of a restart run. Otherwise the model run
308	is aborted. Version numbers are changed whenever new code revisions
309	require a change of the file format.  </p>
310
311
312
313	<p>Starting
314	from the second record, all initial parameters follow
315	(exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>),
316	whereby each parameter fills two records. In the first record the name
317	of the parameter is saved as a character string (30 characters long,
318	short names are filled by trailing blanks, longer names are cut off at
319	the end), in the second record the value (or the values) of the
320	parameter follow. The sequence of parameters on the file may be
321	arbitrary, however the first and second variable must be <a href="chapter_4.1.html#nz">nz</a>
322	and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
323	If a variable with unknown name is found the model run is
324	aborted.  </p>
325
326
327
328	<p>At the end of the initial
329	parameters a record with the string "<i>***
330	end ***</i>"follows (filled up with trailing blanks up to a
331	length of
332	30 characters).  </p>
333
334
335
336	<p>Afterwards the fields
337	of the prognostic and diagnostic
338	variables follow. This part of the file also begins with a record
339	consisting of a character string of length 10, which contains the
340	version number of the subroutine that wrote the arrays that follow
341	(write_3d_binary.f90). It must agree with the number of the reading
342	subroutine (read_3d_binary.f90).  </p>
343
344
345
346	<p>The
347	following record contains the number of processors which
348	were used in the model run producing this file, the processor ID of the
349	special processor, which creates the file, as well as the lower and
350	upper array indices of the subdomain belonging to this processing
351	element. If no complete agreement with the values of the current model
352	run exists, then this is aborted. This examination must be made in
353	particular on parallel computers, because the jobs of a job chain
354	always have to use the same number of processors and the same virtual
355	processor grid.  </p>
356
357
358
359	<p>After these tests the
360	individual arrays as well as parameters
361	and variables for plots of horizontally averaged vertical profiles
362	follow. Like the initialization parameters, they consist of two
363	records. In the first record, the name of the array or the variable
364	(character string, consisting of 20 characters, filled with trailing
365	blanks) is located, in the second one its values follow. The sequence
366	of the individual variables may be arbitrary again. The parameters for
367	the plot and the respective variables are only read in if for the run
368	parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
369	= <i>.TRUE</i> is selected, otherwise they will be
370	skipped.  </p>
371
372
373
374	<p>At the end of the file there
375	has to be a record with the
376	character string "<span style="font-style: italic;"></span><i>***
377	end
378	***</i>"(filled up with trailing blanks up to a length of 20
379	characters).</p>
380
381
382	</td>
383
384
385	</tr>
386
387
388	<tr valign="top">
389
390
391	<td style="text-align: center;" width="8%">
392
393	<p align="center">14</p>
394
395
396	</td>
397
398
399	<td width="12%">
400
401	<p><a name="BINOUT"></a>BINOUT/<br>
402
403
404	(BINOUT<span style="font-weight: bold;">_O</span>/)</p>
405
406
407	</td>
408
409
410	<td width="4%">
411
412	<p align="center">O</p>
413
414
415	</td>
416
417
418	<td width="9%">
419
420	<p>Binary</p>
421
422
423	</td>
424
425
426	<td colspan="1" width="67%">
427
428	<p>Binary data,
429	which are written by the model at the end of the
430	run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
431	3.3</a>) for the initialization. This output file is then read in
432	as
433	file <a href="#BININ">BININ</a>.
434	It contains the initial parameters (see <a href="chapter_4.1.html">chapter
435	4.1</a>) of the model run, arrays of the prognostic and
436	diagnostic
437	variables as well as those parameters determined so far during a job
438	chain and variables for plots of horizontally averaged vertical
439	profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
440	With runs on several processors it has to be noted that each processing
441	element writes its own file and the file content is
442	processor-dependent. A specification of the file format can be found in
443	the
444	description of the file <a href="#BININ">BININ</a>.
445	</p>
446
447
448
449	<p>The file BINOUT is written by the model only if,
450	with the help
451	of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is
452	assigned for the
453	environment
454	variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span>
455	(see <a href="chapter_3.3.html">chapter
456	3.3</a>).  </p>
457
458
459
460	<p>With large grid point
461	numbers the file BINOUT (or the
462	files residing in directory BINOUT/) will be very large and should
463	be stored (if available) on the archive system of the remote computer.</p>
464
465
466	</td>
467
468
469	</tr>
470
471
472	<tr>
473
474
475	<td style="vertical-align: top; text-align: center;">15<br>
476
477
478	</td>
479
480
481	<td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL<br>
482
483
484	(RUN_CONTROL_O)</td>
485
486
487	<td style="vertical-align: top;">O</td>
488
489
490	<td style="vertical-align: top;">Ascii</td>
491
492
493	<td colspan="1" width="67%">
494
495	<p>This file contains
496	the so-called time step control output of
497	the model. At certain temporal intervals, which are described by the
498	run
499	parameter <a href="chapter_4.1.html#dt_run_control">dt_run_control</a>,
500	a line with the values of certain control parameters is written into
501	this
502	file. Additionally, such a control line is always written, whenever the
503	time step of the model changes. All data and quantities always refer to
504	the entire model domain.  </p>
505
506
507
508	<p>If the
509	1D-model is switched on for the initialization of the
510	3D-models, then control lines are likewise written into this file at
511	certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>).
512	</p>
513
514
515
516	<p>By default, the file RUN_CONTROL only lists
517	information
518	about the selected model parameters at the beginning of the
519	initial run. These informations are written at the beginnning of a run.
520	They correspond to those of the file <a href="#HEADER">HEADER</a>
521	(however without data concerning the consumed CPU time, because these
522	are
523	only known at the end of a run). With the run parameter <a href="chapter_4.2.html#force_print_header">force_print_header</a>
524	it can be achieved that this information is also written at the
525	beginning of the file RUN_CONTROL at restart runs.  </p>
526
527
528
529	<p>The individual columns of the 1D - time step control
530	output
531	have the following meaning (listed by the respective heading of the
532	appropriate
533	column in the file):  <br>
534
535
536	</p>
537
538
539
540	<table style="text-align: left; width: 100%;" cellpadding="2">
541
542
543	<tbody>
544
545
546	<tr>
547
548
549	<td style="vertical-align: top;">ITER.</td>
550
551
552	<td style="vertical-align: top;">Number of
553	time steps
554	accomplished so far</td>
555
556
557	</tr>
558
559
560	<tr>
561
562
563	<td style="vertical-align: top;">HH:MM:SS</td>
564
565
566	<td style="vertical-align: top;">Time (in
567	hours: minutes:
568	seconds)</td>
569
570
571	</tr>
572
573
574	<tr>
575
576
577	<td style="vertical-align: top;">DT</td>
578
579
580	<td style="vertical-align: top;">Time step (in
581	s)</td>
582
583
584	</tr>
585
586
587	<tr>
588
589
590	<td style="vertical-align: top;">UMAX</td>
591
592
593	<td style="vertical-align: top;">Maximum
594	absolute wind
595	velocity
596	(u-component) (in m/s)</td>
597
598
599	</tr>
600
601
602	<tr>
603
604
605	<td style="vertical-align: top;">VMAX</td>
606
607
608	<td style="vertical-align: top;">Maximum
609	absolute wind
610	velocity
611	(v-component) (in m/s)</td>
612
613
614	</tr>
615
616
617	<tr>
618
619
620	<td style="vertical-align: top;">U *</td>
621
622
623	<td style="vertical-align: top;">Friction
624	velocity (<font color="#000000">in </font>m/s)</td>
625
626
627	</tr>
628
629
630	<tr>
631
632
633	<td style="vertical-align: top;">ALPHA</td>
634
635
636	<td style="vertical-align: top;">Angle of the
637	wind vector
638	(to the x-axis) at the top of the
639	Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td>
640
641
642	</tr>
643
644
645	<tr>
646
647
648	<td style="vertical-align: middle;">ENERG.</td>
649
650
651	<td style="vertical-align: top;">Kinetic
652	energy of the
653	1D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
654	averaged over all grid points</td>
655
656
657	</tr>
658
659
660
661	</tbody>
662
663	</table>
664
665
666
667	<p>
668	The individual columns of the 3D - time step control output
669	have the following meaning (listed by the respective heading of the
670	appropriate
671	column in the file):<br>
672
673
674	</p>
675
676
677
678	<table style="text-align: left; width: 100%;" cellpadding="2">
679
680
681	<tbody>
682
683
684	<tr>
685
686
687	<td style="vertical-align: top;">RUN</td>
688
689
690	<td style="vertical-align: top;">Serial-number
691	of the job
692	in the job chain. The initial
693	run has the number 0, restart runs accordingly have larger numbers.</td>
694
695
696	</tr>
697
698
699	<tr>
700
701
702	<td style="vertical-align: top;">ITER.</td>
703
704
705	<td style="vertical-align: top;">Number of
706	time steps
707	accomplished since starting time t=0 of
708	the initial run.</td>
709
710
711	</tr>
712
713
714	<tr>
715
716
717	<td style="vertical-align: top;">HH:MM:SS</td>
718
719
720	<td style="vertical-align: top;">Time (<font color="#000000">in </font>hours: minutes:
721	seconds) since starting time t=0 of the
722	initial run.</td>
723
724
725	</tr>
726
727
728	<tr>
729
730
731	<td style="vertical-align: top;">DT (E)</td>
732
733
734	<td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
735	following character indicates whether the
736	time
737	step is limited by the advection criterion (A) or the diffusion
738	criterion (D). After changes of the time step a further character
739	follows,
740	which indicates with which time step procedure the changed time step
741	was accomplished (<span style="font-family: monospace;">L:</span>
742	Leapfrog, <span style="font-family: monospace;">E:</span>
743	Euler). This
744	does
745	not apply for the default Runge-Kutta timestep scheme.</td>
746
747
748	</tr>
749
750
751	<tr>
752
753
754	<td style="vertical-align: top;">UMAX</td>
755
756
757	<td style="vertical-align: top;">Maximum
758	absolute wind
759	velocity (u-component) (<font color="#000000">in </font>m/s).
760	If at
761	the
762	appropriate output time a random disturbance was added to the
763	horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
764	the character D will appear directly after the velocity value.</td>
765
766
767	</tr>
768
769
770	<tr>
771
772
773	<td style="vertical-align: top;">VMAX</td>
774
775
776	<td style="vertical-align: top;">Maximum
777	absolute wind
778	velocity (v-component) (<font color="#000000">in </font>m/s).
779	If at
780	the
781	appropriate output time a random disturbance was added to the
782	horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
783	the character D will appear directly after the velocity value.</td>
784
785
786	</tr>
787
788
789	<tr>
790
791
792	<td style="vertical-align: top;">WMAX</td>
793
794
795	<td style="vertical-align: top;">Maximum
796	absolute wind
797	velocity (w-component) (<font color="#000000">in </font>m/s).</td>
798
799
800	</tr>
801
802
803	<tr>
804
805
806	<td style="vertical-align: top;">U
807	*</td>
808
809
810	<td style="vertical-align: top;">Horizontal
811	average of the
812	friction velocity (<font color="#000000">in </font>m/s).</td>
813
814
815	</tr>
816
817
818	<tr>
819
820
821	<td style="vertical-align: top;">W
822	*</td>
823
824
825	<td style="vertical-align: top;">Convective
826	velocity scale
827	(<font color="#000000">in </font>m/s). The assumed
828	boundary layer
829	height is determined via the heat flux minimum criterion.</td>
830
831
832	</tr>
833
834
835	<tr>
836
837
838	<td style="vertical-align: top;">THETA *</td>
839
840
841	<td style="vertical-align: top;">Characteristic
842	temperature
843	of the Prandtl - layer (<font color="#000000">in </font>K).</td>
844
845
846	</tr>
847
848
849	<tr>
850
851
852	<td style="vertical-align: top;">Z_I</td>
853
854
855	<td style="vertical-align: top;">Height of the
856	convective
857	boundary layer (<font color="#000000">in </font>m),
858	determined via
859	the criterion of the heat flux minimum.</td>
860
861
862	</tr>
863
864
865	<tr>
866
867
868	<td style="vertical-align: middle;">ENERG.</td>
869
870
871	<td style="vertical-align: top;">Average
872	resolved total
873	energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
874	normalized with the total number of grid points.</td>
875
876
877	</tr>
878
879
880	<tr>
881
882
883	<td style="vertical-align: middle;">DISTENERG</td>
884
885
886	<td style="vertical-align: top;">Average
887	resolved
888	disturbance energy of flow field (<font color="#000000">in
889	</font>m<sup>2</sup>/s<sup>2</sup>),
890	normalized with the total number of grid points.</td>
891
892
893	</tr>
894
895
896	<tr>
897
898
899	<td style="vertical-align: top;">DIVOLD</td>
900
901
902	<td style="vertical-align: top;"><font color="#000000">Divergence
903	of the velocity field (sum of
904	the absolute values) (</font><font color="#000000">in
905	</font><font color="#000000">1/s) before
906	call of the
907	pressure solver,
908	normalized with the total number of grid points.</font></td>
909
910
911	</tr>
912
913
914	<tr>
915
916
917	<td style="vertical-align: top;">DIVNEW</td>
918
919
920	<td style="vertical-align: top;"><font color="#000000">Divergence
921	of the velocity field (sum of
922	the absolute values) (</font><font color="#000000">in
923	</font><font color="#000000">1/s) after
924	call of the
925	pressure solver, normalized</font>
926	with the total number of grid points.</td>
927
928
929	</tr>
930
931
932	<tr>
933
934
935	<td style="vertical-align: top;">UMAX (KJI)</td>
936
937
938	<td style="vertical-align: top;">Indices of
939	the grid point
940	with the maximum absolute
941	u-component of the wind velocity (sequence: k, j, i).</td>
942
943
944	</tr>
945
946
947	<tr>
948
949
950	<td style="vertical-align: top;">VMAX (KJI)</td>
951
952
953	<td style="vertical-align: top;">Indices of
954	the grid point
955	with the maximum absolute
956	v-component of the wind velocity (sequence: k, j, i).</td>
957
958
959	</tr>
960
961
962	<tr>
963
964
965	<td style="vertical-align: top;">WMAX (KJI)</td>
966
967
968	<td style="vertical-align: top;">Indices of
969	the grid point
970	with the maximum absolute
971	w-component of the wind velocity (sequence: k, j, i).</td>
972
973
974	</tr>
975
976
977	<tr>
978
979
980	<td style="vertical-align: top;">ADVECX</td>
981
982
983	<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
984	coordinate system has been moved in
985	x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
986
987
988	</tr>
989
990
991	<tr>
992
993
994	<td style="vertical-align: top;">ADVECY</td>
995
996
997	<td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
998	coordinate system has been moved in
999	y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
1000
1001
1002	</tr>
1003
1004
1005
1006	</tbody>
1007
1008	</table>
1009
1010
1011	</td>
1012
1013
1014	</tr>
1015
1016
1017	<tr>
1018
1019
1020	<td style="vertical-align: top; text-align: center;">16<br>
1021
1022
1023	</td>
1024
1025
1026	<td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL<br>
1027
1028
1029	(LIST_PROFIL_O) </td>
1030
1031
1032	<td style="vertical-align: top;">O<br>
1033
1034
1035	</td>
1036
1037
1038	<td style="vertical-align: top;">Ascii<br>
1039
1040
1041	</td>
1042
1043
1044	<td style="vertical-align: top;">This file contains
1045	horizontally
1046	(and possibly temporally)
1047	averaged vertical profiles of some model variables. The quantities
1048	saved are set model-internally and can not be determined by the user.
1049	At each output time (see <a href="chapter_4.2.html#dt_dopr_listing">dt_dopr_listing</a>)
1050	two tables are written to the file consecutively. The first contains
1051	variables which are defined on the scalar / u-v-grid-levels, the
1052	second table contains variables which are defined on the w-grid-levels.
1053	If subdomains were defined with the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions </a>for
1054	additional statistic evaluation, then the tables
1055	described above are written for each individual subdomain. The name of
1056	the respective subdomain (see <a href="chapter_4.3.html#region">region</a>)
1057	appears in the header of the respective table. <br>
1058
1059
1060	In each case the tables consist of a header, followed by the
1061	profiles arranged next to each other in columns. The header contains
1062	some basic information of the respective run (model version, run
1063	identifier consisting of
1064	basic file name and number of the job in the job chain, executing
1065	computer, date, time of the beginning of the run, name of the
1066	subdomain, output time, kind of averaging). On the u-v-level the
1067	following columns are written: <br>
1068
1069
1070
1071	<table style="text-align: left; width: 100%;" cellpadding="2">
1072
1073
1074	<tbody>
1075
1076
1077	<tr>
1078
1079
1080	<td style="text-align: left; vertical-align: middle;">k<br>
1081
1082
1083	</td>
1084
1085
1086	<td style="text-align: left; vertical-align: middle;">Vertical
1087	grid point index.</td>
1088
1089
1090	</tr>
1091
1092
1093	<tr>
1094
1095
1096	<td style="text-align: left; vertical-align: middle;">zu<br>
1097
1098
1099	</td>
1100
1101
1102	<td style="text-align: left; vertical-align: middle;">Height
1103	of the grid point
1104	level (<font color="#000000">in </font>m).</td>
1105
1106
1107	</tr>
1108
1109
1110	<tr>
1111
1112
1113	<td style="text-align: left; vertical-align: middle;">u<br>
1114
1115
1116	</td>
1117
1118
1119	<td style="text-align: left; vertical-align: middle;">u-component
1120	of the wind
1121	velocity (<font color="#000000">in </font>m/s).</td>
1122
1123
1124	</tr>
1125
1126
1127	<tr>
1128
1129
1130	<td style="text-align: left; vertical-align: middle;">du<br>
1131
1132
1133	</td>
1134
1135
1136	<td style="text-align: left; vertical-align: middle;">Deviation
1137	of the
1138	u-component from the initial profile at the
1139	time t=0 (initialization profile) (<font color="#000000">in
1140	</font>m/s).</td>
1141
1142
1143	</tr>
1144
1145
1146	<tr>
1147
1148
1149	<td style="text-align: left; vertical-align: middle;">v<br>
1150
1151
1152	</td>
1153
1154
1155	<td style="text-align: left; vertical-align: middle;">v-component
1156	of the wind
1157	velocity (<font color="#000000">in </font>m/s).</td>
1158
1159
1160	</tr>
1161
1162
1163	<tr>
1164
1165
1166	<td style="text-align: left; vertical-align: middle;">dv<br>
1167
1168
1169	</td>
1170
1171
1172	<td style="text-align: left; vertical-align: middle;">Deviation
1173	of the
1174	v-component from the initial profile at the
1175	time t=0 (initialization profile) (<font color="#000000">in
1176	</font>m/s).</td>
1177
1178
1179	</tr>
1180
1181
1182	<tr>
1183
1184
1185	<td style="text-align: left; vertical-align: middle;">pt
1186	<br>
1187
1188
1189	</td>
1190
1191
1192	<td style="text-align: left; vertical-align: middle;">Potential
1193	temperature (<font color="#000000">in </font>K).</td>
1194
1195
1196	</tr>
1197
1198
1199	<tr>
1200
1201
1202	<td style="text-align: left; vertical-align: middle;">dpt<br>
1203
1204
1205	</td>
1206
1207
1208	<td style="text-align: left; vertical-align: middle;">Deviation
1209	of potential
1210	temperature from the initial profile at
1211	the time t=0 (initialization profile) (<font color="#000000">in
1212	</font>K).</td>
1213
1214
1215	</tr>
1216
1217
1218	<tr>
1219
1220
1221	<td style="text-align: left; vertical-align: middle;">e<br>
1222
1223
1224	</td>
1225
1226
1227	<td style="text-align: left; vertical-align: middle;">Turbulent
1228	kinetic energy
1229	(subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
1230
1231
1232	</tr>
1233
1234
1235	<tr>
1236
1237
1238	<td style="text-align: left; vertical-align: middle;">Km<br>
1239
1240
1241	</td>
1242
1243
1244	<td style="text-align: left; vertical-align: middle;">Turbulent
1245	diffusion
1246	coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
1247
1248
1249	</tr>
1250
1251
1252	<tr>
1253
1254
1255	<td style="text-align: left; vertical-align: middle;">Kh<br>
1256
1257
1258	</td>
1259
1260
1261	<td style="text-align: left; vertical-align: middle;">Turbulent
1262	diffusion
1263	coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
1264
1265
1266	</tr>
1267
1268
1269	<tr>
1270
1271
1272	<td style="text-align: left; vertical-align: middle;">l<br>
1273
1274
1275	</td>
1276
1277
1278	<td style="text-align: left; vertical-align: middle;">Mixing
1279	length (<font color="#000000">in </font>m).</td>
1280
1281
1282	</tr>
1283
1284
1285	<tr>
1286
1287
1288	<td style="vertical-align: top;"><br>
1289
1290
1291	</td>
1292
1293
1294	<td style="vertical-align: top;"><br>
1295
1296
1297	</td>
1298
1299
1300	</tr>
1301
1302
1303
1304	</tbody>
1305
1306	</table>
1307
1308
1309	On the w-level the following columns are written:<br>
1310
1311
1312	<br>
1313
1314
1315
1316	<table style="text-align: left; width: 100%;" cellpadding="2">
1317
1318
1319	<tbody>
1320
1321
1322	<tr>
1323
1324
1325	<td style="vertical-align: middle;">k<br>
1326
1327
1328	</td>
1329
1330
1331	<td style="vertical-align: middle;">Vertical
1332	grid point
1333	index.</td>
1334
1335
1336	</tr>
1337
1338
1339	<tr>
1340
1341
1342	<td style="vertical-align: middle;">zw<br>
1343
1344
1345	</td>
1346
1347
1348	<td style="vertical-align: middle;">Height of
1349	the grid
1350	point
1351	level (<font color="#000000">in </font>m).</td>
1352
1353
1354	</tr>
1355
1356
1357	<tr>
1358
1359
1360	<td style="vertical-align: middle;">w'pt'</td>
1361
1362
1363	<td style="vertical-align: middle;">Vertical
1364	subgrid-scale
1365	kinematic heat flux (<font color="#000000">in </font>K
1366	m/s).</td>
1367
1368
1369	</tr>
1370
1371
1372	<tr>
1373
1374
1375	<td style="vertical-align: middle;">wpt</td>
1376
1377
1378	<td style="vertical-align: middle;">Vertical
1379	total (
1380	subgrid-scale + resolved)
1381	kinematic heat flux (<font color="#000000">in </font>K
1382	m/s).</td>
1383
1384
1385	</tr>
1386
1387
1388	<tr>
1389
1390
1391	<td style="vertical-align: middle;">w'u'</td>
1392
1393
1394	<td style="vertical-align: middle;">u-component
1395	of the
1396	vertical subgrid-scale momentum flux (<font color="#000000">in
1397	</font>m<sup>2</sup>/s<sup>2</sup>).</td>
1398
1399
1400	</tr>
1401
1402
1403	<tr>
1404
1405
1406	<td style="vertical-align: middle;">wu</td>
1407
1408
1409	<td style="vertical-align: middle;">u-component
1410	of the
1411	total
1412	vertical momentum flux (
1413	subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
1414
1415
1416	</tr>
1417
1418
1419	<tr>
1420
1421
1422	<td style="vertical-align: middle;">w'v'</td>
1423
1424
1425	<td style="vertical-align: middle;">v-component
1426	of the
1427	vertical subgrid-scale momentum flux (<font color="#000000">in
1428	</font>m<sup>2</sup>/s<sup>2</sup>).</td>
1429
1430
1431	</tr>
1432
1433
1434	<tr>
1435
1436
1437	<td style="vertical-align: middle;">wv</td>
1438
1439
1440	<td style="vertical-align: middle;">v-component
1441	of the
1442	total
1443	vertical momentum flux (
1444	subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
1445
1446
1447	</tr>
1448
1449
1450
1451	</tbody>
1452
1453	</table>
1454
1455
1456	<br>
1457
1458
1459	</td>
1460
1461
1462	</tr>
1463
1464
1465	<tr>
1466
1467
1468	<td style="vertical-align: top; text-align: center;">17
1469	</td>
1470
1471
1472	<td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D<br>
1473
1474
1475	(LIST_PROFIL_1D_O)</td>
1476
1477
1478	<td style="vertical-align: top;">O </td>
1479
1480
1481	<td style="vertical-align: top;">Ascii </td>
1482
1483
1484	<td style="vertical-align: top;">This file contains
1485	the vertical
1486	profiles calculated by the
1487	1D-model within initial runs. The quantities saved are set
1488	model-internally and cannot be determined by the user. At the
1489	respective output times (see <a href="chapter_4.1.html#dt_pr_1d">dt_pr_1d</a>)
1490	a table with the following information is written to the file: The
1491	table header contains some basic information of the respective run
1492	(model version, run identifier consisting of basic file name and number
1493	of the job in the
1494	job chain (this number should always be 00, because the 1D-model is
1495	only switched on at initial runs), executing computer, date,
1496	time of the beginning of the run, output time). Afterwards the
1497	following columns appear:<br>
1498
1499
1500
1501	<table style="text-align: left; width: 100%;" cellpadding="2">
1502
1503
1504	<tbody>
1505
1506
1507	<tr>
1508
1509
1510	<td style="text-align: left; vertical-align: middle;">k<br>
1511
1512
1513	</td>
1514
1515
1516	<td style="text-align: left; vertical-align: middle;">Vertical
1517	grid point index.</td>
1518
1519
1520	</tr>
1521
1522
1523	<tr>
1524
1525
1526	<td style="text-align: left; vertical-align: middle;">zu<br>
1527
1528
1529	</td>
1530
1531
1532	<td style="text-align: left; vertical-align: middle;">Height
1533	of the grid point
1534	level (<font color="#000000">in </font>m).</td>
1535
1536
1537	</tr>
1538
1539
1540	<tr>
1541
1542
1543	<td style="text-align: left; vertical-align: middle;">u<br>
1544
1545
1546	</td>
1547
1548
1549	<td style="text-align: left; vertical-align: middle;">u-component
1550	of the wind
1551	velocity (<font color="#000000">in </font>m/s).</td>
1552
1553
1554	</tr>
1555
1556
1557	<tr>
1558
1559
1560	<td style="text-align: left; vertical-align: middle;">v<br>
1561
1562
1563	</td>
1564
1565
1566	<td style="text-align: left; vertical-align: middle;">v-component
1567	of the wind
1568	velocity (<font color="#000000">in </font>m/s).</td>
1569
1570
1571	</tr>
1572
1573
1574	<tr>
1575
1576
1577	<td style="text-align: left; vertical-align: middle;">pt<br>
1578
1579
1580	</td>
1581
1582
1583	<td style="text-align: left; vertical-align: middle;">Potential
1584	temperature (<font color="#000000">in </font>K).</td>
1585
1586
1587	</tr>
1588
1589
1590	<tr>
1591
1592
1593	<td style="text-align: left; vertical-align: middle;">e<br>
1594
1595
1596	</td>
1597
1598
1599	<td style="text-align: left; vertical-align: middle;">Turbulent
1600	kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
1601
1602
1603	</tr>
1604
1605
1606	<tr>
1607
1608
1609	<td style="text-align: left; vertical-align: middle;">rif<br>
1610
1611
1612	</td>
1613
1614
1615	<td style="text-align: left; vertical-align: middle;">Flux
1616	Richardson number</td>
1617
1618
1619	</tr>
1620
1621
1622	<tr>
1623
1624
1625	<td style="text-align: left; vertical-align: middle;">Km<br>
1626
1627
1628	</td>
1629
1630
1631	<td style="text-align: left; vertical-align: middle;">Turbulent
1632	diffusion
1633	coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
1634
1635
1636	</tr>
1637
1638
1639	<tr>
1640
1641
1642	<td style="text-align: left; vertical-align: middle;">Kh<br>
1643
1644
1645	</td>
1646
1647
1648	<td style="text-align: left; vertical-align: middle;">Turbulent
1649	diffusion
1650	coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
1651
1652
1653	</tr>
1654
1655
1656	<tr>
1657
1658
1659	<td style="text-align: left; vertical-align: middle;">l<br>
1660
1661
1662	</td>
1663
1664
1665	<td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
1666	length (</font><font color="#000000">in </font><font color="#000000">m).</font></td>
1667
1668
1669	</tr>
1670
1671
1672
1673	</tbody>
1674
1675	</table>
1676
1677
1678	<br>
1679
1680
1681	</td>
1682
1683
1684	</tr>
1685
1686
1687	<tr>
1688
1689
1690	<td style="vertical-align: top; text-align: center;">18
1691	</td>
1692
1693
1694	<td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES<br>
1695
1696
1697	(CPU_MEASURES_O)</td>
1698
1699
1700	<td style="vertical-align: top;">O </td>
1701
1702
1703	<td style="vertical-align: top;">Ascii </td>
1704
1705
1706	<td style="vertical-align: top;">Time measurements
1707	are
1708	accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file
1709	CPU_MEASURES contains a header with some basic information of the
1710	respective run
1711	(model version, run identifier consisting of basic file name and
1712	number of the job in the job chain, executing computer, date, time of
1713	the beginning of the run) and afterwards two tables with data of CPU
1714	times which have been consumed by certain model parts. The model parts
1715	analyzed in the first table do not overlap and the CPU times needed for
1716	them therefore approximately add up to the “total”
1717	value given in the
1718	first line of this table. In the second table (heading: special
1719	measures) overlaps (in particular with the parts described in the first
1720	table) are possible.  <br>
1721
1722
1723	For each model part it is indicated in the following columns how much
1724	CPU time was needed (absolutely and relative), and how often it was
1725	called.  With runs on several processors the average values of
1726	all
1727	processors are indicated. In the case of parallel runs information for
1728	those processors with the largest and smallest CPU time follow as
1729	well as the standard deviation of all PEs from the average value. With
1730	good
1731	parallelization the CPU times on the individual processors should
1732	differ only little from each other and the standard deviation should be
1733	small.  </td>
1734
1735
1736	</tr>
1737
1738
1739	<tr>
1740
1741
1742	<td style="vertical-align: top; text-align: center;">19
1743	</td>
1744
1745
1746	<td style="vertical-align: top;"><a name="HEADER"></a>HEADER<br>
1747
1748
1749	(HEADER_O) </td>
1750
1751
1752	<td style="vertical-align: top;">O </td>
1753
1754
1755	<td style="vertical-align: top;">Ascii </td>
1756
1757
1758	<td style="vertical-align: top;">
1759
1760	<p>Information about
1761	the selected model parameters (physical and
1762	numerical values) as well as general information about the
1763	run.  </p>
1764
1765
1766
1767	<p>This file contains the values of
1768	all important steering
1769	parameters
1770	(numerical procedures, computing grid and model dimensions, boundary
1771	conditions, physical dimension, turbulence quantities, actions during
1772	the simulation, 1D-model-parameters) as well as data concerning the
1773	selected plot and list outputs. The headlines of the file list the
1774	program version used, date and time of the beginning of the run, the
1775	name of the executing computer, the run identifier (corresponds to the
1776	selected base file name) and the number of the run (number of the
1777	restart run). With parallel runs the number of processors as well as
1778	the assigned virtual processor net also appear. After these headlines
1779	run time and time step information appear (point of starting time,
1780	related to t=0 of the initial run, end-time, time actually reached, CPU
1781	time, etc.). If a model run is incorrectly terminated (e.g.
1782	run time error or excess of the permitted CPU time), information over
1783	the time reached and the necessary CPU time is missing (to understand:
1784	the file HEADER is written twice by the model; once briefly after
1785	beginning of the simulation (naturally here the information over the
1786	time reached is missing etc.) and then briefly before the normal end of
1787	the simulation. The second, now complete output overwrites the first
1788	output.).  </p>
1789
1790
1791
1792	<p>At the end of the file,
1793	information about the values of user
1794	parameters (see <a href="chapter_3.7.html">chapter
1795	3.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter
1796	4.3</a>) can be output by the user with the help of the
1797	subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt>
1798	(located in
1799	the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>).
1800	If no user parameters were found, the string “<tt><font style="font-size: 10pt;" size="2">*** no user-defined
1801	variables found</font></tt>”
1802	appears at the end of the file.
1803	If user parameters were indicated, the string “<tt><font style="font-size: 11pt;" size="2">user-defined
1804	variables and actions</font></tt>”
1805	is printed, followed by informations about the user-defined subdomains
1806	for which
1807	profiles and time series are output. All further information to appear
1808	here, must be provided by the user (by appropriate
1809	WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p>
1810
1811
1812	</td>
1813
1814
1815	</tr>
1816
1817
1818	<tr>
1819
1820
1821	<td style="vertical-align: top; text-align: center;">21
1822	</td>
1823
1824
1825	<td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY<br>
1826
1827
1828	(PLOT2D_XY_O)</td>
1829
1830
1831	<td style="vertical-align: top;">O<br>
1832
1833
1834	</td>
1835
1836
1837	<td style="vertical-align: top;">Binary<br>
1838
1839
1840	</td>
1841
1842
1843	<td style="vertical-align: top;">
1844
1845	<p>This file
1846	contains data of the two-dimensional horizontal
1847	cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>)
1848	in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>
1849	(the first record contains the coordinate information <tt><font style="font-size: 11pt;" size="2">dx</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">eta</font></tt><font style="font-size: 11pt;" size="2">, </font><tt><font style="font-size: 11pt;" size="2">hu</font></tt><font style="font-size: 11pt;" size="2">, <tt>ho</tt></font>,
1850	then
1851	the individual arrays follow). The data are visualized with the help of
1852	ISO2D using
1853	NAMELIST - parameter sets, which are directly written by the model to
1854	the
1855	local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
1856	and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
1857	</p>
1858
1859
1860
1861	<p>With parallel runs and choice of <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
1862	= <i>.T.</i> each processing element writes the data of
1863	its subdomain
1864	to a separate file with the name
1865	PLOT2D_XY_<processor-Id>,
1866	whereby <processor-Id> is a four digit number (e.g.
1867	PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the
1868	end
1869	of the model run they can be combined to one file readable by ISO2D
1870	with
1871	the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
1872	This tool expects the files of the individual processing
1873	elements under the names described above and outputs the combined file
1874	under the name PLOT2D_XY. Usually it is called by an appropriate OUTPUT
1875	- command (OC:) in the MRUN-configuration file. The tool writes
1876	informative messages about the actions accomplished into the job
1877	protocol (e.g., even if no files were found).
1878	By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
1879	possibly existing files of the other cross sections (xz and/or yz)
1880	and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
1881	are also combined.  </p>
1882
1883
1884
1885	<p>Further information
1886	about the output of plots of
1887	two-dimensional cross sections is found in the description of the run
1888	parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p>
1889
1890
1891	</td>
1892
1893
1894	</tr>
1895
1896
1897	<tr>
1898
1899
1900	<td style="vertical-align: top; text-align: center;">22<br>
1901
1902
1903	</td>
1904
1905
1906	<td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ<br>
1907
1908
1909	(PLOT2D_XZ_O) </td>
1910
1911
1912	<td style="vertical-align: top;">O<br>
1913
1914
1915	</td>
1916
1917
1918	<td style="vertical-align: top;">Binary<br>
1919
1920
1921	</td>
1922
1923
1924	<td style="vertical-align: top;">
1925
1926	<p>This file contains
1927	the data of the xz
1928	cross sections written by the model.  </p>
1929
1930
1931	The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
1932	applies to this file, respectively </td>
1933
1934
1935	</tr>
1936
1937
1938	<tr>
1939
1940
1941	<td style="vertical-align: top; text-align: center;">23<br>
1942
1943
1944	</td>
1945
1946
1947	<td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ<br>
1948
1949
1950	<font color="#000000">(PLOT2D_YZ_O)</font></td>
1951
1952
1953	<td style="vertical-align: top;">O<br>
1954
1955
1956	</td>
1957
1958
1959	<td style="vertical-align: top;">Binary<br>
1960
1961
1962	</td>
1963
1964
1965	<td style="vertical-align: top;">
1966
1967	<p>This file contains
1968	the data of the xz
1969	cross sections written by the model.  </p>
1970
1971
1972	The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
1973	applies to this file, respectively </td>
1974
1975
1976	</tr>
1977
1978
1979	<tr>
1980
1981
1982	<td style="vertical-align: top; text-align: center;">27<br>
1983
1984
1985	</td>
1986
1987
1988	<td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL<br>
1989
1990
1991	(PLOT2D_XY_LOCAL_O)</td>
1992
1993
1994	<td style="vertical-align: top;">O<br>
1995
1996
1997	</td>
1998
1999
2000	<td style="vertical-align: top;">Ascii/ NAMELIST<br>
2001
2002
2003	</td>
2004
2005
2006	<td style="vertical-align: top;">
2007
2008	<p>NAMELIST -
2009	parameter sets, with which the plot layout of the
2010	data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
2011	can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.
2012	This file contains the so-called local parameter set (NAMELIST - group
2013	name: &LOCAL) required by ISO2D (one parameter set for each
2014	field
2015	present at the file PLOT2D_XY). After the model run these parameter
2016	sets can be edited by the user, if neccessary.  </p>
2017
2018
2019
2020	<p>Additionally
2021	ISO2D still needs another so-called global
2022	parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>.
2023	Due to the fact that ISO2D expects global and local parameter sets on
2024	one and the same
2025	file, in fact the global parameter set first, the user has to append
2026	the
2027	contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
2028	before the call of ISO2D (e.g. by an OUTPUT-command in the
2029	MRUN-configuration file: “PLOT2D_XY_LOCAL >>
2030	PLOT2D_XY_GLOBAL”).
2031	This relatively pedantic proceeding is due to the fact that the model
2032	can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation
2033	(only then e.g. when the final value of the global ISO2D - parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
2034	is known), while the local parameter sets are written continuously
2035	to the file PLOT2D_XY_LOCAL during the run.</p>
2036
2037
2038	</td>
2039
2040
2041	</tr>
2042
2043
2044	<tr>
2045
2046
2047	<td style="vertical-align: top; text-align: center;">28<br>
2048
2049
2050	</td>
2051
2052
2053	<td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL<br>
2054
2055
2056	<font color="#000000">(PLOT2D_XZ_LOCAL_O)</font>
2057	</td>
2058
2059
2060	<td style="vertical-align: top;">O<br>
2061
2062
2063	</td>
2064
2065
2066	<td style="vertical-align: top;">Ascii/ NAMELIST<br>
2067
2068
2069	</td>
2070
2071
2072	<td style="vertical-align: top;">
2073
2074	<p>NAMELIST -
2075	parameter sets, with which the plot layout of the
2076	data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
2077	can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.
2078	</p>
2079
2080
2081
2082	<p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
2083	applies to this file, respectively. </p>
2084
2085
2086	</td>
2087
2088
2089	</tr>
2090
2091
2092	<tr>
2093
2094
2095	<td style="vertical-align: top; text-align: center;">29<br>
2096
2097
2098	</td>
2099
2100
2101	<td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL<br>
2102
2103
2104	<font color="#000000">(PLOT2D_YZ_LOCAL_O)</font></td>
2105
2106
2107	<td style="vertical-align: top;">O<br>
2108
2109
2110	</td>
2111
2112
2113	<td style="vertical-align: top;">Ascii/ NAMELIST<br>
2114
2115
2116	</td>
2117
2118
2119	<td style="vertical-align: top;">
2120
2121	<p>NAMELIST -
2122	parameter sets, with which the plot layout of the
2123	data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
2124	can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>.
2125	</p>
2126
2127
2128
2129	<p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
2130	applies to this file, respectively. </p>
2131
2132
2133	</td>
2134
2135
2136	</tr>
2137
2138
2139	<tr>
2140
2141
2142	<td style="vertical-align: top; text-align: center;">30<br>
2143
2144
2145	</td>
2146
2147
2148	<td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA<br>
2149
2150
2151	(PLOT3D_DATA_O) </td>
2152
2153
2154	<td style="vertical-align: top;">O<br>
2155
2156
2157	</td>
2158
2159
2160	<td style="vertical-align: top;">Binary<br>
2161
2162
2163	</td>
2164
2165
2166	<td style="vertical-align: top;">
2167
2168	<p>This file contains
2169	the data of the three-dimensional arrays
2170	(see <a href="chapter_4.2.html#data_output">data_output</a>)
2171	written by the model in a format readable for the visualization
2172	software AVS. Beyond that AVS
2173	needs coordinate information, which are output into the
2174	local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
2175	as well as the local files <a href="#PLOT3D_FLD">PLOT3D_FLD</a>
2176	and <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
2177	which describe the structure of the files PLOT3D_DATA and PLOT3D_COOR
2178	in the so-called AVS-FLD-format. Due to
2179	the fact that AVS expects these information in only one (so-called FLD
2180	-) file, the content of the file PLOT3D_FLD_COOR must be appended to
2181	the file PLOT3D_FLD by the user after the end of the model run (e.g.
2182	with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR
2183	>> PLOT3D_FLD</span>").  </p>
2184
2185
2186
2187	<p>With
2188	parallel runs each processing element writes the data of
2189	its subdomain to a separate file with the name
2190	PLOT3D_DATA_<Processor-Id>, where
2191	<Processor-Id> is a
2192	four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable
2193	for AVS, but after the end of the model run they can be combined to one
2194	file readable for AVS with the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
2195	This tool expects the files of the individual processing
2196	elements under the names described above and outputs the combined file
2197	into a new file PLOT3D_DATA. Usually it is called by an appropriate
2198	OUTPUT - command in the MRUN-configuration file. The tool
2199	writes informative messages about the accomplished actions into
2200	the job protocol (e.g., even if no files were
2201	found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
2202	also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>)
2203	are combined.  </p>
2204
2205
2206
2207	<p>With parallel runs the
2208	output of data of large volume is also
2209	possible in compressed form. For this purpose the initialization
2210	parameter  <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>
2211	= <i>.TRUE.</i> must be set and the desired output
2212	accuracy has to be
2213	indicated
2214	with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
2215	In favorable cases the file size can be reduced by
2216	a factor of up to 5. For the visualization of compressed data a special
2217	AVS module (<tt><font style="font-size: 11pt;" size="2">read_compressed_field</font></tt>)
2218	and a further entry in the MRUN-configuration file are needed. More
2219	details can be found in <a href="chapter_4.5.6.html">chapter
2220	4.5.6</a>.</p>
2221
2222
2223	</td>
2224
2225
2226	</tr>
2227
2228
2229	<tr>
2230
2231
2232	<td style="vertical-align: top; text-align: center;">31<br>
2233
2234
2235	</td>
2236
2237
2238	<td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR </td>
2239
2240
2241	<td style="vertical-align: top;">O<br>
2242
2243
2244	</td>
2245
2246
2247	<td style="vertical-align: top;">Binary<br>
2248
2249
2250	</td>
2251
2252
2253	<td style="vertical-align: top;">
2254
2255	<p>Coordinate
2256	information concerning
2257	the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
2258	needed by the visualization software AVS.  </p>
2259
2260
2261
2262	<p>The
2263	file PLOT3D_COOR should be saved by the user into the same
2264	permanent directory as the file PLOT3D_DATA.  </p>
2265
2266
2267
2268	<p>For
2269	parallel runs PLOT3D_COOR is written by PE0 only.</p>
2270
2271
2272	</td>
2273
2274
2275	</tr>
2276
2277
2278	<tr>
2279
2280
2281	<td style="vertical-align: top; text-align: center;">32<br>
2282
2283
2284	</td>
2285
2286
2287	<td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD </td>
2288
2289
2290	<td style="vertical-align: top;">O<br>
2291
2292
2293	</td>
2294
2295
2296	<td style="vertical-align: top;">Ascii/  <br>
2297
2298
2299	AVS-Fld </td>
2300
2301
2302	<td style="vertical-align: top;">
2303
2304	<p>AVS-fld-file
2305	describing the three-dimensional
2306	array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>,
2307	needed by the visualization software AVS.  </p>
2308
2309
2310
2311	<p>This
2312	file describes the structure of the file PLOT3D_DATA
2313	(e.g. number of arrays, array dimensions, data type etc.). It uses the
2314	so-called AVS-Fld-format. It also contains the name of the file
2315	(inclusive cycle number, but without path) under which the local file
2316	PLOT3D_DATA is saved (this is the file name given in the file
2317	connection statement of the MRUN – configuration) in the
2318	permanent
2319	directory of the user (possibly on remote computers). Under this name
2320	AVS expects the data which are to be visualized. If there is no file
2321	connection statement for PLOT3D_DATA indicated in the configuration
2322	file, that file (filename) is registered “unknown”
2323	in the file
2324	PLOT3D_FLD and the
2325	actual name must be inserted later by hand. The file PLOT3D_FLD should
2326	be saved by the user in the same permanent directory as PLOT3D_DATA, so
2327	that AVS can find the file PLOT3D_DATA without any problems. If the two
2328	files lie in different directories, then the path name of the file
2329	PLOT3D_DATA must be added.  </p>
2330
2331
2332
2333	<p>AVS-fld-files
2334	are expected by AVS to have the
2335	suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font>
2336	Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix.
2337	This suffix is
2338	attached to the permanent file names (still after
2339	possible cycle numbers) by <span style="font-weight: bold;">mrun</span>
2340	if "<span style="font-family: monospace;">fld</span>"
2341	is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column
2342	6 </a>of the file connection statement.  </p>
2343
2344
2345
2346	<p>Likewise,
2347	AVS expects information about the coordinate
2348	system underlying the arrays on this file. This information is output
2349	by the model
2350	into the local file <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
2351	whose content the user has to append to the file PLOT3D_FLD after the
2352	end of the model run (e.g. with an appropriate OUTPUT-command in the
2353	MRUN-configuration file: “cat PLOT3D_FLD_COOR
2354	>>
2355	PLOT3D_FLD”).  </p>
2356
2357
2358
2359	<p>For parallel
2360	runs, PLOT3D_FLD is produced by PE0 only.</p>
2361
2362
2363	</td>
2364
2365
2366	</tr>
2367
2368
2369	<tr>
2370
2371
2372	<td style="vertical-align: top; text-align: center;">33
2373	</td>
2374
2375
2376	<td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR </td>
2377
2378
2379	<td style="vertical-align: top;">O<br>
2380
2381
2382	</td>
2383
2384
2385	<td style="vertical-align: top;">Ascii/  <br>
2386
2387
2388	AVS-Fld </td>
2389
2390
2391	<td style="vertical-align: top;">
2392
2393	<p>File
2394	for the description of the coordinate information output
2395	by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
2396	which is needed for the visualization of three-dimensional array data
2397	by visualization-software AVS.  </p>
2398
2399
2400
2401	<p>This
2402	file describes the structure of the file PLOT3D_COOR
2403	(e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format.
2404	It also contains the name of the file (inclusive cycle number, but
2405	without path) into which the local file PLOT3D_COOR (this is the file
2406	name described in the file connection statement of the MRUN -
2407	configuration file) is output in the permanent directory of the user
2408	(possibly on remote computers). Under this name AVS expects the data
2409	which are to be visualized. If there is no file connection statement
2410	for
2411	PLOT3D_COOR indicated in the configuration file, that file is
2412	registered as "unknown" in the file
2413	PLOT3D_FLD_COOR and the actual name
2414	must be inserted later by hand.  </p>
2415
2416
2417
2418	<p>AVS
2419	expects the information contained in the file
2420	PLOT3D_FLD_COOR, as well as the remaining information about the
2421	three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>)
2422	in one and the same file. This is satisfied by appending the file
2423	PLOT3D_FLD_COOR after the end of a run are to the
2424	file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the
2425	MRUN-configuration file: “cat PLOT3D_FLD_COOR
2426	>>
2427	PLOT3D_FLD”).  </p>
2428
2429
2430
2431	<p>For parallel
2432	runs, PLOT3D_FLD_COOR is written by PE0 only.</p>
2433
2434
2435	</td>
2436
2437
2438	</tr>
2439
2440
2441	<tr>
2442
2443
2444	<td style="vertical-align: top; text-align: center;">
2445
2446	<p align="center">40  </p>
2447
2448
2449
2450	<p align="center">and/or  <br>
2451
2452
2453	possibly  </p>
2454
2455
2456
2457	<p align="center">40-49</p>
2458
2459
2460	</td>
2461
2462
2463	<td style="vertical-align: top;">
2464
2465	<p><a name="PLOT1D_DATA"></a>PLOT1D_DATA<br>
2466
2467
2468	(PLOT1D_DATA_O) </p>
2469
2470
2471
2472	<p>and/or  <br>
2473
2474
2475	possibly  </p>
2476
2477
2478	PLOT1D_DATA_0  <br>
2479
2480
2481	PLOT1D_DATA_1<br>
2482
2483
2484	...<br>
2485
2486
2487	<br>
2488
2489
2490	(PLOT1D_DATA<span style="font-weight: bold;">_O</span>_0 <br>
2491
2492
2493	<font color="#000000">PLOT1D_DATA<span style="font-weight: bold;">_O</span>_1 <br>
2494
2495
2496	</font><font color="#000000">...)<span style="font-weight: bold;"></span> </font></td>
2497
2498
2499	<td style="vertical-align: top;">O </td>
2500
2501
2502	<td style="vertical-align: top;">Ascii </td>
2503
2504
2505	<td style="vertical-align: top;">
2506
2507	<p>This file contains
2508	data (possibly horizontally and/or
2509	temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>)
2510	written by the model in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
2511	It is created only if <a href="chapter_4.2.html#data_output_format">data_output_format</a>
2512	= <span style="font-style: italic;">'profil'</span>
2513	is assigned. This file's format is suitable to be read by the plot
2514	software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
2515	Each data point of the profiles is output in one single line (1st
2516	column: height in m, 2nd column: value of the respective quantity).
2517	Within the file, data
2518	of the individual profiles are located one behind the other. The order
2519	of the data in the file follows the order used in the assignment for <b>data_output_pr</b>
2520	(<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,…
2521	means that the file starts with the data of the u-component profile,
2522	followed by the v-component profile, etc.). </p>
2523
2524
2525
2526	<p><br>
2527
2528
2529	The data can only be visualized with <span style="font-weight: bold;">profil</span>
2530	using NAMELIST-parameter sets, which are saved by the
2531	model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.
2532	</p>
2533
2534
2535
2536	<p>The profile data written to the file are described
2537	with the
2538	run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
2539	Plots produced with these data using the parameter file PLOT1D_PAR do
2540	not have to contain all these profiles. The profiles which can be drawn
2541	in the plot are described with run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>.
2542	By subsequent editing of the file PLOT1D_PAR all profiles can be
2543	plotted (also the basic layout of the plots can be
2544	changed). For orientation, each profile existing on the file
2545	PLOT1D_DATA, starts with a comment line, which indicates the
2546	presented variable and the output time. The text of these comment
2547	lines is used as a legend in the plot. The very first line of the file
2548	is a
2549	comment line, containing information about the used model version, the
2550	run identifier (base file name + number of the respective restart
2551	run), the name of the executing computer, as well as the date and time
2552	of the beginning of the run. At the end of this comment line is the
2553	name
2554	of the subdomain, to which the profiles belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
2555	By default, the profiles present averages of the total model domain. If
2556	the model has to produce profiles for other subdomains beyond that, up
2557	to 9 further files (units No. 41-49) are created, whereby the number of
2558	the respective subdomain is attached
2559	to the file name (e.g. PLOT1D_DATA_1). The name of the file with the
2560	data of the total
2561	domain in this case reads PLOT1D_DATA_0.  </p>
2562
2563
2564
2565	<p>For
2566	presentation in the same plot, profile data of the restart
2567	runs can be attached to existing data of preceding runs of a job chain.
2568	One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
2569	in the file connection statement. The model produces a parameter file
2570	(PLOT1D_PAR) for these combined data, if the run parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
2571	= <i>.T</i>. If this is omitted, then the parameter file
2572	gives
2573	wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
2574	= .T.</span> and "<span style="font-family: monospace;">tra</span>"
2575	must be specified together)!  </p>
2576
2577
2578
2579	<p>Further
2580	information about output of
2581	vertical profile data is given in the description of the run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.</p>
2582
2583
2584	</td>
2585
2586
2587	</tr>
2588
2589
2590	<tr>
2591
2592
2593	<td style="vertical-align: top; text-align: center;">80
2594	</td>
2595
2596
2597	<td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/<br>
2598
2599
2600	(PARTICLE_INFOS<span style="font-weight: bold;">_O</span>/)
2601	</td>
2602
2603
2604	<td style="vertical-align: top;">O </td>
2605
2606
2607	<td style="vertical-align: top;">Ascii </td>
2608
2609
2610	<td style="vertical-align: top;">This
2611	file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles
2612	package</a>). It contains statistical informations about the
2613	number of
2614	particles used and about the number of particles exchanged between each
2615	single PE. These informations are output after every timestep if
2616	switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>.
2617	</td>
2618
2619
2620	</tr>
2621
2622
2623	<tr>
2624
2625
2626	<td style="vertical-align: top; text-align: center;">81
2627	</td>
2628
2629
2630	<td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR<br>
2631
2632
2633	(PLOTSP_X_PAR_O)</td>
2634
2635
2636	<td style="vertical-align: top;">O </td>
2637
2638
2639	<td style="vertical-align: top;">Ascii/<br>
2640
2641
2642	NAMELIST </td>
2643
2644
2645	<td style="vertical-align: top;">This
2646	file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
2647	package</a>). It contains the NAMELIST parameter set, with which
2648	the
2649	layout of a plot
2650	of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
2651	can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br>
2652
2653
2654
2655	<p>It contains the so-called RAHMEN (frame)- and
2656	CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or
2657	&CROSS</span>)
2658	needed by <span style="font-weight: bold;">profil</span>.
2659	The user can edit these parameter sets (and thus all details of the
2660	plot layout) after the run.<br>
2661
2662
2663	</p>
2664
2665
2666
2667	<p>By default,
2668	for one quantity, all spectra at different heights
2669	are plotted into a single panel. Different colors and line styles are
2670	used for each height. Panels of up to four quantities are arranged on
2671	one page in two lines (and two columns). More quantities are plotted on
2672	additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
2673	additional pages will be plotted for each single output time. </p>
2674
2675
2676	</td>
2677
2678
2679	</tr>
2680
2681
2682	<tr>
2683
2684
2685	<td style="vertical-align: top; text-align: center;">82<br>
2686
2687
2688	</td>
2689
2690
2691	<td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA<br>
2692
2693
2694	(PLOTSP_X_DATA_O) </td>
2695
2696
2697	<td style="vertical-align: top;">O<br>
2698
2699
2700	</td>
2701
2702
2703	<td style="vertical-align: top;">Ascii<br>
2704
2705
2706	</td>
2707
2708
2709	<td style="vertical-align: top;">This
2710	file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
2711	package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
2712	in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
2713	The data can only be visualized with <span style="font-weight: bold;">profil</span>
2714	using NAMELIST parameter sets, which are written by
2715	the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
2716
2717
2718	<br>
2719
2720
2721	Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
2722	for actual plotting, this file contains all data of spectra specified
2723	by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br>
2724
2725
2726	<br>
2727
2728
2729	<font>Each data point of a spectrum is output in a
2730	single line
2731	(1st column:
2732	wavenumber, 2nd column: spectral coefficient). If spectra are to be
2733	calculated and output for more than one height (see </font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font><font>),
2734	the spectral coefficients for the further heights can be found in the
2735	subsequent columns. </font>The order
2736	of the data in the file follows the order used in the assignment for <span style="font-style: italic;"></span><span style="font-style: italic;"></span><a href="chapter_4.2.html#data_output_sp">data_output_sp</a>.<br>
2737
2738
2739	<br>
2740
2741
2742	For orientation, a header of comment lines (one for each height level)
2743	is placed in front of the spectral data of each quantity. They indicate
2744	the respective quantity and the output time. The text of these comment
2745	lines is used as a legend in the plot. </td>
2746
2747
2748	</tr>
2749
2750
2751	<tr>
2752
2753
2754	<td style="vertical-align: top; text-align: center;">83<br>
2755
2756
2757	</td>
2758
2759
2760	<td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR<br>
2761
2762
2763	(PLOTSP_Y_PAR_O)</td>
2764
2765
2766	<td style="vertical-align: top;">O<br>
2767
2768
2769	</td>
2770
2771
2772	<td style="vertical-align: top;">Ascii<br>
2773
2774
2775	</td>
2776
2777
2778	<td style="vertical-align: top;">This
2779	file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
2780	package</a>). It contains the NAMELIST parameter set, with which
2781	the
2782	layout of a plot
2783	of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
2784	can be steered, if these data are plotted with the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.<br>
2785
2786
2787	<br>
2788
2789
2790	For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
2791
2792
2793	</td>
2794
2795
2796	</tr>
2797
2798
2799	<tr>
2800
2801
2802	<td style="vertical-align: top; text-align: center;">84<br>
2803
2804
2805	</td>
2806
2807
2808	<td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA<br>
2809
2810
2811	(PLOTSP_Y_DATA_O)</td>
2812
2813
2814	<td style="vertical-align: top;">O<br>
2815
2816
2817	</td>
2818
2819
2820	<td style="vertical-align: top;">Ascii<br>
2821
2822
2823	</td>
2824
2825
2826	<td style="vertical-align: top;">This
2827	file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
2828	package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
2829	in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
2830	The data can only be visualized with <span style="font-weight: bold;">profil</span>
2831	using NAMELIST parameter sets, which are written by
2832	the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
2833
2834
2835	<br>
2836
2837
2838	For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td>
2839
2840
2841	</tr>
2842
2843
2844	<tr>
2845
2846
2847	<td style="vertical-align: top; text-align: center;">85<br>
2848
2849
2850	</td>
2851
2852
2853	<td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/<br>
2854
2855
2856	(PARTICLE_DATA<span style="font-weight: bold;">_O</span>/)</td>
2857
2858
2859	<td style="vertical-align: top;">O<br>
2860
2861
2862	</td>
2863
2864
2865	<td style="vertical-align: top;">Binary<br>
2866
2867
2868	</td>
2869
2870
2871	<td style="vertical-align: top;">This
2872	file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
2873	package</a>) and contains all particle data for one or several
2874	output
2875	times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
2876
2877
2878	<br>
2879
2880
2881	The first record of this file contains an identification string (PALM
2882	version number, run identifier, etc., 80 characters long). The second
2883	record also contains a version string (80 characters long) followed by
2884	two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>).
2885	Then, for each
2886	output time, two records follow, where the first one gives some general
2887	information (numbers of particles, etc.) and the second one contains
2888	the actual particle data. A FORTRAN TYPE structure is used for storing
2889	the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span>
2890	for the detailed format.</td>
2891
2892
2893	</tr>
2894
2895
2896	<tr>
2897
2898
2899	<td style="vertical-align: top; text-align: center;">90</td>
2900
2901
2902	<td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
2903
2904
2905	DATA_IN/</td>
2906
2907
2908	<td style="vertical-align: top;">I<br>
2909
2910
2911	</td>
2912
2913
2914	<td style="vertical-align: top;">Binary<br>
2915
2916
2917	</td>
2918
2919
2920	<td style="vertical-align: top;">Binary
2921	data, which are read in by the model at the beginning
2922	of a restart run (see <a href="chapter_3.3.html">chapter
2923	3.3</a>). The appropriate file must have been written by the
2924	preceding
2925	job of the job chain (see <a href="#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>).
2926	This file is needed if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
2927	package</a>) and contains all particle informations (particle
2928	positions, velocities, etc.) from the end of the preceding run.
2929	Concerning runs on
2930	several processors it has to be noted that each processing element
2931	reads its own file and that the file content is processor-dependent.
2932	The
2933	number of processors which can be used must not be changed during a job
2934	chain and/or if a job chain is continued. <br>
2935
2936
2937	<br>
2938
2939
2940	The first record of this file contains a version number (four character
2941	string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>,
2942	see end of
2943	file <span style="font-family: monospace;">advec_particles.f90</span>).
2944	This number has to
2945	agree with the version number of the subroutine which is reading the
2946	file
2947	(<span style="font-family: monospace;">init_parrticles.f90</span>)
2948	in
2949	case of a restart run. Otherwise the model run
2950	is aborted. Version numbers are changed whenever new code revisions
2951	require a change of the file format. Some general informations like the
2952	number of particles stored in the file, the number of particle groups,
2953	etc.. are stored in the second record. The third record includes the
2954	particles to be released at the source and the fourth record contains
2955	all current particles. In case that particle tails are used (see <a href="chapter_4.2.html#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>),
2956	a further record may follow, which contains the particle tail
2957	informations. A FORTRAN TYPE structure is used for storing the particle
2958	attributes. For detailed informations about the file format see the
2959	corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span>
2960	.<br>
2961
2962
2963	</td>
2964
2965
2966	</tr>
2967
2968
2969	<tr>
2970
2971
2972	<td style="vertical-align: top; text-align: center;">90<br>
2973
2974
2975	</td>
2976
2977
2978	<td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
2979
2980
2981	DATA_OUT/</td>
2982
2983
2984	<td style="vertical-align: top;">O<br>
2985
2986
2987	</td>
2988
2989
2990	<td style="vertical-align: top;">Binary<br>
2991
2992
2993	</td>
2994
2995
2996	<td style="vertical-align: top;">Binary
2997	data, which are output at the end of the
2998	run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
2999	3.3</a>) for the initialization. This output file is then read as
3000	file <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.
3001	The file is only written if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
3002	package</a>). For a more detailed description of the file
3003	structure see <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
3004
3005
3006	</tr>
3007
3008
3009	<tr>
3010
3011
3012	<td style="vertical-align: top; text-align: center;">90<br>
3013
3014
3015	</td>
3016
3017
3018	<td style="vertical-align: top;">
3019
3020	<p><a name="PLOT1D_PAR"></a>PLOT1D_PAR<br>
3021
3022
3023	(PLOT1D_PAR_O) </p>
3024
3025
3026
3027	<p>and/or  <br>
3028
3029
3030	possibly  </p>
3031
3032
3033
3034	<p>PLOT1D_PAR_0  <br>
3035
3036
3037	PLOT1D_PAR_1  <br>
3038
3039
3040
3041	.  <br>
3042
3043
3044
3045	.  <br>
3046
3047
3048
3049	.  <br>
3050
3051
3052	PLOT1D_PAR_9</p>
3053
3054
3055
3056	<p></p>
3057
3058
3059
3060	<p>(PLOT1D_PAR<span style="font-weight: bold;">_O</span>_0
3061	<br>
3062
3063
3064	PLOT1D_PAR<font color="#000000"><span style="font-weight: bold;">_O</span></font>_1
3065	<br>
3066
3067
3068
3069	.  <br>
3070
3071
3072
3073	.  <br>
3074
3075
3076
3077	.  <br>
3078
3079
3080	PLOT1D_PAR<font color="#000000"><span style="font-weight: bold;">_O</span></font>_9)</p>
3081
3082
3083	</td>
3084
3085
3086	<td style="vertical-align: top;">O<br>
3087
3088
3089	</td>
3090
3091
3092	<td style="vertical-align: top;">Ascii/
3093	NAMELIST<br>
3094
3095
3096	</td>
3097
3098
3099	<td style="vertical-align: top;">
3100
3101	<p>NAMELIST parameter set, with which the layout of a plot
3102	of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a>
3103	can be steered, if these data are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
3104	</p>
3105
3106
3107
3108	<p>This file contains the so-called RAHMEN (frame)-
3109	and
3110	CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&RAHMEN and/or
3111	&CROSS</span>)
3112	needed by <span style="font-weight: bold;">profil</span>.
3113	These parameter sets (and thus all details of the plot layout) can be
3114	edited after the model run by the user. By default, all profiles of one
3115	variable saved at different times are drawn into one panel. Different
3116	colors are used for each output time. Which profiles are drawn
3117	into which plane and how these planes are arranged on the
3118	plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
3119	<a href="chapter_4.2.html#profile_columns">profile_columns</a>
3120	and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.
3121	</p>
3122
3123
3124
3125	<p>The file PLOT1D_PAR is created by the model
3126	briefly before
3127	the end of a run. If a model run crashes uncontrolled (run time
3128	errors or CPU - time exceeded), this file is usually missing, although
3129	profile data were saved to the file PLOT1D_DATA.  </p>
3130
3131
3132
3133	<p>If
3134	the model has to create profiles for different subdomains
3135	(see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
3136	further files are created, whereby the file name includes the number of
3137	the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of
3138	the file with NAMELIST parameters of the total domain is
3139	PLOT1D_PAR_0.  </p>
3140
3141
3142
3143	<p>For presentation in the
3144	same plot, profile data of the restart
3145	runs can be appended to existing data of preceding runs of a job chain.
3146	One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
3147	in the file connection statement for PLOT1D_DATA. The model produces
3148	a parameter file PLOT1D_PAR for these combined data, if the run
3149	parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
3150	= <i>.T</i>. If this is omitted, then the parameter file
3151	gives
3152	wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
3153	= .T.</span> and "<span style="font-family: monospace;">tra</span>"
3154	must be specified together)!</p>
3155
3156
3157	</td>
3158
3159
3160	</tr>
3161
3162
3163	<tr>
3164
3165
3166	<td style="vertical-align: top; text-align: center;">90<br>
3167
3168
3169	</td>
3170
3171
3172	<td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL<br>
3173
3174
3175	(PLOT2D_XY_GLOBAL_O)</td>
3176
3177
3178	<td style="vertical-align: top;">O<br>
3179
3180
3181	</td>
3182
3183
3184	<td style="vertical-align: top;">Ascii/  <br>
3185
3186
3187	NAMELIST</td>
3188
3189
3190	<td style="vertical-align: top;">
3191
3192	<p>NAMELIST
3193	parameter set, with which the plot layout
3194	of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
3195	can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
3196	This file contains the so-called global parameter set (NAMELIST - group
3197	name: &GLOBAL) needed by <span style="font-weight: bold;">iso2d</span>.
3198	This parameter set can be edited
3199	after the model run by the user. By default, the arrays are drawn using
3200	isolines and each array
3201	will be drawn onto a separate page (thus no color shading
3202	presentation, no vector arrows, streamlines etc.).  </p>
3203
3204
3205
3206	<p>Additionally <span style="font-weight: bold;">iso2d</span>
3207	needs the so-called local parameter
3208	sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
3209	Due to the fact that <span style="font-weight: bold;">iso2d</span>
3210	expects global and local parameter sets on one and the same
3211	file, in fact the global parameter set first, the user has to append
3212	the contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
3213	before call of <span style="font-weight: bold;">iso2d</span>
3214	(e.g. by
3215	an OUTPUT - command in the MRUN -
3216	configuration file: “cat PLOT2D_XY_LOCAL >>
3217	PLOT2D_XY_GLOBAL”).
3218	This
3219	relatively pedantic proceedure is due to the fact that the model can
3220	create the file PLOT2D_XY_GLOBAL only at the end of the simulation
3221	(only then, when the final value of the global <span style="font-weight: bold;">iso2d</span>-parameter <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#PLANZ">planz</a>
3222	is known), while the local parameter sets are written continuously
3223	to the file PLOT2D_XY_LOCAL during the run. Since the file
3224	PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit
3225	90 is used, which is also used for other files.</p>
3226
3227
3228	</td>
3229
3230
3231	</tr>
3232
3233
3234	<tr>
3235
3236
3237	<td style="vertical-align: top; text-align: center;">90<br>
3238
3239
3240	</td>
3241
3242
3243	<td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL<br>
3244
3245
3246	(PLOT2D_XZ_GLOBAL_O)</td>
3247
3248
3249	<td style="vertical-align: top;">O<br>
3250
3251
3252	</td>
3253
3254
3255	<td style="vertical-align: top;">Ascii/  <br>
3256
3257
3258	NAMELIST</td>
3259
3260
3261	<td style="vertical-align: top;">
3262
3263	<p>NAMELIST
3264	parameter set, with which the plot layout of the data
3265	in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
3266	can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
3267	</p>
3268
3269
3270
3271	<p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
3272	applies to this file, respectively.</p>
3273
3274
3275	</td>
3276
3277
3278	</tr>
3279
3280
3281	<tr>
3282
3283
3284	<td style="vertical-align: top; text-align: center;">90<br>
3285
3286
3287	</td>
3288
3289
3290	<td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL<br>
3291
3292
3293	(PLOT2D_YZ_GLOBAL_O)</td>
3294
3295
3296	<td style="vertical-align: top;">O<br>
3297
3298
3299	</td>
3300
3301
3302	<td style="vertical-align: top;">Ascii/  <br>
3303
3304
3305	NAMELIST</td>
3306
3307
3308	<td style="vertical-align: top;">
3309
3310	<p>NAMELIST
3311	parameter set, with which the plot layout of the data
3312	in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
3313	can be steered, if they are visualized with the plot program <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
3314	</p>
3315
3316
3317
3318	<p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
3319	applies to this file, respectively.</p>
3320
3321
3322	</td>
3323
3324
3325	</tr>
3326
3327
3328	<tr>
3329
3330
3331	<td style="vertical-align: top; text-align: center;">90</td>
3332
3333
3334	<td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td>
3335
3336
3337	<td style="vertical-align: top;">I</td>
3338
3339
3340	<td style="vertical-align: top;">Ascii</td>
3341
3342
3343	<td>Two-dimensional <font color="#000000">topography
3344	height information</font>
3345	in m.<br>
3346
3347
3348	In case of  <a href="chapter_4.1.html#topography">topography</a>
3349	= <span style="font-style: italic;">'read_from_file'</span>
3350	the subroutine <span style="font-family: Cumberland AMT;">init_grid</span> reads
3351	the topography height information in m for each grid point in
3352	a free floating point format. The data on file are laid out naturally,
3353	i.e. in W-E orientation horizontally and in S-N orientation vertically,
3354	they must thus be organized as follows:<br>
3355
3356
3357
3358	<ul>
3359
3360
3361	<li>each
3362	line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li>
3363
3364
3365	<li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the
3366	bottom line for <span style="font-style: italic;">j = 0</span>
3367	(South),</li>
3368
3369
3370	<li>individual data must be separated by at
3371	least one blank.</li>
3372
3373
3374
3375	</ul>
3376
3377
3378	Layout sketch:<br>
3379
3380
3381	<span style="font-family: Cumberland AMT;">
3382
3383	N<br>
3384
3385
3386	(0,ny)   </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny)
3387	</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny)
3388	... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny)
3389	<span style="font-family: Times New Roman,Times,serif;"></span></span></font><font color="#000000"> top of file</font><font color="#000000"><span style="font-family: Cumberland AMT;"><span style="font-family: Times New Roman,Times,serif;"></span></span></font><br>
3390
3391
3392	<font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3393	(0,ny-1) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-1) </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-1)
3394	... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1)  <br>
3395
3396
3397	</span></font></font><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">W
3398	(0,ny-2) </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny-2) </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny-2)
3399	... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2)   E<br>
3400
3401
3402	</span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3403
3404	:<br>
3405
3406
3407
3408
3409	:<br>
3410
3411
3412	</span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3413
3414	(0,0)    </span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0)
3415	</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0)
3416	... </span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0)
3417	</span></font></font></font><font color="#000000"> bottom of file</font><br>
3418
3419
3420	<font color="#000000"><span style="font-family: Cumberland AMT;">
3421
3422	S<br></span></font>
3423
3424
3425	<br><span style="font-family: Arial;"></span><font color="#000000">Example for a 50m building surrounded by a 12.5m podium on flat ground:<br>
3426
3427
3428	<span style="font-family: Cumberland AMT;"></span><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3429	0    0    0    0    0
3430	0    0    0    0
3431	0    0    0    0<br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">    0 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5    0    0
3432	</span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"><br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> </span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">    0 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5    0    0
3433	</span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"><br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> </span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3434	0 12.5 12.5   50   50   50   50   50
3435	50 12.5 12.5    0    0
3436	<br></span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3437	0 12.5 12.5   50   50   50   50
3438	50   50 12.5 12.5    0    0
3439	<br></span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3440	0 12.5 12.5   50   50   50   50
3441	50   50 12.5 12.5    0    0
3442	</span></font></font></font></font><br><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">   0 12.5 12.5   50   50   50   50   50   50 12.5 12.5    0    0 <br>
3443	</span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3444	0 12.5 12.5   50   50   50   50
3445	50   50 12.5 12.5    0    0
3446	</span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"><br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3447	0 12.5 12.5   50   50   50   50
3448	50   50 12.5 12.5    0    0
3449	<br></span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">    0 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5    0    0
3450	</span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"><br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> </span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">    0 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5 12.5    0    0
3451	</span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"><br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"> </span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">
3452	0    0    0    0    0
3453	0    0    0    0
3454	0    0    0    0<br></span></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;"></span></font></font></font></font><br>
3455
3456
3457	These data must exactly match the horizontal grid. <font color="#000000">Due to the staggered grid the topography will be displaced by -0.5 <a href="chapter_4.1.html#dx">dx</a> in x-direction and -0.5 <a href="chapter_4.1.html#dy">dy</a> in y-direction.</font><br>
3458
3459
3460	Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a>
3461	to allow different data formats.</td>
3462
3463
3464
3465
3466
3467	</tr>
3468
3469
3470	<tr>
3471
3472
3473	<td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td>
3474
3475
3476	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF<br>
3477
3478
3479	(DATA_2D_XY_NETCDF_O)</font></td>
3480
3481
3482	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3483
3484
3485	<td style="vertical-align: top;"><font color="#000000">Binary/<br>
3486
3487
3488	NetCDF-<br>
3489
3490
3491	format</font></td>
3492
3493
3494	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file
3495	contains data of the two-dimensional horizontal
3496	cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
3497	in NetCDF format. The data in this file can be visualized by any
3498	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3499
3500
3501	<br>
3502
3503
3504	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></td>
3505
3506
3507
3508
3509
3510	</tr>
3511
3512
3513	<tr>
3514
3515
3516	<td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td>
3517
3518
3519	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF<br>
3520
3521
3522	(DATA_2D_XZ_NETCDF_O)</font></td>
3523
3524
3525	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3526
3527
3528	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3529
3530
3531	NetCDF-<br>
3532
3533
3534	format</font></font></td>
3535
3536
3537	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3538	contains data of the two-dimensional vertical (xz)
3539	cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
3540	in NetCDF format. The data in this file can be visualized by any
3541	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3542
3543
3544	<br>
3545
3546
3547	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3548
3549
3550
3551
3552
3553	</tr>
3554
3555
3556	<tr>
3557
3558
3559	<td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td>
3560
3561
3562	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF<br>
3563
3564
3565	(DATA_2D_YZ_NETCDF_O)</font></td>
3566
3567
3568	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3569
3570
3571	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3572
3573
3574	NetCDF-<br>
3575
3576
3577	format</font></font></td>
3578
3579
3580	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3581	contains data of the two-dimensional vertical
3582	(yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
3583	in NetCDF format. The data in this file can be visualized by any
3584	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3585
3586
3587	<br>
3588
3589
3590	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3591
3592
3593
3594
3595
3596	</tr>
3597
3598
3599	<tr>
3600
3601
3602	<td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td>
3603
3604
3605	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF<br>
3606
3607
3608	(DATA_1D_PR_NETCFD_O)</font></td>
3609
3610
3611	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3612
3613
3614	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3615
3616
3617	NetCDF-<br>
3618
3619
3620	format</font></font></td>
3621
3622
3623	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3624	contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>)
3625	in NetCDF format. The data in this file can be visualized by any
3626	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3627
3628
3629	<br>
3630
3631
3632	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3633
3634
3635
3636
3637
3638	</tr>
3639
3640
3641	<tr>
3642
3643
3644	<td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td>
3645
3646
3647	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF<br>
3648
3649
3650	(DATA_1D_TS_NETCDF_O)</font></td>
3651
3652
3653	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3654
3655
3656	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3657
3658
3659	NetCDF-<br>
3660
3661
3662	format</font></font></td>
3663
3664
3665	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3666	contains data of the timeseries (see <a href="chapter_4.2.html#dt_dots">dt_dots</a>)
3667	in NetCDF format. The data in this file can be visualized by any
3668	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3669
3670
3671	<br>
3672
3673
3674	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3675
3676
3677
3678
3679
3680	</tr>
3681
3682
3683	<tr>
3684
3685
3686	<td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td>
3687
3688
3689	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF<br>
3690
3691
3692	(DATA_3D_NETCDF_O)</font></td>
3693
3694
3695	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3696
3697
3698	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3699
3700
3701	NetCDF-<br>
3702
3703
3704	format</font></font></td>
3705
3706
3707	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3708	contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
3709	in NetCDF format. The data in this file can be visualized by any
3710	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3711
3712
3713	<br>
3714
3715
3716	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3717
3718
3719
3720
3721
3722	</tr>
3723
3724
3725	<tr>
3726
3727
3728	<td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td>
3729
3730
3731	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF<br>
3732
3733
3734	(DATA_1D_SP_NETCDF_O)</font></td>
3735
3736
3737	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3738
3739
3740	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3741
3742
3743	NetCDF-<br>
3744
3745
3746	format</font></font></td>
3747
3748
3749	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3750	contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>)
3751	in NetCDF format. The data in this file can be visualized by any
3752	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3753
3754
3755	<br>
3756
3757
3758	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3759
3760
3761
3762
3763
3764	</tr>
3765
3766
3767	<tr>
3768
3769
3770	<td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td>
3771
3772
3773	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/<br>
3774
3775
3776	(DATA_PRT_NETCDF<span style="font-weight: bold;">_O</span>/)</font></td>
3777
3778
3779	<td style="vertical-align: top;"><font color="#000000">I/O</font></td>
3780
3781
3782	<td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
3783
3784
3785	NetCDF-<br>
3786
3787
3788	format</font></font></td>
3789
3790
3791	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3792	contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>)
3793	in NetCDF format. The data in this file can be visualized by any
3794	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3795
3796
3797	<br>
3798
3799
3800	More detailed informations about the PALM-NetCDF-output are given in <a href="../app/chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3801
3802
3803
3804
3805
3806	</tr>
3807
3808
3809	<tr>
3810
3811
3812	<td style="vertical-align: top; text-align: center;">109</td>
3813
3814
3815	<td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF<br>
3816
3817
3818	(DATA_1D_PTS_NETCDF_O)</td>
3819
3820
3821	<td align="left" valign="top">I/O</td>
3822
3823
3824	<td align="left" valign="top">Binary/<br>
3825
3826
3827	NetCDF-<br>
3828
3829
3830	format</td>
3831
3832
3833	<td align="left" valign="top">This
3834	file contains data of the timeseries of particle quantities (<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">see <a href="chapter_4.2.html#dt_prel">dt_prel</a>)
3835	in NetCDF format. </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data
3836	in this file can be visualized by any graphic software which provides a
3837	NetCDF interface (e.g. <span style="font-weight: bold;">NCL
3838	</span>or<span style="font-weight: bold;">
3839	ferret</span>).
3840	For a list of available output quantities see </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"> <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>.</font></font></font></font></font><br>
3841
3842
3843	<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
3844
3845
3846	</font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of
3847	using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
3848	seperate time series are output for each of the groups. The long names
3849	of the variables in the NetCDF file containing the respective
3850	timeseries all end with the string</font><span style="font-style: italic; font-family: monospace;">' PG ##'</span><font face="Thorndale">, where ## is the number of the particle
3851	group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
3852
3853
3854	<br>
3855
3856
3857	</font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More detailed informations about the
3858	PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter
3859	4.5.1</a>.</font></font></font></font></td>
3860
3861
3862
3863
3864
3865	</tr>
3866
3867
3868	<tr>
3869
3870
3871	<td style="text-align: center; vertical-align: top;">111</td>
3872
3873
3874	<td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF<br>
3875
3876
3877	(DATA_2D_XY_AV_NETCDF_O)</td>
3878
3879
3880	<td style="vertical-align: top;">I/O</td>
3881
3882
3883	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
3884
3885
3886	NetCDF-<br>
3887
3888
3889	format</font></font></font></td>
3890
3891
3892	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file
3893	contains data of the temporally averaged two-dimensional horizontal
3894	cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
3895	in NetCDF format. The data in this file can be visualized by any
3896	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3897
3898
3899	<br>
3900
3901
3902	More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></td>
3903
3904
3905
3906
3907
3908	</tr>
3909
3910
3911	<tr>
3912
3913
3914	<td style="text-align: center; vertical-align: top;">112</td>
3915
3916
3917	<td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF<br>
3918
3919
3920	(DATA_2D_XZ_AV_NETCDF_O)</td>
3921
3922
3923	<td style="vertical-align: top;">I/O</td>
3924
3925
3926	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
3927
3928
3929	NetCDF-<br>
3930
3931
3932	format</font></font></font></td>
3933
3934
3935	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file
3936	contains data of the temporally
3937	averaged two-dimensional vertical (xz)
3938	cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
3939	in NetCDF format. The data in this file can be visualized by any
3940	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3941
3942
3943	<br>
3944
3945
3946	More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></font></td>
3947
3948
3949
3950
3951
3952	</tr>
3953
3954
3955	<tr>
3956
3957
3958	<td style="text-align: center; vertical-align: top;">113</td>
3959
3960
3961	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF<br>
3962
3963
3964	(DATA_2D_YZ_AV_NETCDF_O)</font></td>
3965
3966
3967	<td style="vertical-align: top;">I/O</td>
3968
3969
3970	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
3971
3972
3973	NetCDF-<br>
3974
3975
3976	format</font></font></font></td>
3977
3978
3979	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file
3980	contains data of the temporally
3981	averaged two-dimensional vertical
3982	(yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
3983	in NetCDF format. The data in this file can be visualized by any
3984	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
3985
3986
3987	<br>
3988
3989
3990	More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></font></td>
3991
3992
3993
3994
3995
3996	</tr>
3997
3998
3999	<tr>
4000
4001
4002	<td style="text-align: center; vertical-align: top;">116</td>
4003
4004
4005	<td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF<br>
4006
4007
4008	(DATA_3D_AV_NETCDF_O)</font></td>
4009
4010
4011	<td style="vertical-align: top;">I/O</td>
4012
4013
4014	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
4015
4016
4017	NetCDF-<br>
4018
4019
4020	format</font></font></font></td>
4021
4022
4023	<td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file
4024	contains data of the temporally
4025	averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
4026	in NetCDF format. The data in this file can be visualized by any
4027	graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
4028
4029
4030	<br>
4031
4032
4033	More detailed informations about the PALM-NetCDF-output are given in <a href="chapter_4.5.1.html">chapter  4.5.1</a>.</font></font></font></font></td>
4034
4035
4036
4037
4038
4039	</tr>
4040
4041
4042
4043	</tbody>
4044	</table>
4045
4046
4047	<font color="#000000"><br>
4048
4049
4050	</font><br>
4051
4052
4053	<font color="#000080"><font color="#000080"><a href="chapter_3.3.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_3.5.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>
4054
4055
4056
4057	<br>
4058
4059
4060
4061	<span style="font-style: italic;">Last change:</span>
4062	$Id: chapter_3.4.html 134 2007-11-21 07:28:38Z letzel $<br>
4063
4064
4065	</font><br>
4066
4067
4068	</body></html>

Note: See TracBrowser for help on using the repository browser.

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |