Home

Context Navigation

chapter_4.0.html @ 89

Last change on this file since 89 was 83, checked in by raasch, 18 years ago

New:
---

Changed:

PALM can be generally installed on any kind of Linux-, IBM-AIX-, or NEC-SX-system by adding appropriate settings to the configuration file.

Scripts are also running under the public domain ksh.

All system relevant compile and link options as well as the host identifier (local_host) are specified in the configuration file.

Filetransfer by ftp removed (options -f removed from mrun and mbuild).

Call of (system-)FLUSH routine moved to new routine local_flush.

return_addres and return_username are read from ENVPAR-NAMELIST-file instead of using local_getenv.

Preprocessor strings for different linux clusters changed to "lc", some preprocessor directives renamed (new: intel_openmp_bug), preprocessor directives for old systems removed

advec_particles, check_open, cpu_log, cpu_statistics, data_output_dvrp, flow_statistics, header, init_dvrp, init_particles, init_1d_model, init_dvrp, init_pegrid, local_getenv, local_system, local_tremain, local_tremain_ini, modules, palm, parin, run_control

new:
local_flush

mbuild, mrun

Errors:

Property svn:keywords set to Id

File size: 8.2 KB

Rev	Line
[5]	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
[62]	2	<html><head>
[83]	3	<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 4.0</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040809;14214479"> <meta name="CHANGED" content="20041112;15151993"> <meta name="KEYWORDS" content="parallel LES model"> <style>
[62]	4	<!--
	5	@page { size: 21cm 29.7cm }
	6	-->
	7	</style></head>
	8	<body style="direction: ltr;" lang="en-US"><h2 style="line-height: 100%;"><font size="4">4.0
	9	Steering parameters</font></h2>
	10	<p style="line-height: 100%;">Before carrying out a model
	11	run, the user
[5]	12	has to /determine/ a data set - the model parameters - e.g. how
	13	many grid points are to be used, how large the horizontal and
	14	vertical grid spacing should be, which kind of boundary conditions are
	15	to be used for the individual variables, which numerical schemes
	16	implemented in the model are to be used, how long the simulated time
	17	should be, at which times and points plot output are supposed to be
	18	made, etc. <br>
[62]	19	</p><p style="line-height: 100%;">These data are
	20	assigned with the help of
[83]	21	so-called “NAMELIST-driven input” (FORTRAN -
[62]	22	NAMELIST –
[83]	23	input). The chosen values of the model parameters are
[62]	24	written
[5]	25	into an ASCII file with fixed format, which is expected by the model as
	26	an input
	27	file under the local name <a href="chapter_3.4.html#PARIN">PARIN</a>.
	28	On this file the parameters are represented by their variable names
	29	they have in the model. These parameters can be assigned one or more
	30	values, depending on the type and size the variable has. The following
	31	example shows the format of the file
	32	PARIN: <br>
	33	</p>
[62]	34	<ul> <p style="line-height: 100%; font-family: monospace;">&inipar
	35	nx
[5]	36	= 79, ny = 79, nz = 40, <br>
[62]	37
	38	dx = 50.0, dy = 50.0, dz =
[5]	39	50.0, <br>
[62]	40
	41	initializing_actions =
[5]	42	"set_1d-model_profiles", <br>
[62]	43
	44	prandtl_layer = .TRUE.,/ </p> <p style="line-height: 100%; font-family: monospace;">&d3par
	45	end_time = 9000.0, section_xy = 1, 10, 20,/ </p> <p style="line-height: 100%; font-family: monospace;">&packagename
	46	var1 = .TRUE. / </p> <p style="line-height: 100%;"><span style="font-family: monospace;">&userpar
[5]	47	abcd = 1234,0,/ </span><br>
	48	<br>
	49	</p>
[62]	50	</ul><p style="line-height: 100%;">The parameters
	51	are separated into four
[5]	52	different groups which all start with the so-called NAMELIST group
	53	names.
[62]	54	These are <span style="font-family: monospace;">&inipar</span>,
	55	<span style="font-family: monospace;">&d3par</span>
	56	and <span style="font-family: monospace;">&packagename</span>
	57	as well as <span style="font-family: monospace;">&userpar</span>.
	58	In each case a
[5]	59	group is terminated with one backslash ("/"). Between the beginning of
	60	the line and the group name at least one blank has to be typed. Between
	61	the
	62	group names and the "/", the
	63	values are assigned to the variables. The example shows that in
	64	principle all FORTRAN data types are allowed. For more details
	65	concerning the NAMELIST syntax, refer to
	66	appropriate FORTRAN manuals. <br>
[62]	67	</p><p style="line-height: 100%;">Parameters
	68	belonging to the group <span style="font-family: monospace;">inipar</span>
	69	are first read by PALM.
[5]	70	These are the initialization parameters. Second, the so-called run
	71	parameters belonging to the group <span style="font-family: monospace;">d3par</span>
	72	are read in, then the parameters for steering the optional software
	73	packages (group <span style="font-family: monospace;">packagename,</span>
	74	the string <span style="font-family: monospace;">"packagename"</span>
	75	must be replaced by the NAMELIST
	76	group name of the respective package) as well as user-defined
	77	parameters
[62]	78	(group <span style="font-family: monospace;">userpar</span>).
	79	The four
	80	groups must be given in this order, the last groups, <span style="font-family: monospace;">packagename</span> and
	81	<span style="font-family: monospace;">userpar</span>,
	82	may
[5]	83	be omitted. If several software packages are selected
	84	(see chapter <a href="chapter_3.7.html">3.7</a>),
[62]	85	further NAMELIST groups may be inserted before the group <span style="font-family: monospace;">userpar</span>.
	86	</p><p style="line-height: 100%;"><b>The
	87	initialization, run</b> and
[5]	88	<b>package parameters</b> differ as follows: </p>
[62]	89	<ul> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
	90	parameters </b>are steering the basic settings of the model run.
	91	They
[5]	92	define e.g. the number of the grid points, the numerical schemes to be
	93	used, initial and boundary conditions to be applied, how the
	94	three-dimensional fields are initialized at the beginning of a model
	95	run (constant  value profiles or 1D-model-pre-run, the initial
	96	temperature profile etc.). These parameters apply to the total model
	97	run and thus can not be changed with restart runs! If one tries to
	98	change these values within the NAMELIST input file of a restart run,
[62]	99	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
	100	must be given the
	101	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
	102	runs). <br>
	103	</p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
	104	parameters</b> are generally steering actions to be carried out
	105	during
[5]	106	a model run. One can select for example, at which times plot output
	107	should happen and which variables are to be written. Additionally one
	108	can (and must) specify the time to be simulated. Run parameters only
	109	apply to the actual run (job) and with each restart run other values
	110	may be declared (if runs are restarted automatically, parameters will
	111	usually keep their values, provided that the NAMELIST input file was
	112	not changed by the user in the meantime). <br>
[62]	113	</p> </li> <li> <p style="line-height: 100%;"><b>Package parameters</b>
	114	behave like <b>run parameters</b>. Package parameters
	115	determine the behavior of
	116	the additional (not user-defined) software packages . </p> </li>
	117	</ul><p style="line-height: 100%;">The user-defined
	118	parameters are assigned
	119	by the user within the NAMELIST group name <tt>&userpar</tt>
	120	(see <a href="chapter_3.5.2.html">chapter
	121	3.5.2</a>). They steer actions programmed by the user. By
	122	default,
[5]	123	this group has only one parameter (<a href="chapter_4.3.html#region">region</a>).
	124	If the
	125	user don't want to assign any values to the user-defined
[62]	126	parameters, the group<span style="font-family: monospace;">
	127	userpar
	128	</span>may be omitted. The group name <span style="font-family: monospace;">&userpar</span>
[5]	129	can be changed by the user in the user-defined code. In
	130	addition to this, further NAMELIST groups may also be declared (all
	131	within routine <span style="font-family: monospace;">user_parin</span>
	132	in file <span style="font-family: monospace;">user_interface.f90</span>).
	133	<a href="chapter_4.4.html">Chapter
[62]	134	4.4</a> shows a simple but complete example of the input file
	135	PARIN.
[5]	136	This example file can be used together with the configuration file
	137	(described in <a href="chapter_3.2.html">chapter
	138	3.2</a>) for the execution of a model test run. </p>
	139	<p style="line-height: 100%;">PALM assigns default
	140	values to nearly all parameters. They become effective
	141	if no other assignments are given in the parameter file. These
	142	default values as well as the parameter name, type and its
	143	explanation are described in the lists of the following subsections. <br>
	144	</p>
[62]	145	<hr><p style="line-height: 100%;"><br>
	146	<font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font color="#000080"><img src="left.gif" name="Grafik1" align="bottom" border="2" height="32" width="32"></font></a><a href="index.html"><font color="#000080"><img src="up.gif" name="Grafik2" align="bottom" border="2" height="32" width="32"></font></a><a href="chapter_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>
[5]	147	<br>
[62]	148	<span style="font-style: italic;">Last change:</span>
	149	$Id: chapter_4.0.html 83 2007-04-19 16:27:07Z raasch $<br>
	150	</p></body></html>

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

Context Navigation

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

Download in other formats: