Home

Context Navigation

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

Last change on this file since 55 was 54, checked in by raasch, 18 years ago
property Id set for most of all files, small bug in mbuild fixed
Property svn:keywords set to `Id`
File size: 102.3 KB

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

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

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |