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

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



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


mbuild, mrun


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