Home

Context Navigation

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

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

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

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

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

Property svn:keywords set to Id

File size: 105.0 KB

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

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

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |