Mar 12, 2007 5:42:06 AM (15 years ago)

further preliminary changes for revision 3.2

1 edited


  • palm/trunk/DOC/app/chapter_3.7.html

    r54 r61  
    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 3.7</title>
    7   <meta name="GENERATOR" content="StarOffice 7  (Win32)">
    8   <meta name="AUTHOR" content="Siegfried Raasch">
    9   <meta name="CREATED" content="20040809;13460943">
    10   <meta name="CHANGED" content="20041112;15085727">
    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 <h3 style="line-height: 100%;">3.7 Optional software packages</h3>
    20 <p style="line-height: 100%;">Starting from version 2.1 PALM includes
     3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM
     4chapter 3.7</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20040809;13460943"> <meta name="CHANGED" content="20041112;15085727"> <meta name="KEYWORDS" content="parallel LES model"> <style>
     6@page { size: 21cm 29.7cm }
     10<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 100%;">3.7 Optional software packages</h3>
     11<p style="line-height: 100%;">Starting from version 2.1
     12PALM includes
    2113so-called software packages which can be used optionally. These
    2214software packages are part of the model, but they are not compiled with
    2719compilation time as well as the memory demand of the model is limited
    2820to the real needs. </p>
    29 <p style="line-height: 100%;">To use software packages in a model run,
    30 they must be requested with <b>mrun</b> option <tt><font
    31  style="font-size: 10pt;" size="2">-p</font>.</tt>
     21<p style="line-height: 100%;">To use software packages in
     22a model run,
     23they must be requested with <b>mrun</b> option <tt><font style="font-size: 10pt;" size="2">-p</font>.</tt>
    3224Then the subroutines belonging to the respective package are
    3325additionally compiled for the run (and the respective restart
    3426runs; the filenames of these subroutines are also displayed on the
    35 terminal after <b>mrun</b> has been called). If one wants to use e.g.
     27terminal after <b>mrun</b> has been called). If one wants
     28to use e.g.
    3629the two packages with the names
    37 <tt>package1</tt> and <tt>package2</tt>, then the <b>mrun</b> call
     30<tt>package1</tt> and <tt>package2</tt>, then
     31the <b>mrun</b> call
    3832has to be: </p>
    39 <ul>
    40   <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
    41  size="2">mrun ... -p “package1 package2” </font>.</tt></p>
    42 </ul>
    43 <p style="line-height: 100%;">Further package names can be added to
     33<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">mrun ... -p
     34&ldquo;package1 package2&rdquo; </font>.</tt></p>
     35</ul><p style="line-height: 100%;">Starting from version 3.2, the particles-package is part of the default model, so it does not have to be switched on using <span style="font-weight: bold;">mrun</span>-option <span style="font-family: Courier New,Courier,monospace;">-p</span>. However, the respective parameters have still to be set by using the NAMELIST group <span style="font-family: Courier New,Courier,monospace;">particles_par</span>.</p><p style="line-height: 100%;">Further package
     36names can be added to
    4437the list, separated by blanks. If the respective packages permit user
    4538steering, the appropriate parameters must be given at the end of
    4639the file <a href="chapter_3.4.html#PARIN">PARIN</a>.
    47 They must be given <b>before</b> possible user-defined parameters!
     40They must be given <b>before</b> possible user-defined
    4842Each package requires its own NAMELIST group. The respective NAMELIST
    4943group name is given in the table below. For the example above one
    5044would have to add the following lines to PARIN (example): &nbsp; </p>
    51 <ul>
    52   <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
    53  size="2">&amp;namelist_packagename1 var1 = 1,0, var2 =
    54 “abcd” /</font></tt><font style="font-size: 10pt;" size="2"> </font> </p>
    55   <p style="line-height: 100%;"><tt><font style="font-size: 10pt;"
    56  size="2">&amp;namelist_packagename2 var3 = .TRUE.,
     45<ul> <p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">&amp;namelist_packagename1
     46var1 = 1,0, var2 =
     47&ldquo;abcd&rdquo; /</font></tt><font style="font-size: 10pt;" size="2"> </font> </p>
     48<p style="line-height: 100%;"><tt><font style="font-size: 10pt;" size="2">&amp;namelist_packagename2
     49var3 = .TRUE.,
    5750var4 = 0 /</font></tt></p>
    58 </ul>
    59 <p style="margin-bottom: 0cm; line-height: 100%;">The following
     51</ul><p style="margin-bottom: 0cm; line-height: 100%;">The
    6053packages are available: <br>
    6154&nbsp; <br>
    6255&nbsp; </p>
    63 <table border="1" cellpadding="2" cellspacing="2" width="100%">
    64   <tbody>
    65     <tr>
    66       <td>
    67       <p><b>Package name:</b></p>
    68       </td>
    69       <td>
    70       <p><b>NAMELIST group name:</b></p>
    71       </td>
    72       <td>
    73       <p><b>Functionality:</b></p>
    74       </td>
    75       <td>
    76       <p><b>Control parameter:</b></p>
    77       </td>
    78     </tr>
    79     <tr valign="top">
    80       <td>
    81       <p>particles</p>
    82       </td>
    83       <td>
    84       <p>particles_par</p>
    85       </td>
    86       <td>
    87       <p>Release and advection of particles. The particle sources can
    88 additionally be defined by the user in subroutine <tt><font
    89  style="font-size: 10pt;" size="2">user_init_particles</font></tt> .</p>
    90       </td>
    91       <td>
    92       <p>see section 4.2</p>
    93       </td>
    94     </tr>
    95     <tr valign="top">
    96       <td>
    97       <p>dvrp_graphics</p>
    98       </td>
    99       <td>
    100       <p>dvrp_graphics_par</p>
    101       </td>
    102       <td>
    103       <p>Graphical output with the dvrp software of the RRZN. This is
     56<table border="1" cellpadding="2" cellspacing="2" width="100%"> <tbody> <tr> <td> <p><b>Package
     57name:</b></p> </td> <td> <p><b>NAMELIST
     58group name:</b></p> </td> <td> <p><b>Functionality:</b></p>
     59</td> <td> <p><b>Control parameter:</b></p>
     60</td> </tr> <tr valign="top"> <td> <p>--- (see above)</p>
     61</td> <td> <p>particles_par</p> </td> <td>
     62<p>Release and advection of particles. The particle sources can
     63additionally be defined by the user in subroutine <tt><font style="font-size: 10pt;" size="2">user_init_particles</font></tt>
     64.</p> </td> <td> <p>see section 4.2</p>
     65</td> </tr> <tr valign="top"> <td> <p>dvrp_graphics</p>
     66</td> <td> <p>dvrp_graphics_par</p> </td>
     67<td> <p>Graphical output with the dvrp software of the
     68RRZN. This is
    10469only available on the IBM Regatta "hanni" of the HLRN. Possible output
    10570are iso-surfaces, cross-sections and particles (if the particle package
    106 is selected). The use of this package is described in section <a
    107  href="chapter_4.5.7.html">4.5.7</a>.</p>
    108       </td>
    109       <td>
    110       <p>see section 4.2</p>
    111       </td>
    112     </tr>
    113     <tr valign="top">
    114       <td>
    115       <p>spectra</p>
    116       </td>
    117       <td>
    118       <p>spectra_par</p>
    119       </td>
    120       <td>
    121       <p>Computation and output of horizontal power spectra of the
    122 prognostic variables. </p>
    123       </td>
    124       <td>
    125       <p>see section <a href="chapter_4.2.html#spectra_package">4.2</a></p>
    126       </td>
    127     </tr>
    128   </tbody>
    129 </table>
    130 <hr>
    131 <p style="line-height: 100%;"><br>
    132 <font color="#000080"><font color="#000080"><a href="chapter_3.6.html"><font
    133  color="#000080"><img src="left.gif" name="Grafik1" align="bottom"
    134  border="2" height="32" width="32"></font></a><a href="index.html"><font
    135  color="#000080"><img src="up.gif" name="Grafik2" align="bottom"
    136  border="2" height="32" width="32"></font></a><a href="chapter_4.0.html"><font
    137  color="#000080"><img src="right.gif" name="Grafik3" align="bottom"
    138  border="2" height="32" width="32"></font></a></font></font></p>
    139 <p style="line-height: 100%;"><i>Last change:&nbsp;</i> 15/04/05 (SR)</p>
    140 </body>
    141 </html>
     71is selected). The use of this package is described in section <a href="chapter_4.5.7.html">4.5.7</a>.</p> </td>
     72<td> <p>see section 4.2</p> </td> </tr>
     73<tr valign="top"> <td> <p>spectra</p> </td>
     74<td> <p>spectra_par</p> </td> <td> <p>Computation
     75and output of horizontal power spectra of the
     76prognostic variables. </p> </td> <td> <p>see
     77section <a href="chapter_4.2.html#spectra_package">4.2</a></p>
     78</td> </tr> </tbody>
     80<p style="line-height: 100%;"><br><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.0.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p>
     81<p style="line-height: 100%;"><i>Last
     82change:&nbsp;</i> $Id$</p>
Note: See TracChangeset for help on using the changeset viewer.