source: palm/trunk/DOC/app/chapter_4.3.html @ 217

Last change on this file since 217 was 217, checked in by letzel, 13 years ago
  • NCL scripts in trunk/SCRIPTS/NCL updated
  • Property svn:keywords set to Id
File size: 9.5 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2<html><head>
3<meta http-equiv="CONTENT-TYPE" content="text/html; charset=windows-1252"><title>PALM chapter 4.3</title> <meta name="GENERATOR" content="StarOffice 7 (Win32)"> <meta name="AUTHOR" content="Siegfried Raasch"> <meta name="CREATED" content="20041013;13364831"> <meta name="CHANGED" content="20041015;15380006"> <meta name="KEYWORDS" content="parallel LES model"> <style>
4<!--
5@page { size: 21cm 29.7cm }
6-->
7</style></head>
8<body style="direction: ltr;" lang="en-US"><h3 style="line-height: 200%;">4.3 User-defined parameters</h3>
9<table style="width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr valign="top">
10<td> <p><font size="4"><b>Parameter name</b></font></p>
11</td> <td> <p><font size="4"><b>Type</b></font></p>
12</td> <td> <p><b><font size="4">Default</font></b>&nbsp;
13<br> <b><font size="4">value</font></b></p>
14</td> <td> <p><font size="4"><b>Explanation</b></font></p>
15</td> </tr> <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="data_output_pr_user"></a>data_output_pr_user</span></td><td style="vertical-align: top;">C * 10<br>(200)</td><td style="vertical-align: top;"><span style="font-style: italic;">200 * ' '</span></td><td style="vertical-align: top;">User defined quantities for
16which horizontally averaged profile data is to be output.<br><br>Beside
17the PALM standard output quantities (which can be selected via
18parameter <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>),
19the user can define (without any restriction) additional output
20quantities (e.g. turbulent resolved-scale horizontal momentum fluxes, etc.). Each of these
21quantities has to be given a unique identifier (string) which must be
22different from the strings defining the standard output quantities (see
23list from the description of <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>).
24Data output can be switched on by assigning the respective strings to <span style="font-weight: bold;">data_output_user</span>.<br><br>The
25user has to calculate/provide the respective data array(s) by
26appropriately extending the user interface (see <a href="chapter_3.5.4.html">3.5.4</a>).<br><br>For
27further steering of the user defined output (output times, cross
28section levels, time averaging, etc.), the steering parameters for <a href="chapter_4.2.html#data_output_pr">data_output_pr</a>
29apply accordingly.</td></tr><tr><td style="vertical-align: top;"><a name="data_output_user"></a><span style="font-weight: bold;">data_output_user</span></td><td style="vertical-align: top;">C * 10 (100)</td><td style="vertical-align: top;"><span style="font-style: italic;">100 * ' '</span></td><td style="vertical-align: top;">User defined quantities for
30which 2d cross section and/or 3d volume data are to be output.<br><br>Beside
31the PALM standard output quantities (which can be selected via
32parameter <a href="chapter_4.2.html#data_output">data_output</a>),
33the user can define (without any restriction) additional output
34quantities (e.g. the temperature variance, etc.). Each of these
35quantities has to be given a unique identifier (string) which must be
36different from the strings defining the standard output quantities (see
37list from the description of <a href="chapter_4.2.html#data_output">data_output</a>).
38Data output can be switched on by assigning the respective strings to <span style="font-weight: bold;">data_output_user</span>.<br><br>The
39user has to calculate/provide the respective data array(s) by
40appropriately extending the user interface (see <a href="chapter_3.5.4.html">3.5.4</a>).<br><br>For
41further steering of the user defined output (output times, cross
42section levels, time averaging, etc.), the steering parameters for <a href="chapter_4.2.html#data_output">data_output</a>
43apply accordingly.<br><br><span style="font-weight: bold;">Example:</span><br>If
44the user defined output quantity is the temperature variance and if the
45user has chosen the string <span style="font-style: italic;">'pt2'</span>
46as an identifier for this quantity, then output of horizontal cross
47sections can be selected by assigning <span style="font-weight: bold;">data_output_user</span> = <span style="font-style: italic;">'pt2_xy'</span>.</td></tr><tr valign="top"> <td> <p><b><a name="region"></a>region</b></p> </td>
48<td> <p>C*40 (0:9)</p> </td> <td> <p>&nbsp;</p>
49</td> <td> <p>Name(s) of the subdomain(s) defined
50by the user.&nbsp; </p> <p>With this variable, names
51can be assigned to the subsections
52defined by the user (see <a href="chapter_4.1.html#statistic_regions">statistic_regions</a>)
53which afterwards appear in the headers of the respective files (<a href="chapter_3.4.html#PLOT1D_DATA">PLOT1D_DATA</a>)
54and within the respective plots. Up to 9 subdomains are allowed (<b>region</b>
55(1) to <b>region</b> (9)), the total domain has the index
560 (<b>region</b>
57(0)).</p> </td> </tr><tr><td style="vertical-align: top;"><a name="topography_grid_convention"></a><span style="font-weight: bold;">topography_grid_</span><br style="font-weight: bold;"><span style="font-weight: bold;">convention</span></td><td style="vertical-align: top;">C*11</td><td style="vertical-align: top;"><span style="font-style: italic;">default depends on value of <a href="chapter_4.1.html#topography">topography</a>; see text for details</span><span style="font-style: italic;"></span></td><td style="vertical-align: top;">Convention for defining the&nbsp;topography grid.<br><br>Possible values are<br><ul><li><span style="font-style: italic;">'cell_edge':&nbsp;</span>the distance between cell edges defines the extent of topography. This setting is normally for <span style="font-style: italic;">generic topographies</span>, i.e. topographies that are constructed using length parameters. For example, <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'single_building'</span> is constructed using <a href="chapter_4.1.html#building_length_x">building_length_x</a> and <a href="chapter_4.1.html#building_length_y">building_length_y</a>. The advantage of this setting is that the actual size of generic topography is independent of the grid size, provided that the length parameters are an integer multiple of the grid lengths&nbsp;<a href="chapter_4.1.html#dx">dx</a> and&nbsp;<a href="chapter_4.1.html#dy">dy</a>. This is convenient&nbsp;for resolution parameter studies.</li><li><span style="font-style: italic;">'cell_center'</span><span style="font-style: italic;">:&nbsp;</span>the number of topography cells define the extent of topography. This setting is normally for <span style="font-style: italic;">rastered real topographies</span> derived from digital elevation models.&nbsp;For example, <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'read_from_file'</span> is constructed using&nbsp;the input file <a href="chapter_3.4.html#TOPOGRAPHY_DATA">TOPOGRAPHY_DATA</a><font color="#000000">.&nbsp;</font>The
58advantage of this setting is that the&nbsp;rastered topography cells of
59the input file are directly mapped to topography grid boxes in PALM. <span style="font-style: italic;"></span></li></ul>The example files for&nbsp;<big><code>sgl_bldg_cell_center</code></big> and
60<big><code>sgl_bldg_cell_edge</code></big> in <big><code>trunk/EXAMPLES/</code></big>
61illustrate the difference between
62both approaches. Both examples simulate a single building and yield the
63same results. The former uses a rastered topography input file with <span style="font-style: italic;">'cell_center'</span> convention, the latter applies a generic topography with <span style="font-style: italic;">'cell_edge'</span> convention.<br><br>The default value is<br><ul><li><span style="font-style: italic;">'cell_edge' </span>if <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'single_building'</span>,</li><li><span style="font-style: italic;">'cell_center'</span><span style="font-style: italic;"></span> if <a href="chapter_4.1.html#topography">topography</a> = <span style="font-style: italic;">'read_from_file'</span>,</li><li><span style="font-style: italic;">none (' '</span> ) otherwise, leading to an abort if&nbsp;<span style="font-weight: bold;">topography_grid_convention</span> is not set.</li></ul>This means that <br><ul><li>For PALM simulations using a <span style="font-style: italic;">user-defined topography</span>, the<span style="font-weight: bold;"> topography_grid_convention</span> must be explicitly set to either <span style="font-style: italic;">'cell_edge'</span> or <span style="font-style: italic;">'cell_center'</span>.</li><li>For PALM simulations using a <span style="font-style: italic;">standard topography</span> <span style="font-style: italic;">('single_building'</span> or <span style="font-style: italic;">'read_from_file')</span>, it is possible but not required to set the&nbsp; <span style="font-weight: bold;">topography_grid_convention</span> because appropriate default values apply</li></ul></td></tr> </tbody>
64</table><p style="line-height: 200%;">&nbsp; <br>
65&nbsp; </p>
66<hr><p><br>
67<font color="#000080"><font color="#000080"><a href="chapter_4.2.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.4.html"><font color="#000080"><img src="right.gif" name="Grafik3" align="bottom" border="2" height="32" width="32"></font></a></font></font></p><p><span style="font-style: italic;">Last change:</span>
68$Id: chapter_4.3.html 217 2008-12-09 18:00:48Z letzel $&nbsp;</p>
69</body></html>
Note: See TracBrowser for help on using the repository browser.