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

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