Ignore:
Timestamp:
Mar 13, 2007 2:52:40 AM (16 years ago)
Author:
raasch
Message:

Id string added to all html files

File:
1 edited

Legend:

Unmodified
Added
Removed
  • palm/trunk/DOC/app/chapter_4.0.html

    r54 r62  
    11<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    2 <html>
    3 <head>
    4   <meta http-equiv="CONTENT-TYPE"
    5  content="text/html; charset=windows-1252">
    6   <title>PALM chapter 4.0</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20040809;14214479">
    10   <meta name="CHANGED" content="20041112;15151993">
    11   <meta name="KEYWORDS" content="parallel LES model">
    12   <style>
    13         <!--
    14                 @page { size: 21cm 29.7cm }
    15         -->
    16         </style>
    17 </head>
    18 <body dir="ltr" lang="en-US">
    19 <h2 style="line-height: 100%;"><font size="4">4.0 Steering parameters</font></h2>
    20 <p style="line-height: 100%;">Before carrying out a model run, the user
     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
    2114has to /determine/ a data set - the model parameters - e.g. how
    2215many grid points are to be used, how large the horizontal and
     
    2619should be, at which times and points plot output are supposed to be
    2720made, etc. <br>
    28 </p>
    29 <p style="line-height: 100%;">These data are assigned with the help of
    30 so-called ?“NAMELIST-driven input”? (FORTRAN - NAMELIST –
    31 input). The ?gewählten? values of the model parameters are written
     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
    3227into an ASCII file with fixed format, which is expected by the model as
    3328an input
     
    3934PARIN: <br>
    4035&nbsp; </p>
    41 <ul>
    42   <p style="line-height: 100%; font-family: monospace;">&amp;inipar nx
     36<ul> <p style="line-height: 100%; font-family: monospace;">&amp;inipar
     37nx
    4338= 79, ny = 79, nz = 40, <br>
    44 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dx = 50.0, dy = 50.0, dz =
     39&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     40dx = 50.0, dy = 50.0, dz =
    454150.0, <br>
    46 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; initializing_actions =
     42&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
     43initializing_actions =
    4744"set_1d-model_profiles", <br>
    48 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; prandtl_layer = .TRUE.,/ </p>
    49   <p style="line-height: 100%; font-family: monospace;">&amp;d3par&nbsp;
    50 end_time = 9000.0, section_xy = 1, 10, 20,/ </p>
    51   <p style="line-height: 100%; font-family: monospace;">&amp;packagename
    52 var1 = .TRUE. / </p>
    53   <p style="line-height: 100%;"><span style="font-family: monospace;">&amp;userpar
     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
    5449abcd = 1234,0,/ </span><br>
    5550&nbsp; <br>
    5651&nbsp;</p>
    57 </ul>
    58 <p style="line-height: 100%;">The parameters are separated into four
     52</ul><p style="line-height: 100%;">The parameters
     53are separated into four
    5954different groups which all start with the so-called NAMELIST group
    6055names.
    61 These are <span style="font-family: monospace;">&amp;inipar</span>, <span
    62  style="font-family: monospace;">&amp;d3par</span> and <span
    63  style="font-family: monospace;">&amp;packagename</span> as well as <span
    64  style="font-family: monospace;">&amp;userpar</span>. In each case a
     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
    6561group is terminated with one backslash ("/"). Between the beginning of
    6662the line and the group name at least one blank has to be typed. Between
     
    7167concerning the NAMELIST syntax, refer to
    7268appropriate FORTRAN manuals. <br>
    73 </p>
    74 <p style="line-height: 100%;">Parameters belonging to the group <span
    75  style="font-family: monospace;">inipar</span> are first read by PALM.
     69</p><p style="line-height: 100%;">Parameters
     70belonging to the group <span style="font-family: monospace;">inipar</span>
     71are first read by PALM.
    7672These are the initialization parameters. Second, the so-called run
    7773parameters belonging to the group <span style="font-family: monospace;">d3par</span>
     
    8278group name of the respective package) as well as user-defined
    8379parameters
    84 (group <span style="font-family: monospace;">userpar</span>). The four
    85 groups must be given in this order, the last groups, <span
    86  style="font-family: monospace;">packagename</span> and <span
    87  style="font-family: monospace;">userpar</span>, may
     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
    8885be omitted. If several software packages are selected
    8986(see chapter <a href="chapter_3.7.html">3.7</a>),
    90 further NAMELIST groups may be inserted before the group <span
    91  style="font-family: monospace;">userpar</span>.
    92 </p>
    93 <p style="line-height: 100%;"><b>The initialization, run</b> and
     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
    9490<b>package parameters</b> differ as follows: </p>
    95 <ul>
    96   <li>
    97     <p style="margin-bottom: 0cm; line-height: 100%;">The <b>initialization
    98 parameters </b>are steering the basic settings of the model run. They
     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
    9994define e.g. the number of the grid points, the numerical schemes to be
    10095used, initial and boundary conditions to be applied, how the
     
    10499run and thus can not be changed with restart runs! If one tries to
    105100change these values within the NAMELIST input file of a restart run,
    106 then these changes are ignored (sole exception is the parameter <a
    107  style="font-family: monospace;"
    108  href="chapter_4.1.html#initializing_actions">initializing_actions</a><font
    109  style="font-size: 10pt;" size="2">, </font>which must be given the
    110 value<span style="font-family: thorndale,serif,mon;"> </span><span
    111  style="font-family: monospace; font-style: italic;">read_restart_data</span><span
    112  style="font-family: thorndale,serif,mon;"> for </span>restart runs). <br>
    113 &nbsp; </p>
    114   </li>
    115   <li>
    116     <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run
    117 parameters</b> are generally steering actions to be carried out during
     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
    118108a model run. One can select for example, at which times plot output
    119109should happen and which variables are to be written. Additionally one
     
    123113usually keep their values, provided that the NAMELIST input file was
    124114not changed by the user in the meantime). <br>
    125 &nbsp; </p>
    126   </li>
    127   <li>
    128     <p style="line-height: 100%;"><b>Package parameters</b> behave like
    129     <b>run parameters</b>. Package parameters determine the behavior of
    130 the additional (not user-defined) software packages . </p>
    131   </li>
    132 </ul>
    133 <p style="line-height: 100%;">The user-defined parameters are assigned
    134 by the user within the NAMELIST group name <tt>&amp;userpar</tt> (see <a
    135  href="chapter_3.5.2.html">chapter
    136 3.5.2</a>). They steer actions programmed by the user. By default,
     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,
    137125this group has only one parameter (<a href="chapter_4.3.html#region">region</a>).
    138126If the
    139127user don't want to assign any values to the user-defined&nbsp;
    140 parameters, the group<span style="font-family: monospace;"> userpar
    141 </span>may be omitted. The group name <span
    142  style="font-family: monospace;">&amp;userpar</span>
     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>
    143131can be changed by the user in the user-defined code. In
    144132addition to this, further NAMELIST groups may also be declared (all
     
    146134in file <span style="font-family: monospace;">user_interface.f90</span>).
    147135<a href="chapter_4.4.html">Chapter
    148 4.4</a> shows a simple but complete example of the input file PARIN.
     1364.4</a> shows a simple but complete example of the input file
     137PARIN.
    149138This example file can be used together with the configuration file
    150139(described in <a href="chapter_3.2.html">chapter
     
    156145explanation are described in the lists of the following subsections. <br>
    157146&nbsp; </p>
    158 <hr>
    159 <p style="line-height: 100%;"><br>
    160 <font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font
    161  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    162  border="2" height="32" width="32"></font></a><a href="index.html"><font
    163  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    164  border="2" height="32" width="32"></font></a><a href="chapter_4.1.html"><font
    165  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    166  border="2" height="32" width="32"></font></a></font></font><br>
    167 &nbsp;
     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;
    168149<br>
    169 &nbsp;<span style="font-style: italic;">Last change:</span> 15/04/05
    170 (SR)<br>
    171 </p>
    172 </body>
    173 </html>
     150&nbsp;<span style="font-style: italic;">Last change:</span>
     151$Id$<br>
     152</p></body></html>
Note: See TracChangeset for help on using the changeset viewer.