Home

Context Navigation

source: palm/trunk/DOC/app/chapter_4.0.html @ 2689

Last change on this file since 2689 was 108, checked in by letzel, 17 years ago

Improved coupler: evaporation - salinity-flux coupling for humidity = .T.,

avoid MPI hangs when coupled runs terminate, add DOC/app/chapter_3.8;

Optional calculation of km and kh from initial TKE e_init;
Default initialization of km,kh = 0.00001 for ocean = .T.;
Allow data_output_pr= q, wq, w"q", w*q* for humidity = .T.;
Bugfix: Rayleigh damping for ocean fixed.

Property svn:keywords set to Id

File size: 8.4 KB

Rev	Line
[5]	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
[108]	2	<html>
	3	<head>
	4
	5
	6
	7	<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252">
	8
	9
	10
	11
	12	<title>PALM chapter 4.0</title>
	13	<meta name="GENERATOR" content="StarOffice 7 (Win32)">
	14
	15
	16
	17	<meta name="AUTHOR" content="Siegfried Raasch">
	18
	19
	20
	21	<meta name="CREATED" content="20040809;14214479">
	22
	23
	24
	25	<meta name="CHANGED" content="20041112;15151993">
	26
	27
	28
	29	<meta name="KEYWORDS" content="parallel LES model">
	30
	31
	32
	33	<style>
[62]	34	<!--
	35	@page { size: 21cm 29.7cm }
	36	-->
[108]	37	</style>
	38	</head>
	39
	40
	41	<body style="direction: ltr;" lang="en-US">
	42
	43	<h2 style="line-height: 100%;"><font size="4">4.0
[62]	44	Steering parameters</font></h2>
[108]	45
	46
[62]	47	<p style="line-height: 100%;">Before carrying out a model
	48	run, the user
[5]	49	has to /determine/ a data set - the model parameters - e.g. how
	50	many grid points are to be used, how large the horizontal and
	51	vertical grid spacing should be, which kind of boundary conditions are
	52	to be used for the individual variables, which numerical schemes
	53	implemented in the model are to be used, how long the simulated time
	54	should be, at which times and points plot output are supposed to be
	55	made, etc. <br>
[108]	56
	57
	58	</p>
	59
	60	<p style="line-height: 100%;">These data are
[62]	61	assigned with the help of
[83]	62	so-called “NAMELIST-driven input” (FORTRAN -
[62]	63	NAMELIST –
[83]	64	input). The chosen values of the model parameters are
[62]	65	written
[5]	66	into an ASCII file with fixed format, which is expected by the model as
	67	an input
	68	file under the local name <a href="chapter_3.4.html#PARIN">PARIN</a>.
	69	On this file the parameters are represented by their variable names
	70	they have in the model. These parameters can be assigned one or more
	71	values, depending on the type and size the variable has. The following
	72	example shows the format of the file
	73	PARIN: <br>
[108]	74
	75
[5]	76	</p>
[108]	77
	78
	79	<ul>
	80
	81
	82
	83	<p style="line-height: 100%; font-family: monospace;">&inipar
[62]	84	nx
[5]	85	= 79, ny = 79, nz = 40, <br>
[108]	86
	87
[62]	88
	89	dx = 50.0, dy = 50.0, dz =
[5]	90	50.0, <br>
[108]	91
	92
[62]	93
	94	initializing_actions =
[5]	95	"set_1d-model_profiles", <br>
[108]	96
	97
[62]	98
[108]	99	prandtl_layer = .TRUE.,/ </p>
	100
	101
	102
	103	<p style="line-height: 100%; font-family: monospace;">&d3par
	104	end_time = 9000.0, section_xy = 1, 10, 20,/ </p>
	105
	106
	107
	108	<p style="line-height: 100%; font-family: monospace;">&packagename
	109	var1 = .TRUE. / </p>
	110
	111
	112
	113	<p style="line-height: 100%;"><span style="font-family: monospace;">&userpar
[5]	114	abcd = 1234,0,/ </span><br>
[108]	115
	116
[5]	117	<br>
[108]	118
	119
[5]	120	</p>
[108]	121
	122
	123	</ul>
	124
	125	<p style="line-height: 100%;">The parameters
[62]	126	are separated into four
[5]	127	different groups which all start with the so-called NAMELIST group
	128	names.
[62]	129	These are <span style="font-family: monospace;">&inipar</span>,
	130	<span style="font-family: monospace;">&d3par</span>
	131	and <span style="font-family: monospace;">&packagename</span>
	132	as well as <span style="font-family: monospace;">&userpar</span>.
	133	In each case a
[5]	134	group is terminated with one backslash ("/"). Between the beginning of
	135	the line and the group name at least one blank has to be typed. Between
	136	the
	137	group names and the "/", the
	138	values are assigned to the variables. The example shows that in
	139	principle all FORTRAN data types are allowed. For more details
	140	concerning the NAMELIST syntax, refer to
	141	appropriate FORTRAN manuals. <br>
[108]	142
	143
	144	</p>
	145
	146	<p style="line-height: 100%;">Parameters
[62]	147	belonging to the group <span style="font-family: monospace;">inipar</span>
	148	are first read by PALM.
[5]	149	These are the initialization parameters. Second, the so-called run
	150	parameters belonging to the group <span style="font-family: monospace;">d3par</span>
	151	are read in, then the parameters for steering the optional software
	152	packages (group <span style="font-family: monospace;">packagename,</span>
	153	the string <span style="font-family: monospace;">"packagename"</span>
	154	must be replaced by the NAMELIST
	155	group name of the respective package) as well as user-defined
	156	parameters
[62]	157	(group <span style="font-family: monospace;">userpar</span>).
	158	The four
	159	groups must be given in this order, the last groups, <span style="font-family: monospace;">packagename</span> and
	160	<span style="font-family: monospace;">userpar</span>,
	161	may
[5]	162	be omitted. If several software packages are selected
	163	(see chapter <a href="chapter_3.7.html">3.7</a>),
[62]	164	further NAMELIST groups may be inserted before the group <span style="font-family: monospace;">userpar</span>.
[108]	165	</p>
	166
	167	<p style="line-height: 100%;"><b>The
[62]	168	initialization, run</b> and
[5]	169	<b>package parameters</b> differ as follows: </p>
[108]	170
	171
	172	<ul>
	173
	174	<li>
	175
	176	<p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
[62]	177	parameters </b>are steering the basic settings of the model run.
	178	They
[5]	179	define e.g. the number of the grid points, the numerical schemes to be
	180	used, initial and boundary conditions to be applied, how the
	181	three-dimensional fields are initialized at the beginning of a model
	182	run (constant  value profiles or 1D-model-pre-run, the initial
	183	temperature profile etc.). These parameters apply to the total model
	184	run and thus can not be changed with restart runs! If one tries to
	185	change these values within the NAMELIST input file of a restart run,
[62]	186	then these changes are ignored (sole exception is the parameter <a style="font-family: monospace;" href="chapter_4.1.html#initializing_actions">initializing_actions</a><font style="font-size: 10pt;" size="2">, </font>which
	187	must be given the
	188	value<span style="font-family: thorndale,serif,mon;"> </span><span style="font-family: monospace; font-style: italic;">read_restart_data</span><span style="font-family: thorndale,serif,mon;"> for </span>restart
	189	runs). <br>
[108]	190
	191
	192	</p>
	193
	194	</li>
	195
	196	<li>
	197
	198	<p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
[62]	199	parameters</b> are generally steering actions to be carried out
	200	during
[5]	201	a model run. One can select for example, at which times plot output
	202	should happen and which variables are to be written. Additionally one
	203	can (and must) specify the time to be simulated. Run parameters only
	204	apply to the actual run (job) and with each restart run other values
	205	may be declared (if runs are restarted automatically, parameters will
	206	usually keep their values, provided that the NAMELIST input file was
	207	not changed by the user in the meantime). <br>
[108]	208
	209
	210	</p>
	211
	212	</li>
	213
	214	<li>
	215
	216	<p style="line-height: 100%;"><b>Package parameters</b>
[62]	217	behave like <b>run parameters</b>. Package parameters
	218	determine the behavior of
[108]	219	the additional (not user-defined) software packages . </p>
	220
	221	</li>
	222
	223
	224	</ul>
	225
	226	<p style="line-height: 100%;">The user-defined
[62]	227	parameters are assigned
	228	by the user within the NAMELIST group name <tt>&userpar</tt>
	229	(see <a href="chapter_3.5.2.html">chapter
	230	3.5.2</a>). They steer actions programmed by the user. By
	231	default,
[5]	232	this group has only one parameter (<a href="chapter_4.3.html#region">region</a>).
	233	If the
	234	user don't want to assign any values to the user-defined
[62]	235	parameters, the group<span style="font-family: monospace;">
	236	userpar
	237	</span>may be omitted. The group name <span style="font-family: monospace;">&userpar</span>
[5]	238	can be changed by the user in the user-defined code. In
	239	addition to this, further NAMELIST groups may also be declared (all
	240	within routine <span style="font-family: monospace;">user_parin</span>
	241	in file <span style="font-family: monospace;">user_interface.f90</span>).
[97]	242	<a href="chapter_4.4.1.html">Chapter
	243	4.4.1</a> shows a simple but complete example of the input file
[62]	244	PARIN.
[5]	245	This example file can be used together with the configuration file
	246	(described in <a href="chapter_3.2.html">chapter
	247	3.2</a>) for the execution of a model test run. </p>
[108]	248
	249
[5]	250	<p style="line-height: 100%;">PALM assigns default
	251	values to nearly all parameters. They become effective
	252	if no other assignments are given in the parameter file. These
	253	default values as well as the parameter name, type and its
	254	explanation are described in the lists of the following subsections. <br>
[108]	255
	256
[5]	257	</p>
[108]	258
	259
	260	<hr>
	261	<p style="line-height: 100%;"><br>
	262
	263
	264	<font color="#000080"><font color="#000080"><a href="chapter_3.8.html"><font color="#000080"><img style="border: 2px solid ; width: 32px; height: 32px;" alt="" src="left.gif" name="Grafik1"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_4.1.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font><br>
	265
	266
[5]	267	<br>
[108]	268
	269
[62]	270	<span style="font-style: italic;">Last change:</span>
	271	$Id: chapter_4.0.html 108 2007-08-24 15:10:38Z Giersch $<br>
[108]	272
	273
	274	</p>
	275
	276	</body>
	277	</html>

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

Download in other formats:

| Impressum | ©Leibniz Universität Hannover |