Home


About us
PALM
PALM-4U
Installation
Release notes
Documentation
Getting Help
Gallery
Developers area

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

Last change on this file since 37 was 5, checked in by raasch, 18 years ago

html-documentation added
File size: 109.0 KB
RevLine 
[5]1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html>
3<head>
4
5
6
7
8
9 
10 
11 
12 
13 
14  <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
15  <title>chapter_3.4</title>
16</head>
17
18<body>
19
20
21
22
23
24<h3 style="line-height: 100%;"><font color="#000000">3.4 Input and
25output files</font></h3>
26
27
28
29
30
31<p style="line-height: 100%;"><font color="#000000"></font></p>
32
33<p style="line-height: 100%;"><font color="#000000">The model works
34with a set of files, which are all located in the temporary working
35directory and which are either expected at the beginning of the run
36(the so-called input files) or which are
37produced during the run and/or at the end of the simulation (output
38files).</font><font color="#800000">
39<font color="#000000">The following table lists all default files
40addressed by the model. They are arranged according to the
41associated FORTRAN unit (unit number).</font> </font><font color="#000000">The
42unit 90 is used for different files, which are opened only briefly
43and uniquely in the model and closed directly afterwards.
44Unit numbers 101 - 109, 111 - 113, and 116&nbsp;refer to data files which have NetCDF format.
45These are not opened by a FORTRAN-OPEN-statement but by a corresponding
46NetCDF call (NF90_CREATE or NF90_OPEN). These files are only created on
47machines where a NetCDF library is available.<br>
48
49</font></p>
50
51
52<p style="line-height: 100%;"><font color="#000000">The file
53names described in the list correspond to the names indicated in the
54respective OPEN instruction, i.e. the files are expected and saved
55under these names in the temporary working directory of the model. By
56default, file names are always written in capital letters. The
57third column indicates whether it is an input or output file (I
58and/or O). The NetCDF files can be both input and output files (I/O).
59If restart jobs shall append data to an existing NetCDF file (created
60by a previous job of the job chain), the respective file has to be
61given as an input file (see also <a href="../app/chapter_4.5.1.html">chapter 4.5.1</a> which gives more details about the PALM-NetCDF-output).</font> </p>
62
63<p style="line-height: 100%;"> </p>
64
65
66
67
68
69
70<p style="line-height: 100%;"><font color="#000000">On parallel
71computers many of the files are read and/or written by the central
72processing element 0 (PE0) only. These files have processor-independent
73content (and therefore they can be read or written by other
74PEs just as well). However, certain files have processor-dependent
75content. For the binary output of data for restart runs (local file
76<a href="#BINOUT">BINOUT</a>),
77for example, <font color="#000000">each PE outputs only the data of
78its subdomain. So each processing element writes
79into its own file with its own file name. These files lie in a
80subdirectory of the temporary working directory. Their names are build
81off from the underline ("_ ") and the four digit
82processor ID. The data written for restart runs would be e.g. on the
83files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc.
84Such files, which have processor-dependent content on parallel
85computers, are marked in the following list by the fact, that to the
86file name a line (&rdquo;/&ldquo;) is attached. If appropriate output
87files are to be copied through <b>mrun</b> to permanent files, and/or
88files with processor-dependent content are supposed to be copied as
89input files into the temporary working directory of the model, you have
90to indicate a special file attribute in the appropriate file
91connection statement </font>(see <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#arpe">arpe</a>,
92<a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#flpe">flpe</a>
93<font color="#000000">in the <b>mrun </b>description).</font><font color="#800000">
94</font><font color="#000000">Then the permanent file name will be
95interpreted as a directory name, in which the input files are
96expected and/or to which output files are written. The file names in
97these directories are always named _0000, _0001, _0002 etc. </font>
98</font></p>
99
100
101
102
103
104<font color="#000000"><font color="#000000">For internal use,
105the model may open a set of further files, which are not
106defined by the user but contain no usable information and
107therefore are not included in this list. <br>
108
109
110
111
112
113<br>
114
115
116
117
118
119</font>
120<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2">
121
122
123
124
125
126  <tbody>
127
128
129
130
131
132    <tr valign="top">
133
134
135
136
137
138      <td width="8%">
139     
140     
141     
142     
143     
144      <p><font size="4"><b>Unit</b></font></p>
145
146
147
148
149
150      </td>
151
152
153
154
155
156      <td width="12%">
157     
158     
159     
160     
161     
162      <p><font size="4"><b>Name</b></font></p>
163
164
165
166
167
168      </td>
169
170
171
172
173
174      <td width="4%">
175     
176     
177     
178     
179     
180      <p><font size="4"><b>I/O</b></font></p>
181
182
183
184
185
186      </td>
187
188
189
190
191
192      <td width="9%">
193     
194     
195     
196     
197     
198      <p><font size="4"><b>Format</b></font></p>
199
200
201
202
203
204      </td>
205
206
207
208
209
210      <td colspan="1" width="67%">
211     
212     
213     
214     
215     
216      <p><font size="4"><b>Description/contents</b></font></p>
217
218
219
220
221
222      </td>
223
224
225
226
227
228    </tr>
229
230
231
232
233
234    <tr valign="top">
235
236
237
238
239
240      <td style="text-align: center;" width="8%"> 11<br>
241
242
243
244
245
246      </td>
247
248
249
250
251
252      <td width="12%">
253     
254     
255     
256     
257     
258      <p><a name="PARIN"></a>PARIN</p>
259
260
261
262
263
264      </td>
265
266
267
268
269
270      <td width="4%">
271     
272     
273     
274     
275     
276      <p align="center">I</p>
277
278
279
280
281
282      </td>
283
284
285
286
287
288      <td style="width: 9%;">
289     
290     
291     
292     
293     
294      <p>ASCII/&nbsp; <br>
295
296
297
298
299
300NAMELIST</p>
301
302
303
304
305
306      </td>
307
308
309
310
311
312      <td colspan="1" width="67%">
313     
314     
315     
316     
317     
318      <p><font color="#000000">Parameter for model steering. This file
319is needed by the model in each case. Its content and structure is
320described in detail in</font> <a href="chapter_4.0.html">chapter
3214.0</a>. <a href="chapter_4.4.html">Chapter
3224.4</a> <font color="#000000">shows a simple example. </font> </p>
323
324
325
326
327
328     
329     
330     
331     
332     
333
334
335
336
337      </td>
338
339
340
341
342
343    </tr>
344
345
346
347
348
349    <tr valign="top">
350
351
352
353
354
355      <td style="text-align: center;" width="8%">
356     
357     
358     
359     
360     
361      <p align="center">13</p>
362
363
364
365
366
367      </td>
368
369
370
371
372
373      <td width="12%">
374     
375     
376     
377     
378     
379      <p><a name="BININ"></a>BININ/</p>
380
381
382
383
384
385      </td>
386
387
388
389
390
391      <td width="4%">
392     
393     
394     
395     
396     
397      <p align="center">I</p>
398
399
400
401
402
403      </td>
404
405
406
407
408
409      <td width="9%">
410     
411     
412     
413     
414     
415      <p>Binary</p>
416
417
418
419
420
421      </td>
422
423
424
425
426
427      <td colspan="1" width="67%">
428     
429     
430     
431     
432     
433      <p>Binary data, which are read in by the model at the beginning
434of a restart run (see <a href="chapter_3.3.html">chapter
4353.3</a>). The appropriate file must have been written by the preceding
436job of the job chain (see <a href="#BINOUT">BINOUT</a>).
437This file contains the initial parameters (see <a href="chapter_4.1.html">chapter
4384.1</a>) of the job chain, arrays of the prognostic and diagnostic
439variables as well as those parameters and variables for plots of
440horizontally averaged vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>),
441which have been determined by the job chain so far. Concerning runs on
442several processors it has to be noted that each processing element
443reads its own file and the file content is processor-dependent. The
444number of processors which can be used must not be changed during a job
445chain and/or if a job chain is continued.&nbsp; </p>
446
447
448
449
450
451     
452     
453     
454     
455     
456      <p>Knowledge of the file structure is usually not necessary,
457because the file is produced and also read again by the model, but it
458can be useful for error determination in case of read errors .
459Therefore the file structure is described in the following.&nbsp; </p>
460
461
462
463
464
465     
466     
467     
468     
469     
470      <p>The first record of this file contains a version number (ten
471character string) of the subroutine, which, which output the data that
472follows (write_var_list.f90). This number has to
473agree with the version number subroutine which is reading the file
474(read_var_list.f90) in case of a restart run. Otherwise the model run
475is aborted. Version numbers are changed whenever new code revisions
476require a change of the file format.&nbsp; </p>
477
478
479
480
481
482     
483     
484     
485     
486     
487      <p>Starting from the second record, all initial parameters follow
488(exception: <a href="chapter_4.1.html#initializing_actions">initializing_actions</a>),
489whereby each parameter fills two records. In the first record the name
490of the parameter is saved as a character string (30 characters long,
491short names are filled by trailing blanks, longer names are cut off at
492the end), in the second record the value (or the values) of the
493parameter follow. The sequence of parameters on the file may be
494arbitrary, however the first and second variable must be <a href="chapter_4.1.html#nz">nz</a>
495and <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>.
496If a variable with unknown name is found the model run is
497aborted.&nbsp; </p>
498
499
500
501
502
503     
504     
505     
506     
507     
508      <p>At the end of the initial parameters a record with the string "<i>***
509end ***</i>"follows (filled up with trailing blanks up to a length of
51030 characters).&nbsp; </p>
511
512
513
514
515
516     
517     
518     
519     
520     
521      <p>Afterwards the fields of the prognostic and diagnostic
522variables follow. This part of the file also begins with a record
523consisting of a character string of length 10, which contains the
524version number of the subroutine that wrote the arrays that follow
525(write_3d_binary.f90). It must agree with the number of the reading
526subroutine (read_3d_binary.f90).&nbsp; </p>
527
528
529
530
531
532     
533     
534     
535     
536     
537      <p>The following record contains the number of processors which
538were used in the model run producing this file, the processor ID of the
539special processor, which creates the file, as well as the lower and
540upper array indices of the subdomain belonging to this processing
541element. If no complete agreement with the values of the current model
542run exists, then this is aborted. This examination must be made in
543particular on parallel computers, because the jobs of a job chain
544always have to use the same number of processors and the same virtual
545processor grid.&nbsp; </p>
546
547
548
549
550
551     
552     
553     
554     
555     
556      <p>After these tests the individual arrays as well as parameters
557and variables for plots of horizontally averaged vertical profiles
558follow. Like the initialization parameters, they consist of two
559records. In the first record, the name of the array or the variable
560(character string, consisting of 20 characters, filled with trailing
561blanks) is located, in the second one its values follow. The sequence
562of the individual variables may be arbitrary again. The parameters for
563the plot and the respective variables are only read in if for the run
564parameter <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
565= <i>.TRUE</i> is selected, otherwise they will be skipped.&nbsp; </p>
566
567
568
569
570
571     
572     
573     
574     
575     
576      <p>At the end of the file there has to be a record with the
577character string "<span style="font-style: italic;"></span><i>*** end
578***</i>"(filled up with trailing blanks up to a length of 20
579characters).</p>
580
581
582
583
584
585      </td>
586
587
588
589
590
591    </tr>
592
593
594
595
596
597    <tr valign="top">
598
599
600
601
602
603      <td style="text-align: center;" width="8%">
604     
605     
606     
607     
608     
609      <p align="center">14</p>
610
611
612
613
614
615      </td>
616
617
618
619
620
621      <td width="12%">
622     
623     
624     
625     
626     
627      <p><a name="BINOUT"></a>BINOUT/</p>
628
629
630
631
632
633      </td>
634
635
636
637
638
639      <td width="4%">
640     
641     
642     
643     
644     
645      <p align="center">O</p>
646
647
648
649
650
651      </td>
652
653
654
655
656
657      <td width="9%">
658     
659     
660     
661     
662     
663      <p>Binary</p>
664
665
666
667
668
669      </td>
670
671
672
673
674
675      <td colspan="1" width="67%">
676     
677     
678     
679     
680     
681      <p>Binary data, which are written by the model at the end of the
682run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
6833.3</a>) for the initialization. This output file is then read in as
684file <a href="#BININ">BININ</a>.
685It contains the initial parameters (see <a href="chapter_4.1.html">chapter
6864.1</a>) of the model run, arrays of the prognostic and diagnostic
687variables as well as those parameters determined so far during a job
688chain and variables for plots of horizontally averaged vertical
689profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
690With runs on several processors it has to be noted that each processing
691element writes its own file and the file content is
692processor-dependent. A specification of the file format can be found in
693the
694description of the file <a href="#BININ">BININ</a>.&nbsp; </p>
695
696
697
698
699
700     
701     
702     
703     
704     
705      <p>The file BINOUT is written by the model only if, with the help
706of the <b>mrun</b>-configuration file, the <font face="Thorndale, serif">value</font> <span style="font-family: monospace;">true</span> is assigned for the
707environment
708variable <span style="font-size: 10pt; font-family: monospace;">write_binary</span>
709(see <a href="chapter_3.3.html">chapter
7103.3</a>).&nbsp; </p>
711
712
713
714
715
716     
717     
718     
719     
720     
721      <p>With large grid point numbers the file BINOUT (or the
722files residing in directory BINOUT/) will be very large and should
723be stored (if available) on the archive system of the remote computer.</p>
724
725
726
727
728
729      </td>
730
731
732
733
734
735    </tr>
736
737
738
739
740
741    <tr>
742
743
744
745
746
747      <td style="vertical-align: top; text-align: center;">15<br>
748
749
750
751
752
753      </td>
754
755
756
757
758
759      <td style="vertical-align: top;"><a name="RUN_CONTROL"></a>RUN_CONTROL</td>
760
761
762
763
764
765      <td style="vertical-align: top;">O</td>
766
767
768
769
770
771      <td style="vertical-align: top;">Ascii</td>
772
773
774
775
776
777      <td colspan="1" width="67%">
778     
779     
780     
781     
782     
783      <p>This file contains the so-called time step control output of
784the model. At certain temporal intervals, which are described by the
785run
786parameter <a href="chapter_4.1.html#dt_run_control">dt_run_control</a>,
787a line with the values of certain control parameters is written into
788this
789file. Additionally, such a control line is always written, whenever the
790time step of the model changes. All data and quantities always refer to
791the entire model domain.&nbsp; </p>
792
793
794
795
796
797     
798     
799     
800     
801     
802      <p>If the 1D-model is switched on for the initialization of the
8033D-models, then control lines are likewise written into this file at
804certain temporal intervals (see <a href="chapter_4.1.html#dt_run_control_1d">dt_run_control_1d</a>).&nbsp;
805      </p>
806
807
808
809
810
811     
812     
813     
814     
815     
816      <p>By default, the file RUN_CONTROL only lists information
817about the selected model parameters at the beginning of the
818initial run. These informations are written at the beginnning of a run.
819They correspond to those of the file <a href="#HEADER">HEADER</a>
820(however without data concerning the consumed CPU time, because these
821are
822only known at the end of a run). With the run parameter <a href="chapter_4.2.html#force_print_header">force_print_header</a>
823it can be achieved that this information is also written at the
824beginning of the file RUN_CONTROL at restart runs.&nbsp; </p>
825
826
827
828
829
830     
831     
832     
833     
834     
835      <p>The individual columns of the 1D - time step control output
836have the following meaning (listed by the respective heading of the
837appropriate
838column in the file):&nbsp; <br>
839
840
841
842
843
844      </p>
845
846
847
848
849
850     
851     
852     
853     
854     
855      <table style="text-align: left; width: 100%;" cellpadding="2">
856
857
858
859
860
861        <tbody>
862
863
864
865
866
867          <tr>
868
869
870
871
872
873            <td style="vertical-align: top;">ITER.</td>
874
875
876
877
878
879            <td style="vertical-align: top;">Number of time steps
880accomplished so far</td>
881
882
883
884
885
886          </tr>
887
888
889
890
891
892          <tr>
893
894
895
896
897
898            <td style="vertical-align: top;">HH:MM:SS</td>
899
900
901
902
903
904            <td style="vertical-align: top;">Time (in hours: minutes:
905seconds)</td>
906
907
908
909
910
911          </tr>
912
913
914
915
916
917          <tr>
918
919
920
921
922
923            <td style="vertical-align: top;">DT</td>
924
925
926
927
928
929            <td style="vertical-align: top;">Time step (in s)</td>
930
931
932
933
934
935          </tr>
936
937
938
939
940
941          <tr>
942
943
944
945
946
947            <td style="vertical-align: top;">UMAX</td>
948
949
950
951
952
953            <td style="vertical-align: top;">Maximum absolute wind
954velocity
955(u-component) (in m/s)</td>
956
957
958
959
960
961          </tr>
962
963
964
965
966
967          <tr>
968
969
970
971
972
973            <td style="vertical-align: top;">VMAX</td>
974
975
976
977
978
979            <td style="vertical-align: top;">Maximum absolute wind
980velocity
981(v-component) (in m/s)</td>
982
983
984
985
986
987          </tr>
988
989
990
991
992
993          <tr>
994
995
996
997
998
999            <td style="vertical-align: top;">U *</td>
1000
1001
1002
1003
1004
1005            <td style="vertical-align: top;">Friction velocity (<font color="#000000">in </font>m/s)</td>
1006
1007
1008
1009
1010
1011          </tr>
1012
1013
1014
1015
1016
1017          <tr>
1018
1019
1020
1021
1022
1023            <td style="vertical-align: top;">ALPHA</td>
1024
1025
1026
1027
1028
1029            <td style="vertical-align: top;">Angle of the wind vector
1030(to the x-axis) at the top of the
1031Prandtl layer (k=1) (<font color="#000000">in </font>degrees)</td>
1032
1033
1034
1035
1036
1037          </tr>
1038
1039
1040
1041
1042
1043          <tr>
1044
1045
1046
1047
1048
1049            <td style="vertical-align: middle;">ENERG.</td>
1050
1051
1052
1053
1054
1055            <td style="vertical-align: top;">Kinetic energy of the
10561D-model (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
1057averaged over all grid points</td>
1058
1059
1060
1061
1062
1063          </tr>
1064
1065
1066
1067
1068
1069       
1070       
1071       
1072       
1073       
1074        </tbody>
1075     
1076     
1077     
1078     
1079     
1080      </table>
1081
1082
1083
1084
1085
1086     
1087     
1088     
1089     
1090     
1091      <p>&nbsp;
1092The individual columns of the 3D - time step control output
1093have the following meaning (listed by the respective heading of the
1094appropriate
1095column in the file):<br>
1096
1097
1098
1099
1100
1101      </p>
1102
1103
1104
1105
1106
1107     
1108     
1109     
1110     
1111     
1112      <table style="text-align: left; width: 100%;" cellpadding="2">
1113
1114
1115
1116
1117
1118        <tbody>
1119
1120
1121
1122
1123
1124          <tr>
1125
1126
1127
1128
1129
1130            <td style="vertical-align: top;">RUN</td>
1131
1132
1133
1134
1135
1136            <td style="vertical-align: top;">Serial-number of the job
1137in the job chain. The initial
1138run has the number 0, restart runs accordingly have larger numbers.</td>
1139
1140
1141
1142
1143
1144          </tr>
1145
1146
1147
1148
1149
1150          <tr>
1151
1152
1153
1154
1155
1156            <td style="vertical-align: top;">ITER.</td>
1157
1158
1159
1160
1161
1162            <td style="vertical-align: top;">Number of time steps
1163accomplished since starting time t=0 of
1164the initial run.</td>
1165
1166
1167
1168
1169
1170          </tr>
1171
1172
1173
1174
1175
1176          <tr>
1177
1178
1179
1180
1181
1182            <td style="vertical-align: top;">HH:MM:SS</td>
1183
1184
1185
1186
1187
1188            <td style="vertical-align: top;">Time (<font color="#000000">in
1189            </font>hours: minutes:
1190seconds) since starting time t=0 of the
1191initial run.</td>
1192
1193
1194
1195
1196
1197          </tr>
1198
1199
1200
1201
1202
1203          <tr>
1204
1205
1206
1207
1208
1209            <td style="vertical-align: top;">DT (E)</td>
1210
1211
1212
1213
1214
1215            <td style="vertical-align: top;">Time step (<font color="#000000">in </font>s). The
1216following character indicates whether the
1217time
1218step is limited by the advection criterion (A) or the diffusion
1219criterion (D). After changes of the time step a further character
1220follows,
1221which indicates with which time step procedure the changed time step
1222was accomplished (<span style="font-family: monospace;">L:</span>
1223Leapfrog, <span style="font-family: monospace;">E:</span> Euler). This
1224does
1225not apply for the default Runge-Kutta timestep scheme.</td>
1226
1227
1228
1229
1230
1231          </tr>
1232
1233
1234
1235
1236
1237          <tr>
1238
1239
1240
1241
1242
1243            <td style="vertical-align: top;">UMAX</td>
1244
1245
1246
1247
1248
1249            <td style="vertical-align: top;">Maximum absolute wind
1250velocity (u-component) (<font color="#000000">in </font>m/s). If at
1251the
1252appropriate output time a random disturbance was added to the
1253horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
1254the character D will appear directly after the velocity value.</td>
1255
1256
1257
1258
1259
1260          </tr>
1261
1262
1263
1264
1265
1266          <tr>
1267
1268
1269
1270
1271
1272            <td style="vertical-align: top;">VMAX</td>
1273
1274
1275
1276
1277
1278            <td style="vertical-align: top;">Maximum absolute wind
1279velocity (v-component) (<font color="#000000">in </font>m/s). If at
1280the
1281appropriate output time a random disturbance was added to the
1282horizontal velocity field (see <a href="chapter_4.2.html#create_disturbances">create_disturbances</a>),
1283the character D will appear directly after the velocity value.</td>
1284
1285
1286
1287
1288
1289          </tr>
1290
1291
1292
1293
1294
1295          <tr>
1296
1297
1298
1299
1300
1301            <td style="vertical-align: top;">WMAX</td>
1302
1303
1304
1305
1306
1307            <td style="vertical-align: top;">Maximum absolute wind
1308velocity (w-component) (<font color="#000000">in </font>m/s).</td>
1309
1310
1311
1312
1313
1314          </tr>
1315
1316
1317
1318
1319
1320          <tr>
1321
1322
1323
1324
1325
1326            <td style="vertical-align: top;">U *</td>
1327
1328
1329
1330
1331
1332            <td style="vertical-align: top;">Horizontal average of the
1333friction velocity (<font color="#000000">in </font>m/s).</td>
1334
1335
1336
1337
1338
1339          </tr>
1340
1341
1342
1343
1344
1345          <tr>
1346
1347
1348
1349
1350
1351            <td style="vertical-align: top;">W *</td>
1352
1353
1354
1355
1356
1357            <td style="vertical-align: top;">Convective velocity scale
1358(<font color="#000000">in </font>m/s). The assumed boundary layer
1359height is determined via the heat flux minimum criterion.</td>
1360
1361
1362
1363
1364
1365          </tr>
1366
1367
1368
1369
1370
1371          <tr>
1372
1373
1374
1375
1376
1377            <td style="vertical-align: top;">THETA *</td>
1378
1379
1380
1381
1382
1383            <td style="vertical-align: top;">Characteristic temperature
1384of the Prandtl - layer (<font color="#000000">in </font>K).</td>
1385
1386
1387
1388
1389
1390          </tr>
1391
1392
1393
1394
1395
1396          <tr>
1397
1398
1399
1400
1401
1402            <td style="vertical-align: top;">Z_I</td>
1403
1404
1405
1406
1407
1408            <td style="vertical-align: top;">Height of the convective
1409boundary layer (<font color="#000000">in </font>m), determined via
1410the criterion of the heat flux minimum.</td>
1411
1412
1413
1414
1415
1416          </tr>
1417
1418
1419
1420
1421
1422          <tr>
1423
1424
1425
1426
1427
1428            <td style="vertical-align: middle;">ENERG.</td>
1429
1430
1431
1432
1433
1434            <td style="vertical-align: top;">Average resolved total
1435energy of the flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
1436normalized with the total number of grid points.</td>
1437
1438
1439
1440
1441
1442          </tr>
1443
1444
1445
1446
1447
1448          <tr>
1449
1450
1451
1452
1453
1454            <td style="vertical-align: middle;">DISTENERG</td>
1455
1456
1457
1458
1459
1460            <td style="vertical-align: top;">Average resolved
1461disturbance energy of flow field (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>),
1462normalized with the total number of grid points.</td>
1463
1464
1465
1466
1467
1468          </tr>
1469
1470
1471
1472
1473
1474          <tr>
1475
1476
1477
1478
1479
1480            <td style="vertical-align: top;">DIVOLD</td>
1481
1482
1483
1484
1485
1486            <td style="vertical-align: top;"><font color="#000000">Divergence
1487of the velocity field (sum of
1488the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) before call of the pressure solver,
1489normalized with the total number of grid points.</font></td>
1490
1491
1492
1493
1494
1495          </tr>
1496
1497
1498
1499
1500
1501          <tr>
1502
1503
1504
1505
1506
1507            <td style="vertical-align: top;">DIVNEW</td>
1508
1509
1510
1511
1512
1513            <td style="vertical-align: top;"><font color="#000000">Divergence
1514of the velocity field (sum of
1515the absolute values) (</font><font color="#000000">in </font><font color="#000000">1/s) after call of the pressure solver, normalized</font>
1516with the total number of grid points.</td>
1517
1518
1519
1520
1521
1522          </tr>
1523
1524
1525
1526
1527
1528          <tr>
1529
1530
1531
1532
1533
1534            <td style="vertical-align: top;">UMAX (KJI)</td>
1535
1536
1537
1538
1539
1540            <td style="vertical-align: top;">Indices of the grid point
1541with the maximum absolute
1542u-component of the wind velocity (sequence: k, j, i).</td>
1543
1544
1545
1546
1547
1548          </tr>
1549
1550
1551
1552
1553
1554          <tr>
1555
1556
1557
1558
1559
1560            <td style="vertical-align: top;">VMAX (KJI)</td>
1561
1562
1563
1564
1565
1566            <td style="vertical-align: top;">Indices of the grid point
1567with the maximum absolute
1568v-component of the wind velocity (sequence: k, j, i).</td>
1569
1570
1571
1572
1573
1574          </tr>
1575
1576
1577
1578
1579
1580          <tr>
1581
1582
1583
1584
1585
1586            <td style="vertical-align: top;">WMAX (KJI)</td>
1587
1588
1589
1590
1591
1592            <td style="vertical-align: top;">Indices of the grid point
1593with the maximum absolute
1594w-component of the wind velocity (sequence: k, j, i).</td>
1595
1596
1597
1598
1599
1600          </tr>
1601
1602
1603
1604
1605
1606          <tr>
1607
1608
1609
1610
1611
1612            <td style="vertical-align: top;">ADVECX</td>
1613
1614
1615
1616
1617
1618            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
1619coordinate system has been moved in
1620x-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
1621
1622
1623
1624
1625
1626          </tr>
1627
1628
1629
1630
1631
1632          <tr>
1633
1634
1635
1636
1637
1638            <td style="vertical-align: top;">ADVECY</td>
1639
1640
1641
1642
1643
1644            <td style="vertical-align: top;">Distance (<font color="#000000">in </font>km) the
1645coordinate system has been moved in
1646y-direction with Galilei-Transformation switched on (see <a href="chapter_4.1.html#galilei_transformation">galilei_transformation</a>).</td>
1647
1648
1649
1650
1651
1652          </tr>
1653
1654
1655
1656
1657
1658       
1659       
1660       
1661       
1662       
1663        </tbody>
1664     
1665     
1666     
1667     
1668     
1669      </table>
1670
1671
1672
1673
1674
1675      </td>
1676
1677
1678
1679
1680
1681    </tr>
1682
1683
1684
1685
1686
1687    <tr>
1688
1689
1690
1691
1692
1693      <td style="vertical-align: top; text-align: center;">16<br>
1694
1695
1696
1697
1698
1699      </td>
1700
1701
1702
1703
1704
1705      <td style="vertical-align: top;"><a name="LIST_PROFIL"></a>LIST_PROFIL
1706      </td>
1707
1708
1709
1710
1711
1712      <td style="vertical-align: top;">O<br>
1713
1714
1715
1716
1717
1718      </td>
1719
1720
1721
1722
1723
1724      <td style="vertical-align: top;">Ascii<br>
1725
1726
1727
1728
1729
1730      </td>
1731
1732
1733
1734
1735
1736      <td style="vertical-align: top;">This file contains horizontally
1737(and possibly temporally)
1738averaged vertical profiles of some model variables. The quantities
1739saved are set model-internally and can not be determined by the user.
1740At each output time (see <a href="chapter_4.2.html#dt_dopr_listing">dt_dopr_listing</a>)
1741two tables are written to the file consecutively. The first contains
1742variables which are defined on the scalar / u-v-grid-levels, the
1743second table contains variables which are defined on the w-grid-levels.
1744If subdomains were defined with the initialization parameter <a href="chapter_4.1.html#statistic_regions">statistic_regions </a>for
1745additional statistic evaluation, then the tables
1746described above are written for each individual subdomain. The name of
1747the respective subdomain (see <a href="chapter_4.3.html#region">region</a>)
1748appears in the header of the respective table. <br>
1749
1750
1751
1752
1753
1754In each case the tables consist of a header, followed by the
1755profiles arranged next to each other in columns. The header contains
1756some basic information of the respective run (model version, run
1757identifier consisting of
1758basic file name and number of the job in the job chain, executing
1759computer, date, time of the beginning of the run, name of the
1760subdomain, output time, kind of averaging). On the u-v-level the
1761following columns are written: <br>
1762
1763
1764
1765
1766
1767     
1768     
1769     
1770     
1771     
1772      <table style="text-align: left; width: 100%;" cellpadding="2">
1773
1774
1775
1776
1777
1778        <tbody>
1779
1780
1781
1782
1783
1784          <tr>
1785
1786
1787
1788
1789
1790            <td style="text-align: left; vertical-align: middle;">k<br>
1791
1792
1793
1794
1795
1796            </td>
1797
1798
1799
1800
1801
1802            <td style="text-align: left; vertical-align: middle;">Vertical
1803grid point index.</td>
1804
1805
1806
1807
1808
1809          </tr>
1810
1811
1812
1813
1814
1815          <tr>
1816
1817
1818
1819
1820
1821            <td style="text-align: left; vertical-align: middle;">zu<br>
1822
1823
1824
1825
1826
1827            </td>
1828
1829
1830
1831
1832
1833            <td style="text-align: left; vertical-align: middle;">Height
1834of the grid point
1835level (<font color="#000000">in </font>m).</td>
1836
1837
1838
1839
1840
1841          </tr>
1842
1843
1844
1845
1846
1847          <tr>
1848
1849
1850
1851
1852
1853            <td style="text-align: left; vertical-align: middle;">u<br>
1854
1855
1856
1857
1858
1859            </td>
1860
1861
1862
1863
1864
1865            <td style="text-align: left; vertical-align: middle;">u-component
1866of the wind
1867velocity (<font color="#000000">in </font>m/s).</td>
1868
1869
1870
1871
1872
1873          </tr>
1874
1875
1876
1877
1878
1879          <tr>
1880
1881
1882
1883
1884
1885            <td style="text-align: left; vertical-align: middle;">du<br>
1886
1887
1888
1889
1890
1891            </td>
1892
1893
1894
1895
1896
1897            <td style="text-align: left; vertical-align: middle;">Deviation
1898of the
1899u-component from the initial profile at the
1900time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
1901
1902
1903
1904
1905
1906          </tr>
1907
1908
1909
1910
1911
1912          <tr>
1913
1914
1915
1916
1917
1918            <td style="text-align: left; vertical-align: middle;">v<br>
1919
1920
1921
1922
1923
1924            </td>
1925
1926
1927
1928
1929
1930            <td style="text-align: left; vertical-align: middle;">v-component
1931of the wind
1932velocity (<font color="#000000">in </font>m/s).</td>
1933
1934
1935
1936
1937
1938          </tr>
1939
1940
1941
1942
1943
1944          <tr>
1945
1946
1947
1948
1949
1950            <td style="text-align: left; vertical-align: middle;">dv<br>
1951
1952
1953
1954
1955
1956            </td>
1957
1958
1959
1960
1961
1962            <td style="text-align: left; vertical-align: middle;">Deviation
1963of the
1964v-component from the initial profile at the
1965time t=0 (initialization profile) (<font color="#000000">in </font>m/s).</td>
1966
1967
1968
1969
1970
1971          </tr>
1972
1973
1974
1975
1976
1977          <tr>
1978
1979
1980
1981
1982
1983            <td style="text-align: left; vertical-align: middle;">pt&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1984            <br>
1985
1986
1987
1988
1989
1990            </td>
1991
1992
1993
1994
1995
1996            <td style="text-align: left; vertical-align: middle;">Potential
1997temperature (<font color="#000000">in </font>K).</td>
1998
1999
2000
2001
2002
2003          </tr>
2004
2005
2006
2007
2008
2009          <tr>
2010
2011
2012
2013
2014
2015            <td style="text-align: left; vertical-align: middle;">dpt<br>
2016
2017
2018
2019
2020
2021            </td>
2022
2023
2024
2025
2026
2027            <td style="text-align: left; vertical-align: middle;">Deviation
2028of potential
2029temperature from the initial profile at
2030the time t=0 (initialization profile) (<font color="#000000">in </font>K).</td>
2031
2032
2033
2034
2035
2036          </tr>
2037
2038
2039
2040
2041
2042          <tr>
2043
2044
2045
2046
2047
2048            <td style="text-align: left; vertical-align: middle;">e<br>
2049
2050
2051
2052
2053
2054            </td>
2055
2056
2057
2058
2059
2060            <td style="text-align: left; vertical-align: middle;">Turbulent
2061kinetic energy
2062(subgrid-scale) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
2063
2064
2065
2066
2067
2068          </tr>
2069
2070
2071
2072
2073
2074          <tr>
2075
2076
2077
2078
2079
2080            <td style="text-align: left; vertical-align: middle;">Km<br>
2081
2082
2083
2084
2085
2086            </td>
2087
2088
2089
2090
2091
2092            <td style="text-align: left; vertical-align: middle;">Turbulent
2093diffusion
2094coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
2095
2096
2097
2098
2099
2100          </tr>
2101
2102
2103
2104
2105
2106          <tr>
2107
2108
2109
2110
2111
2112            <td style="text-align: left; vertical-align: middle;">Kh<br>
2113
2114
2115
2116
2117
2118            </td>
2119
2120
2121
2122
2123
2124            <td style="text-align: left; vertical-align: middle;">Turbulent
2125diffusion
2126coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
2127
2128
2129
2130
2131
2132          </tr>
2133
2134
2135
2136
2137
2138          <tr>
2139
2140
2141
2142
2143
2144            <td style="text-align: left; vertical-align: middle;">l<br>
2145
2146
2147
2148
2149
2150            </td>
2151
2152
2153
2154
2155
2156            <td style="text-align: left; vertical-align: middle;">Mixing
2157length (<font color="#000000">in </font>m).</td>
2158
2159
2160
2161
2162
2163          </tr>
2164
2165
2166
2167
2168
2169          <tr>
2170
2171
2172
2173
2174
2175            <td style="vertical-align: top;"><br>
2176
2177
2178
2179
2180
2181            </td>
2182
2183
2184
2185
2186
2187            <td style="vertical-align: top;"><br>
2188
2189
2190
2191
2192
2193            </td>
2194
2195
2196
2197
2198
2199          </tr>
2200
2201
2202
2203
2204
2205       
2206       
2207       
2208       
2209       
2210        </tbody>
2211     
2212     
2213     
2214     
2215     
2216      </table>
2217
2218
2219
2220
2221
2222On the w-level the following columns are written:<br>
2223
2224
2225
2226
2227
2228      <br>
2229
2230
2231
2232
2233
2234     
2235     
2236     
2237     
2238     
2239      <table style="text-align: left; width: 100%;" cellpadding="2">
2240
2241
2242
2243
2244
2245        <tbody>
2246
2247
2248
2249
2250
2251          <tr>
2252
2253
2254
2255
2256
2257            <td style="vertical-align: middle;">k<br>
2258
2259
2260
2261
2262
2263            </td>
2264
2265
2266
2267
2268
2269            <td style="vertical-align: middle;">Vertical grid point
2270index.</td>
2271
2272
2273
2274
2275
2276          </tr>
2277
2278
2279
2280
2281
2282          <tr>
2283
2284
2285
2286
2287
2288            <td style="vertical-align: middle;">zw<br>
2289
2290
2291
2292
2293
2294            </td>
2295
2296
2297
2298
2299
2300            <td style="vertical-align: middle;">Height of the grid
2301point
2302level (<font color="#000000">in </font>m).</td>
2303
2304
2305
2306
2307
2308          </tr>
2309
2310
2311
2312
2313
2314          <tr>
2315
2316
2317
2318
2319
2320            <td style="vertical-align: middle;">w'pt'</td>
2321
2322
2323
2324
2325
2326            <td style="vertical-align: middle;">Vertical subgrid-scale
2327kinematic heat flux (<font color="#000000">in </font>K m/s).</td>
2328
2329
2330
2331
2332
2333          </tr>
2334
2335
2336
2337
2338
2339          <tr>
2340
2341
2342
2343
2344
2345            <td style="vertical-align: middle;">wpt</td>
2346
2347
2348
2349
2350
2351            <td style="vertical-align: middle;">Vertical total (
2352subgrid-scale + resolved)
2353kinematic heat flux (<font color="#000000">in </font>K m/s).</td>
2354
2355
2356
2357
2358
2359          </tr>
2360
2361
2362
2363
2364
2365          <tr>
2366
2367
2368
2369
2370
2371            <td style="vertical-align: middle;">w'u'</td>
2372
2373
2374
2375
2376
2377            <td style="vertical-align: middle;">u-component of the
2378vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
2379
2380
2381
2382
2383
2384          </tr>
2385
2386
2387
2388
2389
2390          <tr>
2391
2392
2393
2394
2395
2396            <td style="vertical-align: middle;">wu</td>
2397
2398
2399
2400
2401
2402            <td style="vertical-align: middle;">u-component of the
2403total
2404vertical momentum flux (
2405subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
2406
2407
2408
2409
2410
2411          </tr>
2412
2413
2414
2415
2416
2417          <tr>
2418
2419
2420
2421
2422
2423            <td style="vertical-align: middle;">w'v'</td>
2424
2425
2426
2427
2428
2429            <td style="vertical-align: middle;">v-component of the
2430vertical subgrid-scale momentum flux (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
2431
2432
2433
2434
2435
2436          </tr>
2437
2438
2439
2440
2441
2442          <tr>
2443
2444
2445
2446
2447
2448            <td style="vertical-align: middle;">wv</td>
2449
2450
2451
2452
2453
2454            <td style="vertical-align: middle;">v-component of the
2455total
2456vertical momentum flux (
2457subgrid-scale + resolved) (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
2458
2459
2460
2461
2462
2463          </tr>
2464
2465
2466
2467
2468
2469       
2470       
2471       
2472       
2473       
2474        </tbody>
2475     
2476     
2477     
2478     
2479     
2480      </table>
2481
2482
2483
2484
2485
2486      <br>
2487
2488
2489
2490
2491
2492      </td>
2493
2494
2495
2496
2497
2498    </tr>
2499
2500
2501
2502
2503
2504    <tr>
2505
2506
2507
2508
2509
2510      <td style="vertical-align: top; text-align: center;">17 </td>
2511
2512
2513
2514
2515
2516      <td style="vertical-align: top;"><a name="LIST_PROFIL_1D"></a>LIST_PROFIL_1D
2517      </td>
2518
2519
2520
2521
2522
2523      <td style="vertical-align: top;">O </td>
2524
2525
2526
2527
2528
2529      <td style="vertical-align: top;">Ascii </td>
2530
2531
2532
2533
2534
2535      <td style="vertical-align: top;">This file contains the vertical
2536profiles calculated by the
25371D-model within initial runs. The quantities saved are set
2538model-internally and cannot be determined by the user. At the
2539respective output times (see <a href="chapter_4.1.html#dt_pr_1d">dt_pr_1d</a>)
2540a table with the following information is written to the file: The
2541table header contains some basic information of the respective run
2542(model version, run identifier consisting of basic file name and number
2543of the job in the
2544job chain (this number should always be 00, because the 1D-model is
2545only switched on at initial runs), executing computer, date,
2546time of the beginning of the run, output time). Afterwards the
2547following columns appear:<br>
2548
2549
2550
2551
2552
2553     
2554     
2555     
2556     
2557     
2558      <table style="text-align: left; width: 100%;" cellpadding="2">
2559
2560
2561
2562
2563
2564        <tbody>
2565
2566
2567
2568
2569
2570          <tr>
2571
2572
2573
2574
2575
2576            <td style="text-align: left; vertical-align: middle;">k<br>
2577
2578
2579
2580
2581
2582            </td>
2583
2584
2585
2586
2587
2588            <td style="text-align: left; vertical-align: middle;">Vertical
2589grid point index.</td>
2590
2591
2592
2593
2594
2595          </tr>
2596
2597
2598
2599
2600
2601          <tr>
2602
2603
2604
2605
2606
2607            <td style="text-align: left; vertical-align: middle;">zu<br>
2608
2609
2610
2611
2612
2613            </td>
2614
2615
2616
2617
2618
2619            <td style="text-align: left; vertical-align: middle;">Height
2620of the grid point
2621level (<font color="#000000">in </font>m).</td>
2622
2623
2624
2625
2626
2627          </tr>
2628
2629
2630
2631
2632
2633          <tr>
2634
2635
2636
2637
2638
2639            <td style="text-align: left; vertical-align: middle;">u<br>
2640
2641
2642
2643
2644
2645            </td>
2646
2647
2648
2649
2650
2651            <td style="text-align: left; vertical-align: middle;">u-component
2652of the wind
2653velocity (<font color="#000000">in </font>m/s).</td>
2654
2655
2656
2657
2658
2659          </tr>
2660
2661
2662
2663
2664
2665          <tr>
2666
2667
2668
2669
2670
2671            <td style="text-align: left; vertical-align: middle;">v<br>
2672
2673
2674
2675
2676
2677            </td>
2678
2679
2680
2681
2682
2683            <td style="text-align: left; vertical-align: middle;">v-component
2684of the wind
2685velocity (<font color="#000000">in </font>m/s).</td>
2686
2687
2688
2689
2690
2691          </tr>
2692
2693
2694
2695
2696
2697          <tr>
2698
2699
2700
2701
2702
2703            <td style="text-align: left; vertical-align: middle;">pt<br>
2704
2705
2706
2707
2708
2709            </td>
2710
2711
2712
2713
2714
2715            <td style="text-align: left; vertical-align: middle;">Potential
2716temperature (<font color="#000000">in </font>K).</td>
2717
2718
2719
2720
2721
2722          </tr>
2723
2724
2725
2726
2727
2728          <tr>
2729
2730
2731
2732
2733
2734            <td style="text-align: left; vertical-align: middle;">e<br>
2735
2736
2737
2738
2739
2740            </td>
2741
2742
2743
2744
2745
2746            <td style="text-align: left; vertical-align: middle;">Turbulent
2747kinetic energy (<font color="#000000">in </font>m<sup>2</sup>/s<sup>2</sup>).</td>
2748
2749
2750
2751
2752
2753          </tr>
2754
2755
2756
2757
2758
2759          <tr>
2760
2761
2762
2763
2764
2765            <td style="text-align: left; vertical-align: middle;">rif<br>
2766
2767
2768
2769
2770
2771            </td>
2772
2773
2774
2775
2776
2777            <td style="text-align: left; vertical-align: middle;">Flux
2778Richardson number</td>
2779
2780
2781
2782
2783
2784          </tr>
2785
2786
2787
2788
2789
2790          <tr>
2791
2792
2793
2794
2795
2796            <td style="text-align: left; vertical-align: middle;">Km<br>
2797
2798
2799
2800
2801
2802            </td>
2803
2804
2805
2806
2807
2808            <td style="text-align: left; vertical-align: middle;">Turbulent
2809diffusion
2810coefficient for momentum (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
2811
2812
2813
2814
2815
2816          </tr>
2817
2818
2819
2820
2821
2822          <tr>
2823
2824
2825
2826
2827
2828            <td style="text-align: left; vertical-align: middle;">Kh<br>
2829
2830
2831
2832
2833
2834            </td>
2835
2836
2837
2838
2839
2840            <td style="text-align: left; vertical-align: middle;">Turbulent
2841diffusion
2842coefficient for heat (<font color="#000000">in </font>m<sup>2</sup>/s).</td>
2843
2844
2845
2846
2847
2848          </tr>
2849
2850
2851
2852
2853
2854          <tr>
2855
2856
2857
2858
2859
2860            <td style="text-align: left; vertical-align: middle;">l<br>
2861
2862
2863
2864
2865
2866            </td>
2867
2868
2869
2870
2871
2872            <td style="text-align: left; vertical-align: middle;"><font color="#000000">Mixing
2873length (</font><font color="#000000">in </font><font color="#000000">m).</font></td>
2874
2875
2876
2877
2878
2879          </tr>
2880
2881
2882
2883
2884
2885       
2886       
2887       
2888       
2889       
2890        </tbody>
2891     
2892     
2893     
2894     
2895     
2896      </table>
2897
2898
2899
2900
2901
2902      <br>
2903
2904
2905
2906
2907
2908      </td>
2909
2910
2911
2912
2913
2914    </tr>
2915
2916
2917
2918
2919
2920    <tr>
2921
2922
2923
2924
2925
2926      <td style="vertical-align: top; text-align: center;">18 </td>
2927
2928
2929
2930
2931
2932      <td style="vertical-align: top;"><a name="CPU_MEASURES"></a>CPU_MEASURES
2933      </td>
2934
2935
2936
2937
2938
2939      <td style="vertical-align: top;">O </td>
2940
2941
2942
2943
2944
2945      <td style="vertical-align: top;">Ascii </td>
2946
2947
2948
2949
2950
2951      <td style="vertical-align: top;">Time measurements are
2952accomplished through the subroutine <span style="font-family: monospace;">cpu_log.f90.</span><span style="font-size: 10pt;"></span> The file
2953CPU_MEASURES contains a header with some basic information of the
2954respective run
2955(model version, run identifier consisting of basic file name and
2956number of the job in the job chain, executing computer, date, time of
2957the beginning of the run) and afterwards two tables with data of CPU
2958times which have been consumed by certain model parts. The model parts
2959analyzed in the first table do not overlap and the CPU times needed for
2960them therefore approximately add up to the &ldquo;total&rdquo; value given in the
2961first line of this table. In the second table (heading: special
2962measures) overlaps (in particular with the parts described in the first
2963table) are possible.&nbsp; <br>
2964
2965
2966
2967
2968
2969For each model part it is indicated in the following columns how much
2970CPU time was needed (absolutely and relative), and how often it was
2971called.&nbsp; With runs on several processors the average values of all
2972processors are indicated. In the case of parallel runs information for
2973those processors with the largest and smallest CPU time follow as
2974well as the standard deviation of all PEs from the average value. With
2975good
2976parallelization the CPU times on the individual processors should
2977differ only little from each other and the standard deviation should be
2978small.&nbsp; </td>
2979
2980
2981
2982
2983
2984    </tr>
2985
2986
2987
2988
2989
2990    <tr>
2991
2992
2993
2994
2995
2996      <td style="vertical-align: top; text-align: center;">19 </td>
2997
2998
2999
3000
3001
3002      <td style="vertical-align: top;"><a name="HEADER"></a>HEADER </td>
3003
3004
3005
3006
3007
3008      <td style="vertical-align: top;">O </td>
3009
3010
3011
3012
3013
3014      <td style="vertical-align: top;">Ascii </td>
3015
3016
3017
3018
3019
3020      <td style="vertical-align: top;">
3021     
3022     
3023     
3024     
3025     
3026      <p>Information about the selected model parameters (physical and
3027numerical values) as well as general information about the run.&nbsp; </p>
3028
3029
3030
3031
3032
3033     
3034     
3035     
3036     
3037     
3038      <p>This file contains the values of all important steering
3039parameters
3040(numerical procedures, computing grid and model dimensions, boundary
3041conditions, physical dimension, turbulence quantities, actions during
3042the simulation, 1D-model-parameters) as well as data concerning the
3043selected plot and list outputs. The headlines of the file list the
3044program version used, date and time of the beginning of the run, the
3045name of the executing computer, the run identifier (corresponds to the
3046selected base file name) and the number of the run (number of the
3047restart run). With parallel runs the number of processors as well as
3048the assigned virtual processor net also appear. After these headlines
3049run time and time step information appear (point of starting time,
3050related to t=0 of the initial run, end-time, time actually reached, CPU
3051time, etc.). If a model run is incorrectly terminated (e.g.
3052run time error or excess of the permitted CPU time), information over
3053the time reached and the necessary CPU time is missing (to understand:
3054the file HEADER is written twice by the model; once briefly after
3055beginning of the simulation (naturally here the information over the
3056time reached is missing etc.) and then briefly before the normal end of
3057the simulation. The second, now complete output overwrites the first
3058output.).&nbsp; </p>
3059
3060
3061
3062
3063
3064     
3065     
3066     
3067     
3068     
3069      <p>At the end of the file, information about the values of user
3070parameters (see <a href="chapter_3.7.html">chapter
30713.7</a> and <a href="targetliste:chapter_1.0.html#chapter%204.3">chapter
30724.3</a>) can be output by the user with the help of the subroutine <tt><font style="font-size: 11pt;" size="2">user_header</font></tt> (located in
3073the file <tt><font style="font-size: 10pt;" size="2">user_interface.f90</font></tt>).
3074If no user parameters were found, the string &ldquo;<tt><font style="font-size: 10pt;" size="2">*** no user-defined variables found</font></tt>&rdquo;
3075appears at the end of the file.
3076If user parameters were indicated, the string &ldquo;<tt><font style="font-size: 11pt;" size="2">user-defined variables and actions</font></tt>&rdquo;
3077is printed, followed by informations about the user-defined subdomains
3078for which
3079profiles and time series are output. All further information to appear
3080here, must be provided by the user (by appropriate
3081WRITE statements in <tt><font style="font-size: 10pt;" size="2">user_header</font></tt>).</p>
3082
3083
3084
3085
3086
3087      </td>
3088
3089
3090
3091
3092
3093    </tr>
3094
3095
3096
3097
3098
3099    <tr>
3100
3101
3102
3103
3104
3105      <td style="vertical-align: top; text-align: center;">21 </td>
3106
3107
3108
3109
3110
3111      <td style="vertical-align: top;"><a name="PLOT2D_XY"></a>PLOT2D_XY
3112      </td>
3113
3114
3115
3116
3117
3118      <td style="vertical-align: top;">O<br>
3119
3120
3121
3122
3123
3124      </td>
3125
3126
3127
3128
3129
3130      <td style="vertical-align: top;">Binary<br>
3131
3132
3133
3134
3135
3136      </td>
3137
3138
3139
3140
3141
3142      <td style="vertical-align: top;">
3143     
3144     
3145     
3146     
3147     
3148      <p>This file contains data of the two-dimensional horizontal
3149cross sections written by the model (see <a href="chapter_4.2.html#data_output">data_output</a>)
3150in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">ISO2D</a>
3151(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>, then
3152the individual arrays follow). The data are visualized with the help of
3153ISO2D using
3154NAMELIST - parameter sets, which are directly written by the model to
3155the
3156local files <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
3157and <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.&nbsp; </p>
3158
3159
3160
3161
3162
3163     
3164     
3165     
3166     
3167     
3168      <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>
3169= <i>.T.</i> each processing element writes the data of its subdomain
3170to a separate file with the name PLOT2D_XY_&lt;processor-Id&gt;,
3171whereby &lt;processor-Id&gt; is a four digit number (e.g.
3172PLOT2D_XY_0000). These files are not suitable for ISO2D, but after the
3173end
3174of the model run they can be combined to one file readable by ISO2D
3175with
3176the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
3177This tool expects the files of the individual processing
3178elements under the names described above and outputs the combined file
3179under the name PLOT2D_XY. Usually it is called by an appropriate OUTPUT
3180- command (OC:) in the MRUN-configuration file. The tool writes
3181informative messages about the actions accomplished into the job
3182protocol (e.g., even if no files were found).
3183By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
3184possibly existing files of the other cross sections (xz and/or yz)
3185and three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
3186are also combined.&nbsp; </p>
3187
3188
3189
3190
3191
3192     
3193     
3194     
3195     
3196     
3197      <p>Further information about the output of plots of
3198two-dimensional cross sections is found in the description of the run
3199parameter <a href="chapter_4.2.html#data_output">data_output</a>.</p>
3200
3201
3202
3203
3204
3205      </td>
3206
3207
3208
3209
3210
3211    </tr>
3212
3213
3214
3215
3216
3217    <tr>
3218
3219
3220
3221
3222
3223      <td style="vertical-align: top; text-align: center;">22<br>
3224
3225
3226
3227
3228
3229      </td>
3230
3231
3232
3233
3234
3235      <td style="vertical-align: top;"><a name="PLOT2D_XZ"></a>PLOT2D_XZ
3236      </td>
3237
3238
3239
3240
3241
3242      <td style="vertical-align: top;">O<br>
3243
3244
3245
3246
3247
3248      </td>
3249
3250
3251
3252
3253
3254      <td style="vertical-align: top;">Binary<br>
3255
3256
3257
3258
3259
3260      </td>
3261
3262
3263
3264
3265
3266      <td style="vertical-align: top;">
3267     
3268     
3269     
3270     
3271     
3272      <p>This file contains the data of the xz
3273cross sections written by the model.&nbsp; </p>
3274
3275
3276
3277
3278
3279The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
3280applies to this file, respectively </td>
3281
3282
3283
3284
3285
3286    </tr>
3287
3288
3289
3290
3291
3292    <tr>
3293
3294
3295
3296
3297
3298      <td style="vertical-align: top; text-align: center;">23<br>
3299
3300
3301
3302
3303
3304      </td>
3305
3306
3307
3308
3309
3310      <td style="vertical-align: top;"><a name="PLOT2D_YZ"></a>PLOT2D_YZ
3311      </td>
3312
3313
3314
3315
3316
3317      <td style="vertical-align: top;">O<br>
3318
3319
3320
3321
3322
3323      </td>
3324
3325
3326
3327
3328
3329      <td style="vertical-align: top;">Binary<br>
3330
3331
3332
3333
3334
3335      </td>
3336
3337
3338
3339
3340
3341      <td style="vertical-align: top;">
3342     
3343     
3344     
3345     
3346     
3347      <p>This file contains the data of the xz
3348cross sections written by the model.&nbsp; </p>
3349
3350
3351
3352
3353
3354The description of the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
3355applies to this file, respectively </td>
3356
3357
3358
3359
3360
3361    </tr>
3362
3363
3364
3365
3366
3367    <tr>
3368
3369
3370
3371
3372
3373      <td style="vertical-align: top; text-align: center;">27<br>
3374
3375
3376
3377
3378
3379      </td>
3380
3381
3382
3383
3384
3385      <td style="vertical-align: top;"><a name="PLOT2D_XY_LOCAL"></a>PLOT2D_XY_LOCAL
3386      </td>
3387
3388
3389
3390
3391
3392      <td style="vertical-align: top;">O<br>
3393
3394
3395
3396
3397
3398      </td>
3399
3400
3401
3402
3403
3404      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
3405
3406
3407
3408
3409
3410      </td>
3411
3412
3413
3414
3415
3416      <td style="vertical-align: top;">
3417     
3418     
3419     
3420     
3421     
3422      <p>NAMELIST - parameter sets, with which the plot layout of the
3423data in the local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
3424can 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>.
3425This file contains the so-called local parameter set (NAMELIST - group
3426name: &amp;LOCAL) required by ISO2D (one parameter set for each field
3427present at the file PLOT2D_XY). After the model run these parameter
3428sets can be edited by the user, if neccessary.&nbsp; </p>
3429
3430
3431
3432
3433
3434     
3435     
3436     
3437     
3438     
3439      <p>Additionally ISO2D still needs another so-called global
3440parameter set. This is saved by the model to the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>.
3441Due to the fact that ISO2D expects global and local parameter sets on
3442one and the same
3443file, in fact the global parameter set first, the user has to append
3444the
3445contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
3446before the call of ISO2D (e.g. by an OUTPUT-command in the
3447MRUN-configuration file: &ldquo;PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL&rdquo;).
3448This relatively pedantic proceeding is due to the fact that the model
3449can produce the file PLOT2D_XY_GLOBAL only at the end of the simulation
3450(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>
3451is known), while the local parameter sets are written continuously
3452to the file PLOT2D_XY_LOCAL during the run.</p>
3453
3454
3455
3456
3457
3458      </td>
3459
3460
3461
3462
3463
3464    </tr>
3465
3466
3467
3468
3469
3470    <tr>
3471
3472
3473
3474
3475
3476      <td style="vertical-align: top; text-align: center;">28<br>
3477
3478
3479
3480
3481
3482      </td>
3483
3484
3485
3486
3487
3488      <td style="vertical-align: top;"><a name="PLOT2D_XZ_LOCAL"></a>PLOT2D_XZ_LOCAL
3489      </td>
3490
3491
3492
3493
3494
3495      <td style="vertical-align: top;">O<br>
3496
3497
3498
3499
3500
3501      </td>
3502
3503
3504
3505
3506
3507      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
3508
3509
3510
3511
3512
3513      </td>
3514
3515
3516
3517
3518
3519      <td style="vertical-align: top;">
3520     
3521     
3522     
3523     
3524     
3525      <p>NAMELIST - parameter sets, with which the plot layout of the
3526data in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
3527can 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;
3528      </p>
3529
3530
3531
3532
3533
3534     
3535     
3536     
3537     
3538     
3539      <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
3540applies to this file, respectively. </p>
3541
3542
3543
3544
3545
3546      </td>
3547
3548
3549
3550
3551
3552    </tr>
3553
3554
3555
3556
3557
3558    <tr>
3559
3560
3561
3562
3563
3564      <td style="vertical-align: top; text-align: center;">29<br>
3565
3566
3567
3568
3569
3570      </td>
3571
3572
3573
3574
3575
3576      <td style="vertical-align: top;"><a name="PLOT2D_YZ_LOCAL"></a>PLOT2D_YZ_LOCAL
3577      </td>
3578
3579
3580
3581
3582
3583      <td style="vertical-align: top;">O<br>
3584
3585
3586
3587
3588
3589      </td>
3590
3591
3592
3593
3594
3595      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
3596
3597
3598
3599
3600
3601      </td>
3602
3603
3604
3605
3606
3607      <td style="vertical-align: top;">
3608     
3609     
3610     
3611     
3612     
3613      <p>NAMELIST - parameter sets, with which the plot layout of the
3614data in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
3615can 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;
3616      </p>
3617
3618
3619
3620
3621
3622     
3623     
3624     
3625     
3626     
3627      <p>The description of the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>
3628applies to this file, respectively. </p>
3629
3630
3631
3632
3633
3634      </td>
3635
3636
3637
3638
3639
3640    </tr>
3641
3642
3643
3644
3645
3646    <tr>
3647
3648
3649
3650
3651
3652      <td style="vertical-align: top; text-align: center;">30<br>
3653
3654
3655
3656
3657
3658      </td>
3659
3660
3661
3662
3663
3664      <td style="vertical-align: top;"><a name="PLOT3D_DATA"></a>PLOT3D_DATA
3665      </td>
3666
3667
3668
3669
3670
3671      <td style="vertical-align: top;">O<br>
3672
3673
3674
3675
3676
3677      </td>
3678
3679
3680
3681
3682
3683      <td style="vertical-align: top;">Binary<br>
3684
3685
3686
3687
3688
3689      </td>
3690
3691
3692
3693
3694
3695      <td style="vertical-align: top;">
3696     
3697     
3698     
3699     
3700     
3701      <p>This file contains the data of the three-dimensional arrays
3702(see <a href="chapter_4.2.html#data_output">data_output</a>)
3703written by the model in a format readable for the visualization
3704software AVS. Beyond that AVS
3705needs coordinate information, which are output into the
3706local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
3707as well as the local files <a href="#PLOT3D_FLD">PLOT3D_FLD</a>
3708and <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
3709which describe the structure of the files PLOT3D_DATA and PLOT3D_COOR
3710in the so-called AVS-FLD-format. Due to
3711the fact that AVS expects these information in only one (so-called FLD
3712-) file, the content of the file PLOT3D_FLD_COOR must be appended to
3713the file PLOT3D_FLD by the user after the end of the model run (e.g.
3714with an appropriate OUTPUT - command in the MRUN - configuration file: "<span style="font-family: monospace;">cat PLOT3D_FLD_COOR &gt;&gt; PLOT3D_FLD</span>").&nbsp;
3715      </p>
3716
3717
3718
3719
3720
3721     
3722     
3723     
3724     
3725     
3726      <p>With parallel runs each processing element writes the data of
3727its subdomain to a separate file with the name
3728PLOT3D_DATA_&lt;Processor-Id&gt;, where &lt;Processor-Id&gt; is a
3729four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable
3730for AVS, but after the end of the model run they can be combined to one
3731file readable for AVS with the help of the program <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>.
3732This tool expects the files of the individual processing
3733elements under the names described above and outputs the combined file
3734into a new file PLOT3D_DATA. Usually it is called by an appropriate
3735OUTPUT - command in the MRUN-configuration file. The tool
3736writes informative messages about the accomplished actions into
3737the job protocol (e.g., even if no files were
3738found). By the call of <tt><font style="font-size: 10pt;" size="2">combine_plot_fields.x</font></tt>
3739also possibly existing files with two-dimensional plot data (see e.g. <a href="#PLOT2D_XY">PLOT2D_XY</a>)
3740are combined.&nbsp; </p>
3741
3742
3743
3744
3745
3746     
3747     
3748     
3749     
3750     
3751      <p>With parallel runs the output of data of large volume is also
3752possible in compressed form. For this purpose the initialization
3753parameter&nbsp; <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>
3754= <i>.TRUE.</i> must be set and the desired output accuracy has to be
3755indicated
3756with the help of <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>.
3757In favorable cases the file size can be reduced by
3758a factor of up to 5. For the visualization of compressed data a special
3759AVS module (<tt><font style="font-size: 11pt;" size="2">read_compressed_field</font></tt>)
3760and a further entry in the MRUN-configuration file are needed. More
3761details can be found in <a href="chapter_4.5.6.html">chapter
37624.5.6</a>.</p>
3763
3764
3765
3766
3767
3768      </td>
3769
3770
3771
3772
3773
3774    </tr>
3775
3776
3777
3778
3779
3780    <tr>
3781
3782
3783
3784
3785
3786      <td style="vertical-align: top; text-align: center;">31<br>
3787
3788
3789
3790
3791
3792      </td>
3793
3794
3795
3796
3797
3798      <td style="vertical-align: top;"><a name="PLOT3D_COOR"></a>PLOT3D_COOR
3799      </td>
3800
3801
3802
3803
3804
3805      <td style="vertical-align: top;">O<br>
3806
3807
3808
3809
3810
3811      </td>
3812
3813
3814
3815
3816
3817      <td style="vertical-align: top;">Binary<br>
3818
3819
3820
3821
3822
3823      </td>
3824
3825
3826
3827
3828
3829      <td style="vertical-align: top;">
3830     
3831     
3832     
3833     
3834     
3835      <p>Coordinate information concerning
3836the three-dimensional arrays (see <a href="#PLOT3D_DATA">PLOT3D_DATA</a>)
3837needed by the visualization software AVS.&nbsp; </p>
3838
3839
3840
3841
3842
3843     
3844     
3845     
3846     
3847     
3848      <p>The file PLOT3D_COOR should be saved by the user into the same
3849permanent directory as the file PLOT3D_DATA.&nbsp; </p>
3850
3851
3852
3853
3854
3855     
3856     
3857     
3858     
3859     
3860      <p>For parallel runs PLOT3D_COOR is written by PE0 only.</p>
3861
3862
3863
3864
3865
3866      </td>
3867
3868
3869
3870
3871
3872    </tr>
3873
3874
3875
3876
3877
3878    <tr>
3879
3880
3881
3882
3883
3884      <td style="vertical-align: top; text-align: center;">32<br>
3885
3886
3887
3888
3889
3890      </td>
3891
3892
3893
3894
3895
3896      <td style="vertical-align: top;"><a name="PLOT3D_FLD"></a>PLOT3D_FLD
3897      </td>
3898
3899
3900
3901
3902
3903      <td style="vertical-align: top;">O<br>
3904
3905
3906
3907
3908
3909      </td>
3910
3911
3912
3913
3914
3915      <td style="vertical-align: top;">Ascii/&nbsp; <br>
3916
3917
3918
3919
3920
3921AVS-Fld </td>
3922
3923
3924
3925
3926
3927      <td style="vertical-align: top;">
3928     
3929     
3930     
3931     
3932     
3933      <p>AVS-fld-file describing the three-dimensional
3934array data, saved by the model into the local file <a href="#PLOT3D_DATA">PLOT3D_DATA</a>,
3935needed by the visualization software AVS.&nbsp; </p>
3936
3937
3938
3939
3940
3941     
3942     
3943     
3944     
3945     
3946      <p>This file describes the structure of the file PLOT3D_DATA
3947(e.g. number of arrays, array dimensions, data type etc.). It uses the
3948so-called AVS-Fld-format. It also contains the name of the file
3949(inclusive cycle number, but without path) under which the local file
3950PLOT3D_DATA is saved (this is the file name given in the file
3951connection statement of the MRUN &ndash; configuration) in the permanent
3952directory of the user (possibly on remote computers). Under this name
3953AVS expects the data which are to be visualized. If there is no file
3954connection statement for PLOT3D_DATA indicated in the configuration
3955file, that file (filename) is registered &ldquo;unknown&rdquo; in the file
3956PLOT3D_FLD and the
3957actual name must be inserted later by hand. The file PLOT3D_FLD should
3958be saved by the user in the same permanent directory as PLOT3D_DATA, so
3959that AVS can find the file PLOT3D_DATA without any problems. If the two
3960files lie in different directories, then the path name of the file
3961PLOT3D_DATA must be added.&nbsp; </p>
3962
3963
3964
3965
3966
3967     
3968     
3969     
3970     
3971     
3972      <p>AVS-fld-files are expected by AVS to have the
3973suffix "<span style="font-family: monospace;">.fld</span>"<font face="Cumberland, monospace">.</font>
3974Cycle numbers must not be attached behind this "<span style="font-family: monospace;">.fld</span>" suffix. This suffix is
3975attached to the permanent file names (still after
3976possible cycle numbers) by <span style="font-weight: bold;">mrun</span>
3977if&nbsp;"<span style="font-family: monospace;">fld</span>"
3978is indicated in the <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#Spalte6">column
39796 </a>of the file connection statement.&nbsp; </p>
3980
3981
3982
3983
3984
3985     
3986     
3987     
3988     
3989     
3990      <p>Likewise, AVS expects information about the coordinate
3991system underlying the arrays on this file. This information is output
3992by the model
3993into the local file <a href="#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>,
3994whose content the user has to append to the file PLOT3D_FLD after the
3995end of the model run (e.g. with an appropriate OUTPUT-command in the
3996MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR &gt;&gt;
3997PLOT3D_FLD&rdquo;).&nbsp; </p>
3998
3999
4000
4001
4002
4003     
4004     
4005     
4006     
4007     
4008      <p>For parallel runs, PLOT3D_FLD is produced by PE0 only.</p>
4009
4010
4011
4012
4013
4014      </td>
4015
4016
4017
4018
4019
4020    </tr>
4021
4022
4023
4024
4025
4026    <tr>
4027
4028
4029
4030
4031
4032      <td style="vertical-align: top; text-align: center;">33 </td>
4033
4034
4035
4036
4037
4038      <td style="vertical-align: top;"><a name="PLOT3D_FLD_COOR"></a>PLOT3D_FLD_COOR
4039      </td>
4040
4041
4042
4043
4044
4045      <td style="vertical-align: top;">O<br>
4046
4047
4048
4049
4050
4051      </td>
4052
4053
4054
4055
4056
4057      <td style="vertical-align: top;">Ascii/&nbsp; <br>
4058
4059
4060
4061
4062
4063AVS-Fld </td>
4064
4065
4066
4067
4068
4069      <td style="vertical-align: top;">
4070     
4071     
4072     
4073     
4074     
4075      <p>File for the description of the coordinate information output
4076by the model into the local file <a href="#PLOT3D_COOR">PLOT3D_COOR</a>,
4077which is needed for the visualization of three-dimensional array data
4078by visualization-software AVS.&nbsp; </p>
4079
4080
4081
4082
4083
4084     
4085     
4086     
4087     
4088     
4089      <p>This file describes the structure of the file PLOT3D_COOR
4090(e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format.
4091It also contains the name of the file (inclusive cycle number, but
4092without path) into which the local file PLOT3D_COOR (this is the file
4093name described in the file connection statement of the MRUN -
4094configuration file) is output in the permanent directory of the user
4095(possibly on remote computers). Under this name AVS expects the data
4096which are to be visualized. If there is no file connection statement
4097for
4098PLOT3D_COOR indicated in the configuration file, that file is
4099registered as "unknown" in the file
4100PLOT3D_FLD_COOR and the actual name
4101must be inserted later by hand.&nbsp; </p>
4102
4103
4104
4105
4106
4107     
4108     
4109     
4110     
4111     
4112      <p>AVS expects the information contained in the file
4113PLOT3D_FLD_COOR, as well as the remaining information about the
4114three-dimensional arrays output by the model (see <a href="#PLOT3D_FLD">PLOT3D_FLD</a>)
4115in one and the same file. This is satisfied by appending the file
4116PLOT3D_FLD_COOR after the end of a run are to the
4117file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the
4118MRUN-configuration file: &ldquo;cat PLOT3D_FLD_COOR &gt;&gt;
4119PLOT3D_FLD&rdquo;).&nbsp; </p>
4120
4121
4122
4123
4124
4125     
4126     
4127     
4128     
4129     
4130      <p>For parallel runs, PLOT3D_FLD_COOR is written by PE0 only.</p>
4131
4132
4133
4134
4135
4136      </td>
4137
4138
4139
4140
4141
4142    </tr>
4143
4144
4145
4146
4147
4148    <tr>
4149
4150
4151
4152
4153
4154      <td style="vertical-align: top; text-align: center;">
4155     
4156     
4157     
4158     
4159     
4160      <p align="center">40&nbsp; </p>
4161
4162
4163
4164
4165
4166     
4167     
4168     
4169     
4170     
4171      <p align="center">and/or&nbsp; <br>
4172
4173
4174
4175
4176
4177possibly&nbsp; </p>
4178
4179
4180
4181
4182
4183     
4184     
4185     
4186     
4187     
4188      <p align="center">40-49</p>
4189
4190
4191
4192
4193
4194      </td>
4195
4196
4197
4198
4199
4200      <td style="vertical-align: top;">
4201     
4202     
4203     
4204     
4205     
4206      <p><a name="PLOT1D_DATA"></a>PLOT1D_DATA&nbsp; </p>
4207
4208
4209
4210
4211
4212     
4213     
4214     
4215     
4216     
4217      <p>and/or&nbsp; <br>
4218
4219
4220
4221
4222
4223possibly&nbsp; </p>
4224
4225
4226
4227
4228
4229PLOT1D_DATA_0&nbsp; <br>
4230
4231
4232
4233
4234
4235PLOT1D_DATA_1&nbsp; </td>
4236
4237
4238
4239
4240
4241      <td style="vertical-align: top;">O </td>
4242
4243
4244
4245
4246
4247      <td style="vertical-align: top;">Ascii </td>
4248
4249
4250
4251
4252
4253      <td style="vertical-align: top;">
4254     
4255     
4256     
4257     
4258     
4259      <p>This file contains data (possibly horizontally and/or
4260temporally averaged) of the vertical profiles (see <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>)
4261written by the model in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>. It is created only if <a href="chapter_4.2.html#data_output_format">data_output_format</a> = <span style="font-style: italic;">'profil'</span> is assigned. This file's format is suitable to be read by the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
4262Each data point of the profiles is output in one single line (1st
4263column: height in m, 2nd column: value of the respective quantity).
4264Within the file, data
4265of the individual profiles are located one behind the other. The order
4266of the data in the file follows the order used in the assignment for <b>data_output_pr</b>
4267(<b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,&hellip;
4268means that the file starts with the data of the u-component profile,
4269followed by the v-component profile, etc.).&nbsp;</p>
4270      <p><br>
4271The data can only be visualized with <span style="font-weight: bold;">profil</span>
4272using NAMELIST-parameter sets, which are saved by the
4273model into the local file <a href="#PLOT1D_PAR">PLOT1D_PAR</a>.&nbsp; </p>
4274
4275
4276
4277
4278
4279     
4280     
4281     
4282     
4283     
4284      <p>The profile data written to the file are described with the
4285run parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>.
4286Plots produced with these data using the parameter file PLOT1D_PAR do
4287not have to contain all these profiles. The profiles which can be drawn
4288in the plot are described with run parameter <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>.
4289By subsequent editing of the file PLOT1D_PAR all profiles can be
4290plotted (also the basic layout of the plots can be
4291changed). For orientation, each profile existing on the file
4292PLOT1D_DATA, starts with a comment line, which indicates the
4293presented variable and the output time. The text of these comment
4294lines is used as a legend in the plot. The very first line of the file
4295is a
4296comment line, containing information about the used model version, the
4297run identifier (base file name + number of the respective restart
4298run), the name of the executing computer, as well as the date and time
4299of the beginning of the run. At the end of this comment line is the
4300name
4301of the subdomain, to which the profiles belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
4302By default, the profiles present averages of the total model domain. If
4303the model has to produce profiles for other subdomains beyond that, up
4304to 9 further files (units No. 41-49) are created, whereby the number of
4305the respective subdomain is attached
4306to the file name (e.g. PLOT1D_DATA_1). The name of the file with the
4307data of the total
4308domain in this case reads PLOT1D_DATA_0.&nbsp; </p>
4309
4310
4311
4312
4313
4314     
4315     
4316     
4317     
4318     
4319      <p>For presentation in the same plot, profile data of the restart
4320runs can be attached to existing data of preceding runs of a job chain.
4321One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
4322in the file connection statement. The model produces a parameter file
4323(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>
4324= <i>.T</i>. If this is omitted, then the parameter file gives
4325wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
4326= .T.</span> and "<span style="font-family: monospace;">tra</span>"
4327must be specified together)!&nbsp; </p>
4328
4329
4330
4331
4332
4333     
4334     
4335     
4336     
4337     
4338      <p>Further information about output of
4339vertical 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>
4340
4341
4342
4343
4344
4345      </td>
4346
4347
4348
4349
4350
4351    </tr>
4352
4353
4354
4355
4356
4357    <tr>
4358
4359
4360
4361
4362
4363      <td style="vertical-align: top; text-align: center;">
4364     
4365     
4366     
4367     
4368     
4369      <p align="center">50&nbsp; </p>
4370
4371
4372
4373
4374
4375     
4376     
4377     
4378     
4379     
4380      <p align="center">and/or&nbsp; <br>
4381
4382
4383
4384
4385
4386possibly&nbsp; </p>
4387
4388
4389
4390
4391
4392     
4393     
4394     
4395     
4396     
4397      <p align="center">50-59</p>
4398
4399
4400
4401
4402
4403      </td>
4404
4405
4406
4407
4408
4409      <td style="vertical-align: top;">
4410     
4411     
4412     
4413     
4414     
4415      <p><a name="PLOTTS_DATA"></a>PLOTTS_DATA&nbsp; </p>
4416
4417
4418
4419
4420
4421     
4422     
4423     
4424     
4425     
4426      <p>and/or&nbsp; <br>
4427
4428
4429
4430
4431
4432possibly&nbsp; </p>
4433
4434
4435
4436
4437
4438     
4439     
4440     
4441     
4442     
4443      <p>PLOTTS_DATA_0&nbsp; <br>
4444
4445
4446
4447
4448
4449PLOTTS_DATA_1&nbsp; <br>
4450
4451
4452
4453
4454
4455&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4456.&nbsp; <br>
4457
4458
4459
4460
4461
4462&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4463.&nbsp; <br>
4464
4465
4466
4467
4468
4469&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4470.&nbsp; <br>
4471
4472
4473
4474
4475
4476PLOTTS_DATA_9</p>
4477
4478
4479
4480
4481
4482      </td>
4483
4484
4485
4486
4487
4488      <td style="vertical-align: top;">O</td>
4489
4490
4491
4492
4493
4494      <td style="vertical-align: top;">Ascii<br>
4495
4496
4497
4498
4499
4500      </td>
4501
4502
4503
4504
4505
4506      <td style="vertical-align: top;">
4507     
4508     
4509     
4510     
4511     
4512      <p>This file contains the data of the time series written by the
4513model (see <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>)
4514in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
4515The data can only be visualized with <span style="font-weight: bold;">profil</span>
4516using NAMELIST parameter sets, which are written by
4517the model to the local file <a href="#PLOTTS_PAR">PLOTTS_PAR</a>.&nbsp;
4518      </p>
4519
4520
4521
4522
4523
4524     
4525     
4526     
4527     
4528     
4529      <p>Regardless of the (sub)set of time series specified by <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>
4530for actual output, this file allways contains all possible time series.
4531They are arranged next to each other in 22 columns. The
4532first column contains the time in s. With initial runs the
4533variables in the individual columns are described in the comment lines
4534at the beginning of the file (see also <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>).
4535The text of these comment lines is used as a legend in the plot. The
4536first line of the file is a comment line in case of initial runs
4537and contains information about the used model version, the run
4538identifier (base file name + number of the respective restart run),
4539the name of the executing computer, as well as the date and time of the
4540beginning of the run. At the end of this comment line is the name of
4541the
4542subdomain, to which the time series belong (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
4543By default, it is the &ldquo;total domain&rdquo;, i.e. the time series
4544apply to the whole model domain. If the model has to produce profiles
4545for subdomains, up to 9 further files (units No. 51-59) are
4546produced. The file names include the number of the respective
4547subdomain (e.g. PLOTTS_DATA_1). In this case the name of the file with
4548the data of the total domain is PLOTTS_DATA_0.&nbsp; </p>
4549
4550
4551
4552
4553
4554     
4555     
4556     
4557     
4558     
4559      <p>Time series data of restart runs <b>must
4560always</b> be attached to existing data of preceding runs of a job
4561chain, because
4562they do not contain comment lines (see above) and otherwise are not
4563visualizable with <span style="font-weight: bold;">profil</span>. Time
4564series plotted with <span style="font-weight: bold;">profil</span>
4565therefore always begin with t=0. An appending of the data to one file
4566is
4567obtained with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
4568in the file connection statement. <br>
4569
4570
4571
4572
4573
4574      </p>
4575
4576
4577
4578
4579
4580      </td>
4581
4582
4583
4584
4585
4586    </tr>
4587
4588
4589
4590
4591
4592    <tr>
4593
4594
4595
4596
4597
4598      <td style="vertical-align: top; text-align: center;">80 </td>
4599
4600
4601
4602
4603
4604      <td style="vertical-align: top;"><a name="PARTICLE_INFOS"></a>PARTICLE_INFOS/
4605      </td>
4606
4607
4608
4609
4610
4611      <td style="vertical-align: top;">O </td>
4612
4613
4614
4615
4616
4617      <td style="vertical-align: top;">Ascii </td>
4618
4619
4620
4621
4622
4623      <td style="vertical-align: top;">This
4624file is created in case of particle transport (see the <a href="chapter_4.2.html#particles_package">particles
4625package</a>). It contains statistical informations about the number of
4626particles used and about the number of particles exchanged between each
4627single PE. These informations are output after every timestep if
4628switched on by parameter <a href="chapter_4.2.html#write_particle_statistics">write_particle_statistics</a>.
4629      </td>
4630
4631
4632
4633
4634
4635    </tr>
4636
4637
4638
4639
4640
4641    <tr>
4642
4643
4644
4645
4646
4647      <td style="vertical-align: top; text-align: center;">81 </td>
4648
4649
4650
4651
4652
4653      <td style="vertical-align: top;"><a name="PLOTSP_X_PAR"></a>PLOTSP_X_PAR
4654      </td>
4655
4656
4657
4658
4659
4660      <td style="vertical-align: top;">O </td>
4661
4662
4663
4664
4665
4666      <td style="vertical-align: top;">Ascii/<br>
4667
4668
4669
4670
4671
4672NAMELIST </td>
4673
4674
4675
4676
4677
4678      <td style="vertical-align: top;">This
4679file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
4680package</a>). It contains the NAMELIST parameter set, with which the
4681layout of a plot
4682of the data in the local file <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
4683can 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>
4684
4685
4686
4687
4688
4689     
4690     
4691     
4692     
4693     
4694      <p>It contains the so-called RAHMEN (frame)- and
4695CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
4696needed by <span style="font-weight: bold;">profil</span>.
4697The user can edit these parameter sets (and thus all details of the
4698plot layout) after the run.<br>
4699
4700
4701
4702
4703
4704      </p>
4705
4706
4707
4708
4709
4710     
4711     
4712     
4713     
4714     
4715      <p>By default, for one quantity, all spectra at different heights
4716are plotted into a single panel. Different colors and line styles are
4717used for each height. Panels of up to four quantities are arranged on
4718one page in two lines (and two columns). More quantities are plotted on
4719additional page(s). If there is more than one output time (see <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>),
4720additional pages will be plotted for each single output time. </p>
4721
4722
4723
4724
4725
4726      </td>
4727
4728
4729
4730
4731
4732    </tr>
4733
4734
4735
4736
4737
4738    <tr>
4739
4740
4741
4742
4743
4744      <td style="vertical-align: top; text-align: center;">82<br>
4745
4746
4747
4748
4749
4750      </td>
4751
4752
4753
4754
4755
4756      <td style="vertical-align: top;"><a name="PLOTSP_X_DATA"></a>PLOTSP_X_DATA
4757      </td>
4758
4759
4760
4761
4762
4763      <td style="vertical-align: top;">O<br>
4764
4765
4766
4767
4768
4769      </td>
4770
4771
4772
4773
4774
4775      <td style="vertical-align: top;">Ascii<br>
4776
4777
4778
4779
4780
4781      </td>
4782
4783
4784
4785
4786
4787      <td style="vertical-align: top;">This
4788file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
4789package</a>). It contains the spectral data along x (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
4790in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
4791The data can only be visualized with <span style="font-weight: bold;">profil</span>
4792using NAMELIST parameter sets, which are written by
4793the model to the local file <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
4794
4795
4796
4797
4798
4799      <br>
4800
4801
4802
4803
4804
4805Regardless of the (sub)set of spectra specified by <a href="chapter_4.2.html#plot_spectra_level">plot_spectra_level</a>
4806for actual plotting, this file contains all data of spectra specified
4807by <a href="chapter_4.2.html#comp_spectra_level">comp_spectra_level</a>.<br>
4808
4809
4810
4811
4812
4813      <br>
4814
4815
4816
4817
4818
4819      <font>Each data point of a spectrum is output in a single line
4820(1st column:
4821wavenumber, 2nd column: spectral coefficient). If spectra are to be
4822calculated 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>),
4823the spectral coefficients for the further heights can be found in the
4824subsequent columns. </font>The order
4825of 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>
4826
4827
4828
4829
4830
4831      <br>
4832
4833
4834
4835
4836
4837For orientation, a header of comment lines (one for each height level)
4838is placed in front of the spectral data of each quantity. They indicate
4839the respective quantity and the output time. The text of these comment
4840lines is used as a legend in the plot. </td>
4841
4842
4843
4844
4845
4846    </tr>
4847
4848
4849
4850
4851
4852    <tr>
4853
4854
4855
4856
4857
4858      <td style="vertical-align: top; text-align: center;">83<br>
4859
4860
4861
4862
4863
4864      </td>
4865
4866
4867
4868
4869
4870      <td style="vertical-align: top;"><a name="PLOTSP_Y_PAR"></a>PLOTSP_Y_PAR
4871      </td>
4872
4873
4874
4875
4876
4877      <td style="vertical-align: top;">O<br>
4878
4879
4880
4881
4882
4883      </td>
4884
4885
4886
4887
4888
4889      <td style="vertical-align: top;">Ascii<br>
4890
4891
4892
4893
4894
4895      </td>
4896
4897
4898
4899
4900
4901      <td style="vertical-align: top;">This
4902file is created if spectra along y are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
4903package</a>). It contains the NAMELIST parameter set, with which the
4904layout of a plot
4905of the data in the local file <a href="#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
4906can 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>
4907
4908
4909
4910
4911
4912      <br>
4913
4914
4915
4916
4917
4918For more details see <a href="#PLOTSP_X_PAR">PLOTSP_X_PAR</a>.<br>
4919
4920
4921
4922
4923
4924      </td>
4925
4926
4927
4928
4929
4930    </tr>
4931
4932
4933
4934
4935
4936    <tr>
4937
4938
4939
4940
4941
4942      <td style="vertical-align: top; text-align: center;">84<br>
4943
4944
4945
4946
4947
4948      </td>
4949
4950
4951
4952
4953
4954      <td style="vertical-align: top;"><a name="PLOTSP_Y_DATA"></a>PLOTSP_Y_DATA</td>
4955
4956
4957
4958
4959
4960      <td style="vertical-align: top;">O<br>
4961
4962
4963
4964
4965
4966      </td>
4967
4968
4969
4970
4971
4972      <td style="vertical-align: top;">Ascii<br>
4973
4974
4975
4976
4977
4978      </td>
4979
4980
4981
4982
4983
4984      <td style="vertical-align: top;">This
4985file is created if spectra along x are calculated and output (see the <a href="chapter_4.2.html#particles_package">spectra
4986package</a>). It contains the spectral data along y (see <a href="chapter_4.2.html#data_output_sp">data_output_sp</a>)
4987in a format readable by <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html">profil</a>.
4988The data can only be visualized with <span style="font-weight: bold;">profil</span>
4989using NAMELIST parameter sets, which are written by
4990the model to the local file <a href="#PLOTSP_Y_PAR">PLOTSP_Y_PAR</a>.<br>
4991
4992
4993
4994
4995
4996      <br>
4997
4998
4999
5000
5001
5002For more details see <a href="#PLOTSP_X_DATA">PLOTSP_X_DATA</a>.</td>
5003
5004
5005
5006
5007
5008    </tr>
5009
5010
5011
5012
5013
5014    <tr>
5015
5016
5017
5018
5019
5020      <td style="vertical-align: top; text-align: center;">85<br>
5021
5022
5023
5024
5025
5026      </td>
5027
5028
5029
5030
5031
5032      <td style="vertical-align: top;"><a name="PARTICLE_DATA"></a>PARTICLE_DATA/</td>
5033
5034
5035
5036
5037
5038      <td style="vertical-align: top;">O<br>
5039
5040
5041
5042
5043
5044      </td>
5045
5046
5047
5048
5049
5050      <td style="vertical-align: top;">Binary<br>
5051
5052
5053
5054
5055
5056      </td>
5057
5058
5059
5060
5061
5062      <td style="vertical-align: top;">This
5063file is created if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
5064package</a>) and contains all particle data for one or several output
5065times (see <a href="chapter_4.2.html#dt_write_particle_data">dt_write_particle_data</a>).<br>
5066
5067
5068
5069
5070
5071      <br>
5072
5073
5074
5075
5076
5077The first record of this file contains an identification string (PALM
5078version number, run identifier, etc., 80 characters long). The second
5079record also contains a version string (80 characters long) followed by
5080two records with particle group informations (see file <span style="font-family: monospace;">check_open.f90</span>). Then, for each
5081output time, two records follow, where the first one gives some general
5082information (numbers of particles, etc.) and the second one contains
5083the actual particle data. A FORTRAN TYPE structure is used for storing
5084the particle attributes. See file <span style="font-family: monospace;">advec_particles.f90</span>
5085for the detailed format.</td>
5086
5087
5088
5089
5090
5091    </tr>
5092
5093
5094
5095
5096
5097    <tr>
5098
5099
5100
5101
5102
5103      <td style="vertical-align: top; text-align: center;">90</td>
5104
5105
5106
5107
5108
5109      <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
5110
5111
5112
5113
5114
5115DATA_IN/</td>
5116
5117
5118
5119
5120
5121      <td style="vertical-align: top;">I<br>
5122
5123
5124
5125
5126
5127      </td>
5128
5129
5130
5131
5132
5133      <td style="vertical-align: top;">Binary<br>
5134
5135
5136
5137
5138
5139      </td>
5140
5141
5142
5143
5144
5145      <td style="vertical-align: top;">Binary
5146data, which are read in by the model at the beginning
5147of a restart run (see <a href="chapter_3.3.html">chapter
51483.3</a>). The appropriate file must have been written by the preceding
5149job of the job chain (see <a href="#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>).
5150This file is needed if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
5151package</a>) and contains all particle informations (particle
5152positions, velocities, etc.) from the end of the preceding run.
5153Concerning runs on
5154several processors it has to be noted that each processing element
5155reads its own file and that the file content is processor-dependent.
5156The
5157number of processors which can be used must not be changed during a job
5158chain and/or if a job chain is continued. <br>
5159
5160
5161
5162
5163
5164      <br>
5165
5166
5167
5168
5169
5170The first record of this file contains a version number (four character
5171string) of the subroutine, which output the data that follows (<span style="font-family: monospace;">write_particles</span>, see end of
5172file <span style="font-family: monospace;">advec_particles.f90</span>).
5173This number has to
5174agree with the version number of the subroutine which is reading the
5175file
5176(<span style="font-family: monospace;">init_parrticles.f90</span>) in
5177case of a restart run. Otherwise the model run
5178is aborted. Version numbers are changed whenever new code revisions
5179require a change of the file format. Some general informations like the
5180number of particles stored in the file, the number of particle groups,
5181etc.. are stored in the second record. The third record includes the
5182particles to be released at the source and the fourth record contains
5183all 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>),
5184a further record may follow, which contains the particle tail
5185informations. A FORTRAN TYPE structure is used for storing the particle
5186attributes. For detailed informations about the file format see the
5187corresponding READ statements in file <span style="font-family: monospace;">init_particles.f90</span> .<br>
5188
5189
5190
5191
5192
5193      </td>
5194
5195
5196
5197
5198
5199    </tr>
5200
5201
5202
5203
5204
5205    <tr>
5206
5207
5208
5209
5210
5211      <td style="vertical-align: top; text-align: center;">90<br>
5212
5213
5214
5215
5216
5217      </td>
5218
5219
5220
5221
5222
5223      <td style="vertical-align: top;"><a name="PARTICLE_RESTART_DATA_IN"></a>PARTICLE_RESTART_<br>
5224
5225
5226
5227
5228
5229DATA_OUT/</td>
5230
5231
5232
5233
5234
5235      <td style="vertical-align: top;">O<br>
5236
5237
5238
5239
5240
5241      </td>
5242
5243
5244
5245
5246
5247      <td style="vertical-align: top;">Binary<br>
5248
5249
5250
5251
5252
5253      </td>
5254
5255
5256
5257
5258
5259      <td style="vertical-align: top;">Binary
5260data, which are output at the end of the
5261run and possibly needed by restart runs (see <a href="chapter_3.3.html">chapter
52623.3</a>) for the initialization. This output file is then read as
5263file <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.
5264The file is only written if particle transport is switched on (see the <a href="chapter_4.2.html#particles_package">particles
5265package</a>). For a more detailed description of the file structure see
5266      <a href="#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>.</td>
5267
5268
5269
5270
5271
5272    </tr>
5273
5274
5275
5276
5277
5278    <tr>
5279
5280
5281
5282
5283
5284      <td style="vertical-align: top; text-align: center;">90<br>
5285
5286
5287
5288
5289
5290      </td>
5291
5292
5293
5294
5295
5296      <td style="vertical-align: top;">
5297     
5298     
5299     
5300     
5301     
5302      <p><a name="PLOTTS_PAR"></a>PLOTTS_PAR&nbsp; </p>
5303
5304
5305
5306
5307
5308     
5309     
5310     
5311     
5312     
5313      <p>and/or&nbsp; <br>
5314
5315
5316
5317
5318
5319possibly&nbsp; </p>
5320
5321
5322
5323
5324
5325     
5326     
5327     
5328     
5329     
5330      <p>PLOTTS_PAR_0&nbsp; <br>
5331
5332
5333
5334
5335
5336PLOTTS_PAR_1&nbsp; <br>
5337
5338
5339
5340
5341
5342&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5343.&nbsp; <br>
5344
5345
5346
5347
5348
5349&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5350.&nbsp; <br>
5351
5352
5353
5354
5355
5356&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5357.&nbsp; <br>
5358
5359
5360
5361
5362
5363PLOTTS_PAR_9</p>
5364
5365
5366
5367
5368
5369      </td>
5370
5371
5372
5373
5374
5375      <td style="vertical-align: top;">O<br>
5376
5377
5378
5379
5380
5381      </td>
5382
5383
5384
5385
5386
5387      <td style="vertical-align: top;">Ascii/&nbsp; <br>
5388
5389
5390
5391
5392
5393NAMELIST</td>
5394
5395
5396
5397
5398
5399      <td style="vertical-align: top;">
5400     
5401     
5402     
5403     
5404     
5405      <p>NAMELIST parameter set, with which the layout of a plot
5406of the time series data in the local file <a href="#PLOTTS_DATA">PLOTTS_DATA</a>
5407can 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;
5408      </p>
5409
5410
5411
5412
5413
5414     
5415     
5416     
5417     
5418     
5419      <p>This file contains the so-called RAHMEN (frame)- and
5420CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
5421needed by <span style="font-weight: bold;">profil</span>. These
5422parameter sets (and thus all details of the layout) can be edited after
5423the model run by the user. By
5424default, all time series are drawn in different panels on one page. The
5425grouping is model-internally fixed and can only be
5426changed manually later. Only those time series specified by the
5427parameter <a href="chapter_4.2.html#data_output_ts">data_output_ts</a>
5428are actually drawn.&nbsp; </p>
5429
5430
5431
5432
5433
5434     
5435     
5436     
5437     
5438     
5439      <p>The file PLOTTS_PAR is allways produced by the model at
5440the beginning and at the end of a run, whereby at the end of the run
5441the file produced at the beginning is overwritten. Any later file
5442differs from the initial file by the fact that it additionally contains
5443ranges of values for the axes of coordinates. If a model run crashes
5444uncontrolled (e.g. run time error or CPU - time exceeded) a
5445parameter file is still available and the (incomplete) time
5446series can - contrary to the vertical profiles - nevertheless be
5447plotted.&nbsp; </p>
5448
5449
5450
5451
5452
5453     
5454     
5455     
5456     
5457     
5458      <p>If the model is to produce time series for different
5459subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
5460further files are output , whereby the file name gets an additionally
5461underline and the number of the respective subdomain is appended (e.g.
5462PLOTTS_PAR_1). The name of the file with NAMELIST-parameters for the
5463total domain in this case&nbsp; reads PLOTTS_PAR_0.&nbsp;&nbsp; <br>
5464
5465
5466
5467
5468
5469      </p>
5470
5471
5472
5473
5474
5475      </td>
5476
5477
5478
5479
5480
5481    </tr>
5482
5483
5484
5485
5486
5487    <tr>
5488
5489
5490
5491
5492
5493      <td style="vertical-align: top; text-align: center;">90<br>
5494
5495
5496
5497
5498
5499      </td>
5500
5501
5502
5503
5504
5505      <td style="vertical-align: top;">
5506     
5507     
5508     
5509     
5510     
5511      <p><a name="PLOT1D_PAR"></a>PLOT1D_PAR&nbsp; </p>
5512
5513
5514
5515
5516
5517     
5518     
5519     
5520     
5521     
5522      <p>and/or&nbsp; <br>
5523
5524
5525
5526
5527
5528possibly&nbsp; </p>
5529
5530
5531
5532
5533
5534     
5535     
5536     
5537     
5538     
5539      <p>PLOT1D_PAR_0&nbsp; <br>
5540
5541
5542
5543
5544
5545PLOT1D_PAR_1&nbsp; <br>
5546
5547
5548
5549
5550
5551&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5552.&nbsp; <br>
5553
5554
5555
5556
5557
5558&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5559.&nbsp; <br>
5560
5561
5562
5563
5564
5565&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5566.&nbsp; <br>
5567
5568
5569
5570
5571
5572PLOT1D_PAR_9</p>
5573
5574
5575
5576
5577
5578      </td>
5579
5580
5581
5582
5583
5584      <td style="vertical-align: top;">O<br>
5585
5586
5587
5588
5589
5590      </td>
5591
5592
5593
5594
5595
5596      <td style="vertical-align: top;">Ascii/ NAMELIST<br>
5597
5598
5599
5600
5601
5602      </td>
5603
5604
5605
5606
5607
5608      <td style="vertical-align: top;">
5609     
5610     
5611     
5612     
5613     
5614      <p>NAMELIST parameter set, with which the layout of a plot
5615of the data in the local file <a href="#PLOT1D_DATA">PLOT1D_DATA</a>
5616can 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;
5617      </p>
5618
5619
5620
5621
5622
5623     
5624     
5625     
5626     
5627     
5628      <p>This file contains the so-called RAHMEN (frame)- and
5629CROSS-parameter sets (NAMELIST- group names <span style="font-style: normal;">&amp;RAHMEN and/or &amp;CROSS</span>)
5630needed by <span style="font-weight: bold;">profil</span>.
5631These parameter sets (and thus all details of the plot layout) can be
5632edited after the model run by the user. By default, all profiles of one
5633variable saved at different times are drawn into one panel. Different
5634colors are used for each output time. Which profiles are drawn
5635into which plane and how these planes are arranged on the
5636plot, is determined with the parameters <a href="chapter_4.2.html#cross_profiles">cross_profiles</a>, <a href="chapter_4.2.html#profile_columns">profile_columns</a>
5637and <a href="chapter_4.2.html#profile_rows">profile_rows</a>.&nbsp; </p>
5638
5639
5640
5641
5642
5643     
5644     
5645     
5646     
5647     
5648      <p>The file PLOT1D_PAR is created by the model briefly before
5649the end of a run. If a model run crashes uncontrolled (run time
5650errors or CPU - time exceeded), this file is usually missing, although
5651profile data were saved to the file PLOT1D_DATA.&nbsp; </p>
5652
5653
5654
5655
5656
5657     
5658     
5659     
5660     
5661     
5662      <p>If the model has to create profiles for different subdomains
5663(see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>),
5664further files are created, whereby the file name includes the number of
5665the respective subdomain (e.g. PLOT1D_PAR_1). In this case the name of
5666the file with NAMELIST parameters of the total domain is
5667PLOT1D_PAR_0.&nbsp; </p>
5668
5669
5670
5671
5672
5673     
5674     
5675     
5676     
5677     
5678      <p>For presentation in the same plot, profile data of the restart
5679runs can be appended to existing data of preceding runs of a job chain.
5680One can do this with the file attribute <a href="http://www.muk.uni-hannover.de/institut/software/mrun_beschreibung.html#tra">tra</a>
5681in the file connection statement for PLOT1D_DATA. The model produces
5682a parameter file PLOT1D_PAR for these combined data, if the run
5683parameter is set <a href="chapter_4.2.html#use_prior_plot1d_parameters">use_prior_plot1d_parameters</a>
5684= <i>.T</i>. If this is omitted, then the parameter file gives
5685wrong plots (i.e. <span style="font-family: monospace;">use_prior_plot1d_parameters
5686= .T.</span> and "<span style="font-family: monospace;">tra</span>"
5687must be specified together)!</p>
5688
5689
5690
5691
5692
5693      </td>
5694
5695
5696
5697
5698
5699    </tr>
5700
5701
5702
5703
5704
5705    <tr>
5706
5707
5708
5709
5710
5711      <td style="vertical-align: top; text-align: center;">90<br>
5712
5713
5714
5715
5716
5717      </td>
5718
5719
5720
5721
5722
5723      <td style="vertical-align: top;"><a name="PLOT2D_XY_GLOBAL"></a>PLOT2D_XY_GLOBAL</td>
5724
5725
5726
5727
5728
5729      <td style="vertical-align: top;">O<br>
5730
5731
5732
5733
5734
5735      </td>
5736
5737
5738
5739
5740
5741      <td style="vertical-align: top;">Ascii/&nbsp; <br>
5742
5743
5744
5745
5746
5747NAMELIST</td>
5748
5749
5750
5751
5752
5753      <td style="vertical-align: top;">
5754     
5755     
5756     
5757     
5758     
5759      <p>NAMELIST parameter set, with which the plot layout
5760of the data in local file <a href="#PLOT2D_XY">PLOT2D_XY</a>
5761can 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>.
5762This file contains the so-called global parameter set (NAMELIST - group
5763name: &amp;GLOBAL) needed by <span style="font-weight: bold;">iso2d</span>.
5764This parameter set can be edited
5765after the model run by the user. By default, the arrays are drawn using
5766isolines and each array
5767will be drawn onto a separate page (thus no color shading
5768presentation, no vector arrows, streamlines etc.).&nbsp; </p>
5769
5770
5771
5772
5773
5774     
5775     
5776     
5777     
5778     
5779      <p>Additionally <span style="font-weight: bold;">iso2d</span>
5780needs the so-called local parameter
5781sets. These are saved by the model to the local file <a href="#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>.
5782Due to the fact that <span style="font-weight: bold;">iso2d</span>
5783expects global and local parameter sets on one and the same
5784file, in fact the global parameter set first, the user has to append
5785the contents of the file PLOT2D_XY_LOCAL to the file PLOT2D_XY_GLOBAL
5786before call of <span style="font-weight: bold;">iso2d</span> (e.g. by
5787an OUTPUT - command in the MRUN -
5788configuration file: &ldquo;cat PLOT2D_XY_LOCAL &gt;&gt; PLOT2D_XY_GLOBAL&rdquo;).
5789This
5790relatively pedantic proceedure is due to the fact that the model can
5791create the file PLOT2D_XY_GLOBAL only at the end of the simulation
5792(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>
5793is known), while the local parameter sets are written continuously
5794to the file PLOT2D_XY_LOCAL during the run. Since the file
5795PLOT2D_XY_GLOBAL needs to be addressed only briefly once, output-unit
579690 is used, which is also used for other files.</p>
5797
5798
5799
5800
5801
5802      </td>
5803
5804
5805
5806
5807
5808    </tr>
5809
5810
5811
5812
5813
5814    <tr>
5815
5816
5817
5818
5819
5820      <td style="vertical-align: top; text-align: center;">90<br>
5821
5822
5823
5824
5825
5826      </td>
5827
5828
5829
5830
5831
5832      <td style="vertical-align: top;"><a name="PLOT2D_XZ_GLOBAL"></a>PLOT2D_XZ_GLOBAL</td>
5833
5834
5835
5836
5837
5838      <td style="vertical-align: top;">O<br>
5839
5840
5841
5842
5843
5844      </td>
5845
5846
5847
5848
5849
5850      <td style="vertical-align: top;">Ascii/&nbsp; <br>
5851
5852
5853
5854
5855
5856NAMELIST</td>
5857
5858
5859
5860
5861
5862      <td style="vertical-align: top;">
5863     
5864     
5865     
5866     
5867     
5868      <p>NAMELIST parameter set, with which the plot layout of the data
5869in the local file <a href="#PLOT2D_XZ">PLOT2D_XZ</a>
5870can 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;
5871      </p>
5872
5873
5874
5875
5876
5877     
5878     
5879     
5880     
5881     
5882      <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
5883applies to this file, respectively.</p>
5884
5885
5886
5887
5888
5889      </td>
5890
5891
5892
5893
5894
5895    </tr>
5896
5897
5898
5899
5900
5901    <tr>
5902
5903
5904
5905
5906
5907      <td style="vertical-align: top; text-align: center;">90<br>
5908
5909
5910
5911
5912
5913      </td>
5914
5915
5916
5917
5918
5919      <td style="vertical-align: top;"><a name="PLOT2D_YZ_GLOBAL"></a>PLOT2D_YZ_GLOBAL</td>
5920
5921
5922
5923
5924
5925      <td style="vertical-align: top;">O<br>
5926
5927
5928
5929
5930
5931      </td>
5932
5933
5934
5935
5936
5937      <td style="vertical-align: top;">Ascii/&nbsp; <br>
5938
5939
5940
5941
5942
5943NAMELIST</td>
5944
5945
5946
5947
5948
5949      <td style="vertical-align: top;">
5950     
5951     
5952     
5953     
5954     
5955      <p>NAMELIST parameter set, with which the plot layout of the data
5956in the local file <a href="#PLOT2D_YZ">PLOT2D_YZ</a>
5957can 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;
5958      </p>
5959
5960
5961
5962
5963
5964     
5965     
5966     
5967     
5968     
5969      <p>The description of the local file <a href="#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>
5970applies to this file, respectively.</p>
5971
5972
5973
5974
5975
5976      </td>
5977
5978
5979
5980
5981
5982    </tr>
5983
5984
5985
5986
5987    <tr>
5988
5989
5990
5991
5992      <td style="vertical-align: top; text-align: center;">90</td>
5993
5994
5995
5996
5997      <td style="vertical-align: top;"><a name="TOPOGRAPHY_DATA"></a>TOPOGRAPHY_DATA</td>
5998
5999
6000
6001
6002      <td style="vertical-align: top;">I</td>
6003
6004
6005
6006
6007      <td style="vertical-align: top;">Ascii</td>
6008
6009
6010
6011
6012      <td>Two-dimensional&nbsp;<font color="#000000">topography height information</font> in m.<br>
6013
6014
6015
6016
6017In case of &nbsp;<a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'read_from_file'</span> the&nbsp;subroutine <span style="font-family: Cumberland AMT;">init_grid</span>&nbsp;reads the topography height information in m for each grid point in
6018a free floating point format. The data on file are laid out naturally,
6019i.e. in W-E orientation horizontally and in S-N orientation vertically,
6020they must thus be organized as follows:<br>
6021
6022
6023     
6024     
6025      <ul>
6026
6027
6028        <li>each line contains height information in m from <span style="font-style: italic;">i = 0, ..., nx</span>,</li>
6029
6030
6031        <li>the top line contains height information in m for <span style="font-style: italic;">j = ny</span> (North), the bottom line for <span style="font-style: italic;">j = 0</span> (South),</li>
6032
6033
6034        <li>individual data must be separated by at least one blank.</li>
6035
6036
6037     
6038     
6039      </ul>
6040
6041
6042Layout sketch:<br>
6043
6044
6045      <span style="font-family: Cumberland AMT;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;N<br>
6046
6047
6048&nbsp; &nbsp; (0,ny) &nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,ny) &nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,ny) &nbsp; ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny) &nbsp; &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>
6049
6050
6051      <font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp; (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) ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-1) &nbsp;<br>
6052
6053
6054      </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; (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) ...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,ny-2) &nbsp; E<br>
6055
6056
6057      </span></font></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
6058
6059
6060&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:<br>
6061
6062
6063      </span></font></font><font color="#000000"><font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp; (0,0) &nbsp;&nbsp;&nbsp;</span><font color="#000000"><span style="font-family: Cumberland AMT;">(1,0) &nbsp;&nbsp;&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(2,0) &nbsp; &nbsp;...&nbsp;</span></font><font color="#000000"><span style="font-family: Cumberland AMT;">(nx,0) &nbsp; &nbsp; &nbsp;&nbsp;</span></font></font></font><font color="#000000">&nbsp;bottom of file</font><br>
6064
6065
6066      <font color="#000000"><span style="font-family: Cumberland AMT;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp;S</span></font><br>
6067
6068
6069      <font style="font-family: Arial;" color="#000000"></font><span style="font-family: Arial;"></span><br>
6070
6071
6072
6073
6074These data must exactly match the horizontal grid.<br>
6075
6076
6077Alternatively, the user may add code to the user interface subroutine <a href="chapter_3.5.1.html#user_init_grid">user_init_grid</a> to allow different data formats.</td>
6078
6079
6080
6081
6082      <td><br>
6083
6084      </td>
6085
6086
6087
6088
6089    </tr>
6090    <tr>
6091
6092      <td style="vertical-align: top; text-align: center;"><font color="#000000">101</font></td>
6093
6094      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XY_NETCDF"></a>DATA_2D_XY_NETCDF</font></td>
6095
6096      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6097
6098      <td style="vertical-align: top;"><font color="#000000">Binary/<br>
6099
6100NetCDF-<br>
6101
6102format</font></td>
6103
6104      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional horizontal
6105cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
6106in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6107
6108      <br>
6109
6110More 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>
6111
6112      <td style="vertical-align: top;"><br>
6113
6114      </td>
6115
6116    </tr>
6117
6118    <tr>
6119
6120      <td style="vertical-align: top; text-align: center;"><font color="#000000">102</font></td>
6121
6122      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_XZ_NETCDF"></a>DATA_2D_XZ_NETCDF</font></td>
6123
6124      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6125
6126      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6127
6128NetCDF-<br>
6129
6130format</font></font></td>
6131
6132      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional vertical (xz)
6133cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
6134in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6135
6136      <br>
6137
6138More 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>
6139
6140      <td style="vertical-align: top;"><br>
6141
6142      </td>
6143
6144    </tr>
6145
6146    <tr>
6147
6148      <td style="vertical-align: top; text-align: center;"><font color="#000000">103</font></td>
6149
6150      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_NETCDF"></a>DATA_2D_YZ_NETCDF</font></td>
6151
6152      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6153
6154      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6155
6156NetCDF-<br>
6157
6158format</font></font></td>
6159
6160      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the two-dimensional vertical
6161(yz) cross sections (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
6162in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6163
6164      <br>
6165
6166More 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>
6167
6168      <td style="vertical-align: top;"><br>
6169
6170      </td>
6171
6172    </tr>
6173
6174    <tr>
6175
6176      <td style="vertical-align: top; text-align: center;"><font color="#000000">104</font></td>
6177
6178      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_PR_NETCDF"></a>DATA_1D_PR_NETCDF</font></td>
6179
6180      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6181
6182      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6183
6184NetCDF-<br>
6185
6186format</font></font></td>
6187
6188      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the horizontally averaged vertical profiles (see <a href="../app/chapter_4.2.html#data_output_pr">data_output_pr</a>)
6189in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6190
6191      <br>
6192
6193More 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>
6194
6195      <td style="vertical-align: top;"><br>
6196
6197      </td>
6198
6199    </tr>
6200
6201    <tr>
6202
6203      <td style="vertical-align: top; text-align: center;"><font color="#000000">105</font></td>
6204
6205      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_TS_NETCDF"></a>DATA_1D_TS_NETCDF</font></td>
6206
6207      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6208
6209      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6210
6211NetCDF-<br>
6212
6213format</font></font></td>
6214
6215      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the timeseries (see <a href="../app/chapter_4.2.html#data_output_ts">data_output_ts</a>)
6216in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6217
6218      <br>
6219
6220More 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>
6221
6222      <td style="vertical-align: top;"><br>
6223
6224      </td>
6225
6226    </tr>
6227
6228    <tr>
6229
6230      <td style="vertical-align: top; text-align: center;"><font color="#000000">106</font></td>
6231
6232      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_NETCDF"></a>DATA_3D_NETCDF</font></td>
6233
6234      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6235
6236      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6237
6238NetCDF-<br>
6239
6240format</font></font></td>
6241
6242      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the 3d-volume data (see <a href="../app/chapter_4.2.html#data_output">data_output</a>)
6243in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6244
6245      <br>
6246
6247More 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>
6248
6249      <td style="vertical-align: top;"><br>
6250
6251      </td>
6252
6253    </tr>
6254
6255    <tr>
6256
6257      <td style="vertical-align: top; text-align: center;"><font color="#000000">107</font></td>
6258
6259      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_1D_SP_NETCDF"></a>DATA_1D_SP_NETCDF</font></td>
6260
6261      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6262
6263      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6264
6265NetCDF-<br>
6266
6267format</font></font></td>
6268
6269      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the horizontal spectra (see <a href="../app/chapter_4.2.html#data_output_sp">data_output_sp</a>)
6270in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6271
6272      <br>
6273
6274More 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>
6275
6276      <td style="vertical-align: top;"><br>
6277
6278      </td>
6279
6280    </tr>
6281
6282    <tr>
6283
6284      <td style="vertical-align: top; text-align: center;"><font color="#000000">108</font></td>
6285
6286      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_PRT_NETCDF"></a>DATA_PRT_NETCDF/</font></td>
6287
6288      <td style="vertical-align: top;"><font color="#000000">I/O</font></td>
6289
6290      <td style="vertical-align: top;"><font color="#000000"><font color="#000000">Binary/<br>
6291
6292NetCDF-<br>
6293
6294format</font></font></td>
6295
6296      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains particle data (see <a href="../app/chapter_4.2.html#dt_prel">dt_prel</a>)
6297in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6298
6299      <br>
6300
6301More 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>
6302
6303      <td style="vertical-align: top;"><br>
6304
6305      </td>
6306
6307    </tr>
6308    <tr>
6309      <td style="vertical-align: top; text-align: center;">109</td>
6310      <td align="left" valign="top"><a name="DATA_1D_PTS_NETCDF"></a>DATA_1D_PTS_NETCDF</td>
6311      <td align="left" valign="top">I/O</td>
6312      <td align="left" valign="top">Binary/<br>
6313NetCDF-<br>
6314format</td>
6315      <td align="left" valign="top">This file contains data of the timeseries of particle quantities (<font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">see <a href="chapter_4.2.html#dt_prel">dt_prel</a>)
6316in NetCDF format.&nbsp;</font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>). For a list of available output quantities see </font></font></font></font><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"> <a href="chapter_4.2.html#dt_dopts">dt_dopts</a>.</font></font></font></font></font><br>
6317      <font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000"><br>
6318      </font></font></font></font><span lang="en-GB"><font face="Thorndale">In case of using more than one particle group (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
6319seperate time series are output for each of the groups. The long names
6320of the variables in the NetCDF file containing the respective
6321timeseries 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 group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br>
6322      <br>
6323      </font></span><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">More 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>
6324      <td align="left" valign="top"></td>
6325    </tr>
6326    <tr>
6327      <td style="text-align: center; vertical-align: top;">111</td>
6328      <td style="vertical-align: top;"><a name="DATA_2D_XY_AV_NETCDF"></a>DATA_2D_XY_AV_NETCDF</td>
6329      <td style="vertical-align: top;">I/O</td>
6330      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
6331
6332NetCDF-<br>
6333
6334format</font></font></font></td>
6335      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged two-dimensional horizontal
6336cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
6337in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6338
6339      <br>
6340
6341More 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>
6342      <td></td>
6343    </tr>
6344    <tr>
6345      <td style="text-align: center; vertical-align: top;">112</td>
6346      <td style="vertical-align: top;"><a name="DATA_2D_XZ_AV_NETCDF"></a>DATA_2D_XZ_AV_NETCDF</td>
6347      <td style="vertical-align: top;">I/O</td>
6348      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
6349
6350NetCDF-<br>
6351
6352format</font></font></font></td>
6353      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged two-dimensional vertical (xz)
6354cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
6355in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6356
6357      <br>
6358
6359More 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>
6360      <td></td>
6361    </tr>
6362    <tr>
6363      <td style="text-align: center; vertical-align: top;">113</td>
6364      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_2D_YZ_AV_NETCDF"></a>DATA_2D_YZ_AV_NETCDF</font></td>
6365      <td style="vertical-align: top;">I/O</td>
6366      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
6367
6368NetCDF-<br>
6369
6370format</font></font></font></td>
6371      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged two-dimensional vertical
6372(yz) cross sections (see <a href="chapter_4.2.html#data_output">data_output</a>)
6373in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6374
6375      <br>
6376
6377More 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>
6378      <td></td>
6379    </tr>
6380    <tr>
6381      <td style="text-align: center; vertical-align: top;">116</td>
6382      <td style="vertical-align: top;"><font color="#000000"><a name="DATA_3D_AV_NETCDF"></a>DATA_3D_AV_NETCDF</font></td>
6383      <td style="vertical-align: top;">I/O</td>
6384      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000">Binary/<br>
6385
6386NetCDF-<br>
6387
6388format</font></font></font></td>
6389      <td style="vertical-align: top;"><font color="#000000"><font color="#000000"><font color="#000000"><font color="#000000">This file contains data of the temporally averaged 3d-volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
6390in NetCDF format. The data in this file can be visualized by any graphic software which provides a NetCDF interface (e.g. <span style="font-weight: bold;">NCL </span>or<span style="font-weight: bold;"> ferret</span>).<br>
6391
6392      <br>
6393
6394More 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>
6395      <td></td>
6396    </tr>
6397
6398
6399
6400
6401
6402
6403 
6404 
6405 
6406 
6407 
6408  </tbody>
6409</table>
6410
6411
6412
6413
6414
6415<font color="#000000"><br>
6416
6417
6418
6419
6420
6421</font>
6422<br>
6423
6424
6425
6426
6427
6428<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>
6429
6430
6431
6432
6433
6434&nbsp;
6435<br>
6436
6437
6438
6439
6440
6441&nbsp;
6442<span style="font-style: italic;">Last change:</span> 07/11/06 (ML)<br>
6443
6444
6445
6446
6447
6448</font><br>
6449
6450
6451
6452
6453
6454</body>
6455</html>
Note: See TracBrowser for help on using the repository browser.
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |