Changeset 62 for palm/trunk/DOC/app/chapter_4.0.html
- Timestamp:
- Mar 13, 2007 2:52:40 AM (18 years ago)
- File:
-
- 1 edited
-
palm/trunk/DOC/app/chapter_4.0.html (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_4.0.html
r54 r62 1 1 <!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 4 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 <!-- 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 11 Steering parameters</font></h2> 12 <p style="line-height: 100%;">Before carrying out a model 13 run, the user 21 14 has to /determine/ a data set - the model parameters - e.g. how 22 15 many grid points are to be used, how large the horizontal and … … 26 19 should be, at which times and points plot output are supposed to be 27 20 made, 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 22 assigned with the help of 23 so-called ?“NAMELIST-driven input”? (FORTRAN - 24 NAMELIST – 25 input). The ?gewählten? values of the model parameters are 26 written 32 27 into an ASCII file with fixed format, which is expected by the model as 33 28 an input … … 39 34 PARIN: <br> 40 35 </p> 41 <ul> 42 <p style="line-height: 100%; font-family: monospace;">&iniparnx36 <ul> <p style="line-height: 100%; font-family: monospace;">&inipar 37 nx 43 38 = 79, ny = 79, nz = 40, <br> 44 dx = 50.0, dy = 50.0, dz = 39 40 dx = 50.0, dy = 50.0, dz = 45 41 50.0, <br> 46 initializing_actions = 42 43 initializing_actions = 47 44 "set_1d-model_profiles", <br> 48 prandtl_layer = .TRUE.,/ </p> 49 <p style="line-height: 100%; font-family: monospace;">&d3par 50 end_time = 9000.0, section_xy = 1, 10, 20,/ </p> 51 <p style="line-height: 100%; font-family: monospace;">&packagename 52 var1 = .TRUE. / </p> 53 <p style="line-height: 100%;"><span style="font-family: monospace;">&userpar 45 46 prandtl_layer = .TRUE.,/ </p> <p style="line-height: 100%; font-family: monospace;">&d3par 47 end_time = 9000.0, section_xy = 1, 10, 20,/ </p> <p style="line-height: 100%; font-family: monospace;">&packagename 48 var1 = .TRUE. / </p> <p style="line-height: 100%;"><span style="font-family: monospace;">&userpar 54 49 abcd = 1234,0,/ </span><br> 55 50 <br> 56 51 </p> 57 </ul> 58 <p style="line-height: 100%;">The parametersare separated into four52 </ul><p style="line-height: 100%;">The parameters 53 are separated into four 59 54 different groups which all start with the so-called NAMELIST group 60 55 names. 61 These are <span style="font-family: monospace;">&inipar</span>, <span 62 style="font-family: monospace;">&d3par</span> and <span 63 style="font-family: monospace;">&packagename</span> as well as <span 64 style="font-family: monospace;">&userpar</span>. In each case a 56 These are <span style="font-family: monospace;">&inipar</span>, 57 <span style="font-family: monospace;">&d3par</span> 58 and <span style="font-family: monospace;">&packagename</span> 59 as well as <span style="font-family: monospace;">&userpar</span>. 60 In each case a 65 61 group is terminated with one backslash ("/"). Between the beginning of 66 62 the line and the group name at least one blank has to be typed. Between … … 71 67 concerning the NAMELIST syntax, refer to 72 68 appropriate 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 70 belonging to the group <span style="font-family: monospace;">inipar</span> 71 are first read by PALM. 76 72 These are the initialization parameters. Second, the so-called run 77 73 parameters belonging to the group <span style="font-family: monospace;">d3par</span> … … 82 78 group name of the respective package) as well as user-defined 83 79 parameters 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>). 81 The four 82 groups 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>, 84 may 88 85 be omitted. If several software packages are selected 89 86 (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 87 further NAMELIST groups may be inserted before the group <span style="font-family: monospace;">userpar</span>. 88 </p><p style="line-height: 100%;"><b>The 89 initialization, run</b> and 94 90 <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 92 parameters </b>are steering the basic settings of the model run. 93 They 99 94 define e.g. the number of the grid points, the numerical schemes to be 100 95 used, initial and boundary conditions to be applied, how the … … 104 99 run and thus can not be changed with restart runs! If one tries to 105 100 change 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 </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 101 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 102 must be given the 103 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 104 runs). <br> 105 </p> </li> <li> <p style="margin-bottom: 0cm; line-height: 100%;">The <b>run 106 parameters</b> are generally steering actions to be carried out 107 during 118 108 a model run. One can select for example, at which times plot output 119 109 should happen and which variables are to be written. Additionally one … … 123 113 usually keep their values, provided that the NAMELIST input file was 124 114 not changed by the user in the meantime). <br> 125 </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>&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 </p> </li> <li> <p style="line-height: 100%;"><b>Package parameters</b> 116 behave like <b>run parameters</b>. Package parameters 117 determine the behavior of 118 the additional (not user-defined) software packages . </p> </li> 119 </ul><p style="line-height: 100%;">The user-defined 120 parameters are assigned 121 by the user within the NAMELIST group name <tt>&userpar</tt> 122 (see <a href="chapter_3.5.2.html">chapter 123 3.5.2</a>). They steer actions programmed by the user. By 124 default, 137 125 this group has only one parameter (<a href="chapter_4.3.html#region">region</a>). 138 126 If the 139 127 user don't want to assign any values to the user-defined 140 parameters, the group<span style="font-family: monospace;"> userpar141 </span>may be omitted. The group name <span 142 style="font-family: monospace;">&userpar</span>128 parameters, the group<span style="font-family: monospace;"> 129 userpar 130 </span>may be omitted. The group name <span style="font-family: monospace;">&userpar</span> 143 131 can be changed by the user in the user-defined code. In 144 132 addition to this, further NAMELIST groups may also be declared (all … … 146 134 in file <span style="font-family: monospace;">user_interface.f90</span>). 147 135 <a href="chapter_4.4.html">Chapter 148 4.4</a> shows a simple but complete example of the input file PARIN. 136 4.4</a> shows a simple but complete example of the input file 137 PARIN. 149 138 This example file can be used together with the configuration file 150 139 (described in <a href="chapter_3.2.html">chapter … … 156 145 explanation are described in the lists of the following subsections. <br> 157 146 </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 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> 168 149 <br> 169 <span style="font-style: italic;">Last change:</span> 15/04/05 170 (SR)<br> 171 </p> 172 </body> 173 </html> 150 <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.
