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

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

Redefine initial nzb_local as the actual total size of topography (later the
extent of topography in nzb_local is reduced by 1dx at the E topography walls
and by 1dy at the N topography walls to form the basis for nzb_s_inner);
for consistency redefine 'single_building' case.

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