Home

Context Navigation

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

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

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

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |