Home

Context Navigation

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

Last change on this file since 349 was 270, checked in by letzel, 16 years ago
update of chapter 3.4
Property svn:keywords set to `Id`
File size: 104.9 KB

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

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

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |