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

Last change on this file since 77 was 62, checked in by raasch, 18 years ago

Id string added to all html files

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