Home

Context Navigation

source: palm/trunk/DOC/app/chapter_4.2.html @ 104

Last change on this file since 104 was 103, checked in by raasch, 17 years ago
further preliminary changes concerning coupling
Property svn:keywords set to `Id`
File size: 232.5 KB

Rev	Line
[5]	1	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
	2	<html><head>
[48]	3	<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>PALM chapter 4.2</title></head>
	4	<body><h3 style="line-height: 100%;"><a name="Kapitel4.2"></a>4.2 <a href="#Laufparameter">Runtime
[102]	5	parameters</a>, <a href="#particle_parameters">particle parameters</a>, and <a href="#Paketparameter">package
[5]	6	parameters</a></h3>
[48]	7	<h3 style="margin-bottom: 0cm; line-height: 100%;"><a name="Laufparameter"></a>Runtime parameters:</h3>
[61]	8	<br><br><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody>
	9	<tr>
[48]	10	<td style="vertical-align: top;"><font size="4"><b>Parameter
	11	name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
	12	<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
	13	<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
	14	</tr> <tr> <td style="vertical-align: top;"><a name="averaging_interval"></a><span style="font-weight: bold;">averaging_interval</span><br>
	15	</td> <td style="vertical-align: top;">R<br> </td>
	16	<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
	17	<td style="vertical-align: top;">Averaging interval for
	18	all output of temporally averaged data (in s).<br><br>This
[5]	19	parameter defines the time interval length for temporally averaged data
	20	(vertical profiles, spectra, 2d cross-sections, 3d volume data). By
[48]	21	default, data are not subject to temporal averaging. The
	22	interval
	23	length is limited by the parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
	24	In any case, <span style="font-weight: bold;">averaging_interval</span>
	25	<= <span style="font-weight: bold;">dt_data_output_av</span>
	26	must hold.<br><br>If
[5]	27	an interval is defined, then by default the average is calculated from
	28	the data values of all timesteps lying within this interval. The number
	29	of time levels entering into the average can be reduced with the
[48]	30	parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<br><br>If
	31	an averaging interval can not be completed at the end of a run, it
[5]	32	will be finished at the beginning of the next restart run. Thus for
	33	restart runs, averaging intervals do not
[48]	34	necessarily begin at the beginning of the run.<br><br>Parameters
	35	<a href="#averaging_interval_pr">averaging_interval_pr</a>
	36	and <a href="#averaging_interval_sp">averaging_interval_sp</a>
	37	can be used to define different averaging intervals for vertical
	38	profile data and spectra, respectively.<br> </td> </tr>
	39	<tr> <td style="vertical-align: top;"> <p><a name="averaging_interval_pr"></a><b>averaging_interval_pr</b></p>
	40	</td> <td style="vertical-align: top;">R<br> </td>
	41	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#averaging_interval">averaging_<br>
[5]	42	interval</a><br>
[61]	43	</span> </td> <td style="vertical-align: top;"><p>Averaging
	44	interval for output of vertical profiles to
[48]	45	local
	46	file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
	47	</font></font>and/or  <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
	48	(in s).  </p> <p>If
[5]	49	this parameter is given a non-zero value, temporally
	50	averaged vertical profile data are output. By default, profile data
	51	data are not subject to temporal averaging. The interval length is
[48]	52	limited by the parameter <a href="#dt_dopr">dt_dopr</a>.
	53	In any case <b>averaging_interval_pr</b> <= <b>dt_dopr
	54	</b>must
	55	hold.</p>If an interval is defined, then by default the average
	56	is calculated
[5]	57	from the data values of all timesteps lying within this interval. The
	58	number of time levels entering into the average can be reduced with the
	59	parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>.
[48]	60	<p>If
[5]	61	an averaging interval can not be completed at the end of a run, it will
	62	be finished at the beginning of the next restart run. Thus for restart
	63	runs, averaging intervals do not
[48]	64	necessarily begin at the beginning of the run.</p> </td> </tr>
	65	<tr> <td style="vertical-align: top;"><a name="call_psolver_at_all_substeps"></a><span style="font-weight: bold;">call_psolver_at_all_<br>
	66	substeps</span></td> <td style="vertical-align: top;">L<br>
	67	</td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
	68	<td style="vertical-align: top;">Switch
	69	to steer the call of the pressure solver.<br> <br>
[5]	70	In order to speed-up performance, the Poisson equation for perturbation
[48]	71	pressure (see <a href="#psolver">psolver</a>) can
	72	be called only at the last substep of multistep Runge-Kutta
	73	timestep schemes (see <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>)
	74	by setting <span style="font-weight: bold;">call_psolver_at_all_substeps</span>
	75	= <span style="font-style: italic;">.F.</span>.
[5]	76	In many cases, this sufficiently reduces the divergence of the velocity
	77	field. Nevertheless, small-scale ripples (2-delta-x) may occur. In this
	78	case and in case
[48]	79	of non-cyclic lateral boundary conditions, <span style="font-weight: bold;">call_psolver_at_all_timesteps</span>
	80	= <span style="font-style: italic;">.T.</span>
	81	should be used. <span style="font-weight: bold;"></span></td>
[61]	82	</tr> <tr> <td style="vertical-align: top;"><p><a name="fcl_factor"></a><b>cfl_factor</b></p>
[48]	83	</td> <td style="vertical-align: top;">R<br> </td>
	84	<td style="vertical-align: top;"> <p><i>0.1,
	85	0.8 or 0.9</i> <br> <i>(see right)</i></p>
	86	</td> <td style="vertical-align: top;"> <p lang="en-GB">Time step limiting factor.  </p>
	87	<p><span lang="en-GB">In the model, the <span lang="en-GB">maximum
	88	allowed </span>time step according to CFL and
	89	diffusion-criterion
	90	dt_max is reduced by </span><a href="chapter_4.1.html#dt"><span lang="en-GB">dt</span></a> <span lang="en-GB">=
	91	dt_max * <b>cfl_factor</b>
[5]	92	in order to avoid stability problems which may arise in the vicinity of
[48]	93	the maximum allowed timestep. The condition <i>0.0</i>
	94	< <b>cfl_factor</b>
	95	< <i>1.0 </i>applies.<br> </span></p>
	96	<p><span lang="en-GB">The default value of
	97	cfl_factor depends on
	98	the </span><a href="chapter_4.1.html#timestep_scheme"><span lang="en-GB">timestep_scheme</span></a><span lang="en-GB"> used:<br> </span></p> <p><span lang="en-GB">For the third order Runge-Kutta scheme it
	99	is <b>cfl_factor</b> = </span><span style="font-style: italic;">0.9</span><span lang="en-GB">.<br> </span></p> <p><span lang="en-GB">In case of the leapfrog scheme a quite
[5]	100	restrictive value of <span style="font-weight: bold;">cfl_factor</span>
[48]	101	= <span style="font-style: italic;">0.1 </span></span><span lang="en-GB">is used because for larger values the velocity
	102	divergence
[5]	103	significantly effects the accuracy of the model results.</span><a href="chapter_4.1.html#scalar_advec"><span lang="en-GB"></span></a><span lang="en-GB"> Possibly larger values may
	104	be used with the leapfrog scheme but these are to be determined by
	105	appropriate test runs.<span style="font-family: times new roman;"><br>
[48]	106	</span></span></p> <span lang="en-GB"><span style="font-family: times new roman;"></span><font face="Times New Roman">The default value for the Euler
	107	scheme is <span style="font-weight: bold;">cfl_factor</span>
	108	= <span style="font-style: italic;">0.8</span> .</font></span></td>
[61]	109	</tr><tr> <td style="vertical-align: top;"> <p><a name="create_disturbances"></a><b>create_disturbances</b></p>
[48]	110	</td> <td style="vertical-align: top;">L<br> </td>
	111	<td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
	112	<td style="vertical-align: top;"> <p>Switch to
	113	impose random perturbations to the horizontal
	114	velocity field.  </p> <p>With <b>create_disturbances</b>
	115	= <i>.T.,</i> random
[5]	116	perturbations can be imposed to the horizontal velocity field at
	117	certain times e.g. in order to trigger off the onset of convection,
[48]	118	etc..<br> </p> <p>The temporal interval between
	119	these times can be steered with <a href="#dt_disturb">dt_disturb</a>,
[5]	120	the vertical range of the perturbations with <a href="#disturbance_level_b">disturbance_level_b</a>
	121	and <a href="#disturbance_level_t">disturbance_level_t</a>,
	122	and the perturbation amplitude with <a href="#disturbance_amplitude">disturbance_amplitude</a>.
	123	In case of non-cyclic lateral boundary conditions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
	124	and <a href="chapter_4.1.html#bc_ns">bc_ns</a>),
	125	the horizontal range of the perturbations is determined by <a href="chapter_4.1.html#inflow_disturbance_begin">inflow_disturbance_begin</a>
	126	and <a href="chapter_4.1.html#inflow_disturbance_end">inflow_disturbance_end</a>.
	127	A perturbation is added to each grid point with its individual value
	128	determined by multiplying the disturbance amplitude with a uniformly
	129	distributed random number.
	130	After this, the arrays of u and v are smoothed by applying a
	131	Shuman-filter twice and made divergence-free by applying the pressure
[48]	132	solver.<br> </p> <p>The random number generator to
	133	be used can be chosen with <a href="chapter_4.1.html#random_generator">random_generator</a>.<br>
	134	</p> <p>As soon as the desired flow features have
	135	developed
	136	(e.g.  convection has started), further imposing of
	137	perturbations
[5]	138	is not necessary and can be omitted (this does not hold for non-cyclic
	139	lateral boundaries!). This can be steered by assigning
	140	an upper limit value for the perturbation energy (the perturbation
	141	energy is defined by the deviation of the velocity from the mean flow)
	142	using the parameter <a href="#disturbance_energy_limit">disturbance_energy_limit</a>.
	143	As soon as the perturbation energy has exceeded this energy limit, no
	144	more random perturbations are assigned<br>
	145	.  <br>
	146	Timesteps where a random perturbation has been imposed are marked in
	147	the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
	148	by the character "D" appended to the values of the maximum horizontal
[48]	149	velocities. </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_x"></a><b>cross_normalized_x</b></p>
	150	</td> <td style="vertical-align: top;">C*10
	151	<br>   (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td>
	152	<td style="vertical-align: top;"> <p>Type of
	153	normalization applied to the x-coordinate of vertical
[5]	154	profiles to be plotted with <span style="font-weight: bold;">profil</span>.</p>
[48]	155	<p>This parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	156	= <span style="font-style: italic;">'profil'</span>.</p><p>If
	157	vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
	158	local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
[5]	159	parameters on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
	160	the x-values of the data points can be normalized with respect to
	161	certain quantities (e.g. the near-surface heat flux) in order to ensure
	162	a better comparability. This type of normalization then applies to all
	163	profiles of one coordinate system (panel). The normalization quantities
	164	are re-calculated for each output time of each individual profile. If
	165	temporally averaged profiles are output (see <a href="#averaging_interval_pr">averaging_interval_pr</a>),
	166	then the normalization quantities are also temporally averaged
	167	accordingly. If the value of a normalization quantity becomes zero,
	168	then normalization for the total respective coordinate system (panel)
[48]	169	is switched off automatically (also for the y-axis).<br> </p>
	170	<p>By default, the normalization quantities are calculated as the
[5]	171	horizontal mean of the total model domain and and these values are also
	172	used for the normalization of profiles from subdomains (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
	173	Instead of this, they can be calculated from the data of a certain
	174	subdomain by using the parameter <a href="#normalizing_region">normalizing_region</a>
	175	(however, they are used again for all subdomains and even for the total
[48]	176	domain).  </p> <p>The user can choose between
	177	the following normalization
	178	quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'wpt0'</i></td>
	179	<td style="vertical-align: top;">Normalization with
	180	respect
[5]	181	to the total surface sensible heat
[48]	182	flux (k=0 ).</td> </tr> <tr> <td style="vertical-align: middle;"><i>'ws2'</i></td>
	183	<td style="vertical-align: top;">Normalization with
	184	respect
[5]	185	to w<sub>*</sub> <sup>2</sup>
	186	(square of the characteristic vertical wind speed of the CBL)</td>
[48]	187	</tr> <tr> <td style="vertical-align: top;"><i>'tsw2'</i></td>
	188	<td style="vertical-align: top;">Normalization with
	189	respect
[5]	190	to the square of the characteristic
[48]	191	temperature of the CBL theta<sub>*</sub> (this is defined
	192	as ratio of
	193	the surface heat flux and w<sub>*</sub>).</td> </tr>
	194	<tr> <td style="vertical-align: middle;"><i>'ws3'</i></td>
	195	<td style="vertical-align: top;">Normalization with
	196	respect
	197	to w<sub>*</sub> <sup>3</sup>.</td> </tr>
	198	<tr> <td style="vertical-align: middle;"><i>'ws2tsw'</i></td>
	199	<td style="vertical-align: top;">Normalization with
	200	respect
[5]	201	to w<sub></sub><sup>2</sup>theta<sub></sub>
	202	(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
[48]	203	</tr> <tr> <td style="vertical-align: middle;"><i>'wstsw2'</i></td>
	204	<td style="vertical-align: top;">Normalization with
	205	respect
[5]	206	to w<sub></sub><sup>2 </sup>theta<sub></sub>
	207	(for definition of theta<sub>*</sub> see <span style="font-style: italic;">'tsw2'</span>).</td>
[48]	208	</tr> </tbody> </table> <p>For each
	209	coordinate system (panel) to be drawn (see <a href="#cross_profiles">cross_profiles</a>)
	210	an individual normalization quantity can be assigned. For example: if <span style="font-weight: bold;">cross_normalized_x</span> =
	211	<span style="font-style: italic;">'ws2'</span><i>,'ws3'</i>,
	212	then the
[5]	213	x-values in the 1st coordinate system are normalized with respect to w<sub>*</sub><sup>2</sup>
[48]	214	and in the 2nd system with respect to w<sub>*</sub><sup>3</sup>.
	215	Data
[5]	216	of the further coordinate systems (if any are to be drawn) are not
[48]	217	normalized.  </p> <p>Using a normalization
	218	leaves all vertical profile data on
[5]	219	local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
[48]	220	unaffected, it only affects the visualization. Within <span style="font-weight: bold;">profil</span>, the
	221	normalization is steered
[5]	222	by parameter <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#NORMX">normx</a>
	223	which may be changed subsequently by the user in the parameter file
	224	(local file <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>).<br>
	225	<br>
	226	The assigned normalization quantity is noted in the axes labels of the
	227	respective coordinate systems (see <a href="#cross_xtext">cross_xtext</a>).</p>
[48]	228	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_normalized_y"></a><b>cross_normalized_y</b></p>
	229	</td> <td style="vertical-align: top;">C*10
	230	<br>   (100)</td> <td style="vertical-align: top;"><i>100 * ' '</i></td>
	231	<td style="vertical-align: top;"> <p>Type of
	232	normalization applied to the y-coordinate of vertical
[5]	233	profiles to be plotted with <span style="font-weight: bold;">profil</span>. </p>
[48]	234	<p>This parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	235	= <span style="font-style: italic;">'profil'</span>.</p><p>If
	236	vertical profiles are plotted with the plot software <span style="font-weight: bold;">profil</span> (data on
	237	local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
[5]	238	parameter on local file <a href="http://www.muk.uni-hannover.de/%7Eraasch/PALM_group/PLOT1D_PAR">PLOT1D_PAR</a>)
	239	the y-values of the data points can be normalized with respect to
	240	certain quantities (at present only the normalization with respect to
	241	the boundary layer height is possible) in order to ensure a better
[48]	242	comparability. </p> <p>The user can choose between the
	243	following normalization
	244	quantities: <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'z_i'</i></td>
	245	<td style="vertical-align: top;">Normalization with
	246	respect
[5]	247	to the boundary layer height
	248	(determined from the height where the heat flux achieves its minimum
[48]	249	value).</td> </tr> </tbody> </table> <p>For
	250	further explanations see <a href="#cross_normalized_x">cross_normalized_x.</a></p>
	251	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_profiles"></a><b>cross_profiles</b></p>
	252	</td> <td style="vertical-align: top;">C*100
	253	<br>   (100)</td> <td style="vertical-align: top;">see right<br> </td>
	254	<td style="vertical-align: top;"> <p>Determines
	255	which vertical profiles are to be presented in
	256	which coordinate system if the plot software <span style="font-weight: bold;">profil</span> is used.
	257	</p> <p>This parameter only applies for
	258	<a href="chapter_4.2.html#data_output_format">data_output_format</a>
	259	= <span style="font-style: italic;">'profil'</span>.</p><p>The
	260	default assignment is:  </p> <p><b>cross_profiles</b>
	261	=  </p> <ul> <p><span style="font-family: monospace; font-style: italic;">'
	262	u v ',</span><br> <span style="font-family: monospace; font-style: italic;">' pt
	263	',  </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">'
	264	w"pt" wpt wptBC wpt wptBC ',  </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">'
	265	w"u" wu wu w"v"wv wv ',  </span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' km
	266	kh ',</span><br style="font-family: monospace; font-style: italic;"> <span style="font-family: monospace; font-style: italic;">' l '
[5]	267	,</span><br>
[48]	268	14 * <span style="font-family: monospace; font-style: italic;">'
	269	'</span></p> </ul> <p>If plot output of
	270	vertical profiles is produced (see <a href="#data_output_pr">data_output_pr</a>),
[5]	271	the appropriate data are written to the local file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.
	272	Simultaneously, the model produces a parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
	273	which describes the layout for a plot to be generated with the plot
[48]	274	program <span style="font-weight: bold;">profil</span>.
	275	The parameter <b>cross_profiles</b>
[5]	276	determines how many coordinate systems (panels) the plot contains and
	277	which profiles are supposed to be drawn into which panel. <b>cross_profiles</b>
	278	expects a character string (up to 100 characters long) for each
	279	coordinate system, which consists of the names of the profiles to be
	280	drawn into this system (all available profiles and their respective
	281	names are described at parameter <a href="#data_output_pr">data_output_pr</a>).
	282	The single names have to be separated by one blank (' ') and a blank
[48]	283	must be spent also at the beginning and at the end of the
	284	string.  </p> <p>Example:  </p> <ul>
	285	<p><b>cross_profiles</b> = <span style="font-family: monospace; font-style: italic;">' u v ',
	286	' pt '</span></p> </ul> <p>In this case the
	287	plot consists of two coordinate systems
[5]	288	(panels) with the first panel containing the profiles of the horizontal
[48]	289	velocity components (<span style="font-style: italic;">'u'</span>
	290	and <span style="font-style: italic;">'v'</span>)
	291	of all output times (see <a href="#dt_dopr">dt_dopr</a>)
[5]	292	and the second one containing the profiles of the potential temperature
	293	(<span style="font-style: italic;">'pt'</span>).<br>
[48]	294	</p> <p>Whether the coordinate systems are actually drawn,
	295	depends on
[5]	296	whether data of the appropriate profiles were output during the run
	297	(profiles to be output have to be selected with the parameter <a href="#data_output_pr">data_output_pr</a>).
[48]	298	For example if <b>data_output_pr</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span> was assigned,
	299	then
[5]	300	the plot only consists of one panel, since no profiles of the potential
	301	temperature were output. On the other hand, if profiles were assigned
	302	to <b>data_output_pr </b>whose names do not appear in <b>cross_profiles</b>,
	303	then the respective profile data are output (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
[48]	304	but they are not drawn in the plot. <br> </p>
[5]	305	The arrangement of the panels in the plot can be controlled
	306	with the parameters <a href="#profile_columns">profile_columns</a>
	307	and <a href="#profile_rows">profile_rows</a>.
	308	Up to 100 panels systems are allowed in a plot (however, they may be
[48]	309	distributed on several pages).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cross_xtext"></a><b>cross_xtext</b></p>
	310	</td> <td style="vertical-align: top;">C*40
	311	<br>   (100)</td> <td style="vertical-align: top;">see right<br> </td>
	312	<td style="vertical-align: top;"> <p>x-axis labels
	313	of vertical profile coordinate systems to be
	314	plotted with <span style="font-weight: bold;">profil</span>.
	315	</p> <p>This parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	316	= <span style="font-style: italic;">'profil'</span>.</p><p>The
	317	default assignment is:  </p> <p><b>cross_xtext</b>
	318	=  </p> <ul> <p><span style="font-style: italic;">'wind speed in
	319	ms>->1',  </span><br style="font-style: italic;"> <span style="font-style: italic;">'pot. temperature in
[5]	320	K',  </span><br style="font-style: italic;">
[48]	321	<span style="font-style: italic;">'heat flux in K
	322	ms>->1',  </span><br style="font-style: italic;"> <span style="font-style: italic;">'momentum flux in
	323	m>2s>2',  </span><br style="font-style: italic;"> <span style="font-style: italic;">'eddy diffusivity in
	324	m>2s>->1',  </span><br style="font-style: italic;"> <span style="font-style: italic;">'mixing length in m',</span>
	325	<br>14 * <span style="font-style: italic;">' '</span></p>
	326	</ul> <p>This parameter can be used to assign x-axis
	327	labels to vertical
	328	profiles to be plotted with the plot software <span style="font-weight: bold;">profil </span>(for output
	329	of vertical
[5]	330	profile data see <a href="#data_output_pr">data_output_pr</a>).<br>
	331	The labels are assigned to those coordinate systems (panels) defined by
[48]	332	<a href="#cross_profiles">cross_profiles</a>
[5]	333	according to their respective order (compare the default values of <b>cross_xtext</b>
[48]	334	and <b>cross_profiles</b>). </p> <p>Umlauts
	335	are possible (write “ in front of, similar to TeX), as
	336	well as super- and subscripts (use ">" or "<" in front of
	337	each
[5]	338	character), special characters etc. (see UNIRAS manuals) when using the
	339	plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_beschreibung.html#chapter3.2.6">profil</a>.</p>
[48]	340	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="cycle_mg"></a><b>cycle_mg</b></p>
	341	</td> <td style="vertical-align: top;">C*1</td>
	342	<td style="vertical-align: top;"><i>'w'</i></td>
	343	<td style="vertical-align: top;"> <p>Type of cycle
	344	to be used with the multi-grid method.  </p> <p>This
	345	parameter determines which type of cycle is applied in
[5]	346	the multi-grid method used for solving the Poisson equation for
	347	perturbation pressure (see <a href="#psolver">psolver</a>).
	348	It defines in which way it is switched between the fine and coarse
	349	grids. So-called v- and w-cycles are realized (i.e. <b>cycle_mg</b>
[48]	350	may be assigned the values <i>'v'</i> or <i>'w'</i>).
	351	The
[5]	352	computational cost of w-cycles is much higher than that of v-cycles,
[48]	353	however, w-cycles give a much better convergence. </p> </td>
[61]	354	</tr> <tr> <td style="vertical-align: top;"><p><a name="data_output"></a><b>data_output</b></p>
[48]	355	</td> <td style="vertical-align: top;">C * 10 (100)<br>
	356	</td> <td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span><br>
	357	</td> <td style="vertical-align: top;">Quantities
	358	for which 2d cross section and/or 3d volume data are to be output.<br><br>PALM
[5]	359	allows the output of instantaneous data as well as of temporally
	360	averaged data which is steered by the strings assigned to this
[48]	361	parameter (see below).<br><br>By default, cross section
	362	data are output (depending on the selected cross sections(s), see
	363	below)  to local files <a href="chapter_3.4.html#DATA_2D_XY_NETCDF">DATA_2D_XY_NETCDF</a>,
	364	<a href="chapter_3.4.html#DATA_2D_XZ_NETCDF">DATA_2D_XZ_NETCDF</a>
	365	and/or <a href="chapter_3.4.html#DATA_2D_YZ_NETCDF">DATA_2D_YZ_NETCDF</a>.
	366	Volume data are output to file <a href="chapter_3.4.html#DATA_3D_NETCDF">DATA_3D_NETCDF</a>.
	367	If the user has switched on the output of temporally averaged data,
	368	these are written seperately to local files <a href="chapter_3.4.html#DATA_2D_XY_AV_NETCDF">DATA_2D_XY_AV_NETCDF</a>,
	369	<a href="chapter_3.4.html#DATA_2D_XZ_AV_NETCDF">DATA_2D_XZ_AV_NETCDF</a>,
	370	<a href="chapter_4.3.html#DATA_2D_YZ_AV_NETCDF">DATA_2D_YZ_AV_NETCDF</a>,
	371	and <a href="chapter_3.4.html#DATA_3D_AV_NETCDF">DATA_3D_AV_NETCDF</a>,
	372	respectively.<br><br>The
[5]	373	filenames already suggest that all files have NetCDF format.
	374	Informations about the file content (kind of quantities, array
	375	dimensions and grid coordinates) are part of the self describing NetCDF
	376	format and can be extracted from the NetCDF files using the command
[48]	377	"ncdump -c <filename>". See chapter <a href="chapter_4.5.1.html">4.5.1</a> about processing
	378	the PALM NetCDF data.<br><br>The following quantities are
[72]	379	available for output by default (quantity names ending with '*' are only allowed for the output of horizontal cross sections):<br><br><table style="text-align: left; width: 576px; height: 481px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="width: 106px;"><span style="font-weight: bold;">quantity
[48]	380	name</span></td><td style="width: 196px;"><span style="font-weight: bold;">meaning</span></td><td><span style="font-weight: bold;">unit</span></td><td><span style="font-weight: bold;">remarks</span></td></tr><tr><td style="width: 106px;"><span style="font-style: italic;">e</span></td><td style="width: 196px;">SGS TKE</td><td>m<sup>2</sup>/s<sup>2</sup></td><td></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">lwp*</span></td><td style="width: 196px; vertical-align: top;">liquid water path</td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">only horizontal cross section
	381	is allowed, requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
	382	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">p</span></td><td style="width: 196px; vertical-align: top;">perturpation
	383	pressure</td><td style="vertical-align: top;">N/m<sup>2</sup>,
	384	Pa</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pc</span></td><td style="width: 196px; vertical-align: top;">particle/droplet
	385	concentration</td><td style="vertical-align: top;">#/gridbox</td><td style="vertical-align: top;">requires that particle
	386	advection is switched on by <span style="font-weight: bold;">mrun</span>-option
	387	"-p particles"</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pr</span></td><td style="width: 196px; vertical-align: top;">mean
	388	particle/droplet radius </td><td style="vertical-align: top;">m</td><td style="vertical-align: top;">requires that particle
	389	advection is switched on by <span style="font-weight: bold;">mrun</span>-option
[72]	390	"-p particles"</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">pra*</span></td><td style="vertical-align: top;">precipitation amount</td><td style="vertical-align: top;">mm</td><td style="vertical-align: top;">only horizontal cross section
	391	is allowed, requires <a href="chapter_4.1.html#precipitation">precipitation</a>
	392	= <span style="font-style: italic;">.TRUE., </span>time interval on which amount refers to is defined by <a href="#precipitation_amount_interval">precipitation_amount_interval</a></td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">prr*</span></td><td style="vertical-align: top;">precipitation rate</td><td style="vertical-align: top;">mm/s</td><td style="vertical-align: top;">only horizontal cross section
	393	is allowed, requires <a href="chapter_4.1.html#precipitation">precipitation</a>
	394	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">pt</span></td><td style="width: 196px; vertical-align: top;">potential
[48]	395	temperature<br></td><td style="vertical-align: top;">K</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">q</span></td><td style="width: 196px; vertical-align: top;">specific humidity
[75]	396	(or total water content, if cloud physics is switched on)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql</span></td><td style="width: 196px; vertical-align: top;">liquid water
[48]	397	content</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
	398	= <span style="font-style: italic;">.TRUE.</span>
	399	or <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
	400	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_c</span></td><td style="width: 196px; vertical-align: top;">change in liquid
	401	water content due to condensation/evaporation during last timestep</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
	402	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_v</span></td><td style="width: 196px; vertical-align: top;">volume of liquid
	403	water</td><td style="vertical-align: top;">m<sup>3</sup>/gridbox</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
	404	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">ql_vp</span></td><td style="width: 196px; vertical-align: top;">weighting factor</td><td style="vertical-align: top;"></td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>
	405	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">qv</span></td><td style="width: 196px; vertical-align: top;">water vapor
	406	content (specific humidity)</td><td style="vertical-align: top;">kg/kg</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#cloud_physics">cloud_physics</a>
[97]	407	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic;">rho</span></td><td align="undefined" valign="undefined">potential density</td><td align="undefined" valign="undefined">kg/m<sup>3</sup></td><td align="undefined" valign="undefined">requires <a href="chapter_4.1.html#ocean">ocean</a>
[48]	408	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">s</span></td><td style="width: 196px; vertical-align: top;">concentration of
	409	the scalar</td><td style="vertical-align: top;">1/m<sup>3</sup></td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#passive_scalar">passive_scalar</a>
[97]	410	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic;">sa</span></td><td align="undefined" valign="undefined">salinity</td><td align="undefined" valign="undefined">psu</td><td align="undefined" valign="undefined">requires <a href="chapter_4.1.html#ocean">ocean</a>
[48]	411	= <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">t*</span></td><td style="width: 196px; vertical-align: top;">(near surface)
	412	characteristic temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">only horizontal cross section
	413	is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u</span></td><td style="width: 196px; vertical-align: top;">u-component of
	414	the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">u*</span></td><td style="width: 196px; vertical-align: top;">(near surface)
	415	friction velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;">only horizontal cross section
	416	is allowed</td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">v</span></td><td style="width: 196px; vertical-align: top;">v-component of
	417	the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">vpt</span></td><td style="width: 196px; vertical-align: top;">virtual potential
[75]	418	temperature</td><td style="vertical-align: top;">K</td><td style="vertical-align: top;">requires <a href="chapter_4.1.html#humidity">humidity</a> = <span style="font-style: italic;">.TRUE.</span></td></tr><tr><td style="width: 106px; vertical-align: top;"><span style="font-style: italic;">w</span></td><td style="width: 196px; vertical-align: top;">w-component of
[72]	419	the velocity</td><td style="vertical-align: top;">m/s</td><td style="vertical-align: top;"></td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">z0*</span></td><td style="vertical-align: top;">roughness length</td><td style="vertical-align: top;">m</td><td></td></tr></tbody></table><br>Multiple
[48]	420	quantities can be assigned, e.g. <span style="font-weight: bold;">data_output</span>
	421	= <span style="font-style: italic;">'e'</span>, <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'w'</span>.<br><br>By
[5]	422	assigning the pure strings from the above table, 3d volume data is
[48]	423	output. Cross section data can be output by appending the string <span style="font-style: italic;">'_xy'</span>, <span style="font-style: italic;">'_xz'</span>, or <span style="font-style: italic;">'_yz'</span> to the
	424	respective quantities. Time averaged output is created by
	425	appending the string <span style="font-style: italic;">'_av'
	426	</span>(for
[5]	427	cross section data, this string must be appended after the cross
	428	section string). Cross section data can also be (additionally) averaged
	429	along the direction normal to the respective section (see below).
	430	Assignments of quantities can be given in arbitrary
	431	order:<br><br>Example:<br><br><div style="margin-left: 40px;"><span style="font-weight: bold;">data_output</span> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'pt_xz_av'</span>, <span style="font-style: italic;">'w_xy'</span>, <span style="font-style: italic;">'u_av'</span>.<br></div><br>This
	432	example will create the following output: instantaneous 3d volume data
	433	of u-velocity component (by default on file DATA_3D_NETCDF), temporally
	434	averaged 3d volume data of u-velocity component (by default on file
	435	DATA_3D_AV_NETCDF), instantaneous horizontal cross section data of
	436	w-velocity component (by default on file DATA_2D_XY_NETCDF), and
	437	temporally averaged vertical cross section data of potential
[48]	438	temperature (by default on file DATA_2D_XZ_AV_NETCDF).<br><br>The
	439	user is allowed to extend the above list of quantities by defining his
	440	own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>).<br><br>The
	441	time interval of the output times is determined via <a href="#dt_data_output">dt_data_output</a>.
[5]	442	This is valid for all types of output quantities by default. Individual
[48]	443	time intervals for instantaneous  (!) 3d and section data can
	444	be
	445	declared using <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="#dt_do2d_xz">dt_do2d_xz</a>, and <a href="#dt_do2d_yz">dt_do2d_yz</a>.<br><br>Also,
	446	an individual time interval for output of temporally averaged data can
	447	be assigned using parameter <a href="#dt_data_output_av">dt_data_output_av</a>.
	448	This applies to both 3d volume and cross section data. The length of
	449	the averaging interval is controlled via parameter <a href="#averaging_interval">averaging_interval</a>.<br><br>The
	450	parameter <a href="#skip_time_data_output">skip_time_data_output</a>
	451	can be used to shift data output activities for a given time interval.
	452	Individual intervals can be set using <a href="#skip_time_do3d">skip_time_do3d</a>,
	453	<a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><p>With
	454	the parameter <a href="chapter_4.2.html#nz_do3d">nz_do3d</a>
[5]	455	the output can be limited in the vertical direction up to a certain
[48]	456	grid point.<br> </p> Cross sections extend through the
	457	total model
	458	domain. In the two horizontal directions all grid points with 0
	459	<= i
[5]	460	<= nx+1 and 0 <= j
[48]	461	<= ny+1 are output so that in case of cyclic boundary conditions
	462	the
	463	complete total domain is represented. The location(s) of the cross
	464	sections can be defined with parameters <a href="#section_xy">section_xy</a>,
	465	<a href="#section_xz">section_xz</a>, and <a href="#section_yz">section_yz</a>. Assigning <span style="font-weight: bold;">section_..</span> = <span style="font-style: italic;">-1</span>
	466	causes the output data to be averaged along the direction
	467	normal to the respective section.<br><br><br><span style="font-weight: bold;">Output of user defined quantities:</span><br><br>Beside
[5]	468	the standard quantities from the above list, the user can output any
	469	other quantities. These have to be defined and calculated within the
[48]	470	user-defined code (see <a href="chapter_3.5.4.html">3.5.4</a>).
	471	They can be selected for output with the user-parameter <a href="chapter_4.3.html#data_output_user">data_output_user</a>
	472	for which the same rules apply as for <span style="font-weight: bold;">data_output</span>.
[5]	473	Output of the user defined quantities (time interval, averaging,
	474	selection of cross sections, etc.) is controlled with the parameters
	475	listed above and data are written to the same file(s) as the standard
[48]	476	quantities.<br><br><p style="font-weight: bold;">Output
	477	on parallel machines:</p><p>
[5]	478	By default, with parallel runs, processors output only data
	479	of their respective subdomains into seperate local files (file names
	480	are
	481	constructed by appending the four digit processor ID, e.g.
[48]	482	<filename>_0000, <filename>_0001, etc.).
	483	After PALM has
[5]	484	finished, the contents of these individual
[48]	485	files are sampled into one final file<span style="font-weight: bold;"></span>
	486	using the program <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
[5]	487	(to be started e.g. by a suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
[48]	488	configuration file).</p> <p>Alternatively, PALM is able to
	489	collect all grid points of a
	490	cross section on PE0 before output is done. In this case only
	491	one
[5]	492	output file (DATA_2D_XY_NETCDF, etc.) is created and <tt><font style="font-size: 11pt;" size="2">combine_plot_fields.x</font></tt>
[48]	493	does not have to be called. In case of very large numbers of horizontal
	494	gridpoints, sufficient
	495	memory is required on PE0.  This method can be used by
	496	assigning <a href="chapter_4.2.html#data_output_2d_on_each_pe">data_output_2d_on_each_pe</a>
	497	= <i>.F.</i>.</p><p>3d volume data output is
	498	always handled seperately by each processor so that <span style="font-family: monospace;">combine_plot_fields.x</span>
	499	has to be called anyway after PALM has been finished.</p><p><br><span style="font-weight: bold;">Old formats:</span></p>
	500	<p>Beside
	501	the NetCDF format, 2d cross section data and 3d volume data
	502	can
[5]	503	also be output, for historical reasons, in a different (binary) format
[48]	504	using parameter <a href="#data_output_format">data_output_format</a>.</p><p>By
	505	assigning <span style="font-weight: bold;">data_output_format
	506	</span>= <span style="font-style: italic;">'avs'</span>,
	507	the 3d volume data is output to the local file <a href="chapter_3.4.html#PLOT3D_DATA">PLOT3D_DATA</a>.
[5]	508	Output is in FORTRAN binary format readable by
	509	the plot software <span style="font-weight: bold;">AVS</span>.
	510	The order of data on the file follows the order used in the assignment
[48]	511	for <b>data_output</b> (e.g. <b>data_output</b>
	512	= <span style="font-style: italic;">'p'</span>, <span style="font-style: italic;">'v'</span>,...
[5]	513	means that the file starts with the pressure data, followed by the
	514	v-component of the velocity, etc.). Both instantaneous and time
	515	averaged data are written on this file! Additional to this file, PALM
	516	creates
	517	a second binary file (local name <a href="chapter_3.4.html#PLOT3D_COOR">PLOT3D_COOR</a>)
	518	with coordinate information needed by <span style="font-weight: bold;">AVS</span>.
	519	As third and
	520	fourth file two ASCII files are created (AVS-FLD-format, local name <a href="chapter_3.4.html#PLOT3D_FLD">PLOT3D_FLD</a>
	521	and <a href="chapter_3.4.html#PLOT3D_FLD_COOR">PLOT3D_FLD_COOR</a>),
	522	which describe the contents of the data file and/or coordinate file
	523	and are used by AVS. However, AVS expects the content description in
	524	one file. This needs the local file PLOT3D_FLD_COOR to be appended to
	525	the file
	526	PLOT3D_FLD (by suitable OUTPUT command in the <span style="font-weight: bold;">mrun</span>
	527	configuration file: “<span style="font-family: monospace;">cat
[48]	528	PLOT3D_FLD_COOR >> PLOT3D_FLD</span>”)
	529	after PALM has
	530	finished. To reduce the amount of data, output to this file
	531	can be done
[5]	532	in
[48]	533	compressed form (see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>).
	534	Further details about plotting 3d volume data with <span style="font-weight: bold;">AVS </span>can be found in
	535	<a href="chapter_4.5.5.html">chapter
	536	4.5.5</a>.</p>By assigning <span style="font-weight: bold;">data_output_format </span>=
	537	<span style="font-style: italic;">'iso2d'</span>,
	538	the cross section data is output to the local files <a href="chapter_3.4.html#PLOT2D_XY">PLOT2D_XY</a>, <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>, and <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
[5]	539	Output is in FORTRAN binary format readable by
	540	the plot software <span style="font-weight: bold;">iso2d</span>.
	541	The order of data on the files follows the order used in the assignment
[48]	542	for <b>data_output</b> (e.g. <b>data_output</b>
	543	= <span style="font-style: italic;">'p_xy'</span>, <span style="font-style: italic;">'v_xy_av'</span>,...
[5]	544	means that the file containing the horizontal cross section data starts
	545	with the instantaneous pressure data, followed by the
	546	temporally averaged v-component of the velocity, etc.). Both
	547	instantaneous and time averaged data are written on this
	548	file!Additional to these binary files, PALM
	549	creates NAMELIST parameter files
	550	(local names <a href="chapter_3.4.html#PLOT2D_XY_GLOBAL">PLOT2D_XY_GLOBAL</a>,
[48]	551	<a href="chapter_3.4.html#PLOT2D_XY_LOCAL">PLOT2D_XY_LOCAL</a>,
	552	<a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>,
	553	<a href="chapter_3.4.html#PLOT2D_XZ_LOCAL">PLOT2D_XZ_LOCAL</a>,
	554	<a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>,
	555	<a href="chapter_3.4.html#PLOT2D_YZ_LOCAL">PLOT2D_YZ_LOCAL</a>)
[5]	556	which can be used as parameter input files for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html">iso2d</a>.
	557	That needs local files with suffix _LOCAL to be appended to the
	558	respective files with suffix _GLOBAL (by
	559	suitable OUTPUT commands in the <span style="font-weight: bold;">mrun</span>
	560	configuration file, e.g.: “<span style="font-family: monospace;">cat
[48]	561	PLOT2D_XY_LOCAL >> PLOT2D_XY_GLOBAL</span>”)
	562	after PALM has
	563	finished. Cross sections can be directly plotted with <span style="font-weight: bold;">iso2d</span> using the
	564	respective data and
[5]	565	parameter file. The plot layout is steered via the parameter input
	566	file.
	567	The values of these <span style="font-weight: bold;">iso2d</span>
	568	parameters are determined by a set of mostly internal PALM parameters
	569	(exception: <a href="chapter_4.2.html#z_max_do2d">z_max_do2d</a>).
	570	All parameter values can be changed by editing the parameter input
[48]	571	file. Further details about plotting 2d cross sections with <span style="font-weight: bold;">iso2d </span>can be found
	572	in <a href="chapter_4.5.4.html">chapter
	573	4.5.4</a>.<br><br><span style="font-weight: bold;">Important:</span><br>There
	574	is no guarantee that iso2d- and avs-output will be available in future
	575	PALM versions (later than 3.0). </td> </tr> <tr> <td style="vertical-align: top;"><a name="data_output_format"></a><span style="font-weight: bold;">data_output_format</span><br>
	576	</td> <td style="vertical-align: top;">C * 10 (10) </td>
	577	<td style="vertical-align: top;"><span style="font-style: italic;">'netcdf'</span> </td>
	578	<td style="vertical-align: top;">Format of output data.<br><br>By
	579	default, all data (profiles, time
[5]	580	series, spectra, particle data, cross sections, volume data) are output
[48]	581	in NetCDF format (see chapter <a href="chapter_4.5.1.html">4.5.1</a>).
	582	Exception: restart data (local files <a href="chapter_3.4.html#BININ">BININ</a>, <a href="chapter_3.4.html#BINOUT">BINOUT</a>, <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
	583	<a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a>)
	584	are always output in FORTRAN binary format.<br><br>The
	585	numerical precision of the NetCDF output is determined with parameter <a href="#chapter_4.1.html#netcdf_precision">netcdf_precision</a>.<br><br>The
	586	maximum file size for NetCDF files is 2 GByte by default. Use the
	587	parameter <a href="#netcdf_64bit">netcdf_64bit</a>
	588	if larger files have to be created.<br><br>For historical
	589	reasons, other data formats are still available. Beside 'netcdf', <span style="font-weight: bold;">data_output_format</span>
	590	may be assigned the following values:<br><br><table style="text-align: left; width: 594px; height: 104px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td style="vertical-align: top;"><span style="font-style: italic;">'profil'</span></td><td>output
	591	of profiles, time series and spectra in ASCII format to be
	592	read by the graphic software <span style="font-weight: bold;">profil
	593	</span>(see chapters <a href="chapter_4.5.2.html">4.5.2</a>,
	594	<a href="#chapter_4.5.3.html">4.5.3</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'iso2d'</span></td><td>output
	595	of 2d cross-sections in FORTRAN binary format to be read by the graphic
	596	software <span style="font-weight: bold;">iso2d</span>
	597	(see chapter <a href="chapter_4.5.4.html">4.5.4</a>)</td></tr><tr><td style="vertical-align: top;"><span style="font-style: italic;">'avs'</span></td><td>output
	598	of 3d volume data in FORTRAN binary format to be read by the graphic
	599	software <span style="font-weight: bold;">AVS</span>
	600	(see chapter <a href="chapter_4.5.5.html">4.5.5</a>)</td></tr></tbody></table><br>Multiple
	601	values can be assigned to <span style="font-weight: bold;">data_output_format</span>,
	602	i.e. if the user wants to have both the "old" data format suitable for <span style="font-weight: bold;">iso2d</span> as well as
	603	cross section data in NetCDF format, then <span style="font-weight: bold;">data_output_format</span> =
	604	<span style="font-style: italic;">'iso2d'</span>, <span style="font-style: italic;">'netcdf'</span> has to be
	605	assigned.<br><br><span style="font-weight: bold;">Warning:</span>
	606	There is no guarantee that the "old" formats will be available in
	607	future PALM versions (beyond 3.0)!<br> </td> </tr> <tr>
	608	<td style="vertical-align: top;"> <p><a name="data_output_pr"></a><b>data_output_pr</b></p>
	609	</td> <td style="vertical-align: top;">C *
	610	10  <br>
	611	(100)</td> <td style="vertical-align: top;"><i>100
	612	* ' '</i></td> <td style="vertical-align: top;">
	613	<p>Quantities for which vertical profiles (horizontally averaged)
	614	are to be output.  </p> <p>By default vertical
	615	profile data is output to the local file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>.
	616	The file's format is NetCDF.  Further details about processing
	617	NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>For
	618	historical reasons, data can also be output in ASCII-format on local
	619	file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>
	620	which is readable by the graphic software <span style="font-weight: bold;">profil</span>. See
	621	parameter <a href="#data_output_format">data_output_format</a>
	622	for defining the format in which data shall be output.<br> </p>
	623	<p>For horizontally averaged vertical
	624	profiles always <span style="font-weight: bold;">all</span>
	625	vertical
[5]	626	grid points (0 <= k <= nz+1) are output to file. Vertical
	627	profile data refers to the total domain but profiles for subdomains can
	628	also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
[48]	629	</p> <p>The temporal interval of the output times of
	630	profiles is
[5]	631	assigned via the parameter <a href="chapter_4.2.html#dt_dopr">dt_dopr</a>.
[48]	632	Within the file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>,
	633	the profiles are ordered with respect to their
	634	output times.</p><p>Profiles can also be temporally
	635	averaged (see <a href="chapter_4.2.html#averaging_interval_pr">averaging_interval_pr</a>). <br>
	636	</p> <p>The following list shows the values which can be
	637	assigned to <span style="font-weight: bold;">data_output_pr</span>.
[5]	638	The profile data is either defined on
[48]	639	u-v-levels (variables marked in <font color="#ff6600">red</font>)
	640	or
	641	on w-levels (<font color="#33ff33">green</font>).
	642	According to this,
[5]	643	the
	644	z-coordinates of the individual profiles vary. Beyond that, with a
	645	Prandtl layer switched on (<a href="chapter_4.1.html#prandtl_layer">prandtl_layer</a>)
	646	the lowest output
[48]	647	level is z = zu(1) instead of z = zw(0) for profiles <i>w''
	648	u'',w''v"</i>, <i>wu</i> and <i>wv</i>
	649	.  <br> </p> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u</i></font></td>
	650	<td style="vertical-align: top;">u-component of the
	651	velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v</i></font></td>
	652	<td style="vertical-align: top;">v-component of the
	653	velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w</i></font></td>
	654	<td style="vertical-align: top;">w-component of the
	655	velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt</i></font></td>
	656	<td style="vertical-align: top;">Potential temperature (in
	657	K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>vpt</i></font></td>
	658	<td style="vertical-align: top;">Virtual potential
	659	temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>lpt</i></font></td>
	660	<td style="vertical-align: top;">Potential liquid water
	661	temperature (in K).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>q</i></font></td>
	662	<td style="vertical-align: top;">Total water content
	663	(in kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>qv</i></font></td>
	664	<td style="vertical-align: top;">Specific humidity (in
	665	kg/kg).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>ql</i></font></td>
	666	<td style="vertical-align: top;">Liquid water content
[97]	667	(in kg/kg).</td> </tr> <tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(255, 102, 0);">rho</span></td><td align="undefined" valign="undefined">Potential density (in kg/m<sup>3</sup>).</td></tr><tr> <td style="vertical-align: middle; font-style: italic;"><font color="#ff6600">s</font></td>
[48]	668	<td style="vertical-align: top;">Scalar concentration (in
[97]	669	kg/m<sup>3</sup>).</td> </tr> <tr><td align="undefined" valign="undefined"><span style="font-style: italic; background-color: rgb(255, 255, 255); color: rgb(255, 102, 0);">sa</span></td><td align="undefined" valign="undefined">Salinity (in psu).</td></tr><tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e</i></font></td>
[48]	670	<td style="vertical-align: top;">Turbulent kinetic energy
[5]	671	(TKE, subgrid-scale) (in m<sup>2</sup>/s<sup>2</sup>).</td>
[48]	672	</tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>e*</i></font></td>
	673	<td style="vertical-align: top;">Perturbation energy
[5]	674	(resolved) (in m<sup>2</sup>/s<sup>2</sup>).</td>
[48]	675	</tr> <tr> <td style="vertical-align: middle;"><font color="#ff6600"><i>km</i></font></td>
	676	<td style="vertical-align: top;">Eddy diffusivity for
	677	momentum (in m<sup>2</sup>/s).</td> </tr> <tr>
	678	<td style="vertical-align: middle;"><font color="#ff6600"><i>kh</i></font></td>
	679	<td style="vertical-align: top;">Eddy diffusivity for heat
	680	(in m<sup>2</sup>/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>l</i></font></td>
	681	<td style="vertical-align: top;">Mixing length (in m).</td>
	682	</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"u"</i></font></td>
	683	<td style="vertical-align: top;">u-component of the
[5]	684	subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[48]	685	</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
	686	<td style="vertical-align: top;">u-component of the
[5]	687	resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[48]	688	</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wu</i></font></td>
	689	<td style="vertical-align: top;">u-component of the total
	690	vertical momentum flux (<i>w"u"</i> + <i>wu</i>)
	691	(in m<sup>2</sup>/s<sup>2</sup>).</td> </tr>
	692	<tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>w"v"</i></font></td>
	693	<td style="vertical-align: top;">v-component of the
[5]	694	subgrid-scale vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[48]	695	</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
	696	<td style="vertical-align: top;">v-component of the
[5]	697	resolved vertical momentum flux (in m<sup>2</sup>/s<sup>2</sup>).</td>
[48]	698	</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>wv</i></font></td>
	699	<td style="vertical-align: top;">v-component of the total
	700	vertical momentum flux (<i>w"v"</i> + <i>wv</i>)
	701	(in m<sup>2</sup>/s<sup>2</sup>).</td> </tr>
	702	<tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"pt"</i></font></td>
	703	<td style="vertical-align: top;">Subgrid-scale vertical
	704	sensible heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
	705	<td style="vertical-align: top;">Resolved vertical
	706	sensible
	707	heat flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
	708	<td style="vertical-align: top;">Total vertical sensible
[5]	709	heat flux (<i>w"pt"</i> + <i>wpt</i>)
	710	(in K
[48]	711	m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
	712	<td style="vertical-align: top;">Subgrid-scale vertical
[5]	713	sensible heat flux using the
[48]	714	Bott-Chlond scheme (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wptBC</i></font></td>
	715	<td style="vertical-align: top;">Total vertical sensible
[5]	716	heat flux using the Bott-Chlond scheme
	717	(<i>w"pt"</i>
[48]	718	+ <i>wptBC</i>) (in K m/s).</td> </tr> <tr>
	719	<td style="vertical-align: top;"><font color="#33ff33"><i>w"vpt"</i></font></td>
	720	<td style="vertical-align: top;">Subgrid-scale vertical
	721	buoyancy flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt</i></font></td>
	722	<td style="vertical-align: top;">Resolved vertical
	723	buoyancy
	724	flux (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wvpt</i></font></td>
	725	<td style="vertical-align: top;">Total vertical buoyancy
	726	flux (w"vpt" + wvpt) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"q"</i></font></td>
	727	<td style="vertical-align: top;">Subgrid-scale vertical
	728	water flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
	729	<td style="vertical-align: top;">Resolved vertical water
	730	flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wq</i></font></td>
	731	<td style="vertical-align: top;">Total vertical water flux
	732	(w"q" + wq) (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w"qv"</i></font></td>
	733	<td style="vertical-align: top;">Subgrid-scale vertical
	734	latent heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
	735	<td style="vertical-align: top;">Resolved vertical latent
	736	heat flux (in kg/kg m/s).</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wqv</i></font></td>
	737	<td style="vertical-align: top;">Total vertical latent
	738	heat
	739	flux (w"qv" + wqv) (in kg/kg m/s).</td> </tr> <tr>
	740	<td style="vertical-align: middle;"><font color="#33ff33"><i>w"s"</i></font></td>
	741	<td style="vertical-align: top;">Subgrid-scale vertical
[5]	742	scalar concentration flux (in kg/m<sup>3 </sup>m/s).</td>
[48]	743	</tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
	744	<td style="vertical-align: top;">Resolved vertical scalar
[97]	745	concentration flux (in kg/m<sup>3</sup> m/s).</td> </tr>
[48]	746	<tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>ws</i></font></td>
	747	<td style="vertical-align: top;">Total vertical scalar
[5]	748	concentration flux (w"s" + ws) (in kg/m<sup>3 </sup>m/s).</td>
[97]	749	</tr> <tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">w"sa"</span></td><td align="undefined" valign="undefined">Subgrid-scale vertical
	750	salinity flux (in psu<sup> </sup>m/s).</td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td><td align="undefined" valign="undefined">Resolved vertical salinity flux (in psu m/s).</td></tr><tr><td align="undefined" valign="undefined"><span style="font-style: italic; color: rgb(51, 255, 51);">wsa</span></td><td align="undefined" valign="undefined">Total vertical salinity flux (w"sa" + wsa) (in psu<sup> </sup>m/s).</td></tr><tr> <td style="vertical-align: top;"><font color="#33ff33"><i>we</i></font></td>
[48]	751	<td style="vertical-align: top;">Vertical flux of
	752	perturbation energy (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>u*2</i></font></td>
	753	<td style="vertical-align: top;">Variance of the
	754	u-velocity
	755	component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>v*2</i></font></td>
	756	<td style="vertical-align: top;">Variance of the
	757	v-velocity
	758	component (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*2</i></font></td>
	759	<td style="vertical-align: top;">Variance of the potential
	760	temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6600"><i>pt*2</i></font></td>
	761	<td style="vertical-align: top;">Variance of the potential
	762	temperature (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w*3</i></font></td>
	763	<td style="vertical-align: top;">Third moment of the
	764	w-velocity component (resolved)</td> </tr> <tr> <td style="vertical-align: middle;"><font color="#33ff33"><i>Sw</i></font></td>
	765	<td style="vertical-align: top;">Skewness of the
	766	w-velocity
[5]	767	component (resolved, S<sub>w</sub>
	768	= W<sup>3</sup>/(w<sup>2</sup>)<sup>1.5</sup>)</td>
[48]	769	</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>w2pt</i></font></td>
	770	<td style="vertical-align: top;">Third moment (resolved)</td>
	771	</tr> <tr> <td style="vertical-align: top;"><font color="#33ff33"><i>wpt2</i></font></td>
	772	<td style="vertical-align: top;">Third moment (resolved)</td>
	773	</tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>wuu*/dz</i></font></td>
	774	<td style="vertical-align: top;">Energy production by
	775	shear
	776	(resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>wp/dz</i></font></td>
	777	<td style="vertical-align: top;">Energy production by
[5]	778	turbulent transport of pressure
[48]	779	fluctuations (resolved)</td> </tr> <tr> <td style="vertical-align: top;"><font color="#ff6666"><i>w"e/dz</i></font></td>
	780	<td style="vertical-align: top;">Energy production by
	781	transport of resolved-scale TKE</td> </tr> </tbody>
[61]	782	</table> <br>Beyond that, initial profiles (t=0) of some
	783	variables can be also be
[5]	784	output (this output is only done once
	785	with the first plot output and not repeated with the profile output at
	786	later
	787	times). The names of these profiles result from the ones specified
[48]	788	above leaded by a hash "#".  Allowed values are:<br> <ul>
	789	<p><i>#u</i>, <i>#v</i>, <i>#pt</i>,
	790	<i>#km</i>, <i>#kh</i>, <i>#l</i></p>
	791	</ul> <p>These initial profiles have been either set by
	792	the user or
[89]	793	have been calculated by a 1d-model prerun.</p>The
	794	user is allowed to extend the above list of quantities by defining his
	795	own output quantities (see the user-parameter <a href="chapter_4.3.html#data_output_pr_user">data_output_pr_user</a>).<br><br>In case
[48]	796	of ASCII data output to local file PLOT1D_DATA,
[5]	797	PALM additionally creates a NAMELIST parameter file (local name <a href="chapter_3.4.html#PLOT1D_PAR">PLOT1D_PAR</a>)
	798	which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>.
	799	Profiles can be directly plotted with <span style="font-weight: bold;">profil</span>
	800	using these two files. The
	801	plot layout is
[48]	802	steered via the parameter input file. The values of these <span style="font-weight: bold;">profil</span>-parameters
	803	are determined by
[5]	804	a set of PALM parameters (<a href="chapter_4.2.html#profile_columns">profile_columns</a>,
[48]	805	<a href="chapter_4.2.html#profile_rows">profile_rows</a>,
	806	<a href="chapter_4.2.html#z_max_do1d">z_max_do1d</a>,
	807	<a href="chapter_4.2.html#cross_profiles">cross_profiles</a>,
[5]	808	etc.) All parameter values can be changed by editing the parameter
	809	input
[48]	810	file. <br><br>Further details about plotting vertical
	811	profiles with <span style="font-weight: bold;">profil </span>can
	812	be found in <a href="chapter_4.5.2.html">chapter
	813	4.5.2</a></td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="data_output_2d_on_each_pe"></a><b>data_output_2d_on</b>
	814	<br> <b>_each_pe</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">.T.</span><br> </td>
	815	<td style="vertical-align: top;">Output 2d cross section
	816	data by one or
	817	all processors.  <p>In runs with several processors, by
	818	default, each processor
	819	outputs cross section data of its subdomain into an individual
	820	file. After PALM
	821	has finished, the contents of these files have to be sampled into one
	822	file<span style="font-weight: bold;"></span> using
[5]	823	the program <tt>combine_plot_fields.x</tt>.  </p>
[48]	824	<p>Alternatively, by assigning <b>data_output_2d_on_each_pe</b>
	825	= <i>.F.,</i>
[5]	826	the respective data is gathered on PE0 and output is done directly
[48]	827	into one file, so <tt>combine_plot_fields.x</tt> does not
	828	have to be
	829	called. However, in case of very large numbers of horizontal
	830	gridpoints, sufficient
	831	memory is required on PE0. </p> </td> </tr>
	832	<tr> <td style="vertical-align: top;"> <p><a name="disturbance_amplitude"></a><b>disturbance<br>
	833	_amplitude</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.25</i></td>
	834	<td style="vertical-align: top;"> <p>Maximum
	835	perturbation amplitude of the random perturbations
[5]	836	imposed to the horizontal velocity field (in m/s).  </p>
[48]	837	<p>The parameter <a href="#create_disturbances">create_disturbances</a>
[5]	838	describes how to impose random perturbations to the horizontal velocity
	839	field. Since the perturbation procedure includes two filter operations,
[48]	840	the amplitude assigned by <b>disturbance_amplitude</b> is
	841	only an
	842	approximate value of the real magnitude of the perturbation.</p> </td>
[61]	843	</tr> <tr> <td style="vertical-align: top;"><p><a name="disturbance_energy_limit"></a><b>disturbance_energy</b>
[48]	844	<br> <b>_limit</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.01</i></td>
	845	<td style="vertical-align: top;"> <p lang="en-GB">Upper
	846	limit value of the perturbation energy of
[5]	847	the velocity field used as a criterion for imposing random
[48]	848	perturbations (in m<sup>2</sup>/s<sup>2</sup>).
	849	</p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
	850	describes how to impose
[5]	851	random perturbations to the horizontal velocity field. The perturbation
	852	energy is defined as the volume average (over the total model domain)
	853	of the squares of the deviations of the velocity components from the
	854	mean flow (horizontal average). If the perturbation energy exceeds the
	855	assigned value, random perturbations to the fields of horizontal
	856	velocities are imposed no more. The value of this parameter usually
	857	must be determined by trial and error (it depends e.g. on the total
[48]	858	number of grid points).</span> </font> </p> </td>
[61]	859	</tr> <tr> <td style="vertical-align: top;"><p><a name="disturbance_level_b"></a><b>disturbance_level_b</b></p>
[48]	860	</td> <td style="vertical-align: top;">R</td>
[97]	861	<td style="vertical-align: top;"><i>zu(3) or<br>zu(nz*2/3)<br>see right</i></td>
[48]	862	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Lower
[5]	863	limit of the vertical range for which random perturbations are to be
[48]	864	imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).
	865	</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This
[97]	866	parameter must hold the condition zu(3) <= <b>disturbance_level_b</b>
	867	<= zu(</font></span><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span><span lang="en-GB"><font face="Thorndale, serif">.
[48]	868	Additionally, <b>disturbance_level_b</b>
	869	<= </font></span><a href="#disturbance_level_t"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_t</font></span></a>
	870	<span lang="en-GB"><font face="Thorndale, serif">must
[97]	871	also hold.</font></span></p><p><span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_b</span> = <span style="font-style: italic;">(nz * 2) / 3</span>.</span></span><a href="chapter_4.1.html#nz"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">The
[48]	872	parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
	873	describes how to impose
	874	random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
	875	</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="disturbance_level_t"></a><b>disturbance_level_t</b></p>
	876	</td> <td style="vertical-align: top;">R</td>
[97]	877	<td style="vertical-align: top;"><i>zu(nz/3) or<br>zu(nzt-3)<br>see right</i></td>
[48]	878	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Upper
[5]	879	limit of the vertical range for which random perturbations are to be
[48]	880	imposed on the horizontal wind field (</font></font>in <font face="Thorndale, serif"><font size="3">m).
	881	</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This
	882	parameter must hold the condition <b>disturbance_level_t</b>
	883	<= zu<i>(</i></font></span><i><a href="chapter_4.1.html#nz"><span lang="en-GB"><font face="Thorndale, serif">nz-1</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)</font></span></i><span lang="en-GB"><font face="Thorndale, serif">.
	884	Additionally, </font></span><a href="#disturbance_level_b"><span lang="en-GB"><font face="Thorndale, serif">disturbance_level_b</font></span></a>
	885	<span lang="en-GB"><font face="Thorndale, serif"><=
	886	<b>disturbance_level_t</b>
[97]	887	must also hold.</font></span></p><span lang="en-GB"><font face="Thorndale, serif">In case of ocean runs (see <a href="chapter_4.1.html#ocean">ocean</a>) </font></span><span lang="en-GB"><span style="font-family: Thorndale,serif;">the default value is <span style="font-weight: bold;">disturbance_level_t</span> = <span style="font-style: italic;">nzt - 3</span>.</span></span><p><span lang="en-GB"><font face="Thorndale, serif">The
[48]	888	parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
	889	describes how to impose
	890	random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
	891	</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do2d_at_begin"></a><b>do2d_at_begin</b></p>
	892	</td> <td style="vertical-align: top;">L<br> </td>
	893	<td style="vertical-align: top;">.F.<br> </td>
	894	<td style="vertical-align: top;"> <p>Output of 2d
	895	cross section data at the beginning of a run.  </p> <p>The
	896	temporal intervals of output times of 2d cross section data (see <a href="chapter_4.2.html#data_output">data_output</a>)
	897	are usually determined with parameters <a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_xy</a>, <a href="chapter_4.2.html#dt_do2d_xz">dt_do2d_xz</a>
[5]	898	and <a href="chapter_4.2.html#dt_do2d_yz">dt_do2d_yz</a>.
[48]	899	By assigning <b>do2d_at_begin</b> = <i>.T.</i>
	900	an additional output
[5]	901	will be made at the
	902	beginning of a run (thus at the time t = 0 or at the respective
[48]	903	starting times of restart runs).</p> </td> </tr> <tr>
	904	<td style="vertical-align: top;"> <p><a name="do3d_at_begin"></a><b>do3d_at_begin</b></p>
	905	</td> <td style="vertical-align: top;">L<br> </td>
	906	<td style="vertical-align: top;">.F.<br> </td>
	907	<td style="vertical-align: top;">Output of 3d volume data
	908	at the beginning
	909	of a run.<br><br>The temporal intervals of output times of
	910	3d volume data (see <a href="chapter_4.2.html#data_output">data_output</a>)
[5]	911	is usually determined with parameter <a href="chapter_4.2.html#dt_do3d">dt_do3d</a>.
[48]	912	By assigning <b>do3d_at_begin</b> = <i>.T.</i>
	913	an additional output
[5]	914	will be made at the
	915	beginning of a run (thus at the time t = 0 or at the respective
[48]	916	starting times of restart runs).</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_compress"></a><b>do3d_compress</b></p>
	917	</td> <td style="vertical-align: top;">L<br> </td>
	918	<td style="vertical-align: top;">.F.<br> </td>
	919	<td style="vertical-align: top;"> <p>Output of data
	920	for 3d plots in compressed form.  </p> <p>This
	921	parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	922	= <span style="font-style: italic;">'avs'</span>.</p><p>Output
	923	of 3d volume data may need huge amounts of disc storage
[5]	924	(up to several Terabytes ore more). Data compression can serve to
	925	reduce this requirement. PALM is able to output 3d data in compressed
	926	form using 32-bit integers, if <span style="font-weight: bold;">do3d_compress</span>
[48]	927	= <span style="font-style: italic;">.T.</span> is
	928	assigned. This
[5]	929	yields a loss of accuracy, but the file size is clearly reduced. The
	930	parameter <a href="chapter_4.2.html#do3d_precision">do3d_precision</a>
	931	can be used to separately define the number of significant digits for
[48]	932	each quantity.<br> </p> <p>So far compressed data
	933	output is only possible for Cray-T3E
[5]	934	machines. Additional information for
	935	handling compressed data is given in <a href="chapter_4.5.6.html">chapter
[48]	936	4.5.6</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="do3d_precision"></a><b>do3d_precision</b></p>
	937	</td> <td style="vertical-align: top;">C *
	938	7  <br>
	939	(100)</td> <td style="vertical-align: top;">see
	940	right<br> </td> <td style="vertical-align: top;">
	941	<p>Significant digits in case of compressed data
	942	output.  </p> <p>This parameter only applies for
	943	<a href="chapter_4.2.html#data_output_format">data_output_format</a>
	944	= <span style="font-style: italic;">'avs'</span>.</p><p>In
	945	case that data compression is used for output of 3d data
[5]	946	(see <a href="chapter_4.2.html#do3d_compress">do3d_compress</a>),
	947	this parameter determines the number of significant digits
[48]	948	which are to be output.<br> </p> <p>Fewer digits
	949	clearly reduce the amount
[5]	950	of data. Assignments have to be given separately for each individual
[48]	951	quantity via a character string of the form <span style="font-style: italic;">'<quantity
	952	name><number of
[5]	953	significant digits>'</span>, e.g. <span style="font-style: italic;">'pt2'</span>.
	954	Only those quantities listed in <a href="chapter_4.2.html#data_output">data_output</a>
	955	are admitted. Up to 9 significant digits are allowed (but large values
	956	are not very reasonable
[48]	957	because they do not effect a significant compression).<br> </p>
	958	<p>The default assignment is <span style="font-weight: bold;">do3d_precision</span>
	959	= <span style="font-style: italic;">'u2'</span>, <span style="font-style: italic;">'v2'</span>, <span style="font-style: italic;">'w2'</span>, <span style="font-style: italic;">'p5'</span>, <span style="font-style: italic;">'pt2'</span>.</p> </td>
[61]	960	</tr><tr> <td style="vertical-align: top;"> <p><a name="dt_laufparameter"></a><b>dt</b></p>
[48]	961	</td> <td style="vertical-align: top;">R</td>
	962	<td style="vertical-align: top;"><i>variable</i></td>
	963	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale, serif"><font size="3">Time
	964	step to be used by the 3d-model (</font></font>in <font face="Thorndale, serif"><font size="3">s).
	965	</font></font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">This parameter</font></span>
	966	<font face="Thorndale, serif"><span lang="en-GB">is
	967	described in
	968	detail with the initialization parameters (see</span></font><span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB">).
	969	Additionally, it may be
[5]	970	used as a run parameter and then applies to all restart runs (until it
	971	is changed again). A switch from a constant time step to a variable
[48]	972	time step can be achieved with <b>dt</b> = <i>-1.0</i>.</span>
	973	</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_averaging_input"></a><span style="font-weight: bold;">dt_averaging_input</span><br>
	974	</td> <td style="vertical-align: top;">R<br> </td>
	975	<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
	976	<td style="vertical-align: top;">Temporal interval
	977	of data which are subject to temporal averaging (in s).<br><br>By
	978	default, data from each timestep within the interval defined by <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>
	979	are used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input</span>
	980	> <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
[5]	981	the number of time levels entering the average can be minimized. This
	982	reduces the CPU-time of a run but may worsen the quality of the
[48]	983	average's statistics.<br><br><font face="Thorndale, serif"><span lang="en-GB">With
	984	variable time step (see <span style="font-weight: bold;">dt</span>),
	985	the number of time levels entering the average can vary from one
	986	averaging interval to the next (for a more detailed explanation see </span></font><font><a href="#averaging_interval"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval</font></span></a>)</font><font face="Thorndale, serif"><span lang="en-GB">. It
	987	is approximately given by the quotient of <span style="font-weight: bold;">averaging_interval</span> /
	988	MAX(<span style="font-weight: bold;"> dt_averaging_input</span>,
	989	<span style="font-weight: bold;">dt</span>) (which
	990	gives a more or less exact value if a fixed timestep is used and if
	991	this is an integral divisor of <span style="font-weight: bold;">dt_averaging_input</span>).</span></font>
	992	<br><br><span style="font-weight: bold;">Example:</span><br>With
	993	an averaging interval of 100.0 s and <span style="font-weight: bold;">dt_averaging_input</span> =
	994	<span style="font-style: italic;">10.0</span>,
[5]	995	the time levels entering the average have a (minimum) distance of 10.0
	996	s (their distance may of course be larger if the current timestep is
	997	larger than 10.0 s), so the average is calculated from the data of
[48]	998	(maximum) 10 time levels.<br><br><font face="Thorndale, serif"><span lang="en-GB">It
	999	is allowed
	1000	to change <b>dt_averaging_input</b> during a job chain. If
	1001	the last averaging
[5]	1002	interval of the run previous to the change could not be completed (i.e.
	1003	has to be finished in the current run), the individual profiles and/or
	1004	spectra entering the averaging are not uniformly distributed over the
[48]	1005	averaging interval.<br><br></span></font>Parameter <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a> can
	1006	be used to define a different temporal interval for
	1007	vertical profile data and spectra.<br> </td> </tr>
	1008	<tr> <td style="vertical-align: top;"> <p><a name="dt_averaging_input_pr"></a><b>dt_averaging_input_pr</b></p>
	1009	</td> <td style="vertical-align: top;">R</td>
	1010	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#dt_averaging_input">dt_<br>averaging_<br>input</a></span></td>
	1011	<td style="vertical-align: top;"> <p lang="en-GB">Temporal
	1012	interval of data which are subject to temporal averaging of <font face="Thorndale, serif"><font size="3">vertical
	1013	profiles and/or spectra (</font></font>in <font face="Thorndale, serif"><font size="3">s).
	1014	</font></font> </p> <p>By default, data from
	1015	each timestep within the interval defined by<font face="Thorndale, serif"><span lang="en-GB"> </span></font><a href="#averaging_interval_pr"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_pr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><span lang="en-GB"><font face="Thorndale, serif">and </font></span><a href="#averaging_interval_sp"><span lang="en-GB"><font face="Thorndale, serif">averaging_interval_sp</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> </font></span>are
	1016	used for calculating the temporal average. By choosing <span style="font-weight: bold;">dt_averaging_input_pr</span>
	1017	> <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale, serif">dt</font></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><span style="font-style: italic;"></span>,
[5]	1018	the number of time levels entering the average can be minimized. This
	1019	reduces the CPU-time of a run but may worsen the quality of the
[48]	1020	average's statistics. <span lang="en-GB"><font face="Thorndale, serif"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span></font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font><span lang="en-GB"></span><br> </p><p>For
	1021	more explanations see parameter <a href="#dt_averaging_input">dt_averaging_input</a>.<a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><font face="Thorndale, serif"><span lang="en-GB"></span></font></p></td>
[103]	1022	</tr> <tr><td style="vertical-align: top;"><a name="dt_coupling"></a><span style="font-weight: bold;">dt_coupling</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span></td><td style="vertical-align: top;">Temporal interval for the data exchange in case of runs with coupled models (e.g. atmosphere - ocean) (in s).<br><br>This parameter has an effect only in case of a run with coupled models.<br>It is available starting from version 3.3a. A more detailed explanation will be given soon.</td></tr><tr> <td style="vertical-align: top;"><a name="dt_data_output"></a><span style="font-weight: bold;">dt_data_output</span><br>
[48]	1023	</td> <td style="vertical-align: top;">R<br> </td>
	1024	<td style="vertical-align: top;"><span style="font-style: italic;">9999999.9</span><br>
	1025	</td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
	1026	at which data (3d volume data (instantaneous or time
	1027	averaged),
[5]	1028	cross sections (instantaneous or time averaged), vertical profiles,
	1029	spectra) shall be output (</font>in <font face="Thorndale">s). </font></p>
[48]	1030	<span lang="en-GB"><font face="Thorndale">If
	1031	data output is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">, <a href="#data_output_pr">data_output_pr</a>, <a href="#data_output_sp">data_output_sp</a>, and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
	1032	parameter can be used to
[5]	1033	assign the temporal interval at which these data shall be
[48]	1034	output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
	1035	simulation using parameter <a href="#skip_time_data_output">skip_time_data_output</a>,
	1036	which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
	1037	time is the beginning of the simulation, i.e. output
	1038	takes place at times t = <b>skip_time_data_output +
	1039	dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
	1040	+ 2*<b>dt_data_output</b>, <span style="font-weight: bold;">skip_time_data_output</span>
	1041	+ 3*<b>dt_data_output</b>,
[5]	1042	etc. Since output is only done at the discrete time levels given by
[48]	1043	the timestep used, the actual output times can slightly
	1044	deviate
	1045	from these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br>Individual temporal
	1046	intervals for the different output quantities can be assigned using
	1047	parameters <a href="#dt_do3d">dt_do3d</a>, <a href="#dt_do2d_xy">dt_do2d_xy</a>, <a href="dt_do2d_xz">dt_do2d_xz</a>, <a href="#dt_do2d_yz">dt_do2d_yz</a>, <a href="#dt_dopr">dt_dopr</a>, <a href="#dt_dosp">dt_dosp</a>,
	1048	and <a href="#dt_data_output_av">dt_data_output_av</a>.</font></span>
	1049	</td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_data_output_av"></a><span style="font-weight: bold;">dt_data_output_av</span><br>
	1050	</td> <td style="vertical-align: top;">R<br> </td>
	1051	<td style="vertical-align: top;"><i>value of
	1052	<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i>
	1053	</td> <td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal interval</font>
[5]	1054	at which time averaged 3d volume data and/or 2d cross section data
[48]	1055	shall be output (</font>in <font face="Thorndale">s). </font></p><span lang="en-GB"><font face="Thorndale">If data
	1056	output of time averaged 2d and 3d data is switched on (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a> <span lang="en-GB"><font face="Thorndale">and </font></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
	1057	parameter can be used to
[5]	1058	assign the temporal interval at which they shall be
[48]	1059	output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
	1060	simulation using parameter <a href="#skip_time_data_output_av">skip_time_data_output_av</a>,
	1061	which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
	1062	time is the beginning of the simulation, i.e. output
	1063	takes place at times t = <b>skip_time_data_output_av +
	1064	dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
	1065	+ 2*<b>dt_data_output_av</b>, <span style="font-weight: bold;">skip_time_data_output_av</span>
	1066	+ 3*<b>dt_data_output_av</b>,
[5]	1067	etc. Since output is only done at the discrete time levels given by
[48]	1068	the timestep used, the actual output times can slightly
	1069	deviate from
	1070	these theoretical values</font></span><a href="chapter_4.2.html#dt_dopr_zeitpunkte"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">.<br><br></font></span>The
	1071	length of the averaging interval is controlled via parameter <a href="chapter_4.2.html#averaging_interval">averaging_interval</a>.</td>
[61]	1072	</tr><tr> <td style="vertical-align: top;"> <p><a name="dt_disturb"></a><b>dt_disturb</b></p>
[48]	1073	</td> <td style="vertical-align: top;">R</td>
	1074	<td style="vertical-align: top;"><i>9999999.9</i></td>
	1075	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1076	interval</font> at which random
[5]	1077	perturbations are to be imposed on the horizontal velocity field
[48]	1078	(</font>in <font face="Thorndale">s).  </font>
	1079	</p> <p><span lang="en-GB"><font face="Thorndale, serif">The parameter </font></span><a href="#create_disturbances"><span lang="en-GB"><font face="Thorndale, serif">create_disturbances</font></span></a><font face="Thorndale, serif"><span lang="en-GB">
	1080	describes how to impose
	1081	random perturbations to the horizontal velocity field</span></font><font face="Thorndale, serif"><span lang="en-GB">.</span>
	1082	</font> </p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_dopr"></a><b>dt_dopr</b></p>
	1083	</td> <td style="vertical-align: top;">R</td>
	1084	<td style="vertical-align: top;"><i>value of
	1085	<a href="#dt_data_output">dt_data_<br>output</a></i></td>
	1086	<td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale">Temporal
	1087	interval at
[5]	1088	which data of vertical profiles shall be output (to local
[48]	1089	file <a href="chapter_3.4.html#DATA_1D_PR_NETCDF">DATA_1D_PR_NETCDF</a>
	1090	or/and </font></span><a href="chapter_3.4.html#PLOT1D_DATA"><span lang="en-GB"><font face="Thorndale">PLOT1D_DATA</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
	1091	<span lang="en-GB"><font face="Thorndale">s).
	1092	</font></span> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
	1093	horizontally averaged vertical profiles is switched on (see </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
	1094	parameter can be used to
	1095	assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> </font></span><span lang="en-GB"><font face="Thorndale">Output can
	1096	be skipped at the beginning of a simulation using parameter <a href="#skip_time_dopr">skip_time_dopr</a>, which has
	1097	zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
	1098	time is the beginning
[5]	1099	of the simulation, thus t = 0, </font></span><span lang="en-GB"><font face="Thorndale">i.e. output
[48]	1100	takes place at times t = <b>skip_time_dopr + dt_dopr</b>, <span style="font-weight: bold;">skip_time_dopr</span> + 2*<b>dt_dopr</b>,
	1101	<span style="font-weight: bold;">skip_time_dopr</span>
	1102	+ 3*<b>dt_dopr</b>,
[5]	1103	etc.</font></span><span lang="en-GB"><font face="Thorndale"> Since
	1104	profiles can not be calculated for times lying within a time step
	1105	interval, the output times can deviate from these theoretical values.
	1106	If a time step ranges from t = 1799.8 to t = 1800.2, then in the
	1107	example above the output would take place at t = 1800.2. In general,
[48]	1108	the output always lie between t = 1800.0 and t = 1800.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If the
	1109	model uses a variable time step, these
[5]	1110	deviations from the theoretical output times will of course be
[48]	1111	different for each output time.<br> </font></span></p>
	1112	<p><span lang="en-GB"><font face="Thorndale">In
	1113	order to
	1114	guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">,
	1115	<span style="font-weight: bold;">end_time</span>
[5]	1116	should be equal or a little bit
	1117	larger than the respective theoretical output time. For example, if <b>dt_dopr</b>
[48]	1118	= <i>900.0</i><span style="font-style: italic;">
	1119	</span>and 3600.0
[5]	1120	seconds are to be simulated, then <b>end_time</b>
[48]	1121	>= 3600.0 should be chosen.</font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span>  </font></span>
	1122	</p> <p><span lang="en-GB"><font face="Thorndale">A selection of
	1123	profiles to be output can be done via parameter </font></span><a href="chapter_4.2.html#data_output_pr"><span lang="en-GB"><font face="Thorndale">data_output_pr</font></span></a><span lang="en-GB"><font face="Thorndale">. </font></span>
	1124	</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="dt_dopr_listing"></a><span style="font-weight: bold;">dt_dopr_listing</span><br>
	1125	</td> <td style="vertical-align: top;">R<br> </td>
	1126	<td style="vertical-align: top;"><i>9999999.9</i></td>
	1127	<td style="vertical-align: top;"> <p><span lang="en-GB"><font face="Thorndale, serif">Temporal
	1128	interval</font> at which data <font face="Thorndale">of
	1129	vertical
	1130	profiles shall be output (output for printouts, local file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a><span lang="en-GB"><font face="Thorndale">) (</font></span>in
	1131	<span lang="en-GB"><font face="Thorndale">s). </font></span>
	1132	</p> <p>T<span lang="en-GB"></span><a href="chapter_4.2.html#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
[5]	1133	parameter can be used to
[48]	1134	assign the temporal interval at which profile data shall be output.</font></span><span lang="en-GB"><font face="Thorndale"> Reference
	1135	time is the beginning
	1136	of the simulation, thus t = 0. For example if <b>dt_dopr_listing</b>
	1137	= 1800.0,
[5]	1138	then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since
	1139	profiles can not be calculated for times lying within a time step
	1140	interval, the output times can deviate from these theoretical values.
	1141	If a time step ranges from t = 1799.8 to t = 1800.2, then in the
	1142	example above the output would take place at t = 1800.2. In general,
[48]	1143	the output always lie between t = 1800.0 and t = 1800.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a> <span lang="en-GB"><font face="Thorndale">(numbers
	1144	are related to
[5]	1145	the
	1146	example above). If the model uses a variable time step, these
	1147	deviations from the theoretical output times will of course be
[48]	1148	different for each output time.<br> </font></span></p>
	1149	<p><span lang="en-GB"><font face="Thorndale">In
	1150	order to
	1151	guarantee an output of profile data at the end of a simulation (see </font></span><font><a href="chapter_4.1.html#end_time"><span lang="en-GB"><font face="Thorndale">end_time</font></span></a></font><span lang="en-GB"><font face="Thorndale">) in any way</font></span><span lang="en-GB"><font face="Thorndale">,
	1152	<span style="font-weight: bold;">end_time</span>
[5]	1153	should be a little bit
	1154	larger than the respective theoretical output time. For example, if <b>dt_dopr_listing</b>
[48]	1155	= <i>900.0</i><span style="font-style: italic;">
	1156	</span>and 3600.0
[5]	1157	seconds are to be simulated, then it should be at least  <b>end_time</b>
[48]	1158	> 3600.0 + </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">. If
	1159	variable time steps are used
[5]	1160	(which is the default), <span style="font-weight: bold;">dt</span>
	1161	should be properly estimated.  </font></span> </p>
[48]	1162	<p><span lang="en-GB"><font face="Thorndale">Data
	1163	and output
	1164	format of the file </font></span><a href="chapter_3.4.html#LIST_PROFIL"><span lang="en-GB"><font face="Thorndale">LIST_PROFIL</font></span></a>
	1165	<span lang="en-GB"><font face="Thorndale">is
	1166	internally fixed. In this file
[5]	1167	the profiles of the most important model variables are arranged in
[48]	1168	adjacent columns.</font></span> </p> </td> </tr>
	1169	<tr> <td style="vertical-align: top;"> <p><a name="dt_dots"></a><b>dt_dots</b></p>
	1170	</td> <td style="vertical-align: top;">R</td>
	1171	<td style="vertical-align: top;"><span style="font-style: italic;">see right</span></td>
	1172	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1173	interval</font> at which time series data shall be
	1174	output (</font>in <font face="Thorndale">s). </font>
	1175	</p> <p>The default interval for the output of timeseries
	1176	is calculated as shown below (this tries to minimize the number of
	1177	calls of <span style="font-family: Courier New,Courier,monospace;">flow_statistics</span>)</p><p style="font-family: Courier New,Courier,monospace;">
	1178	IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
	1179	== 0.0 )  THEN<br>
	1180	<span style="font-weight: bold;">dt_dots</span> =
	1181	MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
	1182	ELSE<br>
	1183	<span style="font-weight: bold;">dt_dots</span> =
	1184	MIN( dt_run_control, <a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
	1185	)<br>
	1186	ENDIF</p><p>This parameter can be used to
	1187	assign the temporal interval at which data points shall be output. <span lang="en-GB"><font face="Thorndale">Reference
	1188	time is the beginning of
[5]	1189	the simulation, i.e. output takes place at times t = <b>dt_dots</b>,
[48]	1190	2<b>dt_dots</b>, 3<b>dt_dots</b>, etc. The
	1191	actual output times can
	1192	deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).
	1193	Is <b>dt_dots</b> < </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then data
	1194	of the time series are
[5]	1195	written after each time step (if this is requested it should be <b>dt_dots</b>
[48]	1196	= <i>0</i>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">The default
	1197	value of <span style="font-weight: bold;">dt_dots</span>
	1198	is calculated as follows:</font></span></p>
	1199	IF ( <a href="#averaging_interval_pr">averaging_interval_pr</a>
	1200	== 0.0 )  THEN<br>
	1201	<span style="font-weight: bold;">dt_dots</span> =
	1202	MIN( <a href="#dt_run_control">dt_run_control</a>, <a href="#dt_dopr">dt_dopr</a> )<br>
	1203	ELSE<br>
	1204	<span style="font-weight: bold;">dt_dots</span> =
	1205	MIN( <span style="font-weight: bold;">dt_run_control</span>,
	1206	<a href="#dt_averaging_input_pr">dt_averaging_input_pr</a>
	1207	)<br>
	1208	ENDIF<br><br>(which minimizes the number of calls of
	1209	routine flow_statistics).<br><p>By default time series data
	1210	is output to the local file <a href="chapter_3.4.html#DATA_1D_TS_NETCDF">DATA_1D_TS_NETCDF</a>.
	1211	Because of the default settings of <span style="font-weight: bold;">dt_dots</span>,
	1212	it will generally be created for each model run. The file's
	1213	format is NetCDF.  Further details about processing NetCDF
	1214	data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p>The
	1215	file contains the following timeseries quantities (the first column
	1216	gives the name of the quantities as used in the NetCDF file):<br><table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="font-style: italic; vertical-align: middle;">E<br>
	1217	</td> <td style="vertical-align: top;">Total
	1218	kinetic energy of
	1219	the flow (in m<sup>2</sup>/s<sup>2</sup>)
	1220	(normalized with respect to the total number of grid points).</td>
	1221	</tr> <tr> <td style="font-style: italic; vertical-align: middle;">E*<br>
	1222	</td> <td style="vertical-align: top;">Perturbation
	1223	kinetic
	1224	energy of the flow (in m<sup>2</sup>/s<sup>2</sup>)<sup>
	1225	</sup>(normalized
	1226	with respect to the total number of grid
	1227	points)</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">dt<br>
	1228	</td> <td style="vertical-align: top;">Time step
	1229	size (in s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">u<sub>*</sub></td>
	1230	<td style="vertical-align: top;">Friction velocity (in
	1231	m/s)
	1232	(horizontal average).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w<sub>*</sub></td>
	1233	<td style="vertical-align: top;">Vertical velocity scale
	1234	of
	1235	the CBL (in m/s) (horizontal average)</td> </tr> <tr>
	1236	<td style="vertical-align: top; font-style: italic;">th<sub>*</sub></td>
	1237	<td style="vertical-align: top;">Temperature
	1238	scale (Prandtl layer), defined as <i>w"pt"0
	1239	/ </i><i>u<sub>*</sub></i>
	1240	(horizontal
	1241	average) (in K).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">umax<br>
	1242	</td> <td style="vertical-align: top;">Maximum
	1243	u-component of the
	1244	velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">vmax<br>
	1245	</td> <td style="vertical-align: top;">Maximum
	1246	v-component of the
	1247	velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wmax<br>
	1248	</td> <td style="vertical-align: top;">Maximum
	1249	w-component of the
	1250	velocity (in m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_old<br>
	1251	</td> <td style="vertical-align: top;">Divergence
	1252	of the velocity
	1253	field before the pressure
	1254	solver has been called (normalized with respect to the total number of
	1255	grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">div_new</td>
	1256	<td style="vertical-align: top;">Divergence of the
	1257	velocity
	1258	field after the pressure
	1259	solver has been called (normalized with respect to the total number of
	1260	grid points) (in 1/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_wpt</td>
	1261	<td style="vertical-align: top;">Height of the convective
	1262	boundary layer (horizontal average)
	1263	determined by the height of the minimum sensible heat flux (in m).</td>
	1264	</tr> <tr> <td style="vertical-align: top; font-style: italic;">z_i_pt</td>
	1265	<td style="vertical-align: top;">Height of the convective
	1266	boundary layer (horizontal average)
	1267	determined by the temperature profile (in m).</td> </tr> <tr>
	1268	<td style="vertical-align: top; font-style: italic;">w"pt"0</td>
	1269	<td style="vertical-align: top;">Subgrid-scale sensible
	1270	heat flux near the surface (horizontal
	1271	average)
	1272	between z = 0 and z = z<sub>p</sub> = zu(1) (there it
	1273	corresponds to
	1274	the total heat flux) (in K m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">w"pt"</td>
	1275	<td style="vertical-align: top;">Subgrid-scale heat flux
	1276	(horizontal average) for z = zw(1) (in K
	1277	m/s).</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">wpt</td>
	1278	<td style="vertical-align: top;">Total heat flux
	1279	(horizontal average) for z = zw(1) (in K m/s).</td> </tr> <tr>
	1280	<td style="vertical-align: top; font-style: italic;">pt(0)</td>
	1281	<td style="vertical-align: top;">Potential temperature at
	1282	the surface (horizontal average) (in K).</td> </tr> <tr>
	1283	<td style="vertical-align: top; font-style: italic;">pt(zp)</td>
	1284	<td style="vertical-align: top;">Potential temperature for
	1285	z = zu(1) (horizontal average) (in K).</td> </tr> <tr>
	1286	<td style="vertical-align: top; font-style: italic;">splptx</td>
	1287	<td style="vertical-align: top;">Percentage of grid points
	1288	using upstream scheme along x with
	1289	upstream-spline advection switched on.</td> </tr> <tr>
	1290	<td style="vertical-align: top; font-style: italic;">splpty</td>
	1291	<td style="vertical-align: top;">Percentage of grid points
	1292	using upstream scheme along y with
	1293	upstream-spline
	1294	advection switched on.</td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">splptz</td>
	1295	<td style="vertical-align: top;">Percentage of grid points
	1296	using upstream scheme along z with
	1297	upstream-spline
	1298	advection switched on.<br> </td> </tr> <tr> <td style="vertical-align: top; font-style: italic;">L</td>
	1299	<td style="vertical-align: top;">Monin-Obukhov length.</td>
	1300	</tr> </tbody> </table><br>Additionally, the
	1301	user can add his own timeseries quantities to the file, by using the
	1302	user-interface subroutines<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_init">user_init</a> </span>and<span style="font-family: Courier New,Courier,monospace;"> <a href="chapter_3.5.1.html#user_statistics">user_statistics</a></span>.
	1303	These routines contain (as comment lines) a simple example how to do
	1304	this.<br><br>Time series data refers to the total
	1305	domain, but time series for subdomains can also be output (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>).
	1306	However, the following time series always present the values of the
	1307	total model domain (even with output for subdomains): <i>umax</i>,
	1308	<i>vmax</i>, <i>wmax</i>, <i>div_old</i>,
	1309	<i>div_new</i>.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xy"></a><b>dt_do2d_xy</b></p>
	1310	</td> <td style="vertical-align: top;">R</td>
	1311	<td style="vertical-align: top;"><i>value of
	1312	<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
	1313	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1314	interval</font> at which horizontal cross section data
	1315	shall be output (</font>in <font face="Thorndale">s).
	1316	</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
[5]	1317	horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
[48]	1318	<span lang="en-GB"><font face="Thorndale">and
	1319	</font></span><a href="#section_xy"><span lang="en-GB"><font face="Thorndale">section_xy</font></span></a><span lang="en-GB"><font face="Thorndale">), this
	1320	parameter can be used to
[5]	1321	assign the temporal interval at which cross section data shall be
[48]	1322	output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
	1323	simulation using parameter <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>,
	1324	which has zero value by default. </font></span><span lang="en-GB"><font face="Thorndale">Reference
	1325	time is the beginning of the simulation, i.e. output
	1326	takes place at times t = <b>skip_time_do2d_xy + dt_do2d_xy</b>,
	1327	<span style="font-weight: bold;">skip_time_do2d_xy</span>
	1328	+ 2*<b>dt_do2d_xy</b>, <span style="font-weight: bold;">skip_time_do2d_xy</span>
	1329	+ 3*<b>dt_do2d_xy</b>,
[5]	1330	etc. The actual output times can deviate from these theoretical values
	1331	(see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
[48]	1332	</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
	1333	has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
	1334	the time t = 0 or at the
[5]	1335	respective starting times of restart runs).</font></span> </p>
[48]	1336	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_xz"></a><b>dt_do2d_xz</b></p>
	1337	</td> <td style="vertical-align: top;">R</td>
	1338	<td style="vertical-align: top;"><i>value of
	1339	<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
	1340	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1341	interval</font> at which vertical cross sections data
	1342	(xz) shall be output (</font>in <font face="Thorndale">s).
	1343	</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
[5]	1344	horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
[48]	1345	<span lang="en-GB"><font face="Thorndale">and
	1346	</font></span><a href="#section_xz"><span lang="en-GB"><font face="Thorndale">section_xz</font></span></a><span lang="en-GB"><font face="Thorndale">),
[5]	1347	this parameter can be used to assign the temporal interval at which
[48]	1348	cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
	1349	be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, which
	1350	has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
	1351	the simulation, i.e. output takes place at times t = <b>skip_time_do2d_xz
	1352	+ dt_do2d_xz</b>,
	1353	<span style="font-weight: bold;">skip_time_do2d_xz</span>
	1354	+ 2*<b>dt_do2d_xz</b>, <span style="font-weight: bold;">skip_time_do2d_xz</span>
	1355	+ 3*<b>dt_do2d_xz</b>, etc. The actual output times
[5]	1356	can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
[48]	1357	</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
	1358	has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
	1359	the time t = 0 or at the
[5]	1360	respective starting times of restart runs).</font></span> </p>
[48]	1361	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do2d_yz"></a><b>dt_do2d_yz</b></p>
	1362	</td> <td style="vertical-align: top;">R</td>
	1363	<td style="vertical-align: top;"><i>value of
	1364	<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
	1365	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1366	interval</font> at which vertical cross section data
	1367	(yz) shall be output (</font>in s<font face="Thorndale">).
	1368	</font> </p> <p><span lang="en-GB"><font face="Thorndale">If output of
[5]	1369	horizontal cross sections is switched on (see </font></span><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>
[48]	1370	<span lang="en-GB"><font face="Thorndale">and
	1371	</font></span><a href="#section_yz"><span lang="en-GB"><font face="Thorndale">section_yz</font></span></a><span lang="en-GB"><font face="Thorndale">),
[5]	1372	this parameter can be used to assign the temporal interval at which
[48]	1373	cross section data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
	1374	be skipped at the beginning of a simulation using parameter <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, which
	1375	has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
	1376	time is the beginning of
	1377	the simulation, i.e. output takes place at times t = <b>skip_time_do2d_yz
	1378	+ dt_do2d_yz</b>,
	1379	<span style="font-weight: bold;">skip_time_do2d_yz</span>
	1380	+ 2*<b>dt_do2d_yz</b>, <span style="font-weight: bold;">skip_time_do2d_yz
	1381	</span>+ 3*<b>dt_do2d_yz</b>, etc. The actual output
	1382	times
[5]	1383	can deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
[48]	1384	</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do2d_at_begin"><span lang="en-GB"><font face="Thorndale">do2d_at_begin</font></span></a>
	1385	has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
	1386	the time t = 0 or at the
[5]	1387	respective starting times of restart runs).</font></span> </p>
[48]	1388	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_do3d"></a><b>dt_do3d</b></p>
	1389	</td> <td style="vertical-align: top;">R</td>
	1390	<td style="vertical-align: top;"><i>value of
	1391	<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
	1392	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1393	interval</font> at which 3d volume data shall be output (</font>in
	1394	<font face="Thorndale">s).  </font> </p>
	1395	<p><span lang="en-GB"><font face="Thorndale">If
	1396	output of
	1397	3d-volume data is switched on (see </font></span><font><a href="#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a>)<span style="font-family: thorndale;">, this parameter can be used
	1398	to assign
[5]	1399	th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
[48]	1400	interval at which 3d-data shall be output. </font></span><span lang="en-GB"><font face="Thorndale">Output can
	1401	be skipped at the beginning of a simulation using parameter <a href="#skip_time_do3d">skip_time_do3d</a>, which has
	1402	zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
	1403	time is the
	1404	beginning of the simulation, i.e. output takes place at times t = <b>skip_time_do3d
	1405	+ dt_do3d</b>,
	1406	<span style="font-weight: bold;">skip_time_do3d</span>
	1407	+ 2*<b>dt_do3d</b>, <span style="font-weight: bold;">skip_time_do3d</span>
	1408	+ 3*<b>dt_do3d</b>, etc. The actual output times can
[5]	1409	deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">). <br>
[48]	1410	</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Parameter </font></span><a href="#do3d_at_begin"><span lang="en-GB"><font face="Thorndale">do3d_at_begin</font></span></a>
	1411	has to be used if an additional output is wanted at the start of a run <span lang="en-GB"><font face="Thorndale">(thus at
	1412	the time t = 0 or at the
[5]	1413	respective starting times of restart runs).</font></span> </p>
[61]	1414	</td> </tr> <tr><td style="vertical-align: top;"><a name="dt_max"></a><span style="font-weight: bold;">dt_max</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">20.0</span></td><td>Maximum
	1415	allowed value of the timestep (in s).<br><br>By default,
	1416	the maximum timestep is restricted to be 20 s. This might be o.k. for
	1417	simulations of any kind of atmospheric turbulence but may have to be
	1418	changed for other situations.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="dt_restart"></a><b>dt_restart</b></p>
[48]	1419	</td> <td style="vertical-align: top;">R</td>
	1420	<td style="vertical-align: top;"><i>9999999.9</i></td>
	1421	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1422	interval</font> at which a new
	1423	restart run is to be carried out (</font>in <font face="Thorndale">s). </font> </p> <p><span lang="en-GB"><font face="Thorndale">For a
	1424	description
[5]	1425	how to assign restart times manually see run time parameter </font></span><a href="#restart_time"><span lang="en-GB"><font face="Thorndale">restart_time</font></span></a><span lang="en-GB"><font face="Thorndale">. <span style="font-weight: bold;">dt_restart</span>
	1426	does not show any effect, if <span style="font-weight: bold;">restart_time</span>
[48]	1427	has not been set.</font></span> </p> </td> </tr>
	1428	<tr> <td style="vertical-align: top;"> <p><a name="dt_run_control"></a><b>dt_run_control</b></p>
	1429	</td> <td style="vertical-align: top;">R</td>
	1430	<td style="vertical-align: top;"><i>60.0</i></td>
	1431	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1432	interval</font> at which run control
	1433	output is to be made (</font>in <font face="Thorndale">s).
	1434	</font> </p> <p><span lang="en-GB"><font face="Thorndale">Run control
	1435	information is output to the local ASCII-file </font></span><a href="chapter_3.4.html#RUN_CONTROL"><span lang="en-GB"><font face="Thorndale">RUN_CONTROL</font></span></a><span lang="en-GB"><font face="Thorndale">. At each
	1436	output time, one line
[5]	1437	with information about the size of the time step, maximum speeds, total
	1438	kinetic energy etc. is written to this file. Reference time is the
	1439	beginning of the simulation, i.e. output takes place at times t = <b>dt_run_control</b>,
[48]	1440	2<b>dt_run_control</b>, 3<b>dt_run_control</b>,
	1441	etc., and always at
[5]	1442	the beginning of a model run (thus at the time t = 0 or at the
	1443	respective starting times of restart runs). The actual output times can
	1444	deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).<br>
[48]	1445	</font></span></p> <p><span lang="en-GB"><font face="Thorndale">Run control
[5]	1446	information is output after each time step can be achieved via <b>dt_run_control</b>
[48]	1447	= <i>0.0</i>.</font></span> </p> </td>
[61]	1448	</tr> <tr> <td style="vertical-align: top;"><p><a name="end_time"></a><b>end_time</b></p>
[48]	1449	</td> <td style="vertical-align: top;">R</td>
	1450	<td style="vertical-align: top;"><i>0.0</i></td>
	1451	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Simulation time of the 3D
	1452	model (</font>in <font face="Thorndale">s).
	1453	</font> </p> <p><span lang="en-GB"><font face="Thorndale">The simulation time
[5]	1454	is starting from the beginning of the initialization run (t = 0), not
	1455	starting from the beginning of the respective restart run.</font></span>
[48]	1456	</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="force_print_header"></a><b>force_print_header</b></p>
	1457	</td> <td style="vertical-align: top;">L</td>
	1458	<td style="vertical-align: top;"><i>.F.</i></td>
	1459	<td style="vertical-align: top;"> <p>Steering of
	1460	header output to the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
	1461	</p> <p>By default, informations about the model
	1462	parameters in use are
[5]	1463	output to the beginning of file RUN_CONTROL for initial runs only
	1464	(these informations are identical to that which are output to the local
	1465	file <a href="chapter_3.4.html#HEADER">HEADER</a>).
[48]	1466	With <b>force_print_header</b> = <i>.T.</i>,
	1467	these informations are
[5]	1468	also output to <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
[48]	1469	at restart runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mg_cycles"></a><b>mg_cycles</b></p>
	1470	</td> <td style="vertical-align: top;">I</td>
	1471	<td style="vertical-align: top;"><i>-1</i></td>
	1472	<td style="vertical-align: top;"> <p>Number of
	1473	cycles to be used with the multi-grid scheme.<br> <br>
[5]	1474	This parameter determines the number of cycles to be carried out in the
	1475	multi-grid method used for solving the Poisson equation for
	1476	perturbation pressure (see <a href="#psolver">psolver</a>).
	1477	The type of the cycles can be set with <a href="#cycle_mg">cycle_mg</a>.<br>
[61]	1478	</p> <br>By default (<b>mg_cyles</b> = <i>-
	1479	1</i>), the
[48]	1480	number of cycles
[5]	1481	depends on the requested accuracy of the scheme (see <a href="#residual_limit">residual_limit</a>)
	1482	and may vary from time step to time step. In this case, the CPU time
	1483	for a run will be difficult to estimate, since it heavily depends on
[48]	1484	the total number of the cycles to be carried out.<br> <br>
	1485	By assigning <b>mg_cycles</b> a value (>=<span style="font-style: italic;">1</span>), the number of
	1486	cycles can be
	1487	fixed so that the CPU time can be clearly estimated. <br> <br>
	1488	<b>Note:</b> When using a fixed number of cycles, the user
	1489	must
[5]	1490	examine the local file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>
	1491	regularly to check whether the divergence of the velocity field is
	1492	sufficiently reduced by the pressure solver. It should be reduced at
	1493	least by two orders of magnitude. For cyclic boundary conditions along
	1494	both horizontal directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
[48]	1495	and <a href="chapter_4.1.html#bc_ns">bc_ns</a>) <span style="font-weight: bold;">mg_cycles</span> = <span style="font-style: italic;">2</span> is typically a
	1496	good choice, for
[5]	1497	non-cyclic lateral boundary conditions <span style="font-weight: bold;">mg_cycles</span>
[48]	1498	= <span style="font-style: italic;">4</span> may be
	1499	sufficient.</td> </tr> <tr> <td style="vertical-align: top;"><a name="mg_switch_to_pe0_level"></a><b>mg_switch_to_pe0_<br>
	1500	level</b></td> <td style="vertical-align: top;">I</td>
	1501	<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;">Grid
	1502	level at which data shall be gathered on PE0.<br> <br>
[5]	1503	In case of a run using several PEs and the multigrid method for solving
	1504	the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
	1505	the value of this parameter defines on which grid level the data are
	1506	gathered on PE0 in order to allow for a further coarsening of the grid.
	1507	The finest grid defines the largest grid level. By default, the
	1508	gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
	1509	It is only possible to gather data from a level larger than the one
	1510	determined automatically. A test run may be neccessary to determine
[48]	1511	this level.</td> </tr> <tr> <td style="vertical-align: top;"><a name="netcdf_64bit"></a><span style="font-weight: bold;">netcdf_64bit</span><br>
	1512	</td> <td style="vertical-align: top;">L<br> </td>
	1513	<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td>
	1514	<td style="vertical-align: top;">NetCDF files will have 64
	1515	bit offset format.<br><br>By
[5]	1516	default, the maximum file size of the NetCDF files opened by PALM is 2
	1517	GByte. Using netcdf_64bit = .TRUE. allows file sizes larger than 2
[48]	1518	GByte.<br><br>The 64 bit offset format can be separately
	1519	switched off for those NetCDF files containing 3d volume date (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
	1520	<span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>)
	1521	using <a href="#netcdf_64bit_3d">netcdf_64bit_3d</a>.<br><br><span style="font-weight: bold;">Warning:</span><br>Some
	1522	(PD or commercial) software may not support the 64 bit offset format.<br>
[61]	1523	</td> </tr><tr><td style="vertical-align: top;"><a name="netcdf_64bit_3d"></a><span style="font-weight: bold;">netcdf_64bit_3d</span></td><td style="vertical-align: top;">L</td><td style="vertical-align: top;">.T.</td><td style="vertical-align: top;">NetCDF files containing 3d
[48]	1524	volume data will have 64 bit offset format.<br><br>This
	1525	switch only comes into effect if <a href="#netcdf_64bit">netcdf_64bit</a>
	1526	= .TRUE.. It allows to switch off separately the 64 bit offset format
	1527	for those NetCDF files containing 3d volume data (<span style="font-family: Courier New,Courier,monospace;">DATA_3D_NETCDF</span>,
	1528	<span style="font-family: Courier New,Courier,monospace;">DATA_3D_AV_NETCDF</span>).</td></tr><tr>
	1529	<td style="vertical-align: top;"> <p><a name="ngsrb"></a><b>ngsrb</b></p> </td>
	1530	<td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>2</i></td>
	1531	<td style="vertical-align: top;">Grid
	1532	level at which data shall be gathered on PE0.<br> <br>
[5]	1533	In case of a run using several PEs and the multigrid method for solving
	1534	the Poisson equation for perturbation pressure (see <a href="#psolver">psolver</a>),
	1535	the value of this parameter defines on which grid level the data are
	1536	gathered on PE0 in order to allow for a further coarsening of the grid.
	1537	The finest grid defines the largest grid level. By default, the
	1538	gathering level is determined automatically and displayed in file <a href="chapter_3.4.html#RUN_CONTROL">RUN_CONTROL</a>.
	1539	It is only possible to gather data from a level larger than the one
	1540	determined automatically. A test run may be neccessary to determine
[48]	1541	this level.</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="normalizing_region"></a><b>normalizing_region</b></p>
	1542	</td> <td style="vertical-align: top;">I</td>
	1543	<td style="vertical-align: top;"><span style="font-style: italic;">0</span><br> </td>
	1544	<td style="vertical-align: top;"> <p>Determines the
	1545	subdomain from which the normalization
	1546	quantities are calculated.  </p> <p>If output
	1547	data of the horizontally averaged vertical profiles
[5]	1548	(see <a href="#data_output_pr">data_output_pr</a>)
	1549	is to be normalized (see <a href="#cross_normalized_x">cross_normalized_x</a>,
[48]	1550	<a href="#cross_normalized_y">cross_normalized_y</a>),
[5]	1551	the respective normalization quantities are by default calculated from
	1552	the averaged data of the total model domain (<b>normalizing_region</b>
[48]	1553	= <i>0</i>) and are thus representative for the total
	1554	domain. Instead
[5]	1555	of that, normalization quantities can also be calculated for a
[48]	1556	subdomain. The wanted subdomain can be given with the parameter <span style="font-weight: bold;">normalizing_region</span>,
	1557	where <i>1</i>
	1558	<= <b>normalizing_region</b> <= <i>9 </i>must
	1559	hold. These
[5]	1560	quantities are then used for normalizing of all profiles (even for that
[48]	1561	of the total domain).</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nsor"></a><b>nsor</b></p>
	1562	</td> <td style="vertical-align: top;">I</td>
	1563	<td style="vertical-align: top;"><i>20</i></td>
	1564	<td style="vertical-align: top;"> <p>Number of
	1565	iterations to be used with the SOR-scheme.  </p> <p>This
	1566	parameter is only effective if the SOR-scheme is selected
[5]	1567	as pressure solver (<a href="#psolver">psolver</a>
[48]	1568	= <span style="font-style: italic;">'sor'</span>).
	1569	The number of
[5]	1570	iterations necessary for a sufficient convergence of the scheme depends
	1571	on the grid point numbers and is to be determined by appropriate test
	1572	runs (the default value will not at all be sufficient for larger grid
	1573	point numbers). The number of iterations used for the first call of the
	1574	SOR-scheme (t = 0) is determined via the parameter <a href="chapter_4.1.html#nsor_ini">nsor_ini</a>.</p>
[48]	1575	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="nz_do3d"></a><b>nz_do3d</b></p>
	1576	</td> <td style="vertical-align: top;">I</td>
	1577	<td style="vertical-align: top;"><i>nz+1</i></td>
	1578	<td style="vertical-align: top;"> Limits the output of 3d
	1579	volume data along the vertical direction (grid point index k).<br><br>By
	1580	default, data for all grid points along z are output. The parameter <span style="font-weight: bold;">nz_do3d</span>
[5]	1581	can be used to limit the output up to a certain vertical grid point
	1582	(e.g. in order to reduce the amount of output data). It affects all
[48]	1583	output of volume data ("normal" output to file, see <a href="#data_output">data_output</a>, as well as output
	1584	for <span style="font-weight: bold;">dvrp</span>-software,
	1585	see <a href="#mode_dvrp">mode_dvrp</a>).</td>
[61]	1586	</tr> <tr> <td style="vertical-align: top;"><p><a name="omega_sor"></a><b>omega_sor</b></p>
[48]	1587	</td> <td style="vertical-align: top;">R</td>
	1588	<td style="vertical-align: top;"><i>1.8</i></td>
	1589	<td style="vertical-align: top;"> <p>Convergence
	1590	factor to be used with the the SOR-scheme.  </p> <p>If
	1591	the SOR-scheme is selected (<a href="#psolver">psolver</a>
	1592	= <span style="font-style: italic;">'sor'</span>),
	1593	this parameter
	1594	determines the value of the convergence factor, where <i>1.0</i>
	1595	<= <b>omega_sor</b> < <i>2.0 </i>.
	1596	The optimum value of <b>omega_sor</b>
[5]	1597	depends on the number of grid points along the different directions in
	1598	space. For non-equidistant grids it can only be determined by
[48]	1599	appropriate test runs.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="prandtl_number"></a><b>prandtl_number</b></p>
	1600	</td> <td style="vertical-align: top;">R</td>
	1601	<td style="vertical-align: top;"><i>1.0</i></td>
	1602	<td style="vertical-align: top;"> <p>Ratio of the
	1603	eddy diffusivities for momentum and heat (K<sub>m</sub>/K<sub>h</sub>).
	1604	</p> <p>For runs with constant eddy diffusivity (see <a href="chapter_4.1.html#km_constant">km_constant</a>),
[5]	1605	this parameter can be used to assign the Prandtl number (ratio K<sub>m</sub>
[72]	1606	/ K<sub>h</sub>).</p> </td> </tr> <tr><td style="vertical-align: top;"><a name="precipitation_amount_interval"></a><span style="font-weight: bold;">precipitation_amount_</span><br style="font-weight: bold;"><span style="font-weight: bold;">interval</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><i>value of
	1607	<a href="chapter_4.2.html#dt_do2d_xy">dt_do2d_<br>xy</a></i></td><td style="vertical-align: top;"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	1608	interval</font> for which the precipitation amount (in mm) shall be calculated and output (</font>in <font face="Thorndale">s).
	1609	</font> </p> <p><span lang="en-GB"></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"></span></a><span lang="en-GB"></span><a href="chapter_4.2.html#section_xy"><span lang="en-GB"></span></a><span lang="en-GB"><font face="Thorndale">This
	1610	parameter requires <a href="chapter_4.1.html#precipitation">precipitation</a> = <span style="font-style: italic;">.TRUE.</span>. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"><span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>The interval must be smaller or equal than the output interval for 2d horizontal cross sections given by </font></span><a href="chapter_4.2.html#dt_do2d_xy"><span lang="en-GB"><font face="Thorndale">dt_do2d_xy</font></span></a><span lang="en-GB"><font face="Thorndale">). The output of the precipitation amount also requires setting of <a href="chapter_4.2.html#data_output">data_output</a> =<span style="font-style: italic;"> 'pra*'</span>.<br>
	1611	</font></span></p> <span lang="en-GB"></span></td></tr><tr>
[48]	1612	<td style="vertical-align: top;"> <p><a name="profile_columns"></a><b>profile_columns</b></p>
	1613	</td> <td style="vertical-align: top;">I</td>
	1614	<td style="vertical-align: top;"><i>3</i></td>
	1615	<td style="vertical-align: top;"> <p>Number of
	1616	coordinate systems to be plotted<span style="font-weight: bold;"></span>
	1617	in one row by <span style="font-weight: bold;">profil</span>.
	1618	</p> <p>This parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	1619	= <span style="font-style: italic;">'profil'</span>.</p><p>It
	1620	determines the layout of plots of
[5]	1621	horizontally averaged profiles (<a href="#data_output_pr">data_output_pr</a>)
	1622	when plotted with the plot software <span style="font-weight: bold;">profil</span>.
	1623	Generally, the number and sequence of coordinate systems (panels) to be
	1624	plotted on one page are
[48]	1625	determined by <a href="#cross_profiles">cross_profiles</a>.
	1626	<b>profile_columns</b>
[5]	1627	determines how many panels are to be
	1628	arranged next to each other in one row (number of columns). The
	1629	respective number of rows on a page is assigned by <a href="#profile_rows">profile_rows</a>.
	1630	According to their order given by <a href="#data_output_pr">data_output_pr</a>,
	1631	the panels are arranged beginning in the top row from left to right and
[48]	1632	then continued in the following row. If the number of panels cranz
	1633	> <b>profile_columns</b> * <b>profile_rows</b>,
	1634	the remaining
[5]	1635	panels are drawn on an additional page. If cranz < <b>profile_columns</b>,
[48]	1636	then <b>profile_columns</b> = cranz is automatically set.
	1637	If
[5]	1638	row  contains any panel, then the value of <b>profile_rows</b>
[48]	1639	is reduced automatically.</p> </td> </tr> <tr>
	1640	<td style="vertical-align: top;"> <p><a name="profile_rows"></a><b>profile_rows</b></p>
	1641	</td> <td style="vertical-align: top;">I</td>
	1642	<td style="vertical-align: top;"><i>2</i></td>
	1643	<td style="vertical-align: top;"> <p>Number of rows
	1644	of coordinate systems to be plotted on one page
	1645	by <span style="font-weight: bold;">profil</span>.
	1646	</p> <p>This parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	1647	= <span style="font-style: italic;">'profil'</span>.</p><p>It
	1648	determines the layout of plots of horizontally averaged
[5]	1649	profiles. See <a href="#profile_columns">profile_columns</a>.</p>
[48]	1650	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psolver"></a><b>psolver</b></p>
	1651	</td> <td style="vertical-align: top;">C * 10</td>
	1652	<td style="vertical-align: top;"><i>'poisfft'</i></td>
	1653	<td style="vertical-align: top;"> <p>Scheme to be
	1654	used to solve the Poisson equation for the
	1655	perturbation pressure.  </p> <br>
	1656	The user can choose between the following schemes:<br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>poisfft</i></td>
	1657	<td style="vertical-align: top;">Direct method using FFT
[5]	1658	along x and y, solution of a
	1659	tridiagonal matrix along z, and backward
	1660	FFT (see Siano, institute reports, volume 54). The FFT routines to be
	1661	used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
	1662	This solver is specially optimized for 1d domain decompositions.
	1663	Vectorization is optimized for domain decompositions along x only.</td>
[61]	1664	</tr> <tr> <td style="vertical-align: top;"><p><i>poisfft_</i>
	1665	<br> <i>hybrid</i></p>
[48]	1666	</td> <td style="vertical-align: top;">Direct
	1667	method using FFT
[5]	1668	along x and y, solution of a
	1669	tridiagonal matrix along z, and backward
	1670	FFT (see Siano, institute reports, volume 54). The FFT routines to be
	1671	used can be determined via the initialization parameter <a href="chapter_4.1.html#fft_method">fft_method</a>.<br>
	1672	This solver is specially optimized for 1d domain decompositions.
	1673	Vectorization is optimized for domain decompositions along x only.</td>
[48]	1674	</tr> <tr> <td style="vertical-align: top;"><i>multigrid</i></td>
	1675	<td style="vertical-align: top;"> <p>Multi-grid
	1676	scheme (see Uhlenbrock, diploma thesis). v-
[5]	1677	and
	1678	w-cycles (see <a href="#cycle_mg">cycle_mg</a>)
	1679	are implemented. The convergence of the iterative scheme can be
	1680	steered by the number of v-/w-cycles to be carried out for each call of
	1681	the scheme (<a href="#mg_cycles">mg_cycles</a>)
	1682	and by the number of Gauss-Seidel iterations (see <a href="#ngsrb">ngsrb</a>)
	1683	to be carried out on each grid level. Instead the requested accuracy
[48]	1684	can be given via <a href="#residual_limit">residual_limit</a>.
	1685	<span style="font-weight: bold;">This is the default!</span>
[5]	1686	The
	1687	smaller this limit is, the more cycles have to be carried out in this
	1688	case and the number of cycles may vary from timestep to timestep.</p>
[61]	1689	<br>If <a href="#mg_cycles">mg_cycles</a>
[5]	1690	is set to its optimal value, the computing time of the
[48]	1691	multi-grid scheme amounts approximately to that of the direct solver <span style="font-style: italic;">poisfft</span>, as long as
	1692	the number of
[5]	1693	grid points in the three directions
	1694	of space corresponds to a power-of-two (2<sup>n</sup>)
[48]	1695	where <i>n</i> >= 5 must hold. With large <i>n,
	1696	</i>the
[5]	1697	multi-grid scheme can even be faster than the direct solver (although
	1698	its accuracy is several orders of magnitude worse, but this does not
	1699	affect the accuracy of the simulation). Nevertheless, the user should
	1700	always carry out some test runs in order to find out the optimum value
	1701	for <a href="#mg_cycles">mg_cycles</a>,
	1702	because the CPU time of a run very critically depends on this
[48]	1703	parameter. <p>This scheme requires that the number of grid
	1704	points of
[5]	1705	the
	1706	subdomains (or of the total domain, if only one PE is uesd) along each
	1707	of the directions can at least be devided once by 2 without rest.</p>
	1708	With parallel runs, starting from a certain grid level the
	1709	data of the subdomains are possibly gathered on PE0 in order to allow
	1710	for a further coarsening of the grid. The grid level for gathering can
	1711	be manually set by <a href="#mg_switch_to_pe0_level">mg_switch_to_pe0_level</a>.<br>
[48]	1712	<p>Using this procedure requires the subdomains to be of
[5]	1713	identical size (see <a href="chapter_4.1.html#grid_matching">grid_matching</a>).</p>
[48]	1714	</td> </tr> <tr> <td style="vertical-align: top;"><i>sor</i></td>
	1715	<td style="vertical-align: top;">Successive over
	1716	relaxation
[5]	1717	method (SOR). The convergence of
	1718	this
	1719	iterative scheme is steered with the parameters <a href="#omega_sor">omega_sor</a>,
[48]	1720	<a href="chapter_4.1.html#nsor_ini">nsor_ini</a>
	1721	and <a href="chapter_4.1.html#nsor">nsor</a>.
	1722	<br>Compared to the direct method and the multi-grid method, this
	1723	scheme
[5]	1724	needs substantially
	1725	more computing time. It should only be used for test runs, e.g. if
[48]	1726	errors in the other pressure solver methods are assumed.</td> </tr>
[61]	1727	</tbody> </table> <br>In order to speed-up
	1728	performance, the Poisson equation is by default
[5]	1729	only solved at the last substep of a multistep Runge-Kutta scheme (see <a href="#call_psolver_at_all_substeps">call_psolver
	1730	at_all_substeps</a> and <a href="chapter_4.1.html#timestep_scheme">timestep_scheme</a>).
[48]	1731	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="rayleigh_damping_factor"></a><b>rayleigh_damping</b>
	1732	<br> <b>_factor</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>0.0 or</i><br>
	1733	<i>0.01</i></td> <td style="vertical-align: top;">
	1734	<p>Factor for Rayleigh damping.  </p> <p>A
	1735	so-called Rayleigh damping is applied to all prognostic
[5]	1736	variables if a non-zero value is assigned to <b>rayleigh_damping_factor</b>.
	1737	If switched on, variables are forced towards the value of their
	1738	respective basic states (e.g. the geostrophic wind). The intensity of
	1739	damping is controlled by the value the <b>rayleigh_damping_factor</b>
	1740	is assigned to.
	1741	The damping starts weakly at a height defined by <a href="#rayleigh_damping_height">rayleigh_damping_height</a>
[48]	1742	and rises according to a sin<sup>2</sup>-function to its
	1743	maximum value
[5]	1744	at
[48]	1745	the top boundary. </p> <p>This method
[5]	1746	effectively damps gravity waves, caused by boundary layer convection,
	1747	which may spread out vertically in the inversion layer and which are
	1748	reflected  at the top
	1749	boundary. This particularly happens with the upstream-spline scheme
	1750	switched on (see <a href="chapter_4.1.html#momentum_advec">momentum_advec</a>
	1751	or <a href="chapter_4.1.html#scalar_advec">scalar_advec</a>).
	1752	Therefore, with this scheme the Rayleigh damping is switched on (<b>rayleigh_damping_factor</b>
[48]	1753	= <i>0.01</i>) by default. Otherwise it remains switched
	1754	off.  </p> <p>The Rayleigh damping factor must
	1755	hold the condition <i>0.0</i>
[5]	1756	<= <b>rayleigh_damping_factor</b>
	1757	<= <i>1.0</i>. Large values (close to <span style="font-style: italic;">1.0</span>) can cause
[48]	1758	numerical instabilities.</p> </td> </tr> <tr>
	1759	<td style="vertical-align: top;"> <p><a name="rayleigh_damping_height"></a><b>rayleigh_damping</b>
	1760	<br> <b>_height</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"> <p><i>2/3 *</i>
[61]	1761	<br><span style="font-style: italic;">zu</span><i style="font-style: italic;">(nz)</i></p>
[48]	1762	</td> <td style="vertical-align: top;"> <p>Height
	1763	where the Rayleigh damping starts (in m).  </p> <p>With
	1764	Rayleigh damping switched on (see <a href="#rayleigh_damping_factor">rayleigh_damping_factor</a>),
[5]	1765	this parameter determines the range where damping is applied. By
	1766	default, Rayleigh damping will be applied in the upper third of the
	1767	model
[48]	1768	domain.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="residual_limit"></a><b>residual_limit</b></p>
	1769	</td> <td style="vertical-align: top;">R</td>
	1770	<td style="vertical-align: top;"><i>1.0E-6</i></td>
	1771	<td style="vertical-align: top;"> <p>Largest
	1772	residual permitted for the multi-grid scheme (in s<sup>-2</sup>m<sup>-3</sup>).
	1773	</p> <p>This is a parameter to steer the accuracy of the
	1774	multi-grid
[5]	1775	scheme (see <a href="#psolver">psolver</a>).
	1776	The assigned cycle (v- or w-cycle, see <a href="#mg_cycles">mg_cycles</a>)
[48]	1777	is passed through until the residual falls below the limit given by <span style="font-weight: bold;">residual_limit</span>. If
	1778	this
[5]	1779	is not the case after 1000 cycles, the PALM aborts with a corresponding
[48]	1780	error message.</p> <p>The reciprocal value of this
	1781	parameter can be interpreted as
[5]	1782	a factor by the divergence of the provisional
	1783	velocity field is approximately reduced after the multi-grid scheme has
	1784	been applied (thus the default value causes a reduction of the
[48]	1785	divergence by approx. 6 orders of magnitude).  </p> </td>
[61]	1786	</tr> <tr> <td style="vertical-align: top;"><p><a name="restart_time"></a><b>restart_time</b></p>
[48]	1787	</td> <td style="vertical-align: top;">R</td>
	1788	<td style="vertical-align: top;"><i>9999999.9</i></td>
	1789	<td style="vertical-align: top;"> <p>Simulated time
	1790	after which a restart run is to be carried out
	1791	(in s). </p> <p>The simulated time refers to the
	1792	beginning of the
[5]	1793	initial run (t = 0), not to the beginning of the respective
	1794	restart run. Restart runs can additionally be forced to be carried out
[48]	1795	in regular intervals using the run time parameter <a href="#dt_restart">dt_restart</a>. </p> <p><span style="font-weight: bold;">Note:</span><br>
[5]	1796	A successful operation of this parameter requires additional
	1797	modifications in the <span style="font-weight: bold;">mrun</span>-call
	1798	for the respective run (see <a href="chapter_3.3.html">chapter
[48]	1799	3.3</a>).<br> </p> <p>The choice of <b>restart_time</b>
	1800	or <b>dt_restart</b> does
[5]	1801	not override the automatic start of restart runs in case that the job
[48]	1802	runs out of CPU time. <br> </p> </td> </tr>
	1803	<tr> <td style="vertical-align: top;"> <p><a name="section_xy"></a><b>section_xy</b></p>
	1804	</td> <td style="vertical-align: top;">I(100)<br>
	1805	</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span><br>
	1806	</td> <td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position
	1807	of cross section(s) for output of 2d horizontal cross
	1808	sections (grid point index k).  </font> </p> <p><span lang="en-GB"><font face="Thorndale">If output
	1809	of
	1810	horizontal cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this
	1811	parameter can be used to
[5]	1812	define the position(s) of the cross section(s). Up to 100 positions of
	1813	cross sections can be selected by assigning <b>section_xy</b>
	1814	the
	1815	corresponding vertical grid point index/indices k of the requested
	1816	cross section(s). The exact location (height level) of the cross
	1817	section depends on the variable for which the output is made: zu(k) for
	1818	scalars and horizontal velocities, zw(k) for the vertical velocity.
	1819	Information about the exact location of the cross section is contained
	1820	in the NetCDF output file (if the default NetCDF output is switched on;
	1821	see <a href="#data_output_format">data_output_format</a>).</font></span></p><p><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_xy</span> = <span style="font-style: italic;">-1</span>
[48]	1822	creates the output of horizontal cross sections averaged along z. In
	1823	the
	1824	NetCDF output file these (averaged) cross sections are given the
	1825	z-coordinate <span style="font-style: italic;">-1.0</span>.</font></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Assignments to <b>section_xy</b>
[5]	1826	does not effect the output of horizontal cross sections of variable u<sub>*</sub>
[48]	1827	and theta<sub></sub> and the liquid water path lwp. For
	1828	these quantities always only one cross
	1829	section (for z=zu(1)) is output.</font></span></p><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
	1830	<span style="font-style: italic;">'iso2d'</span> and
	1831	if several cross sections are selected (e.g. <b>section_xy</b>
	1832	= <i>1</i>, <i>10</i>, <i>15</i>),
	1833	then the respective data are
[5]	1834	successively written to file. The output order follows the order given
	1835	by <b>section_xy</b>. </font></span></td>
[61]	1836	</tr> <tr> <td style="vertical-align: top;"><p><a name="section_xz"></a><b>section_xz</b></p>
[48]	1837	</td> <td style="vertical-align: top;">I(100)<br>
	1838	</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
	1839	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of cross section(s)
	1840	for output of 2d (xz) vertical cross sections (grid point
	1841	index j).  </font> </p> <span lang="en-GB"><font face="Thorndale">If output of
	1842	vertical xz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">), this
	1843	parameter can be used to
[5]	1844	define the position(s) of the cross section(s). Up to 100 positions of
[48]	1845	cross sections can be selected by assigning <b>section_xz</b>
	1846	the
[5]	1847	corresponding horizontal grid point index/indices j of the requested
	1848	cross section(s). The exact position (in y-direction) of the cross
[48]	1849	section is given by j</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a> <span lang="en-GB"><font face="Thorndale">or (j-0.5)</font></span><a href="chapter_4.1.html#dy"><span lang="en-GB"><font face="Thorndale">dy</font></span></a><span lang="en-GB"><font face="Thorndale">, depending
	1850	on which grid the output quantity is defined. However, in
	1851	the NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
	1852	default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
	1853	no distinction is made between the quantities and j*<span style="font-weight: bold;">dy</span> is used for all
	1854	positions.<br><br>Assigning <span style="font-weight: bold;">section_xz</span> = <span style="font-style: italic;">-1</span>
[5]	1855	creates the output of vertical cross sections averaged along y. In the
	1856	NetCDF output file these (averaged) cross sections are given the
[48]	1857	y-coordinate <span style="font-style: italic;">-1.0</span>.<br></font></span><span lang="en-GB"><font face="Thorndale"><br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
	1858	<span style="font-style: italic;">'iso2d'</span> and
	1859	</font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
	1860	selected (e.g. <b>section_xz</b> = <i>0</i>, <i>12</i>,
	1861	<i>27</i>),
[5]	1862	then the respective data are successively written to file. The output
	1863	order follows the order given by <b>section_xz</b>.</font></span></td>
[61]	1864	</tr> <tr> <td style="vertical-align: top;"><p><a name="section_yz"></a><b>section_yz</b></p>
[48]	1865	</td> <td style="vertical-align: top;">I(100)<br>
	1866	</td> <td style="vertical-align: top;"><span style="font-style: italic;">no section</span></td>
	1867	<td style="vertical-align: top;"> <p lang="en-GB"><font face="Thorndale">Position of cross section(s)
	1868	for output of 2d (yz) vertical cross sections (grid point
	1869	index i).  </font> </p> <span lang="en-GB"><font face="Thorndale">If output of
[5]	1870	vertical yz cross sections is selected (see </font></span><a href="chapter_4.2.html#data_output"><span lang="en-GB"><font face="Thorndale">data_output</font></span></a><span lang="en-GB"><font face="Thorndale">),
	1871	this parameter can be used to define the position(s) of the cross
	1872	section(s). Up to 100 positions of cross sections can be selected by
[48]	1873	assigning <b>section_yz</b> the corresponding horizontal
	1874	grid point
[5]	1875	index/indices i of the requested cross section(s). The exact position
[48]	1876	(in x-direction) of the cross section is given by i</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a> <span lang="en-GB"><font face="Thorndale">or (i-0.5)</font></span><a href="chapter_4.1.html#dx"><span lang="en-GB"><font face="Thorndale">dx</font></span></a><span lang="en-GB"><font face="Thorndale">, depending
	1877	on which grid the output quantity is defined. </font></span><span lang="en-GB"><font face="Thorndale">However, in
	1878	the NetCDF output file </font></span><span lang="en-GB"><font face="Thorndale">(if the
	1879	default NetCDF output is switched on; see <a href="chapter_4.2.html#data_output_format">data_output_format</a>)
	1880	no distinction is made between the quantities and i*<span style="font-weight: bold;">dx</span> is used for all
	1881	positions.<br><br></font></span><span lang="en-GB"><font face="Thorndale">Assigning <span style="font-weight: bold;">section_yz</span> = <span style="font-style: italic;">-1</span>
[5]	1882	creates the output of vertical cross sections averaged along x. In the
[48]	1883	NetCDF output file these (averaged) cross sections are given the
	1884	x-coordinate <span style="font-style: italic;">-1.0</span>.</font></span><br><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale"> <br></font></span><span lang="en-GB"><font face="Thorndale">In case of <span style="font-weight: bold;">data_output_format</span> =
	1885	<span style="font-style: italic;">'iso2d'</span> and
	1886	</font></span><span lang="en-GB"><font face="Thorndale">if several cross sections are
	1887	selected (e.g. <b>section_yz</b> = <span style="font-style: italic;">3</span>, <span style="font-style: italic;">27</span>, 19), then the
[5]	1888	respective data are successively written to file. The output order
	1889	follows the order given by <b>section_yz</b>.</font></span></td>
[48]	1890	</tr> <tr> <td style="vertical-align: top;"><a name="skip_time_data_output"></a><span style="font-weight: bold;">skip_time_data_output</span><br>
	1891	</td> <td style="vertical-align: top;">R<br> </td>
	1892	<td style="vertical-align: top;"><span style="font-style: italic;">0.0</span><br> </td>
	1893	<td style="vertical-align: top;">No data output before
	1894	this interval has passed (in s).<br><br>This
	1895	parameter causes that data output activities are starting not before
	1896	this interval
	1897	(counting from the beginning of the simulation, t=0) has passed. By
	1898	default, this
[5]	1899	applies for output of instantaneous 3d volume data, cross section data,
	1900	spectra and vertical profile data as well as for temporally averaged 2d
[48]	1901	and 3d data. Individual intervals can be assigned using parameters <a href="#skip_time_do3d">skip_time_do3d</a>, <a href="#skip_time_do2d_xy">skip_time_do2d_xy</a>, <a href="#skip_time_do2d_xz">skip_time_do2d_xz</a>, <a href="#skip_time_do2d_yz">skip_time_do2d_yz</a>, <a href="#skip_time_dosp">skip_time_dosp</a>, <a href="#skip_time_dopr">skip_time_dopr</a>, and <a href="#skip_time_data_output_av">skip_time_data_output_av</a>.<br><br><span style="font-weight: bold;">Example:</span><br>If
	1902	the user has set <a href="#dt_data_output">dt_data_output</a>
	1903	= <span style="font-style: italic;">3600.0</span>
	1904	and <span style="font-weight: bold;">skip_time_data_output</span>
	1905	= <span style="font-style: italic;">1800.0</span>,
	1906	then the first output will be done at t = 5400 s.<br> </td>
	1907	</tr> <tr><td style="vertical-align: top;"><a name="skip_time_data_output_av"></a><span style="font-weight: bold;">skip_time_data_output_av</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="#skip_time_data_output">skip_time_<br>data_output</a></span></td><td style="vertical-align: top;">No output of temporally
	1908	averaged 2d/3d data before this interval has passed (in s).<br><br>This
	1909	parameter causes that data output activities are starting not before
	1910	this interval
	1911	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	1912	the user has set <a href="#dt_data_output_av">dt_data_output_av</a>
	1913	= <span style="font-style: italic;">3600.0</span>
	1914	and <span style="font-weight: bold;">skip_time_data_output_av</span>
	1915	= <span style="font-style: italic;">1800.0</span>,
	1916	then the first output will be done at t = 5400 s.</td></tr><tr>
	1917	<td style="vertical-align: top;"><a name="skip_time_dopr"></a><span style="font-weight: bold;">skip_time_dopr</span><br>
	1918	</td> <td style="vertical-align: top;">R<br> </td>
	1919	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
	1920	</td> <td style="vertical-align: top;">No output of
	1921	vertical profile data before this interval has passed (in s).<br><br>This
	1922	parameter causes that data output activities are starting not before
	1923	this interval
	1924	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	1925	the user has set <a href="#dt_dopr">dt_dopr</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dopr</span> = <span style="font-style: italic;">1800.0</span>, then the
	1926	first output will be done at t = 5400 s. </td> </tr> <tr>
	1927	<td style="vertical-align: top;"><a name="skip_time_do2d_xy"></a><span style="font-weight: bold;">skip_time_do2d_xy</span><br>
	1928	</td> <td style="vertical-align: top;">R<br> </td>
	1929	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
	1930	</td> <td style="vertical-align: top;">No output of
	1931	instantaneous horizontal cross section data before this interval has
	1932	passed (in s).<br><br>This
	1933	parameter causes that data output activities are starting not before
	1934	this interval
	1935	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	1936	the user has set <a href="#dt_do2d_xy">dt_do2d_xy</a>
	1937	= <span style="font-style: italic;">3600.0</span>
	1938	and <span style="font-weight: bold;">skip_time_do2d_xy</span>
	1939	= <span style="font-style: italic;">1800.0</span>,
	1940	then the first output will be done at t = 5400 s. </td> </tr>
	1941	<tr> <td style="vertical-align: top;"><a name="skip_time_do2d_xz"></a><span style="font-weight: bold;">skip_time_do2d_xz</span><br>
	1942	</td> <td style="vertical-align: top;">R<br> </td>
	1943	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
	1944	</td> <td style="vertical-align: top;">No output of
	1945	instantaneous vertical (xz) cross section data before this interval has
	1946	passed (in s).<br><br>This
	1947	parameter causes that data output activities are starting not before
	1948	this interval
	1949	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	1950	the user has set <a href="#dt_do2d_xz">dt_do2d_xz</a>
	1951	= <span style="font-style: italic;">3600.0</span>
	1952	and <span style="font-weight: bold;">skip_time_do2d_xz</span>
	1953	= <span style="font-style: italic;">1800.0</span>,
	1954	then the first output will be done at t = 5400 s. </td> </tr>
	1955	<tr> <td style="vertical-align: top;"><a name="skip_time_do2d_yz"></a><span style="font-weight: bold;">skip_time_do2d_yz</span><br>
	1956	</td> <td style="vertical-align: top;">R<br> </td>
	1957	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
	1958	</td> <td style="vertical-align: top;">No output of
	1959	instantaneous vertical (yz) cross section data before this interval has
	1960	passed (in s).<br><br>This
	1961	parameter causes that data output activities are starting not before
	1962	this interval
	1963	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	1964	the user has set <a href="#dt_do2d_yz">dt_do2d_yz</a>
	1965	= <span style="font-style: italic;">3600.0</span>
	1966	and <span style="font-weight: bold;">skip_time_do2d_yz</span>
	1967	= <span style="font-style: italic;">1800.0</span>,
	1968	then the first output will be done at t = 5400 s. </td> </tr>
	1969	<tr> <td style="vertical-align: top;"><a name="skip_time_do3d"></a><span style="font-weight: bold;">skip_time_do3d</span><br>
	1970	</td> <td style="vertical-align: top;">R<br> </td>
	1971	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
	1972	</td> <td style="vertical-align: top;">No output of
	1973	instantaneous 3d volume data before this interval has passed (in s).<br><br>This
	1974	parameter causes that data output activities are starting not before
	1975	this interval
	1976	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	1977	the user has set <a href="#dt_do3d">dt_do3d</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_do3d</span> = <span style="font-style: italic;">1800.0</span>, then the
	1978	first output will be done at t = 5400 s. </td> </tr>
	1979	<tr> <td style="vertical-align: top;"> <p><a name="termination_time_needed"></a><b>termination_time</b>
	1980	<br> <b>_needed</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">35.0</span><br> </td>
	1981	<td style="vertical-align: top;"> <p>CPU time
	1982	needed for terminal actions at the end of a run in
	1983	batch mode (in s).<br> </p> <p>If the environment
	1984	variable <b>write_binary </b>is
[5]	1985	set <i>true</i> (see <a href="chapter_3.3.html">chapter
[48]	1986	3.3</a>), PALM checks the remaining CPU time of the job after
	1987	each
[5]	1988	timestep. Time integration must not consume the CPU time completely,
	1989	since several actions still have to be carried out after time
	1990	integration has finished (e.g. writing of binary data for the restart
	1991	run, carrying out output commands, copying of local files to their
	1992	permanent destinations, etc.) which also takes some time. The maximum
	1993	possible time needed for these activities plus a reserve is to be given
[48]	1994	with the parameter <b>termination_time_needed</b>. Among
	1995	other things,
[5]	1996	it depends on
	1997	the number of grid points used. If its value is selected too small,
	1998	then the
	1999	respective job will be prematurely aborted by the queuing system, which
	2000	may result in a data loss and will possibly interrupt the job chain.<br>
[48]	2001	</p> <p>An abort happens in any way, if the environment
	2002	variable <span style="font-weight: bold;">write_binary</span>
	2003	is not set to <span style="font-style: italic;">true</span>
	2004	and if moreover the job has
	2005	been assigned an insufficient CPU time by <b>mrun</b>
	2006	option <tt><tt>-t</tt></tt>. <i><br>
	2007	</i> </p> <p><span style="font-weight: bold;">Note:</span><br>
	2008	On the IBM computers of the HLRN the time used by the job <span style="font-weight: bold;">before</span> the start of
	2009	PALM
[5]	2010	have also to be accounted for (e.g. for
[48]	2011	compilation and copying of input files).</p> </td> </tr>
	2012	<tr> <td style="vertical-align: top;"> <p><a name="use_prior_plot1d_parameters"></a><b>use_prior_plot1d</b>
	2013	<br> <b>_parameters</b></p> </td> <td style="vertical-align: top;">L</td> <td style="vertical-align: top;"><i>.F.</i></td>
	2014	<td style="vertical-align: top;"> <p>Additional
	2015	plot of vertical profile data with <span style="font-weight: bold;">profil</span>
	2016	from preceding runs of the
	2017	job chain.  </p> <p>This parameter only applies
	2018	for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	2019	= <span style="font-style: italic;">'profil'</span>.</p><p>By
	2020	default, plots of horizontally averaged vertical profiles
[5]	2021	(see <a href="#data_output_pr">data_output_pr</a>)
	2022	only contain profiles of data produced by the model
	2023	run. If profiles of prior times (i.e. data of preceding jobs of a
	2024	job chain) shall be plotted additionally (e.g. for comparison
[48]	2025	purposes), <b>use_prior_plot1d_parameters</b> = <i>.T</i>.
	2026	must be
	2027	set.<br> </p> <p>For further explanation see <a href="chapter_4.5.2.html">chapter
	2028	4.5.2</a>.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d"></a><b>z_max_do1d</b></p>
	2029	</td> <td style="vertical-align: top;">R</td>
	2030	<td style="vertical-align: top;"><i>zu(nzt+1) (model
	2031	top)</i></td> <td style="vertical-align: top;">
	2032	<p>Height level up to which horizontally averaged profiles are to
[5]	2033	be
[48]	2034	plotted with <span style="font-weight: bold;">profil</span>
	2035	(in
	2036	m).  </p> <p>This parameter only applies for
	2037	<a href="chapter_4.2.html#data_output_format">data_output_format</a>
	2038	= <span style="font-style: italic;">'profil'</span>.</p><p>It
	2039	affects plots of horizontally averaged profiles
[5]	2040	(<a href="#data_output_pr">data_output_pr</a>)
	2041	when plotted with the plot software <span style="font-weight: bold;">profil</span>.
	2042	By default, profiles are plotted up to the top boundary. The height
[48]	2043	level up to which profiles are plotted can be decreased by assigning <span style="font-weight: bold;">z_max_do1d</span> a smaller
	2044	value.
	2045	Nevertheless, <span style="font-weight: bold;">all</span>
	2046	vertical
[5]	2047	grid points (0 <= k <= nz+1) are still output to file <a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>.</p>
[48]	2048	<p>If a normalization for the vertical axis was selected (see <a href="#cross_normalized_y">cross_normalized_y</a>), <b>z_max_do1d</b>
[5]	2049	has no effect. Instead, <a href="#z_max_do1d_normalized">z_max_do1d_normalized</a>
[48]	2050	must be used.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="z_max_do1d_normalized"></a><b>z_max_do1d</b>
	2051	<br> <b>_normalized</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;"><i>determined by plot</i>
	2052	<br> <i>data</i> <br> </td> <td style="vertical-align: top;"> <p>Normalized height
	2053	level up to which horizontally averaged
[5]	2054	profiles are to be plotted with <span style="font-weight: bold;">profil</span>.
[48]	2055	</p> <p>This parameter only applies for  <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	2056	= <span style="font-style: italic;">'profil'</span>.</p><p>It
	2057	affects plots of horizontally averaged profiles
[5]	2058	(<a href="#data_output_pr">data_output_pr</a>)
	2059	when plotted with the plot software <span style="font-weight: bold;">profil</span>,
	2060	if a normalization for the vertical axis is selected
	2061	(see <a href="#cross_normalized_y">cross_normalized_y</a>).
	2062	If e.g. the boundary layer height is used for normalization, then <b>z_max_do1d_normalized</b>
[48]	2063	= <i>1.5</i> means that all profiles up to the height
	2064	level of z =
	2065	1.5* z<sub>i </sub>are plotted.</p> </td> </tr>
	2066	<tr> <td style="vertical-align: top;"> <p><a name="z_max_do2d"></a><b>z_max_do2d</b></p>
	2067	</td> <td style="vertical-align: top;">R<br> </td>
	2068	<td style="vertical-align: top;"><span style="font-style: italic;">zu(nz)</span><br> </td>
	2069	<td style="vertical-align: top;"> <p>Height level
	2070	up to which 2d cross sections are to be plotted
[5]	2071	with <span style="font-weight: bold;">iso2d</span>
[48]	2072	(in m).  </p> <p>This parameter only applies for
	2073	<a href="#data_output_format">data_output_format</a>
	2074	= <span style="font-style: italic;">'iso2d'</span>.</p><p>It
	2075	affects plots of  2d vertical cross
[5]	2076	sections (<a href="#data_output">data_output</a>)
[48]	2077	when plotted with <span style="font-weight: bold;">iso2d</span>.
	2078	By
	2079	default, vertical sections are plotted up to the top boundary. <span style="font-weight: bold;"></span>In contrast, with <b>z_max_do2d
	2080	</b>the
[5]	2081	visualization within
[48]	2082	the plot can be limited to a certain height level (0 <= z
	2083	<= <b>z_max_do2d</b>).
	2084	Nevertheless, <span style="font-weight: bold;">all</span>
	2085	grid points
[5]	2086	of the complete cross section are still output to the local files <a href="chapter_3.4.html#PLOT2D_XZ">PLOT2D_XZ</a>
	2087	or <a href="chapter_3.4.html#PLOT2D_YZ">PLOT2D_YZ</a>.
	2088	The level up to which the section is visualized can later be changed by
	2089	manually editing the
	2090	file <a href="chapter_3.4.html#PLOT2D_XZ_GLOBAL">PLOT2D_XZ_GLOBAL</a>
	2091	or <a href="chapter_3.4.html#PLOT2D_YZ_GLOBAL">PLOT2D_YZ_GLOBAL</a>
	2092	(the respective <span style="font-weight: bold;">iso2d</span>-parameter
	2093	is <a href="http://www.muk.uni-hannover.de/institut/software/iso2d_beschreibung.html#YRIGHT">yright</a>).</p>
[61]	2094	</td> </tr> </tbody></table><br>
[102]	2095	<br><h3 style="line-height: 100%;"><a name="particle_parameters"></a>Particle
[5]	2096	parameters: </h3>
[102]	2097	<span style="font-weight: bold;"></span><span style="font-weight: bold;"></span>NAMELIST group name: <span style="font-weight: bold;">particles_par<br>
[61]	2098	</span><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody><tr>
	2099	<td style="vertical-align: top;"><font size="4"><b>Parameter
	2100	name</b></font></td>
[48]	2101	<td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
	2102	<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
	2103	<td style="vertical-align: top;"> <p><font size="4"><b>Explanation</b></font></p>
	2104	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dt_prel"></a><b>dt_prel</b></p>
	2105	</td> <td style="vertical-align: top;">R</td>
	2106	<td style="vertical-align: top;"><i>9999999.9</i></td>
	2107	<td style="vertical-align: top;"> <p><font face="Thorndale, serif"><span lang="en-GB">Temporal
[5]	2108	interval at
[48]	2109	which particles are to be released <span lang="en-GB">from
	2110	a particle
	2111	source </span>(</span></font>in <font face="Thorndale, serif"><span lang="en-GB">s).</span>
	2112	</font> </p> <p><span lang="en-GB"><font face="Thorndale, serif">By default
[5]	2113	particles are released only at the beginning of a simulation
	2114	(t_init=0). The time of the first release (t_init) can be changed with
	2115	package parameter </font></span><span lang="en-GB"></span><font><a href="#particle_advection_start"><font face="Thorndale, serif">particle_advection_start</font></a>.
[48]	2116	</font><span lang="en-GB"><font face="Thorndale, serif">The time of the last release can be
	2117	set with the package parameter <a href="#end_time_prel">end_time_prel</a>.
	2118	If <span style="font-weight: bold;">dt_prel</span>
	2119	has been set, additional
[5]	2120	releases will be at t = t_init+<span style="font-weight: bold;">dt_prel</span>,
[48]	2121	t_init+2*<span style="font-weight: bold;">dt_prel</span>,
	2122	t_init+3*<span style="font-weight: bold;">dt_prel</span>,
	2123	etc.. Actual release times
	2124	may slightly deviate from thesel values (</font></span><span lang="en-GB"><font face="Thorndale, serif">see
	2125	e.g. </font></span><a href="#dt_dopr"><span lang="en-GB"><font face="Thorndale, serif">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">).</font></span></p>
	2126	<p><span lang="en-GB"><font face="Thorndale, serif"> The domain
	2127	of the particle <span lang="en-GB"><font face="Thorndale, serif">source </font></span>as
	2128	well as the distance of  released particles
	2129	within this source </font></span><span lang="en-GB"><font face="Thorndale, serif">are determined via package
	2130	parameters </font></span><a href="#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
	2131	<span lang="en-GB"><font face="Thorndale, serif">and
	2132	</font></span><a href="#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"><font face="Thorndale, serif"> By
	2133	default, one particle is released at all points defined by these
	2134	parameters. The package parameter <a href="#particles_per_point">particles_per_point</a>
	2135	can be used to start more than one particle per point.<br>
	2136	</font></span></p> <p><span lang="en-GB"><font face="Thorndale, serif">Up to 10
	2137	different groups of particles can be released at the same time (see </font></span><a href="chapter_4.2.html#number_of_particle_groups"><span lang="en-GB"><font face="Thorndale, serif">number_of_particle_groups</font></span></a><span lang="en-GB"><font face="Thorndale, serif">)
	2138	where each group may have a different source. All particles belonging
	2139	to one group have the same density ratio and the same radius. All other
	2140	particle features (e.g. location of the source) are
[5]	2141	identical for all groups of particles.</font></span></p>Subgrid
	2142	scale velocities can (optionally) be included for calculating the
	2143	particle advection, using the method of Weil et al. (2004, JAS, 61,
	2144	2877-2887). This method is switched on by the package
[48]	2145	parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.
	2146	This also forces the Euler/upstream method to be used for time
	2147	advancement of the TKE (see initialization parameter <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>).
	2148	The minimum timestep during the sub-timesteps is controlled by package
	2149	parameter <a href="#dt_min_part">dt_min_part</a>. <p><span lang="en-GB"><font face="Thorndale, serif">By
[5]	2150	default, particles are weightless and transported passively with the
	2151	resolved scale flow. Particles can be given a mass and thus an inertia
	2152	by assigning the
[48]	2153	package parameter </font></span><a href="#density_ratio"><span lang="en-GB"><font face="Thorndale, serif">density_ratio</font></span></a><span lang="en-GB"><font face="Thorndale, serif"> a
	2154	non-zero value (it
[5]	2155	defines the ratio of the density of the fluid and the density of the
	2156	particles). In these cases their </font></span><a href="#radius"><span lang="en-GB"><font face="Thorndale, serif">radius</font></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">
	2157	must also be defined, which affects their flow resistance. </font></span><a href="#diameter"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif"> </font></span> </p>
[48]	2158	<p><span lang="en-GB"><font face="Thorndale, serif">Boundary
[5]	2159	conditions for the particle transport can be defined with package
	2160	parameters </font></span><a href="#bc_par_t"><span lang="en-GB"><font face="Thorndale, serif">bc_par_t</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="#bc_par_lr"><span lang="en-GB"><font face="Thorndale, serif">bc_par_lr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="bc_par_ns"><span lang="en-GB"><font face="Thorndale, serif">bc_par_ns</font></span></a>
[48]	2161	<span lang="en-GB"><font face="Thorndale, serif">and
	2162	</font></span><a href="#bc_par_b"><span lang="en-GB"><font face="Thorndale, serif">bc_par_b</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span></p><span lang="en-GB"><font face="Thorndale, serif">Timeseries
	2163	of particle quantities in NetCDF format can be output to local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>
	2164	by using package parameter <a href="#dt_dopts">dt_dopts</a>.<br></font></span><p>For
	2165	analysis, additional output of
[5]	2166	particle
	2167	information in equidistant temporal intervals can be carried out using <a href="#dt_write_particle_data">dt_write_particle_data</a>
	2168	(file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>).<br>
[48]	2169	</p> <p><span style="font-family: thorndale,serif;">Statistical
[5]	2170	informations</span> (e.g. the total number of particles used, the
	2171	number of particles exchanged between the PEs, etc.) are output to the
	2172	local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>,
	2173	if switched on by the parameter <a href="#write_particle_statistics">write_particle_statistics</a>.
[48]	2174	<br> </p> <p><span lang="en-GB"><font face="Thorndale, serif">If a job
[5]	2175	chain is to be carried out, particle
[48]	2176	informations </font></span><span lang="en-GB"><font face="Thorndale, serif">for the restart run (e.g. current
	2177	location of
[5]	2178	all
	2179	particles at the end of the
	2180	run) is output to
[48]	2181	the local file</font></span> <font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font><a href="chapter_3.4.html#PARTICLE_RESTART_DATA_OUT">PARTICLE_RESTART_DATA_OUT</a><font><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"></span></a></font>,
	2182	<span lang="en-GB"><font face="Thorndale, serif">which
	2183	must be saved at the
	2184	end of the run <tt><span lang="en-GB"></span></tt>and
	2185	given as an
[5]	2186	input file to the restart run
	2187	under local file name</font></span> <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>
[48]	2188	u<span lang="en-GB"><font face="Thorndale, serif">sing
	2189	respective file
[5]	2190	connection statements in the <span style="font-weight: bold;">mrun</span>
[48]	2191	configuration file. </font></span> <span lang="en-GB"></span></p><p><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale, serif">The output of
	2192	particles for visualization with the graphic software <span style="font-weight: bold;">dvrp</span> is steered by
	2193	the package
	2194	parameter </font></span><a href="chapter_4.2.html#dt_dvrp"><span lang="en-GB"><font face="Thorndale, serif">dt_dvrp</font></span></a><font face="Thorndale, serif"><span lang="en-GB">.
	2195	For visualization
[5]	2196	purposes particles can be given a
	2197	diameter by the parameter <a href="chapter_4.2.html#dvrp_psize">dvrp_psize</a>
	2198	(this diameter only affects the visualization). All particles have the
	2199	same size. Alternatively, particles can be given an individual size and
[48]	2200	a </span>color <span lang="en-GB">by modifying the
	2201	user-interface (subroutine</span></font> <span style="font-family: monospace;">user_init_particles</span>)<span lang="en-GB"><font face="Thorndale, serif">.
	2202	Particles can pull a
	2203	“tail” behind themselves to improve their
	2204	visualization.
	2205	This is steered via the parameter <a href="chapter_4.2.html#use_particle_tails">use_particle_tails</a>.</font></span><a href="chapter_4.2.html#maximum_number_of_tailpoints"><span lang="en-GB"></span></a></p> <span lang="en-GB"></span><p><b>So far, the
	2206	particle transport realized in PALM does only
[5]	2207	work
[48]	2208	duly in case of a constant vertical grid spacing!</b></p> </td>
[61]	2209	</tr> <tr> <td style="vertical-align: top;"><p><a name="bc_par_b"></a><b>bc_par_b</b></p>
[48]	2210	</td> <td style="vertical-align: top;">C*15</td>
	2211	<td style="vertical-align: top;"><i>´reflect´</i></td>
	2212	<td style="vertical-align: top;"> <p>Bottom
	2213	boundary condition for particle transport. </p> <p>By
	2214	default, particles are reflected at the bottom boundary.
[5]	2215	Alternatively, a particle absorption can set by <b>bc_par_b</b>
[48]	2216	= <i>´absorb´</i>.</p> </td>
[61]	2217	</tr> <tr> <td style="vertical-align: top;"><p><a name="bc_par_lr"></a><b>bc_par_lr</b></p>
[48]	2218	</td> <td style="vertical-align: top;">C*15</td>
	2219	<td style="vertical-align: top;"><i>´cyclic´</i></td>
	2220	<td style="vertical-align: top;"> <p>Lateral
	2221	boundary condition (x-direction) for particle
	2222	transport. </p> <p>By default, cyclic boundary conditions
	2223	are used along x.
[5]	2224	Alternatively, reflection (<b>bc_par_lr</b>
[48]	2225	= <i>´reflect´</i>) or absorption (<b>bc_par_lr</b>
	2226	= <i>´absorb´</i>)
	2227	can be set. <br> </p> <p>This lateral boundary
	2228	conditions should correspond to the
	2229	lateral boundary condition used for the flow (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>).</p> </td>
[61]	2230	</tr> <tr> <td style="vertical-align: top;"><p><a name="bc_par_ns"></a><b>bc_par_ns</b></p>
[48]	2231	</td> <td style="vertical-align: top;">C*15</td>
	2232	<td style="vertical-align: top;"><i>´cyclic´</i></td>
	2233	<td style="vertical-align: top;"> <p>Lateral
	2234	boundary condition (y-direction) for particle
	2235	transport. </p> <p>By default, cyclic boundary conditions
	2236	are used along y.
[5]	2237	Alternatively, reflection (<b>bc_par_ns</b>
[48]	2238	= <i>´reflect´</i>) or absorption (<b>bc_par_ns</b>
	2239	= <i>´absorb´</i>)
	2240	can be set.<br> </p>
[5]	2241	This lateral boundary conditions should correspond to the lateral
[48]	2242	boundary condition used for the flow (see <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</td> </tr>
	2243	<tr> <td style="vertical-align: top;"> <p><a name="bc_par_t"></a><b>bc_par_t</b></p>
	2244	</td> <td style="vertical-align: top;">C*15</td>
	2245	<td style="vertical-align: top;"><i>´absorb´</i></td>
	2246	<td style="vertical-align: top;"> <p>Top boundary
	2247	condition for particle transport. </p> <p>By default,
	2248	particles are absorbed at the top boundary.
[5]	2249	Alternatively, a reflection condition can be set by <b>bc_par_t</b>
[48]	2250	= <i>´reflect´</i>.</p> </td>
[61]	2251	</tr> <tr> <td style="vertical-align: top;"><p><a name="density_ratio"></a><b>density_ratio</b></p>
[48]	2252	</td> <td style="vertical-align: top;">R (10)</td>
	2253	<td style="vertical-align: top;"> <p><i>0.0, 9</i>
	2254	*<br> <i>9999999.9</i></p> </td> <td style="vertical-align: top;"> <p>Ratio of the density
	2255	of the fluid and the density of the
	2256	particles. </p> <p>With the default value<i> </i>the
[5]	2257	particles are weightless and transported passively with the resolved
	2258	scale flow.
[48]	2259	In case of <span style="font-weight: bold;">density_ratio</span>
	2260	/=
[5]	2261	0.0 particles have a mass and hence inertia so that their velocity
	2262	deviates more or less from the velocity of the surrounding flow.
	2263	Particle velocity is calculated analytically and depends on (besides
	2264	the density ratio and the current velocity difference between particles
	2265	and surrounding fluid) the
	2266	particle radius which is determined via <a href="#radius">radius</a>
	2267	as well as on the molecular viscosity (assumed as 1.461E-5 m<sup>2</sup>/s).
[48]	2268	</p> <p>If <b>density_ratio</b> = <i>1.0</i>,
	2269	the particle density
[5]	2270	corresponds to the density of the surrounding fluid and the particles
	2271	do not feel any buoyancy. Otherwise, particles will be accelerated
	2272	upwards (<b>density_ratio</b> > <i>1.0</i>)
	2273	or downwards (<b>density_ratio</b> < <i>1.0</i>).<br>
[48]	2274	</p> <p>With several groups of particles (see <a href="chapter_4.2.html#number_of_particle_groups">number_of_particle_groups</a>),
	2275	each group can be assigned a different value. If the number of values
	2276	given for <span style="font-weight: bold;">density_ratio</span>
	2277	is less than the number of
[5]	2278	groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
	2279	then the last assigned value is used for all remaining groups. This
[48]	2280	means that by default the particle density ratio for all groups will be
	2281	<span style="font-style: italic;">0.0</span>.</p>
	2282	</td> </tr> <tr><td align="left" valign="top"><a name="dt_dopts"></a><span style="font-weight: bold;">dt_dopts</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><i>value of  <a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td><td align="left" valign="top"><p lang="en-GB"><font face="Thorndale"><font face="Thorndale, serif">Temporal
	2283	interval</font> at which time series data of particle quantities
	2284	shall be output (</font>in <font face="Thorndale">s). </font></p>
	2285	<span lang="en-GB"><font face="Thorndale">If
	2286	particle advection is switched on (see</font></span><font><span style="font-family: thorndale;"> <a href="#dt_prel">dt_prel</a>)
	2287	this parameter can be used to assign
[5]	2288	th</span></font><span lang="en-GB"><font face="Thorndale">e temporal
[48]	2289	interval at which time series of particle quantities shall be output.
	2290	Output is written in NetCDF format on local file <a href="chapter_3.4.html#DATA_1D_PTS_NETCDF">DATA_1D_PTS_NETCDF</a>.<br><br>The
[5]	2291	following list gives a short description of the quantities
	2292	available. Most quantities are averages over all particles. The
	2293	quantity name given in the first column is identical to the respective
[48]	2294	name of the variable on the NetCDF file (see section <a href="chapter_4.5.1.html">4.5.1</a> for a general
	2295	description of the NetCDF files).<br><br>In case of using
	2296	more than one particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
[5]	2297	seperate time series are output for each of the groups. The long names
	2298	of the variables in the NetCDF file containing the respective
[48]	2299	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
	2300	group (<span style="font-style: italic;">01</span>, <span style="font-style: italic;">02</span>, etc.). <br> </font></span><table style="text-align: left; width: 631px; height: 652px;" border="1" cellpadding="2" cellspacing="2"><tbody><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">tnpt</span></td><td align="undefined" valign="undefined">total number of
	2301	particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x_</span></td><td align="undefined" valign="undefined">particle
	2302	x-coordinate with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y_</span></td><td align="undefined" valign="undefined">particle
	2303	y-coordinate with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_</span></td><td align="undefined" valign="undefined">particle
	2304	z-coordinate with respect to the particle origin (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z_abs</span></td><td align="undefined" valign="undefined">absolute
	2305	particle z-coordinate (in m)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u</span></td><td align="undefined" valign="undefined">u particle
	2306	velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v</span></td><td align="undefined" valign="undefined">v particle
	2307	velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w</span></td><td align="undefined" valign="undefined">w particle
	2308	velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u"</span></td><td align="undefined" valign="undefined">subgrid-scale u
	2309	particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">v"</span></td><td align="undefined" valign="undefined">subgrid-scale v
	2310	particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w"</span></td><td align="undefined" valign="undefined">subgrid-scale w
	2311	particle velocity component (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_up</span></td><td align="undefined" valign="undefined">total number of
	2312	upward moving particles</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_up</span></td><td align="undefined" valign="undefined">vertical
	2313	velocity of the upward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">w_down</span></td><td align="undefined" valign="undefined">vertical
	2314	velocity of the downward moving particles (in m/s)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_max</span></td><td align="undefined" valign="undefined">maximum number
	2315	of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">npt_min</span></td><td align="undefined" valign="undefined">minimum number
	2316	of particles in a subdomain (=tnpt for non-parallel runs)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">x*2</span></td><td align="undefined" valign="undefined">variance of the
	2317	particle x-coordinate with respect to <span style="color: rgb(255, 0, 0);">x_ </span>(in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">y*2</span></td><td align="undefined" valign="undefined">variance of the
	2318	particle y-coordinate with respect to <span style="color: rgb(255, 0, 0);">y_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">z*2</span></td><td align="undefined" valign="undefined">variance of the
	2319	particle z-coordinate with respect to <span style="color: rgb(255, 0, 0);">z_</span> (in m<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined"><span style="color: rgb(255, 0, 0);">u*2</span></td><td align="undefined" valign="undefined">variance of the
	2320	u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v*2</td><td align="undefined" valign="undefined">variance of the
	2321	v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w*2</td><td align="undefined" valign="undefined">variance of the
	2322	w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">u"2</td><td align="undefined" valign="undefined">variance of the
	2323	subgrid-scale u particle velocity component with respect to <span style="color: rgb(255, 0, 0);">u" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">v"2</td><td align="undefined" valign="undefined">variance of the
	2324	subgrid-scale v particle velocity component with respect to <span style="color: rgb(255, 0, 0);">v" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">w"2</td><td align="undefined" valign="undefined">variance of the
	2325	subgrid-scale w particle velocity component with respect to <span style="color: rgb(255, 0, 0);">w" </span>(in m<sup>2</sup>/s<sup>2</sup>)</td></tr><tr><td align="undefined" valign="undefined">npt*2</td><td align="undefined" valign="undefined">variance of the
	2326	number of particles with respect to the average number of particles per
	2327	subdomain</td></tr></tbody></table><span lang="en-GB"></span><span lang="en-GB"></span></td></tr><tr><td align="left" valign="top"><a name="dt_min_part"></a><span style="font-weight: bold;">dt_min_part</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">0.0002</span></td><td align="left" valign="top">Minimum value for the
	2328	particle timestep when SGS velocities are used (in s).<br><br>For
	2329	a further explanation see package parameter <a href="#use_sgs_for_particles">use_sgs_for_particles</a>.</td></tr><tr>
	2330	<td style="vertical-align: top;"> <p><a name="dt_write_particle_data"></a><b>dt_write_particle_</b>
	2331	<b>data</b></p> </td> <td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><i>9999999.9</i></td>
	2332	<td style="vertical-align: top;"> <p>Temporal
	2333	interval for output of particle data (in s). </p> <p>T<span lang="en-GB"></span><a href="#pr1d"><span lang="en-GB"></span></a><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">his
[5]	2334	parameter can be used to
	2335	assign the temporal interval at which particle data shall be output.</font></span>
	2336	Data are output to
	2337	the local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_DATA</a>.
[48]	2338	<span style="font-family: mon;">See the file description
	2339	for more
	2340	details about its format</span>. </p> <p>By
	2341	default, no particle data are output.</p> </td> </tr>
	2342	<tr> <td style="vertical-align: top;"> <p><a name="dvrp_psize"></a><b>dvrp_psize</b></p>
	2343	</td> <td style="vertical-align: top;">R<br> </td>
	2344	<td style="vertical-align: top;">0.2 * dx<br> </td>
	2345	<td style="vertical-align: top;"> <p>Diameter that
	2346	the particles is given in visualizations with
	2347	the <span style="font-weight: bold;">dvrp</span>
	2348	software (in
	2349	m).  </p> <p>In case that particles are
	2350	visualized with the <span style="font-weight: bold;">dvrp</span>
	2351	software (see <a href="chapter_4.5.7.html">chapter
	2352	4.5.7</a>), their size can be set by parameter <b>dvrp_psize</b>.
	2353	All
	2354	particles are displayed with this same size.<br> </p> <p>Alternatively,
	2355	the particle diameters can be set with the
[5]	2356	user-interface in routine <span style="font-family: monospace;">user_init_particles</span>
	2357	(at the beginning of the simulation) and/or can be redefined after each
	2358	timestep in routine <tt>user<font style="font-size: 11pt;" size="2">_particle_attributes</font></tt>
	2359	(both routines can be found in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt><font style="font-size: 11pt;" size="2">)</font>. </p>
[48]	2360	<p><b>Note:</b> This parameter determines exclusively
	2361	the size
[5]	2362	under which particles appear in the <span style="font-weight: bold;">dvrp</span>
[48]	2363	visualization. The flow relevant particle radius is determined via the
	2364	particle package parameter <a href="#radius">radius</a>!</p>
	2365	</td> </tr> <tr><td align="left" valign="top"><a name="end_time_prel"></a><span style="font-weight: bold;">end_time_prel</span></td><td align="left" valign="top">R</td><td align="left" valign="top"><span style="font-style: italic;">9999999.9</span></td><td align="left" valign="top">Time of the last release of
	2366	particles (in s).<br><br>See also <a href="#particle_advection_start">particle_advection_start</a>.</td></tr><tr>
	2367	<td style="vertical-align: top;"><span style="font-weight: bold;"><a name="initial_weighting_factor"></a>initial_weighting_factor</span></td>
	2368	<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">1.0</span><br> </td>
	2369	<td style="vertical-align: top;">Factor to define the real
	2370	number of initial droplets in a grid box.<br> <br>
[5]	2371	In case of explicitly simulating cloud droplets (see <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a>),
	2372	the real number of initial droplets in a grid box is equal to the
	2373	initial number of droplets in this box (defined by the particle source
	2374	parameters <span lang="en-GB"><font face="Thorndale, serif"> </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
[48]	2375	<span lang="en-GB"><font face="Thorndale, serif">and
	2376	</font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"></span><span lang="en-GB"></span>)
	2377	times the <span style="font-weight: bold;">initial_weighting_factor</span>.</td>
[61]	2378	</tr><tr> <td style="vertical-align: top;"> <p><a name="maximum_number_of_particles"></a><b>maximum_number_of_</b>
[48]	2379	<br> <b>particles</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>1000</i></td>
	2380	<td style="vertical-align: top;"> <p>Maximum number
	2381	of particles (on a PE).  </p> <p>This parameter
	2382	allows to set the number of particles for which
[5]	2383	memory must be allocated at the beginning of the run.
	2384	If this memory becomes insufficient during the run, due to the
	2385	release of further particles (see <a href="#dt_prel">dt_prel</a>),
[48]	2386	then more memory is automatically allocated.<br> </p>
[5]	2387	For runs on several processors, <span style="font-weight: bold;">maximum_number_of_particles</span>
	2388	defines
	2389	the maximum number on each PE. This number must be larger than the
	2390	maximum number of particles initially released in a subdomain.</td>
[61]	2391	</tr> <tr> <td style="vertical-align: top;"><p><a name="maximum_number_of_tailpoints"></a><b>maximum_number_of_</b>
[48]	2392	<br> <b>tailpoints</b></p> </td> <td style="vertical-align: top;">I</td> <td style="vertical-align: top;"><i>100</i></td>
	2393	<td style="vertical-align: top;"> <p>Maximum number
	2394	of tailpoints that a particle tail can
	2395	have.  </p> <p> <b>maximum_number_of_tailpoints</b>
[5]	2396	sets the number of descrete points the tail consists of. A new point is
	2397	added to the particle tails after each time step. If the maximum number
	2398	of tail
	2399	points is reached after the corresponding number of timesteps, the
	2400	oldest respective tail points is deleted within the following
[48]	2401	timestep.  </p> <p>All particle tails have the
	2402	same number of points. The maximum
[5]	2403	length of
	2404	these
	2405	tails is determined by the value of <b>maximum_number_of_tailpoints</b>
	2406	and by the minimum distance between each of the adjoining
	2407	tailpoints,  which can be set by <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.
	2408	Additionally, it can be determined that the temporal displacement
	2409	between the current position of the particle and the oldest point of
	2410	the tail may become not larger than a value to be assigned by <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>.</p>
[48]	2411	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="maximum_tailpoint_age"></a><b>maximum_tailpoint_</b>
	2412	<br> <b>age</b></p> </td> <td style="vertical-align: top;">R</td> <td style="vertical-align: top;">100000.0</td> <td style="vertical-align: top;"> <p>Maximum age that the
	2413	end point of a particle tail is allowed to have (in s).  </p>
	2414	<p>If the temporal displacement between the oldest point of a
[5]	2415	particle tail and the current position of the particle becomes larger
[48]	2416	than the value given by <b>maximum_tailpoint_age</b>, this
	2417	oldest
[5]	2418	point (which defines the end of the tail) is
	2419	removed. If this time is so small that the number of points defining
	2420	the particle tail do not exceed the value given by <b>maximum_number_of_tailpoints</b>,
	2421	then the length the particle tails is a measure for the distance the
	2422	particle travelled along during the time interval defined via <b>maximum_tailpoint_age</b>,
	2423	i.e. for the
	2424	particle velocity. Fast particles will have long tails, slow particles
	2425	shorter ones (note: this will not neccessarily hold if <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>
[48]	2426	= <i>0.0</i>).</p> </td> </tr> <tr>
	2427	<td style="vertical-align: top;"> <p><a name="minimum_tailpoint_distance"></a><b>minimum_tailpoint_distance</b></p>
	2428	</td> <td style="vertical-align: top;">R</td>
	2429	<td style="vertical-align: top;"><i>0.0</i></td>
	2430	<td style="vertical-align: top;"> <p>Minimum
	2431	distance allowed between two adjacent points of a
	2432	particle tail (in m).  </p> <p>In case of <b>minimum_tailpoint_distance</b>
	2433	> <i>0.0 </i>the
[5]	2434	particle tail is extended by a new point only if the distance between
	2435	its current position and the most recent tail point exceed the
	2436	distance given via <b>minimum_tailpoint_distance</b>.<br>
[48]	2437	</p> <p>If the length of the particle tails shall be
	2438	proportional to
[5]	2439	the respective particle velocity, the parameter <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>
[48]	2440	must also be set appropriately. </p> <b>Note:</b><br>
[5]	2441	A suitable choice of <b>minimum_tailpoint_distance</b>
[48]	2442	> <i>0.0</i> is recommended, because then the tail
	2443	coordinates of
[5]	2444	slowly moving particles require less memory and can also be drawn
	2445	faster. The upper limit of <b>minimum_tailpoint_distance</b>
	2446	should be chosen in a way that the visualized particle
	2447	tails still appear as smooth lines. Example: with a model domain of
	2448	1000 m and a monitor resolution of 1280 * 1024 pixels it
[48]	2449	should be sufficient to set <b>minimum_tailpoint_distance</b>
	2450	= <i>5.0</i>
	2451	(m). </td> </tr> <tr> <td style="vertical-align: top;"><a name="number_of_particle_groups"></a><span style="font-weight: bold;">number_of_particle_groups</span><br>
	2452	</td> <td style="vertical-align: top;">I<br> </td>
	2453	<td style="vertical-align: top;">1<br> </td> <td style="vertical-align: top;">Number of particle groups to be
	2454	used.<br> <br>
	2455	Each particle group can be assigned its own source region (see <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
	2456	<a href="#psr">psr</a>, etc.), particle diameter (<a href="#radius">radius</a>) and particle density ratio (<a href="density_ratio">density_ratio</a>).<br><br>If
	2457	less values are given for <a href="#pdx">pdx</a>, <a href="#psl">psl</a>,
[5]	2458	etc. than the number of particle groups, then the last value is used
	2459	for the remaining values (or the default value, if the user did not set
[48]	2460	the parameter).<br> <br>
	2461	The maximum allowed number of particle groups is limited to <span style="font-style: italic;">10</span>.<br> </td>
[61]	2462	</tr><tr><td align="left" valign="top"><a name="particles_per_point"></a><span style="font-weight: bold;">particles_per_point</span></td><td align="left" valign="top">I</td><td align="left" valign="top">1</td><td align="left" valign="top">Number of particles to be
[48]	2463	started per point.<br><br>By default, one particle is
	2464	started at all points of the particle source, defined by <span style="font-family: Thorndale,serif;">the </span><span lang="en-GB"><font face="Thorndale, serif">package
	2465	parameters </font></span><a href="chapter_4.2.html#pst"><span lang="en-GB"><font face="Thorndale, serif">pst</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psl"><span lang="en-GB"><font face="Thorndale, serif">psl</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psr"><span lang="en-GB"><font face="Thorndale, serif">psr</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pss"><span lang="en-GB"><font face="Thorndale, serif">pss</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psn"><span lang="en-GB"><font face="Thorndale, serif">psn</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#psb"><span lang="en-GB"><font face="Thorndale, serif">psb</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdx"><span lang="en-GB"><font face="Thorndale, serif">pdx</font></span></a><span lang="en-GB"><font face="Thorndale, serif">, </font></span><a href="chapter_4.2.html#pdy"><span lang="en-GB"><font face="Thorndale, serif">pdy</font></span></a>
	2466	<span lang="en-GB"><font face="Thorndale, serif">and
	2467	</font></span><a href="chapter_4.2.html#pdz"><span lang="en-GB"><font face="Thorndale, serif">pdz</font></span></a><span lang="en-GB"><font face="Thorndale, serif">.</font></span><span lang="en-GB"></span></td></tr><tr> <td style="vertical-align: top;"> <p><a name="particle_advection_start"></a><b>particle_advection_</b>
	2468	<br> <b>start</b></p> </td> <td style="vertical-align: top;">R </td> <td style="vertical-align: top;">0.0 </td> <td style="vertical-align: top;"> <p>Time of the first
	2469	release of particles (in s). </p> <p>If particles are not
	2470	to be released at the beginning of the
[5]	2471	run, the release time can be set via <b>particle_advection_start</b>.<br>
	2472	If particle transport is switched on in a restart run, then <a href="#read_particles_from_restartfile">read_particles_from_restartfile</a>
[48]	2473	= <span style="font-style: italic;">.F.</span> is
	2474	also required.</p><p>See also <a href="#end_time_prel">end_time_prel</a>.
	2475	</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="particle_maximum_age"></a><b>particle_maximum_age</b></p>
	2476	</td> <td style="vertical-align: top;">R </td>
	2477	<td style="vertical-align: top;"><i>9999999.9</i>
	2478	</td> <td style="vertical-align: top;"> <p>Maximum
	2479	allowed age of particles (in s).  </p> <p>If the
	2480	age of a particle exceeds the time set by <b>particle_maximum_age</b>,
	2481	the particle as well as its tail is deleted.</p> </td> </tr>
	2482	<tr> <td style="vertical-align: top;"> <p><a name="pdx"></a><b>pdx</b></p> </td>
	2483	<td style="vertical-align: top;">R (10)<br> </td>
	2484	<td style="vertical-align: top;"><i>10 * dx</i>
	2485	</td> <td style="vertical-align: top;"> <p>Distance
	2486	along x between particles within a particle source
	2487	(in m).  </p> <p>If the particle source shall be
	2488	confined to one grid point,
	2489	the distances given by <span style="font-weight: bold;">pdx</span>,
	2490	<a href="#pdy">pdy</a>
[5]	2491	and <a href="#pdz">pdz</a>
[48]	2492	must be set larger than the respective domain size or <a href="#psl">psl</a>
	2493	= <a href="#psr">psr</a> has to be set
	2494	alternatively.<br>
	2495	</p> <p><span style="font-weight: bold;">pdx</span>
	2496	can be assigned a different value for each particle group (see <a href="#number_of_particle_groups">number_of_particle_groups</a>).<br>
	2497	</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pdy"></a><b>pdy</b></p>
	2498	</td> <td style="vertical-align: top;">R (10)<br>
	2499	</td> <td style="vertical-align: top;"><i>10
	2500	* dy</i> </td> <td style="vertical-align: top;">Distance
	2501	along y between
[5]	2502	particles within a
[48]	2503	particle source (in m).  </td> </tr> <tr>
	2504	<td style="vertical-align: top;"> <p><a name="pdz"></a><b>pdz</b></p> </td>
	2505	<td style="vertical-align: top;">R (10)<br>
	2506	</td> <td style="vertical-align: top;"><i>10
	2507	* ( zu(2) - zu(1) )</i> </td> <td style="vertical-align: top;">Distance along z between
[5]	2508	particles within a particle source
[48]	2509	(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psb"></a><b>psb</b></p>
	2510	</td> <td style="vertical-align: top;">R (10)<br>
	2511	</td> <td style="vertical-align: top;"><i>10
	2512	* zu(nz/2)</i> </td> <td style="vertical-align: top;">Bottom
	2513	edge of a particle
	2514	source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psl"></a><b>psl</b></p>
	2515	</td> <td style="vertical-align: top;">R (10)<br>
	2516	</td> <td style="vertical-align: top;"><i>10
	2517	* 0.0</i> </td> <td style="vertical-align: top;">Left
	2518	edge of a particle source
	2519	(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psn"></a><b>psn</b></p>
	2520	</td> <td style="vertical-align: top;">R (10)<br>
	2521	</td> <td style="vertical-align: top;"><i>10
	2522	* (ny * dy)</i> </td> <td style="vertical-align: top;">Rear
	2523	(“north”) edge of a
	2524	particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="psr"></a><b>psr</b></p>
	2525	</td> <td style="vertical-align: top;">R (10)<br>
	2526	</td> <td style="vertical-align: top;"><i>10
	2527	* (nx * dx)</i> </td> <td style="vertical-align: top;">Right
	2528	edge of a particle
	2529	source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pss"></a><b>pss</b></p>
	2530	</td> <td style="vertical-align: top;">R (10)<br>
	2531	</td> <td style="vertical-align: top;"><i>10
	2532	* 0.0</i> </td> <td style="vertical-align: top;">Front
	2533	(“south”) edge of a
	2534	particle source (in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="pst"></a><b>pst</b></p>
	2535	</td> <td style="vertical-align: top;">R (10)<br>
	2536	</td> <td style="vertical-align: top;"><i>10
	2537	* zu(nz/2)</i> </td> <td style="vertical-align: top;">Top
	2538	edge of a particle source
	2539	(in m). </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="radius"></a><b>radius</b></p>
	2540	</td> <td style="vertical-align: top;">R (10)</td>
	2541	<td style="vertical-align: top;"><i>0.0, 9</i>*<br>
	2542	<i>9999999.9</i></td> <td style="vertical-align: top;">Particle radius (in m).<br>
[61]	2543	<br>The viscous friction (in case of a velocity difference
	2544	between
[5]	2545	particles and surrounding fluid) depends on the particle radius which
	2546	must be assigned as soon as <a href="chapter_4.2.html#density_ratio">density_ratio</a>
[48]	2547	/= <i>0.0</i>.<br> <br>
	2548	With several groups of particles (see <a href="#number_of_particle_groups">number_of_particle_groups</a>),
	2549	each group can be assigned a different value. If the number of values
	2550	given for <span style="font-weight: bold;">radius</span>
	2551	is less than the number of
[5]	2552	groups defined by <span style="font-weight: bold;">number_of_particle_groups</span>,
	2553	then the last assigned value is used for all remaining groups. This
[48]	2554	means that by default the particle radius for all groups will be <span style="font-style: italic;">0.0</span>.<br> </td>
[61]	2555	</tr><tr> <td style="vertical-align: top;"> <p><a name="random_start_position"></a><b>random_start_position</b></p>
[48]	2556	</td> <td style="vertical-align: top;">L<br> </td>
	2557	<td style="vertical-align: top;"><i>.F.</i> </td>
	2558	<td style="vertical-align: top;"> <p><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;"><font color="#000000">Initial position of the</font></span>
	2559	particles is
	2560	varied randomly within certain limits.  </p> <p>By
	2561	default, the initial positions of particles within the
[5]	2562	source excatly correspond with the positions given by <a href="#psl">psl</a>,
[48]	2563	<a href="#psr">psr</a>, <a href="#psn">psn</a>,
	2564	<a href="#pss">pss</a>, <a href="#psb">psb</a>,
	2565	<a href="#pst">pst</a>, <a href="#pdx">pdx</a>,
	2566	<a href="#pdy">pdy</a>,
[5]	2567	and<a href="#pdz">
[48]	2568	pdz</a>. With <b>random_start_position</b> = <i>.T.
	2569	</i>the initial
[5]	2570	positions of the particles are allowed to randomly vary from these
[48]	2571	positions within certain limits.  </p> <p><b>Very
	2572	important:<br> </b>In case of <b>random_start_position</b>
	2573	= <i>.T.</i>, the
[5]	2574	random-number generators on the individual PEs no longer
	2575	run synchronously. If random disturbances are applied to the velocity
	2576	field
[48]	2577	(see <a href="#create_disturbances">create_disturbances</a>),
	2578	<font color="#000000">then as consequence for parallel
	2579	runs the
[5]	2580	realizations of the turbulent flow
	2581	fields will deviate between runs which used different numbers of PEs!</font></p>
[48]	2582	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="read_particles_from_restartfile"></a><b>read_particles_from_</b>
	2583	<br> <b>restartfile</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td>
	2584	<td style="vertical-align: top;"> <p>Read particle
	2585	data from the previous run.  </p> <p>By default,
	2586	with restart runs particle data is read
[5]	2587	from file <a href="chapter_3.4.html#PARTICLE_RESTART_DATA_IN">PARTICLE_RESTART_DATA_IN</a>,
	2588	which is created by the preceding run. If this is not requested or if
	2589	in a restart run particle transport is switched on for the
	2590	first time (see <a href="#particle_advection_start">particle_advection_start</a>),
	2591	then <b>read_particles_from_restartfile</b> = <i>.F.</i>
[48]	2592	is required.</p> </td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_particles_for_tail"></a><span style="font-weight: bold;">skip_particles_for_tail</span><br>
	2593	</td> <td style="vertical-align: top;">I<br> </td>
	2594	<td style="vertical-align: top;"><span style="font-style: italic;">1</span><br> </td>
	2595	<td style="vertical-align: top;">Limit the number of
	2596	particle tails.<br> <br>
	2597	If particle tails are switched on (see <a href="#use_particle_tails">use_particle_tails</a>),
	2598	every particle is given a tail by default. <span style="font-weight: bold;">skip_particles_for_tail </span>can
	2599	be used to give only every n'th particle a tail.<br> <br> <span style="font-weight: bold;">Example:</span><br> <span style="font-weight: bold;">skip_particles_for_tail</span>
	2600	= <span style="font-style: italic;">10</span> means
	2601	that only every 10th particle will be given a tail.<br> </td>
	2602	</tr> <tr> <td style="vertical-align: top;"><a name="use_particle_tails"></a><span style="font-weight: bold;">use_particle_tails</span><br>
	2603	</td> <td style="vertical-align: top;">L<br> </td>
	2604	<td style="vertical-align: top;"><span style="font-style: italic;">.F.</span><br> </td>
	2605	<td style="vertical-align: top;">Give particles a tail.<br>
[61]	2606	<br>A particle tail is defined by the path a particle has moved
[5]	2607	along starting from some point of time in the past. It consists of a
	2608	set of descrete points in space which may e.g. be connected by a line
[48]	2609	in order visualize how the particle has moved.<br> <br>
	2610	By default, particles have no tail. Parameter <a href="#skip_particles_for_tail">skip_particles_for_tail</a>
	2611	can be used to give only every n'th particle a tail.<br> <br>
	2612	The length of the tail is controlled by parameters <a href="#maximum_number_of_tailpoints">maximum_number_of_tailpoints</a>, <a href="#maximum_tailpoint_age">maximum_tailpoint_age</a>,
	2613	and <a href="#minimum_tailpoint_distance">minimum_tailpoint_distance</a>.<br>
[61]	2614	</td> </tr><tr><td align="left" valign="top"><a name="use_sgs_for_particles"></a><span style="font-weight: bold;">use_sgs_for_particles</span></td><td align="left" valign="top">L</td><td align="left" valign="top"><span style="font-style: italic;">.F.</span></td><td align="left" valign="top">Use subgrid-scale
[48]	2615	velocities for particle advection.<br><br>These
[5]	2616	velocities are calculated from the resolved and subgrid-scale TKE using
	2617	the Monte-Carlo random-walk method described by Weil et al. (2004, JAS,
	2618	61,
	2619	2877-2887). When using this method, the timestep for the advancement of
	2620	the particles is limited by the so-called Lagrangian time scale. This
	2621	may be smaller than the current LES timestep so that several particle
	2622	(sub-) timesteps have to be carried out within one LES timestep. In
	2623	order to limit the number of sub-timesteps (and to limit the CPU-time),
	2624	the minimum value for the particle timestep is defined by the package
[48]	2625	parameter <a href="#dt_min_part">dt_min_part</a>.<br><br>Setting
	2626	<span style="font-weight: bold;">use_sgs_for_particles</span>
	2627	= <span style="font-style: italic;">.TRUE.</span>
	2628	automatically forces <a href="chapter_4.1.html#use_upstream_for_tke">use_upstream_for_tke</a>
	2629	= <span style="font-style: italic;">.TRUE.</span>.
[5]	2630	This inhibits the occurrence of large (artificial) spatial gradients of
	2631	the subgrid-scale TKE which otherwise would lead to wrong results for
[48]	2632	the particle advection.</td></tr><tr> <td style="vertical-align: top;"> <p><a name="vertical_particle_advection"></a><b>vertical_particle_</b>
	2633	<br> <b>advection</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.T.</i> </td>
	2634	<td style="vertical-align: top;"> <p>Switch on/off
	2635	vertical particle transport. </p> <p>By default,
	2636	particles are transported along all three
	2637	directions in space. With <b>vertical_particle_advection</b>
	2638	= <i>.F., </i>the
	2639	particles will only be transported horizontally.</p> </td>
[61]	2640	</tr> <tr> <td style="vertical-align: top;"><p><a name="write_particle_statistics"></a><b>write_particle_</b>
[48]	2641	<br> <b>statistics</b></p> </td> <td style="vertical-align: top;">L<br> </td> <td style="vertical-align: top;"><i>.F.</i> </td>
	2642	<td style="vertical-align: top;"> <p>Switch on/off
	2643	output of particle informations.<br> </p> <p><br>
[5]	2644	For <span style="font-weight: bold;">write_particle_statistics</span>
	2645	= <span style="font-style: italic;">.T.</span> s<span style="font-family: thorndale,serif;">tatistical
	2646	informations</span> (e.g. the total number of particles used, the
	2647	number of particles exchanged between the PEs, etc.) which may be used
	2648	for debugging are output to the
	2649	local file <a href="chapter_3.4.html#PARTICLE_DATA">PARTICLE_INFOS</a>.
[48]	2650	</p> <p><b>Note:</b> For parallel runs files
	2651	may become very large
	2652	and performance of PALM may decrease.</p> </td> </tr>
[61]	2653	</tbody></table><span style="font-weight: bold;"><br>
[102]	2654	</span><br><h3 style="line-height: 100%;"><a name="Paketparameter"></a>Package
	2655	parameters: </h3><br><span style="font-weight: bold;">Package
[48]	2656	(<span style="font-weight: bold;">mrun</span> option
	2657	-p): <span style="font-weight: bold;"><a name="dvrp_graphics"></a>dvrp_graphics</span>
[5]	2658
	2659	NAMELIST group name: <span style="font-weight: bold;">dvrp_graphics_par<br>
[61]	2660	<br></span></span><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr>
[48]	2661	<td style="vertical-align: top;"><font size="4"><b>Parameter
	2662	name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
	2663	<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
	2664	<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
[61]	2665	</tr> <tr> <td style="vertical-align: top;"><p><a name="dt_dvrp"></a><b>dt_dvrp</b></p>
[48]	2666	</td> <td style="vertical-align: top;">R</td>
	2667	<td style="vertical-align: top;"><i>9999999.9</i></td>
	2668	<td style="vertical-align: top;"> <p>Temporal
	2669	interval of scenes to be displayed with the <span style="font-weight: bold;">dvrp</span> software (in
	2670	s).  </p> <p>Isosurfaces, cross sections and
	2671	particles can be displayed
[5]	2672	simultaneous. The display of particles requires that the particle
	2673	transport is switched on (see <a href="#dt_prel">dt_prel</a>).
[48]	2674	Objects to be displayed have to be determined with <a href="#mode_dvrp">mode_dvrp</a>. </p> <p>If
	2675	output of scenes created by dvrp software is switched on
[5]	2676	(see <a href="#mode_dvrp">mode_dvrp</a>),
	2677	this parameter can be used to assign the temporal interval at which
[48]	2678	scenes are to be created (and the respective  graphical data
	2679	is to
[5]	2680	be output to the streaming server). <span lang="en-GB"><font face="Thorndale">Reference time is the beginning of
	2681	the simulation, i.e. output takes place at times t = <b>dt_dvrp</b>,
[48]	2682	2<b>dt_dvrp</b>, 3<b>dt_dvrp</b>, etc. The
	2683	actual output times can
	2684	deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).
	2685	Is <b>dt_dvrp</b> < </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then
	2686	scenes are created and
[5]	2687	output after each time step (if this is requested it should be <b>dt_dvrp</b>
[48]	2688	= <i>0</i>).</font></span> </p> </td>
[61]	2689	</tr> <tr> <td style="vertical-align: top;"><p><a name="dvrp_directory"></a><b>dvrp_directory</b></p>
[48]	2690	</td> <td style="vertical-align: top;">C*80</td>
	2691	<td style="vertical-align: top;"><i>'default'</i></td>
	2692	<td style="vertical-align: top;"> <p>Name of the
	2693	directory into which data created by the <span style="font-weight: bold;">dvrp</span>
	2694	software shall be saved.  </p> <p>By default,
	2695	the directory name is generated from the user
[5]	2696	name
	2697	(see package parameter <a href="#dvrp_username">dvrp_username</a>)
[48]	2698	and the base file name (given as the argument of <span style="font-weight: bold;">mrun</span> option -d) as <span style="font-style: italic;">'<user
	2699	name>/<base file name>'</span>.</p> </td>
[61]	2700	</tr> <tr> <td style="vertical-align: top;"><p><a name="dvrp_file"></a><b>dvrp_file</b></p>
[48]	2701	</td> <td style="vertical-align: top;">C*80</td>
	2702	<td style="vertical-align: top;"><i>'default'</i></td>
	2703	<td style="vertical-align: top;"> <p>Name of the
	2704	file into which data created by the <span style="font-weight: bold;">dvrp</span>
	2705	software shall be output.  </p> <p>This
	2706	parameter can be given a value only in case of <a href="#dvrp_output">dvrp_output</a>
	2707	= <span style="font-style: italic;">'local'</span><i>
	2708	</i>which
[5]	2709	determines that the data created by <span style="font-weight: bold;">dvrp</span>
	2710	is output to a local file (on the machine where PALM is executed).
	2711	Apart from the default, it is only allowed to assign <span style="font-style: italic;">'/dev/null'</span> (which
	2712	means that no output is really stored). This can be used for special
	2713	runtime measurements of the <span style="font-weight: bold;">dvrp</span>
[48]	2714	software.</p> </td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_host"></a><b>dvrp_host</b></p>
	2715	</td> <td style="vertical-align: top;">C*80</td>
	2716	<td style="vertical-align: top;"> <p><i>'origin.rvs.</i>
[61]	2717	<br>u<i>ni- hanover.de'</i></p> </td> <td style="vertical-align: top;"> <p>Name of the computer
[48]	2718	to which data created by the <span style="font-weight: bold;">dvrp</span>
	2719	software shall be
	2720	transferred.  </p> <p>In case of <a href="#dvrp_output">dvrp_output</a>
	2721	= <span style="font-style: italic;">'rtsp'</span>
	2722	only the default
[5]	2723	value is allowed (streaming server of
	2724	the RRZN). For <a href="#dvrp_output">dvrp_output</a>
[48]	2725	= <span style="font-style: italic;">'local'</span><i>
	2726	</i>the
	2727	assigned value is ignored.</p> </td> </tr> <tr>
	2728	<td style="vertical-align: top;"> <p><a name="dvrp_output"></a><b>dvrp_output</b></p>
	2729	</td> <td style="vertical-align: top;">C*10</td>
	2730	<td style="vertical-align: top;"><i>'rtsp'</i></td>
	2731	<td style="vertical-align: top;"> <p>Output mode
	2732	for the <span style="font-weight: bold;">dvrp</span>
	2733	software. <br> <br> </p>
	2734	The following settings are allowed:<br> <br> <table style="text-align: left; width: 100%;" cellpadding="2" cellspacing="2"> <tbody> <tr> <td style="vertical-align: top;"><i>'rtsp'</i></td>
	2735	<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
[5]	2736	software is transferred using
	2737	a special transmission protocol to a so-called streaming server, which
	2738	is able to continuously transfer visualization data with a
	2739	high transmission rate.  <br>
	2740	Additionally, with this output mode a
	2741	set of files is generated automatically
	2742	within a directory on the streaming server (beside the visualization
	2743	data e.g. some html-files) which can be used to
	2744	visualize the data via an internet-browser plugin. Host
	2745	(streaming-server) and directory can be defined by the user with <a href="#dvrp_host">dvrp_host</a>
	2746	and <a href="#dvrp_directory">dvrp_directory</a>.</td>
[48]	2747	</tr> <tr> <td style="vertical-align: top;"><i>'ftp'</i></td>
	2748	<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
[5]	2749	software is transferred to the destination host (see <a href="#dvrp_host">dvrp_host</a>
	2750	and <a href="#dvrp_directory">dvrp_directory</a>)
[48]	2751	using ftp.</td> </tr> <tr> <td style="vertical-align: top;"><i>'local'</i></td>
	2752	<td style="vertical-align: top;">Data created by the <span style="font-weight: bold;">dvrp</span>
[5]	2753	software is output locally on a file defined by <a href="#dvrp_file">dvrp_file
[48]	2754	</a>.</td> </tr> </tbody> </table> <br>
	2755	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="dvrp_password"></a><b>dvrp_password</b></p>
	2756	</td> <td style="vertical-align: top;">C*80</td>
	2757	<td style="vertical-align: top;">'********'</td> <td style="vertical-align: top;"> <p>Password for the
	2758	computer to which data created by the <span style="font-weight: bold;">dvrp</span> software is to
	2759	be
	2760	transferred.  </p> <p>Assigning a password is
	2761	only necessary in case of <a href="#dvrp_output">dvrp_output</a>
	2762	= <span style="font-style: italic;">'ftp'</span>.
	2763	For <a href="#dvrp_output">dvrp_output</a>
	2764	= <span style="font-style: italic;">'rtsp'</span><i>
	2765	</i>the default
	2766	value must not be changed!</p> </td> </tr> <tr>
	2767	<td style="vertical-align: top;"> <p><a name="dvrp_username"></a><b>dvrp_username</b></p>
	2768	</td> <td style="vertical-align: top;">C*80</td>
	2769	<td style="vertical-align: top;"><br> </td> <td style="vertical-align: top;"> <p>User name of a valid
	2770	account on the computer to which data
	2771	created by the <span style="font-weight: bold;">dvrp</span>
	2772	software
[5]	2773	is to be
[48]	2774	transferred.  </p> <p>Assigning a value to this
	2775	parameter is required in case of <a href="#dvrp_output">dvrp_output</a>
	2776	= <span style="font-style: italic;">'rtsp'</span>
	2777	or <span style="font-style: italic;">'ftp'</span>.</p>
	2778	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="mode_dvrp"></a><b>mode_dvrp</b></p>
	2779	</td> <td style="vertical-align: top;">C*20
	2780	<br>(10)</td> <td style="vertical-align: top;"><i>10
	2781	* ''</i></td> <td style="vertical-align: top;">
	2782	<p>Graphical objects (isosurfaces, slicers, particles) which are
[5]	2783	to be created by the <span style="font-weight: bold;">dvrp</span>
[48]	2784	software.  </p> <p>Several different objects can
	2785	be assigned simultaneously and
[5]	2786	will be displayed in the same scene. Allowed values for <span style="font-weight: bold;">mode_dvrp</span> are <span style="font-style: italic;">'isosurface#'</span>
	2787	(isosurface), <span style="font-style: italic;">'slicer#'</span>
	2788	(cross sections), and <span style="font-style: italic;">'particles'</span>.
	2789	Within the strings the hash character ("#") has to be replaced by a
	2790	digit ≤9. Up to 10 objects
[48]	2791	can be assigned at the same time, e.g. :  </p> <blockquote><b>mode_dvrp</b>
	2792	= <span style="font-style: italic;">'isosurface2'</span><i>,
[5]	2793	'slicer1',
[48]	2794	'particles', 'slicer2'</i></blockquote> <p>In this
	2795	case one isosurface, two cross sections, and particles
[5]	2796	will be created. The quantities for which an isosurface are to be
	2797	created have to be selected with
	2798	the parameter <a href="#data_output">data_output</a>,
	2799	those for cross sections with <a href="#data_output">data_output</a>
[48]	2800	(<span style="font-weight: bold;">data_output</span>
	2801	also determines the
	2802	orientation of the cross section, thus xy, xz, or yz). Since for <span style="font-weight: bold;">data_output</span> and <span style="font-weight: bold;">data_output</span> lists of
	2803	variables may be
[5]	2804	assigned, the digit at the end of the <span style="font-weight: bold;">mode_dvrp</span>-string
	2805	selects the quantity, which is given
[48]	2806	at the respective position in the respective list (e.g. <span style="font-style: italic;">'isosurface2'</span>
	2807	selects the quantity
[5]	2808	given in the second position of <span style="font-weight: bold;">data_output</span>).
[48]	2809	If e.g. <span style="font-weight: bold;">data_output</span>
	2810	and <span style="font-weight: bold;">data_output</span>
	2811	are assigned as <b>data_output</b> = <span style="font-style: italic;">'u_xy'</span><i>,
[5]	2812	'w_xz', 'v_yz'</i> and <b>data_output</b> = <span style="font-style: italic;">'pt'</span><i>,
	2813	'u', 'w' </i>are
[48]	2814	indicated, then - assuming the above assignment of <span style="font-weight: bold;">mode_dvrp</span> - an
	2815	isosurface of u, a
[5]	2816	horizontal cross section of u and
	2817	a vertical cross section (xz) of w is created. For locations of the
	2818	cross sections see <a href="#data_output">data_output</a>.
	2819	The theshold value for which the isosurface is
	2820	to be created can be defined with parameter <a href="#threshold">threshold</a>.<br>
[48]	2821	</p> <p>The vertical extension of the displayed domain is
	2822	given by <a href="#nz_do3d">nz_do3d</a>.<br> </p>
	2823	<p>The vertical extension of the displayed domain is given by <a href="#nz_do3d">nz_do3d</a>. </p> <p><b>Assignments
	2824	of mode_dvrp must correspond to those of data_output
[5]	2825	and
	2826	data_output! </b>If e.g. <b>data_output</b> = <span style="font-style: italic;">'pt_xy'</span>
	2827	and <b>data_output</b>
[48]	2828	= 'w'<i> </i>was set, then only the digit "1" is allowed
	2829	for <b>mode_dvrp</b>,
	2830	thus <span style="font-style: italic;">'isosurface1'</span>
	2831	and/or <span style="font-style: italic;">'slicer1'</span><i>.</i>
	2832	</p> <p>Further details about using the <span style="font-weight: bold;">dvrp</span> software are
	2833	given in <a href="chapter_4.5.7.html">chapter
	2834	4.5.7</a>.<br> </p> <b>Note:</b><br>
[5]	2835	The declaration color charts to be
[48]	2836	used still have to be given "manually" in subroutine <span style="font-family: monospace;">user_dvrp_coltab</span>
	2837	(file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>).
	2838	<br>A change of particle colors and/or particle diameters (e.g.
	2839	according
[5]	2840	to the local characteristics of the flow field) to be used for the
	2841	visualization, must be carried out by adding respective code extensions
	2842	to <tt><font style="font-size: 11pt;" size="2">user_particle_attributes</font></tt>
	2843	(in file <tt><font style="font-size: 11pt;" size="2">user_interface.f90</font></tt>). </td>
[48]	2844	</tr> <tr> <td style="vertical-align: top;"><a name="slicer_range_limits_dvrp"></a><span style="font-weight: bold;">slicer_range_limits_<br>
	2845	dvrp</span></td> <td style="vertical-align: top;">R(2,10)</td>
	2846	<td style="vertical-align: top;"><span style="font-style: italic;">10
	2847	* (-1,1)</span></td> <td style="vertical-align: top;">Ranges
[5]	2848	of values to which a color table has to be mapped (units of the
[48]	2849	respective quantity).<br> <br>
[5]	2850	In case that slicers have to be displayed (see <a href="#threshold">mode_dvrp</a>),
	2851	this parameter defines the ranges of values of the respective
	2852	quantities to which the colortable in use has to be mapped. If e.g. a
	2853	temperature slice shall be displayed, the colortable defines colors
	2854	from blue to red, and <span style="font-weight: bold;">slicer_range_limits_dvrp</span>
	2855	= 290.0, 305.0 then areas with temperature of 290 K are displayed in
	2856	dark blue and those with 305.0 are displayed in dark red. Temperatures
	2857	within these limits will be displayed by a continuous color gradient
	2858	from blue to red and Temperatures outside the limits will
[48]	2859	be displayed either in dark blue or in dark red.<br> <br>
[5]	2860	Up to ten different ranges can be assigned in case that more than one
[48]	2861	slicer has to be displayed.<br> <br>
[5]	2862	See <a href="#threshold">mode_dvrp</a>
[48]	2863	for the declaration of color charts.</td> </tr> <tr>
	2864	<td style="vertical-align: top;"> <p><a name="superelevation"></a><b>superelevation</b></p>
	2865	</td> <td style="vertical-align: top;">R</td>
	2866	<td style="vertical-align: top;"><i>1.0</i></td>
	2867	<td style="vertical-align: top;"> <p>Superelevation
	2868	factor for the vertical coordinate.  </p> <p>For
	2869	domains with unfavorable ratio between the vertical and
[5]	2870	the horizontal size
	2871	(the vertical size is determined by <a href="#nz_do3d">nz_do3d</a>)
[48]	2872	a <span style="font-weight: bold;">superelevation</span>
	2873	/= <span style="font-style: italic;">1.0</span> may
	2874	be used. If e.g. the
[5]	2875	horizontal size is substantially larger
	2876	than the vertical size, a <span style="font-weight: bold;">superelevation</span>
[48]	2877	much larger than <span style="font-style: italic;">1.0</span>
	2878	should
[5]	2879	be used, since otherwise the domain appears as a
	2880	"flat disk" in the visualization and thus the vertical direction is
[48]	2881	only very poorly resolved.</p> </td> </tr> <tr>
	2882	<td style="vertical-align: top;"> <p><a name="superelevation_x"></a><b>superelevation_x</b></p>
	2883	</td> <td style="vertical-align: top;">R<br> </td>
	2884	<td style="vertical-align: top; font-style: italic;">1.0<br>
	2885	</td> <td style="vertical-align: top;"> <p>Superelevation
	2886	factor for the horizontal (x) coordinate.  </p> <p>This
	2887	parameter can be used to stretch the displayed domain
[5]	2888	along the x-direction. See also <a href="#superelevation">superelevation</a>.</p>
[48]	2889	</td> </tr> <tr> <td style="vertical-align: top;"> <p><a name="superelevation_y"></a><b>superelevation_y</b></p>
	2890	</td> <td style="vertical-align: top;">R<br> </td>
	2891	<td style="vertical-align: top; font-style: italic;">1.0<br>
	2892	</td> <td style="vertical-align: top;">Superelevation
	2893	factor for the
	2894	horizontal (y) coordinate.  <p>This parameter can be
	2895	used to
	2896	stretch the displayed domain along the y-direction. See also <a href="#superelevation">superelevation</a>.</p> </td>
[61]	2897	</tr> <tr> <td style="vertical-align: top;"><p><a name="threshold"></a><b>threshold</b></p>
[48]	2898	</td> <td style="vertical-align: top;">R(10)<br>
	2899	</td> <td style="vertical-align: top; font-style: italic;">0.0<br>
	2900	</td> <td style="vertical-align: top;"> <p>Threshold
	2901	value for which an isosurface is to be created by
	2902	the <span style="font-weight: bold;">dvrp</span>
	2903	software.  </p> <p>If the creation of
	2904	isosurfaces is switched on via
[5]	2905	parameter <a href="#mode_dvrp">mode_dvrp</a>,
	2906	then the respective threshold value for which the isosurface is to be
[48]	2907	created can be assigned via <b>threshold</b>. If several
	2908	isosurfaces
	2909	are given by <b>mode_dvrp</b>, then an individual
	2910	threshold value for
[5]	2911	each isosurface can be assigned. The order of the threshold values
	2912	refers to the order of the isosurfaces given by <b>mode_dvrp</b>.</p>
[61]	2913	</td> </tr> </tbody></table><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
[5]	2914	</span></span><span style="font-weight: bold;"><span style="font-weight: bold;">Package (<span style="font-weight: bold;">mrun</span>
	2915	option -p): <span style="font-weight: bold;"><a name="spectra"></a>spectra</span>
	2916	NAMELIST group name: <span style="font-weight: bold;">spectra_par<br>
[61]	2917	<br></span></span></span><table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr>
[48]	2918	<td style="vertical-align: top;"><font size="4"><b>Parameter
	2919	name</b></font></td> <td style="vertical-align: top;"><font size="4"><b>Type</b></font></td>
	2920	<td style="vertical-align: top;"> <p><b><font size="4">Default</font></b> <br> <b><font size="4">value</font></b></p> </td>
	2921	<td style="vertical-align: top;"><font size="4"><b>Explanation</b></font></td>
[61]	2922	</tr> <tr> <td style="vertical-align: top;"><p><a name="averaging_interval_sp"></a><b>averaging_interval_sp</b></p>
[48]	2923	</td> <td style="vertical-align: top;">R<br> </td>
	2924	<td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#averaging_interval">averaging_<br>
	2925	interval</a></span> </td> <td style="vertical-align: top;"> <p>Averaging interval
	2926	for spectra output to local
	2927	file <font color="#000000"><font color="#000000"><a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>
	2928	</font></font>and/or  <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
	2929	/    <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
	2930	(in s).  </p> <p>If
[5]	2931	this parameter is given a non-zero value, temporally
	2932	averaged spectra data are output. By default, spectra data data are not
	2933	subject to temporal averaging. The interval length is limited by the
[48]	2934	parameter <a href="#dt_dosp">dt_dosp</a>. In any
	2935	case <b>averaging_interval_sp</b> <= <b>dt_dosp
	2936	</b>must
	2937	hold.</p>If an interval is defined, then by default the average
	2938	is calculated
[5]	2939	from the data values of all timesteps lying within this interval. The
	2940	number of time levels entering into the average can be reduced with the
	2941	parameter <a href="chapter_4.2.html#dt_averaging_input_pr">dt_averaging_input_pr</a>.
[48]	2942	<p>If
[5]	2943	an averaging interval can not be completed at the end of a run, it will
	2944	be finished at the beginning of the next restart run. Thus for restart
	2945	runs, averaging intervals do not
[48]	2946	necessarily begin at the beginning of the run.</p></td> </tr>
	2947	<tr> <td style="vertical-align: top;"><b><a name="comp_spectra_level"></a>comp_spectra_level</b></td>
	2948	<td style="vertical-align: top;">I(10)</td> <td style="vertical-align: top;"><i>no level</i></td>
	2949	<td style="vertical-align: top;"> <p>Vertical level
	2950	for which horizontal spectra are to be
	2951	calculated and output (gridpoints).<br> </p> <br>
	2952	Spectra can be calculated for up to ten levels.</td> </tr>
	2953	<tr><td style="vertical-align: top;"><p><a name="data_output_sp"></a><b>data_output_sp</b></p></td><td style="vertical-align: top;">C10 (10)</td><td style="vertical-align: top;"><i>10 ' '</i></td><td style="vertical-align: top;"><p>Quantities for which
	2954	horizontal spectra are to be calculated
	2955	and output.</p> <p>Allowed values are:  <b>data_output_sp</b>
	2956	= <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>, <span style="font-style: italic;">'w'</span>, <span style="font-style: italic;">'pt'</span>, <span style="font-style: italic;">'q'</span>.<br> </p>
	2957	<p>Spectra are calculated using the FFT-method defined by <a href="chapter_4.1.html#fft_method">fft_method</a>.</p>
	2958	<p>By default spectra data are output to the local file <a href="chapter_3.4.html#DATA_1D_SP_NETCDF">DATA_1D_SP_NETCDF</a>.
	2959	The file's format is NetCDF.  Further details about processing
	2960	NetCDF data are given in chapter <a href="chapter_4.5.1.html">4.5.1</a>.</p><p>The
	2961	temporal interval of the output times of profiles is
	2962	assigned via the parameter <a href="chapter_4.2.html#dt_dosp">dt_dosp</a>. </p><p>The
	2963	vertical levels for which spectra are to be computed and output must be
	2964	given by parameter <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.
	2965	</p><span style="font-weight: bold;">Note:</span><br>
	2966	Beside <span style="font-weight: bold;">data_output_sp</span>,
	2967	values <span style="font-weight: bold;">must</span>
	2968	be given for each of the
[5]	2969	parameters,  <font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>,
	2970	and <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a></font>,
[48]	2971	otherwise <span style="font-weight: bold;">no</span>
	2972	output will be
[5]	2973	created!<br><br><br>
	2974	Calculation of spectra requires cyclic boundary conditions
	2975	along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
[48]	2976	and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).For
	2977	historical reasons, data can also be output in ASCII-format on local
	2978	files <a href="chapter_3.4.html#PLOTSP_X_DATA">PLOTSP_X_DATA</a>
	2979	and/or <a href="chapter_3.4.html#PLOTSP_Y_DATA">PLOTSP_Y_DATA</a>
	2980	(depending on the direction(s) along which spectra are to be
	2981	calculated; see <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"><font face="Thorndale">spectra_direction</font></span></a>),</font>
	2982	which are readable by the graphic software <span style="font-weight: bold;">profil</span>. See
	2983	parameter <a href="chapter_4.2.html#data_output_format">data_output_format</a>
	2984	for defining the format in which data shall be output. Within
	2985	these file, the spectra are ordered with respect to their
[5]	2986	output times. Spectra can also be temporally averaged (see <a href="chapter_4.2.html#averaging_interval_sp">averaging_interval_sp</a>
[48]	2987	). <font><a href="chapter_4.2.html#spectra_direction"><span lang="en-GB"></span></a>Each data point of a
	2988	spectrum is output in a single line (1st column:
[5]	2989	wavenumber, 2nd column: spectral coefficient). If spectra are to be
	2990	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>),
	2991	the spectral coefficients for the further heighs can be found in the
	2992	subsequent columns. </font>The order
	2993	of the data in the file follows the order used in the assignment for <b>data_output_sp</b>
	2994	(<b>data_output_sp</b> = <span style="font-style: italic;">'u'</span>, <span style="font-style: italic;">'v'</span>,…
	2995	means that the file starts with the spectra of the u-component,
[48]	2996	followed by the v-component spectra, etc.). Additional to the files
	2997	PLOTSP_X_DATA and PLOTSP_Y_DATA which contain
[5]	2998	the data,
	2999	PALM creates NAMELIST parameter files (local name <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_X_PAR</a>
	3000	and <a href="chapter_3.4.html#PLOTSP_X_PAR">PLOTSP_Y_PAR</a>)
	3001	which can be used as parameter input file for the plot software <a href="http://www.muk.uni-hannover.de/institut/software/profil_intro.html">profil</a>.
	3002	Spectra can be directly plotted with <span style="font-weight: bold;">profil</span>
	3003	using the data and the corresponding parameter file. The
	3004	plot layout is
	3005	steered via the parameter input file. The vertical levels for which
[48]	3006	spectra are to be plotted must be given by <font><a href="chapter_4.2.html#plot_spectra_level"><span lang="en-GB"><font face="Thorndale">plot_spectra_level</font></span></a></font><font><a href="chapter_4.2.html#comp_spectra_level"><span lang="en-GB"></span></a></font>. <span style="font-weight: bold;"></span>Otherwise, no
	3007	spectra
[5]	3008	will appear on the plot, although data are available on file. All
	3009	parameter values can be changed by editing the parameter
	3010	input
	3011	file.<span style="font-weight: bold;"><br></span></td></tr><tr>
[48]	3012	<td style="vertical-align: top;"> <p><a name="dt_dosp"></a><b>dt_dosp</b></p>
	3013	</td> <td style="vertical-align: top;">R</td>
	3014	<td style="vertical-align: top;"><i>value of
	3015	<a href="chapter_4.2.html#dt_data_output">dt_data_<br>output</a></i></td>
	3016	<td style="vertical-align: top;"> <p>Temporal
	3017	interval at which spectra data shall be output
	3018	(in s).  </p> <p><span lang="en-GB"><font face="Thorndale">If output of
	3019	horizontal spectra is switched on (see </font></span><a href="#data_output_sp"><span lang="en-GB"><font face="Thorndale">data_output_sp</font></span></a><span lang="en-GB"><font face="Thorndale">), </font></span><span lang="en-GB"><font face="Thorndale">this
	3020	parameter can be used to
[5]	3021	assign the temporal interval at which spectral data  shall be
[48]	3022	output. </font></span><span lang="en-GB"><font face="Thorndale">Output can be skipped at the beginning of a
	3023	simulation using parameter <a href="#skip_time_dosp">skip_time_dosp</a>,
	3024	which has zero value by default. </font></span><span lang="en-GB"></span><span lang="en-GB"><font face="Thorndale">Reference
[5]	3025	time is the beginning of
	3026	the simulation, i.e. output takes place at times t = <span style="font-weight: bold;">skip_time_dosp</span> + <b>dt_dosp</b>,
[48]	3027	<span style="font-weight: bold;">skip_time_dosp</span>
	3028	+ 2<b>dt_dosp</b>, skip_time_dosp + 3<b>dt_dosp</b>,
	3029	etc. The actual output times can
	3030	deviate from these theoretical values (see </font></span><a href="#dt_dopr_zeitpunkte"><span lang="en-GB"><font face="Thorndale">dt_dopr</font></span></a><span lang="en-GB"><font face="Thorndale">).
	3031	If <b>dt_dosp</b> < </font></span><a href="chapter_4.1.html#dt"><span lang="en-GB"><font face="Thorndale">dt</font></span></a><span lang="en-GB"><font face="Thorndale">, then
	3032	spectral data are output
[5]	3033	after each time step (if this is requested it should be <b>dt_dosp</b>
[48]	3034	= <i>0</i>).</font></span> </p> </td>
[61]	3035	</tr> <tr> <td style="vertical-align: top;"><p><a name="plot_spectra_level"></a><b>plot_spectra_level</b></p>
[48]	3036	</td> <td style="vertical-align: top;">I(10)</td>
	3037	<td style="vertical-align: top;"><i>no level</i></td>
	3038	<td style="vertical-align: top;"> <p>Vertical
	3039	level(s) for which horizontal spectra are to be
	3040	plotted (in gridpoints).  </p> <p>This parameter
	3041	only affects the display of spectra in plots
	3042	created with <span style="font-weight: bold;">profil</span>.
	3043	The
[5]	3044	spectral data created and output to file are exclusively determined via
[48]	3045	<font><a href="#comp_spectra_level"><span lang="en-GB"><font face="Thorndale">comp_spectra_level</font></span></a></font>.</p>
	3046	</td> </tr> <tr> <td style="vertical-align: top;"><a name="skip_time_dosp"></a><span style="font-weight: bold;">skip_time_dosp</span></td>
	3047	<td style="vertical-align: top;">R<br> </td> <td style="vertical-align: top;"><span style="font-style: italic;">value of <a href="chapter_4.2.html#skip_time_data_output">skip_time_<br>data_output</a></span>
	3048	</td> <td style="vertical-align: top;">No output of
	3049	spectra data before this interval has passed (in s).<br><br>This
	3050	parameter causes that data output activities are starting not before
	3051	this interval
	3052	(counting from the beginning of the simulation, t=0) has passed. <br><br><span style="font-weight: bold;">Example:</span><br>If
	3053	the user has set <a href="#dt_dosp">dt_dosp</a> = <span style="font-style: italic;">3600.0</span> and <span style="font-weight: bold;">skip_time_dosp</span> = <span style="font-style: italic;">1800.0</span>, then the
	3054	first output will be done at t = 5400 s. </td> </tr>
	3055	<tr> <td style="vertical-align: top;"> <p><a name="spectra_direction"></a><b>spectra_direction</b></p>
	3056	</td> <td style="vertical-align: top;">C*2 (10)</td>
	3057	<td style="vertical-align: top;"><i>10 * ' '</i></td>
	3058	<td style="vertical-align: top;"> <p>Direction(s)
	3059	along which spectra are to be calculated.  </p> <p>Allowed
	3060	values are <span style="font-style: italic;">'x'</span>,
	3061	<span style="font-style: italic;">'y'</span> and <span style="font-style: italic;">'xy'</span>. For
[5]	3062	every quantity given by <a href="#data_output_sp">data_output_sp</a>
	3063	a corresponding
[48]	3064	direction<span style="font-weight: bold;"> </span>must
	3065	be assigned.<br> </p> <p>Calculation of spectra
	3066	requires cyclic boundary conditions
[5]	3067	along the respective directions (see <a href="chapter_4.1.html#bc_lr">bc_lr</a>
	3068	and <a href="chapter_4.1.html#bc_ns">bc_ns</a>).</p>
[61]	3069	</td> </tr> </tbody></table><span style="font-weight: bold;"><span style="font-weight: bold;"><span style="font-weight: bold;"><br>
	3070	</span></span></span><h3 style="line-height: 100%;"><br><a href="chapter_4.1.html"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></a><a href="index.html"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></a><a href="chapter_4.3.html"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></a></h3><span style="font-style: italic;">Last change:</span>
	3071	$Id: chapter_4.2.html 103 2007-07-30 10:49:46Z raasch $ <span style="font-weight: bold;"><span style="font-weight: bold;"><br>
	3072	</span></span><br></body></html>

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

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |